has anyone experience with the Behringer B Nano or BCR2000 to use it as a preset bank for the Casio CZ5000. As far as I read Casios style is a bit more complicated than the other common sysex use. The Caios CZ5000 is limitated in User presets, I use Virtual CZ to send Souds to the Casio, works fine so far, but I can't store them on the Behriger B-Nano or BCR2000, to send them to the Casio without the use of a PC.
I've taken a quick look at a scanned version of the CZ-5000's Operation Manual. Unfortunately some of the tables are almost unreadable, and I couldn't find an explicit description of the CZ-5000's System Exclusive format, but maybe I've missed it.
In any case, a BCR2000 button or encoder can send up to 125 bytes via what BC Manager calls "custom output". (See section 14.6.6 of BC MIDI Implementation.pdf for further details.) BC Manager makes it pretty easy to create such "custom" button/encoder definitions.
So the big question is: how long are the CZ-5000's preset SysEx messages? If they are 125 bytes or less, it should be possible to send them to a CZ-5000 from a BCR2000.
You can forget about the BCN44: the maximum number of "custom" bytes a BCN44 button or encoder can send is 11.
Hope this helps,
txnks for info, the preset sound sysex for the casio cz5000 i have here generated is 5 kb, so it should fit to the bcn44 as well, right? Regarding the bcr2000, I have send from the Roland Aplpha Juno editor sysex soundpresets to the bcr2000, stored them there, and later send them without PC to the Alpha Juno, which works without any problem. With the same set up, the bcr didn't catch any Casio CZ sysex I sent from the Virtual CZ Editor to the BCR2000. Obviously there may be somethibng different. When I sent sysex from the Vitual CZ directly to the CZ5000, it works fine.
I assume you mean that all the CZ-5000 presets together take up 5000 bytes.
But how many bytes does a single preset take up?
As I wrote in my previous reply, a BCN44 button or encoder can send a maximum of 11 bytes. That's bytes, not kilobytes. So unless a single CZ-5000 preset only requires a SysEx message of 11 bytes or less, you can't put a CZ-5000 preset definition in a BCN44 button/encoder.
A BCR2000 button/encoder only has room for 125 bytes. So if the SysEx message for a single CZ-5000 preset contains more than 125 bytes, it can't be stored in BCR2000 button/encoder. Presumably a preset for the Alpha Juno consists of 125 or fewer bytes; that might explain the difference.
ah. I messed with kb and bytes, so 1 CZ preset is 5 kb! then it seems too much for the bcr. Do you have an idea/recommendation which low budget hardware will be suitable as a preset sysex shooter bank for the CZ without use of a PC?
I've always thought that the 125 bytes per preset/button/encoder/fader of the BCF/BCR2000 were pretty generous, particularly in such low-budget devices.
Fully customizable SysEx space is a bit of a "luxury", so I doubt whether there are any low-budget hardware MIDI devices supporting "really long" SysEx messages. (Are there even any "high-budget" devices supporting this?)
But in principle it should be possible to send really long SysEx messages from a Raspberry Pi. Strictly speaking the Raspberry Pi is a kind of "mini-PC", but it's small and relatively cheap, and there is a MIDI sound card/interface available for it. So it might be worth while looking into the Raspberry Pi.