TK.

A new release is available: MIDIboxSEQ V4.059 ~~~~~~~~~~~~~~~~~ o added Euclidean Rhythm Generator for drum and synth sequences. The page can be entered by pressing&holding SELECT in the edit menu -> GP16 o fixed stack overflow which happened when incoming OSC messages were forwarded to OSC in Live mode (they are now automatically filtered to avoid feedback loops) o fixed group selection in BUTTON_DIRECT_TRACK1...16 [/code] Background infos to the Euclidean Rhythm Generator: http://www.ucapps.de/midibox_seq_manual_m.html and Have fun! :smile: Best Regards, Thorsten.

-> TODO (together with the missing patch store/restore capabilities) Btw.: you could already add a simple program/bank change button to the panel by yourself, just enter edit mode and add the controllers! :) Best Regards, Thorsten.

Tja, passt doch! Vielleicht gibt es in Cubase noch mehr Optionen, die Du unabsichtlich aktiviert hast? Das Verhalten "Wenn ich in den Einstellungen die Flags auf Relative stelle, springt der Fader in Cubase zwischen Max., Mitte und Min. " hoert sich so an, als waere ein Modus aktiv, der fuer Decrement den Wert 127, und fuer Increment den Wert 0 erwartet. Den wuerde man mit: int value = incrementer & 0x7f; [/code] programmieren - und die Werte 63/65 wuerde in diesem Fall fuer einen Maximalausschlag sorgen. Gruss, Thorsten.

Your idea doesn't harmonize with the initial concept behind Song/Phrase mode, therefore there won't be a proper solution. In distance, with such an automation you are adding new cases which might be annoying or confusing, such as: - unintended re-latching of mutes if the user temporary switches to another page (e.g. mixer page, or effects), and back to song page while song is playing - mutes could have been latched for a different pattern set with a different organization of instruments, so that the expired setup will mute different instruments - actually I think it's much better if the pattern set and mute setup stays active at the end of a song, e.g. it allows to continue jamming live ("encore!") What are the advantages of this restore operation, and compare it with the disadvantages. Note: if somebody just wants to mute all tracks, or unmute all tracks for editing purposes, he could use the appr. functions in the Utility menu (GP15 and GP16) Best Regards, Thorsten.

Master or Slave mode? Best Regards, Thorsten.

Yes of course, there are no "shadowed" mutes for song mode, they are just controlled from the song list. Your modification can cause the problem that Mutes could get inconsistent over long term, because the user isn't aware of this dependency (mutes copied only if song is not playing) Best Regards, Thorsten.

Please try the following: 1) upload the latest mios32_bootloader application (-> http://www.ucapps.de/mios32_download.html) 2) thereafter enter 'help' in the MIOS terminal -> do you see the commands? Best Regards, Thorsten.

Hi, no, the schematic isn't wrong: I've configured the Tx pin in Open Drain Mode Accordingly a logic-1 will set the pin into high-impedance state, and the voltage level will be pulled to 5V. This is the preferred solution for MIDI. Yes: if you configure the pin in Push-Pull mode, you've to connect the 220 Ohm resistor to 3.3V, but I strongly recommend to change the pin configuration instead. Best Regards, Thorsten.

I can reproduce this, it seems to be related to a software bug which only exists for the CS_SAMMICH_FM option. I will check this soon. Best Regards, Thorsten.

Do you mean that you want to send the same parameter changes to multiple SIDs? Currently this can't be selected in the panel, but it would be possible to add the function. Best Regards, Thorsten.

ok from my side Best Regards, Thorsten.

Using terminal commands is the way to go - these are common SysEx commands which contain ASCII informations. If you are working on a Mac, you could use the "Spy" feature of the Snoize MIDI Monitor to find out how the SysEx string looks like. E.g. "set router 1 OSC4 all USB1 all" is: 00 F0 00 00 7E 32 00 0D 00 73 65 74 20 72 6F 75 74 | ~2 set rout| 10 65 72 20 31 20 4F 53 43 34 20 61 6C 6C 20 55 53 |er 1 OSC4 all US| 20 42 31 20 61 6C 6C 0A F7 |B1 all | [/code] Best Regards, Thorsten.

Isn't this what the "SEQ_SONG_ActiveGet()== 0" condition is causing? Best Regards, Thorsten.

Hm... there is currently no solution to realize this. I possible solution would be a new option which would use a given track as measure reference instead of a static number of steps (let's call it "guide track"). But I'm unsure about the side effects, e.g. when the song position is changed from a DAW. Also the synchronization with external MIDI devices could be difficult, as they rely on a predefined (and never changing) bar counting. Best Regards, Thorsten.

Die PIC basierten Applikationen lassen sich ueber das Terminal nicht konfigurieren. Dafuer gibt es jedoch eine "change_id" Applikation auf der MIOS Download Page, die weiterhilft (README lesen) Gruss, Thorsten.

Very strange! Are you using your MBSEQ in Master or Slave mode? And could you please give my your "system" information after it happenes: 1) play the song until it gets out-of-sync with your MIDI gear 2) open MIOS Studio and connect to your MBSEQ 3) enter "system" in the MIOS Terminal 4) post the output here Best Regards, Thorsten.

Hallo, die "relativen MIDI Events" sind leider nicht genormt, hier gibt es unterschiedliche Varianten - welche wird von Cubase verwendet? Steht das evtl. im Handbuch? Gruss, Thorsten.

Schick' mir bitte mal beide Platinen zu, ich moechte mir das genauer anschauen (auch im Hinblick auf zukuenftige Troubleshooting-Tips) Gruss, Thorsten.

To give us an oversight: - the SID connections are ok, because pressing PLAY starts a sound - your MIDI interface sends the right MIDI events - MIDImon shows that the PIC really receives the events. - the correct MIDI channel has been selected in the ensemble INS menu So, it's not a hardware issue, and since such a behaviour was never reported by somebody else before, also a software issue can be excluded. Therefore I expect a configuration issue. In an earlier posting I asked you to check the MIDI channel in the INS menu, but I haven't got feedback yet. Aside from the MIDI channel, also a keyboard zone can be configured there. Could it be, that it's limited to a certain keyboard range? It would also be interesting how your MIDIbox behaves if it boots without banksticks. Just pull them out of the sockets, reboot the MIDIbox and play some keys. Best Regards, Thorsten.

It displays the current pattern (regardless if it has been generated or not), and will be updated whenever an encoder changes the Step/Pulse or Offset value. Initially this was only intended as a debugging help for me, but then I noticed how essential it is to see the current pattern without the need for going back to the edit screen, especially when the offset value is changed to get pulses matching with the pulses of other drum instruments. Best Regards, Thorsten.

Yes, command line options would probably really a better solution, because I noticed that otherwise there are more GUI enhancements required than expected. Best Regards, Thorsten.

Most of those interfaces are on the blacklist: http://www.midibox.org/dokuwiki/doku.php?id=midi_interface_blacklist Especially this one which is available at Amazon for 7 EUR (since years) but doesn't output (and receive) SysEx properly: ^^^^^^^^ Don't buy! Best Regards, Thorsten.

no, this isn't necessary. The SRIO software driver controls both pins with the same value to ensure compatibility with earlier designs (MBHP_CORE and MBHP_CORE_STM32) It should be possible (and it's a good idea), but I've no schematic on hand to show you the circuit. Basically you need to build the same optocoupler circuit like used for the MIDI IN, but the 1k pull-up should be connected to ground (-> pull-down) Best Regards, Thorsten.

It doesn't work this way due to various reasons: a) as mentioned just one posting above your one the firmware doesn't scan additional DIN pins. You will need a fith core, e.g. running with MIDIO128 b) the HUI protocol doesn't allow to control multiple HUI instances from a single MIDI port, therefore the chaining method won't work -> each core has to be connected to a dedicated MIDI interface port. For both reasons, the best solution is probably to use a MBHP_CORE_LPC17 module in addition, running with MIDIO128. The MBHP_MF_NG modules can be connected to the 4 MIDI IN/OUT ports. Thereafter setup the MIDIO128 based MIDI router to forward the MIDI events directly to the 4 separate USB MIDI ports. In addition, the same app can be used to scan additional buttons and to drive LEDs (up to 128 in a non-matrix configuration) Best Regards, Thorsten.

Das Tutorial ist leider noch nicht fertig (kann noch mind. eine Woche dauern), doch Du koenntest mal in die MIDIO128 reinschauen, wie man so etwas macht: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidio128_v3%2Fsrc%2Fmidio_matrix.c Siehe auch die entsprechenden Function Calls in app.c Im Tutorial wird der Code noch einfacher (und ueberschaubarer) sein. Gruss, Thorsten.