undo history vs. continuous modulation

UHE is now closed. For Technical Support from Ableton, please go here: http://www.ableton.com/support
Locked
siliconarc
Posts: 2872
Joined: Mon Jul 16, 2007 12:27 pm
Location: UK
Contact:

undo history vs. continuous modulation

Post by siliconarc » Thu Nov 03, 2011 10:43 pm

just been messing about with some midi modulator plugins, all mapped to device knobs, when i ran into this message:

Image

the audio stopped, and the message wouldnt go away after clicking 'OK' repeatedly.
did a force-quit, restarted Live. froze on startup.

noticed the undo.cfg file was 2.15gb so trashed it, tried a Live restart. froze again.
:?

ended up having to trash the prefs.cfg, crashdetector.cfg and the undomarker.cfg to get it to startup.
ouch.

i was using 3 of pizmidi's audio2midicc vst, sending out 3 seperate CCs via IAC and routed back in again, mapped to various knobs in operator. it crapped out spectacularly.

i thought this issue had been fixed in Live 8 after all the M4L work done 'under the hood' to stop M4L LFOs etc from flooding the undo history, but maybe that only applies to M4L devices..?

[edit] after a rummage around the M4L forum, looks like you can tell an M4L modulator to be visible or not to the undo. handy! but i don't have M4L, and know F all about it. is there some options.txt entry that i can use to tell Live to ignore continuous modulators?

8.2.5 | OS X 10.6.8

Locked