TK.

no news yet Best Regards, Thorsten.

Congratulations for the next lovely song! :) Best Regards, Thorsten.

Ok, it's set to 129 by default now. No, there is unfortunately no debouncing for encoders. It could be, that they are bouncing a bit more than normally due to the increased SRIO scan rate. Best Regards, Thorsten.

Well, how would you react if you spent several days for the implementation of an editor, and then get the naive complaint that it doesn't work, forget it, your documentation doesn't help, and help me (now!). I think that you expect too much from an open source project which has been developed during sparetime. E.g. a documentation which even explains the very basic things (from my point of view). Do you see a way to clarify your issue on a more comfortable way for both sides? You don't consider the history. Several Ctrlr versions have been released by atom so far, there are dependencies between the panel and the Ctrlr release which have to be considered. You mention that issues have been reported - based on which version, at which point of time? You even haven't mentioned yet, which Ctrlr version you are using, under which operation system in which mode (Standalone, VST, AU)? Your approach isn't academic! Best Regards, Thorsten.

An academical question: if a Ctrlr based panel, which has been tested by multiple people, doesn't work reliable at your side, how can you be sure that your tries with a self-written editor will work better? However, much more detailed informations can be found in the Lua scripts which are embedded into the Ctrlr panel. Alternatively you could have a look into the sources of the Java based editor: http://svnmios.midibox.org/listing.php?repname=svn.mios&path=%2Ftrunk%2Fjava%2F These are two complete open source solutions which should give you enough details to implement a third one, if you really feel that this is the right way. Best Regards, Thorsten.

Hi, I'm very surprised that the Ctrl based panel doesn't work at your side, because it has been tested by multiple people. And I feel demotivated to comment your questions when you are saying that it is buggy at absolute best -> don't expect support from my side... I spent days to make this happen, but only get a stupid complaint from you. My assumption is, that you are not using the right Ctrlr version which is linked at this page: Best Regards, Thorsten.

Unfortunately I've to confirm that this one won't work, it doesn't support SysEx transfers. Some time ago I tested it by myself (-> http://www.amazon.de/KORN-MIDI-USB-INTERFACE-Kabel/dp/B001383XTS/ref=sr_1_2?ie=UTF8&qid=1367270045&sr=8-2&keywords=midi+interface ), there is no workaround. :-( Some people started a Whitelist which helps to find a reliable interface: http://www.midibox.org/dokuwiki/doku.php?id=midi_interface_whitelist With some luck you will be able to buy such an interface second-hand from Ebay (to save some money) Best Regards, Thorsten.

Hi Stephan, if the diodes are in the right direction, no inversion would be required. Neither for the selection lines, nor for the rows. Did you test this as well? Btw.: "inverted=1" and "inverted_sel=1" are actually doing the same. "inverted" only exists due to compatibility reasons. Best Regards, Thorsten.

MBNG currently only supports 64 encoders + 1 for the SCS (I could increase the number meanwhile if this was your question) It's a bug that no error message is generated for n=65 It's no bug that an error message will be generated for n=66 and above Best Regards, Thorsten.

I'm surprised about the difference, because it doesn't make sense (from my point of view). The SRs are linearly addressed. The 5th DOUT in the chain should be sr_dout_r2=5 With the lre8x2x4.ngc it's proven that the numbering works (and it should be independent from the number of rows): http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftemplates%2Flre8x2x4.ngc Are you able to isolate this issue a bit more? no The implementation of scrambling options are error prone, and they especially won't be tested with each new MBNG version. Therefore I don't like such options. I guess that currently you don't use EVENT_LED statements, but address the LEDs with "virtual events" based on their emulated id, right? You could try to do the mapping by defining EVENT_LED events for each LED function, and map the ids to different hw_ids I've no oversight if this trick will really work under all circumstances, but if it works, you are done. If not, it's less likely that I will enhance the firmware to solve such a mapping issue (as mentioned above) Best Regards, Thorsten.

Das Layout ist aber sehr stark am Blofeld orientiert... ;-) Gruss, Thorsten.

the PIC has no integrated USB-MIDI interface, accordingly it can't report the interface name... correct - you've to select the MIDI IN/OUT port of your MIDI interface which is connected to the PIC Upload won't work if even the Query function doesn't work (which checks the bidirectional connection) You mean this one? http://www.ucapps.de/howto_debug_midi.html For remote diagnosis we have to know the outcome of each test in such a form: TEST PC1: done, ok TEST MIDI1: done, ok TEST MIDI2: done, ok TEST OUT1: ... so, TEST OUT1 seems to fail What about TEST PC1, TEST MIDI1 and TEST MIDI2? And the remaining tests if TEST OUT1 is working for some reason (because you found the problem, but Query still doesn't work) Another important question: is your MIDI Interface on the blacklist? -> http://www.midibox.org/dokuwiki/doku.php?id=midi_interface_blacklist Best Regards, Thorsten.

Thanks for testing! :) I just have released the updated 2.4.5 binary unfortunately I can't prevent this, because the number of lines in the info window is limited, so that some lines are truncated E.g. "MIOS_Studio --version --help" will print the version at the top, but one additional line of the help page is missing... now set before Query the Windows console workaround is now applied when --batch is at any position in the command line, so that the ports should be displayed now. Best Regards, Thorsten.

MIOS Studio 2.4.5 is available now Changes: support for command line parameters (see documentation at the MIOS Studio page) MIOS Filebrowser now sorts the directory Best Regards, Thorsten.

Hi Rodolfo, one of the reason is, that with more keyboards the scan frequency decreases, which results into higher latencies. And a practical reason is, that the EEPROM dump structure can only store two set of keyboard parameters - fixing this would result into a lot of incompatible changes. However, you could try MIDIbox NG instead, which comes with the same keyboard driver. In MBNG I could easily increase the number of keyboards (in one of the next versions), because parameters are stored in a configuration file on SD Card. See also the kb_*.ngc examples under: http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2F The usage of MBNG has another advantage: you can easily add more control elements (like drawbars, etc.) Best Regards, Thorsten.

Seems that the inversion flags haven't been set correctly Best Regards, Thorsten.

The mechanism should also work for encoders sending CCs Keep in mind, that the receiver id has to be < 16 ("syxdump_pos=n:p" -> n should be < 16) Best Regards, Thorsten.

Hi Andrew, independent bank zones could be created with conditional events, see also this example: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fconev_3.ngc An alternative approach would be the usage of a .NGR script: http://www.ucapps.de/midibox_ng_manual_ngr.html I'm planning to add an "enable_event" and "disable_event" command which allows to control the state of EVENTs like the bank feature is doing, but with the possibility to maintain each EVENT separately. Best Regards, Thorsten.

There is unfortunately no robust way to use the console from where MIOS Studio has been started. I've tested the workaround to output text in a new console, this seems to work stable. In order to avoid, that the text messages get lost when the batch jobs have been executed, the console has to be closed with the enter key. It would be nice if you could test this at your side: -> http://www.ucapps.de/mios_studio/MIOS_Studio_2_4_5.zip Available options (inclusive the proposed ones): Command Line Parameters: --help this page --version shows version number --batch don't open GUI --in=<port> optional search string for MIDI IN port --out=<port> optional search string for MIDI OUT port --device_id=<id> sets the device id, should be done before upload if necessary --query queries the selected core --upload_hex=<file> upload specified .hex file to core. Multiple --upload_hex allowed! --upload_file=<file> upload specified file to SD Card. Multiple --upload_file allowed! --send_syx=<file> send specified .syx file to core. Multiple --send_syx allowed! --terminal=<command> send a MIOS terminal command. Multiple --terminal allowed! --wait=<seconds> Waits for the given seconds. --gui_x=<x>: specifies the initial window X position --gui_y=<y>: specifies the initial window Y position --gui_width=<width>: specifies the initial window width --gui_height=<height>: specifies the initial window height --gui_title=<name>: changes the name of the application in the title bar --gui_hide_monitors: disables the MIDI IN/OUT monitor when GUI is started --gui_hide_upload: disables the upload panel when GUI is started --gui_hide_terminal: disables the terminal panel when GUI is started --gui_hide_keyboard: disables the virtual keyboard panel when GUI is started Usage Examples: MIOS_Studio --in=MIOS32 --out=MIOS32 starts MIOS Studio with MIDI IN/OUT port matching with 'MIOS32' MIOS_Studio --upload_hex=project.hex starts MIOS Studio and uploads the project.hex file immediately MIOS_Studio --batch --upload_hex=project.hex starts MIOS Studio without GUI and uploads the project.hex file MIOS_Studio --batch --upload_file=default.ngc --upload_file=default.ngl starts MIOS Studio without GUI and uploads two files to SD Card (MIOS32 only) MIOS_Studio --batch --terminal="help" --wait=1 starts MIOS Studio, executes the "help" command in MIOS Terminal and waits 1 second for response NOTE: most parameters can be combined to a sequence of operations. E.g. upload a .hex file, upload files to SD Card, execute a terminal command and wait some seconds before exit. Best Regards, Thorsten.

Well, a command line interface for MIOS Studio was on my TODO list since years, today I implemented it: Command Line Parameters: --help this page --version shows version number --batch don't open GUI --in=<port> optional search string for MIDI IN port --out=<port> optional search string for MIDI OUT port --device_id=<id> sets the device id, should be done before upload if necessary --query queries the selected core --upload_hex=<file> upload specified .hex file to core. Multiple --upload_hex allowed! --upload_file=<file> upload specified file to SD Card. Multiple --upload_file allowed! --send_syx=<file> send specified .syx file to core. Multiple --send_syx allowed! --terminal=<command> send a MIOS terminal command. Multiple --terminal allowed! --wait=<seconds> Waits for the given seconds. Usage Examples: MIOS_Studio --in=MIOS32 --out=MIOS32 starts MIOS Studio with MIDI IN/OUT port matching with 'MIOS32' MIOS_Studio --upload_hex=project.hex starts MIOS Studio and uploads the project.hex file immediately MIOS_Studio --batch --upload_hex=project.hex starts MIOS Studio without GUI and uploads the project.hex file MIOS_Studio --batch --upload_file=default.ngc --upload_file default.ngl starts MIOS Studio without GUI and uploads two files to SD Card (MIOS32 only) MIOS_Studio --batch --terminal="help" --wait=1 starts MIOS Studio, executes the "help" command in MIOS Terminal and waits 1 second for response NOTE: most parameters can be combined to a sequence of operations. E.g. upload a .hex file, upload files to SD Card, execute a terminal command and wait some seconds before exit. It doesn't match with your proposals... hope that you don't mind. E.g. specifiying the target file (+path) requires much more programming and testing effort at my side. If you want to use different file names, you would have to rename the files on your harddisk before upload. The command line extensions are perfectly working under MacOS and Linux, e.g.: macmini2:midibox_ng_v1 TK$ ../../../tools/mios_studio/Builds/MacOSX/build/Release/MIOS_Studio.app/Contents/MacOS/MIOS_Studio --batch --upload_hex=project.hex --upload_file=cfg/templates/lre8x2x4.ngc Waiting for first query. Operating System: MIOS32 Board: MBHP_CORE_LPC17 Core Family: LPC17xx Chip ID: 0x26113f37 Serial: #70E02121AE022535DBA7CCC47000005F Flash Memory Size: 524288 bytes RAM Size: 65536 bytes MIDIbox NG V1.025 © 2013 T.Klose Uploading project.hex... Reading project.hex Trying to contact the core... Upload in progress... project.hex contains 240996 bytes (942 blocks). 0 of 942 blocks (0%) 64 of 942 blocks (6%) 67 of 942 blocks (7%) 76 of 942 blocks (8%) 85 of 942 blocks (9%) 95 of 942 blocks (10%) 104 of 942 blocks (11%) 116 of 942 blocks (12%) 124 of 942 blocks (13%) 132 of 942 blocks (14%) 143 of 942 blocks (15%) 153 of 942 blocks (16%) 161 of 942 blocks (17%) 170 of 942 blocks (18%) 181 of 942 blocks (19%) 190 of 942 blocks (20%) 199 of 942 blocks (21%) 208 of 942 blocks (22%) 217 of 942 blocks (23%) 228 of 942 blocks (24%) 237 of 942 blocks (25%) 245 of 942 blocks (26%) 255 of 942 blocks (27%) 264 of 942 blocks (28%) 275 of 942 blocks (29%) 283 of 942 blocks (30%) 293 of 942 blocks (31%) 302 of 942 blocks (32%) 311 of 942 blocks (33%) 321 of 942 blocks (34%) 330 of 942 blocks (35%) 341 of 942 blocks (36%) 349 of 942 blocks (37%) 358 of 942 blocks (38%) 368 of 942 blocks (39%) 378 of 942 blocks (40%) 387 of 942 blocks (41%) 398 of 942 blocks (42%) 406 of 942 blocks (43%) 415 of 942 blocks (44%) 424 of 942 blocks (45%) 435 of 942 blocks (46%) 443 of 942 blocks (47%) 455 of 942 blocks (48%) 462 of 942 blocks (49%) 471 of 942 blocks (50%) 482 of 942 blocks (51%) 491 of 942 blocks (52%) 500 of 942 blocks (53%) 510 of 942 blocks (54%) 520 of 942 blocks (55%) 529 of 942 blocks (56%) 538 of 942 blocks (57%) 548 of 942 blocks (58%) 556 of 942 blocks (59%) 566 of 942 blocks (60%) 575 of 942 blocks (61%) 585 of 942 blocks (62%) 595 of 942 blocks (63%) 603 of 942 blocks (64%) 614 of 942 blocks (65%) 622 of 942 blocks (66%) 634 of 942 blocks (67%) 642 of 942 blocks (68%) 650 of 942 blocks (69%) 660 of 942 blocks (70%) 671 of 942 blocks (71%) 680 of 942 blocks (72%) 688 of 942 blocks (73%) 698 of 942 blocks (74%) 708 of 942 blocks (75%) 716 of 942 blocks (76%) 728 of 942 blocks (77%) 735 of 942 blocks (78%) 746 of 942 blocks (79%) 756 of 942 blocks (80%) 765 of 942 blocks (81%) 774 of 942 blocks (82%) 783 of 942 blocks (83%) 794 of 942 blocks (84%) 802 of 942 blocks (85%) 811 of 942 blocks (86%) 821 of 942 blocks (87%) 829 of 942 blocks (88%) 839 of 942 blocks (89%) 849 of 942 blocks (90%) 859 of 942 blocks (91%) 867 of 942 blocks (92%) 878 of 942 blocks (93%) 887 of 942 blocks (94%) 896 of 942 blocks (95%) 905 of 942 blocks (96%) 914 of 942 blocks (97%) 925 of 942 blocks (98%) 934 of 942 blocks (99%) 942 of 942 blocks (100%) Upload of 224768 bytes completed after 6.07s (36.16 kb/s) Waiting for reboot... [631821.499] [MBNG_LCD] no response from CLCD #2.1 [631821.499] [MBNG_LCD] no response from CLCD #3.1 [631821.500] [MBNG_LCD] no response from CLCD #4.1 [631821.500] [MBNG_LCD] no response from CLCD #5.1 [631821.513] Init DHCP [631821.613] [network_device_init] PHY initialized [631822.522] SD Card connected: [631822.541] [MBNG_FILE_C:16] ERROR: missing '=' after EVENT_LED ... # [631822.715] Init DHCP [631822.718] [MBNG_FILE_C] Event Pool Number of Items: 71 [631822.718] [MBNG_FILE_C] Event Pool Allocation: 3905 of 24576 bytes (15%) [631822.732] [MBNG_FILE_L] DEFAULT.NGL hasn't been changed; reading labels from existing DEFAULT.BIN file. [631822.739] [MBNG_FILE_L] 4 labels found in /DEFAULT.BIN file [631822.749] [MBNG_FILE_S] snapshot #0 not stored in /DEFAULT.NGS yet [631822.777] Values retrieved Operating System: MIOS32 Board: MBHP_CORE_LPC17 Core Family: LPC17xx Chip ID: 0x26113f37 Serial: #70E02121AE022535DBA7CCC47000005F Flash Memory Size: 524288 bytes RAM Size: 65536 bytes MIDIbox NG V1.025 © 2013 T.Klose Uploading cfg/templates/lre8x2x4.ngc... Uploading /lre8x2x4.ngc (21665 bytes) Uploading /lre8x2x4.ngc: 1024 bytes transmitted (4%, 4.4 kb/s) [631825.592] [FILE] Uploading /lre8x2x4.ngc with 21665 bytes Uploading /lre8x2x4.ngc: 2048 bytes transmitted (9%, 4.4 kb/s) Uploading /lre8x2x4.ngc: 3072 bytes transmitted (14%, 3.7 kb/s) Uploading /lre8x2x4.ngc: 4096 bytes transmitted (18%, 3.4 kb/s) Uploading /lre8x2x4.ngc: 5120 bytes transmitted (23%, 3.9 kb/s) Uploading /lre8x2x4.ngc: 6144 bytes transmitted (28%, 4.3 kb/s) Uploading /lre8x2x4.ngc: 7168 bytes transmitted (33%, 4.7 kb/s) Uploading /lre8x2x4.ngc: 8192 bytes transmitted (37%, 5.1 kb/s) Uploading /lre8x2x4.ngc: 9216 bytes transmitted (42%, 5.4 kb/s) Uploading /lre8x2x4.ngc: 10240 bytes transmitted (47%, 5.6 kb/s) Uploading /lre8x2x4.ngc: 11264 bytes transmitted (51%, 5.9 kb/s) [631827.284] [FILE] Upload of 21665 bytes in progress (47%) Uploading /lre8x2x4.ngc: 12288 bytes transmitted (56%, 6.1 kb/s) Uploading /lre8x2x4.ngc: 13312 bytes transmitted (61%, 6.2 kb/s) Uploading /lre8x2x4.ngc: 14336 bytes transmitted (66%, 6.4 kb/s) Uploading /lre8x2x4.ngc: 15360 bytes transmitted (70%, 6.6 kb/s) Uploading /lre8x2x4.ngc: 16384 bytes transmitted (75%, 6.7 kb/s) Uploading /lre8x2x4.ngc: 17408 bytes transmitted (80%, 6.9 kb/s) Uploading /lre8x2x4.ngc: 18432 bytes transmitted (85%, 7.0 kb/s) Uploading /lre8x2x4.ngc: 19456 bytes transmitted (89%, 7.1 kb/s) Uploading /lre8x2x4.ngc: 20480 bytes transmitted (94%, 7.2 kb/s) Uploading /lre8x2x4.ngc: 21504 bytes transmitted (99%, 7.3 kb/s) [631828.316] [FILE] Upload of 21665 bytes in progress (94%) Uploading /lre8x2x4.ngc: 21664 bytes transmitted (99%, 7.1 kb/s) Upload of /lre8x2x4.ngc (21665 bytes) completed in 3.3s (6.5 kb/s) [631828.703] [FILE] Upload of 21665 bytes finished. [631828.703] AUTOLOAD 'lre8x2x4' [631828.703] [MBNG_FILE_C] Event Pool Number of Items: 65 [631828.703] [MBNG_FILE_C] Event Pool Allocation: 3707 of 24576 bytes (15%) But the bad news: under Windows nothing is print out in the command shell! I don't want to release this extension in such an incomplete state, because the (Windows) user experience will be bad if they don't get any notification... It seems to be a known issue, but the workarounds are ugly: http://www.rawmaterialsoftware.com/viewtopic.php?f=2&t=9868 Windows hasn't been designed for the command line - continue to click on the tiles ;-) Best Regards, Thorsten.

I don't really want to waste memory for definable "lock groups"... Would it help to provide a .NGR based "lock_value <id>" and "unlock_value <id>" command, which then has to be executed for each controller which should be locked/unlocked? Then you could set the lock state in different ^section s, which are triggered by a button (or multiple buttons) This gives you much more flexibility. E.g. you would be able to set different colours for the corresponding RGB LEDs. Best Regards, Thorsten.

Crazy things that you are doing there... ;-) I'm surprised that the Virus allows to edit characters with common MIDI events, is this a special mode? It should start at offset 240 in the SysEx payload Best Regards, Thorsten.

It would be very difficult for me to provide fully customizable functions which allow to select preset parameters in a configuration file. In MBSEQ V4 Lite we've this - but here I directly programmed this into the source code. Of course, if you have programming skills, you could do the appr. modifications in the source code by yourself... However, with the "Bookmarks" feature a semi-customisation is available. It doesn't provide exactly the possibilities that you requested, but at least it could be useful for alternative keyboard assignments: See also the end of this page: http://www.ucapps.de/midibox_seq_manual_m.html I could provide a one-octave option. I guess that you don't want to add 10 octave buttons (and LEDs) in this case, so that the octave range would have to be reduced for such an option (e.g. only play notes between C-1 to B-5) Best Regards, Thorsten.

it seems that you found solutions. I like the third layout where the octave buttons are at the right side. it will be displayed when you push the EDIT button (and selected the 303 view) There is no jump-back function, but in practice it isn't really required (and could be confusing) I don't find this really useful - it's better to use the GP buttons under the LCD for this, so that you see what you are doing... More ideas (e.g. also from other interested people)? Best Regards, Thorsten.

Good idea! Best Regards, Thorsten.