Moog Subsequent 37 system exclusive dokumentation

Everything Sub.
Post Reply
Electrolove
Posts: 1
Joined: Fri Nov 24, 2023 6:32 am

Moog Subsequent 37 system exclusive dokumentation

Post by Electrolove » Fri Nov 24, 2023 6:41 am

I have a home studio with a lot of synths. Among other things, a Moog Subsequent 37. I am a programmer by profession and am in the process of building an editor/librarian for all my synths. I've tried to get hold of the sysem exclusive documentation for Subsequent 37 but can't find it anywhere. Can anyone help me or at least tell me how a sysex dump from Subsequent 37 is packed? For example, Sequential uses the following method.

The data for DSI parameters is split into eight-byte packets. The first byte in each packet contains the high-bit values for the next seven parameters. The second through eighth bytes contain the low seven bits of these parameters. Let's say that a DSI synthesizer has data for the following parameters (note: this does not represent a real synth, it's just to illustrate how data is packed):

Parameter #1 - Attack: 0
Parameter #2 - Decay: 200
Parameter #3 - Sustain: 220
Parameter #4 - Release: 80
Parameter #5 - Waveform: 1 (where 1 represents a square wave)
Parameter #6 - Cutoff Freq: 170
Parameter #7 - Resonance: 32

These values can be represented in binary. So:

Attack = 0000 0000
Decay = 1100 1000
Sustain = 1101 1100
Release = 0101 0000
Waveform = 0000 0001
Cutoff = 1010 1010
Resonance = 0010 0000

Note how several of the parameters (Decay, Sustain, Cutoff) have their high bits set. If these were sent as-is via SysEx, those would be interpreted as command status bytes, and the dump wouldn't work. So, we take the high bit of each parameter in order, and put it into a seven-bit data byte, starting with bit 0.

0100110
^ High bit for Attack (bit 0)
^ High bit for Decay (bit 1)
^ High bit for Sustain (bit 2), etc...


And we send that as the first data byte in the packet. Then, we send the seven parameters with the lowest seven bits, starting with Attack:

0010 0110 (high bits in pack byte)
0000 0000 (Attack)
0100 1000 (Decay)
0101 1100 (Sustain)
0101 0000 (Release)
0000 0001 (Waveform)
0010 1010 (Cutoff)
0010 0000 (Resonance)

That's packed data. Repeat for the next set of seven parameters until you're done. The last packet probably won't contain exactly seven parameters. That's okay, though, you just put 0 in unused places in the pack byte.

How do Subsequent 37 packs data?

timtaylor
Posts: 1
Joined: Wed Dec 27, 2023 5:02 am

Re: Moog Subsequent 37 system exclusive dokumentation

Post by timtaylor » Wed Dec 27, 2023 5:06 am

I’m sorry, but I also couldn’t find the system exclusive documentation for the Moog Subsequent 37. So hard to find it.

Post Reply