So I'm trying to rip some burned DVDs (these aren't factory DVDs, like a movie.) They are DVDs of educational clips that someone has asked me to convert to a digital format. I tried handbrake but it "completed" the ripping 2 minutes through with a 10 minute video clip as a result (the actual clip is 1 hour 45 minutes.)
So I tried MakeMKV but it gave me the errors you will see in the log below. The disc itself is not scratched at all, and it plays fine in a DVD player or VLC, so I'm wondering if there is any way to get this DVD ripped and if not, what did said person who burned the disc do wrong?
MakeMKV v1.14.1 win(x64-release) started
Debug logging enabled, log will be saved as C:\Users\admin/MakeMKV_log.txt
Using direct disc access mode
Title #1 was added (49 cell(s), 0:30:40)
DEBUG: Code 233 at UwdsKQ0MiodAP65xUs0Vl14L:0
Operation successfully completed
Saving 1 titles into directory C:/Users/admin/Desktop
The source file '/VIDEO_TS/VTS_01_1.VOB' is corrupt or invalid at offset 0-32768, attempting to work around
The source file '/VIDEO_TS/VTS_01_1.VOB' is corrupt or invalid at offset 38912, attempting to work around
DEBUG: Code 21248 at ;<g9KMFc,c8YI6kEV7z_:29393930
The source file '/VIDEO_TS/VTS_01_1.VOB' is corrupt or invalid at offset 43008-133120, attempting to work around
The source file '/VIDEO_TS/VTS_01_1.VOB' is corrupt or invalid at offset 137216, attempting to work around
The source file '/VIDEO_TS/VTS_01_1.VOB' is corrupt or invalid at offset 141312, attempting to work around
The source file '/VIDEO_TS/VTS_01_1.VOB' is corrupt or invalid at offset 145408-161792, attempting to work around
DEBUG: Code 52224 at ;<g9KMFc,c8YI6kEV7z_:29393930
The source file '/VIDEO_TS/VTS_01_1.VOB' is corrupt or invalid at offset 165888-167936, attempting to work around
The source file '/VIDEO_TS/VTS_01_1.VOB' is corrupt or invalid at offset 174080-264192, attempting to work around
The source file '/VIDEO_TS/VTS_01_1.VOB' is corrupt or invalid at offset 268288-272384, attempting to work around
The source file '/VIDEO_TS/VTS_01_1.VOB' is corrupt or invalid at offset 276480-393216, attempting to work around
The source file '/VIDEO_TS/VTS_01_1.VOB' is corrupt or invalid at offset 407552-522240, attempting to work around
The source file '/VIDEO_TS/VTS_01_1.VOB' is corrupt or invalid at offset 530432, attempting to work around
The source file '/VIDEO_TS/VTS_01_1.VOB' is corrupt or invalid at offset 534528, attempting to work around
DEBUG: Code 181 at i.FC2K+5&B0M+V^^T}*0b-:213129915
The source file '/VIDEO_TS/VTS_01_1.VOB' is corrupt or invalid at offset 538624-624640, attempting to work around
The source file '/VIDEO_TS/VTS_01_1.VOB' is corrupt or invalid at offset 628736, attempting to work around
The source file '/VIDEO_TS/VTS_01_1.VOB' is corrupt or invalid at offset 636928-753664, attempting to work around
DEBUG: Code 195 at i.FC2K+5&B0M+V^^T}*0b-:213129915
The source file '/VIDEO_TS/VTS_01_1.VOB' is corrupt or invalid at offset 768000-882688, attempting to work around
The source file '/VIDEO_TS/VTS_01_1.VOB' is corrupt or invalid at offset 897024-983040, attempting to work around
DEBUG: Code 9472 at ;<g9KMFc,c8YI6kEV7z_:29393930
The source file '/VIDEO_TS/VTS_01_1.VOB' is corrupt or invalid at offset 987136-993280, attempting to work around
The source file '/VIDEO_TS/VTS_01_1.VOB' is corrupt or invalid at offset 997376-1013760, attempting to work around
The source file '/VIDEO_TS/VTS_01_1.VOB' is corrupt or invalid at offset 1017856-1026048, attempting to work around
The source file '/VIDEO_TS/VTS_01_1.VOB' is corrupt or invalid at offset 1030144-1050624, attempting to work around
DEBUG: Code 58 at Jpuq@`opJjnjI:121262555
DEBUG: Code 6 at Jpuq@`opJjnjI:121262555
DEBUG: Code 30 at Jpuq@`opJjnjI:121262555
DEBUG: Code 36 at Jpuq@`opJjnjI:121262555
DEBUG: Code 42 at Jpuq@`opJjnjI:121262555
DEBUG: Code 4 at Jpuq@`opJjnjI:121262555
DEBUG: Code 44 at Jpuq@`opJjnjI:121262555
DEBUG: Code 28 at Jpuq@`opJjnjI:121262555
DEBUG: Code 18 at Jpuq@`opJjnjI:121262555
DEBUG: Code 34 at Jpuq@`opJjnjI:121262555
DEBUG: Code 18 at Jpuq@`opJjnjI:121262555
DEBUG: Code 6 at Jpuq@`opJjnjI:121262555
DEBUG: Code 18 at Jpuq@`opJjnjI:121262555
DEBUG: Code 58 at Jpuq@`opJjnjI:121262555
DEBUG: Code 28 at Jpuq@`opJjnjI:121262555
DEBUG: Code 42 at Jpuq@`opJjnjI:121262555
DEBUG: Code 36 at Jpuq@`opJjnjI:121262555
DEBUG: Code 12 at Jpuq@`opJjnjI:121262555
DEBUG: Code 28 at Jpuq@`opJjnjI:121262555
DEBUG: Code 28 at Jpuq@`opJjnjI:121262555
DEBUG: Code 36 at Jpuq@`opJjnjI:121262555
DEBUG: Code 1 at 79xyA!J^`q3Gu:213132146
DEBUG: Code 1 at Y.aF2=qB"!l"+[S_ x:29404257
DEBUG: Code 0 at |~2b5H{#xW@uUHh3:213141691
DEBUG: Code 0 at |~2b5H{#xW@uUHh3:29398116
Error 'Internal error - Operation was cancelled (123)' occurred while reading '/VIDEO_TS/VTS_01_1.VOB' at offset '1116160'
DEBUG: Code 0 at L[k>dhTI5_@{<5+sOE>p:121263176
DEBUG: Code 0 at >4p0x80x){u|W-(41&Q:213129915
DEBUG: Code 0 at L[k>dhTI5_@{<5+sOE>p:29394551
DEBUG: Code 545 at L[k>dhTI5_@{<5+sOE>p:29393286
DEBUG: Code 0 at <-SIJ8^D!!'51`)GDZF:29393792
DEBUG: Code 0 at W*(LwO(hz3aLoK(1eiSa :213136332
DEBUG: Code 0 at W*(LwO(hz3aLoK(1eiSa :213136240
DEBUG: Code 0 at p:P[,:]b2AVs'dl]gLz(:29394114
DEBUG: Code 0 at W*(LwO(hz3aLoK(1eiSa :213136332
DEBUG: Code 0 at p:P[,:]b2AVs'dl]gLz(:121262072
DEBUG: Code 0 at p:P[,:]b2AVs'dl]gLz(:121265982
DEBUG: Code 0 at W*(LwO(hz3aLoK(1eiSa :213136332
DEBUG: Code 0 at W*(LwO(hz3aLoK(1eiSa :213136240
DEBUG: Code 48 at pWRM&Uv+fVau.-s|f.:121271433
The source file '/VIDEO_TS/VTS_01_1.VOB' is corrupt or invalid at offset 1054720-1112064, attempting to work around
DEBUG: Code 48 at pWRM&Uv+fVau.-s|f.:29398576
DEBUG: Code 0 at pWRM&Uv+fVau.-s|f.:29400853
DEBUG: Code 0 at pWRM&Uv+fVau.-s|f.:29401934
Failed to save title 0 to file C:/Users/admin/Desktop/title_t00.mkv
0 titles saved, 1 failed
Source file at .... is corrupt or invalid, attempting to work around
-
- Posts: 9
- Joined: Sun Nov 25, 2018 7:12 pm
-
- Posts: 9
- Joined: Sun Nov 25, 2018 7:12 pm
Re: Source file at .... is corrupt or invalid, attempting to work around
Same issue happened with another disc.
The source file '/VIDEO_TS/VTS_01_1.VOB' is corrupt or invalid at offset 461740032-461762560, attempting to work around
that is one of the errors it is giving me. I'm trying to figure out why some of these DVDs won't rip in Handbrake or MakeMKV. The discs themselves don't look damaged or scratched that badly, so is it possible these DVDs are BURNED wrong, and that is why they aren't ripping?
If someone could chime in and give me an opinion it would be appreciated.
The source file '/VIDEO_TS/VTS_01_1.VOB' is corrupt or invalid at offset 461740032-461762560, attempting to work around
that is one of the errors it is giving me. I'm trying to figure out why some of these DVDs won't rip in Handbrake or MakeMKV. The discs themselves don't look damaged or scratched that badly, so is it possible these DVDs are BURNED wrong, and that is why they aren't ripping?
If someone could chime in and give me an opinion it would be appreciated.
Re: Source file at .... is corrupt or invalid, attempting to work around
The MakeMKV error is usually caused by a dirty disk.
Both handbrake and MakeMKV try to do a "perfect" rip, no errors. DVD/BD players accept "mostly good", so occasional errors are simply skipped over.
A disk may look perfect to our eyes, but a laser has a much finer view, and things like a hazy film on the disk will scatter just enough light to cause a read problem. I've seen chemical haze on disks that only becomes apparent after you clean PART of the disk, then it stands out like a sore thumb. I've tried to take pictures of it to post in this topic that covers read errors, but the camera wouldn't focus on the surface of the disk... It focused on the objects reflected in the disk, so the haze was invisible.
The point is, the haze affected the read, but wasn't readily apparent.
Both handbrake and MakeMKV try to do a "perfect" rip, no errors. DVD/BD players accept "mostly good", so occasional errors are simply skipped over.
A disk may look perfect to our eyes, but a laser has a much finer view, and things like a hazy film on the disk will scatter just enough light to cause a read problem. I've seen chemical haze on disks that only becomes apparent after you clean PART of the disk, then it stands out like a sore thumb. I've tried to take pictures of it to post in this topic that covers read errors, but the camera wouldn't focus on the surface of the disk... It focused on the objects reflected in the disk, so the haze was invisible.
The point is, the haze affected the read, but wasn't readily apparent.
MakeMKV Frequently Asked Questions
FAQ about BETA and PERMANENT keys.
How to aid in finding the answer to your problem: Activating Debug Logging
FAQ about BETA and PERMANENT keys.
How to aid in finding the answer to your problem: Activating Debug Logging
-
- Posts: 9
- Joined: Sun Nov 25, 2018 7:12 pm
Re: Source file at .... is corrupt or invalid, attempting to work around
Thanks Woodstock, I will try cleaning the discs again...
You don't think there could be a problem with the way the disc was burned originally, do you? These aren't "factory" DVDs, they are user created.
Could the way the disc was burned affect MakeMKV's ability to rip it? Or do the errors have to be "cleaning" related.
You don't think there could be a problem with the way the disc was burned originally, do you? These aren't "factory" DVDs, they are user created.
Could the way the disc was burned affect MakeMKV's ability to rip it? Or do the errors have to be "cleaning" related.
Re: Source file at .... is corrupt or invalid, attempting to work around
I always ass-u-me we're working with commercial disks around here, unless stated otherwise. So I skipped over the part about them being burned...
Home-brew disks can have a lot of issues, such as "disk wasn't closed", leaving directories pointing at VOBs that haven't been written yet. The burner software should be validating that the actual bits written are readable, but the one disk recorder I used for a while couldn't keep up with video if you asked it to verify the write.
Home-brew disks can have a lot of issues, such as "disk wasn't closed", leaving directories pointing at VOBs that haven't been written yet. The burner software should be validating that the actual bits written are readable, but the one disk recorder I used for a while couldn't keep up with video if you asked it to verify the write.
MakeMKV Frequently Asked Questions
FAQ about BETA and PERMANENT keys.
How to aid in finding the answer to your problem: Activating Debug Logging
FAQ about BETA and PERMANENT keys.
How to aid in finding the answer to your problem: Activating Debug Logging
-
- Posts: 9
- Joined: Sun Nov 25, 2018 7:12 pm
Re: Source file at .... is corrupt or invalid, attempting to work around
Thanks, so I suppose my best bet is to clean the discs off as best I can, try ripping, and if errors occur then they are either burned wrong or physically damaged.
Re: Source file at .... is corrupt or invalid, attempting to work around
Home-made disks USUALLY aren't encrypted, so you might try using Explorer and copying all the contents to a directory on your local drive. If that doesn't hit any read errors, you can try opening the local copy. A number of tools can open non-encrypted DVD file structures on disk, but they're not so good at copying from the optical media.
MakeMKV Frequently Asked Questions
FAQ about BETA and PERMANENT keys.
How to aid in finding the answer to your problem: Activating Debug Logging
FAQ about BETA and PERMANENT keys.
How to aid in finding the answer to your problem: Activating Debug Logging