Kellerkraft

I made some applications that are heavily based on the snapshot function. However after certain runtime the snapshot drops out and doesnt deliver any output anymore.

dropouts-in-the-snapshot-function

Does anyone have a clue why it drops out? Might be a newbies Question as well... But I just won't get it.

Do you think it's a bug or my fault? Might someone else try to run the patch I posted and leave it for 5 Minutes..?

I have the exact same problem! snapshot~ just dies after a few minutes' runtime. Did you find a solution?

I've had it running for 30 minutes. Snapshots are still putting out data.

The @active attribute is unnecessary, especially when not followed by a 1 or 0.

I've had it running for 30 minutes. Snapshots are still putting out data.
The @active attribute is unnecessary, especially when not followed by a 1 or 0.


Running for more than 15 mn now, with or without overdrive and scheduler in audio interrupt...

Running for more than 15 mn now, with or without overdrive and scheduler in audio interrupt...
Mbp 2 x 2.3 ghz 4 Go Ram OSX 10.8.5


Snapshot~ is still freezing up after a few minutes here. Same goes for number~ when it's reporting signal values. In other words I have no way of converting signal to float, which is pretty ridiculous..

I'm running Max 7.0.5 32bit on Windows 7.

I'm having the same problem and it's really annoying...

I just need to have smooth line of numbers, so phasor˜was my friend, but now I have to use line, which is not very convenient (can't change the speed without resetting the numbers)

I have this problem since Max 7, whatever version it is.

I noticed that, most of the time, if I add or remove a msp object in the patch, snapshot work again. So I made a small patcher script which regularly add a number˜object in the patch then remove it, then add it again...

I can't reproduce consistently the problem. The help file of snapshot˜always works....

I'm having the same problem and it's really annoying...
I just need to have smooth line of numbers, so phasor˜was my friend, but now I have to use line, which is not very convenient (can't change the speed without resetting the numbers)

I have this problem since Max 7, whatever version it is.
Mac 10.8.5 and 10.10.5

I can't reproduce consistently the problem. The help file of snapshot˜always works....


Any news and this subject?
I really need the snapshot back...


You could try the peakamp~ object. It's quite stable as I know.

Just wanted to confirm this is still an issue for me, windows 7 64-bit Max 7.3.1. Also can confirm Yoann's "solution" does seem to break snapshot~ from being frozen... but obviously is not really a helpful solution for a patch functionality relying on snapshot~.

Just wanted to confirm this is still an issue for me, windows 7 64-bit Max 7.3.1.  Also can confirm Yoann's "solution" does seem to break snapshot~ from being frozen... but obviously is not really a helpful solution for a patch functionality relying on snapshot~.


I would like to know if this is still a problem in Max 8. I've encountered this problem in Max 7.3.4 today

Hello.
I would like to know if this is still a problem in Max 8. I've encountered this problem in Max 7.3.4 today

I have the same problem, windows 10, focusrite 6i6, max 8

Dropouts in the Snapshot Function