Automatic PDC???

[Trancit]

As far as I know, there is no automatic plugin delay compensation in Mu.Lab, right???

Are there any plans on it, Jo???

For me, biggest problem is, how to manually delay other tracks (without trial and error), if I don't know how much latency is introduced by the plugin???


Trancit

[> DiGiT <]

check this out

http://www.voxengo.com/product/latencydelay/

[Trancit]

check this out

http://www.voxengo.com/product/latencydelay/

I don't think, that this an option for me...

From the website:

Latency Delay introduces 10000 samples latency itself and delays the audio signal by 10000 minus the specified amount of samples or milliseconds.

I don't want to add additional 10000 samples, if I perhaps only need a few...

And most important:

Please note that host audio application should support the latency compensation itself for this plug-in to function properly.

So, we are back to the same problem like before...


Trancit

[MuTools]

As far as I know, there is no automatic plugin delay compensation in Mu.Lab, right??? Are there any plans on it, Jo???

Auto pdc not yet on the M4 wishlist just because i must keep the M4 wishlist realistic, otherwise M4 would take too much time (which it already does).
Auto pdc is on the gobal wishlist though.

Manual pdc is already possible, but i'm open to add some extra support where needed in order to better support manual pdc. Which leads us to your next question:

For me, biggest problem is, how to manually delay other tracks (without trial and error), if I don't know how much latency is introduced by the plugin???

Please try this: Open the Mulab/User/Settings/VstPlugins.Xml and lookup the respective plugin and note the InitialDelay value. That should be the number of samples of delay.

Now we just need to insert a delay at the proper point in the audio path so all other audio is also delayed by that amount. I'm sure there is a Vst plugin that can handle that job.

Does this help?

[robenestobenz]

Latency Delay introduces 10000 samples latency itself and delays the audio signal by 10000 minus the specified amount of samples or milliseconds.

I don't want to add additional 10000 samples, if I perhaps only need a few...

Use their Sounddelay instead.

Developers should really state the delay of plugins somewhere, but if not you can use Christian Budde's awesome VST analyser to find it out. Load the plugin in the analyser, go to window>log and "initial delay" is the number of samples latency the plugin operates at.

[Trancit]

Please try this: Open the Mulab/User/Settings/VstPlugins.Xml and lookup the respective plugin and note the InitialDelay value. That should be the number of samples of delay.

Now we just need to insert a delay at the proper point in the audio path so all other audio is also delayed by that amount. I'm sure there is a Vst plugin that can handle that job.

Does this help?

This helps, but would be nice to have the value visible somewhere in the programm...


Trancit

[> DiGiT <]

Latency Delay introduces 10000 samples latency itself and delays the audio signal by 10000 minus the specified amount of samples or milliseconds.

I don't want to add additional 10000 samples[/quote]

you add up to 10000 samples

once you delay a dry signal to meet the same latency as the wet signal, both will be delayed the same ammount, at least taking care of phasing issues. isnt that what we want? so its a partial solution. but i challenge you to identify which tracks in a composition are delayed by such a small delay if phasing is not an issue.

[MuTools]

This helps, but would be nice to have the value visible somewhere in the programm...

Yes, will do.

And i'll also add a straight audio delay, so all tools for manual pdc are in there. Should be possible for M4.

[> DiGiT <]

wont that clutter up the interface tho?

[robenestobenz]

Latency Delay introduces 10000 samples latency itself and delays the audio signal by 10000 minus the specified amount of samples or milliseconds.

I don't want to add additional 10000 samples

you add up to 10000 samples

once you delay a dry signal to meet the same latency as the wet signal, both will be delayed the same ammount, at least taking care of phasing issues. isnt that what we want? so its a partial solution. but i challenge you to identify which tracks in a composition are delayed by such a small delay if phasing is not an issue.

It's the wrong plugin for the job. Latency delay is for using after plugins that don't report latency to the host. MuLab doesn't presently do anything with the latency reported anyway (no PDC), so Sounddelay's the Voxengo plugin to use for the task.

wont that clutter up the interface tho?

Bit harsh?

[MuTools]

wont that clutter up the interface tho?

You're joking, right?

[> DiGiT <]

maybe a little. harsh? i didnt think so. it is a genuine concern, no?

by the way, either plugin will accomplish the exact same thing. the only reason for delay compensation is so there isnt phasing. it doesnt matter what sort of plugin you use as long as it delays the dry signal the exact amount you need to remedy the phasing introduced by the latency of your plugins process

[robenestobenz]

maybe a little. harsh? i didnt think so. it is a genuine concern, no?

by the way, either plugin will accomplish the exact same thing. the only reason for delay compensation is so there isnt phasing. it doesnt matter what sort of plugin you use as long as it delays the dry signal the exact amount you need to remedy the phasing introduced by the latency of your plugins process

But you have to do the subtracty thing, and Voxengo's own page says it won't behave correctly in hosts without PDC.

Harsh; I think it was the rolleyes. Maybe it's a KVR thing, I dunno, but I never see them used around here to denote anything other than sarcasm, condescension or disapproval.

[> DiGiT <]

oh sorry if your delicate feelings got hurt. seriously please just chuckle and move on.

the 'subtracty thing'? lol ok if you call it that its all good.

what they are saying, is that once you delay the dry signal, BOTH signals will be delayed unless theres PDC. sheesh. but even if im wrong, YOU GET THE POINT

[MuTools]

wont that clutter up the interface tho?

You're joking, right?

DiGiT, you were joking, right?

If not, then could you please explain why you think adding the two pdc things i mentioned could clutter up the interface? Thanks.