TK.

Ooops! Thanks for the hint - it should work again with this version: -> http://www.ucapps.de/mios32/midibox_seq_v4_092_pre6.zip Best Regards, Thorsten.

You've to enable the "sync to track" option for both tracks, and they have to run with the same divider, then it will work! :) Here the new version: -> http://www.ucapps.de/mios32/midibox_seq_v4_092_pre5.zip You are right, I corrected the max. trigger layer lengths of the two additional drum modes that you introduced accordingly in pre5 Best Regards, Thorsten.

Alright, here some updates: -> http://www.ucapps.de/mios32/midibox_seq_v4_092_pre5.zip /edit: corrected to newer link o new drum configurations: 4*16/2*64, 4*16/1*128, 4*16/1*256 o new track mode configuration option: "Note" Allows to specify, if the transposer should take the last or first played note (previously it always played the last note) o individual steps of CC, PitchBender, Program Change and Aftertouch layers can now be disabled so that they won't play. Turn the encoder to the rightmost position (value 128) Also the init value has been changed: for these layers, the steps are now disabled by default. For CCs please change the init value by yourself in the UTIL->OPT page (option #12: Initial CC value) o new behaviour of CLEAR button in recording mode: it clears the selected step only (not the entire pattern). During live recording it will clear the "played" steps so long the button is pressed. o new CC functions which can be configured in MIDI->ExtCtrl.: o Play/Stop: allows to assign the PLAY button to a CC o Record: allows to assign the RECORD button to a CC @EsotericLabs: thanks a lot for testing! G1T2 was playing the last note of the note stack. Since G1T1 played a chord into the transposer but, it was off the root note. In the new version you are able to specify that the first note should be played. Select Track #2, change to the MODE page and press GP button #9 @u-link: - request #1 implemented (I also needed it ;-) - request #2 was already implemented (there is a BUTTON_RECORD and LED_RECORD option in the MBSEQ_HW.V4 file, please update your file according to the templates under hwcfg/*) However, Play/Stop and Record can now also controlled via CC (e.g. to control these functions from a foot switch) - request #3: implemented (yes, it makes sense) - request #4: statement & question: I'm using custom groove patterns to vary the velocity, here I would like to control each 16th In addition, since groove patterns can be applied globally, you want to define them independent of the track divider However, what I could add is an option which allows to synchronize the groove pattern to the track step instead of the global step. Would this satisfy your request? Best Regards, Thorsten.

Ich habe in den letzten Tagen auf eine neue FreeRTOS Version umgestellt, dabei habe ich vergessen ein wichtiges Feature fuer den LPC17 zu aktivieren... Update nochmal das repository, es sollte nun funktionieren. Gruss, Thorsten.

Alright, the problem with the chord display was, that it actually always displayed a label based on the first layer (and not the selected layer). This is fixed now. -> http://www.ucapps.de/mios32/midibox_seq_v4_092_pre3.zip I also added the support for 4 parameter layers in drum tracks. The implementation wasn't so difficult. Would be nice if you could help testing (also the other layer modes to ensure that I haven't corrupted something) Best Regards, Thorsten.

Hat wohl noch gefehlt - hier eine neue version: -> http://www.ucapps.de/mios32/midibox_ng_v1_036_pre2.zip Die digits lassen sich mit %L darstellen Hier ein Konfigurationsbeispiel - die bereits vorhandenen EVENT_LED_MATRIX konfigurationen muessen um fwd_to_lcd, lcd_pos und label erweitert werden: # Following example shows how LC digits could be displayed on a LCD with the events above # notes: # - replace the EVENT_LED_MATRIX configurations above by the new ones with lcd definitions # - change lcd positions by locations which are not used by other text messages yet! # # EVENT_LED_MATRIX id=33 led_matrix_pattern=LcDigit type=CC chn= 1 cc= 64 syxdump_pos=10:0 fwd_to_lcd=1 lcd_pos=1:14:1 label="%L" # EVENT_LED_MATRIX id=34 led_matrix_pattern=LcDigit type=CC chn= 1 cc= 65 syxdump_pos=10:1 fwd_to_lcd=1 lcd_pos=1:13:1 label="%L" # EVENT_LED_MATRIX id=17 led_matrix_pattern=LcDigit type=CC chn= 1 cc= 66 syxdump_pos=10:2 fwd_to_lcd=1 lcd_pos=1:11:1 label=".%L" # EVENT_LED_MATRIX id=18 led_matrix_pattern=LcDigit type=CC chn= 1 cc= 67 syxdump_pos=10:3 fwd_to_lcd=1 lcd_pos=1:10:1 label="%L" # EVENT_LED_MATRIX id=19 led_matrix_pattern=LcDigit type=CC chn= 1 cc= 68 syxdump_pos=10:4 fwd_to_lcd=1 lcd_pos=1:8:1 label=":%L" # EVENT_LED_MATRIX id=20 led_matrix_pattern=LcDigit type=CC chn= 1 cc= 69 syxdump_pos=10:5 fwd_to_lcd=1 lcd_pos=1:7:1 label="%L" # EVENT_LED_MATRIX id=21 led_matrix_pattern=LcDigit type=CC chn= 1 cc= 70 syxdump_pos=10:6 fwd_to_lcd=1 lcd_pos=1:5:1 label=":%L" # EVENT_LED_MATRIX id=22 led_matrix_pattern=LcDigit type=CC chn= 1 cc= 71 syxdump_pos=10:7 fwd_to_lcd=1 lcd_pos=1:4:1 label="%L" # EVENT_LED_MATRIX id=23 led_matrix_pattern=LcDigit type=CC chn= 1 cc= 72 syxdump_pos=10:8 fwd_to_lcd=1 lcd_pos=1:2:1 label=":%L" # EVENT_LED_MATRIX id=24 led_matrix_pattern=LcDigit type=CC chn= 1 cc= 73 syxdump_pos=10:9 fwd_to_lcd=1 lcd_pos=1:1:1 label="%L" # # # status digits # EVENT_LED_MATRIX id=39 led_matrix_pattern=LcDigit type=CC chn= 1 cc= 75 syxdump_pos=11:1 fwd_to_lcd=1 lcd_pos=1:2:2 label="%L" # EVENT_LED_MATRIX id=40 led_matrix_pattern=LcDigit type=CC chn= 1 cc= 74 syxdump_pos=11:0 fwd_to_lcd=1 lcd_pos=1:1:2 label="%L" Mit lcd_pos legst Du das display und die X/Y Koordinaten fest, und mit %L wird ein Logic Digit ausgegeben. Gruss, Thorsten.

Great idea to use such a track to transpose/arpeggiate other tracks :) I'm surprised that a note layer is required to play a chord. I also can't reproduce the chord display issue at my side. Could you please send me an example pattern where you notice this? You can store the pattern into a file from the EVENT->Pattern page Best Regards, Thorsten.

This was related to a stupid mistake that I introduced during the last changes before pushing the release button :-/ Here a new version: -> http://www.ucapps.de/mios32/midibox_seq_v4_092_pre2.zip Meanwhile I also added a more detailed description to the ChangeLog: o new parameter layers for track specific root note and scale Root selection strategy: if Root is assigned to any parameter layer of a track, the layer can either select the global root selection ("Glb") or set the root note for each step explicitely. The global root selection is configured in the FX->Scale page, it's either "Keyb" (for MIDI keyboard entry) or C, C#, ... B The local root selection is C, C#, ... B Notes and Chords will be transposed accordingly if the track is in Normal mode (and not in Transpose or Arpeggiator mode) Similar for Scale: it can override the globally configured scale of the FX->Scale page for each step. Best Regards, Thorsten.

Alright, please try this version: -> http://www.ucapps.de/mios32/midibox_seq_v4_092_pre1.zip There is a new parameter layer for the root note (which also transposes), and I added another parameter layer which allows to change the scale (unfortunately currently only a number will be displayed which corresponds to the numbers in the scale FX page) Best Regards, Thorsten.

I could easily add a parameter layer for a "local" (track specific) root note, would this help? Best Regards, Thorsten.

Update: I migrated to the latest FreeRTOS V9.0.0 Instead of umm_malloc we are using heap_4 now - seems to work fine for my apps, please doublecheck at your side Best Regards, Thorsten.

Ist Dir wirklich gut gelungen! Best Regards, Thorsten.

Has this been solved meanwhile? Best Regards, Thorsten.

Do other readers: MIDIbox Plus is not a MIOS based firmware. This information is only relevant for PIC16F based designs that I published ca. 13 years ago @Anitix: could you please check if the power-up timer is enabled? -> http://microchip.wikidot.com/8bit:pwrt Without this timer it could be that the display initialisation starts too early for your LCD Best Regards, Thorsten.

No, it can't be related to a soldering issue I guess that you did all the required tests. With loopback you mean that you can send text messages in the MIOS Studio terminal and they are sent back? This is a mandatory test, because it ensures that SysEx messages can be sent correctly. If this doesn't work, the issue is related to your MIDI interface Best Regards, Thorsten.

added to wish list for MBSEQV4+ Best Regards, Thorsten.

To the .s file issue: it works at my side with the latest Makefile Under which OS are you trying to build the project? Best Regards, Thorsten.

yes, this is the intended way to setup a default value It's a general problem that each step only stores 7bit data, and program change is 7bit - means: no free value to turn off a step But I've to doublecheck if the 7bit limitation is still valid. Actually MBSEQ V4 has 8bit data per step, so that the 129th value could be used to turn of the step. I added this to the wish list Best Regards, Thorsten.

Well, actually this was on my agenda, because with the introduction of RAM based .NGR scripts the execution of MIDI clock events is fast enough. So, you simply have to tell MBNG what should be done on a MIDI clock event: you could send one or more MIDI events immediately or schedule the event(s) in the integrated sequencer (which was not directly accessible in previous MBNG versions) you could also set/clear LEDs to display the step you could control the note length from an additional encoder you could also do that weird algorithmic stuff or whatever you want :) also transposer, arpeggiator and similar gimmicks should be possible, just requires some clever .NGR programming Examples: 16 note sequencer: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fseq1.ngr 8 note sequencer with control over note and velocity value: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fseq2.ngr 16 CC sequencer: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fseq3.ngr When you look into the .NGC file you will note, that I prepared 4 banks. Which means, that you can switch between 4 different patterns with the SCS Softbuttons: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fseq1.ngc The 5th Soft button can be used to start/stop the sequencer in master mode. If MIDI clock is received, the sequencer automatically switches into slave mode The example setup is prepared for the LRE8x2 with LED Rings - but it should be easy to customize it to any hardware. Also with pots, or buttons (for drum sequencing) Here a pre-release which enables the new features: http://www.ucapps.de/mios32/midibox_ng_v1_036_pre1.zip Best Regards, Thorsten.

Yes, 50V is sufficient. Take this one: http://www.reichelt.de/MKS2-50-330N/3/index.html?&ACTION=3&LA=446&ARTICLE=172678&artnr=MKS2-50+330N&SEARCH=MKS-2+330n Best Regards, Thorsten.

Hallo, ich vermute, dass es aufgrund der langen Schieberegister-Ketten zu den Unstabilitaeten kommt. Urspruenglich wurden nur bis zu 16 Schieberegister hintereinander unterstuetzt (= 4 DINX4 und 4 DOUTX4 Module), sobald die Kette laenger wird, koennen die beschriebenen Probleme auftreten. Abhilfe verschafft die hier beschriebene Line Transmitter/Receiver Schaltung: http://www.ucapps.de/mbhp_line_driver.html Sie sollte spaetestens nach dem 16. Schieberegister eingefuegt werden, bzw. sobald zwischen zwei Schieberegistern ein laengeres Kabel verwendet wird (in ihrem Fall also bereits nach dem 1. DIN) Gruss, Thorsten.

Hi, could be related to a power issue: how do you power the STM32F4DISCOVERY and your MIDI controller in host mode? could also be related to an application issue: which application are you using, resp. if you wrote one by yourself: how is the MIDI data processed? Best Regards, Thorsten.

V4.091 is now available under http://www.ucapps.de/mios32_download.html From the ChangeLog: MIDIboxSEQ V4.091 ~~~~~~~~~~~~~~~~~ o new parameter type "Chord2" provides an alternative set of 32 chords o new parameter type "Aftertouch" allows to send and record channel pressure events o CPU load display has been re-adjusted for LPC17 and STM32F4 o hwcfg/wilba*/MBSEQ_HW.V4: default F1-F4 assignments changed to: F1: Track Select, F2: Live Forwarding, F3: Recording, F4: Save All o MBSEQ_HW.V4: added new button/LED functions: FX, MOVE, SCROLL o MBSEQ_HW.V4: added new LED_MEASURE function which will activate a LED when the first step of the measure is played. o CC Parameter layer label now prints "#<number>" instead of "CC" o Jam page: AStart now starts to record into first step in live recording mode (as intended), it starts on the selected step in step recording mode o Purpose of Record and Live Button & LED change: they switch between record (and live) mode w/o changing to the Jam page o new button/LED combo: JAM_LIVE and JAM_STEP: they switch to the JAM page and select Live resp. Step recording mode o BLM16x16+X keyboard can now record into any track o Transpose page now allows selection based on Scale o New option page item #10 "Initial Gate Trigger Layer" (empty or trigger on each 4th step) o Event configuration page: new drum track configuration 2*64/2*128 o AOUT: added suskey function (AKA fingered portamento: slew rate only enabled if more than 2 keys are played) This function can be enabled in the CV Configuration page o removed obsolete (non-working) pattern based scale control o fixed LED behaviour in Step View page (corrected display if page is deselected) o various minor bugfixes & improvements Best Regards, Thorsten.

@Rowan: unfortunately merging MBSEQ and MBCV isn't possible - too many conflicts, too much work to solve the conflicts, and at the end it would also influence the performance of both apps (running in parallel) @Andrew: I just hacked this into the firmware without testing. Could you please try this version? -> http://www.ucapps.de/mios32/midibox_seq_v4_091_pre9.zip SusKey is always enabled, currently it can only be disabled by editing the MBSEQ_GC.V4 file in the root directory Best Regards, Thorsten.

You could temporary connect a LED via 220 Ohm resistor between 5V and pin #6 as shown in the schematic: http://www.ucapps.de/mbhp/mbhp_iic_midi.pdf If it lights up, you know that the firmware is basically running. Best Regards, Thorsten.