Glad we found the issue!
Actually, from the viewpoint of a developer, I’m also not a big fan of renaming some files and hoping everything else’s still working. 😉 Tools should co-exist on a development platform without interfering each others imho. OpenAL is however a system-wide standard framework shipped with Mac OS X, therefore V-Play assumes the one under the framework search path is the correct one. We however try to change this behavior to be more specific which location should be used in one of our following updates, thanks for pointing this out.