TK.

I'm aware of this issue, but unfortunately the problem has to be solved in Ableton. Best Regards, Thorsten.

Found & fixed the problem - it was related to the midichannel handling. Could you please try the new version in the repository? Best Regards, Thorsten.

Hallo Lutz, der Fehler passiert wegen des reduzierten PIC18F452 Speichers - leider wird aufgrund des Abbruchs das interne EEPROM nicht mehr beschrieben, und deshalb ist der Patch leer. Der Fehler sollte mit dieser Release nicht mehr gemeldet werden: http://www.ucapps.de/mios/midibox_fm_v1_4i.zip Gruss, Thorsten.

Yes, you can change the drum notes in the EVENT page (assumed that the track has been configured for drum mode). The drum instrument is selected with GP#11, and the note with GP#12 Best Regards, Thorsten.

Well, it has been requested that END shouldn't stop the sequencer anymore, and nobody complaint. If you want to get back the old behavior, you've to rebuild the firmware with following change in seq_song.c: search for following lines: case SEQ_SONG_ACTION_End: #if 0 if( song_active ) // not in phrase mode SEQ_BPM_Stop(); #else song_finished = 1; // deactivate song incrementer #endif break; and replace "#if 0" by "#if 1" Best Regards, Thorsten.

Hi, many files have to be changed to support another STM32F4 derivative, especially when it's smaller (memory & package wise) than a STM32F407! Even for me this would take a couple of hours (therefore I can't give you simple instructions for the required changes). Most difficult topic is to decide the IO pin configuration for the reduced 64pin package. Many peripherals won't be available. However, since you already own a STM32F407, it's probably better to skip this idea anyhow. Best Regards, Thorsten.

Great! :thumbsup: Best Regards, Thorsten.

Hi Florian, yes, I could add this to the firmware. I'm unsure about the best access method for this function - which one would you prefer: a) using a key combination, e.g. "COPY+CLEAR" (or similar) b) a dedicated button function, which can be configured in the MBSEQ_HW.V4L file on SD Card. Then you could sacrifice a typically unused button (e.g. UNDO?) and assign the new CLEAR_PB_AND_CC function to this button instead. Best Regards, Thorsten.

Hi Lisa, They seem to have little effect on the sound, other than making it quieter. They also seem to effect the sound all the time, even when "ext in" isn't switched on. yes, the pots will affect the sound regardless of the "ext in" switch. Therefore turn the pot full left if you don't want to use the feedback option. You should hear an effect with "ext in" on, cutoff low, resonance high, pot at least in middle position. Best Regards, Thorsten.

I can confirm that ULN2803 helps to get consistent brightness. Proven in the LRE8x2x4 project: For best brightness results, consider to use 8x16 matrices (each matrix outputs 8 meters, each with up to 16 LEDs), and not a 16x16 matrix, because than more meters share the same row SRs, than less time per meter to display the pattern! Best Regards, Thorsten.

The SID volume shouldn't be modified if the V2A option is enabled in the ensemble menu. From the user manual: V2A (Volume to Analog): Volumes are forwarded to external CV outputs as well (assignments have to be done in the setup_*.asm file). Note that the effective volume value behind the modulation path is taken - accordingly you are able to realize an external VCA to overcome the ADSR bug. Best Regards, Thorsten.

The MIDI router is not enabled by default, therefore this won't work without further configuration. And to confuse you even more: the MF module has a special MIDI router, which is configured with the "MF" command, and ensures that "direct" communication between MF and core module won't be forwarded. Did you already found the configuration examples? E.g. -> http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fmf_cc.ngc The MF command specifies an midi_in_port, midi_out_port and config_port Did you already consider this? If yes: which configuration are you using exactly? Best Regards, Thorsten.

Yes, you are right, the connections are wrongly named at the Discovery side, they are correct at the J10A side. I can fix the schematic in ca. 2 weeks... The PCB has the correct connections. Best Regards, Thorsten.

You will find following option in the OSC menu which has to be enabled for all three oscillators: GSA (Gate Stays Active): once activated, the VCA envelope won't be released anymore, resulting into a permanent sound. This allows you to control the sound volume completely with the internal, or an external filter, or with an external VCA. It's an option which allows you to overcome the infamous ADSR bug of the SID. Best Regards, Thorsten.

Hi, I've no idea why there should be a problem with the SD card under these circumstances. It isn't required to turn off the core when you insert or exchange the SD Card. What happens if you insert/remove it multiple times while the application is running. Do you get additional error messages in the MIOS Terminal? And what is the output of the "sdcard" command when you enter it into the terminal? Best Regards, Thorsten.

yes, but this shouldn't make a difference for the gate LEDs - please focus to debug this first (yes, maybe there is a problem with J19 of the core module) Best Regards, Thorsten.

Probably the missing pull-up resistor was the reason, because it can stall the CAN handler due to random events, so that only the watchdog will bring back the PIC into a controlled state by triggering a reset. That's also documented in the FAQ, see: http://www.ucapps.de/midibox_sid_manual_ki.html Best Regards, Thorsten.

I would propose to assign the buttons to Bookmarks, this gives you full flexibility (see also http://www.ucapps.de/midibox_seq_manual_m.html) Just disable the current F1..F4 assignments in your MBSEQ_HW.V4 file (can be edited with the Filebrowser in MIOS Studio). E.g. if you are using Wilba's Frontpanel with button matrix change: # Following button functions are usually assigned to Fx # buttons, or to dedicated (labeled) buttons # In Wilba's frontpanel layout: # F1 is located at SR M3 Pin 3 # F2 is located at SR M2 Pin 2 # F3 is located at SR M2 Pin 3 # F4 is located at SR M1 Pin 2 # and there are dedicated buttons for Copy/Paste/Clear/Utility/StepView # DISABLE DEFAULT ASSIGNMENTS: # SR Pin BUTTON_BOOKMARK 0 0 BUTTON_PAR_LAYER_SEL 0 0 BUTTON_TRG_LAYER_SEL 0 0 BUTTON_TRACK_SEL 0 0 And assign the SR/pin numbers to the bookmark function instead: # alternative (individual) bookmark buttons # no LEDs available! # SR Pin BUTTON_DIRECT_BOOKMARK1 M3 3 BUTTON_DIRECT_BOOKMARK2 M2 2 BUTTON_DIRECT_BOOKMARK3 M2 3 BUTTON_DIRECT_BOOKMARK4 M1 2 Use sessions! Best Regards, Thorsten.

:thumbsup:

Is it a 74HC595 or 74HCT595? A 74HCT595 wouldn't work properly. Best Regards, Thorsten.

This could be a watchdog reset caused by corrupted app upload. Do you still get error messages when you are trying to upload the application? (the upload window will notify about the number of errors) Best Regards, Thorsten.

I guess that you are mainly searching for some „blink“. Well, I consider to display animated output waveforms of the controlled parameters in future! :smile: E.g. LEDrings should be animated based on the LFO and ENV depth parameter assigned to the corresponding encoder. This was a bug (now fixed in the repository) Actually the LOAD page should search for .CV2 files, and not .MIO files Best Regards, Thorsten.

No, this would require too many changes. I don't want to overcomplicate this project. Best Regards, Thorsten.

It is implemented: J10B is used instead of J28 Pinning: J10B.D8: serial data (was J28.SDA on a MBHP_CORE_LPC17 module) J10B.D9: serial clock (was J28.SC on a MBHP_CORE_LPC17 module) J10B.D10: SR strobe (was J28.WS on a MBHP_CORE_LPC17 module) Note that these assignments are not pin-compatible to a DOUT module anymore! Best Regards, Thorsten.