TK.

Hi, I would say: 1st priority: GP and ABCD LEDs 2nd priority: Mute/Pattern/Song/Edit, Gate/Aux and Live LED 3rd priority: Stop/Play LED 4th priority: Rew/Fwd, Shift and Alt LED Best Regards, Thorsten.

nice tool! Best Regards, Thorsten.

What is the voltage at J1 and J2? Maybe your PSU isn't strong enough? Best Regards, Thorsten.

Great sounds! Please add some reverb drums after ca. 4 minutes! :) Best Regards, Thorsten.

Hi Peter, I read the datasheet and haven't found any topic which would be in contradiction with the MBHP_CORE_STM32 requirements. You will have to jumper the VFD for Motorola mode (see chapter 6) However, since nobody tried this VFD before, it's probably better to test only one display before buying a second one. It would also be advantageous to have a return option for the case that the VFD isn't working properly for any reason. Note also that the power consumption is pretty high - the 7805 of the core module will need a heat sink! It could make sense to use a dedicated 7805 for the two VFDs. Best Regards, Thorsten.

I ordered a new backpanel and asked Schaeffer to compare it with the dimensions of the original panel before producing it. You don't really want to use (or even blind-order) my .fpd file before I tested the new panel, because it could cost you some money (ca. 75 EUR) or some fixing effort (three evenings at my side) if anything is still wrong! Best Regards, Thorsten.

Hi, there will be some news about motorfaders soon (in ca. 3..4 weeks) Please wait until then - it could be that as a beta tester you will get some high-quality Alps faders for free! :) Best Regards, Thorsten.

Great! :) Best Regards, Thorsten.

Hi, yes, this makes sense - it could be related to a power issue! You can check this by disconnecting the LCD backlight. Best Regards, Thorsten.

Ok, looks like a bad soldering joint at the core module - check the track which goes to the J8:Vd pin. Best Regards, Thorsten.

Do you mean MBHP_CORE::J8:Vd with the "line"? Best Regards, Thorsten.

I uploaded this firmware variant (of the midibox_808_v1a package), but can't reproduce the crash. It's possible to select all instruments with the encoder, and changes take place on all tracks (as expected) Does it crash immediately at your side, or are you doing something special? Best Regards, Thorsten.

Beta25 is available now: o now each OSC port has an individual configuration set which consists of the Remote IP, Remote Port, Local Port and Transfer Mode o an OSC Transfer Mode has been added, it can be configured in the network configuration page for each OSC port. In MIDI mode, all events generated by the track will be embedded into a 'm' type packet. This mode allows to tunnel MIDI events via ethernet to a proxy which runs on the host (or any device which is able to convert these messages) In "Text Msg (Integer)" and "Text Msg (Float)" mode, the OSC packets will be encoded the following way: - Note Events: /<chn>/note <note> <velocity> Integer: note and velocity in range 0 .. 127 Float: note still as integer, velocity in range 0.0 .. 1.0 - Poly Pressure Events: /<chn>/polypressure <note> <pressure> Integer: note and pressure in range 0 .. 127 Float: note still as integer, pressure in range 0.0 .. 1.0 - CC Events: /<chn>/cc <cc-number> <value> Integer: value in range 0 .. 127 Float: cc-number still as integer, value in range 0.0 .. 1.0 - Program Change Events: /<chn>/programchange <value> Integer: value in range 0 .. 127 Float: value in range 0.0 .. 1.0 - Aftertouch Events: /<chn>/aftertouch <pressure> Integer: pressure in range 0 .. 127 Float: pressure in range 0.0 .. 1.0 - Pitchbend Events: /<chn>/pitchbend <value> Integer: value in range -8192..8192 Float: value in range -1.0 .. 1.0 <chn> range: 1..16 o OSC option now supports SysEx transfers (SysEx stream is embedded into blobs) o it's now possible to route USB/MIDI/IIC/AOUT ports to the OSC ports in the MIDI Router page. o SysEx streams will now be forwarded by the MIDI Router as well. The Chn setting has to be set to "All" for source and destination port. This allows you to access the SysEx functions of your synth - it's even possible to upload a new firmware to a MIDIbox which is connected to a MIDI port of MBSEQ now. o MIDI->Misc menu: BLM can now be assigned to an OSC port [/code] Especially the SysEx forwarding function has been requested by multiple people. The OSC add-ons are only for nerds ;) Best Regards, Thorsten.

Such a function isn't available yet, and it will be some work. But I will add it sooner or later, because it definitely makes sense! :) Best Regards, Thorsten.

finally! :sweat: Best Regards, Thorsten.

Hi, which MIOS and midibox_808 firmware version are you using? Best Regards, Thorsten.

I guess that Wilba is currently on vacation - be patient, he will come back! ;) Best Regards, Thorsten.

Hi Tobias, thank you for releasing the windows driver! :) I would like to test it, but don't know how to use the RTP-MIDI protocol on iPad. Are there undocumented functions available in iOS, or did you implement the protocol stack for iOS as well? Best Regards, Thorsten.

No, thats uncritical. Hm, strange... it sounds like there is a power problem, e.g. Vss and/or Vdd between core and DOUT module not connected. This could cause such effects as well. Did you already check the connections between core and DOUT modules? Best Regards, Thorsten.

DA 10MM and DA 20MM I'm still working on the backpanel. Today I got an idea for solving the SD Card issue: by flipping the SD Card PCB inside the case there is no collision with the frontpanel LCD connector anymore. Disadvantage: the SD Card has to be inserted upside down (but thats acceptable for me) -> http://midibox.org/forums/index.php?app=gallery&module=images&section=viewimage&img=470 Best Regards, Thorsten.

Fortunately there is enough clearance, see also: http://midibox.org/forums/index.php?app=gallery&module=images&section=viewimage&img=471 MIOS (and MIOS32) can do this, but the software architecture of MBSEQ isn't designed for generating events with a period of less than 1 mS (1 kHz), because it needs this time for doing complex calculations on all 16 tracks. Best Regards, Thorsten.

Ok, I remember why I inserted this special check: VST based instruments didn't play any note in this special case (ca. 4 years ago) - I guess that meanwhile most VST instruments should handle this case properly? Best Regards, Thorsten.

The code snippet above already points you to the file: SEQ_CORE_* functions are located in seq_core.inc Search for the label and you should know where a something has to be changed. But be warned: changes can lead to unwanted side-effects! Best Regards, Thorsten.