el.samm~ and count~ go out of sync with max 5.1.3

Hi Eric,

Thanks for the comments. In the test patch the edge objects are there just to demonstrate the drifting. The problem isn’t that they aren’t lighting at exactly the same time, but that they’re flashing at entirely different rates (I may not have worded that very clearly earlier).

I agree completely that it’s best to stay as much as possible in the signal domain, your objects are really useful for that. Unfortunately in my case (at least i thought) it was necessary to use a count~ object as well as samm because i’m storing single sample ‘triggers’ in a buffer, and i need to be sure they get read out again, by feeding the buffer players (xplay) with a continuous sequence of whole sample index integers.

I reinstalled a previous version of max, and that didn’t solve the sync problem. So i’m wondering if it could be something to do with the general state of my OS. ugh!

Thanks Eric, that patch is helpful.

Do you know whether reading a buffer index based on a sync-ramp * buffer-length-in-samples, is an approach that can be relied upon to safely read every sample in the buffer without skipping any? (assuming the buffer was recorded into at the sampling rate).

I avoided doing this initially because i though there might be subtle problems with rounding leading to skipped samples. But if this works then i think it would solve my problems.