marleynoe

I'm not getting some aspects of the sync~ object. Would be thankful if someone could shed some light on this.

It says in the reference of the sync~ object:

"The word 'offset', followed by a floating point number in the range 0.-1.0, adjusts the "phase" of the current output ramp."

However, I couldn't find a way that this message has any effect on the output ramp at all.

For instance, producing a very slow ramp (bpm 1), and sending "offset" messages by dragging a number box connected to the message "offset $1" (connected to sync~'s inlet), should have an effect on the output ramp, no?

The behaviour is the same in Max6 and Max5, thus I believe I'm not getting what this message means.

"The word 'start' causes the current output ramp to halt, and resets the ramp to 0." -> Again, I can't reproduce this behaviour here. In Max6, the message 'start' will re-trigger a given ramp, but only once while DSP is running, whereas in Max5 it will retrigger multiple times (as described in the reference), which leads me to think this could be a bug.

This is on Max6.1.7 (both 32 and 64Bit), Max5.1.9, MacOS 10.9.2

I'm not getting some aspects of the sync~ object. Would be thankful if someone could shed some light on this.
It says in the reference of the sync~ object: 

However, I couldn't find a way that this message has any effect on the output ramp at all.
For instance, producing a very slow ramp (bpm 1), and sending "offset" messages by dragging a number box connected to the message "offset $1" (connected to sync~'s inlet), should have an effect on the output ramp, no? 

Likewise, it says in the reference:
"The word 'start' causes the current output ramp to halt, and resets the ramp to 0." -> Again, I can't reproduce this behaviour here. In Max6, the message 'start' will re-trigger a given ramp, but only once while DSP is running, whereas in Max5 it will retrigger multiple times (as described in the reference), which leads me to think this could be a bug. 

sync-offset-message-no-effect-start-message-inconsistent-possible-bug

Hi I was wondering if you had any further news on this? I'm having the exact same issue on Max 7 ({

    "version" : "Version 7.0.1 (57afb55) (32-bit mac)",

    "osversion" : "Mac OS X Version 10.10.1 x86_64"})

Hi I was wondering if you had any further news on this? I'm having the exact same issue on Max 7 ({
	"version" : "Version 7.0.1 (57afb55) (32-bit mac)",
	"platform" : "mac",
	"arch" : "x86",
	"osversion" : "Mac OS X Version 10.10.1 x86_64"})


Same for me. OSX, Max 6.19, 64bit. scope~ object attached to sync~ output shows nothing but occasional shudder produced by 'start' message. 'offset 0.' has no effect at all. Please advise.

sync~: "offset" message no effect, "start" message inconsistent - possible bug?