Can "daisy chain"-saving eventually corrupt a set?
Posted: Wed May 26, 2021 5:56 am
TLDR: I have reason to believe that a complex Live-set that I have kept developing for years now, has become buggy.
It makes me wonder if it ever becomes advisable to "rebuild" a set from scratch for reliability of performance.
After lots of testing trying to locate the reason for higher CPU-loads, it appears to be a corruption in the data itself. A current version of the set now idles at 52% while an identical set saved a year ago in the saving-daisy-chain) idles at 33%. That's with every effect turned on and everything else identical as well.
I'm curious if others have similar experiences, and if rebuilding the set made a meaningful difference.
Also wondering from a software-engineer's perspective, if my hypothesis is even realistic. But I do assume that project files (Live sets) can indeed become corrupted for various reasons.
It makes me wonder if it ever becomes advisable to "rebuild" a set from scratch for reliability of performance.
After lots of testing trying to locate the reason for higher CPU-loads, it appears to be a corruption in the data itself. A current version of the set now idles at 52% while an identical set saved a year ago in the saving-daisy-chain) idles at 33%. That's with every effect turned on and everything else identical as well.
I'm curious if others have similar experiences, and if rebuilding the set made a meaningful difference.
Also wondering from a software-engineer's perspective, if my hypothesis is even realistic. But I do assume that project files (Live sets) can indeed become corrupted for various reasons.