Bitwig

iONikbeats · Post by **iONikbeats** » Wed Apr 02, 2014 10:46 pm

UAD PLUGINS!!!!!

ObsoleteAcc99 · Post by **ObsoleteAcc99** » Thu Apr 03, 2014 1:55 am

[DELETED]

Echoes in the Attic · Post by **Echoes in the Attic** » Thu Apr 03, 2014 9:59 pm

TheoM wrote:
Simulant wrote:What happens when oversampling is enabled on a VST? I'd heard that this can cause incorrect PDC, is this true?
Unfortunately this is true and it doesn't matter how good the host is at PDC, as many plugins with OS enabled become un-syncable.

There is a way around it, and that is for the vendor to use linear phase oversampling which reports the latency accurately, even if it is a little higher by using linear phase filters. I enable this on all my voxengo plugins for example otherwise they don't compensate properly when in OS mode.

(just answering this as it has nothing to do with bitwig itself at all, all hosts are affected by the vendor's choice of oversample method).

This is only a concern where the plug-in actually induces latency I assume. It doesn't matter if a plug-in is oversampled but has no additional latency right?

ObsoleteAcc99 · Post by **ObsoleteAcc99** » Fri Apr 04, 2014 3:17 am

[DELETED]

u-u-u · Post by **u-u-u** » Fri Apr 04, 2014 9:50 am

I'm wondering why there is no standart that every plugin reports ist latency itself.

Also I can see that the VST standart isn't very good. Not for developers AND users.
Hopefully the future will bring something better and more reliable than VST that's easier to implement.

Simulant · Post by **Simulant** » Fri Apr 04, 2014 10:53 am

u-u-u wrote:I'm wondering why there is no standart that every plugin reports ist latency itself.

Also I can see that the VST standart isn't very good. Not for developers AND users.
Hopefully the future will bring something better and more reliable than VST that's easier to implement.

Totally agree. The VST "standard" doesn't seem like a standard at all. Every plugin seems to want to install somewhere different, some don't like being moved, some don't work with certain hosts etc. It's a pain in the ass to get everything working smoothly, when we should just be able to install and forget about them.

Costa Rica · Post by **Costa Rica** » Fri Apr 04, 2014 6:07 pm

Oh dear.. there we go. What these VST farmers need is eh kick somewhere. Such expensive biz can't come up with their own standard.. obviously they need a VST Napoleon to fix that standard for them

jaredf · Post by **jaredf** » Tue Apr 08, 2014 6:51 pm

Maybe I missed something but how do you find out the latency of your plugins?

I'm looking in some of my instruments manuals and I can't find anything.

Clearscreen · Post by **Clearscreen** » Sat Apr 12, 2014 5:54 am

From the Plugin Alliance DSM manual...

Total processing delay Pro Tools.
44.1KHz & 48Khz: 48 samples
88.2KHz & 96KHz: 96 samples
176.4KHz & 192KHz: 192 samples
Total processing delay Audio Units.
44.1KHz & 48Khz: 52 samples
88.2KHz & 96KHz: 104 samples
176.4KHz & 192KHz: 208 samples

psycha0s · Post by **psycha0s** » Wed Apr 16, 2014 12:39 pm

Costa Rica wrote:Oh dear.. there we go. What these VST farmers need is eh kick somewhere. Such expensive biz can't come up with their own standard.. obviously they need a VST Napoleon to fix that standard for them

The VST standard (at least v 2.4) is really not good. Official documentation doesn't explain a lot of important things (threading, GUI event handling, etc), so every plugin/host developer running through trial and error.

Klinke1 · Post by **Klinke1** » Sun Jul 27, 2014 6:24 am

The manuals of alot VSTs do not state the latency.

Some posts are deleted..but the whole thread is derailed.

Search the manual for PDC: Nothing.
How is it implemented?: Nothing.
Search it for latency: Nothing.
Not one word.
There is a "latency readout" in the mixer.
People new to the prog do NOT see it.

Bitwig

KVR Audio

Plugin latency overview