TK.

Hi Henk, yes, it's even more flexible (and accurate) than the old approach Yes You wouldn't be able to use the MIDIbox LC application with these OLEDs (unless you've some programming skills to change the source code for your purposes) Therefore the usage of MIDIbox NG is probably a better idea much better, because it's fully customizable without source code modifications. E.g. here the .NGC configuration which emulates a Logic Control: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftemplates%2Flogictrl.ngc Best Regards, Thorsten.

Does this mean, that with this application the green LED doesn't flash anymore? To MIDIO128: please ensure, that you are using the latest version (V3.016) - I remember that there was a problem with one of the earlier versions. Best Regards, Thorsten.

This is really strange (especially because I haven't changed something on the mute function). I can't reproduce this with my existing sessions (ok, I only picked up 2 different sessions, one where drums are at G1T1, another one where they are at G3T2) Best Regards, Thorsten.

Hi, the green LED should slowly fade between on and off (PWM modulated) - periodically. Is this what you mean with "sometimes remains lit, or unlit"? Or do you mean that it stops fading sometimes? And: did you already try to debug this with the ainser_jitter_mon application? It should show you, which inputs are exactly problematic Best Regards, Thorsten.

open seq_ui.c, search for SEQ_UI_Button_Stop change it, so that enable_slaveclk_mute is always 0 (currently it is "u8 enable_slaveclk_mute = !SEQ_BPM_IsMaster()") Then search for SEQ_UI_Button_Play disable the branch where it checks for !SEQ_BPM_IsMaster() Best Regards, Thorsten.

It enables open drain mode as expected... But I didn't remember anymore, that IO pins of a STM32 device with optional analog function are not 5V tolerant. I'm sorry for the wrong and confusing advice! So: the only solution is to change the hardware as proposed in my first reply. Best Regards, Thorsten.

That's unfortunately correct. All analog pins of the STM32 have internal protection diodes against 3.3V, therefore the 5V level can't be reached. Best Regards, Thorsten.

Hehe... ;) This is just the Piano track when it's plays guitar samples. I enabled the echo function with +1..+12 Notes per echo, this leads to the typical glissando. :smile: Best Regards, Thorsten.

I think that the ALL button should get a better purpose in the Mute page. E.g. if ALL is pushed, all tracks will be muted And by pressing&holding MUTE (track mutes will be visible), the ALL button will set these mutes instead of the track mutes. I can confirm that I've a similar issue! :-( Does anybody know, if there are better switches available, which are compatible to this one: http://www.digikey.com/product-detail/en/TL1100F160Q/EG1821-ND/59082 Hm... this seems to be a different issue? Mutes are usually not stored. Best Regards, Thorsten.

There is no migration tool for old patterns available. It would be too much effort to develop this. Best Regards, Thorsten.

This patch was for MBSID V1, not V2... Today there are easier methods which don't require a source code modification. E.g. you could change the MIDI channels with the Ctrlr based editor. And then send following string with the SysEx tool of MIOS Studio to permanently store the ensemble setup: F0 00 00 7E 4B 00 0C 18 70 F7 Best Regards, Thorsten.

Precise (MIDI clock based) control is usually done in the SEQ_CORE_Tick function based on bpm_tick (see seq_core.c) E.g. if you would like to synchronize to the measure, see how the EXT_RESTART_REQ is handled. Best Regards, Thorsten.

set_lock <id> 0 Best Regards, Thorsten.

Ist nun in v1.025 eingebaut - und zwar per default (weil es Sinn macht!) Gruss, Thorsten.

implemented in v1.025 Best Regards, Thorsten.

set_lock is finally available in V1.025 Best Regards, Thorsten.

A new release is available - after more than 1 month, therefore with many bugfixes and enhancements reported/requested by the users :) MIDIbox NG V1.025 ~~~~~~~~~~~~~~~~~ o new terminal commands: - ngc: allows to execute a .NGC command directly - ngr: allows to execute a .NGR command directly - ngr_section: sets the ^section for .NGR execution - ngr_value: sets the ^value for .NGR execution - run: can now also executed without specified <section> <value> (the previously set values will be taken in this case) o inofficial support for MAX72xx chains - see cfg/tests/max72xx.ngc for a configuration example (no schematic available yet) o .NGR: fixed "delay statements in if branches" issue o .NGR: added "set_lock" command. It allows to prevent, that received events will overwrite a value of an event. o .NGR: the "set" command now also allows to change variables, e.g.: set ^value 1 set ^section 2 set ^bank 3 (etc...) the last one (^bank) will also switch MBNG to the specified bank o .NGR: added variables ^dev, ^pat, ^bnk, ^ins, ^chn These are the same which can be used in SysEx strings, and which can be changed in a SCS page (e.g. the variables could also be used for different purposes) o added new SCS menu page to execute the .NGR file with given ^section and ^value o the AIN command now supports the "resolution" parameter o the AINSER command now supports the "muxed" parameter. Use muxed=1 for the AINSER64 module (default), and muxed=0 for the AINSER8 module. o AIN and AINSER events, which are assigned to Note events, send velocity 0 before a new Note is sent with velocity > 0 to avoid hanging notes. o added "ain_filter_delay_ms" to support sensors (experimental stage) o EVENT_RECEIVER in conjunction with ^txt or ^txt56: if ^cursor is not specified in the SysEx stream, it will start at offset 0 from the specified lcd_pos=<device>:<x>:<y> o EVENT ... syxdumppos now supports the full receiver range 1..4095 (previously only 1..15) o the MIDI router forwards SysEx messages regardless if channels are filtered, or "All" is used. It's ensured that messages are only sent once if multiple router nodes forward to the same destination port. Best Regards, Thorsten.

Could you please try if such a mode would really help, or if it would lead to new issues, so that such a dedicated extension is not useful at all? Please add following filter to the NOTIFY_MIDI_Rx function in app.c: Best Regards, Thorsten.

This seems to be a very tricky circuit. Actually two pins are involved: pin 7 controls the latch (=RCLK in MIDIbox terminology) Pin 8 serves clock and data. The clock will be delayed by several nS - I guess that depending on the pulse modulation either a 1 or 0 will be shifted into the register. E.g.: _____ ___| |___ will shift a 1, and _ ___| |______ could shift a 0? This is only an assumption, and the appr. software changes into MIOS could only be developed by a real expert! Best Regards, Thorsten.

The cursor caused problems with certain LCDs in the past, therefore I haven't considered it in the software anymore. It would also be too cumbersome to make it only optional, because supporting two different display options is really a nightmare for testing UI enhancements! :-( Best Regards, Thorsten.

Are they also 5V if the .NGC file is (almost) empty, resp. when it only contains the RESET_HW command? Then it's probably related to a connection error between J8/9 and the shift register chain. Best Regards, Thorsten.

Ja, der Sound sticht auch heutzutage noch aus der breiten Masse an Synths heraus! :smile: Im Source Code gibt es nur drei Zeilen, in denen ein '|' ausgegeben wird: src/cs_menu.inc:276: movlw '|' src/cs_menu.inc:396: movlw '|' src/sid_lcd.inc:237: movlw '|' Du koenntest sie bspw. '|' durch ein grosses 'I' ersetzen. Oder durch ein Leerzeichen, falls Dir das besser gefaellt. Bis Du in der Lage, den Code selbst zu aendern und zu kompilieren? Hier ist bspw. eine Quickstart Guide fuer Windows: http://www.midibox.org/dokuwiki/doku.php?id=windows_toolchain_quickstart&s[]=toolchain (gibt es auch fuer MacOS und Linux) Gruss, Thorsten.

Thanks for the sign of life! :smile: How did you experience the tornado? According to the newspapers it was one of the worst ever! Is it almost so horrible like in the destroyed area at your place, or not worse like after a heavy storm? Best Regards, Thorsten.

Thank you for the update! After I got the shocking news, I was searching in the internet for informations as well, and found this map at CNN: http://edition.cnn.com/interactive/2013/05/us/moore-oklahoma-tornado/?hpt=hp_t2 SmashTV lives ca. 0.5 miles north from the affected area - this is relieving! Best Regards, Thorsten.