Forums > Max For Live

Pattrstorage "by default"

Mar 01 2013 | 11:04 pm

Howdy folks. It’s been a second since I last stopped in, hope all are well.

Consider the following patcher. My goal is to create a system that writes a pattrstorage preset programatically when (and only when) a number is sent to the flonum or a user chooses a value from the umenu. This presents an obvious problem; when a preset is recalled it is also stored, leading to a collision and a hard crash.

Putting a deferlow on the store message seemed to work in max, but not so much in live. The solution using a set message to prevent storage on recall does not crash, but somehow the wrong value always gets recorded for the umenu.

Many thanks in advance for any help


-- Pasted Max Patch, click to expand. --

Mar 02 2013 | 4:55 am

Not quite sure what you mean by collision – I also can’t get this to crash, should I be able to? I tend to use ‘autopattr @autorestore @parameter_enable 1’ for handling storage in m4l patches

Viewing 2 posts - 1 through 2 (of 2 total)

Forums > Max For Live