www.makemkv.com

Woodstock wrote: Thu Oct 18, 2018 5:31 pm On BD sources, MakeMKV does a checksum of the files and tests it against the checksums on the disk; it is unusual for something to pass that process and have a glitch like you describe. Not impossible, just very, very unlikely.

If you play it in both, does the glitch occur in the same frame? Near a scene change? When there is suddenly a lot of action on the screen?

Woodstock wrote: Sun Oct 28, 2018 1:50 pm There are a lot of things it COULD be.

On a BD source where the play list consists of multiple M2TS files stitched together, scene transitions can be "rough", because the video transitions more abruptly than normal. Some segments might not even be the same resolution as the next, and the player is expected to make the transition.

Another possibility is that the glitch is intentional - but that is rare, unless you've picked the wrong play list on an obfuscated Lionsgate disk.

Do you have handbrake? One thing to try is to encode the video with it, and see if the glitch disappears. If it is a case of the transition being badly handled, SOMETIMES handbrake will smooth it out by inserting a proper key frame where the glitch happens. You don't have to encode the whole thing to test it; if you know where the glitch is, you can encode just that section and see if it fixes things.

Woodstock wrote: Sun Oct 28, 2018 1:50 pm There are a lot of things it COULD be.

On a BD source where the play list consists of multiple M2TS files stitched together, scene transitions can be "rough", because the video transitions more abruptly than normal. Some segments might not even be the same resolution as the next, and the player is expected to make the transition.

Another possibility is that the glitch is intentional - but that is rare, unless you've picked the wrong play list on an obfuscated Lionsgate disk.

Do you have handbrake? One thing to try is to encode the video with it, and see if the glitch disappears. If it is a case of the transition being badly handled, SOMETIMES handbrake will smooth it out by inserting a proper key frame where the glitch happens. You don't have to encode the whole thing to test it; if you know where the glitch is, you can encode just that section and see if it fixes things.

Woodstock wrote: Fri Nov 02, 2018 8:00 pm What titles are you having the issue with? Maybe some others here have had the same issue and not said anything at this point...

Woodstock wrote: Sun Nov 04, 2018 2:28 pm External drives can have issues with ripping long titles, if they're USB-powered. The drive electronics "hiccup" if the drive is spun too fast for the available power, can the operating system gets upset about it.

However, when that happens, the location varies, and MakeMKV will error out, and the file will be deleted. The same occurs if the drive (internal or external) decides to spend too much time reading a sector that has problems; The OS times out, the file is declared bad, and MakeMKV deletes it.

For MakeMKV to have saved the file, it passed a checksum test at the end, which is why this seems so weird.

Woodstock wrote: Sun Nov 04, 2018 5:25 pm The debug codes in the log are something Mike would have to look at. He holds the magic decoder ring that says what they mean.