random ear-splitting chaos!
Hello,
I am new to max but finding it to be an amazing tool already on just day 3. I just have one problem. At some point, randomly, when using any patch (and I have already written many) the system will output a random burst of earsplitting noise! sometimes it sounds like white noise and sometimes more of a tonal signal. Either way I have been afraid for the safety of my speakers and even worse, my ears!!
Can someone please tell me what is happening? is this a result of my CPU crashing? Max has never crashed during this earsplitting chaos, but I have no other explanation. The program does behave very strangely when this happens. Sometimes even if I disconnect all of the modules from the dac there is still the noise. Could this be a Max 7 bug, or do I have a corrupted version of the program?
Any help in this matter would be much appreciated.
K
It's going to help to know system info like computer type, OS, sound card etc.
sounds like an audio interface problem rather than a max problem.
Macbook pro OS 10.7.5. M audio Firewire 410. Max 7.
I had an M audio card (PCI, desktop mac), once; can't remember which one, but it caused max to crash unexpectedly -- ended up having to remove it... it might be worth checking to see if you have the same problem with max 6-- if not, then it's something to do with max 7
can't be the soundcard. I just had the same problem when using my laptop without the audio interface plugged in.
I had this problem with Omnisphere plugin occasionally with Max 6, nearly blew my ears out the first time due to using in-ear system. What seemed to be happening was that it was generating NAN values. I used bitsafe~ objects to protect against this problem and it seemed to have worked.
That's interesting dhj, I've had problems with standalone applications making the 'screech' sound in the past, it seems to happen most when changing audio drivers - and then after restarting the application it seems to be OK (not the easiest thing to reproduce). I'll do some trials with bitsafe~
bitsafe~ seems to do the trick. I think it is the standalone applications that are causing problems (including the beap objects that come with max 7)
Bitsafe~ didn't do anything for me.
I get this ultra-daft number (first time I bothered to check before the fight or flight response ebbed away). It is not a sound that one would call pleasant to listen to.
This is when changing to my mac's inbuilt audio driver, and happens with both line/mic inputs.
Managed to get some 'nan' readings out of the second adc~ outlet (not useless after all).