пн, 25 нояб. 2024 г., 01:11 Terje J. Hanssen <terjejhanssen@gmail.com>:

Den 24.11.2024 22:22, skrev Andrew Randrianasulu:

вс, 24 нояб. 2024 г., 19:45 Terje J. Hanssen <terjejhanssen@gmail.com>:

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.

Cingg Set Format Interlace Mode: Not interlaced
did the trick and both hdv and hd could be rendered
FFprobe reported it is pgogressiv, while native FFmpeg transcoding still say interlaced.

But do files rendered by cingg set to progressive and ffmpeg from same tff source differ visually?

No. It is easy to see during VLC  playback that neither av1_qsv from Cin/ffmpeg is progressive, but rather interlaced:
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.

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.

Hm. Then I guess I have no other way but to disable autoadding this flag especially for qsv(av1/h264/vp9).

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.)