The Burning Plain - Fail To Save

Please post here for issues related to DVD discs
Post Reply
Message
Author
Chest Rockwell
Posts: 36
Joined: Fri Jun 04, 2010 4:22 pm

The Burning Plain - Fail To Save

#1 Post by Chest Rockwell » Sat Oct 09, 2010 11:18 pm

I get an immediate FAILED TO SAVE with the DVD "The Burning Plain." I resurfaced the disk and there are no obvious physical smudges or defects on the disk surface. I have also tried two different optical drives and get the same result. This is from the original commercial DVD I bought. Log is:

Debug log started at Sat Oct 09 22:53:06 2010 , written by MakeMKV v1.6.0 win(x86-release)
Using 521472KB for read cache.
001005:0000 MakeMKV v1.6.0 win(x86-release) started
001004:0000 Debug logging enabled, log will be saved as C:\Users\Zap Brannigan/MakeMKV_log.txt
003007:0000 Using direct disc access mode
003025:0000 Title #0 has length of 286 seconds which is less than minimum title length of 500 seconds and was therefore skipped
003028:0000 Title #1 was added (7 cell(s), 0:09:09)
003028:0000 Title #2 was added (7 cell(s), 0:09:09)
003025:0000 Title #3 has length of 11 seconds which is less than minimum title length of 500 seconds and was therefore skipped
003025:0000 Title #4 has length of 11 seconds which is less than minimum title length of 500 seconds and was therefore skipped
003025:0000 Title #5 has length of 1 seconds which is less than minimum title length of 500 seconds and was therefore skipped
003028:0000 Title #6 was added (16 cell(s), 1:46:32)
003028:0000 Title #7 was added (5 cell(s), 0:43:24)
003028:0000 Title #8 was added (2 cell(s), 0:15:33)
003027:0000 Title 3 in VTS 1 is equal to title 2 and was skipped
005011:0000 Operation successfully completed
005014:0000 Saving 1 titles into directory C:/Users/Zap Brannigan/Desktop
001003:0020 DEBUG: Code 0 at T.g'OyG"}$?mfYyd3n=jW:213130490
001003:0020 DEBUG: Code 0 at T.g'OyG"}$?mfYyd3n=jW:213129639
001003:0020 DEBUG: Code 0 at ^m.0&P3(7X$IY\$JhQ@:29394183
001003:0020 DEBUG: Code 0 at T.g'OyG"}$?mfYyd3n=jW:213130490
001003:0020 DEBUG: Code 0 at T.g'OyG"}$?mfYyd3n=jW:213129639
001003:0020 DEBUG: Code 0 at mbekjYvz,FE4*_>|AuF:29394160
001003:0020 DEBUG: Code 0 at mbekjYvz,FE4*_>|AuF:29395195
001002:0020 LIBMKV_TRACE: Exception: Error while reading input
005003:0000 Failed to save title 1 to file C:/Users/Zap Brannigan/Desktop/title01.mkv
005004:0080 0 titles saved, 1 failed
005037:0204 Copy complete. 0 titles saved, 1 failed.

setarip_old
Posts: 2136
Joined: Wed Dec 09, 2009 1:31 pm

Re: The Burning Plain - Fail To Save

#2 Post by setarip_old » Sun Oct 10, 2010 12:30 am

@Chest Rockwell

Hi!
I resurfaced the disk
If I understand you correctly, you did this because "I get an immediate FAILED TO SAVE with the DVD 'The Burning Plain.'"

If that's the case, without getting into HOW you "resurfaced" the original, commercial DVD, I'd suggest that your effort may have actually been the coup de grace - and rendered the disc useless...




Chest Rockwell
Posts: 36
Joined: Fri Jun 04, 2010 4:22 pm

Re: The Burning Plain - Fail To Save

#3 Post by Chest Rockwell » Sun Oct 10, 2010 12:46 am

Yes, I resurfaced the disk AFTER I received the FAILED messages. I continued to get the FAILED messages after resurfacing. Because the DVD data layer is about 50% back from the read surface, there is plenty of plastic to polish away without damaging the disk. I guess you are not aware that many products are sold to do this. They use a suspension of fine alumina powder in water to polish the disk surface. See, e,g.,

http://www.amazon.com/SkipDr-10183-Clas ... 138&sr=8-2

Having ripped about 1,000 DVD's, in my experience resurfacing corrects 80-90% of issues relating to scuffs and scratches.

mike admin
Posts: 4075
Joined: Wed Nov 26, 2008 2:26 am
Contact:

Re: The Burning Plain - Fail To Save

#4 Post by mike admin » Sun Oct 10, 2010 9:46 am

A known problem with 1.6.0 , will be corrected in a next version.

Chest Rockwell
Posts: 36
Joined: Fri Jun 04, 2010 4:22 pm

Re: The Burning Plain - Fail To Save

#5 Post by Chest Rockwell » Sun Oct 24, 2010 4:23 am

v1.6.2 fixed the problem. Thanks.

Post Reply