Sysex

[sawan]

Hi, I’m trying to take the sysex data I’m getting from midiox so I can put it into my ATC-1 panel.

I’m a n00b when it comes to sysex and ctrlr so please bare with me ” title=”Very Happy” />

First thing that’s throwing me is when I try to monitor myself moving the knob on the ATC to change lfo 1’s target, midiox doesn’t detect anything. But if I monitor the output of midiquest doing the same thing I get 4 different event types and 4 long sysex strings. I’ve attached a screenshot of the reading I get when sequentially cycling through 4 of the targets in the list.

Midiquest works fine with the ATC, so I’m guessing that the ATC not sending anything out for this doesn’t really matter anyway.

So my actual problem is translating the midiox monitor data into data I can use in ctrlr. Can anyone explain hpw to do this? Or point me in the direction of somewhere where I can learn?

Thanks

[Filch]

The first 3 lines of code are CC and Program Change messages for patch selection.
The meat you’re looking to get is the white sysex code. I can see that the 17th byte in that sysex screen is incrementing by one. I’m guessing that’s you turning the knob up by 1 each time.

Why midiquest blasts out the bank/program number for each knob change I don’t know. What you need to get is the midi/sysex documentation for that synth. Without that, you’d be spending countless hours trying to guess what each byte represents in this sysex string.

[atom]

also what are you trying to do exactly in ctrlr, are you creating a panel for editing and trying to add program dump, or are you just creating a panel for editing for now. In the second case i’m sure that ATC has some CC based MIDI implementation for it’s controls (but i maybe wrong), in that case find the manual and look at the midi implementation. If there is CC based implementation then you need to decode that sysex dump (but the manual should tell you how to do it)

If you have no idea what i’m talking about, show us the manual, we’ll try to help.

[Filch]

Found this while hunting around :
viewtopic.php?f=26&t=139

[sawan]

I’d just like an editor for now. I actually posted the cc list in the thread Filch linked. There are plenty of things I can control already. It’s more stuff like lfo targets and a few other things which can only be done with sysex that I’m trying to figure out.

"Filch":1yp3q5s1 wrote:

I’m guessing that’s you turning the knob up by 1 each time.[/quote:1yp3q5s1]

Correct ” title=”Smile” />

Would it be possible for ctrlr to have some kind of learn function? i.e. Select a control in ctrlr, and with the correct midi in port selected, tweak the control on the synth to assign it. (maybe even sounddiver/midiquest routed in with midiyoke?)

Could it be possible for ctrlr to decode sysex?

[netchose]

except sysex dump i think S-E synth doesn’t work with sysxex.
i will be very difficult to have a sysex dump documentation.

CTRLR hasn’t midi learn function, but it is very easy to enter value yourself

[sawan]

The ATC definitely uses sysex for certain parameters. That’s the reason Midiquest is able to control the things you can’t access with ccs.

[netchose]

i had the se1x and use midiquest : it send dump for each change it is why i said that .

[Filch]

Yes, midiquest appears to send an entire program parameter dump for each individual parameter change, instead of just directly change the parameter in question. Why midiquest does this, I’m not sure. Perhaps there is no direct sysex string to parameter change for this synth and the only way to send those changes is via a program dump.

Again, the only way to know is to get the sysex doc for this synth. We can guess all day.

You may want to see if there is a midi menu setting on the ATC to turn on or enable controller messages to be sent when making a knob/button change. Many synths have the option to have this on or off. If it does, we could see what the string is for each parameter.

[Author]

Posts