TK.

It seems that your repository contains expired source files, this compile problem for LPC17 has been fixed some time ago. Just update your subversion repository Best Regards, Thorsten.

Hi, you should consider to connect the RGB LEDs to a LED matrix, this is less expensive and also reduces the number of wires. E.g. a 8x16x3 matrix consist of 7 x 74HC595 and allows you to connect 128 RGB LEDs. Then just add another 8x16x3 matrix for the second deck. Do you know the MIDIbox NG application? It supports such features out-of-the-box: http://www.ucapps.de/midibox_ng.html Best Regards, Thorsten.

AFAIK there is no forum posting about this so far. The shift registers are service from MIOS32_SRIO, this code has to be duplicated (and button related functions have to be removed): http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fmios32%2Fcommon%2Fmios32_srio.c Btw.: why do you need the second SRIO chain? Wouldn't it be easier to enhance the first chain by +16 SRs? Best Regards, Thorsten.

Fine! :) For common users the relation between patterns and mixer isn't obvious, it could be very confusing. Especially for those who use only a single mixer map for all patterns. Best Regards, Thorsten.

You got mail. Best Regards, Thorsten.

shouldn't be a problem with pre2 anymore, since patterns are not permanently stored. Please check Best Regards, Thorsten.

I agree that it's better if the pasted patterns are not saved. Also clear is useful. Here a new version: http://www.ucapps.de/mios32/midibox_seq_v4_094_pre2.zip Best Regards, Thorsten.

Nice idea! Please try it: http://www.ucapps.de/mios32/midibox_seq_v4_094_pre1.zip COPY, PASTE, COPY+PASTE now available in PATTERN page Best Regards, Thorsten.

Of course, you are free to service the SR register chain directly without using the SRIO driver (resp. implement a second SRIO driver) Best Regards, Thorsten.

easy: just press COPY+PASTE at the same time, this will duplicate the steps and adapt the length. Best Regards, Thorsten.

V4.093 has been released From the ChangeLog: MIDIboxSEQ V4.093 ~~~~~~~~~~~~~~~~~ o new parameter type "Chord3" provides an alternative set of 108 chords. Thanks to EsotericLabs for providing the chord table! o notes in edit screen are displayed transposed now o drum tracks: random probability layer now working as intended o layers are now initialized for 6 notes polyphony by default (8 layers, 128 steps) o optionally pattern changes don't re-send the PC/bank settings. This option can be configured in the UTILITY->Options menu (item #4/18) Best Regards, Thorsten.

It's very difficult for me to check this (because I haven't used the BLM16x4 since more than 7 years), but I assume that the appr. tracks should be visible when you select a trigger layer within this quarter? Best Regards, Thorsten.

Unfortunately not - the SRIO driver is monolithic, it can only be assigned to a single SPI interface. Best Regards, Thorsten.

Hi, you can switch to J16 with following define in your mios32_config.h file: #define MIOS32_SRIO_SPI 0 Best Regards, Thorsten.

The break contact will be triggered earlier than the make contact, this makes the difference. Especially nice if you want to play organ rakes: Best Regards, Thorsten.

access right issue - try again Best Regards, Thorsten.

Update: I got one of the last 2 prototypes from Andi so that I can test the device before the next batch run. :) Target is to test all functions, and to prepare direct shift register based access, so that the module could be directly connected to a MIOS8 or MIOS32 core w/o MBHP_SID module :) The sound is *very* close to the original. I will provide a A/B comparison soon. Best Regards, Thorsten.

Older releases can be found under: http://www.ucapps.de/mios/backup/ With an old bootloader you wouldn't be able to run upload the application anyhow, so it can't be related to this... Best Regards, Thorsten.

The MBHP_CORE_LPC17 design is pretty much outdated, I would recommend to use a MBHP_CORE_STM32F4 instead. It shouldn't be so difficult to connect a MBHP_DIO_MATRIX module to the pins which belong to J8/J9 even without the line driver, but if you are not an electronic expert, it's safer to use a PCB - both (MBHP_DIO_MATRIX and MBHP_CORE_STM32F4) are available in John's shop: https://modularaddict.com/manufacturer/midibox Best Regards, Thorsten.

Hi, yes, MIDIbox KB is the most simple project for this purpose. Note that it supports two keyboards. For 88 keys just use the first 64 keys as keyboard #1, and the remaining keys as keyboard #2 transposed by 64 semitones. You will need two MBHP_DIO_MATRIX modules Best Regards, Thorsten.

Hi Norbim, thanks a lot for the bugfix! :) It's in the repo now. Best Regards, Thorsten.

And you can overdub the recordings. The initial recording will just define the CC number if it was set to "off" before. You could change the CC number to >127 until it shows "off" But if you mean the values: I just press the "ALL" button and change the value to >127, so that it shows "---" Intuitive and sufficient (easy to remember, no special key combination or hidden menu option, no need to introduce protections, etc) Best Regards, Thorsten.

It isn't required to change the MIOS32_USB_PRODUCT_STR Just change the name with the bootloader as documented here: http://www.ucapps.de/mios32_bootstrap_newbies.html Search for "set name" Once defined, the customized name will be taken instead of the default name defined with MIOS32_USB_PRODUCT_STR It isn't possible to give each port an individual name, the USB MIDI spec doesn't define this as a use case, hence USB MIDI drivers won't support this. In addition, I never saw a commercial device which uses these standard drivers and supports this. However, under MacOS it's possible to change the port names in the MIDI Configuration, and most MIDI applications (incl. MIOS Studio) support this. Maybe Windows provides similar mechanisms? Best Regards, Thorsten.

Yes, this isn't the first time the licenses are discussed... I've to step out now for the next days, because my vacation is over and I've to set priority for more important stuff. Unfortunately instead of spending my limited time to help people, to implement nice new features and/or bugfixes, my attention was too much on this thread. I'm not really happy about this - please understand, that I don't have enough time anymore for this forum to discuss with everybody sufficiently enough. And please don't see this as arrogant behaviour - it's just too difficult to manage under the given conditions. Best Regards, Thorsten.

Added to wish list - that's all I can currently do (but I will work on this definitely before end of this year! ;) Best Regards, Thorsten.