Failed read on brand new disc?

[mazzo]

I have been digitising my library as I said in another post. 99.999% of the time, this programme manages to burn everything.

But there have been a handful of dvds that have given me this failure.

(I'm on a Mac if it makes any difference). I can see no damage to the discs, they were brand new from a sealed set.

Thank you in advance for any suggestions on what to do with this.

Cheers!

[Woodstock]

Assuming by "burn" you actually mean "read", "new in wrapper" basically means "a disk that has sat for months or years absorbing whatever it was packaged with". Any disk released more than 6 months before it was opened probably needs CLEANED. May not look like it, but... the laser in the drive can tell.

[mazzo]

I have certainly cleaned them, that was the first thing I tried. There are certain files that will not be recognised to rip into digital version.

It looks like the original image didn't load when I posted the image, I will add an image description shortly because it will not let me add the image for some reason.

[Woodstock]

Posting pictures from a lot of sites don't work. The forum software supports links to certain (relatively safe) image types, but not to a web page that will have the image on it when it is displayed separately.

Hint: if the link doesn't end in ".gif", ".png", or ".jpg", it probably isn't an image by itself, and the image won't appear in the forum.

[mazzo]

Thank you. It is a screenshot and not from a website. It is a .png, I have tried uploading it multiple times, it gives a green bar and a green check-mark, but still does not show up. I will try one more time, but I will also describe it in case it does not work.

It is a black box with a bright red stop sign and an exclamation point inside the stop sign. It says 'Copy complete. 2 titles saved, 1 failed.' The click box says 'OK'

I have tried this disk about 6 time. I cleaned it thoroughly before I tried the second time, as all the other discs worked straight out of the box. But it just will not recognise this specific episode. I've ripped a lot of DVDs and blu-ray discs with MKV that have created MKV files with no problem, but there have been a small handful of discs that will not recognise one or two of the files. In this specific case, not that it probably matters, it's The Librarians season 3 disc 2, the episode is 'And the Curse of Cindy'.

It is always the same file that fails.

So wondering if there are any work-arounds or ways people have managed to copy files when they've been rejected using MKV.

Thank you!

[Woodstock]

OK, the log will show why MakeMKV couldn't save the file, especially if you've got full logging enabled. You'll see a line like this on start-up:

Code: Select all

Debug logging enabled, log will be saved as C:\Users\[username]/MakeMKV_log.txt

Copying/pasting the text inside code tabs here will tell us what MakeMKV was complaining about, but often it's simply a dirty spot (or worse, an scratch) that appears right in the middle of the data.

As I mentioned before, disks that have been in their packaging for a long time often need to be thoroughly, because the haze isn't something that pops out at you; I posted a picture several years ago of a disk that looked perfect... but for the line where I'd cleaned across it and manipulated the background lighting to make visible. Unfortunately, that picture was lost when the machine it was on was stolen last year.

[mazzo]

Thank you for this.

How do I find that code? I'm on a mac, I am happy to post it but will need to know where to look.

I promise, I did clean the discs very well, every time I tried to run them. There are several that just will NOT go.

I do appreciate your help thank you!

[Woodstock]

The location of the log file should be reported by MakeMKV during start-up, regardless of the operating system. That makes it easy to find later, but... it is also something you can highlight/copy/paste from the main window most of the time. It will tell you things like,

Code: Select all

004004:0000 The source file '/BDMV/STREAM/00006.m2ts' is corrupt or invalid at offset 18586232832-18586238976, attempting to work around

as it works its way through reading the disk. That particular error showed up 141 times as it worked through reading the disk in question, but it eventually pulled a fill copy for me. There should be something similar in your rip, as to why it couldn't handle copying the file.