[FFmpeg-user] Low-quality transcode

[Wouter Verhelst]

Hi list,

I'm a member of the FOSDEM video team. I wrote a tool to automatically
review and transcode FOSDEM video recordings, written in Perl, which
simply calls ffmpeg and ffprobe to do all the hard work[1]. It works
well, but there's something that's a bit weird.

For one particular talk, the quality of the transcode from MP4 to WebM
is very low. I use VBR encoding, but in most cases I end up with a
transcoded file that is about 60-70% of the size of the original file.

In one particular case, however, the file ends up being less than 50% of
the original file, and the quality is very low; the transcoded file ends
up having very visible encoder artifacts:

https://video.fosdem.org/2020/AW1.125/ada_rad.webm

Note the camera PIP at the bottom right corner, where smears etc are
clearly visible.

The command line that was originally used is this one:

'ffmpeg' '-loglevel' 'warning' '-y' '-f' 'concat' '-safe' '0' '-i'
'/tmp/transSnsDON/concat.txt' '-c:v' 'libvpx-vp9' '-b:v' '1024k'
'-minrate' '512k' '-maxrate' '1484.8k' '-r:v' '25/1' '-crf' '32'
'-speed' '4' '-pass' '1' '-passlogfile'
'/srv/sreview/output/2020/AW1.125/ada_rad.webm-multipass' '-c:a'
'libopus' '-b:a' '128k' '-ar' '48000' '-t' '1331.934' '-pix_fmt'
'yuv420p' '-metadata' 'title=On Rapid Application Development in Ada'
'-metadata' 'event=FOSDEM 2020' '-metadata' 'speakers=Tomasz Maluszycki'
'-metadata' 'date=2020-02-01'
'/srv/sreview/output/2020/AW1.125/ada_rad.webm'

'ffmpeg' '-loglevel' 'warning' '-y' '-f' 'concat' '-safe' '0' '-i'
'/tmp/transSnsDON/concat.txt' '-c:v' 'libvpx-vp9' '-b:v' '1024k'
'-minrate' '512k' '-maxrate' '1484.8k' '-r:v' '25/1' '-crf' '32'
'-speed' '2' '-pass' '2' '-passlogfile'
'/srv/sreview/output/2020/AW1.125/ada_rad.webm-multipass' '-c:a'
'libopus' '-b:a' '128k' '-ar' '48000' '-t' '1331.934' '-pix_fmt'
'yuv420p' '-metadata' 'title=On Rapid Application Development in Ada'
'-metadata' 'event=FOSDEM 2020' '-metadata' 'speakers=Tomasz Maluszycki'
'-metadata' 'date=2020-02-01'
'/srv/sreview/output/2020/AW1.125/ada_rad.webm'

which are the same settings as used for all other videos (and those seem
to be fine).

I first thought I'd just tweak things a bit, and tried changing the
bitrate values in the above command line to '-b:v' '1800k' '-minrate'
'900k' '-maxrate' '2610k', with everything else remaining the same. That
didn't result in any visible difference.

Next, I bumped -minrate to '1500k', and left -b:v and -maxrate to the
1800 and 2610k settings. That also didn't result in any visible
difference.

I'm beginning to think that perhaps I've found a bug in ffmpeg. Any
thoughts?

The ffmpeg version used is the one packaged in Debian buster:

ffmpeg version 4.1.4-1~deb10u1 Copyright (c) 2000-2019 the FFmpeg
developers
built with gcc 8 (Debian 8.3.0-6)
configuration: --prefix=/usr --extra-version='1~deb10u1'
--toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu
--incdir=/usr/include/x86_64-linux-gnu --arch=amd64 --enable-gpl
--disable-stripping --enable-avresample --disable-filter=resample
--enable-avisynth --enable-gnutls --enable-ladspa --enable-libaom
--enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca
--enable-libcdio --enable-libcodec2 --enable-libflite
--enable-libfontconfig --enable-libfreetype --enable-libfribidi
--enable-libgme --enable-libgsm --enable-libjack --enable-libmp3lame
--enable-libmysofa --enable-libopenjpeg --enable-libopenmpt
--enable-libopus --enable-libpulse --enable-librsvg
--enable-librubberband --enable-libshine --enable-libsnappy
--enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora
--enable-libtwolame --enable-libvidstab --enable-libvorbis
--enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx265
--enable-libxml2 --enable-libxvid --enable-libzmq --enable-libzvbi
--enable-lv2 --enable-omx --enable-openal --enable-opengl --enable-sdl2
--enable-libdc1394 --enable-libdrm --enable-libiec61883
--enable-chromaprint --enable-frei0r --enable-libx264 --enable-shared
libavutil  56. 22.100 / 56. 22.100
libavcodec 58. 35.100 / 58. 35.100
libavformat58. 20.100 / 58. 20.100
libavdevice58.  5.100 / 58.  5.100
libavfilter 7. 40.101 /  7. 40.101
libavresample   4.  0.  0 /  4.  0.  0
libswscale  5.  3.100 /  5.  3.100
libswresample   3.  3.100 /  3.  3.100
libpostproc55.  3.100 / 55.  3.100

The input video files are removed at the end of the transcode process,
so I cannot produce those; however, the .mp4 files are created with
'-c:v copy -c:a copy', so I believe that should be enough for you to
reproduce the issue (if not, let me know and I can recreate them).

Any insights as to why this is happening would be appreciated.

Thanks,

[1] https://github.com/yoe/sreview, in case you care.

-- 
 Home is where you have to wash the dishes.
  -- #debian-devel, Freenode, 2004-09-22
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link 

Re: [FFmpeg-user] hls and input http stream changes problem

[Michal Hajek]

pá 14. 2. 2020 v 16:57 odesílatel Ted Park  napsal:

> > What parameters make ffmpeg to accept all input streams?
>
> Try if adding -f mpegts -merge_pmt_versions 1 before the input works.
>

It seems to be working, thanks!

Michal


> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
>
> To unsubscribe, visit link above, or email
> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] h264 videos are darker

[Gyan Doshi]

On 17-02-2020 02:52 am, Ted Park wrote:

Thanks for the response; I'm a little confused about "output pixel format", as 
I thought that the -pix_fmt flag is for that. The -pixel_format flag seem to be for the 
input.
So question, what flag are you referring to? Is there another flag to be used 
for the 'output pixel format’?

I think pixel_format is just a private option for some decoders that should be 
mapped to pix_fmt. pix_fmt is both an input and output option, so if you put it 
before the input it is an input option and if you put it before the output it 
is an output option.


It's the other way around. -pix_fmt as input will be mapped to 
-pixel_format for the device/raw input demuxer if it exists. As an 
output option, it inserts a format filter at the end for that output stream.


Gyan
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] Question

[Ted Park]

> Would you be able to help me with why there are skipped segments and how I
> can avoid them? Because after it's downloaded there are frames in the video
> that are frozen. The website I am referring to is:
> https://ch.nicovideo.jp/nicopro if that's of any assistance. Also, if you
> don't mind would you be able to template the solution in a similar
> format that I have, that would be of great help.

Is that a live TV streaming site? (I think I’ve heard it being mentioned in 
Chihayafuru a couple weeks ago)
If you’re downloading a live stream, it most likely means that a segment was 
taken off the master playlist before it was downloaded, as in ffmpeg didn’t 
reach it in time. Something like forcing an HD resolution in a browser and 
missing a few seconds of the stream while the player buffers.
The first workaround that comes to mind is to choose a lower bitrate 
alternative to download than the default, with -map 0:p:# (replacing # with the 
program number). I can’t think of a way to make it switch streams depending on 
bandwidth requirements like what would happen in a browser player 
implementation.
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

[FFmpeg-user] WebVTT demuxer ignores processing every 1st line of each follow-up HLS webvtt-segment

[Reino Wijnsma]

Hello ffmpeg-user,

While reading this 
 
Github-issue-comment and testing the mentioned HLS-webvtt-url I first of all 
noticed that, unlike the user claims, ffmpeg does demux all the 
webvtt-segments. Why this is not happening for this user is most likely because 
of the old ffmpeg-binary he/she uses.
Secondly, what does happen is that ffmpeg doesn't remove the 2nd line of each 
webvtt-segment (except for the 1st segment).

The first webvtt-segment, 
'https://ga.video.cdn.pbs.org/videos/frontline/8f769cee-b6d6-437d-80b5-74252ed7642d/2000150564/hd-16x9-mezzanine-1080p/3717fes-captions0.vtt':

WEBVTT
X-TIMESTAMP-MAP=MPEGTS:187507, LOCAL:00:00:00.000

00:13.400 --> 00:17.400 position:10%,start line:85% size:80%
♪ ♪

00:17.400 --> 00:20.080 position:10%,start line:85% size:80%
WAAD (speaking Arabic):

[...]

03:11.320 --> 03:13.400 position:10%,start line:85% size:80%
(explosion roars)


With [ffmpeg -i 
https://ga.video.cdn.pbs.org/videos/frontline/8f769cee-b6d6-437d-80b5-74252ed7642d/2000150564/hd-16x9-mezzanine-1080p/3717fes-captions0.vtt
 3717fes-captions0.vtt] ffmpeg converts this to...

WEBVTT

00:13.400 --> 00:17.400
♪ ♪

00:17.400 --> 00:20.080
WAAD (speaking Arabic):

[...]

03:11.320 --> 03:13.400
(explosion roars)


...which is expected.
Converting the entire stream with [ffmpeg -i 
https://ga.video.cdn.pbs.org/videos/frontline/8f769cee-b6d6-437d-80b5-74252ed7642d/2000150564/hd-16x9-mezzanine-1080p/3717fes-captions.m3u8
 3717fes-captions.vtt] ffmpeg puts out...

WEBVTT

00:13.400 --> 00:17.400
♪ ♪

00:17.400 --> 00:20.080
WAAD (speaking Arabic):

[...]

03:11.320 --> 03:13.400
(explosion roars)
WEBVTT
X-TIMESTAMP-MAP=MPEGTS:187507, LOCAL:00:00:00.000

03:11.320 --> 03:13.400
(explosion roars)

[...]

05:56.440 --> 05:59.320
WAAD:
WEBVTT
X-TIMESTAMP-MAP=MPEGTS:187507, LOCAL:00:00:00.000

06:14.720 --> 06:16.800
(numerous explosions booming)

[...]

09:09.400 --> 09:12.960
MAN:
WEBVTT
X-TIMESTAMP-MAP=MPEGTS:187507, LOCAL:00:00:00.000

09:23.400 --> 09:25.440
SOLDIER:

[...]


So the very first "WEBVTT\nX-TIMESTAMP-MAP=MPEGTS:187507, LOCAL:00:00:00.000" 
does become "WEBVTT" and all the following instances (at the beginning of each 
webvtt-segment) should've been removed, but are simply ignored/copied.
Also allowing duplicate entries ("03:11.320 --> 03:13.400\n(explosion roars)") 
is weird to say the least.

FFmpeg used:

ffmpeg version N-96249-g81172b5-Reino Copyright (c) 2000-2020 the FFmpeg 
developers
  built with gcc 9.2.0 (GCC)
  configuration: --arch=x86 --target-os=mingw32 
--cross-prefix=/cygdrive/m/ffmpeg-windows-build-helpers-master/ffmpeg_local_builds/sandbox/cross_compilers/mingw-w64-i686/bin/i686-w64-mingw32-
 --pkg-config=pkg-config --pkg-config-flags=--static --extra-version=Reino 
--enable-gray --enable-version3 --disable-debug --disable-doc 
--disable-htmlpages --disable-manpages --disable-podpages --disable-txtpages 
--disable-w32threads --enable-avisynth --enable-frei0r --enable-filter=frei0r 
--enable-gmp --enable-gpl --enable-libaom --enable-libass --enable-libfdk-aac 
--enable-libflite --enable-libfontconfig --enable-libfreetype 
--enable-libfribidi --enable-libgme --enable-libmp3lame --enable-libopenmpt 
--enable-libopus --enable-libsoxr --enable-libvidstab --enable-libvorbis 
--enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 
--enable-libxml2 --enable-mbedtls --extra-cflags='-march=pentium3' 
--extra-cflags='-mtune=athlon-xp' --extra-cflags=-O2 
--extra-cflags='-mfpmath=sse'
--extra-cflags=-msse --enable-static --disable-shared 
--prefix=/cygdrive/m/ffmpeg-windows-build-helpers-master/ffmpeg_local_builds/sandbox/cross_compilers/mingw-w64-i686/i686-w64-mingw32
  libavutil  56. 38.100 / 56. 38.100
  libavcodec 58. 65.102 / 58. 65.102
  libavformat58. 35.101 / 58. 35.101
  libavdevice58.  9.102 / 58.  9.102
  libavfilter 7. 70.101 /  7. 70.101
  libswscale  5.  6.100 /  5.  6.100
  libswresample   3.  6.100 /  3.  6.100
  libpostproc55.  6.100 / 55.  6.100

-- Reino
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] h264 videos are darker

[Ted Park]

> Thanks for the response; I'm a little confused about "output pixel format", 
> as I thought that the -pix_fmt flag is for that. The -pixel_format flag seem 
> to be for the input. 
> So question, what flag are you referring to? Is there another flag to be used 
> for the 'output pixel format’?

I think pixel_format is just a private option for some decoders that should be 
mapped to pix_fmt. pix_fmt is both an input and output option, so if you put it 
before the input it is an input option and if you put it before the output it 
is an output option.


___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] How to compress .MOV file compatible to Canon camera

[Ulf Zibis]

Hey Moritz,

much thanks for your great suggestions. They sound really good. I'll try
all that.

-Ulf

Am 16.02.20 um 13:53 schrieb Moritz Barsnick:

On Sun, Feb 16, 2020 at 13:49:56 +0100, Moritz Barsnick wrote:

Note the "Constrained Baseline".

Alas, I don't know how to tell ffmpeg/libx264 to use this profile -
only "Baseline".

D'uh, I just noticed that using "-profile:v baseline" will get you a
Contrained Baseline output. I still recommend experimenting. ;-)

Moritz
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] Question

[Moritz Barsnick]

On Sat, Feb 15, 2020 at 11:11:53 +, CheeZe AMV's wrote:
> Would you be able to help me with why there are skipped segments and how I
> can avoid them? Because after it's downloaded there are frames in the video
> that are frozen. The website I am referring to is:
> https://ch.nicovideo.jp/nicopro if that's of any assistance.

On this list, it is of utmost assistance if you provide us with the
actual (real, minus private credentials) ffmpeg command line you used,
and its complete, uncut console output. There is lots of valuable
information in there.

Also please be sure to use the most latest version of ffmpeg. Please
retry with a version from git master to see whether your issue
persists.

(Windows:  https://ffmpeg.zeranoe.com/builds/, choose the "Nightly builds 
(2020021x)"
 Linux x86_64: https://johnvansickle.com/ffmpeg/,  choose from the "git master" 
column)

> Also, if you don't mind would you be able to template the solution in
> a similar format that I have, that would be of great help.

What do you mean by template? A command line?

Thanks,
Moritz
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] How to compress .MOV file compatible to Canon camera

[Moritz Barsnick]

On Sun, Feb 16, 2020 at 13:49:56 +0100, Moritz Barsnick wrote:
> Note the "Constrained Baseline".
>
> Alas, I don't know how to tell ffmpeg/libx264 to use this profile -
> only "Baseline".

D'uh, I just noticed that using "-profile:v baseline" will get you a
Contrained Baseline output. I still recommend experimenting. ;-)

Moritz
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] How to compress .MOV file compatible to Canon camera

[Moritz Barsnick]

On Sun, Feb 16, 2020 at 09:58:16 +0100, Ulf Zibis wrote:
> When I copy them back to the camera, they are no more playable on the
> camera. Damn, I wanted to save space on the memory card.
>
> Does anyone have an idea, which options maybe could help to get a
> compatible format for my camera?

You'll have to do some experimenting. On such a camera, video encoding
and decoding are mostly done in hardware. For H.264 on can say, the
more complex the format, the more complex the hardware needs to be.

H.264 and other codecs have so-called profiles and levels to describe
encoding characteristics. Your camera's hardware is likely to be
restricted to a certain maximum profile/level combination.

With ffmpeg's libx264 encoder (which was automatically selected when
you re-encoded to MOV), you can change the default profile with the
encoding options "-profile:v" and "-level:v". (The defaults
ffmpeg/libx264 use without these options depend on other things, such
as "-preset" and possibly resolution.)

Indeed, as you presume, your best bet is to try to copy the original
format:

> Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'MVI_1334.MOV':
>    Metadata:
>      major_brand : qt
>      minor_version   : 537331968
>      compatible_brands: qt  CAEP
>      creation_time   : 2020-02-07T11:35:24.00Z
>    Duration: 00:00:23.76, start: 0.00, bitrate: 22892 kb/s
>      Stream #0:0(eng): Video: h264 (Constrained Baseline) (avc1 / 
> 0x31637661), yuvj420p(pc, smpte170m/bt709/bt709), 1280x720, 22763 kb/s, 29.97 
> fps, 29.97 tbr, 30k tbn, 60k tbc (default)

Note the "Constrained Baseline".

Alas, I don't know how to tell ffmpeg/libx264 to use this profile -
only "Baseline". But you can try some of the others profile/level
combinations, as suggested in this Compatibity section in the wiki:

https://trac.ffmpeg.org/wiki/Encode/H.264#Compatibility

(The examples are for iOS, but apply to any hardware playback.)

Try from most complex (High) to most simple (Baseline) until it works.
Please note that the simpler profiles again result in larger file
sizes! You may get smaller results be reducing the quality slightly,
i.e. increasing the CRF (option "-crf") from its default 23 until you
actually notice changes.

Good luck,
Moritz
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

[FFmpeg-user] How to compress .MOV file compatible to Canon camera

[Ulf Zibis]

Hi,

on my Canon PowerShot A2200 I have some movies in Quicktime format.
I can compress them 5x without any visible quality lost.

When I copy them back to the camera, they are no more playable on the
camera. Damn, I wanted to save space on the memory card.

Does anyone have an idea, which options maybe could help to get a
compatible format for my camera?

Here is the terminal output:

$ ffmpeg -i MVI_1334.MOV -c:a copy MVI_1334.mov
ffmpeg version 4.2-static https://johnvansickle.com/ffmpeg/ Copyright
(c) 2000-2019 the FFmpeg developers
  built with gcc 6.3.0 (Debian 6.3.0-18+deb9u1) 20170516
  configuration: --enable-gpl --enable-version3 --enable-static
--disable-debug --disable-ffplay --disable-indev=sndio
--disable-outdev=sndio --cc=gcc-6 --enable-fontconfig --enable-frei0r
--enable-gnutls --enable-gmp --enable-libgme --enable-gray
--enable-libaom --enable-libfribidi --enable-libass --enable-libvmaf
--enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb
--enable-libopencore-amrwb --enable-libopenjpeg --enable-librubberband
--enable-libsoxr --enable-libspeex --enable-libsrt --enable-libvorbis
--enable-libopus --enable-libtheora --enable-libvidstab
--enable-libvo-amrwbenc --enable-libvpx --enable-libwebp
--enable-libx264 --enable-libx265 --enable-libxml2 --enable-libdav1d
--enable-libxvid --enable-libzvbi --enable-libzimg
  libavutil  56. 31.100 / 56. 31.100
  libavcodec 58. 54.100 / 58. 54.100
  libavformat    58. 29.100 / 58. 29.100
  libavdevice    58.  8.100 / 58.  8.100
  libavfilter 7. 57.100 /  7. 57.100
  libswscale  5.  5.100 /  5.  5.100
  libswresample   3.  5.100 /  3.  5.100
  libpostproc    55.  5.100 / 55.  5.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'MVI_1334.MOV':
  Metadata:
    major_brand : qt
    minor_version   : 537331968
    compatible_brands: qt  CAEP
    creation_time   : 2020-02-07T11:35:24.00Z
  Duration: 00:00:23.76, start: 0.00, bitrate: 22892 kb/s
    Stream #0:0(eng): Video: h264 (Constrained Baseline) (avc1 /
0x31637661), yuvj420p(pc, smpte170m/bt709/bt709), 1280x720, 22763 kb/s,
29.97 fps, 29.97 tbr, 30k tbn, 60k tbc (default)
    Metadata:
  creation_time   : 2020-02-07T11:35:24.00Z
    Stream #0:1(eng): Audio: pcm_u8 (raw  / 0x20776172), 12000 Hz,
mono, u8, 96 kb/s (default)
    Metadata:
  creation_time   : 2020-02-07T11:35:24.00Z
Stream mapping:
  Stream #0:0 -> #0:0 (h264 (native) -> h264 (libx264))
  Stream #0:1 -> #0:1 (copy)
Press [q] to stop, [?] for help
[libx264 @ 0x59406c0] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.1
Cache64
[libx264 @ 0x59406c0] profile Progressive High, level 3.1, 4:2:0, 8-bit
[libx264 @ 0x59406c0] 264 - core 157 r2969 d4099dd - H.264/MPEG-4 AVC
codec - Copyleft 2003-2019 - http://www.videolan.org/x264.html -
options: cabac=1 ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7
psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1
8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=3
lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 interlaced=0
bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1
b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250
keyint_min=25 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=crf
mbtree=1 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40
aq=1:1.00
Output #0, mov, to 'MVI_1334.mov':
  Metadata:
    major_brand : qt
    minor_version   : 537331968
    compatible_brands: qt  CAEP
    encoder : Lavf58.29.100
    Stream #0:0(eng): Video: h264 (libx264) (avc1 / 0x31637661),
yuvj420p(pc), 1280x720, q=-1--1, 29.97 fps, 30k tbn, 29.97 tbc (default)
    Metadata:
  creation_time   : 2020-02-07T11:35:24.00Z
  encoder : Lavc58.54.100 libx264
    Side data:
  cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: -1
    Stream #0:1(eng): Audio: pcm_u8 (raw  / 0x20776172), 12000 Hz,
mono, u8, 96 kb/s (default)
    Metadata:
  creation_time   : 2020-02-07T11:35:24.00Z
frame=   32 fps=0.0 q=0.0 size=   0kB time=00:00:01.42 bitrate=  
0.2kbits/sframe=   47 fps= 40 q=0.0 size=   0kB time=00:00:01.92
bitrate=   0.1kbits/sframe=   54 fps= 31 q=29.0 size=   0kB
time=00:00:01.92 bitrate=   0.1kbits/frame=   60 fps= 26 q=29.0
size=   0kB time=00:00:02.42 bitrate= 0.1kbits/frame=   66 fps= 23
q=29.0 size=   0kB time=00:00:02.42 bitrate=   0.1kbits/frame=   70
fps= 21 q=29.0 size= 256kB time=00:00:02.42 bitrate=
863.6kbits/frame=   76 fps= 19 q=29.0 size= 256kB time=00:00:02.92
bitrate= 716.1kbits/frame=   81 fps= 18 q=29.0 size= 256kB
time=00:00:02.92 bitrate= 716.1kbits/frame=   87 fps= 17 q=29.0
size= 256kB time=00:00:02.92 bitrate= 716.1kbits/frame=   92 fps= 16
q=29.0 size= 512kB time=00:00:03.42 bitrate=1223.0kbits/frame=   99
fps= 15 q=29.0 size= 512kB time=00:00:03.42
bitrate=1223.0kbits/frame=  103 fps= 15 q=29.0 size= 512kB
time=00:00:03.50 bitrate=1197.3kbits/frame=  109 fps= 15 q=29.0
size=