Log in

View Full Version : IFOupdate error: Improper VIDEO_TS.IFO file. Aborting!


Turd_Ferguson
7th April 2003, 05:27
so i have gone through the guide for DIF4U and DCCE4U. i finished reauthoring with scenarist, renamed my files, and placed them into 1 folder with the original files from the DVD. i then use IFOupdate and get the error above. i opened video_ts.ifo with notepad and saw that it did start with "DVDVIDEO-VMG".

any ideas?

OmegaZero
8th April 2003, 01:41
I'm getting the same issue with 'The Godfather'. PGC 1 is the only PGC touched by DIF4U and DC4U. PGC2 is just the Film ratings intro.

As the guide outlines:

VIDEO_TS.BUP 27/04/2001 (original)
VIDEO_TS.IFO 27/04/2001
VTS_01_0.BUP 07/04/2003 (Authored)
VYS_01_0.IFO 07/04/2003
VTS_01_0.VOB 27/04/2001
VTS_01_1.VOB 07/04/2003
VTS_01_2.VOB 07/04/2003
VTS_01_3.VOB 07/04/2003
VTS_01_4.VOB 07/04/2003
VTS_01_5.VOB 07/04/2003
VTS_02_0.VOB 27/04/2001
VTS_02_0.VOB 27/04/2001
VTS_02_1.VOB 27/04/2001

Perhaps something is wrong with the guide? I hope it's just something we are doing wrong.

Eyes`Only
8th April 2003, 02:03
" i then use IFOupdate..." tells us nothing. What did you have in your "original IFO Path" box? "Authored IFO Path"? Did you get vts sectors? We can't help when you give us vague explanations?

OmegaZero
8th April 2003, 02:15
I found out why The Godfather didn't work for me. Just a little confusion on a part of the Trilight guide. In the Trilight thread I posted my little take on it. I might be wrong, but doing what I did made 'The Godfather' work.
Trilight's thread (http://forum.doom9.org/showthread.php?s=&postid=291643#post291643)

TRILIGHT
8th April 2003, 02:47
Well, I am not sure if you are actually following the UberGuide or something else. I will assume that you are since I was referred to this thread by the post on my guide's thread. That being said, here is a quote from the UberGuide...

"You start off by copying all files that you are not going to have to re-author. There's no sense in copying all the VTS_01 VOB files if you're replacing them anyway. You DO however, want ALL of your *_0.VOB files, all IFO files, all BUP files, all VIDEO_TS.* files and any other files you do not plan on reauthoring. For instance, let's say your title set VTS_03 only totalled around 50MB. You might not want to go through the trouble of reauthoring this set. Instead, you would simply use it as-is. Therefore, you will want to copy over all of the VTS_03_*.VOB files into the FINAL directory."


I can only assume that you are not doing this particular step correctly. It sounds as if you are trying to run IFOupdate and not properly selecting the appropriate files. Also, as for the comment on opening the IFO file in Notepad... don't! That's a sure-fire way to totally screw it up. Do not attempt to do anything to an IFO file in Notepad. Use IFOedit.

TRILIGHT
8th April 2003, 02:49
Damn! I guess that's what I get for starting a reply...going to the store...and then completing it when I come back. There were already two replies to what I was replying to by the time I posted! LOL! :D

aquabubble
8th April 2003, 07:51
I have sometimes seen this error when I have the "Get VTS Sectors" option checked in IfoUpdate. Can't imagine why it would be but since I prefer to do this step in IfoEdit, I've never thought much of it. Anyway, give it a shot with this option turned off and see what happens.

Turd_Ferguson
8th April 2003, 07:59
ok. in C:\TRAINING_DAY\VTS01 i have:
-ORIGINAL VIDEO_TS.IFO & .BUP
-ORIGINAL VTS_01_0.IFO & .BUP
-all the files made by DIF4U and DCCE4U.
in IFOUpdate this is the Original IFO Path.

in C:\TRAINING_DAY\final\0\VIDEO_TS i have:
-AUTHORED VTS_01_0.IFO & .BUP
-AUTHORED VTS_01_x.VOB
-ORIGINAL VTS_01_0.VOB
in IFOUpdate this is the Authored IFO Path.
my backup path is C:\TRAINING_DAY\BAK.

now i open IFOUpdate and press the "update IFO" buton. with this configuration, i no longer get the "improper VIDEO_TS.IFO" error. instead i get "ERROR: File: VTS_01_PGC_01 - Stream Information.txt is not correctly sized on sector boundary. ABORTING"

it took me quite awhile to calm my frustration down enough to type this. please help.

TRILIGHT
8th April 2003, 08:07
I think you should take a look at what both myself and OmegaZero had to say in the other thread OmegaZero mentioned above. You are not selecting the proper files. Follow my UberGuide (link listed in my sig) and you will see the flaw in your IFOupdate process. Granted, this addresses only the flaw in the steps you're taking with IFOupdate. There is no telling if you've done something elsewhere to cause additional problems which have served to complicate your total project.

Turd_Ferguson
8th April 2003, 09:46
i give up. i have repeatedly read The UberGuide, Doom9 guide, and OmegaZero's and TRILIGHT's posts on the other thread about this subject. i can see nothing different from what they have said and i have done. thank you for the help by the way. i'm now going to restart everything. last time i followed the Doom9 guide exactly. this time i will change these things:

-check DCCE4U to start automatically in DIF4U. i didn't do this last time because you can't add Chapter File List PGC01-CCE-FILM.TXT to VTS__02_P01.16~9_1 without stopping DC4U. i can live without 'I' frames at the start of chapters, i'd rather get this movie working.
UPDATE! i changed my mind on this and will make chapters.

-i am using AviSynth 2.08, just like last time. i have now changed the footer in DIF4U to "addaudio()" instead of "resampleaudio(44100)". i don't know if DC4U uses the .AVS files, but CCE SP 2.50 alone won't open them unless i change this. mabey it will help.

one other thing. i have noticed something when i open the *.M2V files (the ones made by DIF4U and DC4U) in media player. the files are always longer than the time displayed for them. in other words, they keep playing after the position indicator has reached the end, but not by much. could that have someting to do with the "sector boundary" error i am getting?

jdobbs
8th April 2003, 21:32
I have the code open in front of me. Absolutely the only thing that can give that error is if the first 12 bytes of the file do not spell out "DVDVIDEO-VMG"

aquabubble
9th April 2003, 10:03
I could have sworn I have seen this problem occur when I have "Get VTS Sectors" checked in IfoUpdate. I'm pretty sure that even though I got this error, the IFOs had been updated anyway. But then, my memory could be completely messed up. Then again, why would I have this bizarre recollection... ho hum... :confused:

jdobbs
9th April 2003, 10:50
@aquabubble

You are absolutely correct, that is when you would have seen it. There are only two times that IFOUpdate checks the VIDEO_TS.IFO file -- when Correcting VTS Sectors and when Removing Region Checks. It is just a sanity check to make sure the file is what it says it is before modifying it.

You are also correct on the other count. The Original IFO file has already been updated by the time this check is done. The only thing that would not have been done is the "Correct VTS Sectors". There is a slightly different but similar message that you would get for the "Set Region Free"

searvy
10th April 2003, 00:54
I got this same problem. But I figured it out. Dif4u makes a video_ts folder and copies all the menu vobs and original ifo's. Point ifoupdate to those for original ifo. Then ifoupdate will update the ifo's in the video_ts folder with the info from the ifo in pgcxxx directory. Then all you do is copy the authored vobs from scenarist and leave the scenarist authored ifos behind.

And a sidenote do another get vts sectors with ifoedit because ifoupdate doesn't correct the bups.

TRILIGHT
10th April 2003, 01:02
Originally posted by searvy
And a sidenote do another get vts sectors with ifoedit because ifoupdate doesn't correct the bups.

I am unsure if IFOupdate does this or not. They are backup files anyway so ultimately it should not matter. As for having to do this in IFOedit, it is not necessary. I have not used IFOedit for updating the VTS sectors in forever (I use IFOupdate exclusively now).

jdobbs
10th April 2003, 01:38
And a sidenote do another get vts sectors with ifoedit because ifoupdate doesn't correct the bups.

That is incorrect. IFOUpdate updates the BUPs.

searvy
10th April 2003, 02:04
Originally posted by jdobbs
That is incorrect. IFOUpdate updates the BUPs.

Oh yeah? Get vts sectors with ifoedit after ifoupdate is done. It will update only bups and won't even touch the ifos.

Turd_Ferguson
10th April 2003, 05:45
ladies and gentlemen, i now have a PERFECTLY working backup of Training Day. Main movie chapters, extras, sound... all perfect.

after i restarted everything and got to the point where i was stuck with IFOupdate, i unchecked "autocorrect VTS sectors". i used the suggestions by searvy, and used the files in the VIDEO_TS folder as "originals" and files in VTS0x folders as "authored". all these files and folders were created by DIF4U. under this situation IFOupdate updated the ifo's without an error message. then i clicked the button for "Correct VTS sectors". again all good. next i moved the .VOB files created by scenarist to the VIDEO_TS folder created by DIF4U. i tried powerDVD to see if it worked and it did... badly. the chapters were all off and some extras didn't play what was selected in the menu.

so i went back to IFOupdate. i changed the "authored" ifo's to the ones made by scenarist. this time i checked "autocorrect VTS sectors" in options and updated the ifo's. worked fine, no errors. started powerDVD and discovered i had done everything right this time.

i want to thank everybody who has posted to this thread, and helped me out with my noob problems in making my first backup.

Eyes`Only
10th April 2003, 06:23
Turd_Ferguson: Great to hear! After much experimentation, it seems you got it right:

Original IFO = The .ifo in the VIDEO_TS folder created by DoItFast4U!

Reauthored IFO = The .ifo created by Scenarist, located in it's "<output directory>\0\VIDEO_TS" directory. NOT the one in DoItFast4U!'s working directory.

Sorry you had confusion, but glad to see you persevered, didn't give up, and now are enjoying the fruits of your labor!

jdobbs
10th April 2003, 21:44
@searvy

I have done it hundreds of times. I tested IFOUpdate using IFOEDIT when I wrote it. I have never once seen this happen. That doesn't mean it didn't happen for you -- it just means there is apparently something very unique in the title you are trying to do.

That, however, doesn't mean IFOUpdate doesn't update .BUPs as you contend. If that were the case I would be rushing to fix it.

I repeat. IFOUpdate DOES update the BUPs.

TRILIGHT
10th April 2003, 22:02
Originally posted by Turd_Ferguson
ladies and gentlemen, i now have a PERFECTLY working backup of Training Day. Main movie chapters, extras, sound... all perfect.

Congrats! Glad to hear you got it worked out and are on the right track now!

Grover
14th May 2003, 10:57
Do i need to worry about this IfoUpdate error ?

(a variation on the posts above)

ERROR: File: VIDEO_TS.BUP is not correctly sized on sector boundary. ABORTING

First I chose the original and authored .ifo's for "VTS_01_0.IFO" and press UPDATE IFO. No problems.
Then I press "Correct VTS Sectors". No troubles here.
Then I update the IFO's for VTS_02_0.IFO. again, no problems.
Then when I press "Correct VTS Sectors" I get the error above.

I continued on and succesfully update the rest of the IFO's.

The DVD plays fine in PC and on standalone (although NERO does warn me that "File re-allocation has failed" and then I can continue the burn no problems. It seems to play fine. It's only the .BUP file. Should I worry ?

I did not have the "Auto Correct VTS Sectors" ticked.

Any suggestions ? (thanks...)

jdobbs
14th May 2003, 21:45
The problem is that on a DVD everything is centered around 2048 byte sectors. All file lengths must be an even multiple of 2048. When IFOUpdate was computing the sector offsets for the update it found a .BUP file that wasn't on an even 2048 byte boundary. That file had to have been corrupted in some way.

When you burned the disc, it sounds like NERO has noticed the same thing and tried to correct it. If it is working fine... no big deal, I wouldn't worry about it. BUP files are only backups of the .IFO files and is used only when they are found to be corrupted.

In the future, though, it would be wise to correct an error of this type by simply copying the corresponding .IFO file over the top of the .BUP.

Not sure how the file could have been corrupted, most likely there was some point at which an action was aborted at the wrong point in the copy from DVD or update.

weiyu
17th May 2003, 20:58
Hi I have similar problem with IFOUpdate.

I use DoItFast4U! v.1.1.1.0, DoCCE4U 1.0.1.2 Beta, and ReAuthorist 0.6.2 Beta to backup Training Day NTSC DVD. Everything is nice and smooth until the last step of using IFOUpdate to update the IFO files.

See attached snapshots of IFOUpdate error message.

Please help!!

http://home.covad.net/~weiyu99/ifoupdate.jpg
http://home.covad.net/~weiyu99/ifoupdate2.jpg

ShaneZ
18th May 2003, 02:10
Originally posted by weiyu
Hi I have similar problem with IFOUpdate.

I use DoItFast4U! v.1.1.1.0, DoCCE4U 1.0.1.2 Beta, and ReAuthorist 0.6.2 Beta to backup Training Day NTSC DVD. Everything is nice and smooth until the last step of using IFOUpdate to update the IFO files.

See attached snapshots of IFOUpdate error message.

Please help!!

http://home.covad.net/~weiyu99/ifoupdate.jpg
http://home.covad.net/~weiyu99/ifoupdate2.jpg

Well, this may not be the problem, but I use IFOUpdate on a regular basis with no problems whatsoever. Assuming your /trainingday/test folder is your final direcotry, when Updating I usually have AutoAnalyze Original IFO checked. That may not be your problem, that is just from my settings. Also, make sure you have the original ifo in the /test directory.

Hope that helped...

Shane

jdobbs
18th May 2003, 16:51
@weiyu

That's a completely different error. That one means that the new file was not authored correctly. Specifically it means that the one you've authored has more cells than the original, and the total space needed to store the cell pointers is greater than what is available in the original IFO file.

If you open each and look at them with the graphic view of IFOUpdate you'll see the difference.

jdobbs

weiyu
18th May 2003, 19:07
Originally posted by jdobbs
@weiyu

That's a completely different error. That one means that the new file was not authored correctly. Specifically it means that the one you've authored has more cells than the original, and the total space needed to store the cell pointers is greater than what is available in the original IFO file.

If you open each and look at them with the graphic view of IFOUpdate you'll see the difference.

jdobbs

I use IFOEdit to look at both IFO files (see attached link), they all have same number of cells the only difference I can see is the duration of each cell is different.

Also, when I enable AutoAnalyze in IFOUpdate (see attached link) I got run time error. Any idea what cause this?

BTW, how do you look at graphic view of IFOUpdate?


Many thanks!!


Dennis

weiyu
18th May 2003, 19:40
Originally posted by jdobbs
@weiyu

That's a completely different error. That one means that the new file was not authored correctly. Specifically it means that the one you've authored has more cells than the original, and the total space needed to store the cell pointers is greater than what is available in the original IFO file.

If you open each and look at them with the graphic view of IFOUpdate you'll see the difference.

jdobbs

I use IFOEdit to look at both IFO files (see attached link), they all have same number of cells the only difference I can see is the duration of each cell is different.

Also, when I enable AutoAnalyze in IFOUpdate (see attached link) I got run time error. Any idea what cause this?

BTW, how do you look at graphic view of IFOUpdate?


Many thanks!!


Dennis

http://home.covad.net/~weiyu99/ifoedit_authored.jpg

http://home.covad.net/~weiyu99/ifoedit_original.jpg

http://home.covad.net/~weiyu99/ifoupdate_analyze.jpg

weiyu
20th May 2003, 07:21
Originally posted by Turd_Ferguson
ladies and gentlemen, i now have a PERFECTLY working backup of Training Day. Main movie chapters, extras, sound... all perfect.

after i restarted everything and got to the point where i was stuck with IFOupdate, i unchecked "autocorrect VTS sectors". i used the suggestions by searvy, and used the files in the VIDEO_TS folder as "originals" and files in VTS0x folders as "authored". all these files and folders were created by DIF4U. under this situation IFOupdate updated the ifo's without an error message. then i clicked the button for "Correct VTS sectors". again all good. next i moved the .VOB files created by scenarist to the VIDEO_TS folder created by DIF4U. i tried powerDVD to see if it worked and it did... badly. the chapters were all off and some extras didn't play what was selected in the menu.

so i went back to IFOupdate. i changed the "authored" ifo's to the ones made by scenarist. this time i checked "autocorrect VTS sectors" in options and updated the ifo's. worked fine, no errors. started powerDVD and discovered i had done everything right this time.

i want to thank everybody who has posted to this thread, and helped me out with my noob problems in making my first backup.


Turd_Ferguson,

Did you change any default setting in DoItFast4U and DoCCE4U when you backup Training Day DVD? I'm stuck in the last step which is using the IFOUpdate to update the IFO files and I'm thinking maybe it's the settings in the DoItFast4U and DoCCE4U that cause the problem.

Many Thanks!!

Dennis