Pgc Error With Vobblanker

[dsixteen]

hi guys.

when i try add subtitle to a dvd with subtitle creator. im having this error @step 3 with vobblanker. is there any suggestions??

http://img78.imageshack.us/img78/6208/yenibitelemresmi2ny7.jpg (http://imageshack.us)

[jsoto]

Take a look inside your remuxed DVD.
C:\VIDEO_TS\remuxed\VIDEO_TS.IFO
Open it with pgcEdit (or VobBlanker) and see if the VTS #1 has more than one PGC in the TITLES domain. If it has, this is the problem: to replace PGCs, the replacing IFO must have only one PGC.
But if the IFO has only one PGC, you'd have found a bug in VobBlanker.

jsoto

[dsixteen]

remuxed folder is being deleted by subtitlecreator when progress comlete. i had a look at to source dvd with dvddecrypter. there r another pgc under the main movie. is that might be a problem. any ideas??

http://img299.imageshack.us/img299/6905/adszkc2.jpg (http://imageshack.us)

[Robotik]

load the replacing dvd on your hdd to PgcEdit. if it still has the same structure as shown above, select vtst 3,2; if it hasn't, find the corresponding pgc by playtime. then go to domain -> delete last pgc in domain. if vtst 3,2 has a title number which is not the highest title number on the whole dvd, then you have to remap title numbers first (title -> remap title numbers, select the corresponding title number, and press 'to bottom'), then delete pgc. if that was all the problem, it should be fine afterwards

[jsoto]

The original DVD can have more than one PGC. That's not a problem.
The replacing DVD (the remuxed one in your case) must have only one pgc.
Please copy the IFOs of the replacing DVD (the remuxed one) to a safe folder before closing VobBlanker's error message

jsoto

[dsixteen]

ok. thats the deal.

the remuxed dvd is not able to open with pgc edit or another program. i thimk its broken. but vob files r ok. i've created new ifo files with ifo edit. but this time subs are displaying green and looks very bad. by the way; if i can create ifo files correctly can i still get original menu by using VobBlanker.

[jsoto]

If the remuxed DVD is broken , you should try to detect why. May be in Muxman's log you can find the reason.

Anyway, no problem at all with the subs colors. They will be recovered by VobBlanker when replacing the PGC (just do not check "copy PGC subs palette from replacing IFO" )

jsoto

[Robotik]

how about FixVTS?
or copy the dvd again, and remove pgc before remuxing?

[Robotik]

anyway, once your dvd is working, you can adjust subtitle colors in DVDSubEdit, or in PgcEdit, too
for getting the original menus you can use PgcEdit's menu -> import menu function

[jsoto]

If something that usually works for others, does not work in a particualr case, IMO some time has to be spent trying to find the issue. This is how the bugs are found and fixed. Jumping to other procedure or method without spend one minute does not help anybody.
In this case, I cannot understand why Muxman is producing a corrupted IFO (assuming this is the problem). Muxman is a very stable piece of SW, so I think it requires an investigation, and (probably) the problem will be a different one..
jsoto

[dsixteen]

ok than, lets see . yesterday i subbed about 8 dvd's. 3 of them done without a warning. with 1 of them i had the warnings below. just clicked ok and passed. output worked well but i still wonder what was that all about.

http://img226.imageshack.us/img226/2356/191gu3.jpg (http://imageshack.us)

http://img226.imageshack.us/img226/2075/2qk2.jpg (http://imageshack.us)

and with the other 4 i had the error @first post. i've unchecked the "retain the menu with original..." box. so SubtitleCreator didnt use Vobblanker at all and progress comleted without an error. but output didnt work.

lets investigate it then. what do you recommend me to do. if i had errors during progress i could do anything but without error im tied up:(

[dsixteen]

finally found it. i'm having this error with muxman;

"Reference to non-existant scene "Segment_1_scn36" from PGC "VTS01_TTL01_PGC1"

i read couple of posts about it. everybody says use the latest vs. of pgcdemux and/or delete the last line of celltimes.txt. i allready use latest vs of pgcdemux and deleting the last line of celltimes.txt didn't work. any other suggestions??

[blutach]

Those messages are benign usually. The first one says certain bits of the IFO can be marked in a certain way and VB will do so for you.

The second simply alerts you to different entry points being reported in different parts of the IFO. This warning is very usual in ARccOS DVDs where these PGCs are not played - and it is not an error anyway, since it is legal to have this.

As to your muxman mux, you may have a bad m2v file. Are you sure there are 36 segments? If so, does the m2v for segment 36 play OK in a software player?

Regards

[dsixteen]

there r not 36 segment. there r 36 cells. but here r only 29 chapters. i think problem is cells r more than chapters, is that possible.

MuxMan version 0.17.4
Opened script file C:\VIDEO_TS\SC_TEMP\MuxManProject.mxp
Accepted audio C:\VIDEO_TS\SC_TEMP\AudioFile_80.ac3
Accepted audio C:\VIDEO_TS\SC_TEMP\AudioFile_81.ac3
Opened sub 1 file C:\VIDEO_TS\SC_TEMP\Subpictures_22.sup.
Opened sub 2 file C:\VIDEO_TS\SC_TEMP\Subpictures_21.sup.
Opened sub 3 file D:\Documents and Settings\dsixteen\Desktop\tr.sup.
expanded database to 300 entries.

13:49:08 Begin multiplex VTS01.
Title Segment List
Segment_1 non-seamless
Encoded stream 20 is script stream 1.
Encoded stream 21 is script stream 2.
Encoded stream 22 is script stream 3.
Buffering audio track 1 file C:\VIDEO_TS\SC_TEMP\AudioFile_80.ac3.
Buffering audio track 2 file C:\VIDEO_TS\SC_TEMP\AudioFile_81.ac3.
Maximum audio duration 391870 fields.
Positioned C:\VIDEO_TS\SC_TEMP\VideoFile.m2v to 00:00:00:00
Starting scene Segment_1_scn1 at 00:00:00:00
Starting scene Segment_1_scn2 at 00:04:45:16, requested for 00:04:45:09
Starting scene Segment_1_scn3 at 00:07:43:05, requested for 00:07:43:03
Starting scene Segment_1_scn4 at 00:13:06:01, requested for 00:13:05:28
Starting scene Segment_1_scn5 at 00:15:09:20, requested for 00:15:09:17
Starting scene Segment_1_scn6 at 00:17:05:05
Starting scene Segment_1_scn7 at 00:17:50:25, requested for 00:17:50:12
Starting scene Segment_1_scn8 at 00:21:57:15, requested for 00:21:57:09
Starting scene Segment_1_scn9 at 00:26:50:26, requested for 00:26:50:14
Starting scene Segment_1_scn10 at 00:29:36:10, requested for 00:29:36:03
Starting scene Segment_1_scn11 at 00:30:05:21, requested for 00:30:05:15
Starting scene Segment_1_scn12 at 00:33:24:00
Starting scene Segment_1_scn13 at 00:36:56:18, requested for 00:36:56:12
Starting scene Segment_1_scn14 at 00:43:05:00, requested for 00:43:04:17
Starting scene Segment_1_scn15 at 00:45:28:20, requested for 00:45:28:16
Starting scene Segment_1_scn16 at 00:48:55:11, requested for 00:48:55:09
Starting scene Segment_1_scn17 at 00:53:28:00, requested for 00:53:27:21
Starting scene Segment_1_scn18 at 00:57:21:25, requested for 00:57:21:23
Starting scene Segment_1_scn19 at 00:58:01:21, requested for 00:58:01:20
Starting scene Segment_1_scn20 at 00:59:45:26, requested for 00:59:45:13
Starting scene Segment_1_scn21 at 01:05:04:08, requested for 01:05:04:02
Starting scene Segment_1_scn22 at 01:09:05:00, requested for 01:09:04:19
Starting scene Segment_1_scn23 at 01:09:59:00, requested for 01:09:58:20
Starting scene Segment_1_scn24 at 01:12:30:23, requested for 01:12:30:16
Starting scene Segment_1_scn25 at 01:18:55:21, requested for 01:18:55:13
Starting scene Segment_1_scn26 at 01:23:13:03, requested for 01:23:12:19
Starting scene Segment_1_scn27 at 01:24:27:05, requested for 01:24:26:21
Starting scene Segment_1_scn28 at 01:24:51:17, requested for 01:24:51:08
Starting scene Segment_1_scn29 at 01:29:51:01, requested for 01:29:50:27
Starting scene Segment_1_scn30 at 01:32:59:11, requested for 01:32:58:28
Starting scene Segment_1_scn31 at 01:34:11:08, requested for 01:34:10:24
Starting scene Segment_1_scn32 at 01:38:22:17
Starting scene Segment_1_scn33 at 01:39:57:25
Starting scene Segment_1_scn34 at 01:41:22:00, requested for 01:41:21:17
Starting scene Segment_1_scn35 at 01:44:24:00, requested for 01:44:23:22
SeqEnd at EDF67EC4.
Bytes remaining in buffer = 0.
Bitrate - avg: 5650935, min: 654705 (lba 0), max: 9856951 (lba 1225261).
Shortest GOP has 2 fields, longest GOP has 30 fields.
Fields: 391872, VOBU: 13038, Sectors: 2254901.
Reference to non-existant scene "Segment_1_scn36" from PGC "VTS01_TTL01_PGC1"

[Mtz]

Open the logfile produced by PGCDemux and compare the total number of frames with the latest line from celltimes.txt.
Increase the difference between this 2, lowering the value from celltimes.txt.
Example:
123.456 (logfile)
123.444 (celltimes)
modify 123.444 to 123.410 for example.
Save celltimes and use it in muxman.

enjoy,
Mtz

[jsoto]

Glad to see you follow my recomendation!

BTW, there are many DVDs with an ending blank cell (less than one second) just to allow to jump to the end of the PGC pushing "next-chapter" button in the remote.
In this case, one simple trick to avoid any problem in Muxman is just to delete the last line of Celltimes.txt, which is the init-time of the last cell. When replacing, VobBlanker will add a blank cell to complete the number of cells.

jsoto

[Mtz]

jsoto, in PGCDemux is an option to not save the last cell "include last time". Always I uncheck this, but at many DVDs I need to make the modifications from my previous post. If not, Muxman will give me the same error like dsixteen had. To save time, always I use a smaller value for the last chapter.

enjoy,
Mtz

[dsixteen]

@jsoto
deleted last line but still same error.

@Mtz
increased the difference but still same error.

till cell 34 progress is ok but when it comes to cell 35 progres bar turns from green to dark pink. ps:there r 36 cells

[dsixteen]

i had chapter information with dvddecrypter and put it in celltimes.txt. this time looks ok. i had this warning with vobblanker but output looks ok.

WARNING: Number of Cells lower in replacing title. Blanking last ones.

so am i done:-D or not yet:(

by the way shell i check "fix elapsed time replacing cells" before replacing. i checked it but i dont know what it does. (on the forum some body says it should be checked, thats why i checked)

[jsoto]

@jsoto
deleted last line but still same error.
Difficult to understand.... With one cell less you should have not problems. Any way, you're done!

by the way shell i check "fix elapsed time replacing cells" before replacing. i checked it but i dont know what it does. (on the forum some body says it should be checked, thats why i checked)Not needed if you have re-muxed with muxman. This option is useful if you were replacing cells (you're replacing a PGC) and the replacing cell is created by cutting other one, or something similar, that produces an elapsed time different from zero in the first Nav pack.

jsoto

[mpucoder]

Are you loading a saved project and then trying to import a new chapter list? This will not work as the project file contains all the data (scenes, cells references the scenes, and chapters referencing the cells) created by importing the chapter list the first time. In this case with 0.15 edit the .mxp file to remove the last program of the VTS01_TTL01_PGC1 - the one that refers to "Segment_1_scn36". Also remove the reference to the program from the part of title list. In 0.16 and later you can use the spreadsheet in MuxMan to delete the reference.

[Mtz]

mpucoder, can you explain in a few words why this error appear? (Reference to non-existant scene).
Is some program fault? If yes, which one? PGCDemux or Muxman? This is not happen at all DVDs, only on a few of them and I didn't discovered why. The annoing thing is that the error appear at the end of mux and I must to wait some time if everything is correct.
Can be "relaxed" in Muxman some thing related to this?

jsoto, you are right (as usual, like mpucoder ;)) if the number of cells is not the same as the original, replacing will not work. This is the reason I use a small value for the last cell. Needed a "trick" to have all chapters from muxman output.

enjoy,
Mtz

[mpucoder]

There are two ways to get this error. One is by including the number of frames as the last chapter in the celltimes file. The other happens when trying to make a very short cell at the end and not getting the right frame number of the last GOP. All cells begin on a GOP, and MuxMan will start a new cell on the GOP starting on or after the desired frame. I notice in your log a lot of cells are not beginning where you expected them to. This can be caused by re-encoding without forcing I pictures at the frames that are to be the first in a cell.

[Mtz]

Thanks for the explanations. But this error appear also when I'm trying to add custom subtitles to an original DVD. If the DVD is original, I supposed that all celltimes are starting from a GOP. The software which muxed the original DVD seems that ignore the GOP in that chapter and/or can create small cell.
I think if PGCDemux can make a "Gop check" at the latest cell Muxman will make its job OK. jsoto, can be this possible?

enjoy,
Mtz

PS: in my posts I'm talking about the last cell saved by PGCDemux when I didn't checked the "include last time".

[r0lZ]

If the title is protected by ARccOS or RipGuard, it might have wrong time codes for the chapter points. Try to rebuild the Time Map of the title with PgcEdit (select the PGC, and use any of the Title -> Rebuild Time Map functions.) If PgcEdit displays a text with warnings about wrong cell durations, that's the problem. Save the DVD, and generates the celltimes.txt file again. (BTW, you can also do that from the PGC Editor of PgcEdit. I suggest you use it, and you compare your original celltimes.txt file with the one created by PgcEdit.)

[dsixteen]

Difficult to understand.... With one cell less you should have not problems.

jsoto

Are you loading a saved project and then trying to import a new chapter list? This will not work...

exactly. i'm using the project file which is created by SCreater. so thats why does deleting last line of celltimes not working, does it?

[Mtz]

r0lz, if I remember correctly, I compared the celltimes.txt from PGCDemux and PGCEdit. Was identical. When I'll find another DVD with the same problem I'll post again my experience. Now I can't remember which of them created problems.

dsixteen, I told you in one of my previous post to not delete the last line from celltimes.txt. Just decrease the value of the latest cell until Muxman will not give you any error. Try decreasing about 30 frames that value and mux again. It takes 10 minutes, why don't you try?

enjoy,
Mtz

[dsixteen]

@Mtz
increased the difference but still same error.

dsixteen, I told you in one of my previous post to not delete the last line from celltimes.txt. Just decrease the value of the latest cell until Muxman will not give you any error. Try decreasing about 30 frames that value and mux again. It takes 10 minutes, why don't you try?

enjoy,
Mtz

i already tried it. deleting and decreasing both working. is there any difference between them or which one is better way.

[Mtz]

If you are replacing the whole PGC use the decrease method. If you'll delete the last value VobBlanker will reject it because the number of cells is not identical with the original, as said also jsoto.

When using PGCDemux, do not check "include end time".
In the celltimes.txt decrease the last value. Do not delete it or increase it. Make the latest 3 XXX numbers smaller than X30.
Example:
123.456 > 123.400
or
123.789 > 123.420
enjoy,
Mtz

[jsoto]

if the number of cells is not the same as the original, replacing will not work. No, I did not say this. When replacing a PGC with another one with one cell less, VobBlanker adds the last cell as a blank one. So what I say (may be I can automate it in pgcDemux as an option) is:
If the last cell of the original PGC is a blank one (used by some authoring programs to allow the "next chapter" button, and also used by ARccOS) it can produce this problem in Muxman, so you can delete the last line in Celltimes.txt, because this blank cell will be added by VobBlanker in any case.

i already tried it. deleting and decreasing both working. is there any difference between them or which one is better way. So, both methods did work or not?. Both should work, but I did not understand they worked for you in your other posts..


jsoto

[dsixteen]

both medhod worked. exept one of my dvd. last two cell was too close to total frames number. so deleting last line didnt work. i had to delete last two lines.