|
|
VobBlanker Warning message
I'm using version 2.1.0.0.4b and when i try to blankthe main language screen on insertion of dvd i get this message.
This is the screen i wish to blank and the message i get when i try to.
Is it possible to blank out this screen with vobblanker and if so am i doing something wrong?
Originally Posted by nomorecoastersI'm using version 2.1.0.0.4b and when i try to blankthe main language screen on insertion of dvd i get this message.
This is the screen i wish to blank and the message i get when i try to.
Is it possible to blank out this screen with vobblanker and if so am i doing something wrong?
I think you should use PgcEdit to blank the main language screen. If I'm not mistaken, vobblanker does not do that well at this point, which is why you get this warning. PgcEdit's kill PGC function can handle menus: it will ask you which button you'd like bushed by default when the PGC is killed.
jeanl
Thanks foir the reply, ive looked into PgcEdit bit it looks far to complicated for me
I like the ease of vobblanker its a shame it cant blank the main language screen
nomorecoasters, it's really not difficult, hold on!
Open your DVD in PgcEdit, locate the language menu (you can use the preview for that) by selecting a PGC on the left side (one with buttons) and pressing the quot;`quot; key.
Once you've located your language menu PGC, right click on it and select quot;Kill PGCquot;. A dialog will popup with the menu, and you'll be able to select which language you want. Select it, press Kill and you're done. Save and test...
I don't see that as more complicated than vobblanker...
Jeanl
nomorecoasters
Please give PgcEdit a try. Not difficult.
VobBlanker does a very limited manipulation in VM commands, in fact, only when blanking PGCs. The king in this area is pgcEdit (also freeware), so I'm not going to spend time on it.
A language selection menu cannot be bypassed w/o selecting the language you want, so this is the reason for the warning.
BTW, once you start to play with pcgEdit, you'll find it an essential tool... (and you'll learn a lot)
jsoto
Ok i'll give it another try
Its just that i'm so used to vobbalnker and how it works that there seemed to be so much invloved in pgcedit , but i'll give myelf some time and have another go
OK OK OK i'll take it all back, i did it in next to no time and i was amazed that i didnt have to save out a new copy like i do with VobBlanker.
Its a great proggy although theres a hell of a lot that i dont think i'll ever figure out but for getting rid of these language screens its fantastic.
Thanks for kicking me up the backside and getting me to give it another go
Originally Posted by nomorecoastersThanks for kicking me up the backside and getting me to give it another go
we love to do the kickin'!
Jeanl
Originally Posted by nomorecoasters... i was amazed that i didnt have to save out a new copy like i do with VobBlanker.
It's because PgcEdit doesn't actually remove the PGC contents from the VOBs. It just changes the VM commands so that the PGC is not played anymore.
If you want to regain the space used by the video (probably negligible in the case of a language selection menu), you should accept the option to remove the references from the IFOs when you kill playback, and then process the domain with FixVTS or VobBlanker. (There is no need to blank the PGC, since the unreferenced video will be dropped anyway.)
Ok have seemed to hit on a slight problem
I have balnked out the language screen and all seems fine when played via PowerDvd but once burned with nero it does not play in my standalone dvd player.
I have burned with the language screen in place and it plays just fine but i seem to get a 'bad disc' after using pgcedit and burning.
1. upon loading the dvd im met with a warning screen about there being 'disrepancies in some VMGM/VTSI_MAT tables' so i select 'yes' for macro to fix them.
Then im met with a few more of these warnings that i click 'yes' to.
2. Then a 'find BOV' screen appears that scans so i let it and click close.
3. i use the preview screen to see what i want out and press 'kill PGC playback' i then get a kill PGC playback check that i press yes to.
I then select the language i want to use and press 'kill playback'
4. i then get another screen asking if i want to remove the programs and cells from the PGC, so i say yes.
5. i then press save dvd and its done and ready to burn.
Where ami going wrong please
Originally Posted by nomorecoastersOk have seemed to hit on a slight problem
I have balnked out the language screen and all seems fine when played via PowerDvd but once burned with nero it does not play in my standalone dvd player.
I have burned with the language screen in place and it plays just fine but i seem to get a 'bad disc' after using pgcedit and burning.
Where ami going wrong please
Without a View to the Kill[Playback] VM commands I can only hazard a guess . I think the Language Menu was in a multi-cell PGC and there were other navigation commands in the PGC that the KillPlayback bypass codes did not handle. It could be complicated by the fact that the soft player PowerDVD was fairly forgiving with some invalid command, while the standalone DVD player choke on it.
Anyhow, PgcEdit's Kill Playback function would be ill-fitted for use to bypass Aspect Ratio or Language Menu. The function uses a formulated routine to apply bypass codes to the navigation commands. I think this 'Quick Kill' approach did very well for Title PGC bypass, but not so well in other types of bypass without some tweaking of the commands.
If you still want to continue this pursue, I would suggest a 'Safe Kill' method in this 2COOL guide. It is not as quick but the tutorial was well-written and worth learning. It uses PgcEdit core edit power to apply the bypass, no guess, no mess. Playability is also much better .
Ok thanks for the help and link to the guide, i'll do some more reading and get back
Originally Posted by voo_doo99Anyhow, PgcEdit's Kill Playback function would be ill-fitted for use to bypass Aspect Ratio or Language Menu. The function uses a formulated routine to apply bypass codes to the navigation commands. I think this 'Quick Kill' approach did very well for Title PGC bypass, but not so well in other types of bypass without some tweaking of the commands.
I don't agree with you on that one. PgcEdit's kill function was updated by r0lZ to bypass menus too (in which case it asks you which button to quot;pressquot; in the bypass), and in my opinion, it's as quot;safequot; as it is when you use it to bypass a regular title.
jeanl
Originally Posted by jeanlI don't agree with you on that one. PgcEdit's kill function was updated by r0lZ to bypass menus too (in which case it asks you which button to quot;pressquot; in the bypass), and in my opinion, it's as quot;safequot; as it is when you use it to bypass a regular title.
jeanl
You are batting 0 for 2 for the 'Quick Kill', jeanl. You are not kickin'! a$$ on this one, nor this one .
Just kiddin! mon ami , my point on quot;safequot; [inthis particular instance] was that when navigation steps were short-circuited for a bypass, there might be some adverse effects. The KillPlayback function, as I remember, was original modeled as a macro to automate the steps in 2COOL's PGC TitleSet Blanking guides. For this purpose it did very well, I used it all the times. Maybe at some later point, r0lZ expanded its functionality to bypass menus with buttons. Was this functionality intended to replace 2COOL's Remove Language and Aspect Ratio menu? I didnot try it but I don't think it would do a good job here. Because of the short-circuiting, playability will suffer. As smart and effective as the current KillPlayback is, it was simply not possible to cleanly bridge all navigation steps. 2COOL method employed a more conservative approach and thus retain better playability
I just call it as I see it . My first intent, was to present an alternate solution to the question .
I admit that there are some problems in the kill menu with buttons function. (However, it works just fine when applied to menu PGCs without buttons.)
Currently, the problems are:
1) It is not possible to use the function if the button you want to select by default jumps inside the same PGC. This is, of course, because the PGC cannot be killed this way, since it will still be (partially) played. It is however theoretically possible to follow the chain of cells, and simulate the cell commands if necessary. But it's really difficult to automate. For now, in this case, the user is prompted to select another button, or to abort the macro.
2) Normally, the button command is copied in the pre-commands to simulate it. (There is one exception: a LinkTailPGC is not copied, since it is illegal, and useless anyway.) This method works fine. The problem is that it is possible that a command which is legal in the button is illegal in the pre-commands. This is the case, for example, of a LinkNextPGC command. This case is not checked, and therefore, it is possible to break the navigation. But it works with most of the players, even if it's illegal. I will try to improve this part a bit. The function should at least display a warning in this case.
3) The case of a Set with a Link command is not handled. Therefore, the set command is copied, and the link is not removed. This could lead to navigation problems. It's the main problem, and it is also on my todo list.
As far as I know, there are no other issues with my method.
Voo_doo99, if you think there is another problem, please describe it with more precision. Thanks in advance.
Final note: 2COOL's method is fine, and works well, but it's not comparable to a real kill plauback, since the cell is still played. You have to blank it to bypass it really, and you will still notice the black short cell. My method is an attempt to kill the playback completely.
r0lZ,
Welcome, hope you didn't mind my little critique . Really I was just having a friendly ribbing at jeanl; so funny his 'Quick Kill' pitches in two instances ended up with unexpected complications . And I wanted to mention the alternate method which might bring more satisfactory results.Originally Posted by r0lZ...
Final note: 2COOL's method is fine, and works well, but it's not comparable to a real kill plauback, since the cell is still played. You have to blank it to bypass it really, and you will still notice the black short cell. My method is an attempt to kill the playback completely.
Thanks for the explanations for Kill PlayBack. Frankly, I didn't know about this new usage until I read the first post. But I could see the limitations there, and hence my reservations. The second case [playability] bothered me more because I ran into this issue a few times . Got to hate the quot;digitalquot; behavior of DVD: go-or-nogo; can't just fast forward over the problem like tape. The very reason why I preferred 2COOL method, trading shortcut for minimum disruption in navigation and playability.
I cheer your committment to enhance the functionality. I am impressed with what it can do now, and very certain that you will [magically, like I've seen before ] bring it to perfection. Thanks. |
|