www.makemkv.com

Debug log started at Tue Jan 25 12:44:33 2011 , written by MakeMKV v1.6.3 darwin(x86-release)
Using 524544KB for read cache.
001003:0020 DEBUG: Code 6094848 at 'u<[]5WgK1,d|&;Fk>+An_l:213130007
001003:0020 DEBUG: Code 6094848 at 'u<[]5WgK1,d|&;Fk>+An_l:213130007
001003:0020 DEBUG: Code 6094848 at 'u<[]5WgK1,d|&;Fk>+An_l:213130007
001005:0000 MakeMKV v1.6.3 darwin(x86-release) started
001004:0000 Debug logging enabled, log will be saved as /Users/captain/MakeMKV_log.txt
003007:0000 Using direct disc access mode
DISCID=87FBF426C214A6F759FE4E29D4C2F9BF1EB594A2
003307:0000 File 00000.mpls was added as title #0
003307:0000 File 00014.mpls was added as title #1
003025:0000 Title #00002.m2ts has length of 0 seconds which is less than minimum title length of 120 seconds and was therefore skipped
003307:0000 File 00003.m2ts was added as title #2
003307:0000 File 00004.m2ts was added as title #3
003307:0000 File 00007.m2ts was added as title #4
003025:0000 Title #00008.m2ts has length of 117 seconds which is less than minimum title length of 120 seconds and was therefore skipped
003307:0000 File 00009.m2ts was added as title #5
003025:0000 Title #00010.m2ts has length of 12 seconds which is less than minimum title length of 120 seconds and was therefore skipped
003025:0000 Title #00011.m2ts has length of 11 seconds which is less than minimum title length of 120 seconds and was therefore skipped
003025:0000 Title #00012.m2ts has length of 23 seconds which is less than minimum title length of 120 seconds and was therefore skipped
003025:0000 Title #00014.m2ts has length of 10 seconds which is less than minimum title length of 120 seconds and was therefore skipped
005011:0000 Operation successfully completed
005014:0000 Saving 1 titles into directory /Volumes/Blu-Ray_rips/unforgiven
002008:0020 Program reads data faster than it can write to disk, consider upgrading your hard drive if you see many of these messages.
002008:0020 Program reads data faster than it can write to disk, consider upgrading your hard drive if you see many of these messages.
002008:0020 Program reads data faster than it can write to disk, consider upgrading your hard drive if you see many of these messages.
002008:0020 Program reads data faster than it can write to disk, consider upgrading your hard drive if you see many of these messages.
001003:0020 DEBUG: Code 131072 at `S=Sew$"nHxGB8ko`(C$n{:121262256
001003:0020 DEBUG: Code 4294967295 at `S=Sew$"nHxGB8ko`(C$n{:121262279
001003:0020 DEBUG: Code 28 at `S=Sew$"nHxGB8ko`(C$n{:121262348
001003:0020 DEBUG: Code 131072 at `S=Sew$"nHxGB8ko`(C$n{:121262256
001003:0020 DEBUG: Code 4294967295 at `S=Sew$"nHxGB8ko`(C$n{:121262279
001003:0020 DEBUG: Code 28 at `S=Sew$"nHxGB8ko`(C$n{:121262348
001003:0020 DEBUG: Code 0 at ^J[&'Alz-3\<\;#Mm:29395287
001002:0020 LIBMKV_TRACE: Exception: EOF in writeFully
005003:0000 Failed to save title 0 to file /Volumes/Blu-Ray_rips/unforgiven/title00.mkv
005004:0080 0 titles saved, 1 failed
005037:0204 Copy complete. 0 titles saved, 1 failed.



And, yes, I powercycled the blu-ray drive and restarted MakeMKV. Still no joy.

I am trying the Option "1" for the Prefs IO "read around Mac KEY V2 workaround bug" thing. I cannot access the Prefs during a rip to write the correct thing here. Hope you know what I mean. Estimated 4:30, and rising, to see if this works....

Still fails:

MakeMKV v1.6.3 darwin(x86-release) started
Debug logging enabled, log will be saved as /Users/captain/MakeMKV_log.txt
Using direct disc access mode
File 00000.mpls was added as title #0
File 00014.mpls was added as title #1
Title #00002.m2ts has length of 0 seconds which is less than minimum title length of 120 seconds and was therefore skipped
File 00003.m2ts was added as title #2
File 00004.m2ts was added as title #3
File 00007.m2ts was added as title #4
Title #00008.m2ts has length of 117 seconds which is less than minimum title length of 120 seconds and was therefore skipped
File 00009.m2ts was added as title #5
Title #00010.m2ts has length of 12 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00011.m2ts has length of 11 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00012.m2ts has length of 23 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00014.m2ts has length of 10 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Operation successfully completed
Saving 1 titles into directory /Volumes/Blu-Ray_rips/unforgiven
DEBUG: Code 0 at ^J[&'Alz-3\<\;#Mm:29395287
LIBMKV_TRACE: Exception: EOF in writeFully
Failed to save title 0 to file /Volumes/Blu-Ray_rips/unforgiven/title00.mkv
0 titles saved, 1 failed

Now trying Option 2 for mac bug key v2 workaround thing.

I just ripped that movie the other day using MakeMKV with no problems at all. I agree with the post above mine that your drive is probably the cause of the problem. I have occasionally had a problem like this with random DVDs and Blu-rays, but a quit of MakeMKV and/or an eject and reload of the disc generally fixes the issue and the next attempt succeeds with no errors.

I'm using this drive:

OWC Mercury Pro 12x Blu-ray Pioneer BDR-206 External

Option 0, 1, & 2 all failed. Now trying disabling direct access...

Ah...Interesting conjecture above, that my blu-ray drive is dying. I hope you are wrong, as I'm guessing it just went out of warranty with fewer than 50 discs played/ripped!!

Oh, for crying out loud! MY HD IS OUT OF SPACE!!! Why the Hell doesn't MakeMKV just say THAT, instead of a bunch of cryptic error messages??? AAARGH!!!

Beta tester recommendation to Mike: Have MakeMKV return "Not Enough Disk Space for Rip" error, rather than cryptic errors listed above, when disk space is, or may be, the problem. Better yet, do a PRE-RIP check and pop up a warning with "abort / go ahead" options. At least then the user will know that disk space is a likely cause of a failed rip.

captain wrote:Beta tester recommendation to Mike: Have MakeMKV return "Not Enough Disk Space for Rip" error, rather than cryptic errors listed above, when disk space is, or may be, the problem. Better yet, do a PRE-RIP check and pop up a warning with "abort / go ahead" options. At least then the user will know that disk space is a likely cause of a failed rip.

This is exactly how it supposed to be - MakeMKV usually gives a warning if there is not enough space or target file system doesn't support large files. You've found a bug in that code. Where was a destination directory? Was it local drive, or network share? Can you think of anything unusual?