sysex to individual TGs

[josbouten]

I’ve been reading the MiniDexed topics (all of them) but do not seem to find an answer to my question. And this question is sort of asked before, but the answers or discussion resulting from it is just not clear to me.

I’ve found that the DX7 accepts sysex messages to e.g. set a value of an OP’s EG [1-4] levels or rates. When I try this,, this works for TG1 on my MiniDexed. That is probably because sysex messages do not have a channel number in them and by default the sysex is routed to TG1. However, I like to be able to do this with all TGs. So I would want to be able to e.g. set the EG rate 4 of OP1 for TG2. This implies that a sysex message must be send that contains the TG number in some way which is then to be relayed to TG2 in stead of TG1. As I said I've read some posts about it, but it is not clear to me whether this is currently supported and/or whether this works and/or how to use it.

Furthermore, I read on the forum that MiniDexed should send sysex message to midi out whenever you change one of these parameters. So I thought maybe I can record one and study it. That then should contain some reference to the TG-number, I think. I’ve checked the midi out, but mine does not do this (I've tried this with channel set to 1 and to OMNI). Same questions here: is this currently implemented and should this be working?

I’m contemplating to expand the Sysex implementation or expand the CC handling of my version of MiniDexed, but I’d rather not if it is already in the device (and simply not clear to me how to use those functions).

[BobanSpasic]

DX7 SysEx messages do contain the MIDI channel. It is the lower part of the second byte sent.

[josbouten]

For OP1, EG Range 1 as per the yamaha manual I'm now sending something like this: F0 43 10 00 69 •• F7 where the dots are the value for the rate. This works for OP1 of TG1. If I rewrite the 2nd byte as a binary number then 0x43 becomes 0b0100 0011. So what do you suggest I change this into to change the value for TG2 ?

[BobanSpasic]

Sorry, I forgot about the F0. It is the 3rd byte. Take a look here:
https://github.com/BobanSpasic/MDX_Tool/wiki/01---SysEx

[josbouten]

Ok, thx. I'll give this a try, and will report back.

[josbouten]

I got it to work. Thx !

I have an additional question. In the sysex implementation of the DX7 as described by Yamaha (see extract below) what do the 'Key' and 'Key Strings' in the 4th and 5th column signify?

[BobanSpasic]

Hi. The "Functions" from the DX7 are not implemented. In MiniDexed are these functions part of Performance, which isn't DX7-compatible. Jos Bouten ***@***.***> schrieb am Mi., 19. Feb. 2025, 14:09:

…

I got it to work. Thx ! I have an additional question. In the sysex implementation of the DX7 as described by Yamaha (see extract below) what do the 'Key' and 'Key Strings' in the 4th and 5th column signify? sysex.png (view on web) <https://github.com/user-attachments/assets/fa269b14-7a4b-4ecd-81ca-4463e1058733> — Reply to this email directly, view it on GitHub <#814 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQIHLBSUD3AHPID27WDTXX32QR673AVCNFSM6AAAAABXJOEDWOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMRUHE4DKNQ> . You are receiving this because you commented.Message ID: ***@***.***>

[diyelectromusic]

Yes, whist SysEx doesn't strictly have a channel, it has a device number (see below) we interpret it as channel rather than TG number, which might have been another way to interpret it. Alternatively we could have made it configurable via performance.ini/minidexed.ini. See https://github.com/probonopd/MiniDexed/blob/main/src/mididevice.cpp#L320

Kevin