I’ve always thought that setting -crf [x] determines the output quality, while
(in the same line) -preset [x] affected the output file size.
(Where faster speeds result in bigger output files at the same quality.
But now this:
https://trac.ffmpeg.org/wiki/Encode/H.265
On 5/1/2020 3:18 PM, H wrote:
So you are saying that despite knowing the settings youtube-dl used when
recording the file, it is not possible to use that knowledge when using
ffmpeg to play the file back (barring damage while recording the file
which I have no evidence for)?
You may know certain
I discovered and logged a bug with Windows File Explorer related to the
matroska files and the metadata fields "Data rate" (for video track) and "Bit
rate" (for audio track). The matroska muxer generates a random number for
Track UID and when that number happens to be greater than the max
Am Sa., 2. Mai 2020 um 23:16 Uhr schrieb Rick Maschmann
:
>
> I discovered and logged a bug with Windows File Explorer related to the
> matroska files and the metadata fields "Data rate" (for video track) and "Bit
> rate" (for audio track). The matroska muxer generates a random number for
>