(In reply to comment #38)
> Yet another (and I'm trying it now), would be to have both the native and
> libfaac/libfaad enabled (Windows and OSX). It may be possible to present both
> options to the user. It's certainly possible via the ffmpeg command, but via
> the custom ffmpeg options dialog, it gets a bit confusing (read that as if I'd
> said "I haven't figured it out yet". :-))
>
This will not work easily. We'd have to enable ffmpeg EXPERIMENTAL compliance
just like you have to with the ffmpeg command:
(In reply to comment #38)
> Yet another (and I'm trying it now), would be to have both the native and
> libfaac/libfaad enabled (Windows and OSX). It may be possible to present both
> options to the user. It's certainly possible via the ffmpeg command, but via
> the custom ffmpeg options dialog, it gets a bit confusing (read that as if I'd
> said "I haven't figured it out yet". :-))
>
This will not work easily. We'd have to enable ffmpeg EXPERIMENTAL compliance
just like you have to with the ffmpeg command:
./ffmpeg -i ~/1.wav -strict experimental -acodec libfaac faac.m4a
So, probably not a good option.
> The first option is definitely possible though...well, I'll be testing it in a
> few minutes anyway. :-)
This most definitely works.