Troubleshooting
Roland JX-10 sysex problems!!
Started by rutgerv on .
Sign in or create an account to join the conversation.
Hi there,
I'm trying to build a virtual PG800 programmer for the Lemur. I've already successfully managed to do so in Logic Pro's environment, but as a Lemur newby, I'm having a bit of trouble right now.
For example, the sysex massage for the filter frequency is:
F0 41 36 00 24 20 01 22 xx xx F7
(xx = variables, 0 to 100)
The sysex strings I tried are:
{0x41, 0x36, 0x00, 0x24, 0x20, 0x01, 0x22, 0x00, x*100}
or
{0x41, 0x36, 0x00, 0x24, 0x20, 0x01, 0x22, 0x00, 100*Fader.x}
When comparing both sysex messages from the Logic environment an the Lemur in MIDI Monitor, they're identical (although the Lemur spits out extra 2 bit messages) except the first group of variables, in Lemur it stays 00, in Logic it varies.
Does anybody know what I'm doing wrong?
Cheers,
Rutger
I'm trying to build a virtual PG800 programmer for the Lemur. I've already successfully managed to do so in Logic Pro's environment, but as a Lemur newby, I'm having a bit of trouble right now.
For example, the sysex massage for the filter frequency is:
F0 41 36 00 24 20 01 22 xx xx F7
(xx = variables, 0 to 100)
The sysex strings I tried are:
{0x41, 0x36, 0x00, 0x24, 0x20, 0x01, 0x22, 0x00, x*100}
or
{0x41, 0x36, 0x00, 0x24, 0x20, 0x01, 0x22, 0x00, 100*Fader.x}
When comparing both sysex messages from the Logic environment an the Lemur in MIDI Monitor, they're identical (although the Lemur spits out extra 2 bit messages) except the first group of variables, in Lemur it stays 00, in Logic it varies.
Does anybody know what I'm doing wrong?
Cheers,
Rutger
Hi
Would really need to see the sysex implementation info
It may be using a 2byte format similar to 14bit midi msgs
Have a look and see how those 2 values are changing ...
Check the syses info to see if the package data in some particular way . .
Cheers
Would really need to see the sysex implementation info
It may be using a 2byte format similar to 14bit midi msgs
Have a look and see how those 2 values are changing ...
Check the syses info to see if the package data in some particular way . .
Cheers
Thanx Macciza,
Attached the sysex implementation of the JX-10.
I'll check on the 14bit messages....
Cheers,
Rutger
JX-10 sysex.jpg
Attached the sysex implementation of the JX-10.
I'll check on the 14bit messages....
Cheers,
Rutger
JX-10 sysex.jpg
I'm sorry, the sysex list above is an earlier version. I'm using version 2.3, rewritten by Colin Fraser which actually works.
There's only 1 group for value, instead of two and no checksum. See attachment
JX10 sysex 2.3.jpg
There's only 1 group for value, instead of two and no checksum. See attachment
JX10 sysex 2.3.jpg
Hi
Yeah well the first bit was really just the MIDI implementation not Sysex.
But the nibble-ised system for storing Data to cartridge was one possibility given your earlier info, though in the end it isn't..
The stuff you just posted is whats needed - and looking at that it is only one byte of data XX, not XX, XX as you previously thought
So try {0x41, 0x36, 0x00, 0x24, 0x20, 0x01, 0x22, Fader.x * 100} in either a CustomMIDI or script your own MIDI out
Strange though that they aren't using checksums though they do for RQF, DAT and ACK messages
Often they aren't critical anyway - though if the above message does not work, then try adding an extra 0 at the end (for the checksum)
Cheers
MM
Yeah well the first bit was really just the MIDI implementation not Sysex.
But the nibble-ised system for storing Data to cartridge was one possibility given your earlier info, though in the end it isn't..
The stuff you just posted is whats needed - and looking at that it is only one byte of data XX, not XX, XX as you previously thought
So try {0x41, 0x36, 0x00, 0x24, 0x20, 0x01, 0x22, Fader.x * 100} in either a CustomMIDI or script your own MIDI out
Strange though that they aren't using checksums though they do for RQF, DAT and ACK messages
Often they aren't critical anyway - though if the above message does not work, then try adding an extra 0 at the end (for the checksum)
Cheers
MM
Hi MM,
Thanx!!! Unfortunately it doesn't react to that string (checksum 0 didn't do the trick either).
I checked the sysex output from the JX-10 environment in Logic and it does seem to use 14 bit:
00 00 is 0 (F0 41 36 00 24 20 01 22 00 00 F7 )
7F 01 is max (F0 41 36 00 24 20 01 22 7F 01 F7 )
It seems that Logic automatically creates a 14 bit output, it uses the same sysex string (10 bytes) but outputs 11 bytes....
Any ideas how to do that trick in Lemur:-)
Cheers,
Rutger
Thanx!!! Unfortunately it doesn't react to that string (checksum 0 didn't do the trick either).
I checked the sysex output from the JX-10 environment in Logic and it does seem to use 14 bit:
00 00 is 0 (F0 41 36 00 24 20 01 22 00 00 F7 )
7F 01 is max (F0 41 36 00 24 20 01 22 7F 01 F7 )
It seems that Logic automatically creates a 14 bit output, it uses the same sysex string (10 bytes) but outputs 11 bytes....
Any ideas how to do that trick in Lemur:-)
Cheers,
Rutger
Hi
I'd say they are adding a checksum, but would need to see more values to be sure
The data and checksum should add up to 0 in 7bit format
Cheers
MM
I'd say they are adding a checksum, but would need to see more values to be sure
The data and checksum should add up to 0 in 7bit format
Cheers
MM
Hi MM,
I think you're right!
Here's some more data:
00 F0 41 36 00 24 20 01 22 01 7F F7
00 F0 41 36 00 24 20 01 22 02 7E F7
00 F0 41 36 00 24 20 01 22 03 7D F7
00 F0 41 36 00 24 20 01 22 0A 76 F7
00 F0 41 36 00 24 20 01 22 0D 73 F7
00 F0 41 36 00 24 20 01 22 0F 71 F7
00 F0 41 36 00 24 20 01 22 12 6E F7
00 F0 41 36 00 24 20 01 22 15 6B F7
00 F0 41 36 00 24 20 01 22 17 69 F7
00 F0 41 36 00 24 20 01 22 1A 66 F7
00 F0 41 36 00 24 20 01 22 1D 63 F7
00 F0 41 36 00 24 20 01 22 59 27 F7
00 F0 41 36 00 24 20 01 22 5C 24 F7
00 F0 41 36 00 24 20 01 22 5F 21 F7
00 F0 41 36 00 24 20 01 22 61 1F F7
00 F0 41 36 00 24 20 01 22 64 1C F7
00 F0 41 36 00 24 20 01 22 67 19 F7
00 F0 41 36 00 24 20 01 22 69 17 F7
00 F0 41 36 00 24 20 01 22 6C 14 F7
00 F0 41 36 00 24 20 01 22 6F 11 F7
00 F0 41 36 00 24 20 01 22 71 0F F7
00 F0 41 36 00 24 20 01 22 74 0C F7
00 F0 41 36 00 24 20 01 22 77 09 F7
00 F0 41 36 00 24 20 01 22 79 07 F7
00 F0 41 36 00 24 20 01 22 7C 04 F7
00 F0 41 36 00 24 20 01 22 7F 01 F7
This sysex command gives the same results (I'm using Fader2):
{0x41, 0x36, 0x00, 0x24, 0x20, 0x01, 0x22, Fader2.x * 127, 128-(Fader2.x * 127)}
But the JX-10 still doesn't see it. Maybe I'm doing something wrong with the settings?
Custom MIDI
object target: Midi 0
Target: Midi 0
Message: system exclusive
Trigger: Fader2.x (any)
data: see above (any)
MIDI CC data works just fine, so I think the basic MIDI settings should be fine.....
Cheers,
Rutger
I think you're right!
Here's some more data:
00 F0 41 36 00 24 20 01 22 01 7F F7
00 F0 41 36 00 24 20 01 22 02 7E F7
00 F0 41 36 00 24 20 01 22 03 7D F7
00 F0 41 36 00 24 20 01 22 0A 76 F7
00 F0 41 36 00 24 20 01 22 0D 73 F7
00 F0 41 36 00 24 20 01 22 0F 71 F7
00 F0 41 36 00 24 20 01 22 12 6E F7
00 F0 41 36 00 24 20 01 22 15 6B F7
00 F0 41 36 00 24 20 01 22 17 69 F7
00 F0 41 36 00 24 20 01 22 1A 66 F7
00 F0 41 36 00 24 20 01 22 1D 63 F7
00 F0 41 36 00 24 20 01 22 59 27 F7
00 F0 41 36 00 24 20 01 22 5C 24 F7
00 F0 41 36 00 24 20 01 22 5F 21 F7
00 F0 41 36 00 24 20 01 22 61 1F F7
00 F0 41 36 00 24 20 01 22 64 1C F7
00 F0 41 36 00 24 20 01 22 67 19 F7
00 F0 41 36 00 24 20 01 22 69 17 F7
00 F0 41 36 00 24 20 01 22 6C 14 F7
00 F0 41 36 00 24 20 01 22 6F 11 F7
00 F0 41 36 00 24 20 01 22 71 0F F7
00 F0 41 36 00 24 20 01 22 74 0C F7
00 F0 41 36 00 24 20 01 22 77 09 F7
00 F0 41 36 00 24 20 01 22 79 07 F7
00 F0 41 36 00 24 20 01 22 7C 04 F7
00 F0 41 36 00 24 20 01 22 7F 01 F7
This sysex command gives the same results (I'm using Fader2):
{0x41, 0x36, 0x00, 0x24, 0x20, 0x01, 0x22, Fader2.x * 127, 128-(Fader2.x * 127)}
But the JX-10 still doesn't see it. Maybe I'm doing something wrong with the settings?
Custom MIDI
object target: Midi 0
Target: Midi 0
Message: system exclusive
Trigger: Fader2.x (any)
data: see above (any)
MIDI CC data works just fine, so I think the basic MIDI settings should be fine.....
Cheers,
Rutger
Hmm
If the same message is sent to the same device it should give the same results . . . .
You have had the device respond to the syses message from Logic?
The same message sent from Lemur to same place should work!
How is Target 0 setup ? Try to set up a target that points straight to the device if possible.
If sending through Logic make sure it is passing the message on . .. .
HTH
MM
If the same message is sent to the same device it should give the same results . . . .
You have had the device respond to the syses message from Logic?
The same message sent from Lemur to same place should work!
How is Target 0 setup ? Try to set up a target that points straight to the device if possible.
If sending through Logic make sure it is passing the message on . .. .
HTH
MM