That's the first time I've seen that problem - it looks like it's coming from some low level Max code. I will inquire with the folks at Cycling74 - stay tuned.
Also, they suggested that perhaps a Framework that exists within the application bundle might be corrupted. Can you control-click on the application, select Show Package Contents, and then navigate to Contents/Frameworks/MaxAPI.framework/Versions/A/MaxAPI. If you Get Info on that MaxAPI file, can you tell me how many bytes it is? It should be 660,416 bytes.
If it is, another thing you could try is to trash the whole application, and then re-download it from the App Store - it's possible that something got corrupted the first time you got it??
Ah, great, thanks Arthur24 - so Cycling's suggestion re: the corrupted Framework must have been the problem. Regardless, thanks for the full crash log and the followup!
Now just have to get the full log from gelware so I can get you up and running too...
Sorry for the trouble. Like Arthur24, I wonder if simply reinstalling will solve this too? It may be a corrupted Framework.... Could you try please and let me know?
Dan... I was just sure about the issue of this... I've downloaded again APF and guess what ???!!!! ... Damned, I had about 3 seconds before crashing, which is indeed better then the last performance (about 1 sec)...
Laurent, can you give me more details about your Mac? What OS, hardware, and also what is the default audio output device as selected in the Sound control panel?
Ugh, I'm afraid so! The only thing I can think of is that I know Cycling made some improvements to their CoreAudio driver in the latest versions of Max (which is what I used to build Audio Plugin Player) to address some crashes...
Within the next few days, I'll be submitting the 1.2 version of Audio Plugin Player to the Apple Store, and so hopefully a few days after that, you'll have a new version to try, which uses the very latest version of Max. I can't guarantee anything, because frankly I'm not entirely sure why it's crashing on you, but at least there's some hope that maybe with this new version the problem might be addressed?