<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<br>
<br>
<br>
<div class="moz-cite-prefix">Den 24.11.2024 23:30, skrev Andrew
Randrianasulu:<br>
</div>
<blockquote type="cite"
cite="mid:CA+rFky7rLsE8wAWa4Uqczu_rWs4=KO_PHMgS8cPfjz_JaOwZcw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="auto">
<div><br>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">пн, 25 нояб. 2024 г.,
01:11 Terje J. Hanssen <<a
href="mailto:terjejhanssen@gmail.com"
moz-do-not-send="true" class="moz-txt-link-freetext">terjejhanssen@gmail.com</a>>:<br>
</div>
<blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div> <br>
<br>
<br>
<div>Den 24.11.2024 22:22, skrev Andrew Randrianasulu:<br>
</div>
<blockquote type="cite">
<div dir="auto">
<div><br>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">вс, 24 нояб.
2024 г., 19:45 Terje J. Hanssen <<a
href="mailto:terjejhanssen@gmail.com"
target="_blank" rel="noreferrer"
moz-do-not-send="true"
class="moz-txt-link-freetext">terjejhanssen@gmail.com</a>>:<br>
</div>
<blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div> <br>
I can't notice differences at playback with
VLC and FFplay (other than 16:9 vs 4:3
format as usual). And both visually with
good qualities in my eyes.<br>
<br>
<font face="monospace">Cingg Set Format
Interlace Mode: Not interlaced<br>
did the trick and both hdv and hd could be
rendered <br>
FFprobe reported it is pgogressiv, while
native FFmpeg transcoding still say
interlaced.<br>
</font></div>
</blockquote>
</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">But do files rendered by cingg set
to progressive and ffmpeg from same tff source
differ visually?</div>
</div>
</blockquote>
<br>
No. It is easy to see during VLC playback that neither
av1_qsv from Cin/ffmpeg is progressive, but rather
interlaced:<br>
Pause during horizontal movements (camcorder panning)
shows interlaced vertical edges. Then shortcut "D" on
this still image swithch it to deinterlaced and smoother
edges. This is on a computer LCD monitor.<br>
<br>
I rendered also with global_quality=25 (switched on in
Cingg preset), which then gives higher bitrate and
quality comparable with the output from the native
ffmpeg 7.1.<br>
</div>
</blockquote>
</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">Hm. Then I guess I have no other way but to
disable autoadding this flag especially for qsv(av1/h264/vp9).</div>
<div dir="auto"><br>
</div>
<div dir="auto">You can try to make other qsv profiles with
"format set to progressive hack" in the meantime. (there
should also be mjpeg and mpeg2 encoders - not most useful but
it will be interesting to know if they share same
chocke-on-ildct behavior with av1/h264/vp9.)</div>
<div dir="auto"><br>
</div>
<br>
</div>
</blockquote>
I have not found other interlaced test files, and I think 1080i hdv
as already tested are the main source for interlaced mpeg2.<br>
The other mpeg2 video files I have prepared for dvd via ffmpeg and
dvde, are all progressive.<br>
<br>
From the url below I have tested a few mjpeg clips. Mediainfo
doesn't report any scan type about them, so I think they are not
field interlaced but frame based, as they also render ok with
av1_qsv. Else they seems to be faulty possibly with regards to
timing, as the playback speed seemingly is all too fast<br>
<a class="moz-txt-link-freetext" href="https://filesamples.com/formats/mjpeg?utm_content=cmp-true">https://filesamples.com/formats/mjpeg?utm_content=cmp-true</a><br>
<br>
<br>
<br>
<br>
<br>
</body>
</html>