Yamaha SY35 Voice Editor

Yamaha SY35 Voice Editor

SY35 Voice Editor – Standalone and VST Voice Editor for Yamaha SY35 and SY22 series synthesizers



SY35 Voice Editor only works with the Voice Mode of the synth, not with Multi Mode.


· Librarian
Load and save individual voices in .syx format.

Load and save voice soundbanks in .syx format.

Receive voices from the synth.

Send voices to the synth.

Drag&Drop patches between banks.

· Total Recall

SY35 Voice Editor lets you edit all voice parameters (even those hidden and not editable from the synth!!) and save the latest edit status within the application. This means that you can easily recall the latest status of the previous edit simply by opening SY35 Voice Editor.

· Graphic vector editing page.

Editing the vector path data of a voice has never been easier thanks to SY35 Voice Editor. Visualize Level and Detune paths in different ways, record paths with the mouse, invert, rotate, flip paths…

· Parameter Locking

Lock any section of the synthesizer sound engine. For instance, lock Element A Envelope and Element B Carrier section. When loading or receiving a new patch, the locked sections will not change. Do you like the Level vector path of a voice, or Element B Carrier section? Lock them and test any patch with those settings.

· Patch Randomizer

SY35 Voice Editor provides a Patch Randomizer similar to the one present on the synth. It can be used in conjunction with Parameter Locking section to select which groups of parameters will be randomized.

· Copy&Paste

SY35 Voice Editor let’s you copy&paste Elements and Envelopes.

· Instructions

The zip file below contains both stand-alone and VST plugin version for 32 and 64 bit Windows systems, as well as a short manual.


DOWNLOAD (Windows only)

Downloads: 741

10 thoughts on “Yamaha SY35 Voice Editor”

  1. why dont you upload this panel in .panelz format so it can be used on ALL platforms? whats the idea behind windows only? CTRLR is not “windows only”! cheers from berlin. f.

  2. I had bad experiences in the past uploading panels this way. As I only have Windows, I can’t test for myself the panels on OSX or Linux, and even less give support to those platforms. This leads to erroneous opinions about Ctrlr, the editors, and countless hours trying to solve platform issues out of my reach. This is the reason for “windows only” editors. Also, bear in mind that the editors I’ve published where made for my needs, and once done I don’t mind to share them, but as I’m not making money with them, I don’t need to complicate my life with things not under my control. If I had a Mac, things will be different, but that’s not the case.

    About .panelz format. I’ve been cheated by some user who got my code to later make money of it. This will not happen anymore, I will not share my panels again in open format. Also, both the users and me avoid troubles related to the setup of a panel with .panelz format (Ctrlr versions, mess with .overrides file for parameter automation…).

  3. think about this for a second … you are using a platform that somebody built for sharing midi interfaces across all platforms but you dont want to share your work?

    that makes no sense whatsoever even if you have personal reasons for it. there is another JV interface in this list, i assume you used that to make yours?

    just saying …

  4. I’m not sharing my work? I’ve uploaded 6 editors to this site for free, and you say I don’t want to share my work? C’mon. Where’s your work? Where are your panels? Are you of those who share panels, or of those who just download other’s panels?

    Why don’t you ask at those who are selling panels (totally valid as Ctrlr allow it, by the way) using a free platform to share their work? Where can I see your criticism to them? Ctrlr allows selling panels as much as sharing restricted instances or .panels.

    And btw, you should be better informed before assuming too much. The first JV interface published in this site was my XP30 panel, maybe two or three years before the one I think you talk about (Jay-V panel).

  5. Thanks a lot again. You make great panels. About the open\closed panel discussion. I am glad for anything that is shared. When using closed panels however, my DAW doesn’t seem to find the standard Ctrlr vst anymore. When I erase them temporarily, it is back in the list. This seems like a bug in ctrlr or the DAW. I use an old Cubase and haven’t tested on other platforms yet.
    But thanks. Really. I use your MC505 editor all the time.

  6. Nice Panel, thank you very much!
    The only thing missing for me is draggable envelope points, but I assume Ctrlr does not support that out of the box yet…

  7. Thank you for the great work!
    I have 2 questions:
    Is there a way to play the sounds in the editor while making a pach?

    How do I send a patch to my synth?
    Receiving a pach from the synth to the editor works fine.
    I have the midi parameters as you described in the manual.
    Should I set the synth to a certain bank?
    Using the stand alone 64bit version.
    According to midiox receiving data from the synth works.

    thank you

  8. Hi Timminator, thanks for your words!!

    No, you can’t play sounds from the Editor, you will need to generate externally (from the synth, a midi controller or inside a DAW).

    For the second question, there’s a “SEND” button to send the current patch to the synth. It’s not working?

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Do NOT follow this link or you will be banned from the site!