search

CNMAT / CNMAT-MMJ-Depot

CNMAT's expanding library of Max/MSP/Jitter patches
89 stars 17 forks source link

m29 standalone system errors #60

Closed EdmundCampion closed 9 years ago

EdmundCampion commented 9 years ago

I have had some strange bug behavior on my Mac OS Lion. I tried opening several MU29 standalones and got the error "mixerengine already in use". Then I saw the same error when I opened Max 6. After restarting computer and throwing all preferences from Max and audio midi etc.. I opened the standalones and they crashed immediately on opening. I post the log of one of those crashes below.

Thing is, I went back to a different 2013 version of the standalones and they work fine. The creation date on each paired standlone is the same. I think some of this is my computer audio driver -- but I don't know how to reinstall those drivers.

(log in gist)

equilet commented 9 years ago

https://gist.github.com/equilet/15031a3d8ef867ff83e0

equilet commented 9 years ago

OK, since that kinda freaks me out I'm going to pretend it's Willa's issue until I hear otherwise. Will follow up w/ Ed on the 'mixerengine already in use' thing - Ed, have you verified that you are always opening the standalone up with the correct application (listed in getinfo)?

EdmundCampion commented 9 years ago

The error message reads: mixerengine_new: ##mixerengineinstance## is in use! I can bring in both standalones and show in Wednesday...

I have two of them with the same creation date. My hunch is this has something to do with Quicktime and using the 8-channel mix in quicktime --

EdmundCampion commented 9 years ago

agreed that these are separate issues --

equilet commented 9 years ago

this is the wrong issue thread. I'm moving all comments to a new thread - stay tuned.

equilet commented 9 years ago

@EdmundCampion - please verify that your issue is fixed based on our solution the other day. If so, please close this out.

EdmundCampion commented 9 years ago

All our mu29 patches should come with a DSP loadbang -- so that future standalone builds don't have this problem...