parameter automation precision ?

[dasdeck]

hi there.
seems that one parameter automation event is sent per buffer.
is this true?
so the precision of automation depends on buffer size?
maybe this is not so optimal?
peace!

jm

[Mercado_Negro]

Yes, you're abosolutely right, buffer dependant

It'd be great if Parameter Modulation had a 'look-ahead' feature for those who need to mix at high latency values so we can have get smoother results.

NOTE: you can use a smaller buffer size for rendering tasks though; just go to Options->Preferences->Audio: Block size to use when rendering.

[musicbynumbers]

If that is so, does it still interpolate the two points?

If not you are going to get "zipper noise" as it jumps from one value to the next on things like volume automation.

hope this is not the case? schwa, justin... christophe?

[schwa]

Parameter modulation, like any FX parameter move (including moving a knob on the GUI or moving a physical controller), is sent once per buffer block, that's unfortunately not something that anybody can change. Well-designed plugins will interpolate parameter moves internally to avoid zippering, for example if a filter plugin advertises "smooth sweeps" that's what they mean. For volume and pan parameter modulation, JS/utility/volume_pan does internal smoothing.

If you have a plugin that you want to modulate but you hear zipper noise, you will need to lower the buffer size.

[dasdeck]

but you as a host developer can choose a different buffer size for rendering then the one from the audio device. no problem at all. (i know. i did so )
whatever..seems that since nobodey recognized it yet, it does not have to be that preceise...64samples sized blocks will be enough ...good for the performance ..
thanks!
jm

edit:
by rendering i don't mean offline rendering. i mean the actual realtime process.

[Mercado_Negro]

So there's no room for improvement in this side of the island schwa? Some of that magic you do? Tbh I don't notice too much difference, during mixing, between 2048 and 256 (which is the lowest I can go live) but after rendering some tracks with volume_pan + paramod and a block size of 128 I can, it's much smoother (no zipper noise in any case though).

[musicbynumbers]

Thanks for the reply schwa

so it seems you are saying this is the same in all daws?

I'm sure I remember the time when people were raving on about sample accurate automation?

maybe I'm confusing the issue?

[Xenakios]

Originally Posted by musicbynumbers

Thanks for the reply schwa

so it seems you are saying this is the same in all daws?

I'm sure I remember the time when people were raving on about sample accurate automation?

maybe I'm confusing the issue?

More or less sample accurate automation is possible with VST plugins but with tradeoffs. AFAIK AudioUnits and RTAS/TDM have the capability at the plugin spec level. Implementing sample accurate automation in the host for volume, pan and send levels is quite trivial.

[dasdeck]

Originally Posted by schwa

Parameter modulation, like any FX parameter move (including moving a knob on the GUI or moving a physical controller), is sent once per buffer block, that's unfortunately not something that anybody can change. Well-designed plugins will interpolate parameter moves internally to avoid zippering, for example if a filter plugin advertises "smooth sweeps" that's what they mean. For volume and pan parameter modulation, JS/utility/volume_pan does internal smoothing.

If you have a plugin that you want to modulate but you hear zipper noise, you will need to lower the buffer size.

i fully understand you, but you could break the original buffer wich is dictated by the driver into parts to gain better resolution. afaik you already break the buffer size on loop jumps.