DSP off - only turns on when new audio object created
hello all,
i have a problem - couldnt fin info on it on the forum - but i suppose it might be a known issue?
sometimes when i have patches and turn on dsp - nothing happens.
but it starts to work if i create a new dsp-object (like for example meter~).
are others experiencing that too, and is there a way to work around that ?
thanks, frank
I sometimes experienced that the DSP doesn't start anymore, but for me it's a kind of random thing (no example patch), solved by launching Max again.
PowerBook G4, Max 5.0.6 (maybe I experienced that with 5.0.5).
J-F
yes, it's the same here
it happens every now and then.
and it's not really like the dp get turned off - it just somehow stops responding - it sort of freezes.
the meters don't move anymore and no sound is produced.
and when i create a new object it works again.
i suppose this is some sort of bug.
i'd be happy to know if there are ways to avoid this happening.
most of the time i had that when i loaded a patch. that wasn't really a problem.
but right now i have a patch where this happens every now and then while i work with the patch, which is really bad.
i supect the cause might be a subpatch in which i receive udp-data and do a lot of calculations with these values. but basically just normal mathematical operations. is it possible that these operations are to much and that it causes the dsp to freeze? or could it be udp-related ?
thanks, frank
frank desben wrote on Thu, 02 April 2009 04:31hello all,
i have a problem - couldnt fin info on it on the forum - but i suppose it might be a known issue?
sometimes when i have patches and turn on dsp - nothing happens.
but it starts to work if i create a new dsp-object (like for example meter~).
are others experiencing that too, and is there a way to work around that ?
thanks, frank
Sometimes I also get weirdness with this, I'll turn off the DSP in a patch, then create an MSP object in another, and it turns back on. It's strange, and only seems to happen with multiple patches open.
XP, 5.0.6 (though it's been happening for a lot of versions).
If anyone comes up with a reproduceable set of steps, please send them along to support at cycling 74 dot com.
Are any of you using 'local 1' or 'startwindow' messages to the dac~?
-Ben
The following patch will not turn audio on at all, or it will turn audio on locally. I send [ezdac] a 1 with [loadbang]->[message]. Using [loadmess 1] did not change this behavior.
Max 5.1.4
MacOS 10.6.4
ezdac will never turn audio on globally.
But it should turn on when fed a 1 at load.
I was unaware that [ezdac] is local only.
ezdac is global unless the "switch is local" box is checked in the inspector. All the help files have this checked.