On 2023-12-17 13:22, Bouke / Videotoolshed wrote:
On 17 Dec 2023, at 20:44, Nik Armstrong wrote:
On 2023-12-16 15:01, Erik Dobberkau wrote:
The ildct flag appears only to be making the output file "think" it
is
interlaced, when it is, in fact, progressive. It does not seem to be
doing
Sometimes it’s wanted / needed to have all files ’the same’.
> If that is interlaced, it’s interlaced. Codec should say ‘interlaced’, no
> matter the actual content.
>
> For Avid media, that might (depending on the version of MC) be important
> for a ‘fast import’, or omitting adapters you don’t
> On 17 Dec 2023, at 20:44, Nik Armstrong wrote:
>
> On 2023-12-16 15:01, Erik Dobberkau wrote:
>> The ildct flag appears only to be making the output file "think" it is
>>> interlaced, when it is, in fact, progressive. It does not seem to be doing
>>> anything to change the footage
On 2023-12-16 15:01, Erik Dobberkau wrote:
The ildct flag appears only to be making the output file "think" it is
interlaced, when it is, in fact, progressive. It does not seem to be
doing
anything to change the footage (quality-wise and it's still
progressive).
Since someone other than myself
The ildct flag appears only to be making the output file "think" it is
> interlaced, when it is, in fact, progressive. It does not seem to be doing
> anything to change the footage (quality-wise and it's still progressive).
> Since someone other than myself set the flag on this command, I am
On 2023-12-14 12:50, Nik Armstrong wrote:
I've encountered a scenario where someone else has programmed an
ffmpeg encoding command with flags that seem puzzling, and I'm having
difficulty understanding their purpose.
The command in question is:
ffmpeg -loglevel info -y -r 29.97 -start_number 0
I've encountered a scenario where someone else has programmed an ffmpeg
encoding command with flags that seem puzzling, and I'm having
difficulty understanding their purpose.
The command in question is:
ffmpeg -loglevel info -y -r 29.97 -start_number 0 -i
image_sequence_%4d.png -vcodec dnxhd
