Re: AudioFileComponents
Re: AudioFileComponents
- Subject: Re: AudioFileComponents
- From: William Stewart <email@hidden>
- Date: Wed, 14 Sep 2005 14:23:13 -0700
I haven't tried this myself - but someone just told me privately that
the current Ogg 'eat ' component is still working and behaving fine.
What appears to have stopped working (which doesn't surprise me) is
the SoundMgr decoder component that would be used to decode the
vorbis content.
It would be worth checking this - if this is true, then all that is
needed are the the vorbis components (at least just decoder) and ogg-
vorbis files would then be playable within both QT and iTunes.
Bill
On 14/09/2005, at 11:02 AM, William Stewart wrote:
On 13/09/2005, at 2:47 PM, Francisco Gimeno wrote:
Lets take one of these data formats and imagine we have this
available as an AudioCodec. What does that give me? (Lets take
FLAC as the example)
(1) I could read or write a CAF file with FLAC data in it - CAF
files (CoreAudioFormat Files) can take any audio data format
(2) I could read or write a Movie file with FLAC data in it -
Movie files can also contain any audio data format
These will both work with QT 7 (or Tiger) as it is today.
(3) With an Ogg AFC, I could also read or write Ogg files with
FLAC data
Ok, but I have the impression that this is not enough for *all*
applications in Tiger. It's not at all clear to me which
applications use which APIs and require which components/codecs/
etc. Personally, I'm primarily interested in making iTunes
happy with ogg/vorbis for the moment. Will that require the eat/
spit components?
Yes.
it's any way for doing the qtcomponent reusing the AudioCodec and
AudioFileComponent? was that in mind when Core Audio { AudioCodec
+ AudioFile } was developed?
Yes - QT of course already makes complete use of AudioCodecs - that
is the only way to extend QT's ability to handle data formats.
AFC's - yes, but we've been asking the QT group to do alot over the
last couple of years :-)
The question is that there is a existing qtcomponent [1] for Ogg
that has been broken for a QuickTime API change that hasn't been
detected so far.
I don't know anything about that - that is properly a question for
the QT API list
It could seems the order of GetDataSource calls could be changed
or a structure not being initialized or something. Debugging the
qtcomponent has taken 2/3 days for me with no success at all.
QT API list I guess
Bill
It has been talked a lot on this list and Quicktime-api about
that, but not conclusion at all. Now I'm thinking to back to the
debug ( as far I have started the work on OggAudioFormatComponent ).
[1] http://qtcomponents.sourceforge.net
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40apple.com
This email sent to email@hidden
--
mailto:email@hidden
tel: +1 408 974 4056
______________________________________________________________________
____
"Much human ingenuity has gone into finding the ultimate Before.
The current state of knowledge can be summarized thus:
In the beginning, there was nothing, which exploded" - Terry Pratchett
______________________________________________________________________
____
_______________________________________________
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
--
mailto:email@hidden
tel: +1 408 974 4056
________________________________________________________________________
__
"Much human ingenuity has gone into finding the ultimate Before.
The current state of knowledge can be summarized thus:
In the beginning, there was nothing, which exploded" - Terry Pratchett
________________________________________________________________________
__
_______________________________________________
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