Forums > Max For Live

loop_jump: unexpected behavior

Feb 12 2010 | 3:41 am

I’m observing playback of a clip with the following properties:

64 beats long
Start marker at 1.1.1
Looping enabled
Loop start / end at beat positions 32 and 64 respectively

When observing the loop_jump property, I expect to see a bang when the playback position crosses beat 32, which I do see, however; the loop_jump observer also bangs when the clip is first triggered, i.e. when it starts playing from beat 1. This seems very wrong to me- am I missing something?

Feb 12 2010 | 4:56 am

patch please, as clear as possible.


Feb 12 2010 | 5:12 am

It appears that my initial assessment was incorrect- it’s not playback that triggers the loop_jump observer bang, it’s setting the path for the observer.

Here’s a patch to demonstrate- it observes the first clip in the first track.

-- Pasted Max Patch, click to expand. --

My understanding is that an observer will output the initial value of a property immediately after the property is set, then output any changes from that point on. In this case a bang (indicating the loop point was reached) seems incorrect as the initial state.

I can’t attach a clip to this post, but if you just create one where the loop start point is somewhere after the first beat (in my case it was half-way through the clip), you should see what I mean.


Feb 12 2010 | 4:02 pm

Right on – thanks for the patch, we’ll investigate

For now I’m afraid you’re going to have to work around this with a gate or something, sorry.


Viewing 4 posts - 1 through 4 (of 4 total)

Forums > Max For Live