Ian Dicke

I am building a M4L midi device that uses the pattrstorage system (storing about 400 values).

With my mouse, I can manually recall a preset during playback with live.tab and it works fine without any lag or audio artifacts.

But when I automate the live.tab, every value change causes a short CPU spike and audible click. Setting Live's buffer to a high value (2048) alleviates the issue, but this isn't ideal. I tried setting pattrstorage to "changemode 1", but that doesn't help.

My previous solution is to forgo pattrstorage altogether and substitute a dict preset system instead, but it is a complicated workaround that I am trying to avoid.

I am building a M4L midi device that uses the pattrstorage system (storing about 400 values). 

With my mouse, I can manually recall a preset during playback with live.tab and it works fine without any lag or audio artifacts. 

I am building a M4L midi device that uses the pattrstorage system (storing about 400 values). 
With my mouse, I can manually recall a preset

automating-pattrstorage-causes-clicks

Update: seems like automating live.numbox to recall presets instead of live.tab resolves the issue. I'll keep testing.

How often do you want to recall your pattrstorage preset? That's certainly the problem.

What about using the [change] object before giving the number preset number to pattrstorage?

How often do you want to recall your pattrstorage preset? That's certainly the problem.
What about using the [change] object before giving the number preset number to pattrstorage?

I didn't realize that the automation lane in Live is constantly sending the value to the max object. Another thing that helps is lowering the "Update Limit" found in the inspector.

Automating Pattrstorage Causes Clicks