Cosmos - D3E5 - Fail To Save

[Chest Rockwell]

Brand new commercial disc. Disc surface appears free of scratches/smudges/imperfections. Confirmed on two different drives. Log attached.

[Chest Rockwell]

I uploaded the log but it did not attach. Trying again.

[mike admin]

Brand new commercial disc. Disc surface appears free of scratches/smudges/imperfections. Confirmed on two different drives. Log attached.

Yet disc has no structure protection but files are corrupted. It's a bad disc or drive.

Code: Select all

004004:0000 The source file '/VIDEO_TS/VTS_01_1.VOB' is corrupt or invalid at offset 2411388928, attempting to work around

[StubbsWall]

For whatever it's worth, I'm having the same issue with the same disc and episode (Cosmos D3E5) on my MacBook Pro:

~~~~~~~~~~~~~
MakeMKV v1.6.5 darwin(x86-release) started
Optical drive "DVD+R-DL HL-DT-ST DVDRW GS23N SB11" opened in OS access mode.
It's highly recommended to install DASPI kernel extension to improve performance.
Using direct disc access mode
Title #0 was added (15 cell(s), 1:00:55)
Title #4 was added (15 cell(s), 1:01:04)
Operation successfully completed
Saving 1 titles into directory /Users/Stubbs/Movies/Cosmos
The source file '/VIDEO_TS/VTS_01_1.VOB' is corrupt or invalid at offset 2411388928, attempting to work around
The source file '/VIDEO_TS/VTS_01_1.VOB' is corrupt or invalid at offset 2411390976, attempting to work around
The source file '/VIDEO_TS/VTS_01_1.VOB' is corrupt or invalid at offset 2411393024, attempting to work around
The source file '/VIDEO_TS/VTS_01_1.VOB' is corrupt or invalid at offset 2411395072, attempting to work around
The source file '/VIDEO_TS/VTS_01_1.VOB' is corrupt or invalid at offset 2411401216, attempting to work around
The source file '/VIDEO_TS/VTS_01_1.VOB' is corrupt or invalid at offset 2411403264, attempting to work around
The source file '/VIDEO_TS/VTS_01_1.VOB' is corrupt or invalid at offset 2411425792, attempting to work around
The source file '/VIDEO_TS/VTS_01_1.VOB' is corrupt or invalid at offset 2411427840, attempting to work around
Failed to save title 1 to file /Users/Stubbs/Movies/Cosmos/title01.mkv
~~~~~~~~~~~~~~

All the other discs and episodes worked fine, including Episode 4 on the same disc (D3)

I'll keep an eye on this thread for any ideas. I guess there is some comfort in knowing I'm not alone on this one.

Thanks and Regards,

--Stubbs

[Chest Rockwell]

Yet disc has no structure protection but files are corrupted. It's a bad disc or drive.

Can you please elaborate on what you mean? It is not a bad drive because I get the same failure on two different drives and another poster just posted he has the same problem.

Also, the disc plays fine in a regular DVD player. In addition I can rip an ISO with IMGburn with zero read errors. When I use MakeMKV on the ripped ISO I still get the same problem.

[setarip_old]

I purchased this 7 disc 13 episode set when it was first released in 2002 - and, after two exchanges, was frustrated to discover that although the "Mars" episode played properly on my standalone player, it locked up my computer system part way into the episode.

Eventually, I determined that the disc contained a manufacturing "glitch" (disc mastering error) that only affected it being read by the computer system (Standalone players use UDF1.02 format, while computer systems use ISO9660 format).

If I remember correctly, I had to edit out 1 second of video (Fortunately, the editing was virtually unnoticeable).

Although I would typically not suggest an alternative to MakeMKV, in this unusual instance, I'm sure "mike admin" will forgive me if I suggest you try ripping this particular, unusual problematic disc with "DVDFab" (set to skip unreadable sectors).

Let us know how it goes ;>}

Great series by the way - Very satisfying to see each generation of the grandkids in awe of science FACT for a change, rather than science fiction!

[mike admin]

I'm sure "mike admin" will forgive me

Never.

You can always change what filesystem is parsed for DVD discs. On Mac start the terminal, type

Code: Select all

nano ~/.MakeMKV/settings.conf

and add the following line to configuration file

Code: Select all

fs_ForceIsoForUDF102 = "false"

Change to "true" for default behaivor.

[_JBP_]

I'm sure "mike admin" will forgive me

Never.

You can always change what filesystem is parsed for DVD discs. On Mac start the terminal, type

Code: Select all

nano ~/.MakeMKV/settings.conf

and add the following line to configuration file

Code: Select all

fs_ForceIsoForUDF102 = "false"

Change to "true" for default behaivor.

Is there a way to use this workaround on Windows 7 64-Bit? Thanks.

[mike admin]

I'm sure "mike admin" will forgive me

Never.

You can always change what filesystem is parsed for DVD discs. On Mac start the terminal, type

Code: Select all

nano ~/.MakeMKV/settings.conf

and add the following line to configuration file

Code: Select all

fs_ForceIsoForUDF102 = "false"

Change to "true" for default behaivor.

Is there a way to use this workaround on Windows 7 64-Bit? Thanks.

Yes, a REG_DWORD registry settings with the same name ( fs_ForceIsoForUDF102 ) under HKCU\Software\MakeMKV .

[_JBP_]

I'm assuming since there wasn't a registry key there with that name I needed to create it so I did.. Do I leave the value at 0 for it? Since this is a 64-Bit system do I need to make a REG_QWORD registry key also? Will MakeMKV show anything different in the log for the different reading method? I'm only curious because it failed again... I may have to try editing out that portion of the VOB file if I can locate a editor for it as stated a few posts ago..

[mike admin]

I'm assuming since there wasn't a registry key there with that name I needed to create it so I did.. Do I leave the value at 0 for it? Since this is a 64-Bit system do I need to make a REG_QWORD registry key also? Will MakeMKV show anything different in the log for the different reading method? I'm only curious because it failed again... I may have to try editing out that portion of the VOB file if I can locate a editor for it as stated a few posts ago..

A REG_DWORD with value 0. There is no indication in the log file unfortunately.