Hi everyone.
Lately i started working with a good old synth rack, the crumar bit 01.
I found out that there is third party support for cc implementation with hardware firmware update, but i also realised that there is some kind of sysex implementation too.
The bit 99 ( the same synth with a keyboard) manual is quite clear, but for an inexperienced sysex user like me, not so.
So i’m asking you experts, if by following the data from pages 30 - 34 of the manual, i am correct to assume that for a setting of 10 on the LFO 1 depth parameter, the appropriate sysex message is :
F0 25 01 01 02 11 00 10 F7
Where am i wrong? Where am i right?
F0 is used as start of message ,
25 as manufacturer nr,
01 as model nr,
01 as device nr,
02 as parameter byte,
11 as parameter command,
00 as lsb,
10 as msb,
F7 as end of message.
If you have the time to check the related manual’s pages please advice. Any further advice is more than welcome.
Thanks in advance
Lately i started working with a good old synth rack, the crumar bit 01.
I found out that there is third party support for cc implementation with hardware firmware update, but i also realised that there is some kind of sysex implementation too.
The bit 99 ( the same synth with a keyboard) manual is quite clear, but for an inexperienced sysex user like me, not so.
So i’m asking you experts, if by following the data from pages 30 - 34 of the manual, i am correct to assume that for a setting of 10 on the LFO 1 depth parameter, the appropriate sysex message is :
F0 25 01 01 02 11 00 10 F7
Where am i wrong? Where am i right?
F0 is used as start of message ,
25 as manufacturer nr,
01 as model nr,
01 as device nr,
02 as parameter byte,
11 as parameter command,
00 as lsb,
10 as msb,
F7 as end of message.
If you have the time to check the related manual’s pages please advice. Any further advice is more than welcome.
Thanks in advance
Ted
set the type of the post as
Admin Post — 2 months ago
Looking over the System Exclusive section of the manual, it looks like the only way to change the LFO1 Depth via MIDI is to send a complete Program Dump into the Bit 01. The System Exclusive message would look like this:
The Bit 01 has no MIDI OUT port. So if you only want to change the LFO1 Depth, you would have to manually determine the existing values of all the other parameters in a program dump by calling up the various parameter values on the front panel controls then calculating the correct hex values to use in the program dump. (Alternatively, perhaps you might explore if it is possible to decode the audio tone format used to save data to tape?)
As you can see, this is probably not going to be useful for changing an individual parameter via MIDI.
F0 25 1n 07 pp 0_ 0_ 0y 0x 0_ 0_ 0_ 0_ 0_ 0_ 0_
0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_
0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_
0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_
0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ F7
n is for the MIDI channel number (hex 0 to F for MIDI channel 1 to 16).
pp is for the program number (hex 00 to 4A for program 1 to 75).
xy is for the LFO1 Depth (hex 00 to FF in steps of 4 -- in other words it can be 00, 04, 08, 0C, 10, 14, 18, 1C, ..., F0, F4, F8, or FC).
the _ spots are for all the other parameters in the program (see the "Program Bit Map" table).The Bit 01 has no MIDI OUT port. So if you only want to change the LFO1 Depth, you would have to manually determine the existing values of all the other parameters in a program dump by calling up the various parameter values on the front panel controls then calculating the correct hex values to use in the program dump. (Alternatively, perhaps you might explore if it is possible to decode the audio tone format used to save data to tape?)
As you can see, this is probably not going to be useful for changing an individual parameter via MIDI.
- Page :
- 1
There are no replies made for this post yet.
