Is this some protection method that MakeMKV isn't handling?

Please post here for issues related to Blu-ray discs
Post Reply
Falloutboy
Posts: 12
Joined: Thu Jan 11, 2018 1:03 pm

Is this some protection method that MakeMKV isn't handling?

Post by Falloutboy »

Is this some protection method that MakeMKV isn't handling?
Or just a damaged disk?

There are 24 blu rays in the set that I just backed up on a file by file basis to hard drive 23 of them had no issues but on the 10th disk in the set I get this:

< I didn't want to leave anything out but i did trim messages that occurred like 20 times in a row>

Note this plays on a blu ray player no problems but an LG and an ASUS blu ray drive when trying to play it on a computer can't.

The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806639616, attempting to work around
The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806639616-806645760, attempting to work around
The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806645760, attempting to work around

The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806645760-806651904, attempting to work around

The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806651904, attempting to work around
The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806651904-806658048, attempting to work around

The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806658048, attempting to work around
The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806658048-806664192, attempting to work around

The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806664192, attempting to work around
The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806664192-806670336, attempting to work around

The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806670336, attempting to work around
The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806670336-806676480, attempting to work around
The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806676480, attempting to work around
The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806744064, attempting to work around

The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806744064-806750208, attempting to work around

The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806750208, attempting to work around
The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806750208-806756352, attempting to work around

The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806756352, attempting to work around
The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806756352-806762496, attempting to work around

The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806762496, attempting to work around
The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806762496-806768640, attempting to work around
The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806768640, attempting to work around

The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806768640, attempting to work around
The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806768640-806774784, attempting to work around
The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806774784, attempting to work around

The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806774784, attempting to work around
The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806774784-806780928, attempting to work around
The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806780928, attempting to work around

The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806780928, attempting to work around
The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806780928-806787072, attempting to work around

The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806787072, attempting to work around
The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806787072-806793216, attempting to work around

The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806799360, attempting to work around
The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806799360-806805504, attempting to work around

The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806805504, attempting to work around
The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806805504-806811648, attempting to work around

The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806811648, attempting to work around
The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806811648-806817792, attempting to work around

The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806940672, attempting to work around
The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806940672-806946816, attempting to work around

The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806946816, attempting to work around
The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806946816-806952960, attempting to work around

The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806952960, attempting to work around
The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806952960-806959104, attempting to work around

The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806959104, attempting to work around
The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806959104-806965248, attempting to work around

The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806965248, attempting to work around
The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806965248-806971392, attempting to work around

The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806971392, attempting to work around
The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806971392-806977536, attempting to work around

The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806977536, attempting to work around
The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806977536-806983680, attempting to work around

The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806983680, attempting to work around
The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806983680-806989824, attempting to work around

The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806989824, attempting to work around
The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806989824-806995968, attempting to work around

The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806995968, attempting to work around
The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 806995968-807002112, attempting to work around

The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 810565632, attempting to work around
The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 813766656, attempting to work around
The source file '/BDMV/STREAM/00050.m2ts' is corrupt or invalid at offset 810565632, attempting to work around
AV sync issue in stream 1 at 0:03:38.517 with duration of 10.666ms : broken timecode, apparent audio skew is -853.333ms
AV sync issue in stream 1 at 0:03:38.538 with duration of 21.333ms : audio gap - 2 missing frame(s)
AV sync issue in stream 1 at 0:03:38.741 with duration of 32ms : audio gap - 3 missing frame(s)
AV sync issue in stream 1 at 0:03:38.805 with duration of 32ms : audio gap - 3 missing frame(s)
AV sync issue in stream 1 at 0:03:38.880 with duration of 21.333ms : audio gap - 2 missing frame(s)
Failed to save title 3 to file

{Update}
I have performed a Backup of the blu ray in question and although the file 0050.mts seems to be there in it's entirety it plays back with corruption in it - I have included the log for the backup up to a point here.

MakeMKV v1.10.9 win(x64-release) started
The new version 1.12.0 is available for download at http://www.makemkv.com/download/
Backing up disc into folder "E://backup/STE_S2_D4"
Evaluation version, 3 day(s) out of 30 remaining
Loaded content hash table, will verify integrity of M2TS files.
Hash check failed for file 00050.m2ts at offset 806873088, file is corrupt.
Hash check failed for file 00050.m2ts at offset 807069696, file is corrupt.
Hash check failed for file 00050.m2ts at offset 807266304, file is corrupt.
Hash check failed for file 00050.m2ts at offset 807462912, file is corrupt.
Hash check failed for file 00050.m2ts at offset 807659520, file is corrupt.
Too many hash check errors in file 00050.m2ts.
Hash check for /BDMV/STREAM/00050.m2ts : 0.04% corrupt, 99.94% correct, 99.99% checked.

Again is this a bad disk or some sort of copy protection, the fact that the disk reads without errors and it is the file checksums themselves that fail suggests some sort of protection on this one disk.
Woodstock
Posts: 8043
Joined: Sun Jul 24, 2011 11:21 pm

Re: Is this some protection method that MakeMKV isn't handli

Post by Woodstock »

MakeMKV v1.10.9 win(x64-release) started
The new version 1.12.0 is available for download at http://www.makemkv.com/download/
Start by updating to a current version - you're two releases behind.

Then make sure the disk is clean; the "invalid" messages usually refer to areas that were either read with errors or were unreadable. Where most drives used to return a read failure when a sector didn't read properly, some now return a "best guess" at the contents, which then turn out to be formatted wrong.
MakeMKV Frequently Asked Questions
How to aid in finding the answer to your problem: Activating Debug Logging
Falloutboy
Posts: 12
Joined: Thu Jan 11, 2018 1:03 pm

Re: Is this some protection method that MakeMKV isn't handli

Post by Falloutboy »

I'm guessing at this point that this is something that MakeMKV simply can't handle.

Why?
Through a little fiddling with another program I have the 0050.m2ts file

The disk title plays without any fault on a home theater blu - ray system but on a PC it skips and shows corruption so I am making the assumption that blu ray home theater systems are more fault tolerant and able to handle these things where as PC's read what they read and if it's wrong it's wrong end of story.

The disk is brand new out of the box and not a mark on it even when checked with a magnifying glass and a 50x inspection camera but consistently fails on 3 different PC's and works on two different blu ray home theater systems.

From my perspective I am returning the set for replacement - there is no reason why 23 disks out of the 24 should play ball and this one does not.
Woodstock
Posts: 8043
Joined: Sun Jul 24, 2011 11:21 pm

Re: Is this some protection method that MakeMKV isn't handli

Post by Woodstock »

You might think that, but... Star Trek: Enterprise is NOT on the list of "cannot be ripped!" disks; Others have ripped it, and you've obviously ripped other disks in the season, because you're complaining about a problem with one disk, and not the other 23. It would be extremely unlikely that the studio would use a different copy protection scheme on ONE track of ONE disk of a set.

There is something specific to YOUR disk and drive in play here. As I said, there are a number of BD drives that will fake data when they can't read a track cleanly. MakeMKV checks the data for consistency, and several areas on that disk failed the consistency check.
Through a little fiddling with another program I have the 0050.m2ts file
That's a very ambiguous statement. From what you say, the other program didn't read it either, until you "fiddled with it". Did you tell it to ignore errors?
MakeMKV Frequently Asked Questions
How to aid in finding the answer to your problem: Activating Debug Logging
rivey
Posts: 129
Joined: Fri Dec 29, 2017 3:49 pm
Location: Los Angeles

Re: Is this some protection method that MakeMKV isn't handli

Post by rivey »

Woodstock wrote:You might think that, but... Star Trek: Enterprise is NOT on the list of "cannot be ripped!" disks; Others have ripped it, and you've obviously ripped other disks in the season, because you're complaining about a problem with one disk, and not the other 23. It would be extremely unlikely that the studio would use a different copy protection scheme on ONE track of ONE disk of a set.
Woodstock, is there an actual "cannot be ripped" list and if so where can I find it? It would be helpful information to have. Thanks!
Woodstock
Posts: 8043
Joined: Sun Jul 24, 2011 11:21 pm

Re: Is this some protection method that MakeMKV isn't handli

Post by Woodstock »

Not an official one that I know of, but there are some disks that have not been generally solved. Among them are "screener" DVDs, which have non-standard things done to them.
MakeMKV Frequently Asked Questions
How to aid in finding the answer to your problem: Activating Debug Logging
rivey
Posts: 129
Joined: Fri Dec 29, 2017 3:49 pm
Location: Los Angeles

Re: Is this some protection method that MakeMKV isn't handli

Post by rivey »

Woodstock wrote:Not an official one that I know of, but there are some disks that have not been generally solved. Among them are "screener" DVDs, which have non-standard things done to them.
That makes sense. I had a client 8 or 10 years ago that had to have a special DVD player in his home theater system to play the DVD's for Academy Award consideration. I was told that they would not play in a regular player. Thanks for the info.
Falloutboy
Posts: 12
Joined: Thu Jan 11, 2018 1:03 pm

Re: Is this some protection method that MakeMKV isn't handli

Post by Falloutboy »

Woodstock wrote:You might think that, but... Star Trek: Enterprise is NOT on the list of "cannot be ripped!" disks; Others have ripped it, and you've obviously ripped other disks in the season, because you're complaining about a problem with one disk, and not the other 23. It would be extremely unlikely that the studio would use a different copy protection scheme on ONE track of ONE disk of a set.

There is something specific to YOUR disk and drive in play here. As I said, there are a number of BD drives that will fake data when they can't read a track cleanly. MakeMKV checks the data for consistency, and several areas on that disk failed the consistency check.
Through a little fiddling with another program I have the 0050.m2ts file
That's a very ambiguous statement. From what you say, the other program didn't read it either, until you "fiddled with it". Did you tell it to ignore errors?
I used AndDVD and copied the m2ts file apparently without errors... go figure.
Falloutboy
Posts: 12
Joined: Thu Jan 11, 2018 1:03 pm

Re: Is this some protection method that MakeMKV isn't handli

Post by Falloutboy »

Woodstock wrote:
MakeMKV v1.10.9 win(x64-release) started
The new version 1.12.0 is available for download at http://www.makemkv.com/download/
Start by updating to a current version - you're two releases behind.

Then make sure the disk is clean; the "invalid" messages usually refer to areas that were either read with errors or were unreadable. Where most drives used to return a read failure when a sector didn't read properly, some now return a "best guess" at the contents, which then turn out to be formatted wrong.
Did that it made no difference. Same errors.
Falloutboy
Posts: 12
Joined: Thu Jan 11, 2018 1:03 pm

Re: Is this some protection method that MakeMKV isn't handli

Post by Falloutboy »

Falloutboy wrote:I'm guessing at this point that this is something that MakeMKV simply can't handle.

Why?
Through a little fiddling with another program I have the 0050.m2ts file

The disk title plays without any fault on a home theater blu - ray system but on a PC it skips and shows corruption so I am making the assumption that blu ray home theater systems are more fault tolerant and able to handle these things where as PC's read what they read and if it's wrong it's wrong end of story.

The disk is brand new out of the box and not a mark on it even when checked with a magnifying glass and a 50x inspection camera but consistently fails on 3 different PC's and works on two different blu ray home theater systems.

From my perspective I am returning the set for replacement - there is no reason why 23 disks out of the 24 should play ball and this one does not.
Okay I still don't quite know what to make of this one. I can't rip it with MakeMKV as I get errors I can however play it on a Blu Ray home theatre system without errors - I am presuming because they are made to be error tolerant. and I can quite happily play that episode with no issues in VLC from the disk but not with the freeware Leawo software. AnyDVD copies the m2ts file without throwing any errors and the m2ts seems to play o.k.

I am beginning to think it is a mastering fault but because it plays "o.k" according to the suppliers and there is no fault from their perspective but I quite literally can't rip it direct to an MKV file.

What do you guys do in this situation?

BTW I now seem to be having a similar issue with another disk from a different series.
mlwdofc
Posts: 1
Joined: Sat Oct 06, 2018 6:31 am

Re: Is this some protection method that MakeMKV isn't handling?

Post by mlwdofc »

I have the same problem. It started suddenly. I know it's not the disk(s), because I ripped the disk(s) just a few weeks ago. Also, the disk(s) rip fine on another computer. I know it's not the DVD player, because it plays DVD's successfully; not to mention that I have 2 DVD players in my system and both exhibit the same problem.

What do I think it is? Something to do with the Linux kernel. I am running Linux Mint with kernel 4.15.0-20-generic on the system that quit working (yet worked just a week ago). I am running Linux Mint with kernel 4.13.0-20-generic on the system that continues to work. If I hadn't decided to re-rip about 20 DVD's (that I ripped on 2 different systems just weeks ago), I wouldn't be so confident in ruling out the DVD's or hardware.

Part of my error message: The source file '/BDMV/STREAM/00001.m2ts' is corrupt or invalid at offset 2433153024, attempting to work around

I think an update to the kernel (or perhaps a package) isn't compatible with my currently installed version of MKV.

MakeMKV v.1.12.3 [linux(x64-release)]
GUI version : v1.12.3 [for x86_64-linux-gnu]
License type: Registered
This version expires: Never
Linux Mint 19 Tara
Note: I paid for a license of MKV.
Woodstock
Posts: 8043
Joined: Sun Jul 24, 2011 11:21 pm

Re: Is this some protection method that MakeMKV isn't handling?

Post by Woodstock »

Does the error message stream continue with something about the drive not being available or off-line?

You really don't give much to go on.

Have you read this message yet? https://makemkv.com/forum/viewtopic.php?f=1&t=17872
MakeMKV Frequently Asked Questions
How to aid in finding the answer to your problem: Activating Debug Logging
rdr001
Posts: 1
Joined: Tue Oct 09, 2018 5:57 am

Re: Is this some protection method that MakeMKV isn't handling?

Post by rdr001 »

Having similar issues (apparent bad reads) on two different win 10 pro computers with different BD drives. BD discs play fine on my players. I'm thinking also that this is a protection issue. Problem is new for me! I don't have access to Anydvd to test theory.
Woodstock
Posts: 8043
Joined: Sun Jul 24, 2011 11:21 pm

Re: Is this some protection method that MakeMKV isn't handling?

Post by Woodstock »

Could be as simple as cleaning the disk. Dirty disks are definitely a form of copy protection that MakeMKV can't handle. :)
MakeMKV Frequently Asked Questions
How to aid in finding the answer to your problem: Activating Debug Logging
Post Reply