I think there may be some issues with some types of data from an XF going to a MOXF..for example

I am trying to load in the AXXE library (as a 1Perf Bank and 1Voice rather than just the x3a file as there is no User 4 on the MOXf)

When loading the voices I get an “illegal file” message, but upon checking the User 3 bank (where I sent them) I find that most have loaded and work, except three that show the name of the voice but don’t play, and numbers 106 thru 128 showing as “initialized” voices. (I checked the docs and there are definitely voices in those slots.

So for some reason the MOXf is loading some, but not all the voices. Does anyone have any ideas why a select number do not?

It’s been my experience, at least with the XS and XF, that interrupted loading causes the locations that haven’t as yet been written to be initialized. I therefore suspect that whatever is “illegal” about the file is causing the MOXF to truncate the load, which probably explains what happens to 106 through 128.

As to what’s “illegal” about the AXXE data, IDK. Determining why it is the three Voices don’t play might provide a clue as to what’s happening.

By the way, can you successfully load Voices 106 through 128 individually?

Actually, it is more likely caused by the fact that this collection also contains some user arpeggios and loading via 1bank a) won’t load the arpeggios which b) might then cause some problems - certainly in terms of sounds not seeming to play.

We have tested importing Axxe from the MOX All file and can report that it loads perfectly. If you have that version, use this in place of the Motif XF’s 1 bank load I think.

Dave Polich of DCP is in the process of converting many if not all possible DCP libraries to MOXF as soon as he can. At that time he may (or may not of course!) do some additional programming for the MOXF version so we have decided not to directly ‘offer’ MOXF owners versions of DCP libraries that have not been prepped for the purpose by Dave himself.

So, to recap, the 1bank load method of importing a Motif XF library works ‘technically.’ But if the library in question has additional features that would normally get loaded from an All file then it’s not realistic to bank (sic) on a perfect import using that method. MOX format is a far safer bet since you can still load via an All file.

If you don’t have a MOX version of a library you are interested in using on a MOXF we’d recommend waiting only a short while longer until Dave has had a chance to judge which, what, or whether to make adjustments for MOXF.

Hope this is both clear and fair!

MM

5pinDIN - 20 November 2013 11:26 AM

By the way, can you successfully load Voices 106 through 128 individually?

No 5pin, and the other three that load the name only are the same. They will not load individually either.

I may just have to wait for DP to convert (if he does?) or go the MOX route as suggested by MM above - although as the architecture of the MOX is not as comprehensive as the MOXf I suspect there may be some compromises in that set.

MrMotif - 20 November 2013 11:28 AM

Actually, it is more likely caused by the fact that this collection also contains some user arpeggios and loading via 1bank a) won’t load the arpeggios which b) might then cause some problems - certainly in terms of sounds not seeming to play.

We have tested importing Axxe from the MOX All file and can report that it loads perfectly. If you have that version, use this in place of the Motif XF’s 1 bank load I think.

Dave Polich of DCP is in the process of converting many if not all possible DCP libraries to MOXF as soon as he can. At that time he may (or may not of course!) do some additional programming for the MOXF version so we have decided not to directly ‘offer’ MOXF owners versions of DCP libraries that have not been prepped for the purpose by Dave himself.

So, to recap, the 1bank load method of importing a Motif XF library works ‘technically.’ But if the library in question has additional features that would normally get loaded from an All file then it’s not realistic to bank (sic) on a perfect import using that method. MOX format is a far safer bet since you can still load via an All file.

If you don’t have a MOX version of a library you are interested in using on a MOXF we’d recommend waiting only a short while longer until Dave has had a chance to judge which, what, or whether to make adjustments for MOXF.

Hope this is both clear and fair!

MM

Thx MM - yeah that makes sense. I think I will wait to see if DP does convert this set. As I wrote above I think the MOX version (due to the nature of the beast) may have some compromises in it.

Again a well detailed reply - much appreciated :-)

Please make sure you have updated your MOXF firmware to version 1.03

Bad_Mister - 20 November 2013 12:34 PM

Please make sure you have updated your MOXF firmware to version 1.03

Was the first job I did when I took it out of the box ;-)

Should always be the first thing mentioned whenever posting a problem.

After finally being able to get a MO XF, I have investigated the issues with Axxe XF loading incorrectly to the MO XF. Long story (somewhat) short, there is a mysterious problem with voice 106 that causes it to appear as an illegal file to the MO XF, and no voices after voice 106 will load either. And, indeed, if you tried to load AXXE XF using the “1 bank voice” method, pointing the USR 4 bank to go to USR 3 on the MO XF, you will not load the user arps associated with the voices, and thus some voices will not sound unless you turn the arpeggio button off.

If you have your Motif XF files, there should be a separate “Axxe XF arps” file which you can load first to the MO XF BEFORE loading the voices, and they will find the arpeggios that belong to them. As Bad Mistern pointed out, you MUST have the latest MO XF firmware update installed in order to load the user arpeggios file.

Or you can wait for the “official” converted MO XF version of Axxe (see below). This version will load as an All file, loading voices to User Bank 3 and performances to Performance bank 2, and all the correct arpeggios will load as well.

The problem with voice 106 has been resolved, and Axxe for the MO XF has been converted and is finished. It has been sent to Keyfax and they should post it soon. If Keyfax has a record of your purchase of either AXXE MO X or Axxe Motif XF, you will be able to get the “officially updated” MO XF version of the library free.
Please wait for Axxe MO XF to appear in the Shop before contacting Keyfax about it.

Official MO XF versions of DCP libraries will be following soon.

Thx Dave for your super quick attention to this - kudos! I can’t wait for it to be released!

And to anyone else, once this pack is released, it really is one you MUST have for your MOXf, one of the best around if you like rock, r+b, jazz and acoustic music.
Guitar patches are brilliant and extremely well programmed as are the 16 performances Dave has set up. Do yourself a favour and put AXXE in your basket! (I own the XF version for when I owned an XF7 so I am speaking from experience)

There are also issues with the John Melas Wave Editor....The files work fine in the XF, but on the MOXF I got illegal files as well with my Neo-Soul Suitcase. What I had to do was re-save the file on my XF, then it worked on the MOXF.

GospelMusicians - 21 November 2013 09:42 AM

There are also issues with the John Melas Wave Editor....The files work fine in the XF, but on the MOXF I got illegal files as well with my Neo-Soul Suitcase. What I had to do was re-save the file on my XF, then it worked on the MOXF.

I had the same issue when I tried to load your Neo Soul Suitcase in my brandnew Moxf8. Loaded a single voice from the download file, the Installation startet properly displaying “now installing to flash...”, finishing with “illegal file”.

Don’ t know exactly what the procedure of “re-saving” is all about? Could you please provide a step by step description? I still have a XF8 to do a save-all (is that what you mean?)…

Yes. Simply load the data into the Motif XF and let it make the .X3A file. It seems to make the necessary corrections so that the MOXF can read it.

Hi Phil,

thanks for the quick reply. I have now tried to load the (same) data from a Motif XF all.file (with waveforms) in the MOXF, and that actually works.

I just wonder what MOXF users should do who do not have an XF at hand. Advertising with full compatibility with “all of the sound content developed for the MOTIF XF” is not quite right at the moment…

But great is the free CP-1 Piano, thank you to Yamaha for this goodie.