Does anyone know what the correct sysex is for a patch dump request on the nord lead 2x?
The manual says that to get the slot A edit buffer, it's this: [ 240 51 15 4 10 0 247 ] (ie, msg type is 10 for edit buffer, msg value is 0 for slot A). But this does nothing -- the screen briefly changes to 1, but no output.
After some experiments, this gets the closest: [ 240 51 15 4 10 0 247 ] (ie msg type is 14, not 10). This works for patches, just about, but not percussion kits.
Some details if anyone is interested. Let's say there are patches in slots A and B, and a percussion kit in slot C, and dump request is made as above. Then:
Slot A active, request dump of A or B -> works as expected
Slot A active, request dump of C -> returns an empty patch (ie length 137, so not a percussion kit): [ 240 51 15 4 0 2 0 0 ... 0 247 ]
Slot C active, request anything -> returns a percussion kit patch (ie length 1061), but not the edit buffer, seems to be a saved patch
Nord Lead 2X patch dump request sysex
-
saxwell
- Posts: 5
- Joined: 10 Sep 2021, 09:07
- 3
- Your Nord Gear #1: Nord Drum 2
- Your Nord Gear #2: Nord Modular
- Been thanked: 1 time
Re: Nord Lead 2X patch dump request sysex
If anyone is interested, here is one way to get and set the edit buffer data with sysex on the nord lead 2x.
Getting patches and percussion kits:
When requesting a patch, make sure that the active slot on the synth is also a patch. Doesn't have to be the slot that you're requesting, just has to be a patch slot. Similarly, when requesting a percussion kit, make sure that the active slot is also a percussion kit. If you don't do this, the request will return a sysex message with empty data, ie all zeroes.
Then, the request message format is this: [ 240 51 <global midi chan> 4 14 <slot num> 247 ]. The global midi channel should be in the range 0-15, and the slot number should be 0-3. Note the manual says that the msg type byte should be 10, not 14, but this is wrong.
The response from the synth looks like this: [ 240 51 <global midi chan> 4 0 <slot num> ... <data> ... 247 ]. For patches, the slot number should be in the range 0-3, the same as the request. But for percussion kits it's 16-19.
Setting patches and percussion kits:
To set the contents of the edit buffer, the message format is the same as the response above: [ 240 51 <global midi chan> 4 0 <slot num> ... <data> ... 247 ], where the destination slot number should be in the range 0-3 or 16-19 depending on whether you're setting a patch or percussion kit.
Getting patches and percussion kits:
When requesting a patch, make sure that the active slot on the synth is also a patch. Doesn't have to be the slot that you're requesting, just has to be a patch slot. Similarly, when requesting a percussion kit, make sure that the active slot is also a percussion kit. If you don't do this, the request will return a sysex message with empty data, ie all zeroes.
Then, the request message format is this: [ 240 51 <global midi chan> 4 14 <slot num> 247 ]. The global midi channel should be in the range 0-15, and the slot number should be 0-3. Note the manual says that the msg type byte should be 10, not 14, but this is wrong.
The response from the synth looks like this: [ 240 51 <global midi chan> 4 0 <slot num> ... <data> ... 247 ]. For patches, the slot number should be in the range 0-3, the same as the request. But for percussion kits it's 16-19.
Setting patches and percussion kits:
To set the contents of the edit buffer, the message format is the same as the response above: [ 240 51 <global midi chan> 4 0 <slot num> ... <data> ... 247 ], where the destination slot number should be in the range 0-3 or 16-19 depending on whether you're setting a patch or percussion kit.