Tom Law

I'm using the "loop sync output" on groove~ to sync a slider object over a waveform~ object.  It'll work fine for like 2o minutes, but then that loop sync output just stops putting out a signal for no apparent reason.  If I then connect another number~ object to it (or just delete the cable to the existing number~ object and then undo the delete), it'll start putting out a signal again.

Any ideas what might be causing this?  I'm using the timestretch attribute, don't know if that's contributing to the problem.  It's really hard to troubleshoot, since I have to work for 20 minutes or so after making a change to see if it's made a difference. I'm using Max 8.2.0 on MacOS 11.6.

Any ideas what might be causing this?  I'm using the timestretch attribute, don't know if that's contributing to the problem.  It's really hard to troubleshoot, since I have to work for 20 minutes or so after making a change to see if it's made a difference.  I'm using Max 8.2.0 on MacOS 11.6.

I'm using the "loop sync output" on groove~ to sync a slider object over a waveform~ object.  It'll work fine for like 2o minutes, but then 

"loop-sync-output"-on-groove~-object-stops-working-after-20-minutes

Are you sure it is groove~ sync output, and not number~ that stops responding ?

you can connect meter~ parallel to number~ and check

Are you sure it is groove~ sync output, and not number~ that stops responding ?
you can connect meter~ parallel to number~  and check


Thanks! I did that, and indeed the problem does seem to be with number~, not groove~.

Thanks!  I did that, and indeed the problem does seem to be with number~, not groove~.
So why would number~ stop working, then?

I one only would know and understand all that...

There were reports also about snapshot being unreliable after a longer period of time.

I've run groove~ test yesterday with both meter and number at sync output,

I one only would know and understand all that...
There were reports also about snapshot being unreliable after a longer period of time.
I've run groove~ test yesterday with both meter and number at sync output,
and both were working ok after 3 hours.
Mac, Max 8.1.11


number~ does the same as snapshot~ and peakamp~, that is clear.

always use external metro for these, then all is good.


it should not happen with groove~. 

number~ does the same as snapshot~ and peakamp~, that is clear.

always use external metro for these, then all is good.


I don't understand what you mean about using external metro with either number~ or snapshot~. With either one, I'm feeding them the sync signal from groove~. How would I connect an external metro?

I don't understand what you mean about using external metro with either number~ or snapshot~.  With either one, I'm feeding them the sync signal from groove~.   How would I connect an external metro?
(Thanks!)

snapshot/peakamp can either report the current sample value when it recieves a bang, or using an internal clock / auto mode. only the latter is what does not work right.

regarding number~ i was wrong, bang does already something else there.

grafik.png


snapshot/peakamp can either report the current sample value when it recieves a bang, or using an internal clock / auto mode. only the latter is what does not work right.

regarding number~ i was wrong, bang does already something else there.

OK, this looks promising. I'll try it out first thing tomorrow morning. Thanks so much!

OK, this looks promising.   I'll try it out first thing tomorrow morning.  Thanks so much!

There was a fix for this [number~] and [snapshot~] issue included in 8.1.6, if you are still seeing this in 8.1.11 or 8.2 could you send us a patch that demonstrates the issue with either object, along with your support information, to support@cycling74.com ?

"Loop sync output" on groove~ object stops working after 20 minutes