TK.

You could also call the buttons "Ensemble" and "Patch/Bank". Bank could be selectable with the datawheel by pressing&Holding the Patch/Bank button. I don't think that somebody would switch between the 7 banks so often, compared by switching between ensembles and patches. Therefore these functions should get a higher priority. Best Regards, Thorsten.

My proposal goes a step further - or do you really want to click through 128 ensembles? Best Regards, Thorsten.

Before working with assembly language and meta events, I would suggest to go for the C wrapper for such a simple application, which would only use maybe 10% of the MIDIbox64 firmware. Here an example for soft-takeover: http://www.ucapps.de/mios_c_send_ain_takeover.html Using buttons: http://www.ucapps.de/mios_c_send_din.html Using LEDs: http://www.ucapps.de/mios_c_set_dout.html Best Regards, Thorsten.

It was clear to me, that you probably won't understand the technical details, therefore my answer is "it won't work" There are many MIDIbox users from italy, you could ask in the italy section of the forum for help -> http://www.midibox.org/forum/index.php/board,20.0.html Best Regards, Thorsten.

It seems that the extended BankStick uploading command, which is available since v1.8, hasn't been implemented yet :-( Best Regards, Thorsten.

So far I can see, the Rec/Solo/Mute/Select rows have a different order in my customized setup. Are there other mismatches? Best Regards, Thorsten.

I would place the "channel" buttons close to the "oscillator" buttons, because they belong together. A start/stop button for the arps & sequencers could be useful for live situations as well. Bankstick up/down: wouldn't it be better to replace it by a single button, which a) jumps back to the main page, and b) alternates the datawheel function for incrementing the bank instead of patch. Currently we have a similar behaviour for ensembles when pressing the menu button within the main page, but you could spent a special button for ensembles as well. Summary: replace Bank Inc/Dec by Bank/Ensemble button Usecases: press&hold Bank button: CS jumps to main page, datawheel increments bank press&hold Ensemble button: CS jumps to main page, datawheel increments ensemble press&release bank or ensemble button: CS jumps to main page, datawheel increments patch Best Regards, Thorsten.

Wrong - you can easily setup the NRPNs for MBSID V2: Note that the NRPN assignments I'm using here are only intented for testing purposes, e.g. L/R/All channel selection. All available NRPN parameters are documented under doc/mbsidv2_parameter_chart.txt Best Regards, Thorsten.

You are totally right, I overlooked this - yes, the menu controls are at the wrong side (for right-hand people) Best Regards, Thorsten.

An analog mixer would be sufficient Look at other synths - LCD and menu controls are mostly on the left Best Regards, Thorsten.

Super! :) Nun frage ich mich wirklich, warum das Problem nur bei der MBSEQ V3 auftritt, und nicht bei anderen MIDIboxen, die teilweise mit wesentlich mehr Shiftregistern ausgestattet sind. :-/ Gruss, Thorsten.

It should be described in the manuals which are comming with the debugging tool. But so far I know, PICkit get use of the low-voltage programming mode, accordingly the RB5 pin cannot be accessed by the firmware anymore - you won't be able to use a LCD. I'm sure that there are many people here who could burn and test the PIC for you. Where are you living? Best Regards, Thorsten.

My first thought: why are the waveform and ring/sync buttons so dominant? Wouldn't it be better to add 8 volume pots for the SIDs + 4 "Mono" buttons (which merge two channels together for multi engine) instead of spending area for functions which are not permanently used live? There is no "Poly" engine, it's called "Multi" engine (as you can play up to 6 instruments) The modwheel makes "Knob 1" obsolete Why not adding a second modwheel? CutOff and Resonance knobs are too close together. The modulation matrix is missing :) Best Regards, Thorsten.

Just use a PIC18F4685 and install the MIDIbox SID V2 firmware - beside of LFOs with MIDI-Sync, Sample&Hold, Envelopes it provides much more features you probably haven't thought of yet. :) -> http://www.ucapps.de/midibox_sid_manual_cv.html Best Regards, Thorsten.

Note, that this code will send invalid MIDI events when BLM_MIDI_STARTNOTE >= 65 It's better to write: MIOS_MIDI_TxBufferPut((pin + BLM_MIDI_STARTNOTE) & 0x7f); [/code] and something similar in MPROC_NotifyReceivedEvnt(); so that the "wrapped" note number is still maching between LEDs and Buttons Best Regards, Thorsten.

I updated the README.txt; version number not incremented Best Regards, Thorsten.

Me too, it is matching with the schematic (D0 is bit 7, D1 is bit 6, etc...) Ooops, you are right! I fixed this in version blm_example_v1_2 (-> see MIOS download section) For the 4x16 matrix (which I own) this scrambling is better. Therefore I guess it's only a documentation issue - I added your input to the README.txt file The processing routines in main.c (or in the host software) can easily map the column/row numbers to the "physical layout" if desired. Best Regards, Thorsten.

No - I'm working on USB devices maybe one week per year and therefore don't follow the progress. Which ID is printed on the package? E.g., my non-working (EUSART bug) rev2. has 0504409, the working rev5 has 07351KG I guess that the first four digits stand for year and calendar week of production. I've released the source code + some documentation now: -> http://www.ucapps.de/mbhp_usb_pic.html Best Regards, Thorsten.

Although I initially planned to cancel the project (which I've implemented years ago), I finally decided to release the MBHP_USB_PIC "as-is" with a documentation of the known issues. -> http://www.ucapps.de/mbhp_usb_pic.html Short summary: In general it works fine under Windows and Linux, but there is a potential risk for data loss when large SysEx dumps are sent and received concurrently. However, MIOS uploads are unidirectional, and therefore working stable enough Windows legacy driver is not multiclient capable. This means: you have to close your MIDI software (or release the MIDI ports) when using MIOS Studio The module is not working correctly under Mac OS X (tested with Leopard only) the latest PIC18F4550 (or PIC18F2550) revision 5 is required to overcome the EUSART bug no PCB available (yet), but MBHP_CORE module can be used. Just add the USB socket, a 470 nF cap, replace the crystal by a 20 MHz type, and add a Reset and Bootloader button. Best Regards, Thorsten.

Addendum: Rutger's MBSID V2 editor is doing very good progress - once it is available, configuring voice and MIDI assignments will be a piece of cake! :) Best Regards, Thorsten.

Schicke mir mal den PIC zu, ich moechte ihn an meinem MIDI Interface testen. Meine Adresse findest Du im ucapps.de Impressum Gruss, Thorsten.

You could solder the "link" cable at the bottom of the Core PCB. You are already doing this for the parallel bus connections to OPL3, so this would be a consequential solution. Best Regards, Thorsten.

Support for more than 4 cores is not possible due to conceptional reasons. Best Regards, Thorsten.

Please note that you are talking about the MBSID V2 firmware, and not about Wilba's MB6582 hardware variant. This isn't possible with the lead engine due to conceptional reasons, but with the multi engine. Use two instruments, assign them to different MIDI channels or keyboard zones. This can be done in the INS menu of the ensemble. Assign the voices of the first instrument to left SID (VAs=L), and the voices of the second instrument to right SID (VAs=R). This has to be done in the CFG menu of the patch Thereafter disable the Poly flag in CFG menu and you are done :) Yes, all this can be done with multi engine. You only need to configure the voice assignments and MIDI channel assignments as desired. No problem, with multi patches you have access to 24 seperate mono synths. Yep, MIDIbox SID V2 can be 24-part muli-timbral. Just have a look into http://www.ucapps.de/midibox_sid_manual_m.html Best Regards, Thorsten.

An update is now available (-> sdcc_skeleton_v1_9c) with a minor change in the makefile generator (GPASM_DEFINES variable added to pass parameters to gpasm) Migration copy tools/mkmk.pl into your project. Best Regards, Thorsten.