I see that the Motif XF has better File Management to make this much easier than the XS and also has Tap Tempo which the XS does not. I was wondering if there will be an update for the XS with these features ? If the answer is no, my question is WHY NOT ??????

venattboy - 26 August 2010 08:52 PM

I see that the Motif XF has better File Management to make this much easier than the XS and also has Tap Tempo which the XS does not. I was wondering if there will be an update for the XS with these features ?

yes, motif XS OS update is scheduled for 31st of September at 12:35am SPT and it gonna be huge.

Don’t know about file management, but they have promised tap tempo and drum kit editing in song/pattern mode.

Yeah, can’t wait for that update for my XS8.. :D

Well, if they don’t make this update for the XS, at least to correct the file management issues, the XS will be remember in history as a workstation with SERIOUS FILE MANAGEMENT PROBLEMS.

For me it has been a headache or el TALON DE AQUILES, juts consumes so much of my time I should be spending in music and not in how to deal with file management.

Please Why don´t the Yamaha Team program the Tap-tempo on the Motif XS, as far as I know, the O.S. es just Linux and I think its posible to do. I can´t wait for this OS update.

A little while back when the XF was being announced the Yamaha rep type folks here on these forums let us know that the XS would be receiving an update as well.  The tap tempo thing was part of it (and boy does that make me happy).

So no worries, Yamaha still loves the XS owners too. :)

I would also think that if the XF has a better setup for File Management, an update for the XS in this aspect is posible. Still the FX has other sounds, flash, and another User Bank etc.

The other user bank is tied up with the new rom samples though....

Gee I thought I was the only one who didn’t like the XS file management. Guess I’m not the only one.

Oh and please...don’t criticize the XF in this forum. Yamaha US is I’m sure concerned foremost with how this forum affects sales. We are all beholden to them so please don’t do anything to disrupt their sales cycle.

After all if that happens we might not get any software updates.

So please make sure you post complaints somewhere else…

Guess what Yamaha US? I didn’t start this thread. If you think I’m the only one who thinks I think like I do....I’ve got some news for ya.

Anyone who spends kilobucks on something thinks like I do.

F

Is there support for tap tempo via a footswitch?

The biggest issue with the XS file management system that we have found listening to XS users over the last 3 years is that it is easy to duplicate waveforms when loading from a library file.

Currently the XS will always load what is needed to playback a Voice.  This the safest way to deal with loading a single Voice , but it has one disadvantage.  If you use load one Voice and continually load single Voices , you will end up with duplicated waveforms which wastes RAM space.

On the XF , this file management has been improved in two ways.  First, when you plug in a USB device, the XF will register this device and then you can continue to load from that particular device in one “session” without duplicating waveforms.

On top of that , if you somehow do end up duplicating waveforms, there is now a “delete waveforms with the same name” job in the sampling mode that let’s you select waveforms and see what Voice use that waveform , if a waveform with the sane name exists and the job will automatically delete waveforms with the same name and re-assign or re-point all the voices that use the duplicated waveform. 

We have requested that both these features be added to the OS update planned for the XS.

Does anybody knows when the new OS with Tap Button funtion will be available, Mr delirium said “motif XS OS update is scheduled for 31st of September at 12:35am SPT and it gonna be huge.” nevertheless nothing till now.

You should realize that Delerium has a bit of a different sense of humor and often his posts are in jest.

We believe that the OS update will be available this year , but are headed to Japan the week of Oct 18 and should have more details when we get back.

Yamaha_US - 07 September 2010 10:00 PM

On top of that , if you somehow do end up duplicating waveforms, there is now a “delete waveforms with the same name” job in the sampling mode that let’s you select waveforms and see what Voice use that waveform , if a waveform with the sane name exists and the job will automatically delete waveforms with the same name and re-assign or re-point all the voices that use the duplicated waveform.

Hi Yamaha_US.  I noticed when scrolling through the waveforms I had loaded on my 1GB FLASH that many waveforms would have a tag along the lines of “Used by [Voice XYZ] and others...” (that may not be exactly what it says as I am writing this from memory). How do I access the “and others” portion of that tag to see what other voices the waveform uses?  Is that info only available via the Job mode as mentioned above?  Thanks!

The purpose of the “used by” parameter is to inform you that a particular WAVEFORM is being used by one or more Voices. When you are in a situation where you are eliminating unused data from your FL board, you want to know if a Waveform is still being utilized by any VOICE.

When a WAVEFORM is not used by any VOICE in your current setup, you know you are free (safe) to eliminate it (DELETE ONE). Don’t miss understand the purpose, the purpose is to find the so-called “orphaned” Waveforms… Waveforms that are no longer necessary to carry around because the “parent” Voice is no longer in the current XF Library (internal banks).

It is not a look-up table that will tell you every VOICE that uses a particular WAVEFORM… All you need to know is that the WAVEFORM is being used or still being used by a Voice that is currently occupying one of your INTERNAL Voice bank locations.

Carrying around a bunch a WAVEFORMS that you never use, is simply bad (poor) use of the FL boards. If you are going to be efficient you want to maximize your use of the memory.  When a Waveform is used by more than one VOICE you can be assured you will need that Waveform, its popular. If you overwrite a VOICE that is listed as using it, only the current VOICE that uses it will be shown in the “used by” parameter.

You should not eliminate a WAVEFORM if it is used by a VOICE in your current internal VOICE banks. ... you simply need to know that the WAVEFORM is indeed in use! Go to that VOICE make a decision about if you need it, if not you can write over it. when you write over a VOICE, its status in the ‘used by’ list will be updated.

Hope that helps.

Bad_Mister - 08 October 2010 06:31 AM

It is not a look-up table that will tell you every VOICE that uses a particular WAVEFORM… All you need to know is that the WAVEFORM is being used or still being used by a Voice that is currently occupying one of your INTERNAL Voice bank locations.

Hope that helps.

That does help.  I have been using John M’s awesome tools to construct banks before I load them in to flash, so file management is not an issue for me.  Just seeing how deep I could dig from the front of the XF.

Thanks!