View Full Version : VIDEO_TS.VOB missing - burning failed
Digga
30th May 2006, 03:43
hmm, I don't really know if this is directly related to DVD-Rebuilder. the more I think about it the more I guess it's something related to the ripping process but what do I know. if there is a better place for this thread please feel free to move it mods.
so here it goes:
I ripped the movie 'The Interpreter' (starring Nicole Kidman, R2) with AnyDVD's included ripper to HD, all option checked on the setting tab (removing of protections). the process worked flawlessly.
then I did the movie with DVD-RB, main movie and menus only, 10% steal space from extras, CCE mode (see log).
when trying to burn, Nero complains about that VIDEO_TS.VOB is missing and that it can't recompile the DVD. GEAR burn software does burn the DVD but does so incorrectly.
and really, the file is missing in the DVD output directory. and curiously it's also missing in the source folder. I didn't preprocess nor did I touch the sources in any way.
so... is there something wrong with the sources or did something screw up while encoding/rebuilding?
I tend to believe the former but wouldn't have a clue what might have caused this.
edit: I should mention the that final output is perfectly viewable with PowerDVD if it helps.
setarip_old
30th May 2006, 03:48
Hi!
Does your original DVD contain a "VIDEO_TS.VOB"?
Digga
30th May 2006, 03:53
Does your original DVD contain a "VIDEO_TS.VOB"? I can't check ATM as I borrowed the movie to my sis but I will get it back from her and check.
thanks for your interest.
blutach
30th May 2006, 08:39
If it's not in the source, it isn't going to be in the output!
Despite all of silly Ner0's protestations, there is absolutely no requirement for VIDEO_TS.VOB to be present (for example, look at DVD Shrink or Ner0 Rec0de in re-author mode).
Take your output from DVD Rebuilder (http://dvd-rb.dvd2go.org/) (which I'm sure will be perfect), and run it through PgcEdit (http://www.videohelp.com/~r0lZ/pgcedit/index.html) to make an ISO and burn it with ImgBurn (www.imgburn.com).
See here (http://www.digital-digest.com/~blutach/pgcedit_guide/burning_with_pgcedit/burning_with_pgcedit_v2.htm) for a guide.
Regards
Digga
30th May 2006, 14:27
If it's not in the source, it isn't going to be in the output!well, yeah, I understood that logic ;)
thanks for pointing me to another method though. PgCEdit warns about two discrepancies in some VGM/VTSI_MAT tables and asks if I want to fix it. a quick search reveals that this problem probably can be safely ignored, am I right?
jdobbs
30th May 2006, 22:30
I'd recommend you use DVD Rebuilder to create the ISO image and ImgBurn to write to disc (either automatically through DVD-RB or manually). That way you can be sure it is working correctly.
blutach
31st May 2006, 08:23
@Digga
If you use PgcEdit (http://www.videohelp.com/~r0lZ/pgcedit/index.html), you can either ignore that warning or just click yes and have your stream tables fixed (these are streams left over that you did not keep when you rebuilt your DVD).
@jdobbs - FYI: PgcEdit (http://www.videohelp.com/~r0lZ/pgcedit/index.html) uses mkisofs to build its ISOs, so they are perfectly compliant.
Regards
Digga
31st May 2006, 14:17
I'd recommend you use DVD Rebuilder to create the ISO image and ImgBurn to write to disc (either automatically through DVD-RB or manually). That way you can be sure it is working correctly.it would be nice to implent an option to delete intermediate files then (i.e. processed files in the D2VAVS directory) for users like me with tight space. I do all my backups only with 18 to 20 GB available so creating an image via Rebuilder on the fly is not option for me as I have to free up some space beforehand.
jdobbs
1st June 2006, 04:52
If you keep using the same working/output directory for each encode the intermediate files are cleared for each. But, since the ISO has a different name for each -- it will still be there. That's what I normally do if I have a lot of discs to do and I'm getting short of space.
The problem with clearing the D2VAVS directory is that some people feel just the opposite... they think it should never go away unless they specifically delete it.
setarip_old
1st June 2006, 06:37
@Digga
Have you as yet determined whether your original DVD contain a "VIDEO_TS.VOB"?
blutach
1st June 2006, 08:09
Speaking personally, after having "invested" hours in an encode, I'd wanna check all is 100% before I threw away my D2VAVS folder.
Regards
Digga
1st June 2006, 09:23
Have you as yet determined whether your original DVD contain a "VIDEO_TS.VOB"?unfortunately not, and I won't have the chance to do so until friday. I will report back then if all goes well.
If you keep using the same working/output directory for each encode the intermediate files are cleared for each. But, since the ISO has a different name for each -- it will still be there. That's what I normally do if I have a lot of discs to do and I'm getting short of space.uhm... I'm not sure we understood each other correctly so I'm going to rephrase my point :)
I do keep the same directory for all my encodes but I'm only able to do one movie at a time since I only have about 18GB of storage left for that purpose (and that includes the ripped movie). so I have to manually delete the ripped movie plus the processed files as well as the rebuilt output (after burning) to make room for another movie.
hence I cannot create an ISO to burn, as that would require another 4GB that I don't have available.
now, if there would be an option to delete intermediate files so in my case I would be able to create an image automatically that would be nice.
Speaking personally, after having "invested" hours in an encode, I'd wanna check all is 100% before I threw away my D2VAVS folder.he problem with clearing the D2VAVS directory is that some people feel just the opposite... they think it should never go away unless they specifically delete it.I perfectly agree that my proposal shouldn't be the default as many users might want to keep all involved steps for security reasons until they double checked on a hardware player that the output is fine.
but an option in the GUI, maybe along with a warning or even better some option in the .ini would be very useful, at least for me.
edit: spelling
jdobbs
1st June 2006, 13:13
I'll add it to my list of things to do. I'll make it a "hidden" option.
Digga
1st June 2006, 13:40
thank you.
Digga
12th June 2006, 15:53
update:
VIDEO_TS.VOB is not present in the original movie so naturally it won't won't be there in the ripped files.
it still seems odd to me that GEAR7 and Nero6 choke on this scenario.
building an ISO via PgcEdit 7.x plus burning with ImgBurn did work well but my hardware player (Targa DP-5200x) didn't accept the output. it's sadly dying anyway so I didn't do any further tests and will wait untill I replace it.
rpboy
19th June 2006, 01:50
update:
VIDEO_TS.VOB is not present in the original movie so naturally it won't won't be there in the ripped files.
it still seems odd to me that GEAR7 and Nero6 choke on this scenario.
I am using the latest version of Nero 6 and I have gotten the warning about the missing VIDEO_TS.VOB file every so often and I choose to burn anyway and the discs have been fine.
Even though Nero is warning you, you should be able to continue the burn.
blutach
19th June 2006, 03:30
@rpboy - the reason for this is that it is somehow referenced in the tables of VIDEO_TS.IFO This is incorrect authoring but does no harm. If you wanna get rid of it from the tables, open the project in PgcEdit (http://www.videohelp.com/~r0lZ/pgcedit/index.html), left click on any VMGM PGC, Ctrl-Delete and answer yes when it asks you if you wanna remove all references to it. Save (Ctrl-S) and burn.
Regards
setarip_old
19th June 2006, 04:19
I am using the latest version of Nero 6 and I have gotten the warning about the missing VIDEO_TS.VOB file every so often and I choose to burn anyway and the discs have been fine.the reason for this is that it is somehow referenced in the tables of VIDEO_TS.IFO This is incorrect authoringSo, am I correct in understanding that, in an instance such as this, NERO is correctly pointing out an irregularity in the authoring - and yet is also "smart" enough to allow you to continue with the burn, because it's not a fatal error?
jdobbs
19th June 2006, 06:51
No. That would be incorrect. DVD-RB correctly creates images.
setarip_old
19th June 2006, 18:50
@jdobbs
Hi!
So are you saying that this quoted explanation (not by me) is, likewise, incorrect?the reason for this is that it is somehow referenced in the tables of VIDEO_TS.IFO This is incorrect authoring
jdobbs
19th June 2006, 20:02
@jdobbs
Hi!
So are you saying that this quoted explanation (not by me) is, likewise, incorrect? I'm not saying that at all. I'm saying that if the original disc is authored without a VIDEO_TS.VOB, and NERO is complaining -- that means you would have to assume that NERO is more compliant than a commercially authored DVD. That ain't likely.
I recommend ImgBurn -- not because I have a vested interest (I don't) but because I appreciate quality software that does what it is supposed to do correctly.
setarip_old
19th June 2006, 21:07
I'm probably belaboring the point but, the statement by "blutach" was,the reason for this is that it is somehow referenced in the tables of VIDEO_TS.IFO This is incorrect authoringSuch a condition would seem to have nothing to do with NERO.
Rather, per "blutach", not I, it would be a pre-existing condition in the authoring...
Digga
19th June 2006, 21:59
to add to the confusion, I just rented the same movie (R1) at a store here nearby cause I wanted to watch the movie again with a friend of mine and checked the source in the process.
VIDEO_TS.VOB was there on that disc. I find it highly unlikely that there should be two 'versions' of the same movie at the same region area though, isn't it?!
setarip_old
19th June 2006, 22:20
@Digga
Hi!
As far as I know, every commercial DVD contains a "VIDEO_TS.IFO" file.
Did you mean "VIDEO_TS.VOB"?
Digga
19th June 2006, 23:39
As far as I know, every commercial DVD contains a "VIDEO_TS.IFO" file.
Did you mean "VIDEO_TS.VOB"?yes. I edited my post above to reflect this.
jdobbs
20th June 2006, 00:06
The point is (or at least should be) that if there was no VIDEO_TS.VOB on the original -- there shouldn't be one in the backup. If there was one on the original, there should be one on the backup also.
If VIDEO_TS.VOB exists in the source directory... it will exist in the DVD-RB output. But DVD-RB cannot create it from thin air.... and it shouldn't try. It's supposed to be creating a backup that matched the format of the original.
I have personally never seen a commercial disc that references a non-existent VIDEO_TS.VOB file from VIDEO_TS.IFO...
setarip_old
20th June 2006, 01:34
@DiggaI just rented the same movie (R1) at a store here nearby cause I wanted to watch the movie again with a friend of mine and checked the source in the process.
VIDEO_TS.VOB was there on that disc.Are there any other differences between your owned original and the rented original?
Are the barcodes identical?
Digga
23rd June 2006, 07:31
Are there any other differences between your owned original and the rented original?
Are the barcodes identical?ah, I didn't check that. I only had a quick look at the disk.
friend: 'whatcha doing? come one, I have to get this thing back before 12...'
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.