TK.

Hi Rava, today a typical MIDIbox consists of the MBHP_CORE_LPC17 module, the SPI transfer rate can be changed during runtime and is typically chosen based on the bandwidth requirements and max. "desired" cable length. Anyhow, what kind of informations have to be transfered over SPI? And why do you think that SPI is better than MIDI at the common baudrate? Doesn't this overcomplicate things? And why are additional Microcontrollers required at all? E.g. MBNG could control up to 8 LRE8x2 boards from a single SRIO chain (see for a setup which uses only 4 LRE8x2 to get an impression how big such a controller is) And MBNG provides pretty cool features as well! ;-) Best Regards, Thorsten.

You can't use a DOUT pin to output MIDI data. My proposal for such a setup would be, to connect a TTL based MIDI Output (e.g. J4B.SD) with the Rx pins of the BassBoys in parallel. The grounds have to be connected as well (e.g. via J4B.Vs) Now each synth will receive the same MIDI data, but you are able to differ between the synth by using different MIDI channels. If SysEx data is transmitted as well, then I hope that BassBoy supports a Device ID? Best Regards, Thorsten.

Yes, just type "make clean" in the application directory, pack it into a .zip file and attach it to this thread. Best Regards, Thorsten.

Hi Alex, yes, you can use the STM32 core for MBNG, and the LPC17 core for MBSEQ with AOUT. It will be possible to access the AOUT channels directly via NRPN In addition (but this is unrelated to your request, just a general informations for others), I'm planning a new routing option which allows to send MIDI events to the selected MIDI port/channel of the 16 tracks. It will work the following way: if an external MIDI controller (such as MBNG) sends MIDI events to MBSEQ over channel 1, the events will be routed to the selected MIDI port and channel of Track #1 Channel 2 will be routed to the MIDI port/channel of Track #2, etc. This will significantly simplify the integration of MIDI controllers and keyboards! :smile: Best Regards, Thorsten.

Hi Sebastian, there is no ready-made PIC based MIOS application, which would allow you to drive such a cube without some (complicated) software enhancements. Only the LPC17 based MIDIbox NG Firmware would provide this by default (even for RGB LEDs - and with the possibility to dim the LEDs in order to get different colours! :) Best Regards, Thorsten.

Although I don't want to from trying to implement the J5 based button functions: for me it sounds like a problem with the SC line to the shift register. If it would be permanently 0V or 5V, you would notice exactly the described issue. Best Regards, Thorsten.

Yes, as far as I remember, only the crystal had to be changed, the IO pin assignments should be compatible :) Best Regards, Thorsten.

Hi Freddy, you need a dedicated driver for each pin which drives the optocoupler of a MIDI IN (in fact: the inbuilt LED of an optocoupler). A 74HCT541 could be used for such a purpose - it would allow you to drive up to 8 MIDI INs Best Regards, Thorsten.

A value starting with 0 indicates an octal value: http://en.wikipedia.org/wiki/Octal Such as a value starting with 0x would indicate an hexadecimal value Therefore 08 doesn't work Best Regards, Thorsten.

It won't be possible to control a 808 bass drum from a J5 output, because you will need a 1 mS trigger! Such triggers are only available at DOUT pins, and they have to be configured in the MBSEQ_HW.V4 file: # additional gate triggers are available on common digital output pins of the # DOUT shift register chain - they are assigned to AOUT channel #16 (Note C-1, C#1, D-1, ...) # define the shift registers which should be used here (each provides 8 gates) # Note that SRs assigned to this function cannot be used as LED outputs (exclusive function) # Allowed values: 1-16, 0 disables the function, all other values invalid and not allowed DOUT_GATE_SR1 0 DOUT_GATE_SR2 0 DOUT_GATE_SR3 0 DOUT_GATE_SR4 0 DOUT_GATE_SR5 0 DOUT_GATE_SR6 0 DOUT_GATE_SR7 0 DOUT_GATE_SR8 0 # if set to 1, the DOUT "gates" will send 1mS pulses # useful for analog drums DOUT_1MS_TRIGGER 0 They will work at 5V - like on the MB808 (the second reason, why shift register outputs are used instead of 3.3V based J5 outputs) DOUT bassed triggers can be accessed over AOUT channel #16 as described in the manual: http://www.ucapps.de/midibox_seq_manual_m.html Best Regards, Thorsten.

This new requirement for additional SRs will add a lot of complexity! I wish it would be possible to change the BLM_X assignments, but this would make all existing MBSEQ_HW.V4 files incompatible :sad: There is just no no clean solution for this... Best Regards, Thorsten.

Hi Alex, such a feature would require a some mapping tables which are very hard to maintain! :-/ (effort that I don't really want to spend by myself) You could use a second core and run the MBNG firmware on it. It could send NRPN parameters to the MBSEQ: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fsequencers%2Fmidibox_seq_v4%2Fdoc%2Fmbseqv4_cc_implementation.txt A direct access to the CV outputs is currently not provided via NRPN, but I could add this if you go this route. Best Regards, Thorsten.

Chords are defined in this table: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fsequencers%2Fmidibox_seq_v4%2Fcore%2Fseq_chord.c Since there are already many options to realize enhanced chords on a much more powerful way (as mentioned above), I'm not planning to provide a customizable table. Please try out my proposals first before requesting a feature which is redundant, leads to unnecessary programming effort at my side and overcomplicates the firmware. Currently you are able to play multiple chords in different octaves from a single track. Alternatively you can record customized chords... what else is really required...? Best Regards, Thorsten,

Hi Moroe, have you ever tried to download the files of your session directory with the MIOS File Browser? You will notice that it takes a lot of time - even via USB! -> not practicable! Therefore a better solution (and this is how I organized my setup) is to use dedicated sessions in MBSEQ for different projects/songs in your DAW - with the same name! In theory it would even be possible to send a short SysEx command from your DAW to load the session remotely - just emulate the MIOS Terminal command (but in practice your DAW probably doesn't allow a comfortable entry of such ASCII commands) Best Regards, Thorsten.

Yes, this seems to be a problem with the cable. Especially this measurement: shows, that there is no direct connection between the LCD RW pin, and the core RW pin (btw.: you mean J15B, not J5B) Otherwise you would measure exactly the same voltage. Instead it looks like LCD RW is connected to J15A:Vd (5V) Best Regards, Thorsten.

Set the Bank to 2 in order to send the patches to bank B For bank C take 3, for D bank 4, etc. Best Regards, Thorsten.

It would be interesting if RW is still 5V, or 3.3V now It also makes sense to measure the voltage directly on the core, including the pin on the LPCXPRESSO (see schematic). Measure this with LCD cable connected and disconnected! Best Regards, Thorsten.

If it's related to the push-pull configuration, you would only need to compile the latest version in the repository. Here is a prebuilt binary: http://www.ucapps.de/mios32/midio128_v3_014_pre1.zip Please let me know if this solves the issue - in this case I will release v3.014 officially Best Regards, Thorsten.

Hallo Roman, was ist eigentlich genau unter einer "Emulation" zu verstehen? Handelt es sich dabei um verschiedene Parametersaetze, also quasi ein "Ensemble"? Gruss, Thorsten.

this problem has been solved (as you can see at the end of the thread), and the latest MIDIO128 release contains the changed LCD driver. Yes - it makes sense to measure the voltages at the LCD. And if you notice a failure, continue measuring at the core side to clarify the wrong (or missing) connection. Best Regards, Thorsten.

Hm, strange that sdcard_format doesn't work... actually I would expect that it works more reliable than a PC formatted SD Card. The correct configuration for the router would be: set router 1 USB1 all OUT2 all set router 2 IN2 all USB1 all Best Regards, Thorsten.

Cool! :) Best Regards, Thorsten.

Switching ground is a bad idea - Vdd would be the better choice. It could also be, that this was a temporal issue which is fixed now. The directory contains the artifacts from this malfunction. I would propose to format the SD Card with the "sdcard_format" command in the MIOS Terminal. Best Regards, Thorsten.

Hi, sounds like the LCD isn't initialized - either the RS/RW/E, or the data lines are not connected properly (or in the right order). The latest MIDIO128 release provides a "testlcdpin" command which allows to troubleshoot such problems. Just enter this command in the MIOS Terminal to get the testing instructions. Best Regards, Thorsten.

Cool! :) Could you please do me a favor and test following version at your side: http://www.ucapps.de/mios/midibox_lc_v1_6f.zip In main.inc, USER_Init you only have to change the #if 0 by a #if 1 to enable KS0108 without programming the PIC ID Header The GLCD view should be enabled by the MIOS_LCD_Init call in the middle of USER_Init (hopefully) Best Regards, Thorsten.