Yamaha TG33, SY22, and SY35
Single Patch Editor
This patch editor ought to work properly with all three synthesizers, but it has only been tested on the TG33. Please let me know of any discrepancies you discover.
Communicating with Edisyn
Set your synthesizer to receive and transmit on the same MIDI channel (perhaps Channel 1). Turn on Program Change and System Exclusive data. Turn off memory protect. The TG-33 also has a "device number": ideally this should be set to the same as the MIDI channel. You set both the device number and MIDI channel in Edisyn when connecting to the synthesizer via the Change MIDI menu.
Selecting the Synthesizer Type
Your choice of Synth Type in the Global panel will determine the waves available in Tones A and C (the SY35 is different), and will also determine the kind of sysex message used to send patches to the synthesizer (the TG33 is different). You need to make sure you have sent the Synth Type appropriately both prior to editing and prior to sending patches to your synth.
About the TG33 Menu
This menu has two additional options for you. Send Patch as Pseudo-MPE will prepare a Multimode patch for the TG33 (not the SY22 or SY35) which references this patch, both in current working memory. The Multimode patch will reference it in every single channel, which makes it easy to use MPE devices to play the patch. Note that you'll need to first put the unit into Multi mode manually (see "Gotchas" below). The name of the multimode patch will be the same as that currently in the single-mode patch editor. Receive Vector Data Only will only update Edisyn in response to vector data, not any other data. Thus if you load a file or if Edisyn receives a patch from the TG33/SY22/SY35, only the vector data portion will be updated. This might be useful for editing the vector on the synth manually, then loading it.
Gotchas
- Edisyn cannot write patches to patch memory locations: you can only send them to the current working memory. From there, you will have to manually save them to an appropriate memory location if you like.
- If the SY22 or SY35 (not TG33) is in Edit mode, you cannot change patches. Thus in order to request a patch or to build an MPE patch, you must first manually exit Edit mode (just press the Voice button). The TG33 has a workaround for this bug: but the workaround will likely not help the SY22 or SY35.
- The TG33, SY22, and SY35 are odd machines: they have many more parameters than are available from the front panel. Notably, all of them allow you to program both the carrier and modulator parameters of the FM tones, as well as the FM algorithm in question. So you will find rather more options here than expected.
- Only the TG33 can receive real-time parameter changes; and nearly all Modulator parameters and a few others cannot be sent. Furthermore, the TG33 is very slow in responding to real-time parameter changes.
- A number of parameters range from 0...99 on-screen, but in reality they range from 0...127 or 0...64 and are just mapped to 0...99. Edisyn uses the true mapping values; this means that when you change a number, it may not be the same on Edisyn as it says on the synth.
- The TG33 may occasionally get caught in a strange "Cannot Edit" warning message on-screen when receiving real-time parameter changes. You can get it out of this by selecting the voice and edit buttons again, or some similar combination.
Thanks
Thanks to Rich Hanson who allowed me to use some of his original source code to extract parameter values.
Thanks also to Ben Noble (bnoble@gmail.com) for his considerable assistance in debugging.
Thanks to Carlo Bandini (carlobandini@gmail.com) for finding and helping to fix bugs in the SY22/SY35 patch code.
By
| Sean Luke
|
Date
| January 2020
|