latency reported by VST plugin
That's a good idea.
If the latency is noticable, though, isn't that going to be a pretty big problem for live performing anyways?
If the latency is noticable, though, isn't that going to be a pretty big problem for live performing anyways?
I guess any latency is bad for live performance,especially when you are using realtime instruments. On the other hand latency barely needs to be noticable to cause phase issues in the case where for example you might want to process your audio through two VST's in parallel and one of the VST's delays the audio by 1.5 ms and the other VST doesn't. This is when you would possible want to compensate by delaying the non delayed signal to match the delayed signal. Otherwise 1.5ms would normally be unnoticable.
Also, if the VST had a latency value output in Usine, then assuming the plugin reports its latency at all,or even correctly, it would make it easy to see if a plugin had too much latency for the specific application without having to build a test with a phase inverted delay module.
Also, if the VST had a latency value output in Usine, then assuming the plugin reports its latency at all,or even correctly, it would make it easy to see if a plugin had too much latency for the specific application without having to build a test with a phase inverted delay module.
I suppose it would be sensible to combine this suggestion with suggesting a send latency to host module for the vst version of Usine...?
...and maybe a number-of-samples delay (not milliseconds) module to go with it...? (And yes, I know there are free VSTs doing this already.)
Bjørn S
yes good idea.
Olivier Sens
www.brainmodular.com
www.brainmodular.com
Very good idea, I´d like to have this, pretty essential feature for me...
Sorry for my bad english :/
Maybe the buses could also have a latency out pin? Then latency information from the buses could be dynamic depending on bloc size (or any other factors?)
And slightly off topic, but would it be possible to have an "invisible wire" mode for buses so that they would add no latency when used within a single track but still be name selectable, unlike a normal wire?
And slightly off topic, but would it be possible to have an "invisible wire" mode for buses so that they would add no latency when used within a single track but still be name selectable, unlike a normal wire?
-
damstraversaz
- Member
- Posts: 159
- Location: Chambéry
- Contact:
that's could be very useful. actually, I load each fx on reaper before using it for stage. reaper have a very nive latency report.
Has anyone else tried the new latency out pin on VST's yet? I can't get any value other than 0 to a delay module when connecting to the delay in pin. Am I doing something wrong?
-
martignasse
- Site Admin
- Posts: 611
- Location: Lyon, FRANCE
- Contact:
you have to start the latency test with the new button 'test latency' i guess, tested and ok for megurulogic wrote:Has anyone else tried the new latency out pin on VST's yet? I can't get any value other than 0 to a delay module when connecting to the delay in pin. Am I doing something wrong?
Martin FLEURENT - Usine Developer - SDK maintainer
Ok, I had first tried with a button connected to the latency test pin and it did nothing. If I use a switch instead I get results but mostly they are way off, for example, U-He MFM2 displays alatency of 16ms but if I measure with delay modules and a phase inverter, MFM2 has a latency of .4ms.
usine makes a latency estimation:
the procedure is:
1) clear the vst buffer (as much as possible)
2) send a sound to the vst,
3) wait until the sound comes out and calculate the delay.
most of vst have a 0 latency, that's probably why you have a 0 result.
also the latency depends on effect itself:
- a FFF filter can have up to 4086 samples.
- a look ahead limiter 50 samples,
- a traditional filter 0 samples.
so if you you use a multi fx, the latency can depends on the fx chain and the kind of fx you use.
the procedure is:
1) clear the vst buffer (as much as possible)
2) send a sound to the vst,
3) wait until the sound comes out and calculate the delay.
most of vst have a 0 latency, that's probably why you have a 0 result.
also the latency depends on effect itself:
- a FFF filter can have up to 4086 samples.
- a look ahead limiter 50 samples,
- a traditional filter 0 samples.
so if you you use a multi fx, the latency can depends on the fx chain and the kind of fx you use.
Olivier Sens
www.brainmodular.com
www.brainmodular.com
I thought the latency was supposed to be reported by the plugin to the host?
Bjørn S
Who is online
Users browsing this forum: No registered users and 82 guests
