Don't Get Me Started! • Re: Yamaha isn't smart enough to auto-backup

So I know others don't have this issue, apparently it's only me but I use a lot of technology that auto-saves such as my engineering CAD work. It save all work progress every few minutes.

An 'auto save' that does NOT alter the actual object (performance, pattern, etc) you loaded would be nice. I definitely don't want it to automatically overwrite an object that I load.

This does NOT what I would want:
1. load a performance named 'abc'
2. twiddle for a bit
3. auto save happens replacing original 'abc' with the twiddled version

That would be absolutely disastrous. Twiddling a knob, slider, pedal, parameter would change the original performance if the auto save just overwrote it.

This would be ok:

1. load a performance named 'abc'
2. twiddle a bit
3. auto save happens and creates abc.17 (next number in order)
4. twiddle a bit more
5. auto save happens and but now creates abc.18
6. and so on

That type of auto save just saves intermediate versions but leaves the original alone. You would use the current manual process to overwrite the original so you can control when that happens.

I just have to argue that in 2024 and as advanced as gear is these days why are we still being told to save our work?

Unfortunately you aren't ALWAYS told to save your work and can wind up losing it. Loading a pattern linked to a different performance than the current one, which you have edited, is a good example.

Do we even have infinite undo/redo yet or maybe 10?

I'd like to see a 'change log' created. Even something as simple as a set of SysEx commands that duplicate what you did manually would be useful if you had an easy way to scan the log, highlight a command (or set of commands) and execute them.

A more verbose log could have a comment for each command

// set Note Limit High to C3 (3C) for part 2
// F0 43 10 7F 1C 0D 11 00 02 0A 00 3C F7

Users wouldn't have to know how to construct that SysEx command. The system knows what you are changing and could rather easily compose a command such as the one above.

As for undo that isn't always so easy. But by using the log you could always reload the original performance and then execute the SysEx commands in the 'change log' up to the point you want to work with again.

Statistics: Posted by Douglas — Sun Mar 10, 2024 11:32 pm

---