any max/msp people out there using a Yamaha TX81z?

I suspect someone made an editor librarian for this years ago in max (ie version 2) DZ would probably know.
but there is this-- don't know if it's possible to integrate with max but I assume it would be:
http://www.jsynthlib.org/

It's not as hard as you think. You just have to read the manual and do a bit of head scratching. It says what it starts and ends with and then the variable numbers in between. Each 8 bit number is represented as a 3 digital number so instead of XXXX XXXX you get 256 or the decimal representation of the 8 binary bits. If you look at the first and last numbers of the TX81z sysex requirements the rest becomes pretty easy.

I got the TX81z a few days ago and I was thinking the same myself (that sysex is hard) but I had a look and a bit of fiddle and it wrecked my head for a bit but then was pretty obvious. Just look at the first and last numbers and I think there is a sxformat object example with a typical Yamaha DX sysex so it starts to make more sense.

Not a patch I am afraid. I found I couldn't do it in Ableton (as it filters sysex) and have not gone back yet.

ive got some of the numbers correct for the sxformat object (from the manual - but i cant decipher all of what i need), but im afraid something is not right or im missing something, because when i try to change a parameter or value, nothing happens on the TX81z. i feel like im stuck. if you have something thats working with the sxformat object, let me know what the number string is...thanks!

unfortunately it is always a bit difficutl to convert hexadecimal to something else,
because you cant write it in max.

or does anybody eventually build a converter using textfield and sprint?

one could also make a simple document using a resource editor such as
resorcerer. you´d type the desired bytes from the hardware manual into
a hex editor, save it to disk, and read it into maxmsp using [filein] ... and voila,
decimal representation.

edit: or cant [capture x] dump out content?

Um, you can write hex in Max. Just prefix a number with "0x", e.g. "0x10" in a message box is converted to "16" as soon as you've finished editing.

I've been controlling a TX81Z with SysEx for ages, just with a bunch of [pak] objects, one for each parameter.

Hint: the TX81Z manual has OP2 and OP3 reversed.

P.S. The bit order for operator on/off is reversed too.

P.P.S. The TX81Z has a feeble MIDI buffer - it gets full pretty quick. Stick a [speedlim 50] between your GUI control and the [pak] (or whatever you're using to mash the value into a valid sysex message) to lighten the load.

The TX sounds absolutely awesome and glitchy when you mangle these params live... loads of brilliant stepping and spazzing. It's one of the dirtiest FM synths I've ever used.

@asterisk:

After re-reading this thread I realise this probably wasn't all that much help to you yet. I don't have Max on this machine, but here's an example to get you started...

For VCED parameters:

pseudopatch:
                              [number]
                               |
                              [speedlim 50]
                               |
[pak 0xf0 0x43 0x10* 18 param* i 0xf7]
                               |
                              [midiout]

* 0x10 assuming your TX81Z is set to MIDI Channel 1. For MIDI Channel 2, substitute 0x11. For MIDI Channel 16, substitute 0x1f, etc. etc.

* Stick the desired parameter number from the TX81Z manual here.

For ACED parameters:

pseudopatch:
                              [number]
                               |
                              [speedlim 50]
                               |
[pak 0xf0 0x43 0x10* 19 param* i 0xf7]
                               |
                              [midiout]

* 0x10 assuming your TX81Z is set to MIDI Channel 1. For MIDI Channel 2, substitute 0x11. For MIDI Channel 16, substitute 0x1f, etc. etc.

* Stick the desired parameter number from the TX81Z manual here.

I would post my TX editor, but it's got a lot more sysex trickery in there that would only serve to confuse. Plus I spent hours on it! ;)

@christripledot

I'd be real grateful if you would take a moment to explain the function/meaning of the remaining hex values in this list - I'm comtemplating hacking into my DX9 synth via Max, and have no sysex skills.

thanks
Brendan

Hey Brendan! No problem:

• 0xf0 is always the first byte of a SysEx message. It means "Here comes some SysEx".

• 0x43 is Yamaha's manufacturer ID number.

• 0x1n is the basic MIDI receive channel for your device what you want to SysEx, innit. I'm assuming you can count in hex... for MIDI ch. 1, use 0x10. For MIDI ch. 16, use 0x1f.

• After that there is a number that specifies the parameter group. (On my TX81Z a single patch has its editable parameters lumped into two categories. This just tells the TX what category it's about to mess with.) I'm not sure if any of Yamaha's other FM synths work this way, but the relevant manuals should provide some illumination.

• Next up is the parameter number itself (see your TX/DX manual for this).

• Then comes the parameter value.

• Finally, 0xf7 means "End of SysEx".

I highly recommend fucking up your Yamaha with SysEx. Pattr interpolation is asking a bit much - my TX chokes on all the MIDI data, but I've had some success by restricting the interpolation to envelopes, operator volumes, and lfo depth/speed. Some smooth morphing is possible, with care, but I find it infinitely more pleasing to just blast it with horrible quantised stepped data... crusty FM zipper noise madness!

HTH!