[FFmpeg-devel] -profile option broken(?)
C2Dcks at aol.com
C2Dcks at aol.com
Thu Sep 1 23:04:48 CEST 2011
Can someone Please tell me what the hell this is? It keeps filling up my
email & I don't have a clue whar's going on. None of it makes any since to
me!! How can I stop it?
Thanks I hope
Carl
In a message dated 8/27/2011 5:54:02 P.M. Eastern Daylight Time,
michaelni at gmx.at writes:
On Sat, Jul 30, 2011 at 01:42:55PM -0800, Lou wrote:
> On Wed, 20 Jul 2011 02:19:32 -0700
> Thomas Worth <dev at rarevision.com> wrote:
>
> > On Wed, Jul 20, 2011 at 1:56 AM, Michael Niedermayer
> > <michaelni at gmx.at> wrote:
> > > On Tue, Jul 19, 2011 at 09:49:48AM +0200, Erik Slagter wrote:
> > >> On 19-07-11 00:27, Rodney Baker wrote:
> > >>> On Tue, 19 Jul 2011 02:15:04 Erik Slagter wrote:
> > >>>> There is something very fishy:
> > >>>>
> > >>>> This triggers the error:
> > >>>>
> > >>>> /home/erik/src/ffmpeg/ffmpeg -y -probesize 500000000 -threads 16
> > >>>> -i 00033.avi -vsync 0 -async 0 -profile high -vcodec libx264
> > >>>> -strict experimental -acodec aac -ac 2 -ar 48000 -ab 192k -f
> > >>>> mpegts 00033_tmp.ts
> > >>>>
> > >>>> when I move -profile high to the start like this:
> > >>>>
> > >>>> /home/erik/src/ffmpeg/ffmpeg -profile high -y -probesize
> > >>>> 500000000 -threads 16 -i 00033.avi -vsync 0 -async 0 -vcodec
> > >>>> libx264 -strict experimental -acodec aac -ac 2 -ar 48000 -ab
> > >>>> 192k -f mpegts 00033_tmp.ts
> > >>>>
> > >>>> there is no error.
> > >>>
> > >>> This probably belongs on the ffmpeg-user mailing list,
> > >>
> > >> I agree, but this looks like a bug and I am trying to fix it, or
> > >> at least pinpoint the patch that caused it.
> > >>
> > >>> but have you tried
> > >>> putting -profile after -vcodec libx264? The order of command-line
> > >>> options in ffmpeg is important.
> > >>
> > >> I know I know. The interesting part is
> > >>
> > >> - the command line I'm using used to work a few weeks ago
> > >> - this error message is completely bogus
> > >>
> > >> Also interesting is that git bisect can't locate the offending
> > >> patch, I guess that has something to do with the large imports
> > >> from "qatar".
> > >>
> > >> Still, my question remains, can anyone try this with a current
> > >> version of ffmpeg (x86_64), so I know if it's something I borked,
> > >> although I have an almost clean tree (a few totally unrelated
> > >> patches, they've been the same for months).
> > >
> > > I can confirm the issue.
> > > -vprofile high seems to work.
> > >
> > > with -profile, one could argue it affects audio too and i think
> > > thats where it fails.
> > > but i did not investigate this at all ...
> >
> > I just happened to run into this too while encoding for Blu-ray and
> > for web. It does fail, but only when including audio as you mentioned.
> > My Blu-ray script runs fine because it only generates a video file,
> > but my web script fails because it includes a separate audio file on
> > the ffmpeg command line. I get the following error:
> >
> > [NULL @ 0x101801800] [Eval @ 0x7fff5fbfe140] Undefined constant or
> > missing '(' in 'baseline'
> > [NULL @ 0x101801800] Unable to parse option value "baseline"
> > [NULL @ 0x101801800] Error setting option profile to value baseline.
> >
> > This is on Mac OS X/darwin x86_64.
>
> I can confirm this on a 32-bit Ubuntu Natty VM with:
>
> ffmpeg -i IronMan.mkv -vcodec libx264 -preset medium -profile \
> baseline -crf 24 -strict experimental -acodec aac -y ~/output.mp4
> ffmpeg version N-31478-g5dc6bd8, Copyright (c) 2000-2011 the FFmpeg
> developers
> built on Jul 30 2011 13:40:27 with gcc 4.5.2
> configuration: --enable-gpl --enable-libx264
> ...
> [NULL @ 0xa194720] [Eval @ 0xbfc2e17c] Undefined constant or missing
> '(' in 'baseline' [NULL @ 0xa194720] Unable to parse option value
> "baseline" [NULL @ 0xa194720] Error setting option profile to value
> baseline.
>
> ...and some users on ubuntuforums.org have mentioned the same issue.
>
> 5dc6bd86f0f5cfffb44b47e6e916119f26b12091 bad
> 1885824b20a493d25db4b8e5397666e3a68f45f2 good
>
> I'm not sure what it is from 5dc6bd86 that is causing the issue.
in short -profile X sets the profile for all streams, -vprofile X
just for video streams
X is not valid for aac thus it fails.
Iam not opposed to apply a patch if someone has one to workaround this
case but it really is the user asking for something invalid and an
error is not so wrong as a result
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
I do not agree with what you have to say, but I'll defend to the death your
right to say it. -- Voltaire
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel at ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
More information about the ffmpeg-devel
mailing list