KVR Audio is the Internet's number one news and information resource for open standard audio plugins. We report new releases, product announcements and product updates (major and minor) for all VST Plugins, DirectX Plugins and Audio Units Plugins. We manage a fully searchable audio plugin database (updated daily), and offer many free member services including user reviews, product update notifications and a very active discussion forum. We also host official support forums for many plugin developers plus the official Receptor support forum.
Plug-in Database: Virtual
Instruments, Effects & Hosts
Banks & Patches
Download & Upload
Plug-in Ratings
by KVR Members
Wiki: Tutorials,
Audio Lexicon, ...
Listen to Music
by KVR Members
Search
KVR

Google Powered Search:

in new window

KVR Powered Plug-in Search:

AuthorTopic: Measuring plug-in latency
Evan
Posted: 1st September 2003 07:31
Is there an easy way to measure a VST-DX plug-in's latency in samples?

Thanks
kritikon
Posted: 1st September 2003 12:34
I'm sure there is but I don't know how. Personally I do it the hard way and record to audio then zoom in and look in the audio editor for msecs.

Interestingly enough I was exporting a drum group a few days ago - I was quite horrified at the delays I got - putting the drums through the Triplecomp from Sinus (I must buy that - a lovely comp) and some TC Eq, I got a delay of just over 20mSecs. I think alot of that was from the triplecomp (it uses read ahead for peak-spotting), but it certainly put me off using my group channels as much for running stuff directly to the final mix - After that I started to render all the groups to audio to get rid of the delays. I hate to think what the delays are on some of the other plugs!
IP
Posted: 3rd September 2003 01:29
For read-ahead plugins for example, Waves L1 or L2
measure latency usually impossible becuase delay is inside
algorythm but:
make wav file, with first sample is impulse with amplitude 0dB,
load sound forge, apply plugin and you will see latency in zoom mode with
and select samples as show units.

As for plugins based on Fast Fourier Transform, you can easy calculate latency withL FFTsize and Overlap value:
for example, FFTsize = 1024, Overlap value 4 or 25% usually (overlap 2=50%), So latency= FFTSIZE-FFTSIZE/OVERLAP = 1024-1024/4 = 768 samples. You can try that method with impulse as well.
Good luck
Forum topics in the archive are read only. New posts should be made in the main KVR Forums.
Disclaimer:
All communications made available as part of this forum and any opinions, advice, statements, views or other information expressed in this forum are solely provided by, and the responsibility of, the person posting such communication and not of kvraudio.com (unless kvraudio.com is specifically identified as the author of the communication).