Basic Questions

[Kettykrueger]

Hi all

I’m having trouble with my rips. I just want to know;

Is it possible for MakeMKV to complete, not display any errors, yet still have corruption in the file?

Finally, if so, how do I ensure a perfect rip?

Thanks

[Woodstock]

If NO errors are displayed, it would be rare for MakeMKV to produce a corrupt MKV file.

That said, I cannot say it is impossible, but the potential is very low. There are multiple checks in place.

The debug log would be necessary to know more.

[Kettykrueger]

Cheers for that, Woodstock.

It appears to be a lot of my rips have glitches, missing frames, AV sync errors in them. This has been confirmed by trying the files in multiple apps (Plex, VLC and a Blu Ray app on the Mac, name escapes me).

If MakeMKV is not the cause, what else could be?

[Woodstock]

AV sync errors are mostly harmless - MakeMKV adjusts the audio tracks to compensate when moving between segments in different M2TS files.

Glitches can come from many sources, including a damaged file, but also including exceeding the bandwidth between the server and the player.

The way to confirm if the file is good is to try playing it "locally", that is, file and player both on same device. Also, if the glitches occur at the exact same place every time you play the file on ALL devices/players, it is more likely the file is damaged. If they move around, though, bandwidth is more likely.

I can only say that, in well over 2,000 disks ripped, I've not had a bad file generated without an error being reported. With the exception of BD+ problems, MakeMKV doesn't save the file if uncorrectable read errors exist.

When MakeMKV says there is a problem with BD+, it will rip the file, but there will be issues with playback. I do not count those, because I do not save the files with the BD+ still in them (I submit the dump file and wait for an SVQ to be issued).

[Kettykrueger]

Thanks for the reply.

I’ve ripped about 200 titles, three of them that I’ve checked so far have had glitches in them. By glitch, I mean dropped frames mainly. In one instance there were visual artefacts too.

I have tired playing them locally too, glitches in the same places.

It’s weird because, I’ve done this before. I ripped all my titles a couple of years ago with the same hardware and setup and those files were fine. But I decided to re-rip them and this time, I’m having problems.

I’m inclined to believe the drive is at fault, but saying that, I believe MakeMKV would fail?

Not sure what to do to be honest. It’s really frustrating, especially having had it work fine before.

EDIT: do you know of any other way of verifying files without playing them?

EDIT 2: I've also just tried moving the file to my local hard drive (from ab external drive) but the glitch was there too. That rules out the hard drive.

[Kettykrueger]

I’m starting to think that 1.12.3 is the problem.

All my rips with this version so far have had dropped frames in them.

I’ve just ripped two movies with 1.12.0, watched them and they’ve been perfect.

Could 1.12.3 have issues with ripping?

[Woodstock]

You must have missed the message in the general section from two weeks ago: https://makemkv.com/forum/viewtopic.php?f=1&t=17872

[Kettykrueger]

I saw that but am not experiencing those problems. I don’t get errors, the file saves fine, it just has dropped frames in it.

It’s a damn shame too because I ripped my entire collection with it!

[Woodstock]

If 1.12.3 completes saving a track, it SHOULD be fine; The problem is when it decides there are too many errors to save the track.

[Kettykrueger]

I think I’ve found a new problem then!

Unless it’s a coincidence that all the four rips I tried with 1.12.3 all had problems with them and the two I’ve tried with 1.12.0 have been fine?

[Kettykrueger]

Ha ha, I think I spoke too soon!

Sorry about that. Watched a 1.12.0 rip last night and it had dropped frames.

Woodstock - what could this be? Now, I can only think it’s either the drive or the fact that I’m writing to an external hard drive. Although, the latter didn’t cause problems before.

Any insights?

[Woodstock]

Not sure what the issue could be.

When it happens, does it happen in the same place, regardless of the playback software? I've seen what looks like dropped frames in certain high-bit-rate sources, and I've seen "glitches" during scene transitions, where the MKV file was constructed from multiple M2TS files via a play list. The latter is more noticeable when the source changes resolution at the boundary, but that is VERY rare.

If it happens at the same place each time you rip a specific source, I would follow the procedure outlined in the FAQ in my signature and send the relevant files to support@makemkv.com for Mike to look at. He will probably contact you for additional information (I'm going through this right now with disk 1 of Skip Beat).

[mike admin]

Sorry about that. Watched a 1.12.0 rip last night and it had dropped frames.
Woodstock - what could this be? Now, I can only think it’s either the drive or the fact that I’m writing to an external hard drive. Although, the latter didn’t cause problems before.

Is your source DVD or blu-ray? If blu-ray and you are not getting any hash check errors, then your drive read all data without errors and MakeMKV validated that.

Do you have expert mode enabled? any AV sync messages at all?

[Kettykrueger]

Sorry about that. Watched a 1.12.0 rip last night and it had dropped frames.
Woodstock - what could this be? Now, I can only think it’s either the drive or the fact that I’m writing to an external hard drive. Although, the latter didn’t cause problems before.

Is your source DVD or blu-ray? If blu-ray and you are not getting any hash check errors, then your drive read all data without errors and MakeMKV validated that.

Do you have expert mode enabled? any AV sync messages at all?

Thanks for the reply, Mike.

Blu-rays. I don't think I've seen any hash error messages, and I've had expert mode on.

It's been hard to diagnose because I did most of the rips about a month ago, so obviously don't have logs, and it requires watching the movies to determine any problems. The ones I had problems with, I re-ripped and they didn't have the same problems.

I think I need to re-rip some more, keep the logs and report any issues.

It doesn't make sense to have files with errors in them if no errors are reported.

[Kettykrueger]

Hi

I finally have an update to this. So I re-ripped a movie as the first version had glitches in it, I saved the log this time. Just watched it and it glitched again, different place this time, but still a glitch; pixilation for a second.

Here is the log:

Debug log started at Sun Sep 30 16:04:52 2018 , written by MakeMKV v1.12.3 darwin(x64-release)
Using 524544KB for read cache.
001005:0000 MakeMKV v1.12.3 darwin(x64-release) started
001004:0000 Debug logging enabled, log will be saved as /Users/family/MakeMKV_log.txt
002010:0000 Optical drive "BD-RE TSSTcorp BDDVDW SE-506BB TS00d" opened in OS access mode.
003007:0000 Using direct disc access mode
005050:0000 Evaluation version, 26 day(s) out of 30 remaining
DEBUG: Code 2365587456 at f=Xy"e"yY$f/\gZd:29405660
DEBUG: Code 0 at f=Xy"e"yY$f/\gZd:213139943
DEBUG: Code 0 at ,,F[\O1Kvxjn[m=c:29400623
DEBUG: Code 2147483648 at f=Xy"e"yY$f/\gZd:213133250
DAFD=PAAAADAAAAEABDQkEHwECAQ==
DCE=VOqlwe9OezyusL7E/sUG4RgevQ4woSUlfKZg1LrmTbu8OdEFU8ACmEPoFJnCuUjkldcRgLUIwcDMKL50Gp5YupIUxw09BdGoRAxitEzjxMdAyCJaVZcenMNYycDTtmkALQcbdwgSwbw2cPth66tpIA1QkVhGdAc5DA==
DCE=ZmgMVWkc/nE8EThtdGB3u0Evon6WWDilZ7y21inP3szeKkE8HHRx1YdLRHp2gwU7vkhMYZ9cn8Y+DcTjhF/iWA0E7vdz3g3/y9SuO5Xf6AcZU1l4dQp9gaXEfjrm+D3GABjqXGOb4raNmr+1Yqdicpi6KH1J43WvQQ==
005085:0000 Loaded content hash table, will verify integrity of M2TS files.
DISCID=22C8988404F98D61F8078CD5AD421D888BFFDFF4
003307:0000 File 00001.mpls was added as title #0
003025:0000 Title #00102.mpls has length of 60 seconds which is less than minimum title length of 3000 seconds and was therefore skipped
003025:0000 Title #00000.m2ts has length of 14 seconds which is less than minimum title length of 3000 seconds and was therefore skipped
003025:0000 Title #00001.m2ts has length of 212 seconds which is less than minimum title length of 3000 seconds and was therefore skipped
003025:0000 Title #00081.m2ts has length of 60 seconds which is less than minimum title length of 3000 seconds and was therefore skipped
003025:0000 Title #00082.m2ts has length of 0 seconds which is less than minimum title length of 3000 seconds and was therefore skipped
003025:0000 Title #00083.m2ts has length of 0 seconds which is less than minimum title length of 3000 seconds and was therefore skipped
003025:0000 Title #00104.m2ts has length of 42 seconds which is less than minimum title length of 3000 seconds and was therefore skipped
003025:0000 Title #00502.m2ts has length of 5 seconds which is less than minimum title length of 3000 seconds and was therefore skipped
003025:0000 Title #00503.m2ts has length of 5 seconds which is less than minimum title length of 3000 seconds and was therefore skipped
003025:0000 Title #00504.m2ts has length of 5 seconds which is less than minimum title length of 3000 seconds and was therefore skipped
003025:0000 Title #00205.m2ts has length of 5 seconds which is less than minimum title length of 3000 seconds and was therefore skipped
003025:0000 Title #04999.m2ts has length of 30 seconds which is less than minimum title length of 3000 seconds and was therefore skipped
003025:0000 Title #00021.m2ts has length of 1 seconds which is less than minimum title length of 3000 seconds and was therefore skipped
003025:0000 Title #00022.m2ts has length of 3 seconds which is less than minimum title length of 3000 seconds and was therefore skipped
003025:0000 Title #00101.m2ts has length of 42 seconds which is less than minimum title length of 3000 seconds and was therefore skipped
003025:0000 Title #00105.m2ts has length of 20 seconds which is less than minimum title length of 3000 seconds and was therefore skipped
005011:0000 Operation successfully completed
005014:0000 Saving 1 titles into directory /Volumes/My Poor Brain/Movies
004001:0000 Forced subtitles track #3 turned out to be empty and was removed from output file
005005:0080 1 titles saved
005036:0104 Copy complete. 1 titles saved.

Please help!!