Sicario Backup doesn't play correct main title playlist

Please post here for issues related to Blu-ray discs
Post Reply
Message
Author
Zoopere
Posts: 2
Joined: Tue Jul 07, 2026 11:01 pm

Sicario Backup doesn't play correct main title playlist

#1 Post by Zoopere » Wed Jul 08, 2026 12:23 am

I have a UHD/Blu-ray version of Sicario. Unfortunately the BR was physically damaged on the main video file (00501.m2ts) and my problem started when I tried to make a copy of the BR so I'd have a working physical disc. I created an encrypted backup of the disc with MakeMKV. I used ddrescue to save as much of the damaged m2ts file as possible and then used another physical BR with a damaged copy of 00501.m2ts (but not damaged in the exact same sectors as mine) to create a working, undamaged encrypted copy of 00501.m2ts. I verified all this by loading the encrypted backup into MakeMKV and ripping out the main title. It was perfect. So, I then created an ISO from the good encrypted backup, loaded that into MakeMKV, and created a decrypted backup.

When I played the new decrypted backup, the main title didn't play properly. It stated fine but around 5:14 into the film it jumped to a black screen proclaiming a bad copy and then played the rest of the film out of order. Using Process Monitor and BDEdit I figured out the damaged BR disc, when starting the main title, called 03001.jar which eventually led to 00364.mpls which called 00501.clpi which called 00501.m2ts. All good. But, my decrypted copy did something different when starting the main title. It called 03001.jar which eventually led to 00497.mpls which called 00501.clpi & 03208.clpi which called 00501.m2ts & 03208.m2ts in the order I saw them.

I'm guessing that BD-J is checking for something (what I don't know) and not finding it plays that different main title playlist, starting the chain of the incorrect main title being played.

I tried the quick and simple fix of copying 00364.mpls and renaming it 00497.mpls. This resulted in a blank screen on the player with no sound, no total time shown, but when hitting FF a final time equal to the movie length being shown in the pop-up display with play time ticking down. I tried a similar approach with BDEdit, making 00497.mpls equal to 00364.mpls. Same failed result.

Anybody have an idea what's happening and how to fix this? If it's BD-J causing all this, can I use JD-GUI to modify something to avoid the problem? Other options?

tomty89
Posts: 184
Joined: Sun Dec 13, 2020 8:48 am

Re: Sicario Backup doesn't play correct main title playlist

#2 Post by tomty89 » Wed Jul 08, 2026 10:23 am

Zoopere wrote: Wed Jul 08, 2026 12:23 am Using Process Monitor and BDEdit I figured out the damaged BR disc, when starting the main title, called 03001.jar which eventually led to 00364.mpls which called 00501.clpi which called 00501.m2ts. All good. But, my decrypted copy did something different when starting the main title. It called 03001.jar which eventually led to 00497.mpls which called 00501.clpi & 03208.clpi which called 00501.m2ts & 03208.m2ts in the order I saw them.
No experience with any of the BD-J stuff (or "Process Monitor and BDEdit"), but given what you have written, it sounds to me that the copy somehow ended up with a different 03001.jar, or that the jar thing is simply irrelevant, or it's some sort of copy protection mechanism (in which case the whole "project salvage 00501.m2ts" story would be irrelevant).

What are you using to play them btw? VLC? Does it make any difference when you play the "good encrypted backup" instead? Is 00501.m2ts the only file that is "different" between the "good encrypted backup" and the "the damaged BR disc"?

Zoopere
Posts: 2
Joined: Tue Jul 07, 2026 11:01 pm

Re: Sicario Backup doesn't play correct main title playlist

#3 Post by Zoopere » Wed Jul 08, 2026 4:35 pm

Yes, the 00501.m2ts is the only difference between the "good encrypted backup" and the "the damaged BR disc". The .jar file is the exact same.
Playing with PowerDVD but I also burned a rewriteable BR to check on my standalone player and it evidenced the same behavior.
It seems like a copy protection mechanism but I've never seen this behavior before on the very few BR discs I've burned. Thus the hope somebody in the Forum has and knows what to do.

Post Reply