TK.

Unfortunately this won't be possible with the way how the software is designed, it would require many changes at many places which can only be done by somebody who would own the same hardware, and has the resp. programming skills. Best Regards, Thorsten.

no, this isn't available yet. I added your request to the wishlist, which is currently very long since so many people requested so different features As a temporary solution, you could try to pass CCs to the AOUT port via the MIDI Router Meanwhile I got the proposal that this button could be a good replacement: http://de.mouser.com/ProductDetail/Omron-Electronics/B3F-5050/?Omron-Electronics/B3F-5050/&qs=dOLq8QE0Pqqk/O9x2OpTQw== But I'm not 100% sure, if the footprint is compatible - and actually I would like to test 1..2 before replacing all buttons. Does anybody have experiences with the Omrom buttons? It works, but due to the changed handling, you've to move the encoder of the selected step (marked with >...<) I can't add additional pages (resp. additional mixer map parameters) Would it be ok, to handle it like a "CC" in the CC assignment map (selected with CC number >= 128)? Best Regards, Thorsten.

no Yes! :) You would have to bridge pin 9 and 10 of the removed 74HC165 to ensure that the PIC gets an inactive logic level (=5V) via R22 pull-up yes yes In addition, please select only 6 faders in the "MBHP_MF_NG configuration tool" (part of MIOS STudio), and push the Send button, so that this configuration will be permanently stored in EEPROM. Best Regards, Thorsten.

:-/ Independent control of the LEDs isn't possible with such a wiring. And even for a meter like display, they would require a special control software. Unfortunately multiplexing (like for LED rings) isn't possible -> sell them on ebay, and search for a better suitable hardware. Best Regards, Thorsten.

Welcome on board! Great that you solved this by yourself (a bad 595 connection was my first assumption) Best Regards, Thorsten.

I'm surprised! The maximum stream size is 128 bytes. Did you get an error message while loading the .NGC file? Or was this just an assumption, but the reason why longer SysEx streams can't be sent (or received at the destination?) is located somewhere else? Best Regards, Thorsten.

Alright! :smile: But I will consider an enhancement in MIOS Studio anyhow, because I'm sure that with the new SysEx forwarding behaviour this will happen very often in future. Some words to Alex' request: Would it help, if layer/drum mutes are stored in the pattern, and restored whenever it's selected? Advantage: the initial mute states won't get lost when you are switching to this pattern Disadvantage: let's say you are playing different patterns during a live session, and then switch back to the first pattern which has some layer mutes set - this might result into unintended mutes. Therefore I'm unsure if this approach is really desired. On the other hand it would solve other usecases as well. E.g. somebody could prepare layers for different CCs - with the mutes he would be able to define, which CCs are actually used, and he could quickly enable them whenever they are needed. There is currently no other way to handle this without a cumbersome configuration procedure. Best Regards, Thorsten.

It looks like a SW based feedback loop, therefore my first guess is, that this could be related to the SysEx router enhancement. Since v4.076 SysEx data will also be forwarded if the router only forwards a selected channel, previously SysEx was only forwarded with "All" channels. To doublecheck that this assumption is true: are you trying to upload via MIDI1 instead of USB1? And does it help if you temporary change the MIDI Router configuration, so that no events will be forwarded to MIDI1 (or USB1)? As a sidenote: for MIOS Studio it should be possible to detect a SW based feedback loop, to ignore this and to enter bootloader mode anyhow. I will consider this in the next release. Best Regards, Thorsten.

@Antichambre: you are now registered as a programmer, more details about SVN write access in the lounge Best Regards, Thorsten.

Hi, yes yes, it's recommended to connect the remaining analog inputs to ground (as usual) No need to bridge something else, the H bridges are acting as outputs... not required as long as you don't touch the pins ;-) Best Regards, Thorsten.

STM32 or LPC17? The Baudrate initialisation code is located in $MIOS32_PATH/mios32/*/mios32_uart.c, MIOS32_UART_BaudrateSet should also work on re-configurations... but I never tried this by myself. You could add some debug messages in order to find out why the re-initialisation is failing. (this would help me, because I've currently 0 time to debug such issues by myself) Best Regards, Thorsten.

Hi Kike, unfortunately the LCD customization requires some assembler programming skills - the code can be found here: src/cs_m_display_2x16.inc Only MIDIbox NG allows to create a custom LCD layout based on easy to edit definitions, which are stored in a .NGC file on SD Card. See also: http://www.ucapps.de/midibox_ng.html Best Regards, Thorsten.

Yes, the polarity switch is reliable for all faders Best Regards, Thorsten.

Tja, spaetestens jetzt wirst Du Dich darueber aergern, dass Du Dich mit einem 8-bitter herumschlagen musst. Ich habe auch lange gebraucht (> 2 Jahrzehnte), bis ich es leid war, die Limitations per Assembler zu umgehen (wenn das ueberhaupt noch moeglich war)... irgendwann ist man es leid, und wohin das fuehrt, sieht man in MIOS32. Wie dem auch sei: ein FIR Filter ist relativ einfach zu implementieren. Man muss ja nur addieren und multiplizieren. Der Knackpunkt sind die Koeffizienten, die jeweils passenden findet man per try&error... siehe auch: http://shulgadim.blogspot.de/2012/01/fir-filter-implementation.html Erfahrungsgemaess findet man sie sehr schnell, wenn man den Algorithmus auf einem PC emuliert, bevor man ihn auf dem Mikrocontroller ablaufen laesst. Gruss, Thorsten.

Ich lasse mich bei diesen Geschichten immer von Matlab inspirieren. Laut diesem Tutorial: http://www.mathworks.de/de/help/dsp/examples/envelope-detection.html ist es ausreichend, die Waveform zu quadrieren, und dann durch einen FIR Filter zu schicken: Gruss, Thorsten.

Hi Ingo, wow! First post, and then already with a concrete project, this is unusual! Welcome on board! :) Best Regards, Thorsten.

I don't really like this idea. The data dump will stall all MIDI OUTs (because there is only a single mutex for OUTs), and quite a lot of data would have to be dumped: for all 16 tracks. ca. 2000 bytes - this would stall a common OUT port (not USB) ca. 2 seconds. Does such a "programmer" really make sense for MBSEQ? I fear that I would have to do a lot of enhancements in the firmware to support this properly under all conditions, therefore I'm sceptic that it's worth to start with this. I would only do this if multiple people are interested (and I'm not interested by myself...) Best Regards, Thorsten.

Some new nice features for the cold & rainy weekend (at least in germany ;-)) MIDIboxSEQ V4.077 ~~~~~~~~~~~~~~~~~ o it's now possible to send parameter changes, done from the user interface, to a specified MIDI output port. This allows to record such changes with a DAW. The output port has to be selected in the MIDI->Ext.Ctrl page, where also the input port and channel is specified. o a very useful "quick save" function has been added which significantly improves the song phrases handling. The new function will store the current mixer and pattern setup into predefined bank positions: - Phrase A will use Mixer Map #1 and Patterns 1:A1 2:A1 3:A1 4:A1 - Phrase B will use Mixer Map #2 and Patterns 1:A2 2:A2 3:A2 4:A2 - Phrase C will use Mixer Map #3 and Patterns 1:A3 2:A3 3:A3 4:A3 - ... - Phrase P will use Mixer Map #16 and Patterns 1:B8 2:B8 3:B8 4:B8 After the store operation, following references will be copied into the phrase slot of the song: - 1st phrase step: the current mutes - 2nd phrase step: selects the new mixer map - 3rd phrase step: selects the new pattern set - 4th phrase step: jumps to the 3rd phrase step (could be useful in song mode) How to use this function: Start a new session, edit some tracks, start jamming. Whenever you've found sequences which play well together, change to the SONG page, press&hold the SELECT button, then select "Save&Take over Patterns" with GP button 16. Thereafter release the SELECT button, and select the target phrase slot with one of the GP buttons -> this will store the current mutes/mixer map/patterns into the predefined bank positions and insert references into the phrase slot. Now you can continue jamming, change tracks, change mixer values, change mutes. Whenever you found a new nice working sequence, go to the SONG page and store it into another phrase slot (or overwrite an existing slot). The stored phrases can be restored as usual with the GP buttons in the song page. o it's now possible to specify the initial CC value (for the CLEAR and INIT function) in the UTILITY->Options page o LFO: CC layer modulation is working properly again o Mixer Map not switched on pattern changes anymore (this is actually only part of the "Remix" feature). To get the Remix function properly working again, please open your MBSEQ_GC.V4 file with the MIOS Filebrowser, search for "PatternMixerMapCoupling" and set it to 1. If this parameter doesn't exist yet, please create it: PatternMixerMapCoupling 1 Best Regards, Thorsten.

fixed in v4.077 Best Regards, Thorsten.

now available in V4.077 Best Regards, Thorsten.

Why did I know that somebody would misuse Note Events that way... ;-) Ok, will be switchable in the next release. Best Regards, Thorsten.

I've to revert my statement: while working on a new function, I noticed the same unexpected behaviour. It turned out, that this is due to a function of the "Remix" feature, which isn't properly gated when Remix isn't used. It will be fixed with the next version. Best Regards, Thorsten.

Maybe it was changed from an external CC or program change event, or from a song or phrase? Just disable the appr. option. Best Regards, Thorsten.

currently too many people are giving me requests... Is this enhancement really so important? It seems that you are the only guy who is interested on this, or are there others (maybe even with programming skills) who could help out? Best Regards, Thorsten.

No this isn't normal, and it sounds strange. I don't see a mechanism behind this behaviour... Best Regards, Thorsten.