TK.

Hm! This is strange. It can't be excluded that a wrong resistor or capacitor has been soldered for the small transistor based amplifier unit which is connected to Pin #27 (see also http://www.ucapps.de/mbhp/mbhp_sid_v2.pdf) Because it's in the same release package like the firmware (-> presets directory) One is for the backlight brightness, the remaining ones control the LCD contrast for the slave PICs. They are only useful if a LCD is connected to a slave for debugging purposes. Best Regards, Thorsten.

Almost like Powerpoint ;-) You could consider to use a schematic editor instead, e.g. the one integrated into Eagle. Best Regards, Thorsten.

Thanks! And it was a lot of fun to create them! :) The missing descriptions for the Multi-Arp configurations will be available this evening. very strange! This seems to be related to a auto-correction function on the server. I uploaded a new version with postfix b It's now also possible to access the release (and especially the backup) directory directly: -> http://www.ucapps.de/mios32 Best Regards, Thorsten.

no, there is no backup, and no restore mechanism. Best Regards, Thorsten.

fixed the link. Best Regards, Thorsten.

Mixer maps can now be named in V4.076

now available in v4.076

A new release is available: MIDIboxSEQ V4.076 ~~~~~~~~~~~~~~~~~ o the MIDI router forwards SysEx messages regardless if channels are filtered, or "All" is used. It's ensured that messages are only sent once if multiple router nodes forward to the same destination port. o added optional "SAVE" and "SAVE_ALL" button function to the MBSEQ_HW.V4 file o it's now possible to change the mixer map name. In the mixer page, press SELECT + GP16 button to enter the name editor. o LFO page: the current CC can be sent manually by pressing the GP14 button. o Multi-Arp events are working like intended (again) And three new tutorials which describe, how to create typical "Berlin School" sequences, and how to use the Arpeggiator :smile: -> http://www.ucapps.de/midibox_seq_manual_tut.html (Tutorial #6 needs V4.076, otherwise the Multi-Arp events are not played correctly) Best Regards, Thorsten.

READY! :smile:

Are you using identical SIDs? Did your father get any error messages during the upload? Can't be excluded. Another upload could help. But consider, that a previously incomplete upload could lead to a wrongly initialized patches into the BankSticks - and this could explain, why some SIDs are not working (e.g. because parameters of the left side SID are corrupted). This could be solved by uploading the preset library. MB6582 uses a button/LED matrix configuration, therefore MIDIO128 (V2) can't be used for testing. There are no debug instructions for this. Left and Right SID of the master core Best Regards, Thorsten.

Btw.: the best feature of the MIDI Monitor is the "Spy" function, which allows you to display outgoing MIDI streams as well (something what isn't possible under Windows). It's extremely helpful to determine, which messages are sent to a MIDI device. Best Regards, Thorsten.

RESET! Why do you want to shift the voltage level to 5V, if your buffers already allow to change the gain factor? I see no need for a level-shifter (and it won't add more protection). Best Regards, Thorsten.

I wouldn't do this, because the danger is too high that you destroy the core IO pins if you connect the gate to the wrong plug on your synth (e.g. higher voltage output) Instead, please use a 74HC541 between the J5 based gate outputs and your synth. It will also act as a level shifter, see http://www.ucapps.de/midibox_seq_manual_hw.html (search for "CV Outputs") Best Regards, Thorsten.

Correct! @fourfour: don't forget to spend spirit a beer for his careful observation! :) Best Regards, Thorsten.

Somehow this doesn't make much sense. This meter is intended for audio signals, not for MIDI. I also don't see a way how you could access the audio channels of your DAW with such a meter. Best Regards, Thorsten.

Hi, MIDIbox SEQ V2 is a pretty old software, it won't be supported anymore. Why are you not upgrading to at least V3 (which is better documented)? Anyhow, MBSEQ V2 is good for any MIDI device - but the possibilities are very restricted compared to V3 (or V4 of course) Best Regards, Thorsten.

MBSEQ_M.V4 is a binary file, it could only be edited with a binary editor, otherwise you will corrupt the datastructure (as you noticed). There is no documentation about how to edit such binary structures (and it would be error prone anyhow) I added your request to make Mixer Map names editable in the wishlist. Since you are the first one who requested this, the priority is low (it will be some work to create the UI extension) Best Regards, Thorsten.

The help page shows you the current setup, it's still "single_usb" since you've to reboot the core to take over the change (and to re-initialize the USB interface) In addition, under MacOS you also have to delete the old MIDI interface configuration in the Audio-MIDI-Setup) This is documented at the end of this page: http://www.ucapps.de/mios32_bootstrap_newbies.html Search for the keywords "Working under MacOS" Best Regards, Thorsten.

I'm using "MIDI Patchbay" since years, it's very easy to use and works fine with SysEx (you've to enable it under "Other") -> http://notahat.com/midi_patchbay/ Best Regards, Thorsten.

Yes, the same way like for other EVENTs Sounds like a short circuit! There is definitely a cabling mistake, please doublecheck it Best Regards, Thorsten.

Yes, since the bootloader and MIOS are already installed (these are different .hex files), you only need to install the actual application anymore - only one of the .hex files in the MIDIbox SID V2 release package. I guess that you selected the right one. You've to install MIOS and the application also for the other PICs (the MBSID Slaves). An application update via master core will only be possible (in future), once MBSID has been installed on all slaves. IMPORTANT: keep in mind, that each slave needs a dedicated Device ID (1, 2 and 3). Only the master PIC should have device ID 0 See also: http://www.ucapps.de/midibox_sid_manual_in.html The firmware consists of the bootloader, MIOS and the application (MBSID V2 in your case) SmashTV only installs the bootloader You have to install MIOS and the application. I don't think that anything is wrong here. Such details can change from time to time You could use the mbsid_testtone application to check if the SID socket is really faulty, or if this issue is related to a configuration issue: http://www.ucapps.de/mios_download.html Best Regards, Thorsten.

Servus, danke fuer das Lob! :) Ich koennte mal nachschauen, was sich da machen laesst. Ist "|" das einzige problematische Zeichen, oder gibt es noch mehr? Gruss, Thorsten.

You could try Platypus for this purpose: http://sveinbjorn.org/platypus Best Regards, Thorsten.

Yes, just set the current BUTTON_* assignment for the F button to "0 0" in order to disable it, and then configure the appr. SR/pin combo for the upcoming BUTTON_SAVE or BUTTON_SAVE_ALL function. Best Regards, Thorsten.

of course, because fwd_id will forward the received value to the next event (e.g. forwarding a button value to a LED) E.g. you could use the "trigger" command in your .NGR script to trigger the transmission of ENC:65 and ENC:66 Best Regards, Thorsten.