Rate~ and phase offset in Pluggo

wak's icon

I am using plugphasor~ and rate~ (in lock mode) to keep a LFO in sync with my host (DP 4.6). plugphasor~ cycles every quarter note. If I want LFO to sync to the half note I put 0.5 in the right inlet of rate~.

This is where my problem comes in. I would like to be able to choose weather the cycle starts on 1 and 3 or 2 and 4. Using +~ and pong~ I've implemented a phase offset, but what appears to be happening is this: Depending on where I stop playback and rewind, the rate~ object locks it's phase according to where it left off. The net result of which is rate~ will start its cycle on 1 and 3 part of the time and 2 and 4 part of the time.

I've had a couple thoughts on how I might work around this issue to make the LFO sync how I want it to:

The problem naturally only shows itself when the rate~ ramp is slower than the master ramp. So, having a slower master ramp could alleviate the issue. Is there a way to make a slower ramp out of pluphasor~ with out causing the same problem?

I could possibly use rate~s goto message to correct the sync, but as far as I can imagine, this would mean making a calculation and triggering the message every beat, which seems to me to be a lot of (hopefully) unnecessary processing.

I sure would like some help with this conundrum. Has anyone else dealt with this?

Thank you, one and all.

-ian

justin's icon

the rate object also has different sync modes for managing the phase offset... have you checked the sync message out?

also you could reset the rate object to a certain value by using the host transport info (using the plugsync~ object) to go to a particular beat.

hope that helps,

justin

wak's icon

Quote: justin wrote on Fri, 27 October 2006 06:08
----------------------------------------------------
> the rate object also has different sync modes for managing the phase offset... have you checked the sync message out?

As I mentioned I am using rate~ in lock mode, but I would expect the same issue in cycle mode since the issue arises from stopping the host transport at different places in rate~s cycle.

> also you could reset the rate object to a certain value by using the host transport info (using the plugsync~ object) to go to a particular beat.

This is what I was referring to (sorry if I wasn't clear) when I posited using the goto message, but I can't imagine a way to do this without triggering the sync multiple times per second, and I'd rather avoid this.

Using plugsync~ also brings up compatibility issues with some hosts.

Thanks for your response,

-ian