A MAV can occur in dSpaceCollide() for a multitude of reasons, it isn't necessarily collision related. It commonly means either you and/or the physics engine has tried to access an object (or its properties) that doesn't exist.
I'd suggest commenting out the stuff you've just added and gradually re-implement and test it at each stage until you find the culprit.
Check you're not accessing collision info for the sounds on any geom that has no collision count or no longer exists, that could possibly cause it.
It could also be due to accessing bodies, geoms and joints that no longer exist.
I'd suggest commenting out the stuff you've just added and gradually re-implement and test it at each stage until you find the culprit.
Check you're not accessing collision info for the sounds on any geom that has no collision count or no longer exists, that could possibly cause it.
It could also be due to accessing bodies, geoms and joints that no longer exist.