On Tue, 29 Nov 2005 21:01:29 David Niemeijer
<email@hidden> wrote:
I have been looking at the headers but find no info on whether the
calls below
are supposed to be thread safe or not. Don't know whether that is
a good or
bad sign :-)
Bad sign. I don't remember whether it was said loud but Sound Manager
is deprecated or soon to be so. It was in development before threads
and Mac OS X. There are good chances some of it will work in threads
but there are equally good chances it will be marked deprecated in
Tiger+1 (or is it already?) and removed completely in Tiger+2.
It's been deprecated ever since the existence of CoreAudio, in OS X
10.0.
It can never be removed, of course. That would break Starcraft,
Diablo II and Warcraft III :| And, for that matter, it would probably
break Microsoft Office and hundreds of other non-audio-related apps
which coincidentally play sounds from time to time. Unfortunately,
CoreAudio is very cumbersome for lightweight use; the Sound Manager
still requires many fewer lines of code to play a simple sampled
sound. (The Cocoa side has NSSound, which is based on QuickTime and
is lighter-weight than Sound Manager, not to mention non-deprecated,
but I don't know of a Carbon equivalent "easy" sound technology.
Maybe QuickTime could be directly leveraged without needing a ton of
code.)
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
