Undo.cfg has reached it's full capacity

[LOFA]

Hey y'all,

I got this problem in a Max/Live powered installation, where Live carries out a large amount of midi based operations and eventually a screen pops up. Based on memory, it says undo.cfg has reached full capacity.

Anyway, this makes my installation problematic, because the window pops up on the audience display.

Is there some way of either removing this .cfg or increasing the limit?

Any help would be great. Thanks!

BTW, I did not post this as a bug, because it seems quite intentional of a feature.

[longjohns]

is the display of the error the only problem, or is the error itself a deal-breaker

[LOFA]

Hi,

Only the display of the error, from what I know atm.

The installation will always start from an original default status. Changes will never have to be undone or saved. The everything within and outside of Live seems to function properly. It is the pop-up window that is prohibiting the installation from running uninterrupted, because the pop-up appears within view of the audience.

[longjohns]

what I was wondering is if it would be possible to run dual monitors

i find that often error messages pop up on the primary monitor

if that were true, you could have the live window on the secondary display, and maybe the error dialog would not be visible

[LOFA]

Hey,

I understand what you are saying.

The artist that I work for claims that the pop up interferes with either the full screen functionality of the non-live display, or that it is simply visible.

I really hope that a solution is possible for eliminating the popping up of this window altogether, but if an extension of the undo.cfg file size is possible, then we'll take it.

[[nis]]

we probably have a solution for you. send an email to [email protected]. I can't get back before monday, though.

best,
nico

[LOFA]

Hi Nico,

The email has been sent. Thank you

[shoeshine]

Hey Lofa,

any chance you can let me know what the resolution was?? I have a similar situation with an installation i'm running this weekend (only emerged after 12 hours use ...) and trying to resolve asap!

[LOFA]

Check your pm

[MBOSSA]

I've had the same issue with two installations running automaticly triggered midi notes... Running for long hours.

Has a fix been found? Can you share please?

Thanks.

[luddy]

This is most probably happening because you are using the wrong object in M4L to automate parameters. live.remote~ does not accumulate undo steps. I forget offhand what the control-rate variant of live.remote~ is called, but it *does* accumulate undo steps as the parameter is automated. Using live.remote~ throughout should fix the problem. (unless I've misunderstood what is going on...)

-Luddy