delay timing in ms/bpm

[tomylee]

hi, does anyone know why all the delay times are wrong with mos of the delays? they are inaccurate even when a specific millisecond amount is entered, is there a work around or are there any delay devices that are precise?
thx for advice
t

[wayne]

AFAIK delay time changes with ULLI settings

[Fluxpod]

AFAIK delay time changes with ULLI settings

No.Thats Latency and it only affects asio-wave communication.

The Delays probably work fine,be sure to set the correct time Signature.

Which delays are not working for you?

[tomylee]

the stock delays, it is known bpm values are not correct but I was wondering why even the millisecond setting changes with different ulli setting, milliseconds have nothing to do with ulli imho...

does anyone have further explanations on that matter?

[next to nothing]

AFAIK ULLI does affect timing. At least there are delays where you choose what your ULLI is set to, and the devices adjusts timing accordingly (SpaceF devices). I the old SpaceF echo-days you had to specify your ULLI setting upon getting the device, nowadays there is a switch so you can change settings "in realtime".

[wayne]

A few relevant posts...

http://forums.planetz.com/viewtopic.php ... ulli+delay

http://forums.planetz.com/viewtopic.php?f=1&t=22364

http://forums.planetz.com/viewtopic.php ... ay#p222564

[Fluxpod]

That is extremly odd.Never had that Problem but then...i dont use the asio-wave driver.That is not normal Behaviour.Should be reported to sc.And if that is normal then it sucks ass bigtime.What if you decide to switch latency around mid project? Never heard of any system that binds driver latency to delay times...

[tomylee]

yeah, it is an ancient bug it seems, never got adressed by anyone...but maybe it is due to the fact that audio needs to be routed from scope to ram and back, latencies occurr, it just seems like scope is not able to report them properly