John T


I have the same problem as the OP. If I set it based on time, the frequency of saving seems to bear no relation whatsoever to the value set.

What is your change setting John? It seems to sense even the smallest action as a change which will override the time setting. Theoretically a setting of 5 minutes, zero changes should just save every 5 minutes but TBH I haven't got mine set up like that so that might not work/be broken.

I'm currently using 5 minutes or 30 changes which seems to work well for me.

I have set for every 10 minutes and 0 for changes. And it seems pretty damn random. It's not a big irritant to me. Or at least, having lost lots of work in my time, it's the much lesser of evils. So not one that massively bothers me, but wanted to confirm that the OP is not mistaken. Dunno whether it's a system config issue or what.

I wonder whether transport running time is included in the timer or not? Having said that it shouldn't make it save more often, less if anything but it would make it vary.

What I would like to know is whether it has a set minimum time period..mine seems all over the map.

Yeah, it never initiates a save during playback. Ah, actually, I've just realised what it could be. If a save comes due during playback, it will save as soon as you stop the transport. However, maybe it doesn't reset the timer. So rather than an X minute wait til the next save, it sticks to the previous schedule, and so the next one feels "early". Bet it's something like that.

Could very well be. 

Maybe I might do some checking about this a little later again.

this question was first adressed to Ross in the comedy series "Friends"!

I believe the episode was called "The One with Ross' Autosave Issue". 

John T


Yeah, it never initiates a save during playback. Ah, actually, I've just realised what it could be. If a save comes due during playback, it will save as soon as you stop the transport. However, maybe it doesn't reset the timer. So rather than an X minute wait til the next save, it sticks to the previous schedule, and so the next one feels "early". Bet it's something like that.

Yeah that'd make sense (as to why it works as it does).

In my system autosave work OK, but when use Melodyne is more slow and the scroll freeze 3 or more seconds