Hmmm, this is very confusing. I had asked before about BDRB automatically re-encoding some MKV files because the target size was ample to fit them. Even with ‘ForceNoEncode=1’ (or the proper equivalent, I don’t remember right at the moment )
I was told by both Neuron2 and Sharc that BDRB must be re-encoding because the MKV’s AR must not be compliant (which they weren’t because as I explained before a friend backing up my Blu-rays incorrectly by stripping out the ‘Black bars’)
So, I’m thinking, 'Oh, that’s great then, so all I have to do (lazily) is simply import the ‘bad’ MKV file into BDRB and it will automatically re-encode and add the black bars to make it compliant, right? And, I set it for High Quality 2 pass. So, I’m thinking, ‘Great! it will fix this and make it compliant and playable on my OPPO Blu-ray player.’
Well… I just did my first file that way and when checking the resulting m2ts file with MediaInfo (BEFORE burning it) it shows the AR to be the original 2.40:1…?!!
So, what exactly was BDRB doing with all that supposed re-encoding then? According to MedioInfo, it did NOT correct or ‘fill out’ the resolution like I had hoped. And, on a side note, the original file was about 14 Gigs including of course the full HD audio; the resulting size was a full BD-25 (which WAS the target size, but I was kind of surprised that it used it all) But, no foul there, I just wonder WHY…?
So, DOES BDRB indeed re-encode a MKV file through ‘Import’ and correct an improper AR or doesn’t it? Is there an additional setting that I need to make it do that?
Also, VERY curiously, if I was told that that was precisely why BDRB was forcing a re-encode earlier, why not now…???
Thanks kindly for any ideas!