I recently purchased the Sony MOD release on BD-R of Not Another Teen Movie, because apparently they are never going to issue this on a BD-ROM and I wanted the movie. The movie plays fine on two different bluray players I own. When I tried to rip it with version 8.1.0.0 it keeps hanging up when it starts reading the m2ts file. And the clip files and playlist files rip very slowly. I have tried this on three different bluray drives on two computers. As I said, it plays fine on 2 different bluray players, so it has to be how the disc looks to AnyDVD/Redfox. I am attaching the logfile for help. I hope we can fix this. Because they sell this on a BD-R (which is ridiculous by the way, especially since it costs 23 bucks..), I want to back it up for when the BD-R goes bad (which it seems half of them inevitably do, especially dual layer BD-Rs)
-
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.
Problems with ripping Sony MOD Not Another Teen Movie
- Thread starter dtrell
- Start date
As it has no copy protection AnyDVD does nothing to this so any problems ripping is down to the disc itself.
Also the film was officially released on Blu-ray in Nov 2016 in the US according to Blu-ray.com
http://www.blu-ray.com/movies/Not-Another-Teen-Movie-Blu-ray/26473/
Also the film was officially released on Blu-ray in Nov 2016 in the US according to Blu-ray.com
http://www.blu-ray.com/movies/Not-Another-Teen-Movie-Blu-ray/26473/
Last edited:
The have some kind of protection on it. When I look at the size of the folder on the disc, it says 208GB. Obviously this is not possible on a DL BD-R. Something is fooling the computer. his is a disturbing trend if they can produce a commercially available disc of an older movie that is not 4K that AnyDVD cannot rip.
Yes, they issued it on a BDR. Its called the Sony MOD program. It has not ever been released on a BD-ROM. Its supposed to be a budget version of their blurays, but for 23 bucks it really isn't. I bought it from Best Buy. In fact, they aren't even allowed to use the bluray logo because its not a BD-ROM. They have to use the words "Blu-ray Disc"
It won't rip as in iso. It will not read it using AnyDVD, DVDFab or Roxio.. The disc is fine. Plays perfectly on my bluray players.....for now...
Again, disturbing that there is a commercial double layer bluray out there that we can not make a copy of for our own use.
Playing is not the same as ripping. When playing players can skip over small read errors, when ripping you can't. Blu-ray discs do not contain sector copy protection like DVD's, so if you can't make an ISO then it's because the disc is faulty as the error log states.
That's why there's a section about it in the 'Please READ THIS before you post' sticky
From your logfile
If you open Imgburn with the disc in the drive what is the disc ID?
That's why there's a section about it in the 'Please READ THIS before you post' sticky
From your logfile
Code:
6.72s: read sectors failed, sense 3:11:5
6.72s: tries 9 retry 11737536 to 11737552
10.09s: WM_POWERBROADCAST 0x5
11.89s: read sectors failed, sense 3:11:5
11.93s: tries 8 retry 11737536 to 11737552
17.10s: read sectors failed, sense 3:11:5
17.10s: tries 7 retry 11737536 to 11737552
22.25s: read sectors failed, sense 3:11:5
22.25s: tries 6 retry 11737536 to 11737552
27.38s: read sectors failed, sense 3:11:5
27.38s: tries 5 retry 11737536 to 11737552
32.53s: read sectors failed, sense 3:11:5
32.53s: tries 4 retry 11737536 to 11737552
37.66s: read sectors failed, sense 3:11:5
37.66s: tries 3 retry 11737536 to 11737552
42.81s: read sectors failed, sense 3:11:5
42.81s: tries 2 retry 11737536 to 11737552
47.94s: read sectors failed, sense 3:11:5
47.94s: tries 1 retry 11737536 to 11737552
51.42s: WM_POWERBROADCAST 0x5
53.09s: read sectors failed, sense 3:11:5
53.09s: tries 0 retry 11737536 to 11737552
53.09s: read error 11737536 to 11737552, max 11741312, io->read_error 1
54.18s: standard udf
54.18s: label NOT_ANOTHER_TEEN_MOVIE
61.31s: WM_POWERBROADCAST 0x5
66.88s: read sectors failed, sense 3:11:5
66.88s: tries 9 retry 11736832 to 11736848
72.01s: read sectors failed, sense 3:11:5
72.01s: tries 8 retry 11736832 to 11736848
74.44s: WM_POWERBROADCAST 0x5
77.16s: read sectors failed, sense 3:11:5
77.16s: tries 7 retry 11736832 to 11736848
82.29s: read sectors failed, sense 3:11:5
82.29s: tries 6 retry 11736832 to 11736848
87.42s: read sectors failed, sense 3:11:5
87.42s: tries 5 retry 11736832 to 11736848
92.56s: read sectors failed, sense 3:11:5
92.56s: tries 4 retry 11736832 to 11736848
97.70s: read sectors failed, sense 3:11:5
97.70s: tries 3 retry 11736832 to 11736848
102.84s: read sectors failed, sense 3:11:5
102.84s: tries 2 retry 11736832 to 11736848
107.98s: read sectors failed, sense 3:11:5
107.98s: tries 1 retry 11736832 to 11736848
113.12s: read sectors failed, sense 3:11:5
113.12s: tries 0 retry 11736832 to 11736848
113.12s: read error 11736832 to 11736848, max 11741312, io->read_error 1
118.26s: read sectors failed, sense 3:11:5
118.26s: tries 9 retry 11736836 to 11736837
123.40s: read sectors failed, sense 3:11:5
123.40s: tries 8 retry 11736836 to 11736837
128.54s: read sectors failed, sense 3:11:5
128.54s: tries 7 retry 11736836 to 11736837
133.69s: read sectors failed, sense 3:11:5
133.69s: tries 6 retry 11736836 to 11736837
138.82s: read sectors failed, sense 3:11:5
138.84s: tries 5 retry 11736836 to 11736837
143.97s: read sectors failed, sense 3:11:5
143.97s: tries 4 retry 11736836 to 11736837
149.11s: read sectors failed, sense 3:11:5
149.11s: tries 3 retry 11736836 to 11736837
154.25s: read sectors failed, sense 3:11:5
154.25s: tries 2 retry 11736836 to 11736837
159.39s: read sectors failed, sense 3:11:5
159.39s: tries 1 retry 11736836 to 11736837
164.53s: read sectors failed, sense 3:11:5
164.53s: tries 0 retry 11736836 to 11736837
164.53s: read error 11736836 to 11736837, max 11741312, io->read_error 1
169.67s: read sectors failed, sense 3:11:5
169.67s: tries 9 retry 11736837 to 11736838
174.82s: read sectors failed, sense 3:11:5
174.82s: tries 8 retry 11736837 to 11736838
179.96s: read sectors failed, sense 3:11:5
179.96s: tries 7 retry 11736837 to 11736838
185.10s: read sectors failed, sense 3:11:5
185.10s: tries 6 retry 11736837 to 11736838
190.23s: read sectors failed, sense 3:11:5
190.23s: tries 5 retry 11736837 to 11736838
195.38s: read sectors failed, sense 3:11:5
195.38s: tries 4 retry 11736837 to 11736838
200.51s: read sectors failed, sense 3:11:5
200.51s: tries 3 retry 11736837 to 11736838
205.66s: read sectors failed, sense 3:11:5
205.66s: tries 2 retry 11736837 to 11736838
210.80s: read sectors failed, sense 3:11:5
210.80s: tries 1 retry 11736837 to 11736838
215.94s: read sectors failed, sense 3:11:5
215.94s: tries 0 retry 11736837 to 11736838
215.94s: read error 11736837 to 11736838, max 11741312, io->read_error 1
221.07s: read sectors failed, sense 3:11:5
221.07s: tries 9 retry 11736838 to 11736839
226.22s: read sectors failed, sense 3:11:5
226.22s: tries 8 retry 11736838 to 11736839
231.35s: read sectors failed, sense 3:11:5
231.35s: tries 7 retry 11736838 to 11736839
236.50s: read sectors failed, sense 3:11:5
236.50s: tries 6 retry 11736838 to 11736839
241.63s: read sectors failed, sense 3:11:5
241.63s: tries 5 retry 11736838 to 11736839
246.78s: read sectors failed, sense 3:11:5
246.78s: tries 4 retry 11736838 to 11736839
251.91s: read sectors failed, sense 3:11:5
251.91s: tries 3 retry 11736838 to 11736839
257.06s: read sectors failed, sense 3:11:5
257.06s: tries 2 retry 11736838 to 11736839
262.19s: read sectors failed, sense 3:11:5
262.19s: tries 1 retry 11736838 to 11736839
267.34s: read sectors failed, sense 3:11:5
267.34s: tries 0 retry 11736838 to 11736839
267.34s: read error 11736838 to 11736839, max 11741312, io->read_error 1
272.47s: read sectors failed, sense 3:11:5
272.49s: tries 9 retry 11736839 to 11736840
277.62s: read sectors failed, sense 3:11:5
277.62s: tries 8 retry 11736839 to 11736840
282.75s: read sectors failed, sense 3:11:5
282.75s: tries 7 retry 11736839 to 11736840
287.90s: read sectors failed, sense 3:11:5
287.90s: tries 6 retry 11736839 to 11736840
293.03s: read sectors failed, sense 3:11:5
293.03s: tries 5 retry 11736839 to 11736840
298.18s: read sectors failed, sense 3:11:5
298.18s: tries 4 retry 11736839 to 11736840
303.31s: read sectors failed, sense 3:11:5
303.33s: tries 3 retry 11736839 to 11736840
308.46s: read sectors failed, sense 3:11:5
308.46s: tries 2 retry 11736839 to 11736840
313.59s: read sectors failed, sense 3:11:5
313.59s: tries 1 retry 11736839 to 11736840
318.74s: read sectors failed, sense 3:11:5
318.74s: tries 0 retry 11736839 to 11736840
318.74s: read error 11736839 to 11736840, max 11741312, io->read_error 1
323.87s: read sectors failed, sense 3:11:5
323.87s: tries 9 retry 11736840 to 11736841
329.02s: read sectors failed, sense 3:11:5
329.02s: tries 8 retry 11736840 to 11736841
334.15s: read sectors failed, sense 3:11:5
334.15s: tries 7 retry 11736840 to 11736841
339.30s: read sectors failed, sense 3:11:5
339.30s: tries 6 retry 11736840 to 11736841
344.44s: read sectors failed, sense 3:11:5
344.44s: tries 5 retry 11736840 to 11736841
349.58s: read sectors failed, sense 3:11:5
349.58s: tries 4 retry 11736840 to 11736841
354.71s: read sectors failed, sense 3:11:5
354.71s: tries 3 retry 11736840 to 11736841
359.86s: read sectors failed, sense 3:11:5
359.86s: tries 2 retry 11736840 to 11736841
365.00s: read sectors failed, sense 3:11:5
365.00s: tries 1 retry 11736840 to 11736841
370.14s: read sectors failed, sense 3:11:5
370.14s: tries 0 retry 11736840 to 11736841
370.14s: read error 11736840 to 11736841, max 11741312, io->read_error 1
..........If you open Imgburn with the disc in the drive what is the disc ID?
Last edited:
nebostrangla
Well-Known Member
- Joined
- Sep 2, 2007
- Messages
- 1,144
- Likes
- 462
Also since it states that it has no protection. Disable AnyDvDHD by right-clicking the Fox icon in the traybar. And then use imgburn to make an ISO. If there is no issue with the disc (Bad sectors) then it will make a.ISO.
Be sure to re-enable AnyDvDHD when done.
See screenshot of menu that will appear:
I would think that using the built-in ripper of AnyDvDHD with (keep protection) ticked "should" do the same thing but @James , @Pete or another team member would have to verify that.
i think adbear is probably right. there are probably disc errors that players can ignore and error correct, but straight rips and copies cannot have read errors. i got the playlist using bdinfo and i am going to try using tsmuxer to piece them together and make a ts file. the file with the issue is not part of the main playlist so that may work.
Ch3vr0n
Translator NL
- Joined
- Sep 27, 2009
- Messages
- 24,312
- Likes
- 3,530
The shop doesn't know that do they. Unless the person that sold it to you also sold you the player, actively uses and lives at your house. If AnyDVD has read errors it ALWAYS either a defective disc and/or drive. If the drive reads and rips other discs fine, it's your disc. It's that simple.
- Joined
- Nov 8, 2013
- Messages
- 5,635
- Likes
- 3,508
That is not entirely true nor is it entirely wrong.
This "playing is not the same as ripping" myth has been misinterpreted a lot.
Yes, players can skip read errors - if they are not too "deadly" - sometimes you'll notice, sometimes you won't.
BUT: CloneBD (not sure about CloneDVD) will do the same thing. A few unreadable sectors will be "skipped" and a warning will be shown. Only if the defect is too massive, the copy will abort.
AnyDVD doesn't (though it could).
The more relevant difference between ripping and playing is a completely different one: often the read errors are in areas, that simply didn't get read when determining that "it plays ok" (there have been cases where users later said, they only checked the first 5 minutes to "prove" that it plays OK).
And when ripping, the usual goal is to read every bit, so you won't miss those read errors.
That is in fact what is happening on this one. And it is also how the sector copy protections work - bad sectors in areas, that are never played, the trick is to find out, what can get played and what not.
And I'm pretty sure, this one has, indeed, a copy protection based on read errors.
It is possible on a BD-R - for the same reason you will find that a 3D Blu-ray disc has 80 or 90 GB.
There are files referencing the same physical space on the disc, that way it looks like there is more stuff on it than there really is.
This is a normal, spec conforming feature of the UDF file system.
In this particular case there are files that reference the same block over and over.
For example 19860.m2ts, claims to be 145.201.152 bytes but really is 14.518.272
Have you tried CloneBD? I believe that would be the best tool to fix this one.
A full disc copy won't work, but you can try a partial copy and select only what really belongs to the disc (as far as you can tell - the titlestrip display on the selection page is a tremendous help for that).
I believe, title/playlist 1 is the main movie.
The read errors on that disc are exactly in some of those messed up multiple-self-referencing clips, so that's why I'm pretty sure, they are deliberate.
Last edited:
- Joined
- Oct 22, 2005
- Messages
- 21,801
- Likes
- 3,787
Is it "really" a BD-R? Or is it a pressed disc, which claims to be a BD-R?
A disc, which "claims" to be a BD-R would be a way to save AACS licensing fees, as BD players must refuse to play a BD-ROM without AACS.
- Joined
- Nov 8, 2013
- Messages
- 5,635
- Likes
- 3,508
See here: http://www.blu-ray.com/news/?id=19669
Sony has confirmed that the films will be presented on BD-R media: "BD-R media is the format being used for our Blu-ray Manufacture-on-Demand product. While we're excited by this opportunity to bring a curated slate of titles to market, we also appreciate that playback functionality is of utmost importance and have ensured quality at every step of the process.