Hello,
I opened MakeMKV as I usually would, and was notified of 1.6.8. I closed the program, downloaded the update, and installed it as I always do.
I've tried ripping 3 BDs.
- Blow
- The Crazies
- Law Abiding Citizen
All three rip the entire thing through, then at the very end a popup says "Failed to save title" or something along those lines. I never get an error code, crash, or anything. Is there something fundamentally different with 1.6.8?
Failed to save title - 1.6.8 (1.6.7 worked fine)
-
BonzTM
- Posts: 4
- Joined: Wed Nov 24, 2010 5:08 pm
-
crowfax
- Posts: 973
- Joined: Thu Feb 18, 2010 5:55 am
Re: Failed to save title - 1.6.8 (1.6.7 worked fine)
Turn on debug and post your log please.
Media Box: Ryzen 5700x / Arc A380, Windows 11, BU40N, BW-16D1HT, BP60NB10
Playback Devices: Nvidia Shield Pro, Apple TV 4k
Playback Devices: Nvidia Shield Pro, Apple TV 4k
-
gorbold
- Posts: 6
- Joined: Fri Apr 22, 2011 2:01 am
download 1.6.8
I tried to download 1.6.8 and when running the program, 1.6.7 still shows up
-
jkliop69
- Posts: 3
- Joined: Tue May 10, 2011 5:02 pm
Re: Failed to save title - 1.6.8 (1.6.7 worked fine)
FYI "failed to save title" is the error dialog that I'm getting with both the Planet of the Apes disks. I added the debug log here http://www.makemkv.com/forum2/viewtopic.php?f=8&t=3569
-
richwill
- Posts: 10
- Joined: Tue May 03, 2011 12:27 pm
Re: Failed to save title - 1.6.8 (1.6.7 worked fine)
I have a second BR which will not rip in 1.6.8 which ripped successfully in 1.6.5. Has anyone tried re-ripping BR disks that worked on a previous version?
-
o_mega05
- Posts: 1
- Joined: Fri May 27, 2011 6:16 am
Re: Failed to save title - 1.6.8 (1.6.7 worked fine)
@ BonzTM
Just curious if your issue was resolved? I'm having the same issue since the latest update and I'm getting the same "save failed" message for every 3 out of 4 BD rip attempts. I just thought it had something to do with newer BD releases.
Thanks in advance to anyone who has some incite on this issue.
Just curious if your issue was resolved? I'm having the same issue since the latest update and I'm getting the same "save failed" message for every 3 out of 4 BD rip attempts. I just thought it had something to do with newer BD releases.
Thanks in advance to anyone who has some incite on this issue.
-
captain
- Posts: 175
- Joined: Sat Feb 20, 2010 7:11 am
Re: Failed to save title - 1.6.8 (1.6.7 worked fine)
same problem here with TransSiberian
-
mike admin
- Posts: 4114
- Joined: Wed Nov 26, 2008 2:26 am
Re: Failed to save title - 1.6.8 (1.6.7 worked fine)
Please try 1.6.9
-
richwill
- Posts: 10
- Joined: Tue May 03, 2011 12:27 pm
Re: Failed to save title - 1.6.8 (1.6.7 worked fine)
I am having the same issue with 1.6.10. One thing to note is that the following is appearing in my dmesg during this process:
[74152.915919] sr 18:0:0:0: [sr2] Result: hostbyte=DID_OK driverbyte=DRIVER_OK
[74152.915922] end_request: I/O error, dev sr2, sector 28160
[74273.512891] sr 18:0:0:0: timing out command, waited 120s
[74273.512902] sr 18:0:0:0: [sr2] Unhandled error code
[74273.512903] sr 18:0:0:0: [sr2] Result: hostbyte=DID_OK driverbyte=DRIVER_OK
[74273.512907] end_request: I/O error, dev sr2, sector 29696
[74394.807483] sr 18:0:0:0: timing out command, waited 120s
[74394.807492] sr 18:0:0:0: [sr2] Unhandled error code
[74394.807494] sr 18:0:0:0: [sr2] Result: hostbyte=DID_OK driverbyte=DRIVER_OK
[74394.807498] end_request: I/O error, dev sr2, sector 31232
It's also worth noting that I know that 1.6.5 did not exhibit this issue, 1.6.8 has the same problem, and I'm using a BR drive over an iSCSI connection (which never affected this process in the past).
HTH
[74152.915919] sr 18:0:0:0: [sr2] Result: hostbyte=DID_OK driverbyte=DRIVER_OK
[74152.915922] end_request: I/O error, dev sr2, sector 28160
[74273.512891] sr 18:0:0:0: timing out command, waited 120s
[74273.512902] sr 18:0:0:0: [sr2] Unhandled error code
[74273.512903] sr 18:0:0:0: [sr2] Result: hostbyte=DID_OK driverbyte=DRIVER_OK
[74273.512907] end_request: I/O error, dev sr2, sector 29696
[74394.807483] sr 18:0:0:0: timing out command, waited 120s
[74394.807492] sr 18:0:0:0: [sr2] Unhandled error code
[74394.807494] sr 18:0:0:0: [sr2] Result: hostbyte=DID_OK driverbyte=DRIVER_OK
[74394.807498] end_request: I/O error, dev sr2, sector 31232
It's also worth noting that I know that 1.6.5 did not exhibit this issue, 1.6.8 has the same problem, and I'm using a BR drive over an iSCSI connection (which never affected this process in the past).
HTH
-
cfriedberg
- Posts: 1
- Joined: Thu Jun 09, 2011 11:07 pm
Re: Failed to save title - 1.6.8 (1.6.7 worked fine)
same problem, doesn't matter the version. Trying to rip BD of Harry Potter 2. Debug log attached. Any help greatly appreciated.
-
mike admin
- Posts: 4114
- Joined: Wed Nov 26, 2008 2:26 am
Re: Failed to save title - 1.6.8 (1.6.7 worked fine)
Code: Select all
002003:0000 Error 'Scsi error - NOT READY:CANNOT READ MEDIUM - INCOMPATIBLE FORMAT' occurred while reading '/BDMV/STREAM/00037.m2ts' at offset '21229989888'