But here's the thing: I work on a project and save it. I open it again the next day, work on it _without_ saving and Bitwig crashes. I open the project again, and the plugin states are gone.nickallen wrote:If there is a crash we cannot restore absolutely everything. Well we can for Bitwig native devices but for plugins we are backing up their state every 5 seconds as long as transport is not playing (as asking plugins to save during playback could cause performance problems or audio glitches). So if you are constantly playing the arranger and never stopping transport for more than 5 seconds the plugin's state will not be backed up. The correct way to fix this problem is not to crash of course!der_r wrote:Yes!! More stability improvements.
It's not clear from the bug fix list, but did the bug where plugins reset to default state on crashes get fixed yet?
Why does Bitwig replace my old data with incorrect data without me manually saving? If anything, it should at least backup the old file, before saving over my project. That would solve the problem without having to fix the bug.
