VobBlanker save log message.

It means that it has modified the commands of the blanked PGCs so that they are not played anymore, and you will normally not see the short black video when the PGC is called. You can turn this option off if you want. BTW, it's the same technique than the Kill Playback function in PgcEdit.

It is in red because only 7 PGC/10 were modified. This means that you may still see the black tiny cell in 3 PGCs. 3 PGCs were not modified because, in some cases, it is not safe to do the command modifications. There are many informations on the kill playback method here at D9. Use search. Briefly: the method is to copy the post commands at the end of the pre commands, and change the original BREAK pre-commands to GOTOs to the first added pre-command. This way, the pre-commands are executed normally, but instead of continuing with the playback of the video, the post commands (now pre-commands) are executed immediately. In the original post-commands, there is normally a jump to another PGC. This jump is therefore now executed before the PGC has been played, and the navigation continues normally. Turning this option off has obviously the effect that the playback of the tiny black cells will occur.

In fact, it is Orange (= Warning). Red is used in Errors. jsoto

AH!? Good news! But then, how does it works when the user uses rew or ff over a cell boundary? Does it mean that the operation is stopped and relaunched on the prev or next cell?

I think the settop uses the Cell Elapsed Time, present in the nav pack and the playback time in the IFO, but not sure what it exactly does... jsoto

OK, thanks for the clarification. So, voo_doo99, it is safe to remove/remap any cell except ILV/Angle cells in PgcEdit, and then use FixVTS to remove them from the VOB files. Currently, VobBlanker has the same limitation.

Ooops. Yes, I forgot the ILV case... Well, VobBlanker currently fixes them if the VTS is ILV-ed. And for angles too, but you need to previously remove the angles in the IFOs... jsoto