Re: Core Audio SDK 1.3.1
Re: Core Audio SDK 1.3.1
- Subject: Re: Core Audio SDK 1.3.1
- From: Lance Drake <email@hidden>
- Date: Tue, 29 Jun 2004 03:10:38 -0600
From the developer's perspective, I think it is fair to simply offer
support for the latest free upgrades of any major version. Nobody is
going to be running 10.2.3 since there is a free upgrade to 10.2.8, so
you can reasonably support 10.2.8 and consider you have Jaguar support.
Likewise with QT 6.5.1 (it's been free since v6.0, hasn't it? I
forget).
Normally, I would begin my note to a newsgroup with a nice friendly
invocation like "Hi CoreAudioFolks..." but recently, the AppleList
mail servers have been kicking notes which begin as such as having
been identified as SPAM - so, to the point:
The 1.3.1 SDK example code is really great. Unfortunately, I can't
use it under 10.2.8 unless I embark on a search-&-destroy mission for
things that weren't present in 10.2.8 - such as AudioChannelLayout
which is not defined in the Jaguar CoreAudioTypes.h.
In my case, this was a daunting obstacle to face because I wondered,
"How deep does THIS iceberg go?" - especially when AudioChannelLayouts
are the first things referenced in the CAAudioFile 'init' function.
My compiler complains: "In file included from CAAudioFile.h:13,
CAAudioChannelLayout.h:29: error: parse error before `&' token"
and so on... Obviously, I am doing SOMETHING wrong... but what?
Actually, 'afplay' DOES compile with my Xcode 1.2 SDK 1.3.1 install
with the build selection set to 10.2.8. However, my project, which
makes use of some of this code, does NOT build - although the same
source with a 10.3 OS build-setting DOES. The upside to all this is the
knowledge that, "It's only software..." and that there IS a solution
to all my immediate whoopdeedoo. I have no complaints except with my
own limited skill and knowledge regarding how best to deal with things.
What I wanted to kick into this discussion is how the notion that people
will automatically (or can ever be expected to) upgrade to the latest
free software is not correct. Something like 50% of all Mac Users are
still running OS9 - even 8.6... OUCH!
I can't get my brother to upgrade anything because he is not a
developer,
has a dial-up connection, and 6 to 25 megabytes of some OS updater is
just not gonna happen for him over his phone line. I send him CDs with
updaters on them so he can hope to keep up with it all. And... the only
reason he even bothers with it to begin with is because I am on his back
to do so. My guess is that many people don't see the value in upgrades
-
as long as blue-smoke is not coming out of the CPU.
Thus noted, requiring Users to be up-to-date with their software is more
likely to cause your offerings to be passed - than to exhort them to get
with the program. Besides, the requirements handed to me are that
whatever it is I produce MUST be capable of running with 10.2.3 thru
10.3.4 and QT 6.4+. So, **I** have to pass on things which are known to
not be compatible with that full range of qualifiers - which is OFTEN a
bummer as ever more and more cool/better things come out of Apple.
In Xcode, if you are compiling your projects using the 10.2.8 SDK, your
code should work fine in Jaguar. Just test it before you do a public
release.
Thanks very much!
Lance Drake
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.