Rutger implemented a Java based patch editor and bank librarian for MIDIbox SID V2, which allows you to manage/modify/create new patches under Windows/Mac/Linux remotely without the control surface
Even users who built a complete MIDIbox SID might find it very useful, as this software gives a good insight into hundreds of parameters for all 4 sound engines! 
Note that the editor is still under development. Your feedback is very appreciated!
Best Regards, Thorsten.
Wow, great! It’s released ;). Thanx, TK!
Rutger
ps. Wow, I’m surprised about the screenshots. It looks totally different on a Mac!
Perfect timing. I’m building my first MBSID this weekend and probably won’t get to the control surface, yet. This will be fun to play with once I get my SID modules built, tested and working. Thanks Rutger and TK!
Nice work guys!
Hi TK!
Those screenshoots look fantastic! Alas, I tried to launch it, however, and was greeted with the following:
MacDawgPro:MIOS Programs tim$ java -jar MBSIDV2_Editor_v0_1.jar
Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException: 0 >= 0
at java.util.Vector.elementAt(Vector.java:432)
at org.midibox.midi.MidiDeviceRouting.<init>(MidiDeviceRouting.java:56)
at org.midibox.apps.SIDV2librarian.SIDV2librarian.<init>(SIDV2librarian.java:44)
at org.midibox.apps.SIDV2librarian.SIDV2librarianGUI.main(SIDV2librarianGUI.java:537)
I thought it might simply be because I didn’t have my MB-SID connected, but even if I did, I figured Java still wouldn’t know which interface is for the MB-SID?
Note that Rudger did all the work, not me!
You will be asked by the editor if no MIDI interface is connected
Maybe no interface is found at all?
And which OS and Java version are you using?
Best Regards, Thorsten.
Hah oh yeah. Duh. That was, indeed, the problem. After I plugged my M-Audio MidiSport 1x1 in, it worked.
Just in case you need it, I’m running a MacBook Pro (OS 10.5) with the stock Java:
MacDawgPro:~ tim$ java -version
java version "1.5.0_13"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13-b05-237)
Java HotSpot(TM) Client VM (build 1.5.0_13-119, mixed mode, sharing)
I do have ‘mmj’ installed as, without it, it does not detect my MibiSport 1x1 (which is the only MIDI interface I use on the Mac). I do most of my music stuffs with a Windows PC (but a good chunk of the MidiBox dev stuff on my Mac) so I will try the application on it the next chance I get.
Shame on me for not trying that first 
Awesome!!! 
That’s exactly what I’ve been waiting for since I’ve built my MB_SID
Thanks TK!
Thanks Rutger!
I’m very happy about this. It will make editing those wavetables a lot easier.
Thank you!
Hi everyone,
happy you guys like it! I hope it speeds up the process of building patches and also allows for easy exchange of patches between users. There may still be some bugs in it, so please report them. Also, I have some extra features in mind that will be added in the future.
A special note to Mac users: the part of Java that drives the midi interface is not capable of handling USB devices or other plug-and-play things correctly, therefore it’s recommended to install the so called ‘mmj’ Java extension (http://www.humatic.de/htools/mmj.htm) if you are experiencing problems with your midi device being recognized by the program.
Best,
Rutger
Nice!
This will surely make my step-A a lot easier to handle…
Receiving a patch/ the whole bank works, but shortly afterwards it says my sid doesn’t respond.
Edit doesn’t work either…
My Midiport is the mpu-401 of my mainboard…
Does the tool require the latest firmware? I’m using 2.0RC17…
Now I have a reason to finally build mine!
I was waiting for the MB6582 pcb to build a complete synth, but now I can make the sounds w/o the controllers!!!
Thanx Man! You Rock!
A special note to Mac users: the part of Java that drives the midi interface is not capable of handling USB devices or other plug-and-play things correctly, therefore it’s recommended to install the so called ‘mmj’ Java extension (http://www.humatic.de/htools/mmj.htm) if you are experiencing problems with your midi device being recognized by the program.
TK, maybe you should put this info in the SysEx editor page (http://www.ucapps.de/midibox_sid_manual_ed.html)
What do you think?
Does the tool require the latest firmware? I’m using 2.0RC17…
Yes it does! Good point. You need at least RC19, but preferably the latest. From that version on the communication between Editor and MBSID is different.
Best,
Rutger
Ah, ok…as it seems, i will update today…
Will those patches, which i already exported with the editor, work with the new firmware?
Does flashing a firmware even affect the patches stored on the SID?
No, it does not. At least not after a whole lot of revisions back when the patch structure changed.
Very nice work - unfortunately, I am having the same problem as Imp. When the program is first started I can Receive or send a patch or bank dump, but immediately after this I start to get error messages - sometimes there is an error about the midibox not receiving the correct number of bytes, then there is an error that communication has been lost. My SID has the latest version of MIOS and the SID app, also MIOS Studio (and other Midi software) works perfectly on this system, so I don’t think it’s a Midi problem (system is a Dell laptop with USB Midi cable). Any help would be appreciated. Cheers
Hmm, it smells like a bug indeed.
The communication between software and MBSID is quite difficult. Usually the software sends and the MBSID responds. If the MBSID doesn’t respond you get this error, but it might be that the message still arrived correctly at the synth, in this case there’s just no way for the software to know.
I’ll try to find out what’s happening.
Best,
RUtger
possible bug:
I was changing filter parameters, and suddenly the cutoff knob changes osc type instead, happened once, haven’t tried to reproduce it yet
btw. I get the MBSID doesn’t respond thing too from time to time
Wow just saw this now and downloaded it… Will give it a try tomorrow… Nice looking gui and thanks for taking the time to do this…