View Full Version : NavPack issue in vobblanker cell-replace

jeanl
27th January 2005, 18:02
jsoto,

As you know, I've created a small app to extract a cell (typically from a motion menu) and compress it into a single I-Frame cell with subpics. I then use vobblanker to replace the original cell with the compressed one.
I have noticed that after that the VOB is "inconsistent", because vobblanker does not seem to adjust the VOBU end address in the NavPack of the replaced cell to point to the next cell in the VOB file. I guess my program could do it, come to think of it, but I think vobblanker should really make sure that's the case.
If I then try to run my program again on the newly created VOB, it gets lost navigating the NavPacks, as expected...
So, in other words, if vobblanker replaces a cell with one whose "VOBU end address" isn't set right, the resulting VOB will need a mock strip.

Jeanl

EDIT: I modified my program to adjust the VOBU end address values in the created cell, so I suspect the problem above no longer will exist. I'm guessing vobblanker adjusts the "this->lba" value, but I haven't checked. If it does, we should be in the clear...
jsoto
27th January 2005, 19:28
Yes, VobBlanker does not adjust this and other pointers when replacing cells. I'm assuming the replacing cells are well muxed. So, not sure if I have to do it....

What I'm going to do is to integrate the motion2still in VobBlanker. I'll keep you informed.

jsoto
jeanl
27th January 2005, 19:31
Originally posted by jsoto
Yes, VobBlanker does not adjust this and other pointers when replacing cells. I'm assuming the replacing cells are well muxed. So, not sure if I have to do it....

I understand, I see your point. Vobblanker isn't in the business of fixing poorly muxed stuff.


What I'm going to do is to integrate the motion2still in VobBlanker. I'll keep you informed.
jsoto
That's GREAT!
Jeanl
blutach
27th January 2005, 23:58
But if I understand our test results from yesterday, these need to be fixed or else a menu mock strip is required.

Am I missing something?

Regards
jsoto
28th January 2005, 00:03
A menu mock strip should be done in any case. There are a lot of pointers to be fixed. Well, when deleting the audio may be only a few...
jsoto
jeanl
28th January 2005, 00:32
jsoto, I think you can implement it in vobblanker without any need of a menu mock strip... After all, you know how to do this kind of stuff very well, and It's not any trickier than removing a cell for example...
Jeanl
blutach
28th January 2005, 00:38
But jean, if your "engine" (if I can call it that, because I presume it will be the back-end of the new VobBlanker routine) already adjusts for these issues (at least in version 0.114B), is there, in fact, a problem?

Regards
jsoto
28th January 2005, 00:42
VobBlanker already does a mock strip (pointer adjustments) when you cut part of a cell or when strip audios. I do not calculate from scratch all the pointers, but many of them.
I'm thinking in using the same method (it is already there) in motion2still.

jsoto
blutach
28th January 2005, 00:48
@jsoto

Excellent!! That might also solve the issues that I am sometimes experiencing when I cut in VobBlanker (which we have spoken about already).

BTW: I liked the fish!

Regards
jsoto
28th January 2005, 01:19
@blutach
Sorry, but I've to say it does not fix your problem... VobBlanker is fixing the pointers since 1.4.0.1. so your problem still is there...I believe it is related with PTSs and SCRs and may be with cell flags, but not with navigational pointers.

jsoto