TK.

Hi, MIDI In and Out port are part of the core module (see MBHP_CORE page). Once you are ready to upload the firmware, MIDI In and Out have to be connected to your computer. This is basically described at the bootloader page. Later you can connect a keyboard, a MIDI controller, a hardware sequencer, your PC (for software sequencing) etc.. to MIDI In for receiving Notes/CCs/Aftertouch/Pitchbender/SysEx. Did you ever control an external synthesizer with your MIDI gear? MIDIbox SID is just the same... :) PSU: some details can be found here: http://www.ucapps.de/midibox_sid_manual_hw.html Please note that most features explained in the manual are only supported by the new MIDIbox SID V2 firmware, which requires a PIC18F4685 Best Regards, Thorsten.

Hi Wicked One, welcome to the forum! :) A second encoder row is not supported, and from the available resources I would say it's impossible to add such a feature. But there are also good news: the DIN sync output has a seperate divider within the BPM menu page :) Best Regards, Thorsten.

Hi abcmann, cool that your MBSID is already working on your first forum post! :-) I've cancled the PIC based USB project, but if the guy writes that his firmware is working, I would propose to try it out. Since I'm using the 2x4 MIDI router, I've no personal need anymore for a USB solution (I prefer direct MIDI routing without the need for a PC in order to reduce latencies) Best Regards, Thorsten.

yes this shouldn't make a difference and is not required Best Regards, Thorsten.

So, you even don't get the MIOS boot message? Did you notice any error message during the code upload? Could you please upload the device_id_00.hex file of the change_id package? This ensures that the ID header is programmed correctly (and especially that the right LCD type is selected) Sidenote: under normal circumstances this doesn't need to be done. I only want to ensure that you are starting from a proper state. The PIC ID header is normaly programmed with the bootloader, and is never touched by any application - only exception: change_id Btw.: who did program the bootloader, and which version are you using? Best Regards, Thorsten.

Absolutely not - and I'm also sure, that you don't need to reburn the bootloader with a PIC programmer. MIOS and firmware can be easily uploaded via MIDI within a couple of seconds, thereafter your installation will be up-to-date again. :) I would recomment to install the latest MIOS version (MIOS V1.9e), and to try MIDIbox SID V1.7303 and MIDIbox SID V2.0beta4 (note: beta4 will be the last one which runs on a PIC18F4620 - with beta5 the 64k border has been reached) I propose this, as I cannot guarantee, that any application version will work with any MIOS version. I can only recomment: whenever you notice a strange behaviour, please always make sure that you are using the latest releases. Please let me know if you still notice random characters after the update Best Regards, Thorsten.

Thats strange, your buttons are looking similar to my own (DT6 from reichelt), and I never noticed such problems. I don't think that a debouncing function would help here. Debouncing is used to filter transients after an event has been sampled, but the initial event will always be forwarded to the application. Let us know how the other buttons are working Best Regards, Thorsten.

LEDs are driven time multiplexed, in addition the weak 74HC595 output drivers limit the current, therefore your calculation is wrong. I just did some measurements. When all steps are activated (all green LEDs on), and the sequencer is running (vertical line of red leds), the current is about 110 mA Best Regards, Thorsten.

PIC18F4620... hm, I haven't tried the MBSID application on this derivative for a long time - which MIOS release are you using, and which firmware version? Best Regards, Thorsten.

Did you change the relative positions in LC_HLP_MTCPositionGet_SMPTE (lc_hlp.inc)? Please compare it with the original code - this function should not be touched to ensure, that all digits are print on screen Best Regards, Thorsten.

It's maybe a short, by sending different characters the affected data line can be found out. MIOS Studio provides a special debug window which allows you to send characters to the LCD. They will be visible for 2 seconds, before the MBSID application switches to the previous screen again. Could you please write down which characters you see when following strings are sent to MBSID: (these are 8 spaces) 00000000 11111111 22222222 44444444 88888888 @@@@@@@@ PPPPPPPP aaaaaaaa pppppppp Are you using a PIC18F452, or already a PIC18F4685? Best Regards, Thorsten.

It's explained here: http://www.ucapps.de/midibox_seq_v2.html Keyword: "vintage" Note that MBSEQ V3 doesn't support pots/faders anymore, therefore the reference to MBSEQ V2 Best Regards, Thorsten.

Most of your requests are already implemented! :-) See the user manual and listen to the sound examples: http://www.ucapps.de/midibox_sid_manual.html Unisono: search for detune. Offset: search for phase offset and delay Independent control of oscillators is possible with the multi engine. The voices are dynamically allocated, but especially for ring/sync effects I've added an optional static allocation. So: yes you can do this, but the gate of the third oscillator needs to be controlled from a seperate MIDI channel. By enabling GSA, the gate will stay active once it has been triggered the first time. Best Regards, Thorsten.

Hi Razmo, yes, super-poly isn't a big deal, but there are about 1000 other features I want to add to the first final release which are also cool, and also easy to implement. Step by step w/o hurry - I'm young, I've the time... ;-) Full SysEx Implementation is already available for the lead and multi engine. There is no user-friendly documentation, but as you are a programmer: The SysEx strings are listed in midibox_sid_sysex_implementation.txt The SysEx structure in app_defines.inc, search for "Patch Record Structure" Most important for Sound Diver handling is the capability to divide a 8bit value into two 4bit values, because the sysex data part consists of 1024 nibbles for a 512 byte patch Best Regards, Thorsten.

With MBSEQ V2 (vintage option for analog controllers) you can do this Best Regards, Thorsten.

Maybe it's possible to narrow down the issue: which kind of characters do you see on screen? Are they changing from time to time, or are these always the same characters? Do you see some text (e.g. Chn.) which doesn't change? Best Regards, Thorsten.

Status: got the parts, haven't found the time yet to build the circuit Best Regards, Thorsten.

Soviel ich weiss, hat dieses Remote-Display Konzept noch niemand umgesetzt. Und die Programmierung ist auch leider nicht ganz so trivial, da man das Menuhandling komplett ueberarbeiten muesste, um den MIDI Traffic zu minimieren. Die MB64 Applikation ist hierfuer nicht geeignet. Am besten faengt man ein neues Projekt an, in dem man von Anfang an darauf Ruecksicht nimmt. Dieses koennte auch in C programmiert sein... Gruss, Thorsten. P.S.: auch von meiner Seite Respekt dafuer, dass Du eine funktionsfaehige Box bereits im ersten Forumposting vorzeigen kannst! Was dagegen, wenn ich sie in der MIDIbox of the Week Section veroeffentliche? :)

For the MIDI router project, I warmed up a waldorf knob in a hot-water boiler, so that it was elastic enough to stick it over a burns encoder. It can be easily removed without a knife Best Regards, Thorsten.

Hi Tom, my first statement to this issue won't help you, but I must highlight this: thats a very interesting observation! I will add the reset trick to the troubleshooting guide as an important experiment to check, if the core module is booting thereafter. But before, the reason for this failures has to be found out of course. It's propably a power issue - maybe your PSU doesn't deliver enough current during power-on, so that parts of the PIC is not properly reseted? I guess your LCD has a backlight? Did you already try to boot the MIDIbox without the LCD backlight connection? Best Regards, Thorsten.

I'm surprised that you already took care for a heatsink and ventilation slots - your MIDIbox seems to be constructed better than many other ones. Also the operating temperature range of the LCD seems to be normal. If random characters appear again, please measure the supply voltage. This could give a hint (but propably it doesn't... just a hope ;-)) Best Regards, Thorsten.

Thats very hard to say, and I'm sure that if anybody would start to write down a list, it would be partly wrong, or some ground connections would be missing. The easiest approach is to compare the board with the schematic. I would propose to print out the schematic, search the parts on the board in the schematic, check if it is connected to ground, and wire the appr. connection if it is missing. Mark off each part you've checked that way to ensure that none is missing at the end. This should be a process of ca. 15 minutes - and it will be complete :) Best Regards, Thorsten.

I used some spare parts and haven't taken care for certain trimpot values or capacitor types. The circuit matches with the schematic in the datasheet. No tricks, no black magic. For best circurity please ask an analog expert, and not me - I'm a novice in this area and the wrong person who could give you the right tips. I'm happy enough that I haven't fried the CEM3378 during the experiments, and I don't want to take over the responsibility that you destroy your own CEM3378s Best Regards, Thorsten.

Great, thank you very much! :) It listened to the session four times today in the car (direction Italy - nostalgic feelings - perfect match ;-)) Best Regards, Thorsten.

Hi Matteo, in my eyes this is the expected behaviour. All parameter layers are controlled by the trigger layers. There is only a single gate for all layers, and this one will trigger all Notes/CC of the step. There is no solution available which allows to trigger the notes/CCs independent from each other (only exception: the event modes which have been prepared for drums) Best Regards, Thorsten. P.S.: thanks for the postcard! :)