Anybody seen STC flags like this before?

[blutach]

http://img93.echo.cx/img93/7215/untitled7iy.png (http://www.imageshack.us)

This is very weird. It indicates a system time clock discontinuity at every cell. Why could this be? And won't it produce annoying stops at cell boundaries?

Any advice greatly appreciated.

Regards

[blutach]

Forget it - I just see that there is a VOBID change at every cell and therefore the STC flag needs setting.

Weird way to author the main flick though, isn't it?

Regards

[mpucoder]

Doesn't look that wierd to me - each cell (except 13/2) is a new VOB. By definition a VOB starts with STC = 0. But this will not cause any problems in playback, it's the non-seamless joint between 13/1 and 13/2 that could pause. Usually cell_cat of 0 means there are cell commands.

[mpucoder]

The author could have been forced to do this if the cells were encoded individually and he used Scenarist. It does not accept multiple video files in one track. Scenarist does have a file concatenation function to overcome this, but it crashes all the time. And making a seperate track out of each chapter simplifies the timing - there isn't any.

[D3s7]

you can add 2 video segments back to back.... treats them as 2 cells but I've done it before.. (at least w/ 3)

I've always wondered how the file joiner routine worked.. as in IF it worked or not... guess now I know :)

[blutach]

Thanks guys for the heads up.

I guess I'm just used to seeing thing 1/1 1/2 1/3 etc and perhaps the last chapter being 12 frames 2/1.

Regards

[blutach]

Originally posted by mpucoder
But this will not cause any problems in playback, it's the non-seamless joint between 13/1 and 13/2 that could pause.This is just the LB which has now been removed. :)

However, would there be playback problems if the flags were 8 (as what happened in a VobBlanker replacement)? See this post (http://forum.doom9.org/showthread.php?s=&postid=650391#post650391).

Regards

[mpucoder]

Depends on the player, the new ones are getting better and better at ignoring bad authoring ;)

[blutach]

I suspect it's better to be safe than sorry, so I think I should change them back to reflect the STC discontinuity.

Thanks.

Regards

[jsoto]

Nope, after using VobBlanker, there is not a STC discontinuity.
Yes, I know it is not fully correct, but...

PGC replacement assumes a new and continuous PGC, although the VID/CID of each cell are the originals.

jsoto

[blutach]

I am now confused. So what to do?

Maybe a VidChanger? But that is just going to be cosmetic, isn't it?

Regards

[jsoto]

If this is the only one PGC in the VTS, a VIDchanger (after VobBlanker replacement) will do the right work.
VobBlanker replacement changes the VOB with a continuous one, in terms of STC, assuming you have created the replacing VOB with an external muxer "in only one muxing session".
So, VIDchanger will do the last (yes, cosmetic!) part-> replace all the VID/CID of the cells to make them belong to the same VOB.

And, finally , you will have a fully compliant VOB: a single VOB, and STC continuous VTS.

If there are more PGCs in the VTS, well, depends if the cells are reused or not...

jsoto

[blutach]

As it turns ot there is a second title in the VTS with VCID of 1/1 :(

I have burned a disk and will check the playback over the chapter boundaries and report back.

Regards

[blutach]

OK - well, the burned disk plays back perfectly with the original flags (will try a test later with all 8s).

Regards

[jsoto]

Originally posted by blutach
As it turns ot there is a second title in the VTS with VCID of 1/1 :(
Probably you still can do it. Just be careful with the flags in the second title..

jsoto