• AnyStream is having some DRM issues currently, Netflix is not available in HD for the time being.
    Situations like this will always happen with AnyStream: streaming providers are continuously improving their countermeasures while we try to catch up, it's an ongoing cat-and-mouse game. Please be patient and don't flood our support or forum with requests, we are working on it 24/7 to get it resolved. Thank you.

AnyDVD can't rip the disc correctly.

chenzhuo

Well-Known Member
Thread Starter
Joined
Dec 30, 2019
Messages
46
Likes
10
The real size of disc is 40.2 GB, but I just created 193MB documents after ripping. I couldn't rip the disc correctly. Please help.
 

Attachments

  • AnyDVD_8.5.7.0_Info_E_AAA_C15D12CC_00000000.ziplog
    1.4 MB · Views: 8
There is no AACS encryption on this disc. Therefore I guess it is a bad copy since there are also read errors on this disc which results in the end that your copy fails.
You can try to clean it and try again but if it is a bad burn you are out of luck. DDRescue and DVDisaster may still read it in but it will take a hell lot of time.
 
There is no AACS encryption on this disc. Therefore I guess it is a bad copy since there are also read errors on this disc which results in the end that your copy fails.
You can try to clean it and try again but if it is a bad burn you are out of luck. DDRescue and DVDisaster may still read it in but it will take a hell lot of time.
But AnyDVD didn't show any error information to me. It shows "rip complete" in the end.
 
But AnyDVD didn't show any error information to me. It shows "rip complete" in the end.
Looks like AnyDVD found a lot of read errors to me. Is this an original disc or a copy? AnyDVD shows it to be a BD-R.
Current profile: BD-R

WARNING: Read errors on disc!
47.13s: read sectors failed, sense 3:11:5
47.13s: tries 9 retry 20365248 to 20365264
54.47s: read sectors failed, sense 3:11:5
54.47s: tries 8 retry 20365248 to 20365264
64.53s: read sectors failed, sense 3:11:5
64.53s: tries 7 retry 20365248 to 20365264
73.28s: read sectors failed, sense 3:11:5
73.28s: tries 6 retry 20365248 to 20365264
81.27s: read sectors failed, sense 3:11:5
81.27s: tries 5 retry 20365248 to 20365264
88.30s: read sectors failed, sense 3:11:5
88.30s: tries 4 retry 20365248 to 20365264
96.94s: read sectors failed, sense 3:11:5
96.94s: tries 3 retry 20365248 to 20365264
103.98s: read sectors failed, sense 3:11:5
103.98s: tries 2 retry 20365248 to 20365264
114.05s: read sectors failed, sense 3:11:5
114.05s: tries 1 retry 20365248 to 20365264
121.08s: read sectors failed, sense 3:11:5
121.09s: tries 0 retry 20365248 to 20365264
121.09s: read error 20365248 to 20365264, max 21112960, io->read_error 1
128.13s: read sectors failed, sense 3:11:5
128.13s: tries 9 retry 20365253 to 20365254
135.16s: read sectors failed, sense 3:11:5
135.16s: tries 8 retry 20365253 to 20365254
142.20s: read sectors failed, sense 3:11:5
142.20s: tries 7 retry 20365253 to 20365254
149.23s: read sectors failed, sense 3:11:5
149.25s: tries 6 retry 20365253 to 20365254
156.30s: read sectors failed, sense 3:11:5
156.30s: tries 5 retry 20365253 to 20365254
163.33s: read sectors failed, sense 3:11:5
163.33s: tries 4 retry 20365253 to 20365254
170.39s: read sectors failed, sense 3:11:5
170.39s: tries 3 retry 20365253 to 20365254
177.42s: read sectors failed, sense 3:11:5
177.42s: tries 2 retry 20365253 to 20365254
185.28s: read sectors failed, sense 3:11:5
185.30s: tries 1 retry 20365253 to 20365254
192.33s: read sectors failed, sense 3:11:5
192.34s: tries 0 retry 20365253 to 20365254
192.34s: read error 20365253 to 20365254, max 21112960, io->read_error 1
 
It's a BD-R with Blulock protection, it appears (not a copy, they're sold that way).
The correct playlist, I would assume, is playlist #0 with a whopping 3h 46min duration (unless there's something new and crazy going on).
The read errors don't seem to be protection related. They should also affect playback at around 3:42:35
 
It's a BD-R with Blulock protection, it appears (not a copy, they're sold that way).
The correct playlist, I would assume, is playlist #0 with a whopping 3h 46min duration (unless there's something new and crazy going on).
The read errors don't seem to be protection related. They should also affect playback at around 3:42:35
Do you mean that the disc is damaged and the damage at around 3:42:35?
 
No he means blu-lock. A certain time based mechanism that discs can't be decrypted until a certain date. That duration is just the estimated proper playlist.

Sent from my Pixel 3 XL using Tapatalk
 
My bad then, than what's blu-lock?

Sent from my Pixel 3 XL using Tapatalk
 
My bad then, than what's blu-lock?
A copy protection, that only works on BD-R. Amazon uses it for Disc-On-Demand (low volume discs).
Has a messy playlist layout (worse than Screen Pass), is simpler, though (less complicated, more complex).
Also uses screwed-up clpi files and self-overlapping stream files.
And has deliberate read errors in bogus clips. Which is why I had to look very closely at this one, but the remaining read errors that AnyDVD ran into, clearly seem to be in the playable area of the main movie.
These BD-R discs are a little more likely to have real read errors than BDROM.
 
Back
Top