Sabina

I am working in MacOS Mountain Lion OS. 10.8.2m and last MAX's version (6.1.7)

This morning Max/MSP just does not work: each time that I start audio (by turning on a ezdac~ object, for example)

Max just crashes! Any bug report window shows up.

(Actually it started to happen with version 6.1.6, I just up graded to 6.1.7 in order to see if that could be fixed,

until now, Any idea about what is going on)

I am working in MacOS Mountain Lion OS. 10.8.2m and last MAX's version (6.1.7) 

This morning Max/MSP just does not work:  each time that I start audio (by turning on a ezdac~ object, for example)
Max just crashes! Any bug report window shows up. 

This is super weird.
(Actually it started to happen with version 6.1.6, I just up graded to 6.1.7 in order to see if that could be fixed,
until now, Any idea about what is going on) 

max-crashes-when-i-start-audio-super-mega-max-bug

https://cycling74.com/forums/max-crashes-when-turning-on-audio-output/

"what I did what you said and opened max, changed the driver and closed max immediately and it worked."

"what I did what you said and opened max, changed the driver and closed max immediately and it worked."
It did not work. 

I have a similar problem, I am building a patch to process live sound including filtering and being able to change the filter parameters in real time. Using a Digi 002, MBP, OS 10.8.5. Don't have the exact Max version number since I am at work atm.

I have noticed that whenever I attempt to send parameter data to a biquad~ or cascade~ object, the Max DSP defaults to "Built-in" and locks up. Using Activity Monitor to force the audio processes to restart sometimes helps bring the Max DSP back to life but I really need to restart/reset PRAM to get full function back (until the next time I try to adjust a filter, that is).

You might look to see if any patches are in your startup path that are loading/setting filters.

I did a little bit of testing using my copy of Max 5 and it seems to behave better, I will build a chunk of the project in Max 5 tonight and see if it works in that version. Will let you know if I have better luck.

I have a similar problem, I am building a patch to process live sound including filtering and being able to change the filter parameters in real time.  Using a Digi 002, MBP, OS 10.8.5. Don't have the exact Max version number since I am at work atm. 

I have noticed that whenever I attempt to send parameter data to a biquad~ or cascade~ object, the Max DSP defaults to "Built-in" and locks up.  Using Activity Monitor to force the audio processes to restart sometimes helps bring the Max DSP back to life but I really need to restart/reset PRAM to get full function back (until the next time I try to adjust a filter, that is).

You might look to see if any patches are in your startup path that are loading/setting filters. 

I did a little bit of testing using my copy of Max 5 and it seems to behave better, I will build a chunk of the project in Max 5 tonight and see if it works in that version. Will let you know if I have better luck.


I am not using any complex patcher. Is just a ezdac~ object in a patcher.

Even if there's any patcher and I turn audio on from the Audio Options Menu , Max Crashes.

it again (by putting Max folder in the trash) and it did not work.

I also have upgraded my OS from 10.8.2 to 10.8.5 and I does not work.

I am not using any complex patcher. Is just a ezdac~ object in a patcher.
Even if there's any patcher and I turn audio on from the Audio Options Menu , Max Crashes. 

I already uninstalled Max and installed
it again (by putting Max folder in the trash) and it did not work.
I also have upgraded my OS from 10.8.2 to 10.8.5 and I does not work. 

pardon me if this is too elementary, but have you been resetting PRAM when you restart after one of these crashes? Hold Cmd-Opt-P-R and restart, keep holding them down until the system chimes twice and then allow the restart to continue. I find myself resetting PRAM basically anytime I switch interfaces or set up in a new environment.

pardon me if this is too elementary, but have you been resetting PRAM when you restart after one of these crashes? Hold Cmd-Opt-P-R and restart, keep holding them down until the system chimes twice and then allow the restart to continue.  I find myself resetting PRAM basically anytime I switch interfaces or set up in a new environment.


Yes I did it, resetting PRAM and also after a disc diagnostic (in disc utility) the system displayed that everything is fine with the disc.

In other hand, when I erased the file ad_coreaudio.mxo Max did not crashed anymore, but doing that, there's not sound anymore.

Then, I guess is something related about that file . But what? Not Idea.

So I erased the file, I unistalled Max again, I reinstalled it , and I have still the same problem!

Yes I did it, resetting PRAM and also after a disc diagnostic (in disc utility) the system displayed that everything is fine with the disc. 

In other hand, when I erased the file ad_coreaudio.mxo  Max did not crashed anymore, but doing that, there's not sound anymore.
Then, I guess is something related about that file . But what? Not Idea. 

So I erased the file, I unistalled Max again, I reinstalled it , and I have still the same problem!


what interface are you using? or are you using the built-in audio? If you are using an Avid (Digidesign or M-Audio) product, you might reinstall their CoreAudio driver.

("In other hand, when I erased the file ad_coreaudio.mxo Max did not crashed anymore, but doing that, there’s not sound anymore.")

you could also try opening Activity Monitor, in the "filter" box upper right type "audio" and force-quit all the audio processes. They will automatically restart themselves - then you can see if the audio and/or crashing behavior recur.

what interface are you using? or are you using the built-in audio? If you are using an Avid (Digidesign or M-Audio) product, you might reinstall their CoreAudio driver. 

("In other hand, when I erased the file ad_coreaudio.mxo Max did not crashed anymore, but doing that, there’s not sound anymore.") 

you could also try opening Activity Monitor, in the "filter" box upper right type "audio" and force-quit all the audio processes. They will automatically restart themselves - then you can see if the audio and/or crashing behavior recur.


I tried it with coreaudio driver , and with that driver Built-in Microphone and Built-in Output.

Also with coreaudio driver I tried my sound interface: FireFace 400 for input and output Both settings, Built-in and the external soundcard

I tried it with coreaudio driver , and with that driver Built-in Microphone and Built-in Output.
Also with coreaudio driver I tried my sound interface: FireFace 400 for input and output  Both settings, Built-in and the external soundcard
 cause Crash.


I have this problem to sometime because of my soundcard, the solution : trash your preferences !!!!

I have this problem to sometime because of my soundcard,  the solution : trash your preferences !!!!

Hey, Thanks for answering. Do you mean at the audio options window? I already changed the audio drivers

, the way I explained above, so far, Max continues to crash!

It must be something related with the "ad_coreaudio.mxo" file, since there's not problem when I remove it. (but not sound as well)-

Hey, Thanks for answering. Do you mean at the audio options window? I already changed the audio drivers
, the way I explained above, so far, Max continues to crash! 

It must be something related with the "ad_coreaudio.mxo" file, since there's not problem when I remove it. (but not sound as well)-


I think he means, go to the Preferences folder for your user account and literally throw all your audio and Max preference files into the trash and see if your problem improves after restarting the program (or the computer for good measure). Like the audio processes I mentioned, they will automatically rebuild themselvs when you start Max the next time. You will have to re-set any preferences you had after this. I should have thought of this much earlier myself, it's usually the first thing to try since Mac preferences have a way of becoming corrupted randomly.

I founded this two files in the user/library/preferences/audio /folder.

I do not know what is the function of these files, and I feel scary about deleting them.

(Are protools , and Ableton , etc... going to work properly if I delete this? Actually

I founded this two files in the user/library/preferences/audio /folder.
I do not know what is the function of these files, and I feel scary about deleting them.
(Are protools , and Ableton , etc... going to work properly if I delete this? Actually
what is the function of these two files? 

com.apple.audio.SystemSettings.plist
com.apple.audio.DeviceSettings.plist


Just look in user/library/preferences/ for a file called "com.cycling74.MaxMSP.plist" and toss it out! (You could also look for and delete "com.apple.audio.AudioMIDISetup.plist.") If that doesn't solve the problem, you could also throw out the two files you found. The files you listed store things like what is your alert sound, how loud are the speakers, etc.

The .plist files store whatever you select under the "Preferences" dialog within the application. They can reside in the root Library folder and/or your personal user Library folder. For Word or Excel you might set a lot of complicated prefs, but for Max or audio, not so many. Throwing out the preferences file just means that whenever you restart the computer or application, it starts up with a "factory fresh" set of defaults just as they were the first time you set it up. Then you can go in and recreate your pref choices.

If you reinstall Max, it simply goes and finds the .plist file from the last time you used it, and if that is corrupted, it only reproduces whatever the problem was to begin with. Pref files get corrupted all the time, due to, I don't know, stray bits of magnetism or gamma rays or what have you, so it's not a big deal to throw them out and start fresh. As I said, I should have thought of it earlier myself.

The .plist files store whatever you select under the "Preferences" dialog within the application. They can reside in the root Library folder and/or your personal user Library folder. For Word or Excel you might set a lot of complicated prefs, but for Max or audio, not so many.  Throwing out the preferences file just means that whenever you restart the computer or application, it starts up with a "factory fresh" set of defaults just as they were the first time you set it up. Then you can go in and recreate your pref choices. 

If you reinstall Max, it simply goes and finds the .plist file from the last time you used it, and if that is corrupted, it only reproduces whatever the problem was to begin with. Pref files get corrupted all the time, due to, I don't know, stray bits of magnetism or gamma rays or what have you, so it's not a big deal to throw them out and start fresh. As I said, I should have thought of it earlier myself.


Thanks again for answering,I apreciate it.

Well, I deleted that file and Nope! it did not work .

Not a cue about what is going on. It must be a corrupted file that connects Max and the audio driver.

Hey, DCrandbal;
Thanks again for answering,I apreciate it. 

Well, I deleted that file and Nope! it did not work . 

Not a cue about what is going on.  It must be a corrupted file that connects Max and the audio driver.
Probably one of MacOS system?
Any cue? 

no idea, maybe I'll be able to think of something when I get home tonight and look at it, I only have Max Runtime here at work.

On Osx 10.8 the user preferences are hidden by default…

To see them click on the "Go" Menu in Finder, while you see the options list click the "option" (alt) button on your keyboard and you will see the Library option appear.

Here you will find the preferences of the applications. Try to momentary delete (drop them in to another location) the com.cycling74 plist files, restart your computer and re-open Max.

If nothing as changed put the files in their previous location…

Now that I am home, and somewhat embarrassed, I can report that throwing out the prefs did solve my own problem.

In my case I suspect it was switching back & forth from Max 5 to Max 6 (my Max for Live is still connected to Max 5) and both versions may write a preference file with the same name.

So do check to make sure you have found your own user prefs folder and try throwing out some prefs and see if it helps.

Another thing I checked was to make sure the Sound preferences don't default to AirPlay. I have learned that this will crash Pure Data.

Now that I am home, and somewhat embarrassed, I can report that throwing out the prefs did solve my own problem. 

Here are the files that I tossed out:
com.apple.audio.AggregateDevices.plist
com.apple.audio.AudioMIDISetup.plist
com.apple.audio.DeviceSettings.plist
com.cycling74.Max.plist
com.cycling74.MaxMSP.plist

In my case I suspect it was switching back & forth from Max 5 to Max 6 (my Max for Live is still connected to Max 5) and both versions may write a preference file with the same name. 

So do check to make sure you have found your own user prefs folder and try throwing out some prefs and see if it helps. 

Another thing I checked was to make sure the Sound preferences don't default to AirPlay. I have learned that this will crash Pure Data.


PJEVE, Yes, the problem was that I was not removing all the MAX preferences, because they are hidden.

DCRANDBAL, Yes is has to do with Max preferences. Thanks for support.

I applied this steps in this order and Max came back to life.

To clean out Max 6 entirely, remove these items:

1. ~/Library/Application Support/Cycling '74

In Mac OS 10.7, the Application Support/Cycling '74 folder is hidden. You can find it using the 'Go' Menu in the Finder. From there, choose 'Go To Folder...' and enter:

then navigate to the Cycling '74 folder and delete it.

Then download and reinstall the latest Max 6 release:

Then head to Applications > Utilities > Disk Utility > and 'Repair Permissions' for your main HDD where Max is installed.

Hello everyone.
SOLVED!
Thanks so much for your answers.
PJEVE, Yes, the problem was that I was not removing all the MAX preferences, because they are hidden.
DCRANDBAL, Yes is has to do with Max preferences. Thanks for support.
I applied this steps in this order and Max came back to life. 

To clean out Max 6 entirely, remove these items:
1. ~/Library/Application Support/Cycling '74
 2. /Applications/Max6
In Mac OS 10.7, the Application Support/Cycling '74 folder is hidden. You can find it using the 'Go' Menu in the Finder. From there, choose 'Go To Folder...' and enter:
~/Library/Application Support
then navigate to the Cycling '74 folder and delete it.

Then download and reinstall the latest Max 6 release:
https://cycling74.com/downloads

Then head to Applications > Utilities > Disk Utility > and 'Repair Permissions' for your main HDD where Max is installed.


Just be sure you understand that you might not always need to uninstall Max completely to solve these problems. That's what removing the Application Support folders is referring to.

I only needed to throw out the "*.plist" files I listed to get mine to come back to life. My "~/Library/Application Support/Cycling74" folder has a lot of material in it that would take me a good while to restore!

Just be sure you understand that you might not always need to uninstall Max completely to solve these problems. That's what removing the Application Support folders is referring to. 

I only needed to throw out the "*.plist" files I listed to get mine to come back to life. My "~/Library/Application Support/Cycling74" folder has a lot of material in it that would take me a good while to restore!


Max crashes when I start audio (super mega MAX Bug)