I'm not sure if you also have a Motif - but if you do, it may be interesting to try to load on the Motif.

I've seen reports that there were certain versions of the Melas software which converted XS files (X0V for example) which created "bad" X3V files. The suggestion was to upgrade to a later version of Melas and re-create the X3V from the source X0V. Now, if you didn't create the X3V - then you may not have the original source.

... still, this is a "shot in the dark" and may not be related to your issue at all. However, if it was this problem - then the Motif would have similar issues with recalling the same data correctly.

To that end - I think it would be good to document what this X3V file is. If it's a custom user-created file (through translation or otherwise) - then that would perhaps be seen as a different "class" of issue than if this was a final release, non-demo, non-promotional, commercial X3V available on Yamahamusicsoft.

What you're not communicating is that once you fix the waveforms that still there are certain samples that are silent. That's a whole other issue in how some legacy (mostly promotional material) is no longer supported in Montage/MODX. Namely unsupported encoding types (LPC and WXC) as well as unsupported bit depth (8-bit).

Hi Jason,

First of all, it's good to hear that the issue I described is not a normal behavior, as it would be really time consuming if we need to go through reassigning waveforms everytime a file is imported.

I think I might be experiencing issue related to Melas conversion ...
The X3V file was build in Motif ES, and Melas s/w was used to convert it to XF file. So, I'll redo the "conversion" again, and see if that solved the problem.

As for the waveforms .. I only "fixed" one performance by assigning the right waveform, so I might be experiencing also the second issue you mentioned, certain samples staying silent.

But I did notice that the playback of waveforms is significantly "quiter" than what it was on my Motif.
Any reason for that?

Thanks,
Denis T

I think I might be experiencing issue related to Melas conversion ...
The X3V file was build in Motif ES, and Melas s/w was used to convert it to XF file.

So it is not a .X3V File — the Motif ES would create .W7V or .W7A/ files, it is impossible to create a .X3V file in a Motif ES. So what type of file did you create?

Can you clarify what exactly you did? (it makes pinning down where you went wrong easier).

We assume you have the Melas Motif Waveform Editor(?)

The Motif ES dates back to four Element architecture

Adjusting volume can be handled many different ways... if not importing the original programming you may miss out on the various ways to increase output. But first, let’s determine what you did do... it is not at all clear.

Motif ES = .w7_
Motif XS = .x0_
Motif XF = .x3_

I was throwing some spaghetti at the wall because what you were dealing with (the X3V) was not documented. Although you haven't given full details, you've at least now documented that it's a user created file - so that puts this in a category where a number of things could have gone wrong in the user process of creating the file.

It was only if the file was downloaded from Yamahamusicsoft - and was not a promotional pack - and was compatible with MODX (one of the valid conversion source types) that I would have expected no issues. A user created file - I'm not surprised there's issues.

I apologize for the confusion gentlemen.

Here is some clarification.

The original file was build on my old Motif ES6, and was saved in its .W7V format. The file contained Voices build on high-quality user multisamples.
Those voices worked perfectly fine on my old Motif ES.

Since I've heard that MODX does not accept ES format, but only XF from the legacy keys, I asked a friend of mine to convert the .W7V file into the XF format .X3V.
I believe he used the Melas software for XF to do the conversion, as well as the Awave to convert the samples. Don't have much details on that but I know that those two apps were used to create a .X3V file.

Once that was done, he sent me the .X3V file and I loaded the file first into a library and then into USer bank. The loading and importing went fine, but the newly created performances had issues that I reported above.

I hope this clarifies the issues.

Thank you for your help.

Denis

Don't have much details on that but I know that those two apps were used to create a .X3V file.

And that’s where you need to begin your query... as those details are surely the key to your issue.

Using two pieces of software means that the Voices and the Waveforms were probably converted separately (in all likelihood) which could be why you wound up reassembling the data... but the only way to really know would be to load the data into a Motif XF... does it work? You don’t say.

Thanks BM.
Will do.
I wanted to check first if I used a proper procedure to load an XF file. It seem that you guys don't have issues with the way I loaded files, and haven't seen this problem often.

DT

I didn’t say that. I didn’t have enough information to make a guess about what was wrong — I just knew you didn’t save a .X3V file with a Motif ES!

When you attempt to Load the file to the MODX you have to select the “Voice” option. (There are no Performances in a Motif XF All Voice file).

Your description isn’t that clear about what is loaded properly and what isn’t. The volume difference could be so man6 different things -as the Motif ES had different effect processors and without actually using a Motif XS to apply the “lookup” table when substitute Waveforms were used, you can’t be sure about your friends work.

Recall a converted program.
Navigate to the Part 1, Element 1 screen
On the “Osc/Tune” screen, what Waveform is identified?
And from which Bank is it being recalled

If the Element is OFF, then nothing was converted.
If the Element is set to Number 0001 then that would be the CF3 acoustic piano Waveform (indicating that no lookup table was applied

Bad Mister,

I followed instructions bellow, but I could not find where I can change the IMPORT OPTION to "Voice".
I pretty much looked everywhere.

Also, the Element is set to Preset No.1 "CF3 Stretch Sw St" and is also "OFF"

thanks,
D

"Place the USB Stick into the MODX "To Device" port
Press [UTILITY]
Touch "Contents" > "Load"
Using the Data Dial set the "Content Type" = USER FILE
Touch the box that appears which will identify your USB drive to open it and see its contents.
You can set the IMPORT OPTION to either "VOICE" or "PERF" to load either the 384 Normal + 32 DrumKit Voices, or the 256 Performances."

If your file is a Motif XF ALL VOICE File (.X3V) it will (naturally) NOT contain any Performances (so you will NOT see that option).
If your file is a Motif XF ALL Data File (.X3A) it will contain an option just prior to Loading for Voice or Perf.

The Element Off and the default 0001 Waveform means that the Waveform did not load (your conversion was bogus)

Thanks for clarification about the IMPORT OPTION. As mentioned before, I was working with .X3V file.

The issue is not that the Waveforms were not loaded into MODX, but that they were not linked properly in performances.
As mentioned in my original post, I was able to find and assign proper user waveforms manually, which would not be possible if the waveforms were not loaded.

Now I have to figure out how to fix the low volume.

Cheers,
DT

The issue is not that the Waveforms were not loaded into MODX, but that they were not linked properly in performances.
As mentioned in my original post, I was able to find and assign proper user waveforms manually, which would not be possible if the waveforms were not loaded.

How can you know which Elements go where?

Say you EDIT one of the programs, the Element is turned OFF, and sits on the default CF3 Waveform 0001... what do you do?

In my case, performances (former ES voices) and corresponding waveforms have the same name, so I can easily identify which waveform goes where.