PlanetZ forums - scopeusers.com

Thought i'd expand on what roy was pointing out here. I'm sure it's been discussed before somewhere, but it would be good to get this fixed.

This goes for insert & standalone versions, as well as the modules roy is talking about.

Accurate - delay M, multitap M, delay S, delay LCR S, dual delay S

Inaccurate - delay LM, ducking delay M , ssb delay m, delay LS, delay LCR LS, dual delay LS, - all 215.17ms when they read 250ms.

Pattern Delay is elsewhere altogether.

Don't get me wrong, i like wrongness a lot, but not this kind


Lemmeseeyadodabump

how about the built-in delay effects of newer CWA synths like Minimax?
I can never set a properly timed delay on bpm in those and have to use the delay S inserted behind it instead

Stand down Red Alert - it's all about ulli. Short delays can deal with most settings. Long ones not so.

Roy Thinnes has pointed this out, spurred by Ben Walker's observation that spacef echo has many different ulli versions.

Moral of story - delay times weird? Drop your ulli gearbox back a cog, then step on gas

so...which ulli settings are safe to use? I'm using 7ms at 44.1 khz

Hello, in my system all tempo delays work right only at 24ms ULLI. (bigger setting). That is only related to the tempo division not the delay line as at free mode (ms) all ulli settings are fine. That also implies to all delays , (modular) etc..

i like delayed delays

most delays that show problems with high ulli settings (high in the scope window where you select them) probably work fine at the lowest ulli (34/25/23/12 ms). It is not related to samplerate.

Reversely, a delay that doesn't work at lowest ulli, will work at any other ulli.

This is a problem only when you want to synch delays with a tempo, because it will never be in time if not in the right ulli (it has a nicer effect @ 12 ms by the way, evnthough... unsatisfying)

It doesn't really matter if you don't synch to a tempo (ie use "manual delay time) because approximation can be desired (and is better if you can control it anyway).

I have a ulli setting on most of my devices. But working @ 25ms is a pain, i use 12ms which is the max I can go with my board. On some of my devices (LBH), I have removed ulli settings, because they are internally set to match any other ulli than the highest latency (ie the lower line, 34/25/23/12 ms).

I thought nobody would use the highest latency, but I guess I'll have to re-put this ulli settings where it is missing...