TK.

...or change the way how you download files. A single click will download and unzip the file into the Downloads folder. The .jar File won't be unpacked in this case. The layout will be automatically stored when you exit MIOS Studio properly. Don't use Cmd-Q (like for other Mac applications), but use File->Exit Best Regards, Thorsten.

"ww kabel 1" ist just a test that we are able to rename the ports again!!! :thumbsup: Please say "vielen dank" to Ploytec support! :ahappy: Best Regards, Thorsten.

Of course! Thanks! :) Best Regards, Thorsten.

Vista/Win7 users: please try this version: http://www.ucapps.de/gm5/midibox.org_gm5_WIN32_1.0.10.zip (32bit) http://www.ucapps.de/gm5/midibox.org_gm5_X64_1.0.10.zip (64bit) Best Regards, Thorsten.

Hi Simca, I don't mean this as a personal attack against you, but there is a certain danger that Newbies we don't know use this forum for fake deals or as a commercial platform. By answering to this topic, you demonstrated that you are not an automated forum robot - great! ;) Could you please also post a picture of the Knobs next to your MIDIbox to show us, that they are real? Best Regards, Thorsten.

Newbie alarm... Best Regards, Thorsten.

Unfortunately Ploytec isn't able to reproduce this issue. Something must be different at our side. Therefore I'm asking again: is there any Vista/Windows7 user who got the new driver release successfully running? And to the users who noticed this issue: which configuration (J1/J2/J3/J8 switches) are you using exactly? Best Regards, Thorsten.

Hi, Most simple solution: just upload the MIDIO128 application :) You will find some additional troubleshooting tips for the DIN module here: http://www.midibox.org/dokuwiki/doku.php?id=din_module Best Regards, Thorsten.

I consider to write a benchmark to determine the true speed under MIOS32, since there is no standard for rating SD Cards - as you noticed, "60x" is just a housenumber - It's printed on a noname card that I bought from a supermarket some time ago, and the speed was comparable with the SanDisk SD Card which I'm normaly using. I've another noname card (2GB from Reichelt), which is extremely slow, especially when writing files. No speed infos are print on this card... Some kind of "benchmark" is already part of the firmware I gave you. Nothing is more realistic than directly comparing how long it takes to load a pattern or to process the FAT. :) Best Regards, Thorsten.

:) Could you please upload following firmware: http://www.ucapps.de/tmp/mbseqtest.zip Toggle between the patterns until you notice the glitch again. Thereafter go to the "About this MIDIbox" page, and dump out the System and SD Card informations to the MIOS Terminal (part of MIOS Studio). This firmware uses the Stopwatch to measure the time between Pattern changes. If it takes too long, I've to adjust the timings. Otherwise I need more informations how to reproduce this. E.g., if this happens while switching between two certain patterns, then write them into the preset directory (Track Events->Presets->Save as New Preset") and attach the files to this article. Best Regards, Thorsten.

Beta14 is available: o prepared support for MBHP_BLM_SCALAR. The MIDI port can be configured in Options menu (Utility->Opt.) o various minor bugfixes [/code] Link to BLM_SCALAR emulation (Mac OS Leopard/Snow Leopard only) http://www.ucapps.de/mbhp/blm_scalar_emulation.zip Setup: MIDIbox SEQ: select the MIDI port to which the BLM is linked in the Utility->Opt. page with GP Encoder #16 Emulation: select the same MIDI In/Out port The matrix should be updated automatically. Try different dimensions - 64x16 is a really useful configuration. Currently we have display buttons for Triggers (e.g. Drum patterns), Tracks and Patterns. One function that I'm planning to add next is the possibility to display Accents in the trigger page with the Red LEDs, and to activate accent by pressing "Triggers"+BLM button. Gridracer: it would be interesting if your BLM configuration is still working, since I had to change a lot of code which is also used for common 16x4 BLMs directly connected to the core. Best Regards, Thorsten.

It's the big advantage of the MIDI event scheduler, that even such features are possible now :) Not really, it should work in pause mode. I will check this sooner or later. Best Regards, Thorsten.

Hi Janis, No, this configuration isn't supported by the AOUT_LC driver. Yes, it will be slower. There is a higher danger for MIDI IN buffer overruns. The best solution to get 8x12 bit is the usage of a AOUT_NG module, since it doesn't require to update all channels if only the value of a single channel has changed. This improves the performance significantly. Best Regards, Thorsten.

Sidenote: if this still doesn't help, you have to generate a .syx file in a newer format which is supported by MIDIbox 64 V2 I created this format since so many people were not able to upload large SysEx dumps with their MIDI interface. Details are described here: http://www.ucapps.de/howto_tools_mbsyx.html Meanwhile, mk_syx is part of the midibox64 package, so it's already on your harddisk (-> midibox64_v2_4c/tool/mk_syx directory) Best Regards, Thorsten.

This issue isn't related to MIOS, but to your MIDI interface under Windows. Solution: use MIDI-Ox to upload the .syx file First enter following setup into the configuration window of the SysEx tool: Thereafter load the file into the command window of the SysEx tool: And send it to your MIDIbox: Best Regards, Thorsten.

No, this isn't possible since v1.2 bootloader overlaps the mios v1.8 address range - but why do you need MIOS V1.8? Best Regards, Thorsten.

Btw.: is any Mac user interested on a BLM_SCALAR emulation? I'm using it to test the protocol with matrix dimensions which I would never build myself ;) The application communicates with your MBSEQ via MIDI. Planned features: track editing, drum pattern editing, piano roll editor, pattern selection, mixer control, VU meters, etc.. all implemented in the MBSEQ firmware, the BLM_SCALAR application only acts as a stupid display/data entry device. Best Regards, Thorsten.

Thank you! While I got a notification from goldphoenix last year (see my last posting in this thread), this time I got it from another well known guy: Von: SmashTV <avishowtech@gmail.com> Betreff: MIDIbox Store Order Shipped Datum: 17. November 2009 23:35:45 MEZ An: midibox.org Forum <tk@midibox.org> :) Best Regards, Thorsten.

I have to overwork this section. No, it doesn't have an effect on Roll. The gatelengths are predefined: // force gatelength depending on number of triggers if( triggers < 4 ) { // number of triggers: 2 3 4 5 const u8 gatelength_tab[4] = { 48, 32, 36, 32 }; // strategy: // 2 triggers: played within 1 step at 0 and 48 // 3 triggers: played within 1 step at 0, 32 and 64 // 4 triggers: played within 1.5 steps at 0, 36, 72 and 108 // 5 triggers: played within 1.5 steps at 0, 32, 64, 96 and 128 // in addition, scale length (0..95) over next clock counter to consider the selected clock divider gatelength = (gatelength_tab[triggers-2] * t->step_length) / 96; } [/code] In order to implement such a feature properly, I would have to overwork the concept how encoder speed is handled, and finding a better concept will take some time. So - only a quick idea or really an important feature? Currently the FAST button exclusively controls the encoder speed (which is handled by MIOS32) - for this feature, I would have to make an exception when a "Note" or "Chord" layer is selected. It will become complicated and error prone once switching between layers, switching to a menu page, etc. have to be considered as well... therefore a different concept would be required which considers certain layer/parameter type specific constraints. Such a mechanism wouldn't allow you to handle accent and gate separately, which is important whenever you are working with "prepared grooves", which are starting with a small number of gate triggers, and are enriched by more triggers (or at the end: all steps triggered) while the sequence is playing. I get use of this possibility very often to vary the patterns during a session. You could simply trigger your drummachine from a J5.A0..A7 gate, controlled from a dedicated track which plays 16 notes at the desired clock rate. The clock rate is defined by the clock divider value and normal/triplet mode. Now activate a groove style for this track -> done. :) Best Regards, Thorsten.

It's now documented here: http://www.ucapps.de/mbhp_sdcard.html Best Regards, Thorsten.

Then I've no idea. Maybe google helps you to find more informations about using a Standard USB MIDI device on a PowerPC based Mac. Best Regards, Thorsten. P.S.: it could be important that your core module is powered from an external PSU, or from an USB hub with a "strong" PSU supply.

Thats the tip of the month! :) I will try this as well (already have a Micro SD Card + adaptor) and document it on the MBHP_SDCARD page. Best Regards, Thorsten.

No, an additional installation isn't required. Do you see the device in the Audio-MIDI Setup Application? (see Attachment) Best Regards, Thorsten.

Shipped today: kinrat eightbithustler Best Regards, Thorsten.

Beta 13 is available; ChangeLog: o pulsewidth of DIN Sync clock pulsewidth now definable in MBSEQ_HW.V4 file (DIN_SYNC_CLK_PULSEWIDTH parameter) o Parameter/Trigger Layer selection can now be quickly incremented/decremented by pressing&holding Layer C button, and incrementing with Layer A button, resp. decrementing with Layer B button. o various minor bugfixes [/code] Best Regards, Thorsten.