History Channel's "The Universe"

[Tbone289]

There are 5 titles on this disc, and I have only been able to back up 1 of them successfully so far. I will post error message later today.

[Tbone289]

Disregard this thread. I reinserted the disc and it ripped successfully. I hope this isn't the beginning of intermittent problems with my blu-ray drive.

[Tbone289]

This seems to be more than just bad luck. I'm having trouble with the whole "Universe" series of Blu-ray discs. I have tried to rip the second disc about 8 times, and have eventually had good rips on the first three (of 5) titles. I get a "corrupt or bad offset" error on each of the titles, then try them again, and again, until they finally are successful.

While ripping title 5, I received these errors, then MakeMKV ended with a fatal error:

The source file '/BDMV/STREAM/00004.M2TS' is corrupt or invalid at offset 4295350272, attempting to work around.

The source file '/BDMV/STREAM/00004.M2TS' is corrupt or invalid at offset 4295356416, attempting to work around.

Other times I receive this type of error (or errors), and MakeMKV locks up with a "not responding".

[crowfax]

Code: Select all

The source file '/BDMV/STREAM/00004.M2TS' is corrupt or invalid at offset 4295350272, attempting to work around.
The source file '/BDMV/STREAM/00004.M2TS' is corrupt or invalid at offset 4295356416, attempting to work around.

This is not a MakeMKV issue.

This is a hardware issue.

Your drive can not read the disc.

The disc may be poorly manufactured, damaged, or dirty. You may not be able to see the imperfections with the naked eye. This does not mean they are not there.

You may wish to try cleaning the disc with soapy water and a soft cloth. It is common for new blu-ray discs to have a light greasy film over them.

If that does not work then return the disc for a new one.

[Tbone289]

Thanks for the response crowfax.

I figured that was probably the case, as I've had zero issues with MakeMKV up to this point. I'm betting that it's a problem with the discs themselves. They're clean, but they have sort of an irregular pattern to the read surface, similar to the prismatic effect of an oil sheen on water that I've not noticed on other blurays. These are fairly old discs, so I'm not sure if I can get them replaced at this point. I guess I should have tried backing them up a long time ago, but I figured they were OK since they've always played fine.

Is there any chance that doing a full-disc backup first might remedy the read errors?

Thanks again.

[crowfax]

The "backup" function will confirm to you which parts of the disc are damaged via a hash check that is stored on the disc vs. what your drive is able to read. How usable the output is from the backup function however will be down to the extent of the read failures.

[jumboag]

I'm running into the same problem on Season 1 Disk 1 (so far). The strange thing is that I can backup the disk fine. MakeMKV doesnt give me any errors when I do that, but if I try to extract from the backup (or from the original disk) it freezes the app with the above mentioned errors.

Makes me think its using some encoding scheme that makemkv cant handle or something.

[Romansh]

The "backup" function will confirm to you which parts of the disc are damaged via a hash check that is stored on the disc vs. what your drive is able to read. How usable the output is from the backup function however will be down to the extent of the read failures.

FWIW, I always do a backup first and generate MKV files from the backup.

Sometimes MakeMKV gives me errors when trying to generate an MKV file directly from the disc (including "The source file X is corrupt or invalid at offset Y, attempting to work around").

But the backup completes without any errors (hash check or otherwise), and creating the MKV from the backup also completes without errors.

[jumboag]

on these disks I'm running into problems with generating the mkv from the backup as well as from the disk directly. I've done the backup both ways (both with and without decrypting it). Backup succeeds, but I'm intermittently running into issues creating the MKV's from it.

Very odd.

[jumboag]

crowfax, with all due respect I believe I can prove you to be wrong on your assertion that this is a disk issue. In some cases, you are most certainly correct but with these disks I believe you are not, especially since multiple people are experiencing it.

My logic:

the MakeMKV "backup" function works perfectly on them. (with our w/o a decode). The hash results match up indicating no data integrity issues. An actual bad disk would spit out a hash error.

If you use makeMKV on the backup files (not the disk), it still tends to error out with the "corrupt or invalid" message.

Handbrake now works with a raw bluray m2ts file as long as its decrypted. On two different disks, I've taken a successful makeMKV backup and then failed to convert the files to MKVs. In both instances, Handbrake was able to correctly process the decoded m2ts files and convert them into m4v's.

This seems to indicate that makeMKV is for certain raw data flagging it as corrupt when in fact its not. Not a huge deal for me since I now have a valid workaround, but since I've always been a fan of this software: mike admin, I'd like to offer up any data from my end if you want logs, etc (or even temporarily install a debug library if you need further data) if this is something you wish to pursue.