FFAStrans 1.4.0.2 Interlacing Analyzer issue

Here you can submit bugreports
Post Reply
Pogle
Posts: 12
Joined: Fri Mar 27, 2020 10:03 am

FFAStrans 1.4.0.2 Interlacing Analyzer issue

Post by Pogle »

Hello!

The Interlacing Analyzer doesn't determine reliable results anymore. I work with IMX D-10 files (MXF OP1a), always flagged as 50i in header, but the content varies (progressive and interlaced material). In v 1.3 I always got reliable values for "outcome" and "confidence". In v 1.4.0.2 I always get "outcome" = 1, "confidence" = 0 regardless of the actual scan type of the material. (using/not using the AV Decoder hasn't influence here)

(my settings: Percent of media: 25, Start from: 0, Max analyze duration: 300)

regards
emcodem
Posts: 1812
Joined: Wed Sep 19, 2018 8:11 am

Re: FFAStrans 1.4.0.2 Interlacing Analyzer issue

Post by emcodem »

I can confirm and reproduce this very easy, also it is still there in 1.4.0.4... Thanks for reporting!

The problem is that we updated ffmpeg and the new version outputs the values 2 times while the first time all values are set to 0 and only the second output line contains the correct values. Unfortunately our code takes this first value.

Code: Select all

[Parsed_idet_0 @ 0000019b675c6a40] Repeated Fields: Neither:     0 Top:     0 Bottom:     0
[Parsed_idet_0 @ 0000019b675c6a40] Single frame detection: TFF:     0 BFF:     0 Progressive:     0 Undetermined:     0
[Parsed_idet_0 @ 0000019b675c6a40] Multi frame detection: TFF:     0 BFF:     0 Progressive:     0 Undetermined:     0
frame=   52 fps=0.0 q=-0.0 Lsize=N/A time=00:00:02.04 bitrate=N/A speed=3.17x
[Parsed_idet_0 @ 0000019b6756a100] Repeated Fields: Neither:    66 Top:     1 Bottom:     1
[Parsed_idet_0 @ 0000019b6756a100] Single frame detection: TFF:    68 BFF:     0 Progressive:     0 Undetermined:     0
[Parsed_idet_0 @ 0000019b6756a100] Multi frame detection: TFF:    68 BFF:     0 Progressive:     0 Undetermined:     0
Possible workaround could be to replace the internal ffmpeg.exe to the old version but i would not really recommend this because there might be lots of other stuff that was changed to match new behaviour.

@admin might want to change the code of _proc_helpers.au3 Func _detect_interlacing to catch the last occurence of the lines starting with "Parsed_idet_0"
emcodem, wrapping since 2009 you got the rhyme?
Post Reply