TK.

No, the setting is stored in MBSEQ_GC.V4 (global configuration file), which is located in the root directory. Could you please check if this file exists? And when you open this file: which values are assigned to the AOUT parameters? Best Regards, Thorsten.

Hi, yes, "waveform off" will do the trick. The background sound could be related to the leakage issue of the SID chip. The envelope amplifiers don't completely close if the envelopes reach 0, it's related to an analog design flaw. Especially 6581 is affected, it has been partly (but not completely) solved for 8580 (and 6582) Best Regards, Thorsten.

V3.4h is released now: http://www.ucapps.de/midibox_seq_v3_changelog.html http://www.ucapps.de/mios_download.html Take the external mixer dump capability as a "sorry" for the trouble! :flowers: Best Regards, Thorsten.

First of all (I guess you know this, but just to highlight for others): I won't have the time to add new features, because it's too long ago where I worked on this firmware, the danger is too high that changes will introduce new errors which I won't notice by myself since I prefer to use MBSEQ V4 MBSEQ V3 is in maintenance mode, which means that I can only add simple enhancements and bugfixes. A change would be too complicated. In MBSEQ V4 this has been solved with the "Pattern Remix" feature which combines patterns with mixer maps, and therefore also switches mixer maps on synch with pattern changes. I could add CC control without much effort and risk, it will be part of the upcoming release... You need a V4, and you will like the Remix feature! :) Best Regards, Thorsten.

Got it, it's a bug in the MBSEQ V3 firmware! :) Only the mixer map is affected, the port number isn't masked out when the MIDI event is created. I will test the change and release a new version tomorrow. Best Regards, Thorsten.

permission granted. Best Regards, Thorsten.

Why did I already know that you haven't mentioned certain details... :rolleyes: For further troubleshooting you could compare the IIC modules by: - swapping the IIC IDs between the IIC modules (just change the jumper settings) and power-cycle the core -> are now IIC1 and IIC2 failing? - swapping the ICs -> observations? Best Regards, Thorsten.

Nothing else could be wrong. I've also no idea why "F3 F3" should be sent on mixer map changes... And I'm sure that the firmware is working correctly, as I tested the mixer map again just 1 hour ago... Best Regards, Thorsten.

Yes, the MIDI event should be sent immediately. Are you using the latest firmware version, or an older one? Did you modify the firmware? Best Regards, Thorsten.

I just remember that MBSEQV4L has been explicitly configured for 1 USB port. I did this so that Win7 users don't have to troubleshoot the USB connection... (see bottom of the MIOS Studio page for details) You can change the number of ports in the apps/sequencers/midibox_seq_v4_lite/mios32/mios32_config.h file Change: #define MIOS32_USB_MIDI_NUM_PORTS 1 to: #define MIOS32_USB_MIDI_NUM_PORTS 4 Korg driver: are you using WinXP or Win7? Best Regards, Thorsten.

Hi Alex, sounds like MI and MO are swapped - a 1:1 connection is required: MBHP_LTC::J1:VS to MBHP_CORE::J11:VS MBHP_LTC::J1:MI to MBHP_CORE::J11:MI MBHP_LTC::J1:MO to MBHP_CORE::J11:MO MBHP_LTC::J1:VD to MBHP_CORE::J11:VD Best Regards, Thorsten.

Hi Rio, did you already check with a MIDI Monitor if the appr. MIDI events are sent? Best Regards, Thorsten.

Hi Allan, as long as the new owner is aware of this, it's ok for me. The bootloader update is essential, otherwise the MBSEQ V4 application could crash! Best Regards, Thorsten.

Hallo Christian, leider vermischst Du hier verschiedene Projekte, die untereinander nicht kompatibel sind. So kann man bspw. die MIDIO128 Firmware nicht dazu bringen, Encoder zu scannen, wenn man sie einfach mit dem MIDIbox64E Editor konfiguriert. Das waere in etwa so, wie wenn Du versuchen wuerdest, einem Moog Voyager FM Klaenge zu entlocken, in dem Du ein DX7 Patch auflaedst :turned: Mal davon abgesehen, sind Encoder in der MIDIO128 Firmware gar nicht vorgesehen... Deine Ansprueche an die MIDIbox sind so vielfaeltig, dass ich zumindest sagen kann, dass das mit existierenden Firmwares nicht moeglich sein wird. Du muesstest Dir eine eigene MIOS32 App programmieren (oder programmieren lassen...) Gruss, Thorsten.

Shiruken is right: It will only work with a 12 MHz crystal, because the PLL is configured accordingly. Best Regards, Thorsten.

:w00t:

Doublepost, reply in german:

Hallo, zu 2) das passt so - der "Bildschirm" vom LC Host (also das, was von der DAW gesendet wird) ist 2x55 Zeichen gross, und dieser wird zentriert ueber die beiden 2x40 LCDs dargestellt. Es gibt alternative Display-Modi, die sich entweder ueber eine Tastenkombination selektieren lassen (suche nach ID_MBLC_DISPLAY_PAGE0 .. ID_MBLC_DISPLAY_PAGE3), oder aber auch im MIOS Terminal. Das koenntest Du auch gleich mal ausprobieren: tippe mal "set lc_page 3" im Terminal, in dieser Page sollte der 2x55 Screen ueber beide Displays gezogen werden (zwischen den 7er Bloecken werden Leerzeichen eingefuegt) Es gibt insg 4 verschiedene Modi ("set lc_page 1" .. "set lc_page 4"), und wenn mich nicht alles taeuscht, laesst sich die Einstellung mit "store" im EEPROM abspeichern, so dass sie beim naechsten Power-On automatisch eingestellt wird. zu 3) werden die Meters eigentlich von Deiner DAW unterstuetzt? Wechsel mal zu "set lc_page 2", hier werden die Meters in der unteren LCD Zeile graphisch dargestellt. Zur LED Helligkeit: gefaellt mir auch nicht. Das Problem ist, dass LED-Ringe und Meters sich das selbe DOUT Register teilen. Probiere mal folgendes in lc_hwcfg.c aus: ///////////////////////////////////////////////////////////////////////////// // used by lc_dio.c // the schematic can be found under http://www.ucapps.de/midibox_lc/midibox_lc_ledrings_meters.pdf // NOTE: the shift registers are counted from 1 here, means: 1 is the first shift register, 2 the second... // 0 disables the shift register // NOTE2: it's possible to display the meter values with the LEDrings by using ID_MBLC_*LEDMETER* buttons! // this feature saves you from adding additional LEDs to your MIDIbox ///////////////////////////////////////////////////////////////////////////// lc_hwcfg_ledrings_t lc_hwcfg_ledrings = { .cathodes_ledrings_sr = 9, // shift register with cathodes of the 8 LED rings .cathodes_meters_sr = 13, // shift register with cathodes of the 8 meters .anodes_sr1 = 11, // first shift register with anodes of the 8 LED rings (and 8 meters) .anodes_sr2 = 12, // second shift register with anodes of the 8 LED rings (and 8 meters) }; [/code] hier habe ich cathodes_meters_sr auf DOUT #13 gesetzt - sind die LED Ringe nun heller? Gruss, Thorsten.

Alternative firmware without LED flashing can be downloaded from: http://www.ucapps.de/floorboard/floorboard_v1001_noflash.hex.zip Best Regards, Thorsten.

Hi Nicolas, if you've enabled the ENABLE_MBNET flag, this could be the reason. In this case, RB3 is available at RE2, and RB2 at RE1 of the PIC18F4685 Could you please check your setup file? (resp. which one did you use for upload?) Best Regards, Thorsten.

Hi Luke, I will test the accuracy with a digital pulse generator soon (just added this to my TODO list) Best Regards, Thorsten.

If you mean this MIDI cable: then I can confirm, that it neither works properly under MacOS, nor under Windows or Linux It has a design flaw which prevents proper SysEx transfers. The GM5 order will probably start this weekend! :) Best Regards, Thorsten.

Your plan should work, just replace MID1 by OUT1 :) The 4 USB ports should work under Win7 with the Korg USB MIDI driver: Best Regards, Thorsten.

ok from my side. But: could you please test the USB MIDI connection to the STM32 core before selling it - and update the bootloader? Otherwise debugging could be difficult for somebody who hasn't built the module from scratch. Best Regards, Thorsten.

ok from my side. Best Regards, Thorsten.