TK.

Could this be an artifact from a previous build for STM32? What happens if you enter "make clean" before compiling the whole project again? Best Regards, Thorsten.

Hi Chris, glad to hear that you already managed to get to this point! The low-level function which sends NRPN controllers is sendNRPN(nrpnNumber, nrpnValue) Both parameters are 14 bits. decl chn = 0; decl nrpnNumberMsb = (nrpnNumber >> 7) & 0x7f; decl nrpnNumberLsb = (nrpnNumber >> 0) & 0x7f; decl nrpnValueMsb = (nrpnValue >> 7) & 0x7f; decl nrpnValueLsb = (nrpnValue >> 0) & 0x7f; if( nrpnNumberMsb != lastNrpnAddressMsb ) { lastNrpnAddressMsb = nrpnNumberMsb; midiout(0, {0xb0 + chn, 0x63, nrpnNumberMsb}); } if( nrpnNumberLsb != lastNrpnAddressLsb ) { lastNrpnAddressLsb = nrpnNumberLsb; midiout(0, {0xb0 + chn, 0x62, nrpnNumberLsb}); } midiout(0, {0xb0 + chn, 0x06, nrpnValueMsb}); midiout(0, {0xb0 + chn, 0x26, nrpnValueLsb}); oscout(0, '/1/nrpn', {nrpnNumber, nrpnValue}); [/code] As you can see, there is a check if the last MSB or LSB of the address byte has already been sent. Both variables need to be initialized in - this is done in resetNRPN(), called from init() - and init() will be executed "on load" as you can see in the Execution field. [code] // initialize with invalid values lastNrpnAddressLsb = 0xff; lastNrpnAddressMsb = 0xff; This should do the trick in a new panel. If you doing modifications in my own panel, I would propose to call sendCVNRPN(), because it adds the selected channel to the NRPN number. Best Regards, Thorsten.

I like the idea as well! :) Best Regards, Thorsten.

Hi Marxon, a reboot will happen if the MBSID MIDI OUT isn't connected to the MIDI IN of your PC (and/or not selected in MIOS Studio) Is the Query button working? I guess that it causes the same effect, right? Best Regards, Thorsten.

The best way would be if you would merge your changes into the official branch! :) They are selected via #ifdef anyhow, so that the danger is low that it disturbs an existing function. Best Regards, Thorsten.

Could also be related to the new guide track feature, I will check this. Best Regards, Thorsten.

Still haven't found the time to check the proposed OSC configuration at my side... :-( To the display issue: I never tested more than 5 CS lines... (and everything which hasn't been tested usually doesn't work ;-)) However, on a first look the driver looks ok and uncritical regarding the number of supported CS lines (up to 8 are available). What happens if you swap the CS lines of a "working" and "not working" LCD? Best Regards, Thorsten.

This seems to be unrelated to the hardware. The error message indicates, that something is wrong with the .hex file Could you please download the release from my webpage again, and could you please also try it with the latest MIOS Studio version? Best Regards, Thorsten.

We've multiple problems: - MIOS Studio 2 doesn't work correctly with bootloader v1.1 (which has been replaced by v1.2 more than 6 years ago...) - midimerger_pic18f_with_bootloader.hex can only be handled by bootloader v1.2 - the upgrade from v1.1 to v1.2 is cumbersome and error prone, multiple people already crashed their PIC so that it had to be flashed again with a PIC programmer - it seems that MIOS Studio 2 has also problems to parse the .hex file Idea: if I'm not wrong, you should be able to upload the midimerger_pic18f_without_bootloader.hex file with MIOS Studio 1: http://miosstudio.midibox.org/index_v1.html Background: bootloader v1.1 is located between 0x7c00..0x7fff and starts the application at 0x0000 in midimerger_pic18f_without_bootloader.hex the app is located at this address and MIOS Studio 1 is able to communicate with bootloader v1.1 Best Regards, Thorsten.

Ok from my side, it's really a great looking MB808! Best Regards, Thorsten.

ok from my side... Best Regards, Thorsten.

As mentioned above, I've ordered 100 Mini-PCBs, although only 76 have been requested yet - means: there will be some spares! The Mini-PCB is the best solution if you are planning to integrate an USB interface into a PIC based MIDIbox, resp. if you want to upgrade a device which doesn't natively support USB-MIDI: A GM5x5x5 is nice-to-have if you want to connect multiple synths to a single interface with common MIDI cables, please consider that this means that you also need two MIDI cables per device for bidirectional communication. With a Mini-USB (integrated into the device) you would only need one USB cable connected to the device (just leave out the DIN sockets and directly solder the "MIDI pins" together) - and you could optionally use USB as power supply in some cases (not for MBSID, not for MBFM since the power supply has to deliver more than 5V) It's also possible to control up to 5 MIDI devices through a Mini PCB if the digital IOs (at TTL level) are directly connected to J6! So, I hope that the remaining Mini PCBs are sold as well, otherwise I've to increase the price of the PCBs to compensate the money loss. Best Regards, Thorsten.

Short notice from my side (more details this weekend): I ordered the 250 chips + 100 Mini PCBs at Ploytec, and the order has already been confirmed. I've only ca. 30 GM5x5x5 PCBs anymore - they are white - is there a volunteer who would take over the bulk order handling for additional PCBs, e.g. with a different colour? Best Regards, Thorsten.

Before going into the details: do you have programming skills, or do you expect a ready-made firmware? Best Regards, Thorsten.

Unfortunately I can't retrieve the URL of the old posting - it must be somewhere in the forum (I guess it was from MTE)... On the other hand: I just remember that I personally adapted the MBLC firmware for 4 CLCDs while I visited doc some years ago, here is the source code and binaries: http://www.ucapps.de/tmp/midibox_lc_x4.zip The interconnections should match with the ones showed at the Wiki page. Could you please confirm that it's working at your side? Then I will integrate the variant into the original firmware. Best Regards, Thorsten. P.S.: the button/LED assignments are probably different - this will be solved once you've confirmed that the LCDs are working.

yep, die V4 kann man so konfigurieren, dass die Mutes mit dem Taktanfang synchronisiert werden! :) Gruss, Thorsten.

yes, thats possible! :) Best Regards, Thorsten.

Two sequences are running in parallel, and you can change the MIDI channel for both. See also the description of the MIDI Chn page:: Only a single channel is assigned to a track, it isn't possible to store it into step entries as this would blow up the data format (and isn't prepared anyhow). Playing multi-timbral synths from a single track also doesn't make much sense, since each step only stores a single length for all notes which are played concurrently. Only solution is to use the big brother MBSEQ V4 with 16 tracks in parallel, or to use an external MIDI keyrange->channel splitter if not already provided by the Synth itself. E.g. on MBSID V2 you could assign different keyboard split zones for different instruments which are played on the same channel. This would do the trick. Best Regards, Thorsten.

Where did you find the broken link exactly? Best Regards, Thorsten.

Could it be that you are sending other CCs in addition, such as CC#0 (bank change?) You could use a MIDI monitor (e.g. the one integrated into MIOS Studio) to check this. Best Regards, Thorsten.

yes, it's feasible since the Virus sysex format is well documented (e.g. under http://www.waf80.de/virus/sysex.html) and looks simple; it matches with my data model. Could you please send me a SysEx dump of a complete bank, so that I can try it out (I've to ensure that the checksum calculation is working correctly) Best Regards, Thorsten.

Thanks for the nice words! :) The librarian is now available in MIOS Studio 2.3.0 I hope that it works well at your side, I only tested it under MacOS 10.8 (Mountain Lion) Best Regards, Thorsten.

MIDIbox SID V2.041 is available now. From the ChangeLog: MIDIboxSID V2.041 ~~~~~~~~~~~~~~~~~ o corrected sysex handling for MIOS Studio SysEx Librarian [/code] The SysEx Librarian is part of MIOS Studio 2.3.0 Best Regards, Thorsten.

MBHP_MF_NG firmware v1.3 is available now It allows to select the MIDI channel in Mackie HUI, Motormix and various CC modes. The selection can be done with MIOS Studio 2.3.0 (or higher) Best Regards, Thorsten.