Page 1 of 1
delay timing in ms/bpm
Posted: Thu Sep 13, 2012 10:40 am
by 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
Re: delay timing in ms/bpm
Posted: Thu Sep 13, 2012 4:17 pm
by wayne
AFAIK delay time changes with ULLI settings
Re: delay timing in ms/bpm
Posted: Thu Sep 13, 2012 5:13 pm
by Fluxpod
wayne wrote: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?
Re: delay timing in ms/bpm
Posted: Fri Sep 14, 2012 4:46 am
by 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?
Re: delay timing in ms/bpm
Posted: Fri Sep 14, 2012 5:42 am
by 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".
Re: delay timing in ms/bpm
Posted: Fri Sep 14, 2012 6:59 pm
by wayne
Re: delay timing in ms/bpm
Posted: Sat Sep 15, 2012 9:16 am
by 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...
Re: delay timing in ms/bpm
Posted: Sat Sep 15, 2012 10:36 am
by 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