osxmidi / LinVst

Linux Windows vst wrapper/bridge
GNU General Public License v3.0
683 stars 41 forks source link

Waves plugins don't report latency #38

Closed lentferj closed 6 years ago

lentferj commented 6 years ago

Don't know if this is an issue with Waves plugins or linVST/WINE. As far as I can tell none of the Waves plugins report plugin latency (checked in Ardour via "Edit with simple controls") even those that do have audible latency (Kramer HLS adds about 3.35ms of latency measures with LSP latency meter and tested in Mixbus parallel processing). Other plugins like IK Mulimedia Black 76 or Toonebosters Barricade v4 do report their latency.

lentferj commented 6 years ago

I tried with extracting the plugins with shell2vst.exe, but still no latency (or rather 0 samples reported when their obviously is latency) reported via "simple controls".

osxmidi commented 6 years ago

LinVst does handle latency, so I'm not sure why it's not working with Waves.

lentferj commented 6 years ago

I had some friends check the latency reporting in Mixbus on Mac and Win just to make sure, and there it works (e.g. J37 Master Tape).

lentferj commented 6 years ago

Closing this now means "won't fix"?

osxmidi commented 6 years ago

No, I'm still aware of it but right now Waves Central is broken in Wine Staging 3.12 and 3.13 so I'm trying to fix that and then I'll test some Waves plugins out.

Waves plugins should be no different to others when reporting the latency, so I'll see what happens.

lentferj commented 6 years ago

Very cool, thank you very much in advance. I created a list of Waves plugins and measured latency, if it helps.

osxmidi commented 6 years ago

I think I realize what's happening.

It seems to be a timing thing where the Waves plugin initially report 0 latency when the DAW first calls the Waves plugin but then the Waves plugin seems to update the latency afterwards and so the DAW misses it.

If I put in a latency printout when the GUI opens (much later than when the DAW first calls the Waves plugin for the latency) then the Waves plugin reports a latency that is not 0.

I'll see what I can do about implementing a later latency call for the Waves plugins.

osxmidi commented 6 years ago

I've done some changes to the code.

Reaper seems to report the Waves plugin latency ok now.

lentferj commented 6 years ago

Great. I'll compile from source and give you feedback on behaviour in Ardour/Mixbus later today!

lentferj commented 6 years ago

I can confirm latency reporting works now in Mixbus and the numbers are very close to what I previously measured with LSP latency meter. Great work! Thanks a lot... Waves plugins have suddenly become actually useful ;)

Schroedingers-Cat commented 3 years ago

Using the latest release of LinVst, plugins from Voxengo and DMGAudio don’t seem to report any latency to Reaper v6.25. Tested with Voxengo Soniformer 3.12 and DMGAudio Multiplicity 1.07. Any idea why it’s not working? Native plugins from u-he report their latency just fine and even change it depending on plugin settings.