FAVC Error: Reference to non-existant scene

[major4579]

I've been using FAVC to put 4 episodes at a time of a TV show onto a DVD. This includes a menu and subtitle files. I've done Seasons 1-7 (14 DVDs) without a problem. Suddenly I am getting a problem with some of my DVDs (2 out of the last 4). I see the following error in the MuxScript.log:

Reference to non-existant scene "Seg1_Scn14" from PGC "VTS01_Ttn1_Pgc1"

The first time this happened, it was on the 3rd episode (and the numbers above reflected that). I tried running DIVFix+++ on it, downloaded from a different source, but every time I received the above error. I finally tried DVDStyler and it worked fine (though the quality of the DVD video is no were near the quality out of FAVC).

Now I'm receiving this error on the first episode on another season and I am wondering if there is something I can do to fix it that I haven't tried.

Attached is the entire MuxScript.log. I am running FAVC 1.7 on a WinXP-SP3 computer with 4GB RAM. Is there anything else I can post that would help solve this?

Thanks,
John

[manono]

Go and find the celltimes.txt file and remove/delete the very last number. Remux.

[major4579]

I don't have a celltimes.txt, I do have a TitleChap0.txt (there is also a TitleChap1.txt, 2 & 3 - this is a 4 episode disk) in the working directory with the following contents:

7200
14400
21600
28800
36000
43200
50400
57600
64800
72000
79200
86400
93600

I removed the last number and the first and second episode processed fine, but crashed on the third with the same error message. I removed the 93600 from TitleChap2.txt and Muxman ran through all 4 episodes without a problem.

Thanks, I now know how to fix it. But do you know why it's cropping up in the first place?

[manono]

It's called TitleChap0.txt, eh? OK, but it's the same thing - it lists the chapters by frame numbers rather than by time as some do. When demuxing, PGCDemux gives it to you named as a celltimes.txt. That error message is exactly the same as the one Muxman gives when it runs into that problem, so I figured your program is using Muxman as the muxing engine.

Why does it happen? Some (many) DVDs will have a chapter listed quite close to the end. That's so when you wish to get back to the menu and you press 'Next' on the remote control (like, to skip over the end credits) you don't have to fast forward or wait for the last 'real' chapter to complete. You push 'Next' and because that last chapter is so close to the end it seems as if it's going right to the menu, whereas it's really making a quick stop at that last chapter. Muxman has what I consider a bug in that the last chapter can't be too close to the end. It'll abort. One workaround is to remove that last chapter. That's fine for me as VobBlanker will replace that missing chapter with a 'dummy' one so the chapter count remains the same. I've never used FAVC so I don't know if that removed chapter is ever replaced. You might try playing the finished DVD and hitting 'Next' to see what happens as compared to the original retail DVD. And sometimes (rarely) there will be two chapters too close to the end for Muxman's liking.

Another workaround is to keep that last chapter but just subtract 30 frames (1 second for NTSC) from it. This works most times when using the original chapters from the retail DVD.

Also, your own program may have a bug (or you messed up when trying to set the chapter points). The last chapter can't be later than the length of the episode or movie. It looks to me as if you spaced the chapters evenly 4 minutes apart. If the episode is shorter than 93600 frames (for example, which is equal to 52 minutes), that will also cause an abort.

And if this is from a retail DVD, you can get the original chapter points from PGCDemux or from PGCEdit. They'll be much better than having them all spaced equally.

[major4579]

Thanks Manono,

It's good to know why it's happening. I'm working with AVI files and the chapter marks are inserted every 4 minutes by FAVC. So what's happening is that the length of the AVI files is variable and it just happens that I'm now working with files that end up with a 4 minute chapter mark too close to the end which causes the muxman bug to occur.

Now I know what to do and why I'm doing it.

Thanks for the help and the education!

-John