External controll may build an huge undo.cfg
Posted: Sun Mar 13, 2005 12:17 am
Noticed this:
Controlled three parameters in simpler and resonators with midi clip envelopes though midi yoke.
While running, I replaced the sample in Simpler and tried to undo the replacement. Did not work. Looked in the Edit menu - Undo was set for one of the the parameters controlled.
Started monitoring the undo.cfg and could see it growing. So after some minutes is was up to 25 megs.
For people doing live perfomances over hours, this could easily grow to dimensions where it could conflict whith swapping and general performance stability (I guess).
Suggestion: Skip the automated "editing" flag when building undo.cfg.
And: running a automated set will always turn on the "dirty" flag and signal that the set has been changed. That's confusing when the only thing you did was running the set.
Edit: Seems the undo.cfg jumps back after awile, now it's 5 megs... And I thought a heard a sound glitch when the jump was taken.
// C
Controlled three parameters in simpler and resonators with midi clip envelopes though midi yoke.
While running, I replaced the sample in Simpler and tried to undo the replacement. Did not work. Looked in the Edit menu - Undo was set for one of the the parameters controlled.
Started monitoring the undo.cfg and could see it growing. So after some minutes is was up to 25 megs.
For people doing live perfomances over hours, this could easily grow to dimensions where it could conflict whith swapping and general performance stability (I guess).
Suggestion: Skip the automated "editing" flag when building undo.cfg.
And: running a automated set will always turn on the "dirty" flag and signal that the set has been changed. That's confusing when the only thing you did was running the set.
Edit: Seems the undo.cfg jumps back after awile, now it's 5 megs... And I thought a heard a sound glitch when the jump was taken.
// C