well after returning to a project after a one month absence i was dismayed to find no audio output working at all…
had audio from other patchers but not this one…
after some analysis I found that the matrix~ obejct connected as the last point before the dac~ appeared to be causing a mute to the output when connected, or that as well as the dac~ misbehaving
I replaced the dac~ and matrix~ with identical objects and the problem cleared up!
now this project was a port over from max 4.5.5 to 4.6 running in osx , but it did work last time i opened it. im wondering if this is a familiar problem to anyone – ie object errors/bugs people have heard of? and what i might do to avoid it happening again?
Eliot Palmer wrote:
> after some analysis I found that the matrix~ obejct connected as the
> last point before the dac~ appeared to be causing a mute to the
> output when connected, or that as well as the dac~ misbehaving
a matrix~ would normally mute, if there is a feedback loop. I don’t know
how the different Max versions would find out about it, but if you never
actually create the feedback, and Max didn’t recognise it while building
the audio chain, this might explain why it worked before…
Maybe some send/receive (without ~) which are overseen by the feedback
This is just a shot in the dark, but you could test it by simply
adding/replacing a send~/receive~ pair into the chain…