gbravetti

EDIT: Reported already and got this answer:

"Thanks for the note. This should be fixed in an future update."

-------------------------------------------------------------------------------------------------------------

I'm working on a very basic preset manager for a synthesiser, about 28 values most of them are on off buttons.

I'm using the Patterstorage's Parameter Mode Enabled option so all the information is stored within the live set.

I'm using a live.numbox to recall presets. If I recall presets manually by using my keyboard or mouse all works perfectly, now If I use a MIDI controller or an envelope or a Macro knob to control the live.numbox, there is a lot of CPU peaks and audio drop outs. Even if the envelope is not a ramp but just 2 static values i.e jumping from 1 to 2 and back.

While I'm editing the patcher on Max there are no peaks or audio drop outs and MIDI comes out correctly from the patcher through Ableton Live.

After many tests I disabled the Patterstorage's Parameter Mode Enabled and voila, all works perfect, but now I have to save my presets in a separated file and I don't want to do that.

My guess is that accessing to preset data stored on the "live set" messes with the audio stability.

I'm using an empty live set with the sine testing tone to listen to audio drops.

Any idea or advice on how to overcome this issue?

EDIT: Reported already and got this answer:
"Thanks for the note. This should be fixed in an future update."

-------------------------------------------------------------------------------------------------------------
I'm working on a very basic preset manager for a synthesiser, about 28 values most of them are on off buttons.

After many tests I disabled the  Patterstorage's Parameter Mode Enabled and voila, all works perfect, but now I have to save my presets in a separated file and I don't want to do that.

Automating preset changes + parameter mode enabled = CPU overloads and drops