Auto-latency comp./plug-in loaderr (dry/wet mix-effects)

Request a new device/modular module, and hope that some enterprising developer grants your wish!

Moderators: valis, garyb

Post Reply
voidar
Posts: 1264
Joined: Sun Aug 18, 2002 4:00 pm
Location: Norway

Auto-latency comp./plug-in loaderr (dry/wet mix-effects)

Post by voidar »

More of an idea for developers really, somewhat inspired by the GuStaff plug. I might be able to do this myself, but I am a real SDK newbie. So...

What about a device (hereby refered to as host-device) that would load a device, ping-pong it and thus calculating the sample-offset that a device might, for any reason (DSP-spread etc.), introduce.

This host-device would also have a dry/wet-mix controll.

The host-device would be usefull for sample-coherent parallell processing, i.e. if I wanted to load a Vinco in this host-device, the dry output would be delayed an n-th amount of samples based on the time it takes for the ping to pass through Vinco.

A proceedure should be executed when a device is loaded in the host-device, and/or a "recalculate/reset"-button is pressed .

1. Host-device mutes own outputs.
2. Host-device pings hosted device (ideal ping-signal must be experimented with).
3. Host-device counts hosted device' processing-time in samples: "processing-time" = pong - ping
4. Host-device delays own dry/through-output by "processing-time".
5. Host-device un-mutes own outputs.

Host-device would come in mono and stereo.

Ideally, developers would incorporate this proceedure in their own devices so that on each project reload, project optimization etc., dry/wet relationship would be in sync..
Many a device could benefit from a dry/wet controll :).
User avatar
Shroomz~>
Posts: 5669
Joined: Wed Feb 23, 2005 4:00 pm
Location: The Blue Shadows

Post by Shroomz~> »

In theory it should be possible to build a modified insert slot that does something along these lines. The main issue is that in SFP plugs will load onto different dsps or even different boards (if you have 2 or 3 cards) depending on what devices are already in your project & where they are placed dsp wise. That goes for standalone scope devices as well as insert FX. So my point is that there will never be a set latency for a set plug, as it will often be different or change from one project situation to another. That doesn't mean that a device which measures latency would be useless, it just shines a different light on how it would eventually work & be used.
User avatar
Shroomz~>
Posts: 5669
Joined: Wed Feb 23, 2005 4:00 pm
Location: The Blue Shadows

Post by Shroomz~> »

This has been bugging me Voidar.

Anyone building this yet?
User avatar
Shroomz~>
Posts: 5669
Joined: Wed Feb 23, 2005 4:00 pm
Location: The Blue Shadows

Post by Shroomz~> »

I've got a solution which works really well, but only with insert capable effects & only effects which allow a completely clean unaltered dry sound without using the bypass switch (many effects are latency free when bypassed). Working on a different solution which works for all effects including those which always colour. Strangely 14 samples seems like the most common latency.
User avatar
Shroomz~>
Posts: 5669
Joined: Wed Feb 23, 2005 4:00 pm
Location: The Blue Shadows

Post by Shroomz~> »

Post Reply