u-he

FastTriggerFish · Post by **FastTriggerFish** » Fri Feb 22, 2019 10:44 am

Just wondering as I imagine they use delay lines internally ?

EvilDragon · Post by **EvilDragon** » Fri Feb 22, 2019 11:23 am

No. Well, all u-he plugins by default incur a latency of 16 samples, but you can disable that in preferences.

FastTriggerFish · Post by **FastTriggerFish** » Fri Feb 22, 2019 12:06 pm

I wouldn’t be so sure it’s the same as all uhe plugins - intuitively changing tuning would require changing playback speed which requires a buffer / delay line. Wondering if it’s big enough to be an issue for tracking or not.

FastTriggerFish · Post by **FastTriggerFish** » Fri Feb 22, 2019 12:10 pm

I meant pitch rather than tuning.

EvilDragon · Post by **EvilDragon** » Fri Feb 22, 2019 1:00 pm

What if it isn't a delay line?

Urs · Post by **Urs** » Fri Feb 22, 2019 1:13 pm

Maybe Sascha can chime in, but I'm quite sure Satin has typically more than 16 sample latency due to all the filtering, wowing and fluttering going on.

EvilDragon · Post by **EvilDragon** » Fri Feb 22, 2019 1:37 pm

Says 22 samples when base latency is enabled.

Ploki · Post by **Ploki** » Fri Feb 22, 2019 3:11 pm

man i always forget i can use Satin as a delay... i have to add it under my delays folder.

anyway, 22 samples here in logic too

cthonophonic · Post by **cthonophonic** » Fri Feb 22, 2019 7:47 pm

Trying to null out Satin by mixing with a delayed, inverted dry signal, I get the quietest least comb-y output with the following delays:

22 samples at 0% wow/flutter
42 samples at 25%
61 samples at 50%
80 samples at 75%
99 samples at 100%

This is in Jeskola Buzz, which is not seeing any latency reported by Satin, so no latency compensation to complicate the results.

FastTriggerFish · Post by **FastTriggerFish** » Fri Feb 22, 2019 8:01 pm

Wow thanks a lot for taking the time to do that test !
Seems qualitatively consistent with what I expected, probably a bit much for tracking but quite reasonable overall.

cthonophonic · Post by **cthonophonic** » Fri Feb 22, 2019 9:35 pm

No problem!

Ploki · Post by **Ploki** » Fri Feb 22, 2019 11:21 pm

0,5ms a bit much for tracking? nah

FastTriggerFish · Post by **FastTriggerFish** » Fri Feb 22, 2019 11:33 pm

100 samples at 48khz is 2 ms, you're right it's not terrible but it adds up to the other latencies etc.

sascha · Post by **sascha** » Mon Feb 25, 2019 3:51 pm

If you switch off the base latency, Satin adds only 6 samples (with base latency it's 22).

The wow&flutter test is pretty pointless, as w&f isn't a static process. Like with an LFO, it depends on the momentary excursion, and that not only depends on amplitude but also on the rate. So it's speed-dependent. And since w&f is not only one single frequency (Satin also uses multiples and odd frequencies to mimic scrape flutter, although to a minor degree), there's never a 'compensation' that would work.

You can trust the reported additional 6 samples (or 22, likewise) for things like tracking. But really, when you want to mimic transport fluctuations in realtime you just can't trick physics.

FastTriggerFish · Post by **FastTriggerFish** » Mon Feb 25, 2019 4:25 pm

Thanks a lot Sascha, yes I guess what I was trying to get at is what are the average and worst case transport delays.

u-he

KVR Audio

Do Satin’s wow and flutter add latency?