Delay FX questions/problems

In the delay Fx parameters when turning sync to ON, the delay should be synced to tempo right?

It seems to be working, but I'm confused how to use the beats.ticks for the delay time setting.

If I want the delay time to be one bar I should be entering 01.00 - correct?

I'm sure I'm doing something wrong because the delay time turns out to be something less then one bar.

Anyone else know something about this?

Peace.

the delay doesn't sync for me either so i'm using a good old calculator and enter the delay time in ms .
also remember that the delay time is 1 second maximum

decrepitude wrote:In the delay Fx parameters when turning sync to ON, the delay should be synced to tempo right?

It seems to be working, but I'm confused how to use the beats.ticks for the delay time setting.

If I want the delay time to be one bar I should be entering 01.00 - correct?

I'm sure I'm doing something wrong because the delay time turns out to be something less then one bar.

Anyone else know something about this?

Peace.

what you said there answers your own question. "beats.ticks" and "01.00"

if you want the delay time to be one bar, then 01 in the 'beat' section, isn't one bar, is it? it's one beat, my friend, and there are four beats in one bar.

Mr modnaR wrote:what you said there answers your own question. "beats.ticks" and "01.00"

if you want the delay time to be one bar, then 01 in the 'beat' section, isn't one bar, is it? it's one beat, my friend, and there are four beats in one bar.

Yeah, over night's sleep I knew I'd goofed in my explanation. Sorry for the confusion - I do know 04.00 is 4 beats.

Still, there is a problem.

I initially tried 04.00 which should be one bar, but it wasn't right at all. Then, I tried by dialing it in, knowing the time didn't jive with beats.ticks. It never synced right using the beats.ticks with sync on - the sweet spot (in my case for 158 bpm) is somewhere between 01.13 and 01.14. (That's probably where I was rembering 01.00)

So, I switched sync off and used tempo math which is 758 millisecs for one bar at 158 beats per minute. Now the delay is in perfect time with the beats, but if I want to switch tempo I'll be futzing with the delay time again.

I did a thorough search before posting this, including JOYS and PAINS threads, but only a tiny bit mentioned about the delay. To my knowledge, nothing has been posted about this particular problem yet.

Can anyone please confirm this? I'm suprised nobody else has come across this being it is a new feature of OS 2...

1.00 is not one bar because their are various tempeo.

Best bet, just figure it out, i did, it varies and does seem complicated but once you got it down, its all good from there.

sounds like there is some bug here...

but personally I have tried the Sync twice and im pretty sure it worked properly both times.

I'll start using it more often and see what i find.

sleepersriddle wrote:sounds like there is some bug here...

but personally I have tried the Sync twice and im pretty sure it worked properly both times.

I'll start using it more often and see what i find.

Personally I think it's buggy too, but it sounds nice so I don't mind so much /:

solah wrote:1.00 is not one bar because their are various tempeo.

Best bet, just figure it out, i did, it varies and does seem complicated but once you got it down, its all good from there.

Sorry - that's not correct. As I said...

... proper sync for 158bpm is somehwere between 1.13 and 1.14. 1.13 eventually shifts to being too early, and 1.14 eventually drifts to being too late.

Complicated? That would imply that one could eventually make sense of it. So, sorry - it's not all good. Unless you like living with tempo synced delays that are....NOT.

Same for me. I don't understand how this "sync" delay works...
Anybody out there has a solution ?

i played a little with delay and here are my confusing results.

(test scenario)

sequence - 4 bars
snare on 01:01:00

delay settings:

time: 1.00 - sync:on
feedback:00 - mode:pan
hf damp:00 - width:00
level:99 - pan:mid

(result tempo 30)

3 snare delays within ca. 01.01.00-01.01.20

(result tempo 300)

3 snare delays within ca. 01.01.00-04.04.00

i don't get it ...

well, if it is 1 second max delay time, i would say that would hinder things...as in no bar length delays, unless you are at 240 bpm or above...right?

maybe you guys already realized that...

Rough'nReady wrote:well, if it is 1 second max delay time, i would say that would hinder things...as in no bar length delays, unless you are at 240 bpm or above...right?

maybe you guys already realized that...

Uh - yeah. As I said earlier, a one-bar delay at **158bpm** is 758 millisecs, well under the max.

I'm an idiot. My apologies to Rough'nReady - he was on it.

My calulations were wrong. 1 bar at 158 is actually 1518 millisecs. 759 millisecs is actually equal to 2 quarter notes at 158bpm. Sorry for the confusion.

But really no matter - the sync is still goofy. But, I'm getting closer...

Maybe someone else can help figure this out...

OK. Sync on delay DOES work, but apparently the beats.ticks setting only starts to make sense when you are running at 60, 120, and 240 beats per minute. Well, almost...

So I did some experiments. Setting the beats.ticks to 01.00 for 240bpm yields an exact one-bar delay. (Actually, since the max delay is actually 999 millisecs ((not 1000)), the proper tempo for sync is 240.2 bpm.) The same 01.00 setting for 120bpm yields a half-bar (2 quarter notes), and as suspected the same 01.00 setting for 60bpm yields a quarter-note delay.

Based on the issue of the max delay time (999 msecs), any tempos above 240 (240.2 to be exact) shouldn't be a problem. If the beats.ticks setting *truly is* beats.ticks then 04.00 should yield a 4-quarter note delay at any tempo above 240bpm. (I know most people aren't gonna use 240bpm, but this is just for analysis.)

Unfortunately, even at 60, 120 and 240bpm (even 60.05, 120.1 and 240.2) the sync starts to drift. I'm starting to think SYNC isn't syncing to tempo at all but just some (obviously inaccurate) tempo calculation. I would imagine this has to do with the lack of extra precision in the time setting, and probably some numbers are getting rounded off.

Anyone else have any clues as to what's happening here?