1. Doesn't the MOXF VST editor do the same thing?
2. Do the edits transfer to the VST editor? Because that's where I am calling up my voices now...I've been using the default mode - to save my voices.
3. Do I really need all these tools or just some?

Total Librarian / Voice Editor / Drum Kit Editor / Performance Editor /Mix Editor / Master Editor / Waveform Editor

I know this is the kind of question that everyone hates - because it is so generic. But some basic thoughts will help me!

But it's a fair question and one that deserves an in depth answer. The short answer is if you are interested in creating your own custom data for the MOXF, then the Melas tools are going to be indispensable.

The Yamaha MOXF6/MOXF8 Editor Standalone/VST is quite different from the Melas suite. And one does not replace the other, although there is an area of some overlap. You still will want access to both on occasion.

Yamaha MOXF6/MOXF8 Editor Standalone/VST
Its main unique function is that is a fully integrated VST3 software that allows you to return and process the audio from your MOXF in the DAW (Cubase). VST or Virtual Studio Technology, means MIDI tracks from the DAW are routed through the VST Editor to the MOXF hardware, instead of the audio going directly to the main audio outputs, the audio is *returned* to the DAW (via the Editor) to a place where you can then process it in the same way you process any soft synth. Not only is the MOXF your computer's audio and MIDI interface, the VST Editor allows you to integrate your external synth's audio into the computer environment where you can fully process the MOXF's signal!

The perceived advantage of so called 'soft synths' is that because they are generated on the same computer running the DAW, it is very easy to not only store everything, but you can process the audio of the soft synth within the same DAW computer environment. External devices were just external and could not participate in advanced functions like FREEZE, or EXPORT AUDIO MIXDOWN, or be processed by VST effect plug-ins, etc. The VST EDITOR gives your external MOXF all of these same advantages (and then some).... With the distinct advantage that hardware has its own stuff... you couldn't easily have the same processing capability with a virtual soft synth. The MOXF has its own CPU, its own processing muscle, you are simply adding all the muscle of your computer's CPU.

Here's an example of this: imagine a VSTi soft synth that is 16 Part multi-timbral. Now let's open a three band parametric EQ on each of its Parts... That's 48 bands of EQ ... Just opening that many would have your computer CPU spitting up blood... The MOXF is just idling with that... It has its own. They're available at all times. So in short, the fact that the MOXF6/MOXF8 Editor Standalone/VST is a VST editor allows for advanced MIDI and Audio routing, makes it an invaluable resource that you WILL still use, even if you get the Melas suite. Also the tight integration with the Cubase MediaBay/Sound Browser (where you have instant access to every Voice you collect for your MOXF) this makes it a compelling reason to invest time and effort to add this EDITOR VST to your workflow.

So what does the Melas suite afford you that the free Yamaha MOXF Editor doesn't?
Total Librarian, which is integrated with the Melas Voice Editor, Drum Editor, Performance Editor, Mix and Master Editors takes a close look at what would make managing your MOXF content easier. The Yamaha Editor has just VOICE mode (Voice = Voice and Drum) and SONG/PATTERN modes (Song/Pattern = Mix). The Melas suite includes a "Performance" mode Editor and a "Master" mode Editor. Why these are invaluable can be explained as follows:

A MOXF Performance can have 4 Parts. Each Part contains one Voice. What gets memorized in a Performance is the 4 Voice locations... Not the actual Voice data itself. Say you have a Performance from the EDM EXPANSION library that you like and you'd like to assemble it with a dozen Performances from half a dozen other libraries.
The EDM PERFORMANCE references the following locations:
User Drum: 001(A01)
User 2: 018(B02)
User 2: 002(A02)
User 2: 013(A13)

You could Load a single Performance from the EDM library... You'll receive a notification that the Performance references USER VOICES. What this means is that although the Performance data has been loaded, the MOXF cannot guarantee that the VOICES needed are in these current locations. It simply is pointing to whatever Voices occupy the User locations. If your MOXF currently contains the factory set library... then the Performance data you loaded just will not sound right, because the User Voices cannot be loaded by simply loading the Performance data. You must manually load the four individual Voices to their (expected) target locations. And while this is, indeed, doable... Multiply it by the number of Performances and it can get tedious and you'll need paper and pencil to write down which locations you've already filled, etc., etc., can you feel the headache growing? John did, and he created a solution!

Enter the power of the Melas Total Librarian... You can open multiple library files on your computer (well of course you can, the computer doesn't have make sound in this case, it is just opening the parameter settings) when you literally drag the Performance name from the EDM library, and drop it into a blank Library field, the four Voices that are used are automatically moved to the blank Voice library field. Immediately, you can see the value of the Melas tools... The Performance and its minions are handled together.

It establishes a "parent"/"child" relationship between the Performance and its four Voices, such that when you move the Performance, the data for all the Voices move to the Voice field, as well... Occupying the first four empty locations... And it re-establishes the relationship so the four Parts reference the correct four Voices. As you assemble the Performances (by dragging and dropping the names) the Melas Editor does all the "heavy lifting" - keeping the all-important parent/child relationship between the Performance and its Voices.

If you have a bank of Performances you want to assemble, you could do it manually (of course) but the Melas tools will have finished in a fraction of the time (it does what you'd expect a computer to do... All the heavy lifting!!! ie, make things easier!

Now if you think that is cool, and it very much is... It does the same thing with Master programs and their related data.
You are making the data on the computer that can then be bulked to your hardware MOXF via MIDI. It's brilliant!

But where it really goes "off the charts" useful is in how the Waveform Editor actually moves the audio data (Waveforms and Samples) in the same kind of Parent/Child relationship. Makes organizing and reorganizing tasks a breeze!

The Waveform Editor allows you to make a Motif XF file (.X3A) which, of course, your MOXF can read. The Waveform Editor is able to open native MOTIF XF and MOXF files, including the Waveforms and the individual Samples. And when you drag and drop a Voice from one library all the data (including the audio data) is moved as well. The Parent/Child relationships are maintained. (Hooray!)

With the Waveform Editor you are able to move data from several different Files, create a new File, export that new File to a USB stick, and then load/install it into your MOXF. And using far less calories than I burned explaining this. Trust me once you begin to understand what I refer to as the "heavy lifting", you realize that ... Sure you could do this all manually, but wouldn't you rather fly to California from NY on a jet, instead of traveling in a Conestoga covered wagon? That's why you see those elated testimonials about how valuable the Melas suite is. It's invaluable!

If you are going to or want to become a power user of your MOTIF XF or MOXF... You'll do yourself a huge favor in getting and learning to use the Melas suite. You'll never look at that covered wagon again... You'll be flying first class.

Conclusion: I've not met John personally, but he is extremely helpful if you get stuck, or have a request. The Waveform Editor also allows you to assemble User Arpeggios from several libraries... Something you absolutely cannot do manually, well not easily anyway.

While not for everyone, the Melas suite is for those that want or need to customize or create their own data for their Yamaha Motif XF/MOXF synth.
You still will use the Yamaha Editor VST to route MIDI/Audio, manage and select sounds in Cubase.
Edits you make in the Melas suite become a Library File for your MOXF so the fact that they were constructed in the Melas suite will be irrelevant. They simply become your MOXF's data.
The Waveform Editor (sold separately) is necessary when working with Waveforms and Samples for a MOXF Flash Board.

Hope that helps.

Yup - that was very helpful - thanks!

I was having a hard time understanding how to manage MOXF User Arpeggios libraries using John's tools. John acknowledged that his current version cannot read/write MOXF user arpeggio files. There are some work arounds using MOTIF files but I have not figured out a good workflow. Any suggestions would be appreciated.

Since you've made contact with John, maybe you could ask him if he would be open to making an arp editor???? Don't know if that's possible. But who knows?