• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Re: Core Audio SDK 1.3.1
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Re: Core Audio SDK 1.3.1


  • Subject: Re: Re: Core Audio SDK 1.3.1
  • From: <email@hidden>
  • Date: Fri, 9 Jul 2004 19:35:57 +0000

> From: William Stewart <email@hidden>
> Date: 2004/07/09 fr PM 06:34:02 GMT
> To: Olof Westman <email@hidden>
> CC: email@hidden
> Dmne: Re: Core Audio SDK 1.3.1
>
> Most of the SDK is assuming that you have a reasonably up to date
> version of CoreAudio on your system - particularly the file code in
> CAAudioFile. This thus assumes you have at least QuickTime 6.4 or
> better on your system...

I have got QuickTime 6.5.1. Is it possible to install it
wrongly?

/Olof W



>
> Bill
>
> On 08/07/2004, at 11:02 PM, Olof Westman wrote:
>
> >> 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.
> >>
> >> Lance Drake
> >
> >
> > I have the same kind of problem. What is it that we do wrong?
> >
> > /Olof W
> > _______________________________________________
> > 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.
> >
> >
> --
> mailto:email@hidden
> tel: +1 408 974 4056
>
> ________________________________________________________________________
> __
> Culture Ship Names:
> Ravished By The Sheer Implausibility Of That Last Statement [GSV]
> I said, I've Got A Big Stick [OU]
> Inappropiate Response [OU]
> Far Over The Borders Of Insanity And Still Accelerating [Eccentric]
> ________________________________________________________________________
> __
_______________________________________________
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.


  • Follow-Ups:
    • Re: Core Audio SDK 1.3.1
      • From: William Stewart <email@hidden>
  • Prev by Date: Re: Core Audio SDK 1.3.1
  • Next by Date: >2 channel input now working with AUHAL!
  • Previous by thread: Re: Core Audio SDK 1.3.1
  • Next by thread: Re: Core Audio SDK 1.3.1
  • Index(es):
    • Date
    • Thread