Send/Return plugin detecting latency

[Nofolobricity]

Hi!

Does anyone know a plugin that can:
1. Send impulse to a physical output
2. Receive this (sended) signal from a physical input
3. To compare two signals and report the latency (in ms or samples) between sended and received singals?

[whyterabbyt]

No 3rd-party plugins; there are DAWs which have this functionality built-in, for supporting hardware effects use.

Why do you need this as a plugin?

[Nofolobricity]

No 3rd-party plugins; there are DAWs which have this functionality built-in, for supporting hardware effects use.

Why do you need this as a plugin?

Cuz I use FL Studio

[whyterabbyt]

It can be done manually though. here's a description for audacity but the method can be used in anything.

https://manual.audacityteam.org/man/latency_test.html

are you expecting to change what you're sending through particularly frequently?

[Nofolobricity]

It can be done manually though. here's a description for audacity but the method can be used in anything.

https://manual.audacityteam.org/man/latency_test.html

are you expecting to change what you're sending through particularly frequently?

Thank you! I've got the idea of those experimets. Seems like it's the only way to compensate latency

[whyterabbyt]

Yeah, if the host doesnt support it, manual measurement is your only option.

However, I forgot to mention there is a plugin which can apply a latency offset for you, if the host wont...

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

[Unaspected]

That's funny. I wrote something that does this for reporting latency in Reaktor modules the other day. It might be possible to adapt it to work with other plugins and round trip signals - main issue would be ensuring sync. It would certain extend its use - to capturing IRs from third party plugins - so I might take a look at that at a later date.

I'm happy to upload the module as it is at present if anyone is interested.

[Nofolobricity]

Yeah, if the host doesnt support it, manual measurement is your only option.

However, I forgot to mention there is a plugin which can apply a latency offset for you, if the host wont...

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

Thank you! I've tried it already, and id didn't solve the problem

[Nofolobricity]

That's funny. I wrote something that does this for reporting latency in Reaktor modules the other day. It might be possible to adapt it to work with other plugins and round trip signals - main issue would be ensuring sync. It would certain extend its use - to capturing IRs from third party plugins - so I might take a look at that at a later date.

I'm happy to upload the module as it is at present if anyone is interested.

Sounds very interesting! I think it would be nice to test it

[Unaspected]

That's funny. I wrote something that does this for reporting latency in Reaktor modules the other day. It might be possible to adapt it to work with other plugins and round trip signals - main issue would be ensuring sync. It would certain extend its use - to capturing IRs from third party plugins - so I might take a look at that at a later date.

I'm happy to upload the module as it is at present if anyone is interested.

Sounds very interesting! I think it would be nice to test it

https://unaspectedstudios.com/sharing/R ... rement.mdl

There you go! A quick video explaining what it does in its current state and a direct link to the Reaktor module.

This is essentially a building block that could be developed further to be capable of what you wish to do - which I detail a little more in the video. For my own uses, I just need to be sure that parallel paths in processing modules sync up inside Reaktor so I never contemplated passing it out of the box and then back in - but it should be possible to make that work - depending on the DAW and getting the audio routing set up so the write and read channels hook up to the table whilst the impulse is sent as normal, through the next mixer insert.

Otherwise, it's a simple tool for testing latency inside Reaktor.

I think I forgot to mention setting the table size in its properties to match that of the table size input of the delta function core module. By default it has been set to 64 samples. Full instructions are in the info section for the module.

If the impulse comes back smeared and buried, then the logic test "Find Delta" might break even if using the "Sensitivity" parameter. Though you can still observe by eye and manually scan through using a dial with an upper value equal to the table size until you hit the highest value. I might build something more intelligent to solve that problem in the future.

Enjoy!

[Unaspected]

Cuz I use FL Studio

I should probably add that that FL Studio's Convolver has a feature for triggering an impulse and capturing the response but I'm not sure you will get a sample accurate result from this.