On Wed, May 13, 2015 at 7:07 AM, Anatol anatol2...@gmail.com wrote:
Werner, can you please shortly explain the no-scenecut issue.
Without scenecut detection, if such event occurs in the middle of the GOP,
as it usually does, the video quality till the end of the GOP will be
rather compromised.
Thanks Werner.
I believe that u'll find out that disabling scene cut detection might cause
a significant quality reduction.
Therefore, activating together the forced keyframes and the scene cut
detection is probably the most reasonable compromise.
On Wed, May 13, 2015 at 12:47 PM, Werner Robitza
On Mon, May 11, 2015 at 10:49 PM, Joel Lopez badassmexi...@gmail.com wrote:
Could I just run my unaligned files through ffmpeg again with a set
keyframe interval and disabled scene cut detection?
Or do I need to scrap them and re-encode the source file and generate
new files that are properly
You don't have to disable scene cut detection. Without scencut the video
quality is dramatically lower than when it is used.
'force_key_frames' and 'scenecut' work just fine together. Such videos
passes Apple AppStore validation and Akamai does not complain about it
either.
Make sure to disable
Make sure to disable '-g' option, occasionally x264 generates both forced
and '-g', increasing the bitrate, reducing the quality and causing some
other mess.
There's no way to disable the -g option. If you don't use it, x264
will stick to the default values of keyint=250 and min-keyint=25.
Large gop value is good enough for disabling it.
On Tue, May 12, 2015 at 2:25 PM, Werner Robitza werner.robi...@gmail.com
wrote:
Make sure to disable '-g' option, occasionally x264 generates both forced
and '-g', increasing the bitrate, reducing the quality and causing some
other mess.
On Tue, May 12, 2015 at 2:45 PM, Christian Ebert blacktr...@gmx.net wrote:
* Nicolas George on Tuesday, May 05, 2015 at 17:28:33 +0200
As an additional note, the second solution if by far preferable, because
forcing the frame type too frequently ruins x264's bit allocation
algorithms.
As per
* Nicolas George on Tuesday, May 05, 2015 at 17:28:33 +0200
As an additional note, the second solution if by far preferable, because
forcing the frame type too frequently ruins x264's bit allocation
algorithms.
As per this thread elsewhere there are different opinions on
that. Others say that
* Werner Robitza on Tuesday, May 12, 2015 at 15:10:07 +0200
On Tue, May 12, 2015 at 2:45 PM, Christian Ebert blacktr...@gmx.net wrote:
* Nicolas George on Tuesday, May 05, 2015 at 17:28:33 +0200
As an additional note, the second solution if by far preferable, because
forcing the frame type too
Could I just run my unaligned files through ffmpeg again with a set
keyframe interval and disabled scene cut detection?
Or do I need to scrap them and re-encode the source file and generate
new files that are properly aligned? We have thousands and am trying
to save time where possible.
On
Le sextidi 16 floréal, an CCXXIII, Werner Robitza a écrit :
You need to re-encode them with either the force_key_frames option, or
by setting the keyframe interval for your encoder, and disabling scene
cut detection. For x264 this would be keyint=120:scenecut=-1 if you
want a keyframe every 5
On Tue, May 5, 2015 at 12:05 AM, Joel Lopez badassmexi...@gmail.com wrote:
Should I re-encode these videos or could they still work? I saw that it's
be possible to force keyframes on an existing video.
You need to re-encode them with either the force_key_frames option, or
by setting the
That was definitely easier to read. I did a grep for I for my 4 versions
of the same video at different bitrates. I can now tell that they
keyframes aren't aligned and under 1 second apart. All my research says
keyframes must be aligned and a constant separation between 2 - 10 seconds.
Should
On Thu, Apr 30, 2015 at 5:26 PM, Joel Lopez badassmexi...@gmail.com wrote:
Thanks for the help. It's making a bit of sense now. It looks like my
keyframes are 1/3 of a second. Is less than 2 seconds apart ok?
For adaptive streaming the keyframes should be at regular intervals.
That means,
Thanks for the help. It's making a bit of sense now. It looks like my
keyframes are 1/3 of a second. Is less than 2 seconds apart ok?
In the pict_type field I'm seeing B's and P's with one I. Does that
translate to how far apart they are?
[FRAME]
pkt_pts_time=244.70
Hi,
I'm trying to decipher what the values are in the info presented. I need
to determine how far apart the keyframes are. 3 seconds is what I hear
they should be for adaptive bitrate switching.
Are these miliseconds and bytes?
pkt_pts=754100
pkt_pts_time=251.37
pkt_dts=754100
16 matches
Mail list logo
