Hi guys,

At this point I need to be able to make 100’s of custom Performances and store them without overwriting the MOXF User Performances.

In addition, I would like to be able to edit/construct the Performances on a computer screen.

Once I have all the Performances (the original User ones as well as my custom ones) stored on my computer, I would like to be able to load the Performance (either one at a time or an entire bank) into the MOXF.

Which Melas Product do I need?

Jerry

The Performance Editor, of course.

So a Performance Editor will store/organize/keep up with hundreds of Performances?

Correct, but understand that it is a part of a suite of Editors. You should get the COMPLETE PACK Total Librarian (includes the Performance Editor).

You always look for that “get out of jail free” card. :-) The editors can help YOU manage your hundreds of Performances, but it cannot think for you.

Performances are based on Voices. The Performance remembers that you used the Voice in a specific location. If you then change the Voice in that location, your Performance will sound different.

Specifically, if your Performance contains a Flute Voice in Part 1 that is physically located in User 1:001(A01), the Performance data remembers “USER 1:001(A01)”

If tomorrow you replace User 1:001(A01) with a Tuba… the Performance that you made now substitutes a Tuba for the Flute. Fail to understand this reality at your own peril.

The Factory Performances always work, why? Because they all reference Preset Voices that will always remain in their Voice bank locations. User bank locations can change independent of your Performances.

Your Performances may reference User Voice locations which as stated, are subject to change according to which library you have loaded in. So get the Total Librarian because you will need to manage both your Voices and your Performances. Because you seem to feel you will develop “hundreds” of Performances, we are going to take a guess you will use more than the 384 User Voices to make them… So while you definitely want to get the Performance Editor, you will want to manage your Voices as well. Trust me.

When you wish to assemble your custom Performances, the Melas suite will maintain the parent-child relationship between the Performance (parent) and its Voices (children), so that you can copy the Performance and it brings along its four children into a new library field. And it re-points the Performance to reference the Voices new a User locations.

So yes, the Melas suite will solve your request, but you will need to know how the MOXF works to get the most out of it. Make sense?

Bad_Mister - 07 May 2014 10:34 AM

So yes, the Melas suite will solve your request, but you will need to know how the MOXF works to get the most out of it. Make sense?

Hello Phil!

Yes, it makes perfect cents :)

Last (2) questions:

I notice there are versions available for the XF and the MOXF.

1) Will the MOXF version be backwardly compatible with the XF?

2) Will the XF version be forwardly compatible with MOXF?

Thanks,

Jerry

jerrydpi - 07 May 2014 02:06 PM

Bad_Mister - 07 May 2014 10:34 AM

So yes, the Melas suite will solve your request, but you will need to know how the MOXF works to get the most out of it. Make sense?

Hello Phil!

Yes, it makes perfect cents :)

Last (2) questions:

I notice there are versions available for the XF and the MOXF.

1) Will the MOXF version be backwardly compatible with the XF?

2) Will the XF version be forwardly compatible with MOXF?

Thanks,

Jerry

jerrydpi, the XF and MOXF versions will behave very much like the machines themselves:  The XF version will be able to deal with XS file types (unlike the MOXF), and the MOXF version will be able to deal with MOXF file types (unlike the XF).

is very responsive, he will be glad to answer more nuanced and/specific questions about his products.

For what it’s worth, I agree with Bad Mister: if you plan to do any *serious* amount of editing, whether it be performances or voices, the complete Melas suite is INDISPENSABLE.  I can’t tell you how much time and frustration it has saved me.

The great thing about the Librarian is that it color codes voices and performances so that you can easily see the dependencies.  A great time saver!

Just my two cents…

cmayhle - 07 May 2014 02:35 PM

The XF and MOXF versions will behave very much like the machines themselves:  The XF version will be able to deal with XS file types (unlike the MOXF), and the MOXF version will be able to deal with MOXF file types (unlike the XF).

is very responsive, he will be glad to answer more nuanced and/specific questions about his products.

Hey cmayhle, how ya’ been?

The reason I asked is to see which version (XF or MOXF) I should purchase.

Good to hear from you :)

Jerry

Warning! Danger, Will Robinson, danger!
The Editors communicate via SYSTEM EXCLUSIVE messages. Messages for the Motif XF will be ignored by the MOXF, messages for the MOXF will be ignored by the Motif XF.

Attempting to BULK (the method of moving Voices, Performances, etc between the software and hardware) MOXF Voices to the Motif XF Editor will fail, and vice versa.

Compatibility is one thing, communication in real time is another. The two products have different Model IDs.

If you get the Motif XF Editor suite you will need to communicate with a hardware Motif XF… when you make a file (.X3A) that file will be able to be loaded by the MOXF. That is true.

But you cannot connect the Motif XF Editor directly to the MOXF. Clear? Nor can you connect the MOXF Editor directly to the Motif XF.