TK.

10 uS scan cycle for 64bit means that the required scan frequency is ca. 6.5 MHz. This can't be done with the PIC (if other tasks should run in parallel), but it's possible w/o much programming effort with MIOS32, because the DMA could fetch the shift registers in background while the CPU processes the results of the previous scan in parallel. Best Regards, Thorsten.

The upload shouldn't take longer than 10 seconds; it seems that you are using a MIDI interface which can't handle SysEx messages which are much longer than 100 bytes. 1) check if your MIDI interface is on the blacklist 2) check if there is a driver update for your MIDI interface 3) let us know which interface you are using, and under which operating system it is running. 4) Copy&Paste the output of the MIDI IN window (ca. 1 page is enough) because it may contain helpful diagnosis messages Best Regards, Thorsten.

Any other hardware, such as a PC or Mac? Any software you are already using and which supports OSC? Without more informations from your side it's really hard to propose a suitable setup. If you would own a MBSEQ V4, TouchOSC could send OSC packets to MBSEQ via a WiFi router. MBSEQ can convert OSC to MIDI messages, and then forward to sammichSID. Best Regards, Thorsten.

Of course you have my permission - but you should really keep it! :) Best Regards, Thorsten.

See http://svnmios.midibox.org/filedetails.php?repname=svn.mios&path=%2Ftrunk%2Fapps%2Fsynthesizers%2Fmidibox_sid_v2%2Fsrc%2Fsid_frq_table.inc The formula for calculating these numbers is well described in the SID datasheet Best Regards, Thorsten.

Wait for MBSID V3 no it won't be based on MBHP_CORE_STM32, but on a new board with a more suitable microcontroller. yes, it will provide an integrated ethernet controller yes, ethernet, USB, CAN and MIDI can be used in parallel. yes it will provide OSC Therefore it doesn't make much sense to document the halffinished stuff based on obsolete hardware - especially not to people w/o programming knowledge. However, there are many PC/Mac based possibilities to transfer OSC to MIDI - unfortunately you haven't specified, which HW/SW you already own. Even with MBHP_CORE_STM32 and MBHP_ETH it's possible, but as mentioned above: if you don't own this HW yet, it doesn't make much sense anymore to invest into it. More infos about this topic soon. Best Regards, Thorsten.

It could be directly connected to a MBSEQ V4, especially since a special 303 Edit view is available meanwhile. Parameters can be controlled from a dedicated Mixer Map, complete patches (stored on SD Card) could be sent from the SysEx menu :) Best Regards, Thorsten.

The FT232 chip has to be connected directly to J11 (without optocoupler) anyhow, because it works at TTL level and not as a current loop like MIDI. With All-Zero ID the MIDI interface will run at a common MIDI baudrate of 31250 - is it possible to select this baudrate on a FT232? Best Regards, Thorsten.

I must say that I haven't expected that R30 could disturb serial transfers to the SD Card - I will add a comment! Best Regards, Thorsten.

Edelst!!! :smile: Gruss, Thorsten. P.S.: habe das Posting in die "MIDIbox of the Week" Sektion verschoben

Great project and a very nice price! I guess that the CS will run on a second chip which sends the parameters to the "SSP" via MIDI? Is it possible to reprogram the chip, resp. to try code modifications? Best Regards, Thorsten.

Congratulations! It's especially great to see that you got it housed into the Heidenreich case with Julians frontpanel! This proves that it works! :) Best Regards, Thorsten.

Maybe the FT232BL transmits at the wrong baudrate? (I've no experiences with this chip... at the time it was released I already developed my own MIDI interfaces ;)) Best Regards, Thorsten.

Possible: yes Application: nobody implemented this for MBSID yet... a sophisticated ripper exists for HardSID as far as I remember. Best Regards, Thorsten.

:ahappy: Best Regards, Thorsten.

Beta37 is available - from the ChangeLog: MIDIboxSEQ V4.0beta37 ~~~~~~~~~~~~~~~~~~~~~ o Length Page: quick selection now also available for loops. o Length Page: length/loop presets are now stored in MBSEQ_C.V4 file (located in session directory) under the name "QuickSelLength", "QuickSelLoopLength" and "QuickSelLoopLoop". They could be edited with a text editor if you would like to have different values. o track transpose page now always starts with "octave" item instead of "semitones" item o it's now possible to define 16 individual "direct track selection" buttons in MBSEQ_HW.V4 (search for BUTTON_DIRECT_TRACK*) o it's now possible to define 2 shift registers for outputing the current track selection in MBSEQ_HW.V4 (search for TRACKS_DOUT_L_SR and TRACKS_DOUT_R_SR) o copy function works correctly now if a track is pasted into another track with different partitioning in Paste/Clr = Steps mode (selectable in Utils->Options page) [/code] Best Regards, Thorsten.

Using multiple looppoints is the wrong way, as you would have to define them again and again whenever you created a new pattern. They would also consume some (expensive) pattern memory... although they are never used at the same moment. Therefore I added a new "loop preset" feature into Beta37 (see ChangeLog below) Well, as I mentioned earlier, I'm using octave changes more often as well. In order to move drum kit instrument, I set the semitone individually for each instrument under Track->Event So: I changed it back to octave on page entry in Beta37 Best Regards, Thorsten.

It's viable, but creating a useful GUI will be a huge task. You could already re-organize your sessions by using the session import/export function under Util->Disk It allows to copy patterns from other sessions to create a new session (or vice versa: copy patterns of the current session into another session) Once this has been done, just copy the appr. session directory (/SESSIONS/<session-name>) to the SD Card of the other MBSEQ V4 Best Regards, Thorsten.

Beta36 is available now: MIDIboxSEQ V4.0beta36 ~~~~~~~~~~~~~~~~~~~~~ o The metronome function considers the "steps per measure" correctly now o received MIDI song position command sets the track positions correctly now - this is important when MBSEQ is controlled by a clock master. E.g. Logic Studio sends startpoint-1 when the sequencer continues in a loop [/code] The changes in beta36 are not really related to your observations (I haven't found any dependency on G1T1), but while checking the code I found that steps per measure wasn't used by the metronome as intended, especially on "unequal steps". Also the song position handling of previous versions could lead to a misaligned step counting if MBSEQ is clocked by an external MIDI clock master. Init/Copy issues reported by Echopraxia: nothing done yet, still needs some more thinking about all possible cases. A fix for the copy function is difficult, but feasible. The INIT function can't be realized without clearing all track values (e.g. otherwise layers would play wrong events if their mode is changing, e.g. from CC to Note - very bad while playing live!) Maybe I will implement a new repartitioning function, I would find it useful as well Best Regards, Thorsten.

I tried different brands as well and never noticed unreliable operation, only different performance factors. Would it be possible to send me the non-working SD Cards for further analysis? The metronome already works independent from any track, if you noticed a dependency on G1T1 you found an unexpected bug! The signature is defined as "steps-per-measure", which has to be set in the options page (UTILS->OPT) - it even allows you to define unequal steps (free definable from 1-256) For 3/4 just select 12 (1/16) steps. Best Regards, Thorsten.

To 1) seems to be correct To 2) really strange issue, I never saw this on one of my own LCDs. However, there aren't so many lines which have to be changed: mm:midibox_fm_v1 TK$ grep \'\|\' src/* src/cs_menu.inc: movlw '|' src/cs_menu.inc: movlw '|' src/cs_menu.inc: movlw '|' src/cs_menu.inc: movlw '|' src/cs_menu.inc: movlw '|' src/cs_menu.inc: movlw '|' src/cs_menu.inc: movlw '|' src/cs_menu.inc: movlw '|' [/code] Best Regards, Thorsten.

Also software-wise it's difficult to do this, some clever copy routines are required to change the partitioning properly under all circumstances. It's the same issue like with the copy function that you reported before. There is currently no solution. Great that you found a solution! I will highlight in the documentation that Sandisk cards should be preferred. Best Regards, Thorsten.

You could take the encoder handling code in cs_m_pattern.inc as a template Best Regards, Thorsten.

Selbst eine voll ausgebaute MBSID V1 kann man problemlos auf V2 umruesten :) Siehe auch http://www.ucapps.de/midibox_sid_manual_up.html Den SIDplayer fuer die V1 Hardware habe ich irgendwann von meiner Webseite genommen, da ja mittlerweile jeder auf V2 umgestiegen ist... nunja, scheinbar doch nicht jeder... Wenn Du Glueck hast, funktioniert er noch mit dem aktuellen MIOS: http://www.ucapps.de/mios/sidplayer_v1b.zip Diese Release ist mittlerweile 7 Jahre alt - die Garantie ist somit abgelaufen! ;) Gruss, Thorsten.