On rare occasions (e.g., 4 out of 453 sessions), the DWICount and BaselineCount values in InterlaceChecker are non-sensible, as if they haven't been initialized properly.
e.g.,
DWICount: -1300997086; BaselineCount: 1300997134
FWIW, in all 4 instances, the DWICount was a large negative value, and the BaselineCount was a large positive value. Interestingly, the sum of the two nonetheless accurately reflects the total number of frames remaining after the slicewise check stage.
Also, I don't know if this is somewhat related, but in 3 of 453 sessions which "failed" at the gradient checking stage due to "Too many bad gradient directions found", I get non-sensible values such as the following in the terminal output (or equivalent, the output of the --resultsNotesFile argument):
GradientTotal#/LeftGradientTotal#: 52/1911268545
Baseline#/LeftBaseline#: 2/1904214016
Gradient#/LeftGradient#: 50/7054529
GradientDir#/LeftGradientDir#: 25/-1024065536
On rare occasions (e.g., 4 out of 453 sessions), the DWICount and BaselineCount values in InterlaceChecker are non-sensible, as if they haven't been initialized properly.
e.g.,
DWICount: -1300997086; BaselineCount: 1300997134
FWIW, in all 4 instances, the DWICount was a large negative value, and the BaselineCount was a large positive value. Interestingly, the sum of the two nonetheless accurately reflects the total number of frames remaining after the slicewise check stage.
Also, I don't know if this is somewhat related, but in 3 of 453 sessions which "failed" at the gradient checking stage due to "Too many bad gradient directions found", I get non-sensible values such as the following in the terminal output (or equivalent, the output of the --resultsNotesFile argument):
GradientTotal#/LeftGradientTotal#: 52/1911268545
Baseline#/LeftBaseline#: 2/1904214016
Gradient#/LeftGradient#: 50/7054529
GradientDir#/LeftGradientDir#: 25/-1024065536