[BLKMGK]

Originally Posted by forkicks

I can confirm this. In my case, i narrowed it down to a couple of files that i was trying to convert from avc to 265. The extraction phase could not get the video file from it, and would (wrongly) use the video265 file that was leftover on the Temp folder from the previous conversion, resulting in a file with the correct output name, wrong video track and correct audio track. Also, ripbot showed no error.

In my view, this could be fixed in one of two ways:
1 (and best): before every new file, clear all existing items in the temp folder. This way it would fail and detect the fail because no previous file would exist that could be reused

2: Try to detect when video track extraction fails better. No idea what was causing it to fail in the first place, the file read perfectly fine, no errors, no sync problems, nothing reported wrong at all by other programs (mkvtoolnix, for example).

This is a really big problem because i also run several dozen file batches per day, and now i can't be sure if my previous conversions are right or not. This is silent data corruption at its worst, and in my case, i caught it completely by chance. I'm running the latest version (could not find any updates just now).

Thank your for your time,
fK

Well, at least it isn't just me! Sadly unlike when I was creating files with no soundtrack (don't check the "skip demuxing" box!) I cannot easily find the files with bad data. I am HOPING I caught it early by happenstance and got lucky as spot checking a pile of files didn't find bad ones but that would be a miracle if true!