Target file has 5498 frames, but should have 2749 frames! - Problem with interlaced content. about staxrip HOT 7 CLOSED

🤔 Basically that should have nothing to do with this issue.

Yep. The output file was 50 FPS but it was deinterlaced the wrong way, every other frame was backwards, therefore extreme choppy. But as I said, alone by enabling and disabling another filter the problem was already solved.

from staxrip.

Thanks for the detailed report, I was able to reproduce it. Seems one of the performance updates has its issues, so I will revert it.

So my guess is there is problem with interlaced content.

That's right, it's only the information about the target that are broken, the encode itself is not affected.

A fix is coming soon...

from staxrip.

I've hit the same issue 2 times already since upgrade to 2.38.
I don't use interlaced video, so it is not related to it.
Instead I have custom filter that selects preconfigured number of frames to do compressibility check. I always disable it for final encode but seems sometime it is ignored when this mismatch warning appears. The final encode is OK.

--------------------------- Frame Mismatch ---------------------------

WARNING: Target file has 128978 frames, but should have 2528 frames!
Encoding was probably terminated at 5102.0% with a mismatch of -126450 frames!

--------------------------- Frame Mismatch ---------------------------

Target file has 128978 frames, but should have 2528 frames!

from staxrip.

🤔 Basically that should have nothing to do with this issue. But we will see how it looks like after the next fix, maybe there is something that interferes.

from staxrip.

Thanks for the information.
The fix will be released soon, probably tomorrow. In the meantime you can disable Frame Mismatch in the project options to not get annoyed after each encode. 😕

from staxrip.

That's right, it's only the information about the target that are broken, the encode itself is not affected.

@Dendraspis For completeness, my encoding, or to be more precise the deinterlacing, was affected. It was choppy as hell.

from staxrip.

Very interesting...

The next version including the fix will be released soon, so I close this now. Feel free to reopen it when the issue eith the information persist or open a new one in case there are other problems.

from staxrip.