TK.

Such features are currently not provided. The big question: is the usage of variables really the right approach? What if you want to control both synths from a single control surface? Or would it be better to provide new .NGR commands which allow to change the channel and port assignment for each event? Best Regards, Thorsten,

Hi Andy, some notes: the file structure can be determined by reading the code in MBNG_FILE_S_Write http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fsrc%2Fmbng_file_s.c The file header stores the file positions of the 128 possible snapshots And the snapshot sections store the event id the event value the "secondary" event value for each event The snapshot feature can only work correctly if: no new events are added anymore event ids are not changed So - whenever you are adding events or changing the purpose of event ids, the .NGS file has to be removed, and it has to be created again (unfortunately... there is no automatic "migration" available yet) If this isn't the problem, a debugging hint: enter "set debug on" in MIOS terminal and check the messages while a snapshot is loaded Best Regards, Thorsten.

Just have a look into various .c files under mios32/STM32F4/ which configure IO pins. And then compare with the files under mios32/STM32F1/ Best Regards, Thorsten.

The load command is supported now! :) -> http://www.ucapps.de/mios32/midibox_ng_v1_036_pre3.zip Problem understood - but MBNG currently doesn't allow to remove a LED from the pattern. There is currently no solution/workaround for this use case The event will take over the value, regardless if it's defined in the selected bank or not (otherwise this feature wouldn't make much sense... ;-) Are you using the set_lock command in your .NGR script? This command would allow to lock the value so that it can't be overwritten from an incoming MIDI message. Best Regards, Thorsten.

No -- MBHP_MF_NG is only intended as a "slave device", either for a DAW, or for MIDIbox NG (which allows you to define banks, allows to assign any kind of MIDI event - including SysEx, allows to store/restore snapshots, etc) Best Regards, Thorsten.

Hi, just to make it clear: not so much will change, I will continue the support and development like in the last 2..3 years, means: with ca. 20 days per year. But I will focus this instead of introducing new MIDIbox projects or forking existing HW/SW projects by myself. The license might also be more relaxed in future, but this will be announced in a separate thread in some days (please no discussion in this thread, it's too early) I continued the discussion about a new MBSEQ frontpanel with Andy today, be prepared for a great new solution - no, there won't be an integrated BLM4x16, but the frontpanel will look fresh and useful :) Best Regards, Thorsten.

Similar problem. But while thinking about possible solutions I got an idea, will come back to this tomorrow. Best Regards, Thorsten.

Hi Chris, from the source code: DEBUG_MSG("[MBNG_FILE_R:%d] ERROR: the LOAD command is not supported anymore!", line); // let's see if somebody really needs this... It will be difficult to provide a solution because of conceptial changes, how the NGR script is parsed and executed. There is no replacement So - it can take some time until a solution will be available again Best Regards, Thorsten.

Works at my side, tested with: EVENT_KB id=1 type=NoteOn chn=1 key=any use_key_number=1 range=0:127 lcd_pos=1:1:1 label="Note %n" kb_transpose=0 ports=00000100000000000000 any error message during the upload of the .NGC file? shows that all src_chn and dst_chn are disabled: no routing takes place Is this relevant for the test? Best Regards, Thorsten.

Before providing this option on a comfortable way (eg. via bootloader for all apps), it would be nice if you could configure and rebuilt the applications by yourself. The configuration has to be done in mios32_config.h, e.g. add following #define statements to set all MIDI interfaces to 312.5k baud: #define MIOS32_UART0_BAUDRATE 312500 #define MIOS32_UART1_BAUDRATE 312500 #define MIOS32_UART2_BAUDRATE 312500 #define MIOS32_UART3_BAUDRATE 312500 And if you have some time, it would be interesting to know at which baudrate MIDI transfers become instable. Up to 10 MBit are supported; this won't work through an optocoupler anymore, but should work with a direct eletrical connection. With higher speeds the RX buffer has to be increased, otherwise we run into potential data loss issues. By default, 64 bytes are allocated for each MIDI IN, which can bridge ca. 20 mS at normal baudrate, and ca. 2 mS at 10x faster baudrate (as proposed above) - should still be enough for a common MIOS application. But for the case that you notice data loss, try higher values. Max. supported size is 255 bytes (and not 256 as somebody could assume) #define MIOS32_UART_RX_BUFFER_SIZE 255 You've to try out if the higher MIDI rate improves the overall performance, and you've to find the sweet spot. With higher speeds also the performance of your computer, operating system and DAW become relevant. I'm very interested on reports before providing this as a general configuration option for "common users". Best Regards, Thorsten.

We continue here:

Hi Chris, there is no alternative solution for the physical connection, but if speed does matter: I could easily provide an option to increase the baudrate. E.g. 10 times faster, which would mean that MIDI events are sent within 100 uS instead of 1 mS Best Regards, Thorsten.

No changes are required for the hardware, but there are software optimizations which might require a better hardware setup, such as buffer ICs for the LCD control signals which are shared between multiple displays. Major optimizations in universal/app_lcd.c: APP_LCD_ExtPort_SerDataShift: add more "stretch" operations to slow down the serial clock APP_LCD_ExtPort_UpdateSRs: strobes J28.WS, you could duplicate APP_LCD_ExtPort_PinSet(2, 0) to stretch the pulse APP_LCD_Data: uses APP_LCD_PollUnbusy(2500), was APP_LCD_PollUnbusy(10000) before - maybe a timeout happens with this low cycle number? If software modifications are not successful, please give more details about your hardware setup. This could bring up ideas for improvements. Best Regards, Thorsten.

Hi, I think that I found the problem, could you please try this version? -> http://www.ucapps.de/mios32/midibox_seq_v4_092_pre9.zip Best Regards, Thorsten.

It's implemented now, please try it out - works fine at my side! :) -> http://www.ucapps.de/mios32/midibox_seq_v4_092_pre9.zip o new track mode configuration option: "STrg" (Step Trigger) In this mode, the step progression will be controlled from the transposer bus, hence it can either be triggered from a loopback track or from an external MIDI device (MIDI keyboard, sequencer, etc.) Note that each track can be assigned to a dedicated transpose bus (4 busses are available), this allows to control 4 independent step progressions for all 16 tracks. Best Regards, Thorsten.

Hi, I'm glad that you like the device! :) It's possible to configure the MIDI notes which are sent by the drum instruments: enter the MENU->Event page, select the drum instrument with encoder #11, and change the note with encoder #12. E.g. the first instrument (BD) will output C-1 by default, which is in the 4th octave. Lower octaves are C-0, c-1 and c-2, whereas c-2 can't be played because it's note number 0 (interpreted as "no note" by MBSEQ) Best Regards, Thorsten.

The same way how the MB808 UI is working. Please believe me, the encoder usage for track selection wasn't a good idea, I wouldn't do this again... No, the BLM buttons have to switch between BLM sections, and the purpose of a section depends on the BLM mode. If BLM displays the gates of a track, the BLM buttons would switch between track groups. If BLM displays a drum grid, the BLM buttons would switch between trigger layer (resp. drum instrument) sections etc... You could use the jogwheel for this purpose. The function of the datawheel is already configurable, press&hold EDIT, push GP7 to switch between the functions. Additional functions could be assigned to the jogwheel in future. You are right, that this topic needs more planning. Some functions that I "brainstormed" yesterday might be redundant, such as the mute button that you pointed out. Trigger steps are selectable in BLM drum grid mode - again a conflict with your "TPM", an additional handling could lead to too much confusion. I would prefer the following approach: - show different layout options (how many buttons could be added to the jogwheel section) - then we've to start to write a specification for button assignments and usage, this could be done in the Wiki The only way to get a "big picture" and to work out the details to find the best layout. Best Regards, Thorsten.

This works at my side, could you please check with the latest version? http://www.ucapps.de/mios32/midibox_ng_v1_036_pre2.zip Best Regards, Thorsten.

Commando was the very first tune that I played during implementation of the ASID mode as some kind of reference :) AFAIK nobody worked on a "SID sound extractor" yet, this has to be done at the host side (-> computer software) Best Regards, Thorsten.

Yes, this is the rely message. Does "ngr send... OUT1" also output the event at MIDI OUT1? Best Regards, Thorsten.

No, encoder are worse than buttons. Buttons can be operated almost "blindly", encoders require visual focus to the display and could sometimes select an unintended track if not operated careful enough. I noticed this on the MB808 frontpanel - no fun! I would prefer to select tracks, mutes, parameter and trigger layers with the 4th row By providing another button to select the bookmark (BM) function the user could store and restore any kind of other function (see documentation, bookmarks are very powerful, since they not only allow to switch to pages, but also to select tracks, mutes, etc...) Too waggly usage, not useful in live situations! For me such a big jogwheel in the middle doesn't look nice. Better to place it at the right lower corner, and some buttons below. Probably you've to provide an alternative frontpanel for lefthanded users Buttons should be labeled... by giving generic labels 1/A, 2/B, 3/C, ... users will quickly learn the position and sooner or later operate without focusing the labels anymore... Best Regards, Thorsten.

You are right, this is a documentation error: we are counting from left (USB1 is the leftmost digit) Meanwhile corrected at my website To the actual issue: are you sure that the MIDI output is working at all? You could test it with following terminal command: ngr send CC OUT1 1 1 127 This should send CC#1 with value 127 over channel 1 Doublecheck with: ngr send CC USB1 1 1 127 to ensure that the command itself is working... Best Regards, Thorsten.

Hi Chris, I confirm that this can be confusing: encoders define a default matrix pattern, other events won't, hence no pattern is displayed. If you add "led_matrix_pattern=1" to EVENT_AINSER it will work With the next version all events will get this default assignment Best Regards, Thorsten.

I've to spend some thoughts about this. The request makes sense, but to ensure compatibility a new parameter layer type for this kind of Chord handling has to be introduced. This means that instead of only 32 chords in Chord1, and 32 additional chords in Chord2 mode, we would have up to 128 chords available - ideas how to fill the space? ;-) Added to wish list - makes sense, but will need some time to implement this I will check this with high priority Still on the wish list, but lower priority compared to other (especially easy to implement) requests Could be implemented, but I have to experiment with this hardware before I can give a final confirmation Best Regards, Thorsten.