Wow, that was quick.
On Wed, Jun 05, 2002 at 05:34:31PM +0200, Zdenek Kabelac wrote:
>
> Well these calls are supposed to return something - but it's not garanteed
> what it will be - i.e. for codecs it might happen I'll replace long
> names with short mplayer compatible codec descriptions.
>
> Morever AUDIO_CODECS string is just a hint string for sorting
> (so I'll actually probably provide backward compatible sorting method
> if I'll eventually switch to shorter names)
> It doesn't have to contain all available codecs (video_codes & audio_codecs
> vectort have them - though I do not like that those globals
> variables the change of this would require change of every app using
> libavifile) - i.e. you could put there just FFMPEG and it will
> put all FFMPEG codecs ahead of others...
>
> For Audio Renderer & Video renderer the names will not be changed
> but agains - these string are just preferencies hints and do not
> respect what is compiled/supported by libaviplay library.
>
Ok, so the library doesn't actually "sanitize" the property strings
at all -- if I manually edit the config file and put non-existant codecs
in there, they'll appear in the string returned by player->Get(),
missing ones won't be added in. Have I got that right?
So to get the complete list of codecs, I need to look at the
audio_codecs[] and video_codecs[] vectors if I'm not mistaken. Is there
a corresponding place to get the list of audio/video renderers?
Thanks again for your help.
--
Steve Freeland
[EMAIL PROTECTED]
_______________________________________________
Avifile mailing list
[EMAIL PROTECTED]
http://prak.org/mailman/listinfo/avifile
