Re: tiger app fails on leopard
Re: tiger app fails on leopard
- Subject: Re: tiger app fails on leopard
- From: Michael Thornburgh <email@hidden>
- Date: Fri, 21 Dec 2007 23:59:33 -0800
Brad's correct: the release of MTCoreAudio on november 4th was mainly
to address Leopard (in)compatibility with my incorrect use of
NSConditionLocks in MTBuffer and its descendants. the new locking/
blocking scheme in that release (1.3.2) should work on OS X 10.3.9 ->
10.5+.
-mike
On Dec 18, 2007, at 8:19 PM, Brad Ford wrote:
I think I was the one who helped you. ;-)
The problem was the incorrect usage of NSLocks in MTCoreAudio, if I
remember correctly. And I believe the author of that library has
come up with a new version that behaves better on Leopard.
I just googled and found a version last updated on 11/04/2007 at http://aldebaran.armory.com/~zenomt/macosx/MTCoreAudio/
-Brad Ford
QuickTime Engineering
On Dec 18, 2007, at 7:51 PM, Robert Ackerman wrote:
we had an apple rep look at our tiger app at wwdc on a leopard box.
it had bad audio on playback so he created a new 'lock' class for
us and the app worked fine.
now i have my own macbook pro with leopard and the app from last
june does not playback audio at all --
either a universal built on tiger or a new leopard build.
i have tracked it enough to know that no bytes are going out in the
call to AudioConverterFillComplexBuffer.
i have no idea where to start getting it working, again.
i am using a set of classes called MTCoreAudio by Michael Thornburgh.
the first thing i could use is perhaps a pointer to calls in core
audio on leopard that are different than calls on tiger.
o
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden