posted 02 November 2005 22:55            

QuantizeTimeline.ktl

I'm a little confused with trying to quantize resuming WaitUntils to the beat in a timeline. I'm using a WaitUntil with the following in Resume:

!KeyDown alignWith: (1 bpm: !BPM)

If you look at the attached timeline you'll see two sets of audio files in the tempo of the timeline. If you listen to tracks one and two together, when you resume the time with a !KeyDown, track 2 plays in unison with track 1, instead of launching at the beginning of the file on the next beat. I don't know if this is clear - I think you'll have to listen to the timeline to see what I mean (Also, there is some phasing on my system when I do it, which I do not hear if I line them up to start together at beat 1-1-0 and play them - this is peripheral, but I wonder why that is).

Now, if you mute the first two tracks and listen to tracks 3 and 4, they behave differently (the only difference is that tracks 3+4 are sample modules, while 1+2 are generic source modules, playing from RAM). On !Keydown, the resume begins right away and they don't seem to be quantized together.

First, is my syntax right for the resume (just checked, and it works the same with just !KeyDown in resume, so I assume it's not working)?

And am I missing something obvious about the difference between the Generic Source (with RAM selected) and the Sample modules that explains their different behavior?

thanks,
Phil

posted 03 November 2005 11:12            

PhilCurtiswaitUntilTimeline.ktl

Rather than allowing the Samples free-loop, I tried tying them to the same BPM by placing the following the Gate or Trigger field:

(1 bpm: !BPM) triggerEvery: 8

I also changed the quantization of the Timeline to 1/2048th of a beat and made certain that the two samples and the WaitUntil were aligned (they were a tiny bit off but I doubt that was the problem).

posted 03 November 2005 12:31            

But I'm still confused about why the second sample , when it comes in, comes in not at the beginning of the audio file, but in unision with the first audio file, wherever it happens to be in its cycle when I hit the !KeyDown to resume the WaitUntil. What would I do if I wanted the file that starts with the WaitUntil to start at the beginning of the file, quantized to the nearest beat after I resume the clock?

posted 03 November 2005 15:07            

That way, when you resume the WaitUntil, the second pair of samples will start at the beginning of their files.

posted 03 November 2005 15:49            

quote:

---

Originally posted by SSC:
With identical files like this, any time offsets will cause phase cancellation and filtering. But I am assuming that your final example won't have identical signals in the second pair of samples.

---

Yes, this was just a test, so that I wouldn't have to find two files with the same tempo - guess I could have processed one to make them different enough to not filter each other.

I'm noticing that when I'm doing the "move the WaitUntil to the left a bit" trick, that I need to move a slightly larger amount for some things. For example, If I have a sound that is one bar, lasting from 1-1-0 to 2-1-0, and I want to put a WaitUntil just before 2-1-0, I need to put it at 1-4-509 in 1/512 beat subdivisions in order to prevent the sound from cutting off when it reaches the WaitUntil. Any closer to 2-1-0 and it cuts off.