Voxengo Premium Membership - All Voxengo Plugins For a Fixed One-Time Fee
Forums     Discussions     Announces, Releases and Discussions VST3 latency change on the fly (FIXED)


Last

Next

Previous

First



Hi Aleksey,

seems like your VST3 versions don't inform the host when changing Lin-Phase/Lin-Phase modes:

http://forum.cockos.com/showpost.php?p=1560788&postcount=16

schwa:

I think the plugin is supposed to notify the host when latency changes on the fly, via IComponentHandler::restartComponent(kLatencyChanged).  GlissEQ doesn't seem to send that notification.  I'll drop Alexsey a line.

FIXED (REAPER 5.01)


It's a known issue, can't be resolved, because Steinberg hosts hang up when IComponentHandler::restartComponent(kLatencyChanged) is called from the audio thread.

It can be solved by bypassing the plugin in host's plugin chain.

Bypassing in REAPER doesn't work.  Offlining does.  No big problem.  But why not implementing this feature (for 3rd party hosts) and just don't send this notification in Steinberg hosts?  So all could be happy.

FIXED (REAPER 5.01)


Dandruff: Bypassing in REAPER doesn't work.  Offlining does.  No big problem.  But why not implementing this feature (for 3rd party hosts) and just don't send this notification in Steinberg hosts?  So all could be happy.

It's unreliable.  If Steinberg wasn't able to do it, chances are other vendors may not do it as well due to VST3 architecture features.


On the other hand, latency of VST2 plugins in Reaper can be updated by stopping/restarting the playback.  But strangely, Reaper does not react on VST2 "ioChanged" event from the plugin.  Is there a chance it will react on VST3 event?  Real-time latency are more or less well implement in AudioUnits only.  Most VST hosts treat plugin's latency events as inexistent.

Dandruff: Bypassing in REAPER doesn't work.  Offlining does.  No big problem.  But why not implementing this feature (for 3rd party hosts) and just don't send this notification in Steinberg hosts?  So all could be happy.

Aleksey Vaneev: It's unreliable.  If Steinberg wasn't able to do it, chances are other vendors may not do it as well due to VST3 architecture features.

Or only send the notification for REAPER?


Aleksey Vaneev: On the other hand, latency of VST2 plugins in Reaper can be updated by stopping/restarting the playback.  But strangely, Reaper does not react on VST2 ''ioChanged'' event from the plugin.  Is there a chance it will react on VST3 event?  Real-time latency are more or less well implement in AudioUnits only.  Most VST hosts treat plugin's latency events as inexistent.

Not sure what you mean by this exactly.  What is "ioChanged" doing?


Aleksey Vaneev: On the other hand, latency of VST2 plugins in Reaper can be updated by stopping/restarting the playback.  But strangely, Reaper does not react on VST2 ''ioChanged'' event from the plugin.  Is there a chance it will react on VST3 event?  Real-time latency are more or less well implement in AudioUnits only.  Most VST hosts treat plugin's latency events as inexistent.

Dandruff: Not sure what you mean by this exactly.  What is ''ioChanged'' doing?

From VST2 spec: "Tell Host numInputs and/or numOutputs and/or initialDelay (and/or numParameters: to be avoid) have changed"


Ok, posted at http://forum.cockos.com/showthread.php?t=165248

schwa said he also sent you an email, maybe you can solve this with him directly?

This topic was last updated 180 days ago, and thus it was archived.  Replying is disabled for this topic.

Last

Next

Previous

First