On Fri, Sep 04, 2015 at 13:42:47 -0800, Lou wrote:
> On Thu, 3 Sep 2015 15:39:15 +0200
> Moritz Barsnick wrote:
>
> > I always have my problems decoding this N-36084-g993c84e stuff (why
> > can't any of the git web interfaces search for g993c84e?)
>
> 993c84e (notice no "g" prefix)
That was a "
On Thu, 3 Sep 2015 15:39:15 +0200
Moritz Barsnick wrote:
> I always have my problems decoding this N-36084-g993c84e stuff (why
> can't any of the git web interfaces search for g993c84e?)
993c84e (notice no "g" prefix) does not appear to be a valid
abbreviated commit hash for any commit in the re
thanks, recompiling latest version of x264 and ffmpeg solved the problem!
Not sure what happened a few months ago, must have installed an old version
indeed.
Thanks for your help,
best regards, Frans
2015-09-03 15:39 GMT+02:00 Moritz Barsnick :
> On Thu, Sep 03, 2015 at 15:03:34 +0200, Frans
On Thu, Sep 03, 2015 at 15:03:34 +0200, Frans Gouverne wrote:
> *Hereby my output:*
> ffmpeg version N-36084-g993c84e-xuggle-5.5 Copyright (c) 2000-2012 the
> FFmpeg developers
> built on Jun 11 2015 13:08:14 with gcc 4.4.7 20120313 (Red Hat 4.4.7-11)
I always have my problems decoding this N-36
If I do not use the quotes I do get:
*-bash: syntax error near unexpected token `('*
*So I tried:*
ffmpeg -i demo.mp4 -c:v libx264 -t 100 -force_key_frames
"expr:gte(t,n_forced*5)" -f null -
*Hereby my output:*
ffmpeg version N-36084-g993c84e-xuggle-5.5 Copyright (c) 2000-2012 the
FFmpeg develop
On Thu, Sep 03, 2015 at 13:41:20 +0200, Frans Gouverne wrote:
> I use:
>
> -force_key_frames expr:gte(t,n_forced*5)
>
> It gives me the following error:
>
> Invalid duration specification for force_key_frames:
> expr:gte(t,n_forced*5)
Well, then something is wrong with your ffmpeg version. Pl
I think I mixed up a few things. It looks like expr: is only valid for
option force_key_frames. That is the original option I had troubles with.
Just to make a simple example, I have used it for the frame rate as well.
But now I do understand that "expr:" must not be used for the frame rate.
If I s
Hi Moritz,
thanks for the reply.
Using -r for the frame rate is just a simple example to check if expr: is
working or not. By the way, it should be expr:, not exp: but that does not
change anything for my example or output.
When using max(), I still get:
Invalid framerate value: expr:max(25,30)
Hi Frans,
On Thu, Sep 03, 2015 at 10:36:32 +0200, Frans Gouverne wrote:
> since I recompiled ffmpeg some months ago, I cannot use expressions on the
> command line anymore, they are simply not recognized. For example:
>
> ffmpeg -re -i demo.mp4 -ac 2 -b:a 64k -ar 44100 -c:v libx264 -r
> exp:gt(25
Hello,
since I recompiled ffmpeg some months ago, I cannot use expressions on the
command line anymore, they are simply not recognized. For example:
ffmpeg -re -i demo.mp4 -ac 2 -b:a 64k -ar 44100 -c:v libx264 -r
exp:gt(25,30) -f mp4 output.mp4
Invalid framerate value: exp:gt(25,30)
Below the c
10 matches
Mail list logo
