[rumpelfilter]

There's really a huge lot of great patches here! too bad I can't get them to upload properly to my Midibox SID (actually a sammichSID). But maybe I'm getting something wrong here.
When I send the syx file with MIOS studio, the patch will end up overwriting an existing patch, since MIOS studio places them where they where on the original Midibox (my assumption) and there is no way to tell MIOS studio where to put the patch... or am I missing something? Tried to look it up in the manual but I can't find much information...

[Hawkeye]

Recommendation: use Rutger´s fantastic patch editor/librarian. It allows to load patches to (computer) memory, view them on screen and then send them to MBSID "buffer", meaning it is not stored on the bankstick and then save it where you want it, if you like it. You can also manage whole banks of patches. Great tool!

Bye,
Peter

This post has been edited by Hawkeye: 03 May 2012 - 21:07

[rumpelfilter]

you mean the CTRLR panel? so far I can't find any way to load a patch in there, at least not from a syx file. I have the version from the CTRLR website, dont' know if there's some unofficial builds

update: oh wait, you mean the java version... too bad I'm running OSX Lions, seems like it's not working with it...

I wonder why MIOS does not store the patch in the buffer when you send it a sysex message... would make more sense imho

This post has been edited by rumpelfilter: 03 May 2012 - 21:28

[TK.]

Yes, currently the Ctrlr panel can't be used as patch librarian, I'm waiting for an update as well.

Quote

I wonder why MIOS does not store the patch in the buffer when you send it a sysex message... would make more sense imho

Not true, the SysEx implementation of MBSID is *very* flexible! :-)

It's possible to send the patch either to a given bank and patch slot, or directly into the edit buffer (so that a patch won't be overwritten, resp. could be stored with the SAVE function from the CS)

This is documented here: http://svnmios.midib...lementation.txt
resp. in doc/mbsidv2_sysex_implementation.txt of the installation package that you downloaded.

Quick guide (if you don't want to work through this document):

The SysEx patch starts with:

Quote

F0 00 00 7E 4B <device-number> 02 00 <bank> <patch> <1024 bytes of dump data> <checksum> F7

You can change the bank and patch number directly in the SysEx header, it doesn't affect the checksum.

If you want to send the patch directly to the edit buffer (-> no BankStick overwrite), replace the "00" before <bank> by "08"

Quote

F0 00 00 7E 4B <device-number> 02 08 <bank> <patch> <1024 bytes of dump data> <checksum> F7

(<bank> and <patch> are ignored in this case)

Again, this change doesn't affect the checksum which make manual edits easy!

SysEx data can be loaded/modified/sent with the SysEx tool of MIOS Studio.

Once the promissed Ctrlr updates are also available for MacOS, I will continue on the panel (I'm also a Mac user...)

Best Regards, Thorsten.

[rumpelfilter]

Thanks a lot Thorsten for the detailed explanation! It is very flexible and handy indeed! That solves my problem!