TK.

Yes, it's the same and works per step Best Regards, Thorsten.

It's implemented in this version: http://www.ucapps.de/mios32/midibox_seq_v4_091_pre1.zip Have fun! :) Best Regards, Thorsten.

Could you please provide this information in C format (like the table in your first posting)? It would help me Best Regards, Thorsten.

The intention of the duplicates was to get Minor chords in the same order like major codes, so that it's easier (faster) to remember & access the chord. In addition we've the problem, that any change in the table will lead to compatibility issues with existing patterns. But there might be a good compromise: additional chord tables could be defined, selectable as "Chord1", "Chord2", "Chord3", ... parameter layer currently there are only 4 notes per table item, but I could enhance it to 6 or 8 notes if required chord tables won't be editable in RAM, but I can integrate them directly in the firmware so that they are available for all users So - how would "your" chord table look like exactly? I need 32 entries Best Regards, Thorsten.

In comparison to Bitwig we've a different situation: while Bitwig is developed by a professional company with focus to satisfy as many users as possible (to earn as much money as possible ;-), MBSEQ is only a sparetime project, mainly developed by myself. Of course, MBSEQ is open source, and there is something like a API which could be enhanced or customized by users, but it requires some selfeducation about MIOS32 and the firmware architecture + C programming skills. E.g. somebody could adapt the "BLM_SCALAR_MASTER" driver, which transfers LED states and converts button actions, to another controller: http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fmodules%2Fblm_scalar_master%2F Or somebody could customize the next upper layer called "SEQ_BLM" which allows the external controller to access sequencer functions: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fsequencers%2Fmidibox_seq_v4%2Fcore%2Fseq_blm.c Concerning direct USB connection to the launchpad: unfortunately there are three reasons why this doesn't work with the launchpad: Best Regards, Thorsten.

Hi, unfortunately the number of chords is limited to 32 Which chords should be removed from the list? Best Regards, Thorsten.

Yes, this command should do the trick. It seems that there are variables which are not reset, this isn't intended - on the other hand I've currently no idea what I'm missing here. Would it be possible to create a minimal .NGC file which I could use to reproduce the issue at my side? Best Regards, Thorsten.

In the past J8/9 RC1/RC2 was a common line at the core (MBHP_CORE_PIC, MBHP_CORE_STM32), but always routed as separate lines at DIN/DOUT PCBs. With MBHP_CORE_LPC17 and MBHP_CORE_STM32F4 I introduced separate RC1/RC2 lines at J8/9 core side for future enhancements. This feature isn't used by MIOS32 yet (it just sets both pins at once), but it could be used in future for whatever reason. Best Regards, Thorsten.

Hi, while pressing one of the push encoders, you will get a message in the MIOS Terminal about a button function which hasn't been configured. Typically users assign it to BUTTON_FAST2 in their MBSEQ_HW.V4 file Best Regards, Thorsten.

Currently the step view always prints 16 steps, your request is to display less than 16 steps, and this configuration should be done independently for each track and stored in the pattern. Is this correctly captured? Best Regards, Thorsten.

The MIDIbox SID manual has a "Installation" chapter which describes how the slave cores have to be configured. -> http://www.ucapps.de/midibox_sid_manual_in.html See "Initial Installation of Slave Cores" It's possible to change the Device ID either with a PIC programmer while flashing the bootloader, or via MIDI by using the change_id application. Best Regards, Thorsten.

Hi Matthias, I just tested the following at my end: uploaded usb_midi_2x2_v1_010 application to a STM32F4 core no error message noticed disconnected USB cable to my computer, connected USB host adapter STM32F4 powered via J2 (but I also tested power supply via STLink USB socket) connected M-Audio Oxygen49 keyboard reseted the core (pushing black button) to ensure that the keyboard will be found -> MIDI data will be sent via MIDI OUT1. The green status LED on the STM32F4DISCOVERY board will flash whenever the keyboard sends data Which error message did you get exactly? Best Regards, Thorsten.

Hi, the NGC command "RESET_HW" should reset the state of all elements, are you using it in your NGC file? Best Regards, Thorsten.

Am einfachsten waere es wohl, wenn Du eine bereits vorhandene Funktion, die Du nicht benoetigst, kannibalisierst. Bspw. den "BUTTON_MIXER". Die Pin-Zuweisung wuerdest Du in Deinem MBSEQ_HW.V4 File eintragen (suche dort nach BUTTON_MIXER) Diese wird dann die SEQ_UI_Button_Mixer() Funktion in seq_ui.c aufrufen... ab dort kannst Du dann weitermachen ;-) Alternativ eine neue Button-Funktion einbauen, doch das waere umstaendlicher - Du koenntest bspw. nach einem geeigneten Stichwort greppen, so weisst Du, welche Files zu aendern sind. Hier ein Beispiel: MacMini2:midibox_seq_v4 TK$ grep -i track_transpose core/* core/seq_file_hw.c: } else if( strcasecmp(parameter, "TRANSPOSE") == 0 || strcasecmp(parameter, "TRACK_TRANSPOSE") == 0 ) { core/seq_file_hw.c: seq_hwcfg_button.track_transpose = din_value; core/seq_file_hw.c: } else if( strcasecmp(parameter, "TRANSPOSE") == 0 || strcasecmp(parameter, "TRACK_TRANSPOSE") == 0 ) { core/seq_file_hw.c: seq_hwcfg_led.track_transpose = dout_value; core/seq_hwcfg.c: .track_transpose = ((( 0 -1)<<3)+ 0), core/seq_hwcfg.c: .track_transpose = ((( 0 -1)<<3)+ 0), core/seq_hwcfg.c: .track_transpose = ((( 0 -1)<<3)+ 0), core/seq_hwcfg.h: u8 track_transpose; core/seq_hwcfg.h: u8 track_transpose; core/seq_ui.c: if( pin == seq_hwcfg_button.track_transpose ) core/seq_ui.c: SEQ_LED_PinSet(seq_hwcfg_led.track_transpose, ui_page == SEQ_UI_PAGE_TRKTRAN); In SEQ_UI_Button_FootSwitch siehst Du, wie man einen Doppelklick realisiert. Best Regards, Thorsten.

It does matter! It's important that DINs and DOUTs are chained separately. At the "output port" (J2) the SC line of the longest chain (in your case: DINX6) should be available, RCs are separate anyhow. Best Regards, Thorsten.

To the reed relays: I don't know a source in USA - e.g. Mouser and Dikikey have relays for 3.3V (resp. 3V), but they are pretty expensive (ca. 5 USD), there might be better options, e.g. via ebay Important is the coil voltage - relays for 5V, 12V, 24V or higher won't work, search for 3.3V or 3V Best Regards, Thorsten.

Ich habe eine Vermutung: J10B wird ja beim STM32F4 core fuer die optionalen DIN Clock Outputs verwendet, die stehen nun natuerlich im Konflikt mit den LCD Pins (die ja urspruenglich nicht in der Firmware vorgesehen waren). Ich habe nun seq_cv, seq_hwcfg und seq_file_hw so geaendert, dass die Pins nicht initialisiert werden sollten, wenn im MBSEQ_HW.V4 File "J5_ENABLED" auf 0 gesetzt wurde. Probiere es mal aus: hole Dir die aktuellen Sourcen aus dem Repository, aendere den Wert fuer J5_ENABLED in Deinem MBSEQ_HW.V4 file auf der SD Karte, und tippe dann "reset" im MIOS Terminal. Danach sollten die LCDs eigentlich funktionieren. Falls nicht, muesste man ueberpruefen, ob die Pins noch irgendwo anders gesetzt, und nicht ueber die neue Variable "seq_hwcfg_j5_enabled" gegated werden. Gruss, Thorsten.

You mean this one? ;-) Best Regards, Thorsten.

Blue + Green = Cyan Why do you expect a software problem here? Best Regards, Thorsten.

Ok, so it's very likely a soldering issue around the column select lines for the LEDs. Latigid On can help you to debug this. Alternatively just visually search for soldering errors like you did before for some buttons: Best Regards, Thorsten.

Die Breakpoints werden bei dem optimierten Code nicht immer zuverlaessig funktionieren. Dahinter steht ja: // check if if display already has been disabled if( !(display_available & (1ULL << mios32_lcd_device)) ) return -1; welchen Wert hat display_available? Ich wuerde 15 (hexadezimal 0xf) erwarten. Evtl. macht es Sinn, den Breakpoint in SEQ_LCD_Update() zu setzen, bspw. an der Stelle wo MIOS32_LCD_DeviceSet aufgerufen wird - und ab da mal durchsteppen. Gruss, Thorsten.

The Fader issue is understood now: 14bit values were sent instead of 7bit, this confused the MIDI protocol. So, please update your repository and upload the new blm_scalar application. The LED issue needs a comparison with the PIC based MINI core. Best Regards, Thorsten.

Neither the demonstrated LED behaviour, nor the received MIDI messages make sense, and I'm surprised that anything is working at your side... How exactly did you connect the cores via MIDI? E.g. are you using optocouplers? And are you able to doublecheck the behaviour with a PIC based mini core, just to get more information about the root cause? Best Regards, Thorsten.

Die Anzahl der LCDs setzt man im Bootloader, das muesstest Du noch nachholen falls noch nicht geschehen. Siehe auch: http://www.ucapps.de/midibox_ng_manual_lcd.html In der Bootloader Update Application folgende Kommandos ausfuehren: set lcd_type CLCD set lcd_num_x 4 set lcd_num_y 1 set lcd_width 20 set lcd_height 2 store Gruss, Thorsten.