View Full Version : IfoEdit 0.971 released! (Important bugfix for NTSC authoring)
Derrow
28th November 2004, 20:45
IfoEdit 0.971 released! (Important bugfix for NTSC authoring)
- fixed: NTSC authoring problems (2).
- added: Programs in PGCs can be added now even if there's no program present already.
- added: empty PGCs can be added now to VTS_PGCITI
- fixed: In VOB Extras, the 'Remove Angle' option was always greyed out under XP.
www.ifoedit.com
FilipeAmadeuO
28th November 2004, 22:08
I have a problem with this new version of idoedit.
After doing the first preview of the chapter (by double clicking on it) i canīt preview anymore. And if the chapter is very long it that much time to load.
Derrrow: Is it possible to change the delete playback function in the title VTS to work just like it does in the menu units ??
2COOL
28th November 2004, 22:48
I best be posting in the right thread this time.
So we having a new feature: Add PGC. Is it always going to be a dummy PGC in the VTS Domain or are you going to give us a option to add a Video Title. I was just thinking...instead of starting us with a dummy PGC, how about adding a new 15 frame blank cell to the new PGC? This would ease people on the DVD Specs that a dummy PGC in the VTS Domain is illegal. I hope you understand where I'm getting at. I just woke up and haven't got my morning coffee yet. :p
2COOL
28th November 2004, 23:00
Is this (http://forum.doom9.org/showthread.php?s=&postid=568309#post568309) still on your to do list?
2COOL
28th November 2004, 23:08
@Derrow
I did a small beta test. I checked all my PUOs for a single PGC. I then click on "remove P-UPs". I get a message saying PGC has PUOps. My reporting here is that if I have the PGC up in question in IfoEdit, it doesn't refresh it to show no PUOps. I think this is a simple refresh fix, do you think?
Derrow
28th November 2004, 23:08
yep :p
2COOL
28th November 2004, 23:20
I've mentioned this before and I believe it's a long time bug that hasn't been fixed. Whenever I create new IFOs, I still have to "Get VTS Sectors" afterwards because my Title set starting sector is set to zero in VIDEO_TS.IFO / VMG_PTT_SRPT.
[00000000] Number of Title play Maps 1
[00000002] Unknown 0
[00000004] length of table 19
[00000008] Title_1: Title playback type 20
type details:
one_sequential_pgc
Jump/Link/Call commands only in pre/post 0
Prohibited user op. PTT play or search no
Prohibited user op. Time play or search no
[00000009] Title_1: Number of angles 1
[0000000a] Title_1: Number of chapters (PTTs) 1
[0000000c] Title_1: Parental ID field 0
[0000000e] Title_1: Title set number (VTS#) 1
[0000000f] Title_1: Title set Title-number (VTS_TTN) 1
[00000010] Title_1: Title set starting sector 0
Derrow
29th November 2004, 00:17
Well, it's not really a bug.
It's just a missing feature to do a sector correction afterwards. :D
But I'll do my best to fix it :p
2COOL
29th November 2004, 03:05
Again on the New PGC feature, I'm in NTSC Land so when I added a new PGC in my VTS_PGCITI, I don't get 30 fps but 25 fps. Major bug?
Same goes when I add a new program and cell in my new PGC and it shows 25 fps in my cell's playback time. :(
Sigh... more discrepancies I think.
In my VTS_PGCITI, my new PGC 4 is holding a wrong Category mask. Should be 132 or 1 (non entry)? Can we have more than one similar category mask?
VTS_PGC_1: Category mask 129
VTS_PGC_2: Category mask 130
VTS_PGC_3: Category mask 131
VTS_PGC_4: Category mask 129
DMagic1
29th November 2004, 03:44
Originally posted by FilipeAmadeuO
I have a problem with this new version of idoedit.
After doing the first preview of the chapter (by double clicking on it) i canīt preview anymore. And if the chapter is very long it that much time to load.
Derrrow: Is it possible to change the delete playback function in the title VTS to work just like it does in the menu units ??
It works fine for me.
jorlando
29th November 2004, 05:23
Just tested!
- Chapters.txt doesn't need to have values modified anymore
- Time counter displays the correct timing
thanks a lot!
FilipeAmadeuO
29th November 2004, 10:53
I have another problem a long time.
When it is 0Kb VOB files the get vts sectors are wrong.
jorlando
29th November 2004, 13:22
derrow,
just for the sake of curiosity, in the ifoedit forum I reported the problem with NTSC authoring showing the wrong time of a DVD, and I suggested that it could be using the frame count to calculate time and then using time to calculate frame count.
Was something like that?
Thanks!
Derrow
29th November 2004, 16:03
jorlando,
yea something like that.
When authoring I must use the frame count to calc the correct time.
And because of this RFF stuff, I had a wrong frame count before.
Derrow
29th November 2004, 16:07
Originally posted by 2COOL
Again on the New PGC feature, I'm in NTSC Land so when I added a new PGC in my VTS_PGCITI, I don't get 30 fps but 25 fps. Major bug?
No bug at all.
You can and have to change everything in the created PGC to your needs.
I just wanted to give you guys a simple way to add a pgc, because some did try to do that using hex-editing, which messed up the entire IFO file. Now you've got an easier way to add a pgc.
When I'll have more time, I'll enhance this PGC adding with some features.
2COOL
29th November 2004, 21:44
Originally posted by Derrow
No bug at all.
You can and have to change everything in the created PGC to your needs.Well OK, but IMHO, it wouldn't be a bug if you had disclosed that information though. At least, we have some improvement in the PGC adding department now.
gnutellafan
1st December 2004, 17:32
Derrow, good to see that you are back. Hopefully everything worked out for you with 321 studios. Thanks for the new release!
Ever think of joining up with someone else like Dimand on DVD Remake?
orandennison
2nd December 2004, 03:41
Hi Derrow, thanks for continuing develelopment on ifoedit. I have a little problem with the latest version: when double clicking on menu entry items the automatic preview feature makes it kind of hard to see what each item is because the preview zips through it so quick. When I try to drag the slider back it just springs back to the right without giving my a complete idea of what's really there. I was hoping that there was a way to disable automatic preview for these really short programs? For right now I've been using .96 because it doesn't auto preview.
2COOL
2nd December 2004, 08:28
Is it just me? But when I create new IFOs with then get VTS sectors, I get this now.
http://img24.exs.cx/img24/6730/ae-Image_004.gif
I've tried it with 4 different VOBs. It plays flawlessly in PowerDVD though everytime.
blutach
2nd December 2004, 09:41
@2cool
Heh. I hope not. I have a flipper to do tonight and, as you know, I merge titles and "create ifos". I hope IfoEdit ain't "bung".
Does 0.96 give same problem???
Regards
2COOL
2nd December 2004, 18:29
@blutach
I'm even getting this message with 0.95 so it must be me. The only thing I installed recently is Ulead's Video Studio 7 so I'll look into this with I get home from work. I'm using DirectX 0.9c (4.09.0000.0904).
Derrow
2nd December 2004, 21:26
2Cool
I just tested the IFO creation, and it is not crashing on my machine.
I think it must be you though.
blutach
2nd December 2004, 23:47
@2cool,
sounds like it might be time for a system restore
Regards
2COOL
3rd December 2004, 03:13
Originally posted by 2COOL
@2COOL
Since you installed and removed WinDVD recently too, try removing or renaming your iviaudio.ax file in your C:\Windows\system32 folder.Thanks 2COOL! That was the problem! Damn... you are just TOO COOL! :D
@Derrow
I cannot stress enough on how valuable your codec reporting function has helped me on troubleshooting this problem. I knew that I was supposed to be using my Cyblerlink (PowerDVD) codecs only. I used 0.96 and here's what I had.
http://img50.exs.cx/img50/5043/17-Image_001.gif
In fact to prove more that iviaudio was the culprit, I chose to debug instead of reporting to Microsoft. So, here's what I got in the debugger.
http://img50.exs.cx/img50/3699/53-Image_002.gif
Please! Can we have the codec reporting back as an option? I'm not asking you this time but telling you.
Derrow
3rd December 2004, 03:43
Yes, I see.
I will add it as option some how.
;)
2COOL
3rd December 2004, 03:50
Originally posted by Derrow
Yes, I see.
I will add it as option some how.
;) Thanks!
Lupo Silenzioso
3rd December 2004, 11:10
what does this error message mean ? i get it when i launch DVD Play.
---------------------------
Warning
---------------------------
* No valid DVD-Video volume could be located
Do you still want to continue?
---------------------------
Sė No
---------------------------
the movie starts without problems....
r0lZ
3rd December 2004, 11:39
I think IfoEdit is able to work an a particular IFO file stored on disk, and use the real DVD in your DVD drive for the other IFOs and VOBS. This is a feature allowing to preview the DVD without the need to copy all the files to HDD. If no DVD can be found, you got the warning. Right, Derrow?
BTW, Derrow, could you add an option to remove this warning? Most of the time, it is useless.
Lupo Silenzioso
3rd December 2004, 13:05
Originally posted by r0lZ
I think IfoEdit is able to work an a particular IFO file stored on disk, and use the real DVD in your DVD drive for the other IFOs and VOBS. This is a feature allowing to preview the DVD without the need to copy all the files to HDD. If no DVD can be found, you got the warning. Right, Derrow?
BTW, Derrow, could you add an option to remove this warning? Most of the time, it is useless.
but i don't have the real dvd in the dvd drive! i have decrypted it on my hd and i'm trying to preview it with ifoedit
r0lZ
3rd December 2004, 13:08
That's why you got the warning. You may put ANY valid DVD in your drive, and you will not see the warning anymore.
jsoto
8th December 2004, 13:22
From 0.97 changelog:
- fixed a bug with VTSM_VOBS Video Attributes
Please look at the figures: same VIDEO_TS.IFO file opened with 0.96 and 0.971. This re-authored DVD has a combination of 720x576 (in VTS_02) 352x288 (VTS 03,04 & 05) and 704x576 (VTS06). In this case 0.96 is showing the right resolution in all VTSs, but 0971 is really wrong. I know MPEG-2 in VCD resolution is not DVD full compliant, but 704x576 is.
http://www.iespana.es/jsoto/images/resolutions096.jpg
http://www.iespana.es/jsoto/images/resolutions097.jpg
jsoto
2COOL
9th December 2004, 02:08
@Derrow
I think IfoEdit's DVD Player should be checked for functionality. More on accepting SPRM compare commands like...
[00 A1 00 85 00 01 00 03] 1 if ( sprm(5:Title number in VTS) == 1 ) then { Goto line 3 }
Anyways, I was doing some beta testing on using the Return (GoUp) button.
Here's my setup. I have a VTS with
TTN 1 (Title 1)
TTN 2 (Title 2)
TTN 3 (dummy)
TTN 4 (dummy)
For TTNs 1 and 2, I have the Return (GoUp) button set up to jump to TTN 3. Here's my pre commands in TTN 3.
********** pre commands:
[00 A1 00 85 00 01 00 03] 1 if ( sprm(5:Title number in VTS) == 1 ) then { Goto line 3 }
[30 03 00 00 00 01 00 00] 2 (JumpVTS_TT) Jump to TTN 1 in this VTS
[30 03 00 00 00 02 00 00] 3 (JumpVTS_TT) Jump to TTN 2 in this VTS
As you can see, I had it set up so when I'm in TTN 1 (Title 1), I'll jump to TTN 2 (Title 2) when I press my Return in IfoEdit's player. If I'm in TTN 2, I should jump to TTN 1. Unfortunately, when I'm in TTN 1 and press my Return button, I just stay in TTN 1 but go back to chapter 1. There's no toggle. It seems Pre Command 1 gets bypassed. :confused:
So I went with plan B. That is to have TTN 1 with a GoUp value of 3 and in TTN 3, I only have one pre command. I decided to get rid of the If-SPRM-then command.
********** pre commands:
[30 03 00 00 00 02 00 00] 1 (JumpVTS_TT) Jump to TTN 2 in this VTS
And for TTN 2, I have a GoUp value of 4 and in TTN 4, I also have one pre command.
********** pre commands:
[30 03 00 00 00 01 00 00] 1 (JumpVTS_TT) Jump to TTN 1 in this VTS
This now flawlessly works when I toggle using the Return button. I have tested both plans with PgcEdit's trace and both are logically acceptable. It's just playing the navigations in IfoEdit, is where I run into problems when I executed the first plan. I tried to test it in PowerDVD XP but it doesn't have a Return (GoUp) button and I also didn't want to chance burning my backup also.
r0lZ
9th December 2004, 10:58
IMHO, your first method cannot work because the SPRM 5 is set to 3 when you enter in TTN 3. The SPRM test is therefore never true.
The SPRM 5 do not change when you jump to a menu domain, but is reinitialized in you jump to another TTN.
The second method is OK, and should work.
2COOL
9th December 2004, 18:55
Originally posted by r0lZ
IMHO, your first method cannot work because the SPRM 6 is set to 3 when you enter in TTN 3. The SPRM test is therefore never true.
The SPRM 6 do not change when you jump to a menu domain, but is reinitialized in you jump to another TTN.:confused: I thought I was doing a typo in my last thread but I was using SPRM 5 instead of SPRM 4 but SPRM 6. Also, I was working only in the Title domain.
r0lZ
9th December 2004, 19:12
I made the typo. (now corrected in my prev post)
Anyway, what I mean is that the TTN number in SPRM 5 is changed to the current TTN number when you enter in a PGC of the title domain. So, you can only check it in a PGC of the menu domain.
2COOL
9th December 2004, 19:32
Originally posted by r0lZ
I made the typo. (now corrected in my prev post)No problem. :)
Anyway, what I mean is that the TTN number in SPRM 5 is changed to the current TTN number when you enter in a PGC of the title domain.OK, I know about this...
So, you can only check it in a PGC of the menu domain. In the menu domain? I traced out my first method with PgcEdit and it analyzed the commands logically like I knew it would. I wasn't in the menu domain and I certainly was watching the SPRMs. I'm a little confused, still my morning, about the only checking part in menu domain part. I can check in title domain too.
r0lZ
9th December 2004, 19:42
You can check any GRPM or SPRM in any domain, but checking the SPRM 5 in TTN 3 is useless, since it will be always 3, because it is set to 3 when the TTN 3 is entered.
2COOL
9th December 2004, 19:49
I'm not at my home computer to confirm this so I'm just going on memory. PGC 3 or TTN3 is a dummy created in PgcEdit. There is no Title associated with it? The only way to prove to you that my first method works in PgcEdit trace is for you to try it on your own. I just didn't understand it last night that PgcEdit trace works as I plan but IfoEdit didn't play it the way it was traced.
r0lZ
9th December 2004, 20:01
Well. In PgcEdit (at least in my actual version), SPRM 5 is set to 0 when entering a dummy PGC is the title domain. But perhaps it's a bug in PgcEdit. I really don't know what to do when this happends. I have to check out with my Sony.
Anyway, you can't rely on this. Don't forget that a dummy PGC in title domain is illegal. You cannot have the guarantee that all players will react the same way.
blueboyec
9th December 2004, 20:28
New to Ifoedit.
When keeping only one angle, do all referance that refer to angles get updated to 1 in this update?
2COOL
9th December 2004, 20:28
Originally posted by r0lZ
Don't forget that a dummy PGC in title domain is illegal.I gave up on this belief and though Ralpgh DeBarge had some discrepancies in his book, he does also state it's doable in the title domain. So to beat a horse to death, I go with what I personally experienced.
You cannot have the guarantee that all players will react the same way. True.
mpucoder
9th December 2004, 21:58
By dummy PGC, do you mean one that does not belong to a title? That is not permitted. But a dummy PGC is one without any programs, just commands. And having a PGC like that belonging to a title is OK.
In any case, checking SPRM 5 only makes sense in the menu domain to find out which title called you.
Edit: or to trip someone up if they reauthor.
2COOL
9th December 2004, 22:44
Here's an example of my 4 PGCs with 3 and 4 created as dummies. PGC 2 was created as a new Play All PGC. All were created in PgcEdit.
Number of VTS_PGCI_SRP 4
End byte of VTS_PGCI_SRP table 3897
VTS_PGC_1: Category mask 129
details:
entry PGC: yes
Title number: 1
VTS_PGC_1: Category 0
VTS_PGC_1: Category Parental ID mask 128
VTS_PGC_1: VTS_PGCI start byte 40
VTS_PGC_2: Category mask 0
details:
entry PGC: no
Title number: 0
VTS_PGC_2: Category 0
VTS_PGC_2: Category Parental ID mask 7467
VTS_PGC_2: VTS_PGCI start byte 1710
VTS_PGC_3: Category mask 1
details:
entry PGC: no
Title number: 1
VTS_PGC_3: Category 0
VTS_PGC_3: Category Parental ID mask 0
VTS_PGC_3: VTS_PGCI start byte 3394
VTS_PGC_4: Category mask 1
details:
entry PGC: no
Title number: 1
VTS_PGC_4: Category 0
VTS_PGC_4: Category Parental ID mask 0
VTS_PGC_4: VTS_PGCI start byte 3646
r0lZ
9th December 2004, 22:51
How about continuing this discussion in the PgcEdit thread?
edit: continued here (http://forum.doom9.org/showthread.php?s=&postid=579593#post579586).
2COOL
10th December 2004, 00:09
Originally posted by mpucoder
By dummy PGC, do you mean one that does not belong to a title? That is not permitted. But a dummy PGC is one without any programs, just commands. And having a PGC like that belonging to a title is OK.
My dummy PGC was a non-entry PGC with a category mask of 1. So it did have a title assigned to it. And yes, it didn't have programs and just pre commands.
In any case, checking SPRM 5 only makes sense in the menu domain to find out which title called you. If I do a pre command jump to another title in the same domain, shouldn't my SPRM be updated after that too? It supposed to and I can see the change in PgcEdit's trace too. Why do I really need to be in the menu domain to really check. Sorry for being persistent here too but with the tools I got, I'm seeing it right before me and not virtually playing it out.
If I'm wrong then I'm blind as a bat. :p Anyways, I've continued my topic to the PgcEdit thread (http://forum.doom9.org/showthread.php?s=&postid=579627#post579627).
jeanl
10th December 2004, 01:52
Originally posted by 2COOL
If I do a pre command jump to another title in the same domain, shouldn't my SPRM be updated after that too? It supposed to and I can see the change in PgcEdit's trace too. Why do I really need to be in the menu domain to really check.
I don't think they're saying you need to be in the menu domain. They're saying it only makes sense in the menu domain, because wherever you are in the title domain, you already know what sprm(5) will be so you don't need to test its value. But you certainly can if you want to!
At least that's what I understand from the above posts.
Jeanl
r0lZ
10th December 2004, 02:07
Exactly.
Sorry, I cannot explain some difficult things with my bad english!
davepyne
10th December 2004, 11:57
"I have a problem with this new version of idoedit.
After doing the first preview of the chapter (by double clicking on it) i canīt preview anymore. And if the chapter is very long it that much time to load."
Me too! oh well, i can still use 0.95 to preview (0.96 freezes when i try to double click on any chapter)
davepyne
10th December 2004, 11:59
it works fine if i selct "cancel" instead of "ok" after viewing preview. weird, but it works!
blueboyec
13th December 2004, 21:16
Derrow or anyone else,
I known IfoEdit can remove angles (keep one angle) but does this updated version correct all referances to angles (have the DVD seam as thought it was never a multy angle move)?
thanks
blutach
14th December 2004, 23:10
@Derrow,
Couple of things I think your aware about - one needs fixing badly the other is really just an annoyance (except to those who don't know about it or how to correct it :)).
1. When splitting episodic disks to 2 DVDs, the 2nd disk is created with dummy PGCs in the titles domain that do not belong to a title. This is supposedly illegal as you know and can cause errors.
2. Cell commands, SCR/seamless bits and still times are not copied correctly when stripping VOB streams - this has been mentioned before and is only an annoyance as it's so easy to correct.
Are these to be fixed soon?
Regards
Derrow
22nd December 2004, 22:26
@blutach
These bugs do sound serious.
It's definatly something that should be fixed quickly.
I will fix it for the next release, but can't promise that it will be finished this year :p
blutach
22nd December 2004, 23:05
Thanks Derrow.
MXHNY
Video Dude
16th January 2005, 19:33
Originally posted by blutach
2. Cell commands, SCR/seamless bits and still times are not copied correctly when stripping VOB streams - this has been mentioned before and is only an annoyance as it's so easy to correct.
That sounds like that can be quite a bug. Thanks Derrow for offering to fix it in the next version.
blutach
20th January 2005, 08:36
@derrow
Re: Cells commands, still times etc.
This is quickly becoming an issue, especially with PGCs with several cell commands.
Just wondering if you have a view as to when the next release might be?
Regards
Video Dude
26th January 2005, 22:32
Originally posted by blutach
2. Cell commands, SCR/seamless bits and still times are not copied correctly when stripping VOB streams - this has been mentioned before and is only an annoyance as it's so easy to correct.
After a few tests, it seems that Cell Commands did copy correctly when stripping VOB streams in 0.971.
SCR seems not to be copied like blutach mentioned.
Can anyone else confirm the still times problem?
blutach
26th January 2005, 22:39
@videodude
The commands are there but look at the table of cell commands (easiest to see in PgcEdit) but in IfoEdit look at VTS_PGCITI_PGC## and look at PGC program map and the cell command number (eg 0x00129) vs that of the original. It isn't bring over the cell command number, rendering the cell command useless.
Regards
Video Dude
26th January 2005, 23:01
I thought you meant the actual cell comands, but now I see what you are talking about in the table.
blutach
27th January 2005, 04:20
Yeah, it's a bummer. But as long as ppl know abt it, they can fix it. Otherwise, they are just left wondering what they did wrong :)
I'm sure Derrow will get round to it soon.
Regards
hagge
9th February 2005, 10:29
Sorry to bring up this thread again, but I think I found an error in IfoEdit that is still there in 0.97.1:
When defining the NextPgc entries and then using command "LinkNextPgc" everything works very well. But doing the same with the PrevPgc entries and then using command "LinkPrevPgc" always produces navigation errors in IfoEdit.
The resulting DVD works fine in PgcEdit, PowerDVD, and also on all standalone DVD players I've tested it on, so I guess this is an error in IfoEdit.
Regards,
Hagge
mpucoder
9th February 2005, 16:08
That would be like blaming a compiler for making a program that crashed. In most cases (first pgc in a menu or title) setting the prev pgc link is in itself a navigation error.
r0lZ
9th February 2005, 16:25
hagge dis not say that he used the Prev Link in the first PGC of a menu or title.
Also, setting the Prev Link in an entry PGC works well if it is pointing to itself. This is the trick to allow the usage of the Prev button to go back to the beginning of chapter 1.
Also, I think it is perfectly legal to set the Prev PGC in an entry menu PGC to go back to another menu. Works well with all players I have tested so far.
Seems to work also in title domain, although in this case, it is normally prohibited.
What's strange with what hagge described, is that IfoEdit do use the DirectX filters to play the DVD. So, if it works with the installed DVD player, it should work with IfoEdit too.
But I know there are some problems (at least in old versions) with the << and >> buttons in IfoEdit's preview. Sometimes, the buttons are not working, even if there are no PUOs. I think this occur when a chapter or title has been selected in the drop down lists. Still wondering why. :confused:
hagge
9th February 2005, 17:43
Originally posted by r0lZ
What's strange with what hagge described, is that IfoEdit do use the DirectX filters to play the DVD. So, if it works with the installed DVD player, it should work with IfoEdit too.
Hmm, well, that's interesting. I'm using WinME, so there might be an old version of some DirectX filter involved. I have to check this.
I can elaborate what I want to do: The chapter menu of my DVD consists of several screens where each screen leads to a couple of chapters. For example screen 1 shows chapters 1..5, screen 2 chapters 6..10, etc.
On each menu screen there is also a button to go back to the previous screen and one to go forward to the next screen. To do this I defined PrevPgc and NextPgc in all the menu screens and then use the LinkPrevPgc and LinkNextPgc commands in the navigation packs for the appropriate buttons in the menu VOB. As I also have to set a different button for highlighting in the same command, I can't use the LinkPgcN command.
And here the problem arises when IfoEdit tries to jump to the PrevPgc. I hope this is clear enough.
BTW, is there an easier way of achieving what I want?
Regards,
Hagge
r0lZ
9th February 2005, 18:52
As far as I know, your method should work.
However, I have never used LinkPrev/NextPGC in a menu button. Usually, I prefer to use LinkTailPGC in all buttons, and test the highlighted button in the post commands. For each button, I add the action to be archived here. It's more legible (you don't need to refer to the button commands to understand what's happening) and you can use PgcEdit to edit all actions. I really don't like to modify the commands in the buttons with MenuEdit.
Example:1 Set gprm(15) =(mov) sprm(8:Highlighted button number)
2 Set gprm(15) /=(div) 1024
3 if ( gprm(15) != 1 ) then { Goto line 5 }
4 [action for button 1]
5 NOP
6 if ( gprm(15) != 2 ) then { Goto line 8 }
7 [action for button 2]
8 NOP
9 ... It's a little bit more difficult to do if your PGC is a motion menu, because it will go to the post commands when the menu has finished playing, even if no button was selected. In this case, you may set a LinkPGCN command in the buttons, and use the above logic in the pre-commands of that dummy PGC.
hagge
9th February 2005, 19:40
Well, my approach was to have as little changes as possible from what my authoring program already creates. (It's Magix Video Deluxe; yes I know, not a very good choice for authoring, but hey, it's one I already had. I'm just using it for the menus, the main muxing is done with IfoEdit.) This authoring program automatically builds the menu screens, but always highlights the first button in every menu. Then it's easy to use a LinkPGCN to the next or previous screen and there simply highlight button 1024 in the Prev section, and that's exactly what the program does.
However I want to be able to scroll through the chapters with the left and right buttons, making the forward/back buttons auto-activate. So when I go back to the previous screen, the last chapter button should be highlighted there, and when I go forward to the next screen, the first chapter button should be highlighted there.
This new behaviour requires to change the button commands of the forward and back buttons anyway, so whether I use LinkPrev/NextPGC or LinkTailPGC is just a matter of taste. I think using LinkPrev/NextPGC is even a little easier, as then my PGCs are completely empty -- not one command is required, everything is done in the button commands.
Back-Button: LinkPrevPGC, button 5 (5120)
Forward-Button: LinkNextPGC, button 1 (1024)
I once used the GoUpPGC instead of the PrevPGC and there everything worked fine, even in IfoEdit. But as I understand GoUpPGC has a meaning with the return key, so I wanted to avoid this. BTW, do PrevPGC and NextPGC also work with the Prev/Next skip buttons? I've never tested this, but if yes, this would be another advantage of my approach as I also could switch screens with these buttons then.
Hagge
jeanl
9th February 2005, 21:02
Originally posted by r0lZ
What's strange with what hagge described, is that IfoEdit do use the DirectX filters to play the DVD. So, if it works with the installed DVD player, it should work with IfoEdit too.
r0lZ, there are two different things. The mpeg decoder (which is not included in direct X, and therefore has to be provided by a third party, like an installed DVD player), and the DVD navigation engine. in hagge's case, I'm sure IFOEdit uses the standard (crappy) direct-X navigation engine. However, his soft DVD player most likely does not. PowerDVD for example, does not use the direct-X navigation "filter"...
Just to clarify...
Jeanl
blutach
9th February 2005, 22:32
@hagge
These invisible buttons are useful and fun :)
But I don't use link PrevPGC - just link LinkPGCN with the number of the PGC stated. That way, you will never get into trouble.
Remember, also, on many occasions, the chapter menu is all contained in one PGC and you will be using LinkPGN (and optionally HL button#) as opposed to LinkPGCN.
Regards
r0lZ
10th February 2005, 02:25
Originally posted by hagge
BTW, do PrevPGC and NextPGC also work with the Prev/Next skip buttons? I've never tested this, but if yes, this would be another advantage of my approach as I also could switch screens with these buttons then. Yes.
hagge
10th February 2005, 09:40
Hi blutach,
Originally posted by blutach
These invisible buttons are useful and fun :)
Well, in may case they are not invisible. They just activate automatically when I move focus to them. This allows to scroll through let's say 30 chapter buttons on 6 menu screens with just the right or left key and without having to press Enter anywhere.
But I don't use link PrevPGC - just link LinkPGCN with the number of the PGC stated. That way, you will never get into trouble.
And how do you solve the problem of the highlighted button in the new PGC? Depending on where I came from, the first or the last chapter button should be highlighted. This requires either highlighting in the link command to this PGC or some testable value telling the origin. OK, I can set a GPRM in the LinkPGCN command and test it in the next menu, but why? Is it really a known problem to use the PrevPGC/NextPGC entries?
Using PGCN also makes relocation more difficult as I have to give a fix number in the command. Also it is a different number in each button command. When using PrevPGC/NextPGC the button command itself is always the same, making editing easier. Try changing button commands in VobEdit by entering the hex values, you easily skip a number if the commands aren't identical.
It's not that I want to dismiss your advices, I just can't see the advantage and want to know why I should not use PrevPGC/NextPGC.
Remember, also, on many occasions, the chapter menu is all contained in one PGC and you will be using LinkPGN (and optionally HL button#) as opposed to LinkPGCN.
Right. This depends on the authoring program. In my case, I have a seperate PGC for every menu screen. So I'm dependant on the PGC commands.
Regards,
Hagge
blutach
10th February 2005, 10:13
Howdy hagge
Well, you can make them invisible by putting them anywhere on the screen as a 0 x 0 pixel button. mpucoder gave another method to make them invisible using the various layer colours.
As far as highlighting a button in the next PGCN, you could use for example:[56 04 00 00 04 00 00 05] 2 (SetHL_BTN) Set Highlighted Button =(mov) 1024 (button 1) ; LinkPGCN PGC 5 to set button 1 in PGCN 5.
Typically, you see left and right buttons for each menu selection button that's there. So if you've got, for example:
Button 1 Button 2
Button 3 Button 4 then there would be buttons to the left of 1 and 3 and to the right of 2 and 4, and you could highlight whatever buttons you like depending on where you came from. But, I'm sure you know this.
But, ultimately, it's each to his own. I'm not "poopoo'ing" your methods - far from it. Just making an alternative suggestion. And, I will certainly try your idea.
Regards
r0lZ
10th February 2005, 11:02
Originally posted by blutach
As far as highlighting a button in the next PGCN, you could use for example:[56 04 00 00 04 00 00 05] (SetHL_BTN) Set Highlighted Button =(mov) 1024 (button 1) ; LinkPGCN PGC 5to set button 1 in PGCN 5. That's right. It's the best solution.
I have verified the behavior of the LinkPrev/NextPGC commands when used in a button. Seems that doesn't work as expected. Maybe it's illegal to use these commands in menu buttons? I must still do a test on my Sony to confirm.
Maybe there is a bug in the PgcEdit Trace mode...
r0lZ
10th February 2005, 11:42
OK. Tested on my Sony.
LinkPrevPGC and LinkNextPGC used in buttons are working as expected.
The LinkPrevPGC not allowed by IfoEdit is really a bug in its navigation engine.
PgcEdit's trace is correct.
hagge
10th February 2005, 12:34
Originally posted by blutach
As far as highlighting a button in the next PGCN, you could use for example:[56 04 00 00 04 00 00 05] 2 (SetHL_BTN) Set Highlighted Button =(mov) 1024 (button 1) ; LinkPGCN PGC 5 to set button 1 in PGCN 5.
OK, I see. It seems I've overlooked this command. I always searched in PgcEdit in the "By Type -> LinkTo" section and there it is possible to use Highlight Button only in combination with LinkPrevPGC/LinkNextPGC, but not with LinkPGCN. The idea that setting a register also may jump somewhere is not immediately obvious.
Or at least I always thought that these similar combinations lead to the same command code anyway, independant in which window they were assembled ("Link To" or "Set SRPM"). But now I see that for example the two commands
[20 01 00 00 00 00 04 0A] 1 LinkNextPGC, button 1 (1024)
[56 01 00 00 04 00 00 0A] 2 (SetHL_BTN) Set Highlighted Button =(mov) 1024 (button 1) ; LinkNextPGC
have a completely different code, even if they do exactly the same. Thanks for the hint. You live and learn.
Regards,
Hagge
jarthel
15th February 2005, 11:42
Originally posted by Derrow
- fixed: In VOB Extras, the 'Remove Angle' option was always greyed out under XP.
www.ifoedit.com
using winxp and remove angles is grayed out. I am using version 0.971. It seems only version 0.95 has a working "remove angles".
Video Dude
21st February 2005, 20:00
Originally posted by blutach
Couple of things I think your aware about - one needs fixing badly the other is really just an annoyance (except to those who don't know about it or how to correct it :)).
1. When splitting episodic disks to 2 DVDs, the 2nd disk is created with dummy PGCs in the titles domain that do not belong to a title. This is supposedly illegal as you know and can cause errors.
2. Cell commands, SCR/seamless bits and still times are not copied correctly when stripping VOB streams - this has been mentioned before and is only an annoyance as it's so easy to correct.
The commands are there but look at the table of cell commands (easiest to see in PgcEdit) but in IfoEdit look at VTS_PGCITI_PGC## and look at PGC program map and the cell command number (eg 0x00129) vs that of the original. It isn't bring over the cell command number, rendering the cell command useless.
I just wanted to bump this bug report to the last page of the thread so it does not get lost.
jarthel
28th April 2005, 17:31
Originally posted by Video Dude
I just wanted to bump this bug report to the last page of the thread so it does not get lost.
what he said
blutach
29th April 2005, 14:06
I don't think it's much use in doing this gents, and it's probably against forum rules (though, that's for mpucoder to decide).
If Derrow wanted to continue IfoEdit development, he would. We may as well leave him be.
Regards
Bro
30th April 2005, 09:20
Hi
I understand development of ifoedit has stopped though I still hope someone can answer me on this.
I checked the VTS_01_0.IFO of forrest gump and I find that ifoedit reports.
Coding mode AC3
Channels 2
Sample Rate 48Kbps
Quantization/DRC DRC (dynamic range control)
When I check http://dvd.sourceforge.net/dvdinfo/ifo.html it says at the Audio Attributes:
Coding mode
0 AC3 1 ??? 2 Mpeg-1 3 Mpeg-2ext
4 LPCM 5 ??? 6 DTS 7 ???Quantization/DRC
If Coding mode=2,3
0 = No DRC
1 = DRC
If Coding mode=4
0 = 16bps 1 = 20bps 2 = 24bps, (DRC = dynamic range control)
As I read it, DRC can only occur with coding mode 2,3 and 4.
What I don't understand is how ifoedit can report DRC when it reports AC3 wich is coding mode 0.
Is ifoedit or dvd.sourceforge.net wrong or is there something I don't understand?
mpucoder
30th April 2005, 15:43
I think it's finally time to take action against that sourceforge project. The page you are looking at is from my website, but years ago. I gave them permission to archive the pages, meaning to store them in a manner that was not immediately accessable as a web page. And I have since contacted them about their decision to make the pages browser accessable, and got nothing in return except some open-source rhetoric. As it stands their permission to use those pages was revoked almost 2 years ago by the copyright holder - me.
OK, so I let that pass, afterall the information is old and slightly inaccurate. People who want the truth know to come to my website. But this really bothers me because they have altered the page in a way that makes it inaccurate.
AC3 is always DRC, and those bits should always reflect that.
Hi
Is there anything more than just the correct ifo structure availlable on your site?
I don't like the idea of having to pay to get info though coughing up 5$ should be doable...
While I'm at it...are ifo files copy protected or can they always be viewed directly from from the dvd with a hex editor?
Thanks
Originally posted by Bro
While I'm at it...are ifo files copy protectedNo
or can they always be viewed directly from from the dvd with a hex editor? Yes. If you want to view the readable commands of the IFOs, you can also use IfoEdit.
Older versions of PgcEdit, without menu VOB scanning, could also do it. At the moment, I don't know which version they were though. The current version of PgcEdit doesn't have an option setting to turn it off.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.