scene write, edited tone will be discard

[Redrain68]

So 30 seconds for save create and write a tone name X 256 = 7.680 seconds wasted

7.680/ 60 = 128 minutes = 2 hours and 8 minutes used to save tones for 16 scenes.

Add 1 hour to find a waveform for one partial without a tag and database system and the circle is closed.

It’s a dream for a preset user but a nightmare for a tone creator.

Well, writing a symphony takes some time.
It is a time we are supposed to enjoy, on the basics of creating our own style, our own music.
This way, the Roland way, you make music with unique instruments.
We start with a cello that was put at our disposal, but modify it for the scene, even for a switchgroup.
It is a cello, yes indeed, nice sound, very real, but this time an echo is needed, and a delay....and it must sound when I release the keys, and later it must sound half a second after pressing the very same key....Or even I add a partial into the cello that will sound a castanet if I play within another key range at a higher velocity. Or lower velocity...
Endless ways to make our own dreams come true.

It could be improved, very much, but I thank Roland again.
I have been waiting for this Fantom since I was a child.
.
Perhaps with update 12345.8 Build 19.6 you simply think of it and the music goes on playing loudly all around Earth. Within a split second after your thoughts are done, but of course.
With update 15345.9 it could be heard all around the Milky Way just as you start thinking on the very first couple of notes, since artificial intelligence should know what comes next, why not?

I am on a diet to reach 120 of age. I might see it.

This is true and correct . I simply can’t read and think that the Roland tone / scene management system is the best in the world.

[Acidizer]

99% of the patch tweaks I make are to balance against other sounds in the scene. They are useless and sound bad outside of the scene they were tweaked for.

End result is I waste time having to save every tone individually for no reason, all they do is pollute the user bank with useless tweaked presets. They will never be used outside of their particular scene.

Everything should be saved as a program, like JDXA. Makes complete sense, a scene is your program.

If you actually want to save your patch to the user bank for posterity, e.g. if you made it from scratch, then that option is there. But the user shouldn't be pestered with saving tones otherwise.

Having to save a brand new tone every time because you tweaked the cut off or envelope is complete nonsense. This should be scene level stuff.

[zombietactics]

That's what "Offsets" are for.

[Acidizer]

No offsets only go plus and minus 64. Cut off etc goes to 1024.

Close the cut off filter on the front panel completely then put the offset cut off to the lowest setting, see what happens..

and we shouldn't need to menu dive when it has the dedicated front panel controls, that's moronic. The patches should save with the scene, they are a vital part of the scene the same way volume and pan is.

[jef_citron_2]

I'm agree with Acidizer, the patches should be saved inside the scenes.

[FGM]

When you are done setting a scene and afterwards you start playing, moving anything will change the scene, from panning to volume, from filters to wheels...to S1, S2, S3...anything.

Often, pressing a button will make a parameter to go from +64 to -63...
Once the playing is done you are to leave the scene WITHOUT SAVING anything, by selecting another one and returning back AFTER setting wheel 2 to the required position, as well as some other switches and spiders, or it will become useless, since it will have nothing equal to the scene you started with.

I learned it the hard way... Thankfully I had made a back-up and everything was recovered.

As for saving tones after little changes are made, it is not always necessary if you first press shift and the zone to be edited, then apply changes and will be saved without the advisory " Edited tone will not be saved ".

[aanon]

I have a Fantom G and this kind of issue is one of the main frustrations. If I use the PC editor and save my work, everything is recalled perfectly including changes to patches within a Studio Set. But if I work from the keyboard it is necessary to save custom user patches. I don't understand why they did it this way, and persisted doing it this way in the new Fantom even after all the user complaints.

[Perplextor]

It would be so easy to save the temporary buffers within a scene. There are only 512 scenes. Memory shouldn‘t be an issue.

[arp70blue]

My 25p's worth....

I have Fan X, G and MC-707.
MC-707 I understand has same sound engine as new Fantom.
In MC-707 you load up your tracks, add your patches, do your thing, save your song to USB. Any edits to patches are saved with the song from what I can see.....I.e. I load up XV5050 piano, add longer release and save song. That longer release is there the next time I load up that song, it has not over-written the original XV5050 piano patch in the MC-707. The tech, programming, code or whatever you wish to call it is already there, it should be implemented in new Fantom. USB memory is cheap and available - why not make use of it? I have same frustrations with X and G as others express re new Fantom.. MC707 approach is great.