freeing zero signal?
Hi all,
Did anyone encounter the message: freeing zero signal? in the max window.
My patch seems to work just fine, but I get this message every now and then. What am I doing wrong?
Thanks,
Guy
I do have the same message.
There's a topic here : https://cycling74.com/forums/filewatch-question
BUT the answer of Emmanuel Jourdan gone away with the new version of this website.
Someone ?
thanks
Charles
Don't expect me to write what I wrote on a forum two years ago ;-) You probably have some DSP object which is doing something not really good… The best thing would be to remove DSP objects "one by one" until you find the culprit. Are you using some third party externals?
I'm getting this same thing.
Externals I'm running:
Alex Harker externals
FFTease (codepend~ only) [I suspect this is the culprit]
sigmund~
It doesn't happen all the time, in fact, it happens only rarely. So that makes it harder to delete the one object and just wait. Is this something to be expected from an older external (like Max6 compatibility type stuff)?
Ha Rodrigo Constanzo fancy meetting you here. Bizarrly Eric who makes fftease was one of my tutors a few weeks ago and I asked him about this as well - I cant quite remember what he said though....
Hehe yeah. I've seen your posts/vids on here. Small world.
I'm looking into to some block convolution alternatives just using vanilla objects, so hopefully I'll be off the "ease" in a bit, to then test/see if this was the issue.
Hi all.
Just to go on with the toppic, and hopefully to fin a solution for this "problem". I am just doing some multichannel tests and try to reproduce some crashes of Max 6.1.3. I use only the Audio Tester, no other patch is open. The tester sends oscillator pulses every 250ms while stepping through 32 output channels. I always get these "freeing zero signal?" messages. Not a lot. Maybe 1 every 15 min. I also changed the Audiointerface: 1st I used a USB Madi Device, 2nd I used Jack Audio Connection Kit. Same problems with both devices.Then Max crashed after an hour the last four times. ...
In the morning I programmed in MAx (without the audio tester) - I havn't had crashes.
MY Machine is a Macbook Pro 13" from Mid 2012. OSX is 10.8.4. Nothing else to say at the moment ;)
I can't profess to understand what this message means, but I was able to determine what was causing it in my patch. I had a mc.gen~ with 2 inlets, one of which was receiving a 4-channel multichannel signal. When I explicitly set the other to a number of channels greater than 4, this message would sporadically appear (and actually for me, the entire patch would hang).