TK.

Hm... it would be interesting if the MBSEQ_HW.V4 file can be accessed after you entered the "reset" command into the terminal (this will reboot the MIDIbox without power-cycling) Best Regards, Thorsten.

To 1) a remote update is already possible with the MIDI router, e.g. take an USB port != USB1 (USB2, 3 or 4) and take one USBx->OUTy, and one INy->USBx connection To 2) added to wishlist, but it's unlikely that I will allow to modify parameters with the sliders, because 99% of the users don't have them, and they will need an alternative solution anyhow. In order to avoid complexity, I would prefer to allow only a single way of configuration. Best Regards, Thorsten.

Hi Andy, long cables between DIO_MATRIX and buttons/LEDs shouldn't cause a big problem, but it's important that the cable between CORE and DIO module is as short as possible (typically 10cm and not more than 20 cm), otherwise random things can happen due to transfer failures to the shift registers. If this isn't already the reason, I would recommend two strategies: 1) SW side: reduce the configuration and check if the problem comes up again. E.g. remove all parts from a matrix row, and/or from a matrix column 2) HW side: disconnect cables from a row or column Best Regards, Thorsten. P.S.: I assume that the 1N4148 diodes have been soldered for all buttons/switches, because without them one switch could influence the other switches of the same row

Thanks for the inspiration; interesting, what can be hidden into an Eurorack case! :) The "ICs" in the yellow package are actually 8x220 Ohm resistor arrays Best Regards, Thorsten.

Are the messages really problematic? I mean: these are warnings and no error messages, hence the .hex file should be generated, right? Best Regards, Thorsten.

First of all please install the latest firmware, because the current release for LPC1769 can cause a stack overflow which could lead to random effects: http://midibox.org/forums/topic/19646-pc0x00038a50-hard-fault/?do=findComment&comment=171163 If this doesn't already solve the problem, I would like to know which messages are print on the terminal after the firmware has been uploaded. Best Regards, Thorsten.

Hi Tom, it looks like jumper J27 (bootloader hold mode) is mounted, resp. Pin 1.27 is connected to ground maybe by fault - see also schematic: http://www.ucapps.de/mbhp/mbhp_core_lpc17.pdf This would explain, why the application can be successfully uploaded, but won't be started. Best Regards, Thorsten.

I've to test this at my side if nobody is using this configuration yet Best Regards, Thorsten.

MBSEQ is currently not able to delay individual MIDI clocks, but since this isn't the first time for this request, I added it to the wishlist It could be, that this feature won't be available for the LPC17 based build, since this firmware is running out-of-memory. Best Regards, Thorsten.

I think that this is intended in slave mode: the sequencer won't stop, just mute the tracks and continue in-sync Best Regards, Thorsten.

Thanks for the detailed report! :) I noticed that aside from FWD_MIDI, also AUTO_START and STEPS_PER_KEY are not stored, it's now on the wish list and should be possible with the next release Best Regards, Thorsten.

The SID Player is only available for MacOS, and can't be migrated. However, the "ASID Application" for the Elektron Sidstation might work at your side, it can be downloaded from the Elektron support page Best Regards, Thorsten.

Concerning the character issue: this is a known migration issue, and we can't fix it. Actually Twin-X asked me if it's ok for me to bring the forum back online without solving this issue - I agreed because I had no better idea. We can edit the subjects and manually correct the characters this way - just need help from people who can give us a template ;) To the other issues: I need your help to find out, how to configure this, resp. how to fix this The IPS Support forum is here, maybe you will find the answers? I will change on demand, but I've no time to search for solutions: -> https://community.invisionpower.com Best Regards, Thorsten.

Hi, I received your PM this Thursday, but usually work through various requests only on Sundays, that's the reason for the delayed reply. Here is a quick&dirty hack which should send CC#16...CC#23 over MIDI channel 1 on pots connected to J5.A0...A7 -> http://www.ucapps.de/mios/midio128_v2_2c__ain_enabled.zip Please note that unused analog inputs have to be clamped to ground, otherwise they will cause random MIDI data. Best Regards, Thorsten.

Unfortunately we can't save the settings due to memory limitations. With MBSEQ V4+ (running on a STM32F4) this should be possible, but it will still take some months until the extended firmware version will be available (and it won't run on a STM32F1 or LPC17 based core...) Best Regards, Thorsten.

Angeblich unterstuetzt der neue Standard USB MIDI Treiber unter Win10 nun Multi-Client und geringe Latenzen. Also aehnlich wie unter MacOS Kann das jemand bestaetigen? Wenn das so ist, sollte man am besten keinen zusaetzlichen Treiber installieren, sondern einfach den nehmen, der nach dem Einstecken des Moduls automatisch ausgewaehlt wird. Gruss, Thorsten.

Since USB is interrupt driven, it's for me another indicator that the issue is caused by a stack overflow. I just added too many features which don't fit into the RAM of LPC17 anymore... In order to check if this assumption is true, please try this version: http://www.ucapps.de/mios32/midibox_seq_v4_089_pre6__undo_disabled.zip I disabled the UNDO function which saves around 1.5k If this version is working stable at your side, I've to think about feature reduction for the LPC17 firmware (because I guess that most LPC17 users would like to get back the UNDO function) Best Regards, Thorsten.

Yes, as explained at the bottom of the "installation" section in the user manual: http://www.ucapps.de/midibox_seq_manual_in.html Best Regards, Thorsten.

Thanks for the hint, the issue should be fixed in this version: http://www.ucapps.de/mios32/midibox_seq_v4_089_pre6.zip Best Regards, Thorsten.

Den Kommentaren nach handelt es sich bereits um PM, und nicht FM // calc 32bit increment (phase_increment * fm_ratio >> 8) Gruss, Thorsten.

Hi, great! :) Currently it's only possible to mute entire tracks via CC. I'm unsure if it makes sense to mute individual notes, such a generic filter capability would be very costly (128 * 16 CCs required) Maybe trigger layer mutes could be controlled via CC (currently only possible from the UI), this would fit with your intention? This is possible: press & hold the SELECT button. Change mute states for tracks or parameter/trigger layers (press&hold MUTE button in addition to see them) Release SELECT button to take over the change. I've to check this (added to the long wish list) However, double-click is no option, too risky during live situations Best Regards, Thorsten.

:-( Could you please check if this also happens with the latest pre-release version? -> http://www.ucapps.de/mios32/midibox_seq_v4_089_pre5.zip Which core module are you using? If it's a MBHP_CORE_LPC17, I fear that it's caused by the stack overflow issue that we had some versions ago, with the result that I've to start to remove features for this core (because of missing RAM space) yes, this should work to recover the core. Best Regards, Thorsten.

Update: the copyright message is originated from 2012 - seems that you missed an important bootloader update! Last update 2012 was v1.010 (at this time w/o version information displayed in MIOS Studio) Current version is V1.018 (2014 release) If previously a version before V1.010 was installed, please follow this process: Best Regards, Thorsten.

Unfortunately not from a user documentation: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Finclude%2Fmios32%2Fmios32_midi.h -2 means: more bytes have been received than expected -4 means: write access (to flash) failed, which is just the result of -2 Which MacOS version are you using? I'm a MacOS user as well, and never got this error code... and I upload code to different core modules very frequently ;-) Best Regards, Thorsten.

But you can't do this in the additional note layers of a track - here you've to disable the note by setting it to the lowest value (which is displayed as "---"), and if you want to play the note again it's better if it starts from C3 I'm wondering, why you've to set the note to the lowest at your side? Actually I would like to avoid too many (confusing) options. I will only add it if there are good reasons, and if multiple users confirm that it makes sense. Best Regards, Thorsten.