DVD Authoring Tools

On Friday 13 April 2007, you wrote:
> On Fri, Apr 13, 2007 at 03:59:07PM +0100, Anne Wilson wrote:
> > For some time I have been using mjpegtools and dvdauthor to turn my Hi8
> > tapes into DVDs.  Up to now I have used only a simple format, of one
> > titleset with several chapters.  Now I want to create a set of DVDs, each
> > with two or three titlesets and multiple chapters.  I've printed out man
> > pages and tutorials, but I'm still struggling.
> >
> > For the first titleset I have created a silent airport.mpg and a
> > transparent airport.png with the outlines of the buttons.  My airport.xml
> > looks like this -
> >
> > <subpictures>
> > 	<stream>
> > 		<spu>
>
>   		<spu
>
> > 			force="yes"
> > 			start="00:00:00:00"
> > 			image="airport.jpg"
> > 			highlight="airport_h.png"
> > 			autooutline="infer"
> > 			outlinewidth="6"
> > 			autoorder="rows">
> > 		</spu>
> > 	</stream>
> > </subpictures>
>
> Change as suggested and will work.
>
> Giacomo

Thanks for replying, Giacomo.  Silly mistake.

On running the amended script, first it complained that airport.jpg isn't 
a .png, so I created airport.png and changed the line in the xml.  Now it 
says that

ERR: PNG airport.png is too big: 768x576

This is the size of all my mpg files.  That's really confused me :-(

Anne

On Fri, Apr 13, 2007 at 04:52:34PM +0100, Anne Wilson wrote:
> On Friday 13 April 2007, you wrote:
> > On Fri, Apr 13, 2007 at 03:59:07PM +0100, Anne Wilson wrote:
> > > For some time I have been using mjpegtools and dvdauthor to turn my Hi8
> > > tapes into DVDs.  Up to now I have used only a simple format, of one
> > > titleset with several chapters.  Now I want to create a set of DVDs, each
> > > with two or three titlesets and multiple chapters.  I've printed out man
> > > pages and tutorials, but I'm still struggling.
> > >
> > > For the first titleset I have created a silent airport.mpg and a
> > > transparent airport.png with the outlines of the buttons.  My airport.xml
> > > looks like this -
> > >
> > > <subpictures>
> > > 	<stream>
> > > 		<spu>
> >
> >   		<spu
> >
> > > 			force="yes"
> > > 			start="00:00:00:00"
> > > 			image="airport.jpg"
> > > 			highlight="airport_h.png"
> > > 			autooutline="infer"
> > > 			outlinewidth="6"
> > > 			autoorder="rows">
> > > 		</spu>
> > > 	</stream>
> > > </subpictures>
> >
> > Change as suggested and will work.
> >
> > Giacomo
> 
> Thanks for replying, Giacomo.  Silly mistake.
> 
> On running the amended script, first it complained that airport.jpg isn't 
> a .png, so I created airport.png and changed the line in the xml.  Now it 
> says that
> 
> ERR: PNG airport.png is too big: 768x576

The maximum resolution allowed for a DVD is 720x576.
You have to rescale the image to that size.

> This is the size of all my mpg files.  That's really confused me :-(
>
Probably not. The size should be 720x576 with aspect ratio 2 (4/3)
the player will rescale the video automaically to 768x576.

Giacomo

On Friday 13 April 2007, Giacomo Comes wrote:
> On Fri, Apr 13, 2007 at 04:52:34PM +0100, Anne Wilson wrote:
> > On Friday 13 April 2007, you wrote:
> > > On Fri, Apr 13, 2007 at 03:59:07PM +0100, Anne Wilson wrote:
> > > > For some time I have been using mjpegtools and dvdauthor to turn my
> > > > Hi8 tapes into DVDs.  Up to now I have used only a simple format, of
> > > > one titleset with several chapters.  Now I want to create a set of
> > > > DVDs, each with two or three titlesets and multiple chapters.  I've
> > > > printed out man pages and tutorials, but I'm still struggling.
> > > >
> > > > For the first titleset I have created a silent airport.mpg and a
> > > > transparent airport.png with the outlines of the buttons.  My
> > > > airport.xml looks like this -
> > > >
> > > > <subpictures>
> > > > 	<stream>
> > > > 		<spu>
> > >
> > >   		<spu
> > >
> > > > 			force="yes"
> > > > 			start="00:00:00:00"
> > > > 			image="airport.jpg"
> > > > 			highlight="airport_h.png"
> > > > 			autooutline="infer"
> > > > 			outlinewidth="6"
> > > > 			autoorder="rows">
> > > > 		</spu>
> > > > 	</stream>
> > > > </subpictures>
> > >
> > > Change as suggested and will work.
> > >
> > > Giacomo
> >
> > Thanks for replying, Giacomo.  Silly mistake.
> >
> > On running the amended script, first it complained that airport.jpg isn't
> > a .png, so I created airport.png and changed the line in the xml.  Now it
> > says that
> >
> > ERR: PNG airport.png is too big: 768x576
>
> The maximum resolution allowed for a DVD is 720x576.
> You have to rescale the image to that size.
>
> > This is the size of all my mpg files.  That's really confused me :-(
>
> Probably not. The size should be 720x576 with aspect ratio 2 (4/3)
> the player will rescale the video automaically to 768x576.
>
Duh!  Of course any I make for titles usually get put through yuvscaler along 
with the main mpegs.  Thanks for the reminder.  I'll let you know what 
happens.

Anne

On Friday 13 April 2007, Anne Wilson wrote:
> On Friday 13 April 2007, Giacomo Comes wrote:
> > > On running the amended script, first it complained that airport.jpg
> > > isn't a .png, so I created airport.png and changed the line in the xml.
> > >  Now it says that
> > >
> > > ERR: PNG airport.png is too big: 768x576
> >
> > The maximum resolution allowed for a DVD is 720x576.
> > You have to rescale the image to that size.
> >
> > > This is the size of all my mpg files.  That's really confused me :-(
> >
> > Probably not. The size should be 720x576 with aspect ratio 2 (4/3)
> > the player will rescale the video automaically to 768x576.
>
> Duh!  Of course any I make for titles usually get put through yuvscaler
> along with the main mpegs.  Thanks for the reminder.  I'll let you know
> what happens.
>
Still haven't got it right :-( 

spumux airport.xml < Airport.mpg > airport.mpg
DVDAuthor::spumux, version 0.6.14.
Build options: gnugetopt iconv freetype fribidi
Send bugs to <dvdauthor-users@...>

INFO: Locale=en_US.UTF-8
INFO: Converting filenames to UTF-8
INFO: PNG had 4 colors
INFO: PNG had 2 colors
INFO: Constructing blank sel
INFO: Autodetect 0 = 125x74-232x110
INFO: Autodetect 1 = 467x72-605x112
INFO: Pickbuttongroups, success with 1 groups, useimg=0
spumux: subgen-image.c:788: imgfix: Assertion `useimg' failed.
Aborted

What does this mean, please?

Anne

On Fri, 2007-04-13 at 18:52 +0100, Anne Wilson wrote:
<snip>
> Still haven't got it right :-(=20
>=20
> spumux airport.xml < Airport.mpg > airport.mpg
> DVDAuthor::spumux, version 0.6.14.
> Build options: gnugetopt iconv freetype fribidi
> Send bugs to <dvdauthor-users@...>
>=20
> INFO: Locale=3Den_US.UTF-8
> INFO: Converting filenames to UTF-8
> INFO: PNG had 4 colors
> INFO: PNG had 2 colors
> INFO: Constructing blank sel
> INFO: Autodetect 0 =3D 125x74-232x110
> INFO: Autodetect 1 =3D 467x72-605x112
> INFO: Pickbuttongroups, success with 1 groups, useimg=3D0
> spumux: subgen-image.c:788: imgfix: Assertion `useimg' failed.
> Aborted
>=20
> What does this mean, please?

It means there are too many combinations of colours in the subpictures
(which really shouldn't be reported through an assertion failure, but oh
well).

Each group of subpictures has a 4-colour (plus transparency) palette for
each of the normal, highlighted and selcted states.  Changes between
these states are made purely by switching the palette, not by changing
the bitmap.  spumux tries to encode the changes between bitmaps using
4-colour palettes, but unless you bear in mind this limitation it will
usually fail.

One way to work around this limitation is to encode button images for
one state into the background and then make the subpictures transparent
in that state.

Ben.

--=20
Ben Hutchings
Power corrupts.  Absolute power is kind of neat.
                           - John Lehman, Secretary of the US Navy 1981-198=
7

On 4/13/07, Ben Hutchings <ben@...> wrote:
> Each group of subpictures has a 4-colour (plus transparency) palette for
> each of the normal, highlighted and selcted states.  Changes between
> these states are made purely by switching the palette, not by changing
> the bitmap.  spumux tries to encode the changes between bitmaps using
> 4-colour palettes, but unless you bear in mind this limitation it will
> usually fail.

And it's the number of colors **in the palette** that count, not the
absolute number of colors. This is a great concrete example:
http://www.floatinginspace.za.org/spumux/spumux.html

Joe

On Saturday 14 April 2007, Joe Friedrichsen wrote:
> On 4/13/07, Ben Hutchings <ben@...> wrote:
> > Each group of subpictures has a 4-colour (plus transparency) palette for
> > each of the normal, highlighted and selcted states.  Changes between
> > these states are made purely by switching the palette, not by changing
> > the bitmap.  spumux tries to encode the changes between bitmaps using
> > 4-colour palettes, but unless you bear in mind this limitation it will
> > usually fail.
>
> And it's the number of colors **in the palette** that count, not the
> absolute number of colors. This is a great concrete example:
> http://www.floatinginspace.za.org/spumux/spumux.html
>
I'd printed out that article, but put it aside as a later study, since I 
thought I was following a simpler, first-steps tutorial :-)

Right - a misunderstanding, then.  The highlight layer only contains 1 colour 
plus transparency, but it's a colour not in the four-colour background.  Yes?

I'll try picking up the brightest colour from the background, and see if that 
can be used on the highlight instead.

No, failed again.

INFO: PNG had 3 colors
INFO: PNG had 2 colors

The second one is one colour plus transparent.  The first one, with 3 colours, 
as one colour in common with the second one, so I thought that would be 
treated as only four colours in all.  It mustn't work like that.

Does that mean that I should forget the idea of using a snapshot as the 
background?  I don't quite see how I can get anything decent out of only two 
colours.

I downloaded the gimp button-plugin and followed that exactly.  That failed as 
well.  When I left the background image as a separate layer I got

INFO: Skipped 2034 bytes of garbage
WARN: Incorrect pack header
INFO: 0 subtitles added, 0 subtitles skipped, stream: 32, offset: -0.00

Statistics:
- Processed 0 subtitles.
- The longest display line had -1 characters.
- The maximum number of displayed lines was 0.
- The normal display height of the font arial.ttf was 0.
- The bottom display height of the font arial.ttf was 0.
- The biggest subtitle box had 0 bytes.

Looking at the xml file that it had produced, I had thought it may end up with 
no background, and just the buttons.  I went back to the .xcf file and merged 
the image_bl and background buttons and tried again.  This time I got

INFO: Locale=en_US.UTF-8
INFO: Converting filenames to UTF-8
INFO: PNG had 3 colors
INFO: PNG had 2 colors
INFO: PNG had 2 colors
INFO: Pickbuttongroups, success with 1 groups, useimg=0
spumux: subgen-image.c:788: imgfix: Assertion `useimg' failed.
Aborted

Anne

On 4/14/07, Anne Wilson <cannewilson@...> wrote:
> On Saturday 14 April 2007, Joe Friedrichsen wrote:
> > On 4/13/07, Ben Hutchings <ben@...> wrote:
> > > Each group of subpictures has a 4-colour (plus transparency) palette for
> > > each of the normal, highlighted and selcted states.  Changes between
> > > these states are made purely by switching the palette, not by changing
> > > the bitmap.  spumux tries to encode the changes between bitmaps using
> > > 4-colour palettes, but unless you bear in mind this limitation it will
> > > usually fail.
> >
> > And it's the number of colors **in the palette** that count, not the
> > absolute number of colors. This is a great concrete example:
> > http://www.floatinginspace.za.org/spumux/spumux.html
>
> I'd printed out that article, but put it aside as a later study, since I
> thought I was following a simpler, first-steps tutorial :-)

I think it this case, it would be good to give it a review :-) Which
tutorial are you following?

> Right - a misunderstanding, then.  The highlight layer only contains 1 colour
> plus transparency, but it's a colour not in the four-colour background.  Yes?

Generally not, as that can lead to more than 4 colours in the palette.

> The second one is one colour plus transparent.  The first one, with 3 colours,
> as one colour in common with the second one, so I thought that would be
> treated as only four colours in all.  It mustn't work like that.

It can, but as the link I provided demonstrates, four colors can turn
into many more depending on the button layout.

> Does that mean that I should forget the idea of using a snapshot as the
> background?  I don't quite see how I can get anything decent out of only two
> colours.

A typical work flow is:
  * Make an mpeg with your favorite picture (ppmtoy4m and mpeg2enc for
video, ffmpeg or mp2enc for audio, mplex to combine them). This will
be your background, and since it's in the video stream, it doesn't
have to conform to spumux's 4-colour limit.
  * Make your spumux button overlays (highlight and select). You only
need to provide the colour of the highlight/select mask, since
everything else is in the background mpeg. This usually means that
spumux will tell you 'PNG had 2 colors' -- one for the mask and one
for the alpha/transparency.
  * 'Mux them in :-)

Joe

On Saturday 14 April 2007, Joe Friedrichsen wrote:
> On 4/14/07, Anne Wilson <cannewilson@...> wrote:
> > I'd printed out that article, but put it aside as a later study, since I
> > thought I was following a simpler, first-steps tutorial :-)
>
> I think it this case, it would be good to give it a review :-) Which
> tutorial are you following?
>
I was originally following 
http://en.dahnielson.com/2003/12/dvd-author-primer.html

>   * Make an mpeg with your favorite picture (ppmtoy4m and mpeg2enc for
> video, ffmpeg or mp2enc for audio, mplex to combine them). This will
> be your background, and since it's in the video stream, it doesn't
> have to conform to spumux's 4-colour limit.
>   * Make your spumux button overlays (highlight and select). You only
> need to provide the colour of the highlight/select mask, since
> everything else is in the background mpeg. This usually means that
> spumux will tell you 'PNG had 2 colors' -- one for the mask and one
> for the alpha/transparency.
>   * 'Mux them in :-)
>
This is where I originally started from.  I'm used to creating mpgs with 
mjpegtools.  However, I found that I wasn't sure how to make the masks.  
Perhaps I could do it that way now.  I'm beginning to get a bit more 
understanding of what's needed.

In the meantime, I had downloaded the gimp plugin for handling buttons.  There 
is an html tutorial with that, and that's the one I was following earlier 
today.  That plugin creates the layers and the ...mux.xml file.  Then spumux 
is called using the xml as the first parameter, like this

spumux airport_spu.xml < Airport.mpg > airport.mpg

When creating the masks I was careful to use colours that were already present 
in the background picture.  This is what the output said about that:

INFO: PNG had 3 colors
INFO: PNG had 2 colors
INFO: PNG had 2 colors

In both of the last two cases, there was one colour from the first palette and 
transparency.  That seemed to fit with what I'd understood.  However, it went 
on to say

INFO: Pickbuttongroups, success with 1 groups, useimg=0
spumux: subgen-image.c:788: imgfix: Assertion `useimg' failed.
Aborted

which sounds like too many colours, still.

I just don't understand how to limit the colours when the background is an 
image.  Any less than 3 colours and the image makes no sense at all.I've only 
used colours from that palette for the two masks.

Sorry if I'm being particularly thick on this :-)  but I really do want to 
understand.

Anne

On 4/14/07, Anne Wilson <cannewilson@...> wrote:
> When creating the masks I was careful to use colours that were already present
> in the background picture.  This is what the output said about that:

I'm assuming here that by 'background picture' you're referring to the
mpeg you made from an image. If that's the case, the colours you
choose for the button overlay masks are entirely independent of the
the mpeg video -- you have no obligation to re-use colours from the
mpeg in the overlays.

> INFO: PNG had 3 colors
> INFO: PNG had 2 colors
> INFO: PNG had 2 colors
>
> In both of the last two cases, there was one colour from the first palette and
> transparency.  That seemed to fit with what I'd understood.  However, it went
> on to say
>
> INFO: Pickbuttongroups, success with 1 groups, useimg=0
> spumux: subgen-image.c:788: imgfix: Assertion `useimg' failed.
> Aborted

This sounds like the xml file specifies image, highlight, and select
overlays. I have never had success using all three overlays. Highlight
and select overlays are generally enough, since highlight shows where
the cursor is and (usually) select is just a copy of highlight, but
with a different colour, so that when the viewer hits 'enter', the
button on screen changes colour and shows which was selected.

> I just don't understand how to limit the colours when the background is an
> image.  Any less than 3 colours and the image makes no sense at all.I've only
> used colours from that palette for the two masks.

Again, if the background image is in the mpeg, you are not limited by
the number of colours. Just use a select and highlight overlay.

You can see my struggles and successes in a few places: this list
describes the situation --
http://sourceforge.net/mailarchive/forum.php?thread_name=440C338D.6000209%40gmail.com&forum_name=dvdauthor-users
. The failures -- http://mac.north.googlepages.com/spumux . The
successes -- http://pengi.films.googlepages.com/shizuocha-pp_menus

Joe

On Saturday 14 April 2007, Joe Friedrichsen wrote:
> On 4/14/07, Anne Wilson <cannewilson@...> wrote:
> > When creating the masks I was careful to use colours that were already
> > present in the background picture.  This is what the output said about
> > that:
>
> I'm assuming here that by 'background picture' you're referring to the
> mpeg you made from an image. If that's the case, the colours you
> choose for the button overlay masks are entirely independent of the
> the mpeg video -- you have no obligation to re-use colours from the
> mpeg in the overlays.
>
> > INFO: PNG had 3 colors
> > INFO: PNG had 2 colors
> > INFO: PNG had 2 colors
> >
> > In both of the last two cases, there was one colour from the first
> > palette and transparency.  That seemed to fit with what I'd understood. 
> > However, it went on to say
> >
> > INFO: Pickbuttongroups, success with 1 groups, useimg=0
> > spumux: subgen-image.c:788: imgfix: Assertion `useimg' failed.
> > Aborted
>
> This sounds like the xml file specifies image, highlight, and select
> overlays. I have never had success using all three overlays. Highlight
> and select overlays are generally enough, since highlight shows where
> the cursor is and (usually) select is just a copy of highlight, but
> with a different colour, so that when the viewer hits 'enter', the
> button on screen changes colour and shows which was selected.
>
This is the xlm file generated by the gimp plugin:

<subpictures>
  <stream>
    <spu
       force="yes" 
       start="00:00:00.00" 
       image="airport_image_bl.png"
       highlight="airport_highlight_bl.png"
       select="airport_select_bl.png"
      >
        <button name="Menu" x0="530" y0="88" x1="623" y1="140"/>
        <button name="Shanghai" x0="105" y0="88" x1="228" y1="140"/>
    </spu>
  </stream>
</subpictures>

This first titleset is very short - just one chapter, then the return menu.  
All the other titlesets are longer, but I thought I'd cut my teeth on a 
simple one :-)

> > I just don't understand how to limit the colours when the background is
> > an image.  Any less than 3 colours and the image makes no sense at
> > all.I've only used colours from that palette for the two masks.
>
> Again, if the background image is in the mpeg, you are not limited by
> the number of colours. Just use a select and highlight overlay.
>
OK - I have the various png images and a suitable mpeg.  Now how do I call 
spumux to combine them?  And do I take out the background-image line from the 
xml?

> You can see my struggles and successes in a few places: this list
> describes the situation --
> http://sourceforge.net/mailarchive/forum.php?thread_name=440C338D.6000209%4
>0gmail.com&forum_name=dvdauthor-users . The failures --
> http://mac.north.googlepages.com/spumux . The
> successes -- http://pengi.films.googlepages.com/shizuocha-pp_menus
>
It's getting late now, so I've printed them out, to study in the morning.  
Time zones are not my friend when I'm asking for help :-)

Family calls, so I'll dodge out for an hour or so, but I'll check back in case 
you need any more info to answer my questions.

Thanks

Anne

On 4/14/07, Anne Wilson <cannewilson@...> wrote:
> On Saturday 14 April 2007, Joe Friedrichsen wrote:
> > This sounds like the xml file specifies image, highlight, and select
> > overlays. I have never had success using all three overlays. Highlight
> > and select overlays are generally enough, since highlight shows where
> > the cursor is and (usually) select is just a copy of highlight, but
> > with a different colour, so that when the viewer hits 'enter', the
> > button on screen changes colour and shows which was selected.
> >
> This is the xlm file generated by the gimp plugin:
>
> <subpictures>
>   <stream>
>     <spu
>        force="yes"
>        start="00:00:00.00"
>        image="airport_image_bl.png"
>        highlight="airport_highlight_bl.png"
>        select="airport_select_bl.png"
>       >
>         <button name="Menu" x0="530" y0="88" x1="623" y1="140"/>
>         <button name="Shanghai" x0="105" y0="88" x1="228" y1="140"/>
>     </spu>
>   </stream>
> </subpictures>

Yes, so the GIMP plug-in is using all three overlays (img, hl, sel),
something I haven't figured out how to do yet.

> > > I just don't understand how to limit the colours when the background is
> > > an image.  Any less than 3 colours and the image makes no sense at
> > > all.I've only used colours from that palette for the two masks.
> >
> > Again, if the background image is in the mpeg, you are not limited by
> > the number of colours. Just use a select and highlight overlay.
> >
> OK - I have the various png images and a suitable mpeg.  Now how do I call
> spumux to combine them?  And do I take out the background-image line from the
> xml?

Great. So let's say that you've created your mpeg... You've done something like

ffmpeg -f s16le -i /dev/zero -ac 2 -ar 48000 -ab 224k -t 4 -acodec ac3
-y "/tmp/audio.ac3"

to make silent audio for it, and then

ppmtoy4m -S 420mpeg2 -A 10:11 -F 30000:1001 -n 119 -r "/tmp/menu.ppm"
|   mpeg2enc -a 2 -f 8 -F 4 -n n -o "/tmp/video.m2v"

for the video (my NTSC options won't be same for your PAL ones).
Finally, you joined them together as bg.mpg with

mplex -V -f 8 -o "/tmp/bg.mpg" "/tmp/video.m2v" "/tmp/audio.ac3"

Next, you made your button overlays and saved them as png files:
highlight.png and select.png. All that's left is to tell spumux how to
use them:

<subpictures>
  <stream>
  <spu
       force="yes"
       start="00:00:00.00"
       highlight="/tmp/highlight.png"
       select="/tmp/select.png"
       >
          <button name="Menu" x0="530" y0="88" x1="623" y1="140"/>
          <button name="Shanghai" x0="105" y0="88" x1="228" y1="140"/>
  </spu>
  </stream>
</subpictures>

Finally, you add them to the mpeg with:

spumux "/tmp/menu_buttons.xml" < "/tmp/bg.mpg" > "menu.mpg"

So, in short, try removing the image= line your xml and see if it works. :-)

Joe

On Saturday 14 April 2007, Joe Friedrichsen wrote:
> On 4/14/07, Anne Wilson <cannewilson@...> wrote:
> > On Saturday 14 April 2007, Joe Friedrichsen wrote:
> > > This sounds like the xml file specifies image, highlight, and select
> > > overlays. I have never had success using all three overlays. Highlight
> > > and select overlays are generally enough, since highlight shows where
> > > the cursor is and (usually) select is just a copy of highlight, but
> > > with a different colour, so that when the viewer hits 'enter', the
> > > button on screen changes colour and shows which was selected.
> >
> > This is the xlm file generated by the gimp plugin:
> >
> > <subpictures>
> >   <stream>
> >     <spu
> >        force="yes"
> >        start="00:00:00.00"
> >        image="airport_image_bl.png"
> >        highlight="airport_highlight_bl.png"
> >        select="airport_select_bl.png"
> >
> >         <button name="Menu" x0="530" y0="88" x1="623" y1="140"/>
> >         <button name="Shanghai" x0="105" y0="88" x1="228" y1="140"/>
> >     </spu>
> >   </stream>
> > </subpictures>
>
> Yes, so the GIMP plug-in is using all three overlays (img, hl, sel),
> something I haven't figured out how to do yet.
>
> > > > I just don't understand how to limit the colours when the background
> > > > is an image.  Any less than 3 colours and the image makes no sense at
> > > > all.I've only used colours from that palette for the two masks.
> > >
> > > Again, if the background image is in the mpeg, you are not limited by
> > > the number of colours. Just use a select and highlight overlay.
> >
> > OK - I have the various png images and a suitable mpeg.  Now how do I
> > call spumux to combine them?  And do I take out the background-image line
> > from the xml?
>
> Great. So let's say that you've created your mpeg... You've done something
> like
>
> ffmpeg -f s16le -i /dev/zero -ac 2 -ar 48000 -ab 224k -t 4 -acodec ac3
> -y "/tmp/audio.ac3"
>
> to make silent audio for it, and then
>
> ppmtoy4m -S 420mpeg2 -A 10:11 -F 30000:1001 -n 119 -r "/tmp/menu.ppm"
>
> |   mpeg2enc -a 2 -f 8 -F 4 -n n -o "/tmp/video.m2v"
>
> for the video (my NTSC options won't be same for your PAL ones).
> Finally, you joined them together as bg.mpg with
>
> mplex -V -f 8 -o "/tmp/bg.mpg" "/tmp/video.m2v" "/tmp/audio.ac3"
>
I use

lav2yuv airport.avi | yuvscaler -O DVD | yuvdenoise | mpeg2enc -f 8 -I 1 -q 
7 -o airport.m2v

lav2wav airport.avi | mp2enc -v 2 -o airport.mp2

mplex airport.m2v airport.mp2 -o Airport.mpg

> Next, you made your button overlays and saved them as png files:
> highlight.png and select.png. All that's left is to tell spumux how to
> use them:
>
> <subpictures>
>   <stream>
>   <spu
>        force="yes"
>        start="00:00:00.00"
>        highlight="/tmp/highlight.png"
>        select="/tmp/select.png"
>
>           <button name="Menu" x0="530" y0="88" x1="623" y1="140"/>
>           <button name="Shanghai" x0="105" y0="88" x1="228" y1="140"/>
>   </spu>
>   </stream>
> </subpictures>
>
> Finally, you add them to the mpeg with:
>
> spumux "/tmp/menu_buttons.xml" < "/tmp/bg.mpg" > "menu.mpg"
>
> So, in short, try removing the image= line your xml and see if it works.
> :-)
>

 spumux airport_spu.xml < Airport.mpg > airport.mpg
DVDAuthor::spumux, version 0.6.14.
Build options: gnugetopt iconv freetype fribidi
Send bugs to <dvdauthor-users@...>

INFO: Locale=en_US.UTF-8
INFO: Converting filenames to UTF-8
INFO: PNG had 2 colors
INFO: PNG had 2 colors
INFO: Constructing blank img
INFO: Pickbuttongroups, success with 1 groups, useimg=1
WARN: Incorrect pack header
INFO: Skipped 2034 bytes of garbage
WARN: Incorrect pack header
INFO: Skipped 2034 bytes of garbage
WARN: Incorrect pack header
INFO: Skipped 2034 bytes of garbage
WARN: Incorrect pack header
INFO: Skipped 2034 bytes of garbage
....
WARN: Incorrect pack header
INFO: Skipped 2034 bytes of garbage
WARN: Incorrect pack header
INFO: 0 subtitles added, 0 subtitles skipped, stream: 32, offset: -0.00

Statistics:
- Processed 0 subtitles.
- The longest display line had -1 characters.
- The maximum number of displayed lines was 0.
- The normal display height of the font arial.ttf was 0.
- The bottom display height of the font arial.ttf was 0.
- The biggest subtitle box had 0 bytes.

<sigh>

Anne

On 4/14/07, Joe Friedrichsen <pengi.films@...> wrote:
> You can see my struggles and successes in a few places: this list
> describes the situation --
> http://sourceforge.net/mailarchive/forum.php?thread_name=440C338D.6000209%40gmail.com&forum_name=dvdauthor-users
> . The failures -- http://mac.north.googlepages.com/spumux . The
> successes -- http://pengi.films.googlepages.com/shizuocha-pp_menus

Revisiting 'Round 5' at http://mac.north.googlepages.com/spumux , I
used the difference mode approach described at
http://www.floatinginspace.za.org/spumux/spumux.html to adjust my
'failed' images, and I successfully made a menu with all three
overlays: image, highlight, and select.

There were some mis-alignments between each overlay (most were only a
pixel). Under the difference mode, it became quite clear how much each
overlay was mis-aligned and how many more colors were created because
of that. Once they were aligned correctly, spumux happily accepted all
three images:

$ spumux menu-mux.xml < menu.mpg > my-menu.mpg
DVDAuthor::spumux, version 0.6.11.
Build options: gnugetopt magick iconv freetype fribidi
Send bugs to <dvdauthor-users@...>

INFO: Locale=LC_CTYPE=ja_JP.UTF-8;LC_NUMERIC=en_US.UTF-8;LC_TIME=en_US.UTF-8;LC_COLLATE=en_US.UTF-8;LC_MONETARY=en_US.UTF-8;LC_MESSAGES=en_US.UTF-8;LC_PAPER=en_US.UTF-8;LC_NAME=en_US.UTF-8;LC_ADDRESS=en_US.UTF-8;LC_TELEPHONE=en_US.UTF-8;LC_MEASUREMENT=en_US.UTF-8;LC_IDENTIFICATION=en_US.UTF-8
INFO: Converting filenames to UTF-8
INFO: Picture new-spu-try-img.png had 2 colors
INFO: Picture new-spu-try-hi.png had 4 colors
INFO: Picture new-spu-try-sel.png had 1 colors
INFO: Autodetect 0 = 332x175-387x230
INFO: Autodetect 1 = 332x250-387x305
INFO: Pickbuttongroups, success with 1 groups, useimg=1
WARN:  Read 0, expected 4
INFO: Found EOF in .sub file.
INFO: Max_sub_size=818
INFO: 1 subtitles added, 0 subtitles skipped, stream: 32, offset: 0.18

Statistics:
- Processed 0 subtitles.
- The longest display line had -1 characters.
- The maximum number of displayed lines was 0.
- The normal display height of the font arial.ttf was 0.
- The bottom display height of the font arial.ttf was 0.
- The biggest subtitle box had 818 bytes.

The curious thing here is spumux's report of image colour content:

INFO: Picture new-spu-try-img.png had 2 colors
INFO: Picture new-spu-try-hi.png had 4 colors
INFO: Picture new-spu-try-sel.png had 1 colors

The first two statements are correct, but the third is 'wrong'. Yes,
new-spu-try-img.png had 2 colours: black and alpha. Yes,
new-spu-try-hi.png had 4 colours: black, alpha, green, blue. No,
new-spu-try-sel.png **did not have** 1 colour; it had four: black,
alpha, green, blue.

However, spumux's report is true -- from a palette perspective,
new-spu-try-sel.png did have only 1 color: the extra green ring around
the character. Looking at all the overlays in the GIMP with each layer
in 'Difference' mode shows this exactly. The other three colors come
from the other image overlays.

Cheers to the South Africans!
Joe

On 4/14/07, Anne Wilson <cannewilson@...> wrote:
>  spumux airport_spu.xml < Airport.mpg > airport.mpg
> DVDAuthor::spumux, version 0.6.14.
> Build options: gnugetopt iconv freetype fribidi
> Send bugs to <dvdauthor-users@...>
>
> INFO: Locale=en_US.UTF-8
> INFO: Converting filenames to UTF-8
> INFO: PNG had 2 colors
> INFO: PNG had 2 colors
> INFO: Constructing blank img
> INFO: Pickbuttongroups, success with 1 groups, useimg=1
> WARN: Incorrect pack header
> INFO: Skipped 2034 bytes of garbage
> WARN: Incorrect pack header
> INFO: Skipped 2034 bytes of garbage
> WARN: Incorrect pack header
> INFO: Skipped 2034 bytes of garbage
> WARN: Incorrect pack header
> INFO: Skipped 2034 bytes of garbage
> ....
> WARN: Incorrect pack header
> INFO: Skipped 2034 bytes of garbage
> WARN: Incorrect pack header
> INFO: 0 subtitles added, 0 subtitles skipped, stream: 32, offset: -0.00
>
> Statistics:
> - Processed 0 subtitles.
> - The longest display line had -1 characters.
> - The maximum number of displayed lines was 0.
> - The normal display height of the font arial.ttf was 0.
> - The bottom display height of the font arial.ttf was 0.
> - The biggest subtitle box had 0 bytes.
>
> <sigh>

It looks like the overlay-adding part worked since different messages
came out of the woodwork (those 'pack header' warnings). Perhaps your
input mpeg isn't fully dvd-compliant... How did you make it?

Joe

On Saturday 14 April 2007, Joe Friedrichsen wrote:
> On 4/14/07, Joe Friedrichsen <pengi.films@...> wrote:
> > You can see my struggles and successes in a few places: this list
> > describes the situation --
> > http://sourceforge.net/mailarchive/forum.php?thread_name=440C338D.6000209
> >%40gmail.com&forum_name=dvdauthor-users . The failures --
> > http://mac.north.googlepages.com/spumux . The
> > successes -- http://pengi.films.googlepages.com/shizuocha-pp_menus
>
> Revisiting 'Round 5' at http://mac.north.googlepages.com/spumux , I
> used the difference mode approach described at
> http://www.floatinginspace.za.org/spumux/spumux.html to adjust my
> 'failed' images, and I successfully made a menu with all three
> overlays: image, highlight, and select.
>
I don't understand this.  It seems to assume that you know the Gimp in more 
detail than I do.  This is a part of the Gimp I've never used before, and I 
can't find anything in the Help file to explain it.

I may, though, have identified the problem.  As instructed in the gimp-button 
plugin tutorial, I created a hollow elipse and then used the bucket fill with 
the appropriate colour.  Looking at this greatly magnified, I find that only 
a single line is the pure colour.  I had unchecked anti-aliasing, and have 
gone through all the fill options I can find.  The only one I can see that 
gives solid colour is the dissolve fill, but that looks really fuzzy-edged, 
for some reason.

Short of drawing pencil lines to hide the shaded colours, I can't see how to 
correct this.

> There were some mis-alignments between each overlay (most were only a
> pixel). Under the difference mode, it became quite clear how much each
> overlay was mis-aligned and how many more colors were created because
> of that. Once they were aligned correctly, spumux happily accepted all
> three images:
>
In theory, using the plugin as instructed, that can't happen.  However, if you 
can show me how, I'll check for that.

> $ spumux menu-mux.xml < menu.mpg > my-menu.mpg
> DVDAuthor::spumux, version 0.6.11.
> Build options: gnugetopt magick iconv freetype fribidi
> Send bugs to <dvdauthor-users@...>
>
> INFO:
> Locale=LC_CTYPE=ja_JP.UTF-8;LC_NUMERIC=en_US.UTF-8;LC_TIME=en_US.UTF-8;LC_C
>OLLATE=en_US.UTF-8;LC_MONETARY=en_US.UTF-8;LC_MESSAGES=en_US.UTF-8;LC_PAPER=
>en_US.UTF-8;LC_NAME=en_US.UTF-8;LC_ADDRESS=en_US.UTF-8;LC_TELEPHONE=en_US.UT
>F-8;LC_MEASUREMENT=en_US.UTF-8;LC_IDENTIFICATION=en_US.UTF-8 INFO:
> Converting filenames to UTF-8
> INFO: Picture new-spu-try-img.png had 2 colors
> INFO: Picture new-spu-try-hi.png had 4 colors
> INFO: Picture new-spu-try-sel.png had 1 colors
> INFO: Autodetect 0 = 332x175-387x230
> INFO: Autodetect 1 = 332x250-387x305
> INFO: Pickbuttongroups, success with 1 groups, useimg=1
> WARN:  Read 0, expected 4
> INFO: Found EOF in .sub file.
> INFO: Max_sub_size=818
> INFO: 1 subtitles added, 0 subtitles skipped, stream: 32, offset: 0.18
>
> Statistics:
> - Processed 0 subtitles.
> - The longest display line had -1 characters.
> - The maximum number of displayed lines was 0.
> - The normal display height of the font arial.ttf was 0.
> - The bottom display height of the font arial.ttf was 0.
> - The biggest subtitle box had 818 bytes.
>
> The curious thing here is spumux's report of image colour content:
>
> INFO: Picture new-spu-try-img.png had 2 colors
> INFO: Picture new-spu-try-hi.png had 4 colors
> INFO: Picture new-spu-try-sel.png had 1 colors
>
> The first two statements are correct, but the third is 'wrong'. Yes,
> new-spu-try-img.png had 2 colours: black and alpha. Yes,
> new-spu-try-hi.png had 4 colours: black, alpha, green, blue. No,
> new-spu-try-sel.png **did not have** 1 colour; it had four: black,
> alpha, green, blue.
>
> However, spumux's report is true -- from a palette perspective,
> new-spu-try-sel.png did have only 1 color: the extra green ring around
> the character. Looking at all the overlays in the GIMP with each layer
> in 'Difference' mode shows this exactly. The other three colors come
> from the other image overlays.
>
I'll continue to work on this on-and-off all day.  I'll let you know if I find 
any answers.

Thanks for your patience :-)

Anne

On Sunday 15 April 2007, Anne Wilson wrote:
>
> I may, though, have identified the problem.  As instructed in the
> gimp-button plugin tutorial, I created a hollow elipse and then used the
> bucket fill with the appropriate colour.  Looking at this greatly
> magnified, I find that only a single line is the pure colour.  I had
> unchecked anti-aliasing, and have gone through all the fill options I can
> find.  The only one I can see that gives solid colour is the dissolve fill,
> but that looks really fuzzy-edged, for some reason.
>
> Short of drawing pencil lines to hide the shaded colours, I can't see how
> to correct this.
>
See attached

Anne

On 4/15/07, Anne Wilson <cannewilson@...> wrote:
> On Saturday 14 April 2007, Joe Friedrichsen wrote:
> > Revisiting 'Round 5' at http://mac.north.googlepages.com/spumux , I
> > used the difference mode approach described at
> > http://www.floatinginspace.za.org/spumux/spumux.html to adjust my
> > 'failed' images, and I successfully made a menu with all three
> > overlays: image, highlight, and select.
> >
> I don't understand this.  It seems to assume that you know the Gimp in more
> detail than I do.  This is a part of the Gimp I've never used before, and I
> can't find anything in the Help file to explain it.

When I make custom menus (eg, when not using a tool like tovid's
makemenu or todisc), I use the GIMP, but not the gimp-button plugin.
This is more from ignorance than preference. I started making buttons
before I knew about the plugin, so I feel more comfortable doing it
'from scratch'.

Typically, a button-making process for me is:
  * start the GIMP, add four layers to the drawing and call them mpeg,
image, highlight, and select.
 * delete the default 'Background' layer so that only the four added
remain. Every layer is now transparent.
  * take a frame from the mpeg (with xine, or vlc, or mplayer) and put
that on the mpeg layer.
 * draw my buttons on the image, highlight and select layers.
  * delete the mpeg layer.
  * remove aliasing/soft edges by forcing the image into indexed mode.
Use the menu: Image -> Mode -> Indexed and specify 3 colours as the
maximum allowed. You can change/adjust colours with the colormap
dialog: Dialogs -> Colormap.
  * hide all but one layer and export each as png files.
  * give spumux those files to use as buttons.

Difference mode is a layer property that can help you find incomplete
overlap or cases when spumux will see more than four colours.
  * change the image mode back to RGB
 * add another layer, fill it completely with black, and move it to
the bottom of the layer stack.
 * select each of your image, highlight, and select layers and change
their mode to 'Difference': in the 'Layers' dialog box, you'll see a
drop-box labeled 'Mode:'. Click that and choose 'Difference' (which is
toward the middle).
  * with each layer visible, you'll see how many colours spumux will
see (excluding the black background color).

> I may, though, have identified the problem.  As instructed in the gimp-button
> plugin tutorial, I created a hollow elipse and then used the bucket fill with
> the appropriate colour.  Looking at this greatly magnified, I find that only
> a single line is the pure colour.  I had unchecked anti-aliasing, and have
> gone through all the fill options I can find.  The only one I can see that
> gives solid colour is the dissolve fill, but that looks really fuzzy-edged,
> for some reason.
>
> Short of drawing pencil lines to hide the shaded colours, I can't see how to
> correct this.

Switching the image to indexed mode (with a maximum colour count set
to how many you want that image to have -- eg, if you only want that
gray, then set the maximum to 1) will force those shaded colours to
either your main colour or 100% alpha, depending on their opacity.
However, if spumux really used these shaded images, you would see a
message like

INFO: Picture my-buttons.png had 22 colors

since each shade would be interpreted as a separate colour.

Good luck!
Joe

On Sunday 15 April 2007, Joe Friedrichsen wrote:
> On 4/15/07, Anne Wilson <cannewilson@...> wrote:
>
> When I make custom menus (eg, when not using a tool like tovid's
> makemenu or todisc), I use the GIMP, but not the gimp-button plugin.
> This is more from ignorance than preference. I started making buttons
> before I knew about the plugin, so I feel more comfortable doing it
> 'from scratch'.
>
> Typically, a button-making process for me is:
>   * start the GIMP, add four layers to the drawing and call them mpeg,
> image, highlight, and select.
>  * delete the default 'Background' layer so that only the four added
> remain. Every layer is now transparent.
>   * take a frame from the mpeg (with xine, or vlc, or mplayer) and put
> that on the mpeg layer.
>  * draw my buttons on the image, highlight and select layers.
>   * delete the mpeg layer.
>   * remove aliasing/soft edges by forcing the image into indexed mode.
> Use the menu: Image -> Mode -> Indexed and specify 3 colours as the
> maximum allowed. You can change/adjust colours with the colormap
> dialog: Dialogs -> Colormap.
>   * hide all but one layer and export each as png files.
>   * give spumux those files to use as buttons.
>
Pretty much what the gimp-plugin does anyway - it just leads you through.

> Difference mode is a layer property that can help you find incomplete
> overlap or cases when spumux will see more than four colours.
>   * change the image mode back to RGB
>  * add another layer, fill it completely with black, and move it to
> the bottom of the layer stack.
>  * select each of your image, highlight, and select layers and change
> their mode to 'Difference': in the 'Layers' dialog box, you'll see a
> drop-box labeled 'Mode:'. Click that and choose 'Difference' (which is
> toward the middle).
>   * with each layer visible, you'll see how many colours spumux will
> see (excluding the black background color).
>
As so often happens, I was almost there.  I'd found it all right - but hadn't 
noticed that setting it to difference was only valid for one layer.  Each 
layer needs setting separately.

> > I may, though, have identified the problem.  As instructed in the
> > gimp-button plugin tutorial, I created a hollow elipse and then used the
> > bucket fill with the appropriate colour.  Looking at this greatly
> > magnified, I find that only a single line is the pure colour.  I had
> > unchecked anti-aliasing, and have gone through all the fill options I can
> > find.  The only one I can see that gives solid colour is the dissolve
> > fill, but that looks really fuzzy-edged, for some reason.
> >
> > Short of drawing pencil lines to hide the shaded colours, I can't see how
> > to correct this.
>
> Switching the image to indexed mode (with a maximum colour count set
> to how many you want that image to have -- eg, if you only want that
> gray, then set the maximum to 1) will force those shaded colours to
> either your main colour or 100% alpha, depending on their opacity.
> However, if spumux really used these shaded images, you would see a
> message like
>
> INFO: Picture my-buttons.png had 22 colors
>
I think I had used indexing, but maybe got one colour too many?  I don't know.

> since each shade would be interpreted as a separate colour.
>
This time I've made absolutely certain that everything consists of black, 
grey, blue and transparent.  I've checked the hex notation for each colour 
and made certain they match.

I'm still not quite there.

INFO: Locale=en_US.UTF-8
INFO: Converting filenames to UTF-8
INFO: PNG had 3 colors
INFO: PNG had 3 colors
INFO: Constructing blank img
ERR: Cannot pick button masks
ERR: Blank image, skipping line -1
WARN: Incorrect pack header
INFO: Skipped 2034 bytes of garbage
.....

I'll go through it again in the morning.  It gets a little faster every time I 
try to do it :-)

Anne

On 4/15/07, Anne Wilson <cannewilson@...> wrote:
> This time I've made absolutely certain that everything consists of black,
> grey, blue and transparent.  I've checked the hex notation for each colour
> and made certain they match.

If you have ImageMagick installed, you can see how many colours are in
your overlays with:

$ identify -verbose highlight.png

Look for something like:

  Colors: 2
  Histogram:
    345516: (    0,    0,    0,65535)   freeze
        84: (65535,65535,    0,    0)   yellow

This says that there are 2 colours in the png file: alpha and yellow,
which IM calls 'freeze' and 'yellow'. Colors are given in RGBA sets.

> I'm still not quite there.
>
> INFO: Locale=en_US.UTF-8
> INFO: Converting filenames to UTF-8
> INFO: PNG had 3 colors
> INFO: PNG had 3 colors
> INFO: Constructing blank img
> ERR: Cannot pick button masks
> ERR: Blank image, skipping line -1
> WARN: Incorrect pack header
> INFO: Skipped 2034 bytes of garbage

I think things got a little worse. In an earlier email, spumux was
able to add the buttons:

INFO: Locale=en_US.UTF-8
INFO: Converting filenames to UTF-8
INFO: PNG had 2 colors
INFO: PNG had 2 colors
INFO: Constructing blank img
INFO: Pickbuttongroups, success with 1 groups, useimg=1
WARN: Incorrect pack header
INFO: Skipped 2034 bytes of garbage
...

I think the 'pack header' errors are coming from an slightly incorrect
mpeg. You said your tool chain was:

lav2yuv airport.avi | yuvscaler -O DVD | yuvdenoise | mpeg2enc -f 8 -I 1 -q
7 -o airport.m2v

lav2wav airport.avi | mp2enc -v 2 -o airport.mp2

mplex airport.m2v airport.mp2 -o Airport.mpg

What does the first output of mpeg2enc (and mplex) say about your
stream? The first 20-30 lines (before the frame-by-frame details)
should tell you how it's treating the input. You may need to tweak a
few options for yuvscaler, mpeg2enc, or mplex if airport.avi isn't
quite right.

Joe

On Sunday 15 April 2007, Joe Friedrichsen wrote:
> On 4/15/07, Anne Wilson <cannewilson@...> wrote:

Maybe it's time to call in the mjpegtools team, so I'm cross-posting this.

> If you have ImageMagick installed, you can see how many colours are in
> your overlays with:
>
> $ identify -verbose highlight.png
>
> Look for something like:
>
>   Colors: 2
>   Histogram:
>     345516: (    0,    0,    0,65535)   freeze
>         84: (65535,65535,    0,    0)   yellow
>
With the current versions of the pngs -

  Colors: 2
  Histogram:
    413008: (  0,  3,  0,255)   #000300FF
      1712: (197,221,226,  0)   #C5DDE200

and

  Colors: 2
  Histogram:
      1712: (106,117,124,  0)   #6A757C00
    413008: (  0,  3,  0,255)   #000300FF

It seems I had messed up the buttons last night, so I started afresh today.

 > > I'm still not quite there.
> >
> > INFO: Locale=en_US.UTF-8
> > INFO: Converting filenames to UTF-8
> > INFO: PNG had 3 colors
> > INFO: PNG had 3 colors
> > INFO: Constructing blank img
> > ERR: Cannot pick button masks
> > ERR: Blank image, skipping line -1
> > WARN: Incorrect pack header
> > INFO: Skipped 2034 bytes of garbage
>
> I think things got a little worse. In an earlier email, spumux was
> able to add the buttons:
>
> INFO: Locale=en_US.UTF-8
> INFO: Converting filenames to UTF-8
> INFO: PNG had 2 colors
> INFO: PNG had 2 colors
> INFO: Constructing blank img
> INFO: Pickbuttongroups, success with 1 groups, useimg=1
> WARN: Incorrect pack header
> INFO: Skipped 2034 bytes of garbage
> ...
>
Now I'm back to 

INFO: Locale=en_US.UTF-8
INFO: Converting filenames to UTF-8
INFO: PNG had 2 colors
INFO: PNG had 2 colors
INFO: Constructing blank img
INFO: Pickbuttongroups, success with 1 groups, useimg=1
WARN: Incorrect pack header
INFO: Skipped 2034 bytes of garbage

> I think the 'pack header' errors are coming from an slightly incorrect
> mpeg. You said your tool chain was:
>
> lav2yuv airport.avi | yuvscaler -O DVD | yuvdenoise | mpeg2enc -f 8 -I 1 -q
> 7 -o airport.m2v
>
> lav2wav airport.avi | mp2enc -v 2 -o airport.mp2
>
> mplex airport.m2v airport.mp2 -o Airport.mpg
>
> What does the first output of mpeg2enc (and mplex) say about your
> stream? The first 20-30 lines (before the frame-by-frame details)
> should tell you how it's treating the input. You may need to tweak a
> few options for yuvscaler, mpeg2enc, or mplex if airport.avi isn't
> quite right.
>
lav2yuv airport.avi | yuvscaler -O DVD | yuvdenoise | mpeg2enc -f 8 -I 1 -q 
7 -o airport.m2v
   INFO: [yuvscaler] yuvscaler 1.9.0 (15-02-2004) is a general scaling utility 
for yuv frames
   INFO: [yuvscaler] (C) 2001-2004 Xavier Biquard <xbiquard@...>, 
yuvscaler -h for help, or man yuvscaler
   INFO: [yuvdenoise] yuvdenoise version 1.9.0
   INFO: [yuvdenoise] Using the following thresholds/settings:
   INFO: [yuvdenoise] Gauss-Pre-Filter      [Y,U,V] : [0,0,0]
   INFO: [yuvdenoise] Median-Pre-Filter     [Y,U,V] : [0,0,0]
   INFO: [yuvdenoise] Temporal-Noise-Filter [Y,U,V] : [0,0,0]
   INFO: [yuvdenoise] Median-Post-Filter    [Y,U,V] : [0,0,0]
   INFO: [yuvdenoise] Renoise               [Y,U,V] : [0,0,0]
   INFO: [yuvdenoise] HQ-Mode                       : off
   INFO: [mpeg2enc] SETTING EXTENDED MMX for MOTION!
   INFO: [mpeg2enc] SETTING SSE and MMX for TRANSFORM!
   INFO: [mpeg2enc] SETTING EXTENDED MMX for PREDICTION!
   INFO: [lav2yuv] chroma '422' recommended with this input
   INFO: [lav2yuv] set default chroma '420jpeg'
   INFO: [yuvscaler] DVD output format requested in PAL/SECAM norm
   INFO: [yuvscaler] input:   frame size:  720x576 pixels (622080 bytes)
   INFO: [yuvscaler] input:       chroma:  4:2:0 JPEG/MPEG-1 (interstitial)
   INFO: [yuvscaler] input:   frame rate:  25/1 fps (~25.000000)
   INFO: [yuvscaler] input:    interlace:  top-field-first
   INFO: [yuvscaler] input: sample aspect ratio:  1:1
   INFO: [yuvscaler] from 720x576, take 720x576+0+0, INTERLACED_TOP_FIRST
   INFO: [yuvscaler] scale to 720x576, 720x576 being displayed
   INFO: [yuvscaler] Scaling uses the RESAMPLE algorithm,
   INFO: [yuvscaler] frame rate: 25.000 fps
   INFO: [yuvscaler] Scaling ratio for width is 1 to 1
   INFO: [yuvscaler] and is 1 to 1 for height
   INFO: [yuvscaler] Specific downscaling routing number 4
   INFO: [yuvscaler] output:   frame size:  720x576 pixels (622080 bytes)
   INFO: [yuvscaler] output:       chroma:  4:2:0 JPEG/MPEG-1 (interstitial)
   INFO: [yuvscaler] output:   frame rate:  25/1 fps (~25.000000)
   INFO: [yuvscaler] output:    interlace:  top-field-first
   INFO: [yuvscaler] output: sample aspect ratio:  1:1
   INFO: [yuvdenoise] Y4M-Stream 720x576(4:2:0 JPEG/MPEG-1 (interstitial))
   INFO: [yuvdenoise] Processing Mode : 4:2:0 interlaced
   INFO: [yuvdenoise] Luma-Plane      : 720x576 pixels
   INFO: [yuvdenoise] Chroma-Plane    : 360x288 pixels
   INFO: [yuvdenoise] Buffers allocated.
   INFO: [yuvdenoise] SETTING EXTENDED MMX for MOTION!
   INFO: [yuvscaler] Frame number 0

Anne

On 4/16/07, Anne Wilson <cannewilson@...> wrote:
> ...
>    INFO: [lav2yuv] chroma '422' recommended with this input
>    INFO: [lav2yuv] set default chroma '420jpeg'
> ...
>    INFO: [yuvscaler] input:       chroma:  4:2:0 JPEG/MPEG-1 (interstitial)
> ...
>    INFO: [yuvscaler] output:       chroma:  4:2:0 JPEG/MPEG-1 (interstitial)
> ...
>    INFO: [yuvdenoise] Y4M-Stream 720x576(4:2:0 JPEG/MPEG-1 (interstitial))
>    INFO: [yuvdenoise] Processing Mode : 4:2:0 interlaced

You need to specify the correct chroma subsampling in lav2yuv:

-C chroma
            Set output chroma (default: '420jpeg').  Currently,
'420jpeg', '420mpeg2', '420paldv', '422' are available.

Add '-C 420mpeg2' to your lav2yuv command :-)

Joe

On Monday 16 April 2007, Joe Friedrichsen wrote:
> On 4/16/07, Anne Wilson <cannewilson@...> wrote:
> > ...
> >    INFO: [lav2yuv] chroma '422' recommended with this input
> >    INFO: [lav2yuv] set default chroma '420jpeg'
> > ...
> >    INFO: [yuvscaler] input:       chroma:  4:2:0 JPEG/MPEG-1
> > (interstitial) ...
> >    INFO: [yuvscaler] output:       chroma:  4:2:0 JPEG/MPEG-1
> > (interstitial) ...
> >    INFO: [yuvdenoise] Y4M-Stream 720x576(4:2:0 JPEG/MPEG-1
> > (interstitial)) INFO: [yuvdenoise] Processing Mode : 4:2:0 interlaced
>
> You need to specify the correct chroma subsampling in lav2yuv:
>
> -C chroma
>             Set output chroma (default: '420jpeg').  Currently,
> '420jpeg', '420mpeg2', '420paldv', '422' are available.
>
> Add '-C 420mpeg2' to your lav2yuv command :-)
>
Like this?

lav2yuv airport.avi | yuvscaler -O DVD | yuvdenoise | mpeg2enc -f 8 -I 1 -q 
7 -C 420mpeg2 -o airport.m2v

That can't be right, I think, because I get

[mpeg2enc] Unable to open: 420mpeg2:

I tried it with single quotes, just in case, but that brought

mpeg2enc: invalid option --
**ERROR: [mpeg2enc] -4 option requires arg 0..4


Anne

On 4/16/07, Anne Wilson <cannewilson@...> wrote:
> On Monday 16 April 2007, Joe Friedrichsen wrote:
> > On 4/16/07, Anne Wilson <cannewilson@...> wrote:
> > > ...
> > >    INFO: [lav2yuv] chroma '422' recommended with this input
> > >    INFO: [lav2yuv] set default chroma '420jpeg'
> > > ...
> > >    INFO: [yuvscaler] input:       chroma:  4:2:0 JPEG/MPEG-1
> > > (interstitial) ...
> > >    INFO: [yuvscaler] output:       chroma:  4:2:0 JPEG/MPEG-1
> > > (interstitial) ...
> > >    INFO: [yuvdenoise] Y4M-Stream 720x576(4:2:0 JPEG/MPEG-1
> > > (interstitial)) INFO: [yuvdenoise] Processing Mode : 4:2:0 interlaced
> >
> > You need to specify the correct chroma subsampling in lav2yuv:
> >
> > -C chroma
> >             Set output chroma (default: '420jpeg').  Currently,
> > '420jpeg', '420mpeg2', '420paldv', '422' are available.
> >
> > Add '-C 420mpeg2' to your lav2yuv command :-)
> >
> Like this?
>
> lav2yuv airport.avi | yuvscaler -O DVD | yuvdenoise | mpeg2enc -f 8 -I 1 -q
> 7 -C 420mpeg2 -o airport.m2v

No, to lav2yuv (not mpeg2enc like you did):

lav2yuv -C 420mpeg2 airport.avi | yuvscaler -O DVD | yuvdenoise |
mpeg2enc -f 8 -I 1 -q 7 -o airport.m2v

Joe

On Monday 16 April 2007, Joe Friedrichsen wrote:
> On 4/16/07, Anne Wilson <cannewilson@...> wrote:
> > On Monday 16 April 2007, Joe Friedrichsen wrote:
> > > On 4/16/07, Anne Wilson <cannewilson@...> wrote:
> > > > ...
> > > >    INFO: [lav2yuv] chroma '422' recommended with this input
> > > >    INFO: [lav2yuv] set default chroma '420jpeg'
> > > > ...
> > > >    INFO: [yuvscaler] input:       chroma:  4:2:0 JPEG/MPEG-1
> > > > (interstitial) ...
> > > >    INFO: [yuvscaler] output:       chroma:  4:2:0 JPEG/MPEG-1
> > > > (interstitial) ...
> > > >    INFO: [yuvdenoise] Y4M-Stream 720x576(4:2:0 JPEG/MPEG-1
> > > > (interstitial)) INFO: [yuvdenoise] Processing Mode : 4:2:0 interlaced
> > >
> > > You need to specify the correct chroma subsampling in lav2yuv:
> > >
> > > -C chroma
> > >             Set output chroma (default: '420jpeg').  Currently,
> > > '420jpeg', '420mpeg2', '420paldv', '422' are available.
> > >
> > > Add '-C 420mpeg2' to your lav2yuv command :-)
> >
> > Like this?
> >
> > lav2yuv airport.avi | yuvscaler -O DVD | yuvdenoise | mpeg2enc -f 8 -I 1
> > -q 7 -C 420mpeg2 -o airport.m2v
>
> No, to lav2yuv (not mpeg2enc like you did):
>
> lav2yuv -C 420mpeg2 airport.avi | yuvscaler -O DVD | yuvdenoise |
> mpeg2enc -f 8 -I 1 -q 7 -o airport.m2v
>
<sigh>

lav2yuv -C 420mpeg2 airport.avi | yuvscaler -O DVD | yuvdenoise | mpeg2enc -f 
8 -I 1 -q 7 -o airport.m2v
   INFO: [yuvscaler] yuvscaler 1.9.0 (15-02-2004) is a general scaling utility 
for yuv frames
   INFO: [yuvscaler] (C) 2001-2004 Xavier Biquard <xbiquard@...>, 
yuvscaler -h for help, or man yuvscaler
   INFO: [yuvdenoise] yuvdenoise version 1.9.0
   INFO: [yuvdenoise] Using the following thresholds/settings:
   INFO: [yuvdenoise] Gauss-Pre-Filter      [Y,U,V] : [0,0,0]
   INFO: [yuvdenoise] Median-Pre-Filter     [Y,U,V] : [0,0,0]
   INFO: [yuvdenoise] Temporal-Noise-Filter [Y,U,V] : [0,0,0]
   INFO: [yuvdenoise] Median-Post-Filter    [Y,U,V] : [0,0,0]
   INFO: [yuvdenoise] Renoise               [Y,U,V] : [0,0,0]
   INFO: [yuvdenoise] HQ-Mode                       : off
   INFO: [lav2yuv] chroma '422' recommended with this input
++ WARN: [lav2yuv] 4:2:0 chroma should be '420jpeg' with this input
   INFO: [yuvscaler] DVD output format requested in PAL/SECAM norm
   INFO: [yuvscaler] input:   frame size:  720x576 pixels (622080 bytes)
   INFO: [yuvscaler] input:       chroma:  4:2:0 MPEG-2 (horiz. cositing)
   INFO: [yuvscaler] input:   frame rate:  25/1 fps (~25.000000)
   INFO: [yuvscaler] input:    interlace:  top-field-first
   INFO: [yuvscaler] input: sample aspect ratio:  1:1
   INFO: [yuvscaler] from 720x576, take 720x576+0+0, INTERLACED_TOP_FIRST
   INFO: [yuvscaler] scale to 720x576, 720x576 being displayed
   INFO: [yuvscaler] Scaling uses the RESAMPLE algorithm,
   INFO: [yuvscaler] frame rate: 25.000 fps
   INFO: [yuvscaler] Scaling ratio for width is 1 to 1
   INFO: [yuvscaler] and is 1 to 1 for height
   INFO: [yuvscaler] Specific downscaling routing number 4
   INFO: [yuvscaler] output:   frame size:  720x576 pixels (622080 bytes)
   INFO: [yuvscaler] output:       chroma:  4:2:0 MPEG-2 (horiz. cositing)
   INFO: [yuvscaler] output:   frame rate:  25/1 fps (~25.000000)
   INFO: [yuvscaler] output:    interlace:  top-field-first
   INFO: [yuvscaler] output: sample aspect ratio:  1:1
   INFO: [yuvscaler] Frame number 0
   INFO: [yuvdenoise] Y4M-Stream 720x576(4:2:0 MPEG-2 (horiz. cositing))
   INFO: [yuvdenoise] Processing Mode : 4:2:0 interlaced
   INFO: [yuvdenoise] Luma-Plane      : 720x576 pixels
   INFO: [yuvdenoise] Chroma-Plane    : 360x288 pixels
   INFO: [yuvdenoise] Buffers allocated.
   INFO: [yuvdenoise] SETTING EXTENDED MMX for MOTION!
   INFO: [yuvscaler] Frame number 1
   INFO: [yuvscaler] Frame number 2
   INFO: [yuvscaler] Frame number 3
   INFO: [yuvscaler] Frame number 4
   INFO: [mpeg2enc] SETTING EXTENDED MMX for MOTION!
   INFO: [mpeg2enc] SETTING SSE and MMX for TRANSFORM!
   INFO: [mpeg2enc] SETTING EXTENDED MMX for PREDICTION!
   INFO: [mpeg2enc] Selecting DVD with dummy navigation packets output profile
   INFO: [mpeg2enc] Assuming norm PAL
   INFO: [mpeg2enc] Encoding MPEG-2 video to airport.m2v
   INFO: [mpeg2enc] Horizontal size: 720 pel
   INFO: [mpeg2enc] Vertical size: 576 pel
   INFO: [mpeg2enc] Aspect ratio code: 1 = 1:1 pixels
   INFO: [mpeg2enc] Frame rate code:   3 = 25.0 (PAL/SECAM VIDEO / converted 
FILM)
   INFO: [mpeg2enc] Bitrate: 7500 KBit/s
   INFO: [mpeg2enc] Quality factor: 7 (Quantisation = 7) (1=best, 31=worst)
   INFO: [mpeg2enc] Field order for input: top-field-first
   INFO: [mpeg2enc] Sequence unlimited length
   INFO: [mpeg2enc] Search radius: 16
   INFO: [mpeg2enc] DualPrime: no
   INFO: [mpeg2enc] Using one-pass rate controller
   INFO: [mpeg2enc] GOP SIZE RANGE 7 TO 15
   INFO: [mpeg2enc] Setting colour/gamma parameters to "PAL B/G"
   INFO: [mpeg2enc] Progressive format frames = 0
   INFO: [mpeg2enc] Using default unmodified quantization matrices
   INFO: [mpeg2enc] SETTING MMX and MMX for QUANTIZER!
   INFO: [mpeg2enc] PAR = 0

   INFO: [mpeg2enc] NEW GOP INIT length 15
   INFO: [yuvscaler] Frame number 5
   INFO: [yuvscaler] Frame number 6
   INFO: [mpeg2enc] Enc1      0     0( 0) I q=12.45     [100% Intra]
   INFO: [yuvscaler] Frame number 7

and still I get

INFO: Locale=en_US.UTF-8
INFO: Converting filenames to UTF-8
INFO: PNG had 2 colors
INFO: PNG had 2 colors
INFO: Constructing blank img
INFO: Pickbuttongroups, success with 1 groups, useimg=1
WARN: Incorrect pack header
INFO: Skipped 2034 bytes of garbage

On 4/16/07, Anne Wilson <cannewilson@...> wrote:
> On Monday 16 April 2007, Joe Friedrichsen wrote:
> > On 4/16/07, Anne Wilson <cannewilson@...> wrote:
> > > Like this?
> > >
> > > lav2yuv airport.avi | yuvscaler -O DVD | yuvdenoise | mpeg2enc -f 8 -I 1
> > > -q 7 -C 420mpeg2 -o airport.m2v
> >
> > No, to lav2yuv (not mpeg2enc like you did):
> >
> > lav2yuv -C 420mpeg2 airport.avi | yuvscaler -O DVD | yuvdenoise |
> > mpeg2enc -f 8 -I 1 -q 7 -o airport.m2v
> >
> <sigh>
>
> lav2yuv -C 420mpeg2 airport.avi | yuvscaler -O DVD | yuvdenoise | mpeg2enc -f
> 8 -I 1 -q 7 -o airport.m2v
> ...
>    INFO: [mpeg2enc] Aspect ratio code: 1 = 1:1 pixels
> ...

Now it looks like mpeg2enc isn't setting a correct aspect ratio. Add
'-a 2' to the mpeg2enc part of the pipe.

man mpeg2enc:
       -a|--aspect num
       Set the playback aspect ratio code of the encoded video. By
default, this value is inferred from the input header.
        1 - 1  - 1:1 display
        2 - 2  - 4:3 display
        3 - 3  - 16:9 display
        4 - 4  - 2.21:1 display

If that still fails, perhaps you can try another tool chain to convert
your avi to mpeg2. tovid can convert nearly any video file into
compliant streams for (S)VCD or DVD. A command line that would work in
your case is:

tovid -pal -full -quality 8 -interlaced -in airport.avi -out Airport

tovid adds the file extension (.mpg) automatically, so you only need
to give the base name. See tovid.org for more information.

Joe

On Monday 16 April 2007, Joe Friedrichsen wrote:
> On 4/16/07, Anne Wilson <cannewilson@...> wrote:
> > On Monday 16 April 2007, Joe Friedrichsen wrote:
> > > On 4/16/07, Anne Wilson <cannewilson@...> wrote:
> > > > Like this?
> > > >
> > > > lav2yuv airport.avi | yuvscaler -O DVD | yuvdenoise | mpeg2enc -f 8
> > > > -I 1 -q 7 -C 420mpeg2 -o airport.m2v
> > >
> > > No, to lav2yuv (not mpeg2enc like you did):
> > >
> > > lav2yuv -C 420mpeg2 airport.avi | yuvscaler -O DVD | yuvdenoise |
> > > mpeg2enc -f 8 -I 1 -q 7 -o airport.m2v
> >
> > <sigh>
> >
> > lav2yuv -C 420mpeg2 airport.avi | yuvscaler -O DVD | yuvdenoise |
> > mpeg2enc -f 8 -I 1 -q 7 -o airport.m2v
> > ...
> >    INFO: [mpeg2enc] Aspect ratio code: 1 = 1:1 pixels
> > ...
>
> Now it looks like mpeg2enc isn't setting a correct aspect ratio. Add
> '-a 2' to the mpeg2enc part of the pipe.
>
> man mpeg2enc:
>        -a|--aspect num
>        Set the playback aspect ratio code of the encoded video. By
> default, this value is inferred from the input header.
>         1 - 1  - 1:1 display
>         2 - 2  - 4:3 display
>         3 - 3  - 16:9 display
>         4 - 4  - 2.21:1 display
>
> If that still fails,

It did.

> perhaps you can try another tool chain to convert 
> your avi to mpeg2. tovid can convert nearly any video file into
> compliant streams for (S)VCD or DVD. A command line that would work in
> your case is:
>
> tovid -pal -full -quality 8 -interlaced -in airport.avi -out Airport
>
> tovid adds the file extension (.mpg) automatically, so you only need
> to give the base name. See tovid.org for more information.
>
Short pause while I install tovid :-)

spumux airport_spu.xml < Airport.mpg > airport.mpg
DVDAuthor::spumux, version 0.6.14.
Build options: gnugetopt iconv freetype fribidi
Send bugs to <dvdauthor-users@...>

INFO: Locale=en_US.UTF-8
INFO: Converting filenames to UTF-8
INFO: PNG had 2 colors
INFO: PNG had 2 colors
INFO: Constructing blank img
INFO: Pickbuttongroups, success with 1 groups, useimg=1
INFO: Found EOF in .sub file.
INFO: Max_sub_size=870
WARN: Button y coordinates are odd for button Shanghai: 103x75-224x124; they 
may not display properly.
INFO: 1 subtitles added, 0 subtitles skipped, stream: 32, offset: 0.16

Statistics:
- Processed 0 subtitles.
- The longest display line had -1 characters.
- The maximum number of displayed lines was 0.
- The normal display height of the font arial.ttf was 0.
- The bottom display height of the font arial.ttf was 0.
- The biggest subtitle box had 870 bytes.

Now I guess I have to test it with a dvdauthor, and see what it makes of that 
Shanghai button.  I'll report back.

Anne

On Monday 16 April 2007, Anne Wilson wrote:
> On Monday 16 April 2007, Joe Friedrichsen wrote:
> > On 4/16/07, Anne Wilson <cannewilson@...> wrote:
> > > On Monday 16 April 2007, Joe Friedrichsen wrote:
> > > > On 4/16/07, Anne Wilson <cannewilson@...> wrote:
> > > > > Like this?
> > > > >
> > > > > lav2yuv airport.avi | yuvscaler -O DVD | yuvdenoise | mpeg2enc -f 8
> > > > > -I 1 -q 7 -C 420mpeg2 -o airport.m2v
> > > >
> > > > No, to lav2yuv (not mpeg2enc like you did):
> > > >
> > > > lav2yuv -C 420mpeg2 airport.avi | yuvscaler -O DVD | yuvdenoise |
> > > > mpeg2enc -f 8 -I 1 -q 7 -o airport.m2v
> > >
> > > <sigh>
> > >
> > > lav2yuv -C 420mpeg2 airport.avi | yuvscaler -O DVD | yuvdenoise |
> > > mpeg2enc -f 8 -I 1 -q 7 -o airport.m2v
> > > ...
> > >    INFO: [mpeg2enc] Aspect ratio code: 1 = 1:1 pixels
> > > ...
> >
> > Now it looks like mpeg2enc isn't setting a correct aspect ratio. Add
> > '-a 2' to the mpeg2enc part of the pipe.
> >
> > man mpeg2enc:
> >        -a|--aspect num
> >        Set the playback aspect ratio code of the encoded video. By
> > default, this value is inferred from the input header.
> >         1 - 1  - 1:1 display
> >         2 - 2  - 4:3 display
> >         3 - 3  - 16:9 display
> >         4 - 4  - 2.21:1 display
> >
> > If that still fails,
>
> It did.
>
> > perhaps you can try another tool chain to convert
> > your avi to mpeg2. tovid can convert nearly any video file into
> > compliant streams for (S)VCD or DVD. A command line that would work in
> > your case is:
> >
> > tovid -pal -full -quality 8 -interlaced -in airport.avi -out Airport
> >
> > tovid adds the file extension (.mpg) automatically, so you only need
> > to give the base name. See tovid.org for more information.
>
> Short pause while I install tovid :-)
>
> spumux airport_spu.xml < Airport.mpg > airport.mpg
> DVDAuthor::spumux, version 0.6.14.
> Build options: gnugetopt iconv freetype fribidi
> Send bugs to <dvdauthor-users@...>
>
> INFO: Locale=en_US.UTF-8
> INFO: Converting filenames to UTF-8
> INFO: PNG had 2 colors
> INFO: PNG had 2 colors
> INFO: Constructing blank img
> INFO: Pickbuttongroups, success with 1 groups, useimg=1
> INFO: Found EOF in .sub file.
> INFO: Max_sub_size=870
> WARN: Button y coordinates are odd for button Shanghai: 103x75-224x124;
> they may not display properly.
> INFO: 1 subtitles added, 0 subtitles skipped, stream: 32, offset: 0.16
>
> Statistics:
> - Processed 0 subtitles.
> - The longest display line had -1 characters.
> - The maximum number of displayed lines was 0.
> - The normal display height of the font arial.ttf was 0.
> - The bottom display height of the font arial.ttf was 0.
> - The biggest subtitle box had 870 bytes.
>
> Now I guess I have to test it with a dvdauthor, and see what it makes of
> that Shanghai button.  I'll report back.
>
STAT: Processing airport.mpg...
ERR:  Cannot find button 'Menu' as referenced by the subtitle

<tears out hair>  OK - I'll clean out everything and start again in the 
morning.  At least I feel as though I have something to go on, now.  Tovid 
does seem to have solved the problem.

Anne

On 4/16/07, Anne Wilson <cannewilson@...> wrote:
> On Monday 16 April 2007, Anne Wilson wrote:
> > Now I guess I have to test it with a dvdauthor, and see what it makes of
> > that Shanghai button.  I'll report back.
> >
> STAT: Processing airport.mpg...
> ERR:  Cannot find button 'Menu' as referenced by the subtitle
>
> <tears out hair>  OK - I'll clean out everything and start again in the
> morning.  At least I feel as though I have something to go on, now.  Tovid
> does seem to have solved the problem.

All this means is that your menu xml and dvdauthor xml aren't quite
agreeing about button names or numbers. Please post those files :-)

Joe

On Monday 16 April 2007, Joe Friedrichsen wrote:
> On 4/16/07, Anne Wilson <cannewilson@...> wrote:
> > On Monday 16 April 2007, Anne Wilson wrote:
> > > Now I guess I have to test it with a dvdauthor, and see what it makes
> > > of that Shanghai button.  I'll report back.
> >
> > STAT: Processing airport.mpg...
> > ERR:  Cannot find button 'Menu' as referenced by the subtitle
> >
> > <tears out hair>  OK - I'll clean out everything and start again in the
> > morning.  At least I feel as though I have something to go on, now. 
> > Tovid does seem to have solved the problem.
>
> All this means is that your menu xml and dvdauthor xml aren't quite
> agreeing about button names or numbers. Please post those files :-)
>
Ah, I see.  Yes, I took the dvd xml from an example, about a week ago.  It's 
not right now.  This is what I have -

airport_spu.xml

<subpictures>
  <stream>
    <spu
       force="yes" 
       start="00:00:00.00" 
       highlight="airportmenu_highlight_bl.png"
       select="airportmenu_select_bl.png"
      >
        <button name="Menu" x0="529" y0="74" x1="622" y1="122"/>
        <button name="Shanghai" x0="103" y0="75" x1="224" y1="124"/>
    </spu>
  </stream>
</subpictures>


<dvdauthor dest="/home/anne/recordings/Video/ChinaTest" jumppad="on">
<vmgm>
	<menus>
		<video format="pal">
		</video>
		<pgc entry="title">
			<vob file="main.mpg"></vob>
			<button>jump titleset 1 menu;</button>
			<button>jump titleset 2 menu;</button>
			<button>jump vmgm menu;</button>
		</pgc>
	</menus>
</vmgm>
	<titleset>
		<menus>
			<pgc entry="root">
				<vob file="airport.mpg"></vob>
				<button>jump title 1 chapter 1;</button>
				<button>jump vmgm menu;</button>
			</pgc>
		</menus>
		<titles>
			<pgc>
				<vob file="scene1.mpg"/>
				<post>call vmgm menu;</post>
			</pgc>
		</titles>
	</titleset>
</dvdauthor>

I realise now that the first part was when I was expecting to go straight on 
to include the next section.  The second part is what I need to get right 
now, then I can go back to sorting out the top menu.

I'll delete the top menu bit for now, though that means that I'll have to work 
out how to set the 'Menu' button to loop.  Do the 'Shanghai' and 'Menu' names 
go in place of the <button></button> pairs?

Anne

On 4/16/07, Anne Wilson <cannewilson@...> wrote:
> On Monday 16 April 2007, Joe Friedrichsen wrote:
> > All this means is that your menu xml and dvdauthor xml aren't quite
> > agreeing about button names or numbers. Please post those files :-)
> >
> Ah, I see.  Yes, I took the dvd xml from an example, about a week ago.  It's
> not right now.  This is what I have -
>
> airport_spu.xml
>
> <subpictures>
> ...
>         <button name="Menu" x0="529" y0="74" x1="622" y1="122"/>
>         <button name="Shanghai" x0="103" y0="75" x1="224" y1="124"/>
> ...
> </subpictures>

Since you gave the buttons names in the menu xml, you'll need to use
those same names in the dvdauthor xml.

> <dvdauthor dest="/home/anne/recordings/Video/ChinaTest" jumppad="on">
> ...
>         <titleset>
>                 <menus>
>                         <pgc entry="root">
>                                 <vob file="airport.mpg"></vob>
>                                 <button>jump title 1 chapter 1;</button>
>                                 <button>jump vmgm menu;</button>
>                         </pgc>
>                 </menus>
> ...

General comments:
 * jump pads aren't recommended. They make more problems they solve :-)
 * dvdauthor is also good about detecting video and audio properties,
so I think your <video> tag isn't really needed (but it doesn't hurt
either).

For working on the titleset menu... add the name attribute to the
button elements. And since you're removing the top vmgm menu for now,
you'll need to set a different jump point for the 'Menu' button:

<vob file="airport.mpg"></vob>
<button name="Shanghai">jump title 1 chapter 1;</button>
<button name="Menu">jump menu;</button>

And don't forget to change the <post> command for your title: call menu;

Joe

On Monday 16 April 2007, Joe Friedrichsen wrote:
> On 4/16/07, Anne Wilson <cannewilson@...> wrote:
> > On Monday 16 April 2007, Joe Friedrichsen wrote:
> > > All this means is that your menu xml and dvdauthor xml aren't quite
> > > agreeing about button names or numbers. Please post those files :-)
> >
> > Ah, I see.  Yes, I took the dvd xml from an example, about a week ago. 
> > It's not right now.  This is what I have -
> >
> > airport_spu.xml
> >
> > <subpictures>
> > ...
> >         <button name="Menu" x0="529" y0="74" x1="622" y1="122"/>
> >         <button name="Shanghai" x0="103" y0="75" x1="224" y1="124"/>
> > ...
> > </subpictures>
>
> Since you gave the buttons names in the menu xml, you'll need to use
> those same names in the dvdauthor xml.
>
> > <dvdauthor dest="/home/anne/recordings/Video/ChinaTest" jumppad="on">
> > ...
> >         <titleset>
> >                 <menus>
> >                         <pgc entry="root">
> >                                 <vob file="airport.mpg"></vob>
> >                                 <button>jump title 1 chapter 1;</button>
> >                                 <button>jump vmgm menu;</button>
> >                         </pgc>
> >                 </menus>
> > ...
>
> General comments:
>  * jump pads aren't recommended. They make more problems they solve :-)
>  * dvdauthor is also good about detecting video and audio properties,
> so I think your <video> tag isn't really needed (but it doesn't hurt
> either).
>
> For working on the titleset menu... add the name attribute to the
> button elements. And since you're removing the top vmgm menu for now,
> you'll need to set a different jump point for the 'Menu' button:
>
> <vob file="airport.mpg"></vob>
> <button name="Shanghai">jump title 1 chapter 1;</button>
> <button name="Menu">jump menu;</button>
>
> And don't forget to change the <post> command for your title: call menu;
>
OK - so now it reads

<dvdauthor dest="/home/anne/recordings/Video/ChinaTest">

	<titleset>
		<menus>
			<pgc entry="root">
				<vob file="airport.mpg"></vob>
				<button name="Shanghai">jump title 1 chapter 1;</button>
				<button name="Menu">jump menu;</button>
			</pgc>
		</menus>
		<titles>
			<pgc>
				<vob file="scene1.mpg"/>
				<post>call menu;</post>
			</pgc>
		</titles>
	</titleset>
</dvdauthor>

Dvdauthor appears to be processing nicely, but then it ends with

ERR:  Cannot find PGC with entry
ERR:  in VTSM pgc 0, button 2

I don't understand what's missing.

Anne

On 4/17/07, Anne Wilson <cannewilson@...> wrote:
> OK - so now it reads
>
> <dvdauthor dest="/home/anne/recordings/Video/ChinaTest">
>
>         <titleset>
>                 <menus>
>                         <pgc entry="root">
>                                 <vob file="airport.mpg"></vob>
>                                 <button name="Shanghai">jump title 1 chapter 1;</button>
>                                 <button name="Menu">jump menu;</button>
>                         </pgc>
>                 </menus>
>                 <titles>
>                         <pgc>
>                                 <vob file="scene1.mpg"/>
>                                 <post>call menu;</post>
>                         </pgc>
>                 </titles>
>         </titleset>
> </dvdauthor>
>
> Dvdauthor appears to be processing nicely, but then it ends with
>
> ERR:  Cannot find PGC with entry
> ERR:  in VTSM pgc 0, button 2
>
> I don't understand what's missing.

I haven't seen that error before, so someone else may be able to give
an exact answer. My guess is that my earlier suggestion for your
<button name="Menu"> jump target was incorrect. The man page says that
you need to 'jump cell 1;' to make a looping menu.

Another thing to try, if that fails, is changing your target to
something more specific: jump titleset 1 menu entry root; and later:
call titleset 1 menu entry root.

One error I did notice was that you omitted the vmgm domain. Even
without a vmgm menu, it's necessary to have at least a '<vmgm />' so
that dvdauthor can complete the disc image. An empty vmgm domain does
create problems for a few hardware players, though.

Joe

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Anne Wilson schrieb:
> OK - so now it reads
> 
> <dvdauthor dest="/home/anne/recordings/Video/ChinaTest">
> 
> 	<titleset>
> 		<menus>
> 			<pgc entry="root">
> 				<vob file="airport.mpg"></vob>
> 				<button name="Shanghai">jump title 1 chapter 1;</button>
> 				<button name="Menu">jump menu;</button>
> 			</pgc>
> 		</menus>
> 		<titles>
> 			<pgc>
> 				<vob file="scene1.mpg"/>
> 				<post>call menu;</post>
> 			</pgc>
> 		</titles>
> 	</titleset>
> </dvdauthor>
> 
> Dvdauthor appears to be processing nicely, but then it ends with
> 
> ERR:  Cannot find PGC with entry
> ERR:  in VTSM pgc 0, button 2
> 
> I don't understand what's missing.

I do respect Joe for his patience with this topic, but is it really so
hard to just try out some of the options given in the man pages or
follow one of the excellent examples on how to use dvdauthor's xml
available on the net?

The only thing, that's missing from making your xml above working, is to
specify and additional <vmgm /> (as Joe wrote in his posting before) and
use "call menu entry root" instead of "call menu" in the second button
definition. It's not so hard to figure that out. A little bit of
"try-and-error"-mentality and you're done!

If you do feel helpless and left-alone with dvdauthor's xml-syntax, then
maybe you want to try out some of the helper applications available,
such as my dvdwizard scripts (http://dvdwizard.sf.net). If you don't
like the resulting dvd layout, maybe you can take at least the generated
xml as a starting point for your own solution.

hth
Wolfgang

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFGJRwhgUafbxFH+p8RArWjAJ9l5Qun/UGwzSpSsh2kAU7h5zdPcACg0xo1
SvWrJmIf78uK72iLY8l9AAA=
=jPO5
-----END PGP SIGNATURE-----

On Tuesday 17 April 2007, Wolfgang Wershofen wrote:
>
> I do respect Joe for his patience with this topic, 

Believe me, so do I.

> but is it really so 
> hard to just try out some of the options given in the man pages or
> follow one of the excellent examples on how to use dvdauthor's xml
> available on the net?

Yes, it is, because it's a matter of learning the language.  In between 
talking to Joe each day I have tried to do what you suggest, but if I don't 
understand the error messages, I try the wrong things.  And don't forget that 
a good part of this time my problems were caused by some incompatibility in 
the mpg files created by mjpegtools.  I couldn't have known that.
>
> The only thing, that's missing from making your xml above working, is to
> specify and additional <vmgm /> (as Joe wrote in his posting before) and
> usegpgkeys: key 81469F6F1147FA9F not found on keyserver
>  "call menu entry root" instead of "call menu" in the second button
> definition. It's not so hard to figure that out. A little bit of
> "try-and-error"-mentality and you're done!
>
I'm working on it.  I'm creating the top-level menu, then will try to set up 
the whole thing, based on what I've learned so far.

> If you do feel helpless and left-alone with dvdauthor's xml-syntax, then
> maybe you want to try out some of the helper applications available,
> such as my dvdwizard scripts (http://dvdwizard.sf.net). If you don't
> like the resulting dvd layout, maybe you can take at least the generated
> xml as a starting point for your own solution.
>
I'll certainly take a look at it - thanks for the suggestion - but in the end 
I really do prefer to learn to use this properly.  When I started using 
mjpegtools it took me a while to get my head around some of the basic 
concepts that I take for granted now.  The patience of Bernhard, Ronald and 
Steven on the mjpegtools list, almost 3 years ago, paid off and I've spent 
many happy hours working with them.  I expect the same to apply to this.  
Once I've really understood the concepts I shall be able to adapt them as 
much as I need to.

Thanks for answering.

Anne

On Tuesday 17 April 2007, Joe Friedrichsen wrote:
> On 4/17/07, Anne Wilson <cannewilson@...> wrote:
> > OK - so now it reads
> >
> > <dvdauthor dest="/home/anne/recordings/Video/ChinaTest">
> >
> >         <titleset>
> >                 <menus>
> >                         <pgc entry="root">
> >                                 <vob file="airport.mpg"></vob>
> >                                 <button name="Shanghai">jump title 1
> > chapter 1;</button> <button name="Menu">jump menu;</button> </pgc>
> >                 </menus>
> >                 <titles>
> >                         <pgc>
> >                                 <vob file="scene1.mpg"/>
> >                                 <post>call menu;</post>
> >                         </pgc>
> >                 </titles>
> >         </titleset>
> > </dvdauthor>
> >
> > Dvdauthor appears to be processing nicely, but then it ends with
> >
> > ERR:  Cannot find PGC with entry
> > ERR:  in VTSM pgc 0, button 2
> >
> > I don't understand what's missing.
>
> I haven't seen that error before, so someone else may be able to give
> an exact answer. My guess is that my earlier suggestion for your
> <button name="Menu"> jump target was incorrect. The man page says that
> you need to 'jump cell 1;' to make a looping menu.
>
OK - I'll take a look at that.  Which man page is this, Joe?  I can't see it 
in the one I have printed out, and I can't find another.

> Another thing to try, if that fails, is changing your target to
> something more specific: jump titleset 1 menu entry root; and later:
> call titleset 1 menu entry root.
>
> One error I did notice was that you omitted the vmgm domain. Even
> without a vmgm menu, it's necessary to have at least a '<vmgm />' so
> that dvdauthor can complete the disc image. An empty vmgm domain does
> create problems for a few hardware players, though.
>
I'm going to try to put together the whole disk, rather than do it by steps, 
as I originally inteded.

Somewhere among the dozens of printed out pages here I saw how to tell each 
titleset whether to treat the buttons vertically or horizontally.  At the 
moment I can't find it again.  Any idea?

Anne

On 4/18/07, Anne Wilson <cannewilson@...> wrote:
> On Tuesday 17 April 2007, Joe Friedrichsen wrote:
> > On 4/17/07, Anne Wilson <cannewilson@...> wrote:
> > > Dvdauthor appears to be processing nicely, but then it ends with
> > >
> > > ERR:  Cannot find PGC with entry
> > > ERR:  in VTSM pgc 0, button 2
> > >
> > > I don't understand what's missing.
> >
> > I haven't seen that error before, so someone else may be able to give
> > an exact answer. My guess is that my earlier suggestion for your
> > <button name="Menu"> jump target was incorrect. The man page says that
> > you need to 'jump cell 1;' to make a looping menu.
> >
> OK - I'll take a look at that.  Which man page is this, Joe?  I can't see it
> in the one I have printed out, and I can't find another.

It's at the tail end of man dvdauthor, the very last line in fact : -)
http://dvdauthor.sourceforge.net/doc/dvdauthor.html

> Somewhere among the dozens of printed out pages here I saw how to tell each
> titleset whether to treat the buttons vertically or horizontally.  At the
> moment I can't find it again.  Any idea?

This would be in man spumux: the autoorder="rows" |
autoorder="columns" element in <spu>.
http://dvdauthor.sourceforge.net/doc/spumux.html However, your buttons
are defined with coordinates (not autodetected with
autooutline="infer", so autoorder won't work, or at least the man page
implies it: 'Finally, autoorder describes which way to order the
automatically detected buttons, which is important for numerically
selected buttons and for mapping buttons to button names or to the
implied names.'

Happy authoring!
Joe

On Wednesday 18 April 2007, Joe Friedrichsen wrote:
> On 4/18/07, Anne Wilson <cannewilson@...> wrote:
> >
> > OK - I'll take a look at that.  Which man page is this, Joe?  I can't see
> > it in the one I have printed out, and I can't find another.
>
> It's at the tail end of man dvdauthor, the very last line in fact : -)
> http://dvdauthor.sourceforge.net/doc/dvdauthor.html
>
So it is!  I distinctly remember reading the paragraph starting "[vmgm" just a 
few lines above it, yet missed that!

> > Somewhere among the dozens of printed out pages here I saw how to tell
> > each titleset whether to treat the buttons vertically or horizontally. 
> > At the moment I can't find it again.  Any idea?
>
> This would be in man spumux: the autoorder="rows" |
> autoorder="columns" element in <spu>.
> http://dvdauthor.sourceforge.net/doc/spumux.html However, your buttons
> are defined with coordinates (not autodetected with
> autooutline="infer", so autoorder won't work, or at least the man page
> implies it: 'Finally, autoorder describes which way to order the
> automatically detected buttons, which is important for numerically
> selected buttons and for mapping buttons to button names or to the
> implied names.'
>
Thanks

> Happy authoring!

I'm sure I will have many happy hours, but there's still a bit of work to 
do :-)

At the moment, I'm failing with the following errors, and can't quite see why.  
As far as I can see the tags are pair-matched.

STAT: Processing scene1.mpg...
STAT: VOBU 176 at 97MB, 1 PGCS
INFO: Video pts = 0.120 .. 108.880
INFO: Audio[8] pts = 0.120 .. 108.816
STAT: VOBU 183 at 101MB, 1 PGCS
INFO: Generating VTS with the following video attributes:
INFO: MPEG version: mpeg2
INFO: TV standard: pal
INFO: Aspect ratio: 4:3
INFO: Resolution: 720x576
INFO: Audio ch 0 format: mp2/2ch, 48khz 20bps

STAT: fixed 3 VOBUS
STAT: fixed 183 VOBUS
ERR:  Cannot match start tag 'titleset'.  Valid tags are:
ERR:      fpc
ERR:      titles
ERR:      menus

Am I looking for the wrong thing?

BTW, I'm trying 'resume', as the man page says it defaults to cell1.  If it's 
wrong, there should be some message to follow up. :-)

Anne

On 4/18/07, Anne Wilson <cannewilson@...> wrote:
> At the moment, I'm failing with the following errors, and can't quite see why.
> As far as I can see the tags are pair-matched.
>
> STAT: Processing scene1.mpg...
> STAT: VOBU 176 at 97MB, 1 PGCS
> INFO: Video pts = 0.120 .. 108.880
> INFO: Audio[8] pts = 0.120 .. 108.816
> STAT: VOBU 183 at 101MB, 1 PGCS
> INFO: Generating VTS with the following video attributes:
> INFO: MPEG version: mpeg2
> INFO: TV standard: pal
> INFO: Aspect ratio: 4:3
> INFO: Resolution: 720x576
> INFO: Audio ch 0 format: mp2/2ch, 48khz 20bps
>
> STAT: fixed 3 VOBUS
> STAT: fixed 183 VOBUS
> ERR:  Cannot match start tag 'titleset'.  Valid tags are:
> ERR:      fpc
> ERR:      titles
> ERR:      menus
>
> Am I looking for the wrong thing?

What does your updated xml look like now?

Joe

On Wednesday 18 April 2007, Joe Friedrichsen wrote:
> On 4/18/07, Anne Wilson <cannewilson@...> wrote:
> > At the moment, I'm failing with the following errors, and can't quite see
> > why. As far as I can see the tags are pair-matched.
> >
> > STAT: Processing scene1.mpg...
> > STAT: VOBU 176 at 97MB, 1 PGCS
> > INFO: Video pts = 0.120 .. 108.880
> > INFO: Audio[8] pts = 0.120 .. 108.816
> > STAT: VOBU 183 at 101MB, 1 PGCS
> > INFO: Generating VTS with the following video attributes:
> > INFO: MPEG version: mpeg2
> > INFO: TV standard: pal
> > INFO: Aspect ratio: 4:3
> > INFO: Resolution: 720x576
> > INFO: Audio ch 0 format: mp2/2ch, 48khz 20bps
> >
> > STAT: fixed 3 VOBUS
> > STAT: fixed 183 VOBUS
> > ERR:  Cannot match start tag 'titleset'.  Valid tags are:
> > ERR:      fpc
> > ERR:      titles
> > ERR:      menus
> >
> > Am I looking for the wrong thing?
>
> What does your updated xml look like now?
>
I attached the full file to the last email - unless you are thinking of the 
_spu xml files?

Anne

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Anne Wilson schrieb:

>> Happy authoring!
> 
> I'm sure I will have many happy hours, but there's still a bit of work to 
> do :-)
> 
> At the moment, I'm failing with the following errors, and can't quite see why.  
> As far as I can see the tags are pair-matched.
> 
> ERR:  Cannot match start tag 'titleset'.  Valid tags are:
> ERR:      fpc
> ERR:      titles
> ERR:      menus
> 
> Am I looking for the wrong thing?
> 
> ------------------------------------------------------------------------
> 
> <dvdauthor dest="/home/anne/recordings/Video/ChinaTest">
> 	<vmgm>
(...)
> </vmgm>
> 	<titleset>
(...)

> 	</titleset>
> 	<titleset>
> 		<menus>
(...)

> 		</menus>
> 		<titles>
(...)

> 		</titles> 

This is where you are missing a </titleset> tag.

> 		<titleset>
(...)

cu
Wolfgang
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFGJnLlgUafbxFH+p8RAoQBAJ4j/47cEWq68/d58LtZRvSQoetdpACdFiGu
Sg35GLMJB409vzxSJVUT9Ig=
=ldbF
-----END PGP SIGNATURE-----

Ah, I didn't notice the attachment. Opera points out the syntax error
straight away when opened in a new tab. I didn't know that :-)

Joe

On Wednesday 18 April 2007, Wolfgang Wershofen wrote:

> This is where you are missing a </titleset> tag.
>
> > 		<titleset>

Thanks, Wolfgang.  Sometimes you can't see the wood for the trees :-)

I'm not 'out of the wood' yet, but getting there.  Dvdauthor processing got as 
far as the end of the first set of titles, this time, which is an 
improvement.  I'll keep on trying to debug it, and get back if I get stuck.

Thanks again

Anne

On Wednesday 18 April 2007, Anne Wilson wrote:
> On Wednesday 18 April 2007, Wolfgang Wershofen wrote:
> > This is where you are missing a </titleset> tag.
> >
> > > 		<titleset>
>
> Thanks, Wolfgang.  Sometimes you can't see the wood for the trees :-)
>
> I'm not 'out of the wood' yet, but getting there.  Dvdauthor processing got
> as far as the end of the first set of titles, this time, which is an
> improvement.  I'll keep on trying to debug it, and get back if I get stuck.
>
At the end of the second titleset I have the line

<button name="menu">jump vmgm menu;</button>

I want it to jump back to the top level menu, at that point.  Now, though, I 
have the error

ERR:  Cannot omit menu/title if specifying vmgm/titleset
ERR:  in VTSM pgc 0, button 1kunming

Can you explain that to me, please?  The only example I can find seems to use 
it exactly like that.

Anne

On 4/18/07, Anne Wilson <cannewilson@...> wrote:
> On Wednesday 18 April 2007, Anne Wilson wrote:
> > On Wednesday 18 April 2007, Wolfgang Wershofen wrote:
> > > This is where you are missing a </titleset> tag.
> > >
> > > >           <titleset>
> >
> > Thanks, Wolfgang.  Sometimes you can't see the wood for the trees :-)
> >
> > I'm not 'out of the wood' yet, but getting there.  Dvdauthor processing got
> > as far as the end of the first set of titles, this time, which is an
> > improvement.  I'll keep on trying to debug it, and get back if I get stuck.
> >
> At the end of the second titleset I have the line
>
> <button name="menu">jump vmgm menu;</button>
>
> I want it to jump back to the top level menu, at that point.  Now, though, I
> have the error

It's not that target creating the error...

With each new <titleset>, titles reset their numbering and start from
1again. In a <titles> tag, each <pgc> represents a title and each
<vob> represents a chapter in its corresponding <pgc>.

Your

<button name="1kunming">jump title 2 chapter 1;</button>

and friends need to be

<button name="1kunming">jump title 1 chapter 1;</button>

but since each of your titlesets only have one title (ie <pgc>) in
them, you can probably omit the 'title N' part from the command and
just 'jump chapter M' because the target is obvious.

Joe

On Wednesday 18 April 2007, Joe Friedrichsen wrote:
> On 4/18/07, Anne Wilson <cannewilson@...> wrote:
> > On Wednesday 18 April 2007, Anne Wilson wrote:
> > > On Wednesday 18 April 2007, Wolfgang Wershofen wrote:
> > > > This is where you are missing a </titleset> tag.
> > > >
> > > > >           <titleset>
> > >
> > > Thanks, Wolfgang.  Sometimes you can't see the wood for the trees :-)
> > >
> > > I'm not 'out of the wood' yet, but getting there.  Dvdauthor processing
> > > got as far as the end of the first set of titles, this time, which is
> > > an improvement.  I'll keep on trying to debug it, and get back if I get
> > > stuck.
> >
> > At the end of the second titleset I have the line
> >
> > <button name="menu">jump vmgm menu;</button>
> >
> > I want it to jump back to the top level menu, at that point.  Now,
> > though, I have the error
>
> It's not that target creating the error...
>
> With each new <titleset>, titles reset their numbering and start from
> 1again. In a <titles> tag, each <pgc> represents a title and each
> <vob> represents a chapter in its corresponding <pgc>.
>
> Your
>
> <button name="1kunming">jump title 2 chapter 1;</button>
>
> and friends need to be
>
> <button name="1kunming">jump title 1 chapter 1;</button>
>
I had already figured that out, and changed it.  No difference.

> but since each of your titlesets only have one title (ie <pgc>) in
> them, you can probably omit the 'title N' part from the command and
> just 'jump chapter M' because the target is obvious.
>
I tried that this morning, but still get the same error.

The example I have in front of me uses

<titleset>
<menus>
<pgc entry="root"
<vob file="sun_pm6.mpg"></vob>
<button>jump title 1 chapter 1;</button>
<button>jump title 1 chapter 2;</button>
<button>jump title 1 chapter 3;</button>
<button>jump vmgm menu;</button>
</pgc>
</menus>
<titles>
<pgc>
<vob file="swimb027_001.mpg"></vob>
<vob file="swimb028_001.mpg"></vob>
<vob file="swimb029_001.mpg"></vob>
<post>call vmgm menu;</post>
</pgc>
</titles>
<titleset>

I typed it in full, in case that brought any enlightenment, but everything 
looks the same as mine, apart from the fact that he calls the vmgm menu at 
the end of the vob files.

Still I can't get rid of that error.  The latest version of the xml file is 
attached.

Anne

I appear to have solved the problem.  At least, I think so.  I can't test the 
result just now, because it is 4.8 GB, so will have to use the dual-layer 
burner - drat it :-)  Anyway, dvdauthor continued to the end, so if there are 
any problems it will be with the menus now, and I'll know where to look.

Remember way back when we discussed whether it was necessary to have 'title 1' 
in the button definition, if there was only one title?  Well it is necessary.  
I have made only two changes, both of which I had tried before and failed, 
but together they succeeded.

The line

<button name="1kunming">jump chapter 1;</button>

was replaced by

<button name="1kunming">jump title 1 chapter 1;</button>

and at the end of the second and third titlesets I used

<post>resume;</post>

I could hardly believe my eyes when I saw the processing continue on to the 
third titleset :-)

Thanks for all the help, Joe and Wolfgang.

Anne

On 4/19/07, Anne Wilson <cannewilson@...> wrote:
> Remember way back when we discussed whether it was necessary to have 'title 1'
> in the button definition, if there was only one title?  Well it is necessary.
> I have made only two changes, both of which I had tried before and failed,
> but together they succeeded.

Sorry for the mis-information. Checking back with dvdauthor's man
page, title is always necessary and the others are optional:

 [vmgm | titleset X] title Y [chapter Z]

Glad to see it's working! Regarding your 4.8GB image, the development
version of tovid has a '-fit NUM' option which will make the output
file fit inside NUM megabytes (1024*1024), provided you don't ask the
impossible (tovid won't encode at less than 8MB/min for DVD
resolutions).

Joe

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Anne Wilson schrieb:
> I appear to have solved the problem.  At least, I think so.  I can't test the 
> result just now, because it is 4.8 GB, so will have to use the dual-layer 
> burner - drat it :-)  Anyway, dvdauthor continued to the end, so if there are 
> any problems it will be with the menus now, and I'll know where to look.

Why aren't you able to test the result? Don't you have xine or mplayer
or another software player installed? Don't waste your precious DVD
media unless you are sure the DVD works as expected in a software
player! There's lots more to come until you have a working DVD and to
distinguish problems with a wrong authoring from pure hardware dependent
issues will help you a lot - trust me!

But anyway, you don't neccessarily need to use a DL-DVD for 4.8G. There
are some really good compression tools available to reduce the size of a
DVD without noticable loss of quality. I use DVDShrink for that purpose,
although it's a Windoze soft, but it's free and runs fine under wine.
There are also some Linux native solutions for this task (you may want
to try out k9copy - looks promising. See http://k9copy.sf.net).

> 
> Remember way back when we discussed whether it was necessary to have 'title 1' 
> in the button definition, if there was only one title?  Well it is necessary.  
> I have made only two changes, both of which I had tried before and failed, 
> but together they succeeded.
> 
> The line
> 
> <button name="1kunming">jump chapter 1;</button>
> 
> was replaced by
> 
> <button name="1kunming">jump title 1 chapter 1;</button>

That's what the error message in you previous posting was saying:
ERR:  Cannot omit menu/title if specifying vmgm/titleset
ERR:  in VTSM pgc 0, button 1kunming

It tells you which button had the error and that you may not leave out
the title specification. Wasn't too hard to guess, was it?

> 
> and at the end of the second and third titlesets I used
> 
> <post>resume;</post>

What do you want to achieve with this? I suspect this won't work. AFAIK,
the resume function only works, if a menu was called from within a
playing title with the remote control. Resume will then jump back to the
    point in the movie, where the menu was called.
- From the manpage of dvdauthor, I read that a "resume" can only work to
return from a "call" statement. And since you can only "call" a menu,
IMHO "resume" outside a menu definition doesn't make any sense.

> 
> I could hardly believe my eyes when I saw the processing continue on to the 
> third titleset :-)

Miracles do happen - everyday! ;-)

hth
Wolfgang

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFGJ5ykgUafbxFH+p8RAkaXAKDPurk0llNtQ+2USGTab6gbHjcKYgCgiNqw
Vwcw+8x8ZfEDmbKhkjSaH70=
=kwBY
-----END PGP SIGNATURE-----

On Thursday 19 April 2007, Joe Friedrichsen wrote:
> On 4/19/07, Anne Wilson <cannewilson@...> wrote:
> > Remember way back when we discussed whether it was necessary to have
> > 'title 1' in the button definition, if there was only one title?  Well it
> > is necessary. I have made only two changes, both of which I had tried
> > before and failed, but together they succeeded.
>
> Sorry for the mis-information. Checking back with dvdauthor's man
> page, title is always necessary and the others are optional:
>
>  [vmgm | titleset X] title Y [chapter Z]
>
> Glad to see it's working! Regarding your 4.8GB image, the development
> version of tovid has a '-fit NUM' option which will make the output
> file fit inside NUM megabytes (1024*1024), provided you don't ask the
> impossible (tovid won't encode at less than 8MB/min for DVD
> resolutions).
>
Thanks, I'll look into that.

Anne

On Thursday 19 April 2007, Wolfgang Wershofen wrote:

>
> Why aren't you able to test the result? Don't you have xine or mplayer
> or another software player installed? 

I used to test in xine, but this box is running FC6 and xine is broken once 
again.  The command 'xine dvd:path/' is what I used, but mplayer doesn't work 
with that - or at least it didn't when I last tried it.

> Don't waste your precious DVD 
> media unless you are sure the DVD works as expected in a software
> player! There's lots more to come until you have a working DVD and to
> distinguish problems with a wrong authoring from pure hardware dependent
> issues will help you a lot - trust me!
>
I never doubted it.  I did try burning one disk, knowing that I'd probably 
have to do it again, but I never got past the top-level menu when trying to 
view it.  I'll take another look at the spumux part.  I'm a bit worried that 
I'm running out of time before my vacation, and I did want it finished before 
then :-)

> But anyway, you don't neccessarily need to use a DL-DVD for 4.8G. There
> are some really good compression tools available to reduce the size of a
> DVD without noticable loss of quality. I use DVDShrink for that purpose,
> although it's a Windoze soft, but it's free and runs fine under wine.
> There are also some Linux native solutions for this task (you may want
> to try out k9copy - looks promising. See http://k9copy.sf.net).
>
I've never tried any of these.  I'll take a look, thanks.

> > Remember way back when we discussed whether it was necessary to have
> > 'title 1' in the button definition, if there was only one title?  Well it
> > is necessary. I have made only two changes, both of which I had tried
> > before and failed, but together they succeeded.
> >
> > The line
> >
> > <button name="1kunming">jump chapter 1;</button>
> >
> > was replaced by
> >
> > <button name="1kunming">jump title 1 chapter 1;</button>
>
> That's what the error message in you previous posting was saying:
> ERR:  Cannot omit menu/title if specifying vmgm/titleset
> ERR:  in VTSM pgc 0, button 1kunming
>
> It tells you which button had the error and that you may not leave out
> the title specification. Wasn't too hard to guess, was it?
>
At the time, yes, though it's obvious now.

> > and at the end of the second and third titlesets I used
> >
> > <post>resume;</post>
>
> What do you want to achieve with this? I suspect this won't work. AFAIK,
> the resume function only works, igpgkeys: key 81469F6F1147FA9F not found on
> keyserver f a menu was called from within a
> playing title with the remote control. Resume will then jump back to the
>     point in the movie, where the menu was called.
> From the manpage of dvdauthor, I read that a "resume" can only work to
> return from a "call" statement. And since you can only "call" a menu,
> IMHO "resume" outside a menu definition doesn't make any sense.
>
OK, so I need to find what will work.  At the end of a titleset I want it to 
jump back to the menu for that same titleset.

> > I could hardly believe my eyes when I saw the processing continue on to
> > the third titleset :-)
>
> Miracles do happen - everyday! ;-)
>
It can be hard going at times, but the promise of light at the end makes it 
all worth while :-)

Anne

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Anne Wilson schrieb:
> On Thursday 19 April 2007, Wolfgang Wershofen wrote:
> 
>> Why aren't you able to test the result? Don't you have xine or mplayer
>> or another software player installed? 
> 
> I used to test in xine, but this box is running FC6 and xine is broken once 
> again.  The command 'xine dvd:path/' is what I used, but mplayer doesn't work 
> with that - or at least it didn't when I last tried it.
> 

Ok, sorry, mplayer wasn't the right thing since it has no support for
menus. On my (SuSE)-machine, I use xine with

	xine dvd://<full_path_to_dvd_directory>

e.g. if the DVD was authored into /home/user/dvd, then you have to you
use "xine dvd:///home/user/dvd". AFAIK, the double-slash after dvd: is
essential for xine.

>> Don't waste your precious DVD 
>> media unless you are sure the DVD works as expected in a software
>> player! There's lots more to come until you have a working DVD and to
>> distinguish problems with a wrong authoring from pure hardware dependent
>> issues will help you a lot - trust me!
>>
> I never doubted it.  I did try burning one disk, knowing that I'd probably 
> have to do it again, but I never got past the top-level menu when trying to 
> view it.  I'll take another look at the spumux part.  I'm a bit worried that 
> I'm running out of time before my vacation, and I did want it finished before 
> then :-)

Ok, but esspecially with the display of menus, some hardware players are
quite picky. That's why you have to make sure, the menus work as desired
on a software player.

>>> and at the end of the second and third titlesets I used
>>>
>>> <post>resume;</post>
>> What do you want to achieve with this? I suspect this won't work. AFAIK,
>> the resume function only works, igpgkeys: key 81469F6F1147FA9F not found on
>> keyserver f a menu was called from within a
>> playing title with the remote control. Resume will then jump back to the
>>     point in the movie, where the menu was called.
>> From the manpage of dvdauthor, I read that a "resume" can only work to
>> return from a "call" statement. And since you can only "call" a menu,
>> IMHO "resume" outside a menu definition doesn't make any sense.
>>
> OK, so I need to find what will work.  At the end of a titleset I want it to 
> jump back to the menu for that same titleset.

That's very easy. Each menu has an entry name specified in the
corresponding <pgc>-tag (e.g. <pgc entry="root">). So if you want to
return to the root-menu of your titleset, then you should use "call menu
entry root;" as command in the <post>-tag.

hth
Wolfgang
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFGKGBCgUafbxFH+p8RAoCgAKCLOtqAcXJVEGp6zj4HT3MQfb7XUwCgi8XD
CUDx5MYmCL43muz7Pe77Jag=
=hfnH
-----END PGP SIGNATURE-----

On 4/19/07, Anne Wilson <cannewilson@...> wrote:
> On Thursday 19 April 2007, Wolfgang Wershofen wrote:
>
> >
> > Why aren't you able to test the result? Don't you have xine or mplayer
> > or another software player installed?
>
> I used to test in xine, but this box is running FC6 and xine is broken once
> again.  The command 'xine dvd:path/' is what I used, but mplayer doesn't work
> with that - or at least it didn't when I last tried it.

Try using absolute paths -- i.e. xine (or mplayer) dvd:/`pwd`/ from
the DVD directory (those are back ticks, equivalent to $(pwd), or
running the pwd command and typing its output in that spot -- just in
case you aren't fully familiar with shell usage).  This is just a wild
guess, but you may also try mplayer dvd:// -dvd-device . (the . is
part of the command)

Mike Bourgeous

On Friday 20 April 2007, Wolfgang Wershofen wrote:
> Anne Wilson schrieb:
> Ok, sorry, mplayer wasn't the right thing since it has no support for
> menus. On my (SuSE)-machine, I use xine with
>
> 	xine dvd://<full_path_to_dvd_directory>
>
> e.g. if the DVD was authored into /home/user/dvd, then you have to you
> use "xine dvd:///home/user/dvd". AFAIK, the double-slash after dvd: is
> essential for xine.
>
As, I think, a trailing '/' is :-)  OK - I have Mandriva on a laptop, and I 
can call it there.  However, the menus do not work at all.  I get the 
top-level menu screen, but no highlights and no response from a mouse-click.

> > OK, so I need to find what will work.  At the end of a titleset I want it
> > to jump back to the menu for that same titleset.
>
> That's very easy. Each menu has an entry name specified in the
> corresponding <pgc>-tag (e.g. <pgc entry="root">). So if you want to
> return to the root-menu of your titleset, then you should use "call menu
> entry root;" as command in the <post>-tag.
>
Amendments made, thanks.  Now I need to know why the menus are totally 
kaput :-)

Anne

On Friday 20 April 2007, Michael Bourgeous wrote:
> On 4/19/07, Anne Wilson <cannewilson@...> wrote:
> > On Thursday 19 April 2007, Wolfgang Wershofen wrote:
> > > Why aren't you able to test the result? Don't you have xine or mplayer
> > > or another software player installed?
> >
> > I used to test in xine, but this box is running FC6 and xine is broken
> > once again.  The command 'xine dvd:path/' is what I used, but mplayer
> > doesn't work with that - or at least it didn't when I last tried it.
>
> Try using absolute paths -- i.e. xine (or mplayer) dvd:/`pwd`/ from
> the DVD directory (those are back ticks, equivalent to $(pwd), or
> running the pwd command and typing its output in that spot -- just in
> case you aren't fully familiar with shell usage).  This is just a wild
> guess, but you may also try mplayer dvd:// -dvd-device . (the . is
> part of the command)
>
Thanks for replying, Mike.  I have it working now on my Mandriva laptop.  The 
menus are still useless, though.

Anne

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Anne Wilson schrieb:
> On Friday 20 April 2007, Wolfgang Wershofen wrote:
> Amendments made, thanks.  Now I need to know why the menus are totally 
> kaput :-)

Ok, then let's go into the details. You say, the top-level (I suggest
vmgm) menu is displayed, but you don't see any highlights and no mouse
reaction, right?

Do you have any webspace on the net available, where you can put your
image files, spumux xml and the spumux output messages concerning the
vmgm menu, so I can download and check them out? I guess, the whole
stuff will be too much to be accepted as attachment on this list.
If you don't have webspace, please put all the files into a tarball and
send them to me as PM.

Just one shot in the dark: Did you use any "pause" parameters on the pgc
of vob-tags in your vmgm menu? If not, try to specify pause="inf" either
on your pgc or vob in the menu.
This will ensure, the player waits for a user input before advancing. I
don't know, what happens if the pausing is not present (and no <post>
instruction), but I could imaging that the player doesn't know what to
do next and simply freezes.

If there's no pause in your xml, try to change it and retry. If it still
fails, supply me with your working files and command outputs.

When does your vacation start? ;-)

hth
Wolfgang
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFGKIyMgUafbxFH+p8RAmrPAJ9GoYqUM9HdNV4wp4GPi2SbKYEEMQCffX7j
hE9+yJrFyVlpfP2iuIdwLh0=
=J/WP
-----END PGP SIGNATURE-----

On Friday 20 April 2007, Wolfgang Wershofen wrote:
> Anne Wilson schrieb:
> > On Friday 20 April 2007, Wolfgang Wershofen wrote:
> > Amendments made, thanks.  Now I need to know why the menus are totally
> > kaput :-)
>
> Ok, then let's go into the details. You say, the top-level (I suggest
> vmgm) menu is displayed, but you don't see any highlights and no mouse
> reaction, right?
>
Right.

> Do you have any webspace on the net available, where you can put your
> image files, spumux xml and the spumux output messages concerning the
> vmgm menu, so I can download and check them out? I guess, the whole
> stuff will be too much to be accepted as attachment on this list.
> If you don't have webspace, please put all the files into a tarball and
> send them to me as PM.
>
Just the files relating to menus?  Yes, I think I have enough space for that.  
I'll mail you direct when they are up.

> Just one shot in the dark: Did you use any "pause" parameters on the pgc
> of vob-tags in your vmgm menu? If not, try to specify pause="inf" either
> on your pgc or vob in the menu.
> This will ensure, the player waits for a user input before advancing. I
> don't know, what happens if the pausing is not present (and no <post>
> instruction), bgpgkeys: key 81469F6F1147FA9F not found on keyserver
> ut I could imaging that the player doesn't know what to
> do next and simply freezes.
>
That could be the case.

> If there's no pause in your xml, try to change it and retry. If it still
> fails, supply me with your working files and command outputs.
>
I'll try that before putting the files up.

> When does your vacation start? ;-)
>
Early Monday morning.

Anne

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Anne Wilson schrieb:
> On Friday 20 April 2007, Wolfgang Wershofen wrote:
>> If you don't have webspace, please put all the files into a tarball and
>> send them to me as PM.
>>
> Just the files relating to menus?  Yes, I think I have enough space for that.  
> I'll mail you direct when they are up.
> 

- From the vmgm menu, I need the image files with your button masks as
specified in the spumux xml, the xml definition itself (for spumux and
dvdauthor), the underlying mpeg file where the buttons should be muxed
in (before spumux!!!) and the messages, spumux issued when creating the
menu mpeg with the buttons.

>> When does your vacation start? ;-)
>>
> Early Monday morning.

So we have the whole weekend to work on that. Should be possible, but I
hope, your bags are already packed... ;-)

cu
Wolfgang
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFGKKFMgUafbxFH+p8RAi6bAKDXeikmT5DzwyRCp3cQwT4WJDOIjACfa7pX
SxW4lcKAsR91ECTGf9EVNAo=
=GqdP
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Anne Wilson schrieb:
>> Do you have any webspace on the net available, where you can put your
>> image files, spumux xml and the spumux output messages concerning the
>> vmgm menu, so I can download and check them out? I guess, the whole
>> stuff will be too much to be accepted as attachment on this list.
>> If you don't have webspace, please put all the files into a tarball and
>> send them to me as PM.
>>
> Just the files relating to menus?  Yes, I think I have enough space for that.  
> I'll mail you direct when they are up.
> 

Ok, got your files and started working with them.

First thing was to see what spumux has to say about your button masks,
so I did a
	spumux -v4 main_spu.xml < Main.mpg > Main_spu.mpg

The output was:

ERR: Cannot pick button masks
ERR: Blank image, skipping line -1
INFO: 0 subtitles added, 1 subtitles skipped, stream: 32, offset: 0.16

It seems, your button masks don't align exactly together and thus result
in a combined palette that has more than 4 colors. Refer to Joe's link
to this excellent spumux limitation description.
But from this, it is no wonder, that you can't see any button outlines
on your dvd - they are simply not there!

So I mogrified your button masks to contain only 2 colors each with
	mogrify -colors 2 main_highlight_bl.png
	mogrify -colors 2 main_select_bl.png
(mogrify is a tool from ImageMagick and changes images in place).

I spumuxed again and now it worked:

INFO: Pickbuttongroups, success with 1 groups, useimg=1
INFO: After read_bmp(): xd=384 yd=196 x0=138 y0=146
INFO: Found EOF in .sub file.
INFO: Max_sub_size=1788
WARN: Button y coordinates are odd for button 1Shanghai:
137x145-523x208; they may not display properly.
INFO: Subtitle inserted at: 0.160000 sd=0
INFO: 1 subtitles added, 0 subtitles skipped, stream: 32, offset: 0.16

Except for the warning, everything is fine. The essential message is: "1
subtitles added".

The same applies to your Airport.mpg and corresponding button masks.
After "mogrification", all went fine.

Surprisingly enough, the last two menus spumuxed fine, as the button
masks already had only two colors each.

So, all the menus now have subtitle tracks with button definitions muxed
in and are ready to go.

I then had to adjust your dvdauthor-xml - not only to reflect the new
menu mpegs and some "dummy"-mpegs, I used to reproduce your complete dvd
structure. Here are the changes, you may have to reproduce on your side
as well to make the DVD work as it should:

1. In the vmgm, button 3Shanghai: Change "titleset 2" to "titleset 3"
2. For all return jumps to the vmgm domain: Better use "jump vmgm menu
entry title" instead of only "jump vmgm menu"
3. In the <post>-instruction of titleset 1: Change "resume" to "call
menu entry root;"

That's it. I authored the DVD with that changes and tested it in xine -
worked flawlessly!

Check it out.

hth
Wolfgang



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFGKOntgUafbxFH+p8RAozgAKCQ6isx3opWLn+jg/VNU3RXQXfuFgCgpkLw
c3/KEyvL+B+GHUVGSiNPp/M=
=CpBk
-----END PGP SIGNATURE-----

On Friday 20 April 2007, Wolfgang Wershofen wrote:
>
> Ok, got your files and started working with them.
>
> First thing was to see what spumux has to say about your button masks,
> so I did a
> 	spumux -v4 main_spu.xml < Main.mpg > Main_spu.mpg
>
> The output was:
>
> ERR: Cannot pick button masks
> ERR: Blank image, skipping line -1
> INFO: 0 subtitles added, 1 subtitles skipped, stream: 32, offset: 0.16
>
> It seems, your button masks don't align exactly together and thus result
> in a combined palette that has more than 4 colors. Refer to Joe's link
> to this excellent spumux limitation description.
> But from this, it is no wonder, that you can't see any button outlines
> on your dvd - they are simply not there!
>
> So I mogrified your button masks to contain only 2 colors each with
> 	mogrify -colors 2 main_highlight_bl.png
> 	mogrify -colors 2 main_select_bl.png
> (mogrify is a tool from ImageMagick and changes images in place).
>
Odd - or maybe not so odd.  I definitely got it down to having only two 
colours in the masks, and spumux ran completely and accepted them.  But then, 
come to think of it,  I've tried so long to get them right, and there have 
been so many versions in the directory, that maybe I've used an older version 
of something, and that's messed it up.

> I spumuxed again and now it worked:
>
> INFO: Pickbuttongroups, success with 1 groups, useimg=1
> INFO: After read_bmp(): xd=384 yd=196 x0=138 y0=146
> INFO: Found EOF in .sub file.
> INFO: Max_sub_size=1788
> WARN: Button y coordinates are odd for button 1Shanghai:
> 137x145-523x208; they may not display properly.
> INFO: Subtitle inserted at: 0.160000 sd=0
> INFO: 1 subtitles added, 0 subtitles skipped, stream: 32, offset: 0.16
>
> Except for the warning, everything is fine. The essential message is: "1
> subtitles added".
>
> The same applies to your Airport.mpg and corresponding button masks.
> After "mogrification", all went fine.
>
> Surprisingly enough, the last two megpgkeys: key 81469F6F1147FA9F not found
> on keyserver nus spumuxed fine, as the button
> masks already had only two colors each.
>
> So, all the menus now have subtitle tracks with button definitions muxed
> in and are ready to go.
>
> I then had to adjust your dvdauthor-xml - not only to reflect the new
> menu mpegs and some "dummy"-mpegs, I used to reproduce your complete dvd
> structure. Here are the changes, you may have to reproduce on your side
> as well to make the DVD work as it should:
>
> 1. In the vmgm, button 3Shanghai: Change "titleset 2" to "titleset 3"
> 2. For all return jumps to the vmgm domain: Better use "jump vmgm menu
> entry title" instead of only "jump vmgm menu"
> 3. In the <post>-instruction of titleset 1: Change "resume" to "call
> menu entry root;"
>
> That's it. I authored the DVD with that changes and tested it in xine -
> worked flawlessly!
>
> Check it out.
>
> hth
> Wolfgang
>
Thanks for all the time spent on this.  I'll go through it all this evening, 
checking the masks.  I haven't used mogrify, but I'll check it out.  It 
sounds as though I need it.

When everything's done I'll report back.  Thanks again

Anne

On Friday 20 April 2007, Wolfgang Wershofen wrote:
>
> That's it. I authored the DVD with that changes and tested it in xine -
> worked flawlessly!
>
> Check it out.
>
Not quite there, I'm afraid.  Mogrify chewed up my buttons images and I didn't 
notice it before authoring :-(  I still have the .xcf file, so I can re-do 
them.

More serious, though, is that the last titleset, Shanghai, doesn't have any 
menu buttons at all.  I'll have to rebuild that.  I'm not sure what could 
have gone wrong there.

Still, everything's recoverable.  I owe my family some time now, so I'll leave 
it until morning, but I'm happy now to see that I was nearly there :-)

Thanks again.

Anne

On Friday 20 April 2007, Anne Wilson wrote:
> On Friday 20 April 2007, Wolfgang Wershofen wrote:
> > That's it. I authored the DVD with that changes and tested it in xine -
> > worked flawlessly!
> >
> > Check it out.
>
> Not quite there, I'm afraid.  Mogrify chewed up my buttons images and I
> didn't notice it before authoring :-(  I still have the .xcf file, so I can
> re-do them.
>
Had to come back to it - couldn't leave it alone :-)
> More serious, though, is that the last titleset, Shanghai, doesn't have any
> menu buttons at all.  I'll have to rebuild that.  I'm not sure what could
> have gone wrong there.
>
I've got my png files back (remembered I had a backup).  The 'airport' files 
and the 'main' files had bleed-through, giving them 3 colours rather than the 
2 intended.  Fixed that.

The top level menu is now fine, but I still have a display problem 
with 'airport', and 'shanghai' menu doesn't work at all.  During the spumux 
on both of these I see messages like

WARN: Button y coordinates are odd for button oldtown: 50x131-335x177; they 
may not display properly.

The xml line for this button is

        <button name="oldtown" x0="50" y0="131" x1="335" y1="177"/>

I wonder if the problem is that the buttons are not snapped to grid?  Other 
than that, I can't see what could be wrong.  The very variable length of the 
button names on screen make it difficult to line them up.  Maybe that's it, 
but if it is, I can't think what to do about it.

Time to sleep on it.

Anne

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Anne Wilson schrieb:
> On Friday 20 April 2007, Wolfgang Wershofen wrote:
>> That's it. I authored the DVD with that changes and tested it in xine -
>> worked flawlessly!
>>
>> Check it out.
>>
> Not quite there, I'm afraid.  Mogrify chewed up my buttons images and I didn't 
> notice it before authoring :-(  I still have the .xcf file, so I can re-do 
> them.

Don't worry. We'll get it done before you start your vacation. Promised!
Did you call mogrify just as I described it? If not, ImageMagick-tools
are quite picky about the sequence of options specified.  Please bear in
mind that options are worked on in order left-to-right.

Instead of mogrify, you may use convert, but you'll have to give it an
output filename, e.g. convert main_highlight_bl.png -colors 2
main_high_bl.png.

This will leave your original button mask untouched are write the
results of color reduction to main_high_bl.png.

> 
> More serious, though, is that the last titleset, Shanghai, doesn't have any 
> menu buttons at all.  I'll have to rebuild that.  I'm not sure what could 
> have gone wrong there.

Hm, what you gave me, was Shanghai.avi, so maybe you forgot to convert
Shanghai.avi to an MPEG-file and spumux the button into it? I used
ffmpeg to convert the avi to a DVD-compliant mpeg and muxed the buttons
without problems.

> 
> Still, everything's recoverable.  I owe my family some time now, so I'll leave 
> it until morning, but I'm happy now to see that I was nearly there :-)

You're not almost there. I put my changes and everything you gave me on
my own webspace. You may download it from
http://www.wershofen.de/anne/ChinaTest

Please refer to the files there, if you have any questions.

One more thought - or hint:
You did specify all the button coordinates in your spumux xml files. Did
you notice, that spumux has a very good automatism to detect the buttons
defined? There are two parms in spumux xml to control the behaviour of
this autodetection, called "autooutline" and "outlinewidth". Refer to
the main_spu.xml in the above mentioned directory on how to use it.
You may name your buttons according to your liking but don't need to
specify the coordinates. This will save you some hassle to detect the
button coords manually.

hth
Wolfgang
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFGKTI1gUafbxFH+p8RApnOAKCPuBK/S1xAfdyPCX5yWvnKZPZ3xwCeNJbV
vXSBLZVYnImj312ORKnFRNI=
=edrf
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Anne Wilson schrieb:
> Had to come back to it - couldn't leave it alone :-)
>> More serious, though, is that the last titleset, Shanghai, doesn't have any
>> menu buttons at all.  I'll have to rebuild that.  I'm not sure what could
>> have gone wrong there.
>>
> I've got my png files back (remembered I had a backup).  The 'airport' files 
> and the 'main' files had bleed-through, giving them 3 colours rather than the 
> 2 intended.  Fixed that.
> 
> The top level menu is now fine, but I still have a display problem 
> with 'airport', and 'shanghai' menu doesn't work at all.  During the spumux 
> on both of these I see messages like
> 
> WARN: Button y coordinates are odd for button oldtown: 50x131-335x177; they 
> may not display properly.
> 
> The xml line for this button is
> 
>         <button name="oldtown" x0="50" y0="131" x1="335" y1="177"/>
> 
> I wonder if the problem is that the buttons are not snapped to grid?  Other 
> than that, I can't see what could be wrong.  The very variable length of the 
> button names on screen make it difficult to line them up.  Maybe that's it, 
> but if it is, I can't think what to do about it.
> 
> Time to sleep on it.

Please refer to my previous posting about using spumux autodetection
feature. Your button outlines are perfect to be recognized and thus, you
don't need to specify the coords manually.

hth
Wolfgang
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFGKTLagUafbxFH+p8RAgBOAKCELAcIZ7ZMXLJDojBfAMZg0YjOKwCg2i7p
oh4dFeou1O1FmKJHfmlbgzQ=
=mSOI
-----END PGP SIGNATURE-----

On Friday 20 April 2007, Wolfgang Wershofen wrote:
> Anne Wilson schrieb:
> > On Friday 20 April 2007, Wolfgang Wershofen wrote:
> >> That's it. I authored the DVD with that changes and tested it in xine -
> >> worked flawlessly!
> >>
> >> Check it out.
> >
> > Not quite there, I'm afraid.  Mogrify chewed up my buttons images and I
> > didn't notice it before authoring :-(  I still have the .xcf file, so I
> > can re-do them.
>
> Don't worry. We'll get it done before you start your vacation. Promised!
> Did you call mogrify just as I described it?=20

I did.  In fact, to make sure, I just copied your command and pasted it, th=
en=20
edited the filename as necessary.

> If not, ImageMagick-tools=20
> are quite picky about the sequence of options specified.  Please bear in
> mind that options are worked on in order left-to-right.
>
> Instead of mogrify, you may use convert, but you'll have to give it an
> output filename, e.g. convert main_highlight_bl.png -colors 2
> main_high_bl.png.
>
> This will leave your original button mask untouched are write the
> results of color reduction to main_high_bl.png.
>
Worth knowing, thanks.  What I actually did was open the mask files in Gimp=
=20
and edit the colourmap.

> > More serious, though, is that the last titleset, Shanghai, doesn't have
> > any menu buttons at all.  I'll have to rebuild that.  I'm not sure what
> > could have gone wrong there.
>
> Hm, what you gave me, was Shanghai.avi, so maybe you forgot to convert
> Shanghai.avi to an MPEG-file and spumux the button into it? I used
> ffmpeg to convert the avi to a DVD-compliant mpeg and muxed the buttons
> without problems.
>
That gave me the clue I needed.  If you could get it right from the avi and=
 I=20
couldn't from the mpg (sorry I uploaded the wrong file, but it's=20
serendipity :-) ), then the mpg was wrong.  I rebuilt the mpg re-ran spumux=
=20
and built again.  This time there were no problems.

> > Still, everything's recoverable.  I owe my family some time now, so I'll
> > leave it until morning, but I'm happy now to see that I was nearly there
> > :-)
>
> You're not almost there. I put my changes and everything you gave me on
> my own webspace. You may download it from
> http://www.wershofen.de/anne/ChinaTest
>
> Please refer to the files there, if you have any questions.
>
> One more thought - or hint:
> You did specify all the button coordinates in your spumux xml files. Did
> you notice, that spumux has a very good automatism to detect the buttons
> defined? There are two parms in spumux xml to control the behaviour of
> this autodetection, called "autooutline" and "outlinewidth". Refer to
> the main_spu.xml in the above mentioned directorgpgkeys: key
> 81469F6F1147FA9F not found on keyserver y on how to use it.
> You may name your buttons according to your liking but don't need to
> specify the coordinates. This will save you some hassle to detect the
> button coords manually.
>
I've altered the _spu.xml files to use 'autooutline' and 'outlinewidth'.  I=
t=20
worked well.

Well - I have a playable DVD structure, though not correct yet :-)  The two=
=20
that I've re-built - airport and shanghai - have all the buttons mapped the=
=20
wrong way round.  'Menu' plays chapter 1, 'Chapter 1' returns to the menu. =
=20
The penultimate button playes chapter 2 and so on.  I'll work on that next.

The *_spu.xml files all list the buttons in reverse order.  I wonder if tha=
t's=20
significant?  I'll copy the file elsewhere, then try editing one and see if=
=20
that makes the difference.

I do feel that I'm beginning to understand more now, thanks to you.  Once I=
've=20
sorted the button order out, the next improvement would be to have a 'Play=
=20
All' button in each titleset.  Let's see if I have the strategy right for=20
this.

Consider the titles referenced by 'Shanghai' from the main menu.

The menu set would require two titlesets.  The first titleset would be as a=
t=20
present, and 'Play All' would simply jump to chapter 1.  The second titlese=
t=20
would need a 'call menu entry root;', presumably in a <post> tag.

Does that sound right, or am I being too simplistic?

On Saturday 21 April 2007, Anne Wilson wrote:
>
> Well - I have a playable DVD structure, though not correct yet :-)  The t=
wo
> that I've re-built - airport and shanghai - have all the buttons mapped t=
he
> wrong way round.  'Menu' plays chapter 1, 'Chapter 1' returns to the menu.
> The penultimate button playes chapter 2 and so on.  I'll work on that nex=
t.
>
> The *_spu.xml files all list the buttons in reverse order.  I wonder if
> that's significant?  I'll copy the file elsewhere, then try editing one a=
nd
> see if that makes the difference.
>
It did.   They are now correct.  The original xml files were created by the=
=20
gimp plugin.  I'll have to watch that.

> I do feel that I'm beginning to understand more now, thanks to you.  Once
> I've sorted the button order out, the next improvement would be to have a
> 'Play All' button in each titleset.  Let's see if I have the strategy rig=
ht
> for this.
>
> Consider the titles referenced by 'Shanghai' from the main menu.
>
Oops - missed part of the statement:

> The menu set would require two titlesets.  The first titleset would be as
> at present, and 'Play All' would simply jump to chapter 1,=20
continuing unbroken through the chapters. =20
> The second=20
> titleset would need a 'call menu entry root;', presumably in a <post> tag
after each scene.
>
> Does that sound right, or am I being too simplistic?

Anne

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Anne Wilson schrieb:
>> One more thought - or hint:
>> You did specify all the button coordinates in your spumux xml files. Did
>> you notice, that spumux has a very good automatism to detect the buttons
>> defined? There are two parms in spumux xml to control the behaviour of
>> this autodetection, called "autooutline" and "outlinewidth". Refer to
>> the main_spu.xml in the above mentioned directorgpgkeys: key
>> 81469F6F1147FA9F not found on keyserver y on how to use it.
>> You may name your buttons according to your liking but don't need to
>> specify the coordinates. This will save you some hassle to detect the
>> button coords manually.
>>
> I've altered the _spu.xml files to use 'autooutline' and 'outlinewidth'.  It 
> worked well.
> 
> Well - I have a playable DVD structure, though not correct yet :-)  The two 
> that I've re-built - airport and shanghai - have all the buttons mapped the 
> wrong way round.  'Menu' plays chapter 1, 'Chapter 1' returns to the menu.  
> The penultimate button playes chapter 2 and so on.  I'll work on that next.
> 
> The *_spu.xml files all list the buttons in reverse order.  I wonder if that's 
> significant?  I'll copy the file elsewhere, then try editing one and see if 
> that makes the difference.

The order, in which buttons are automatically detected by spumux depends
on what you specify in "autoorder". If you say "rows" there, then
buttons are detected left to right and top to bottom. With "columns"
you'll have top-bottom and then left-right.
If you have any button naming in your xml, then spumux assigns the
button names in the xml top-down to the buttons in order it detects
them. So you simply have to change the order of the <button>-tags in
your spumux xml to reflect to detection order.

> 
> I do feel that I'm beginning to understand more now, thanks to you.  Once I've 
> sorted the button order out, the next improvement would be to have a 'Play 
> All' button in each titleset.  Let's see if I have the strategy right for 
> this.
> 
> Consider the titles referenced by 'Shanghai' from the main menu.
> 
> The menu set would require two titlesets.  The first titleset would be as at 
> present, and 'Play All' would simply jump to chapter 1.  The second titleset 
> would need a 'call menu entry root;', presumably in a <post> tag.
> 
> Does that sound right, or am I being too simplistic?

Only a bit. ;-)

The xml, you sent me via PM, is not working:

<titles>
	...
	<pgc>
		<vob file="scene2.mpg"></vob>
		<post>call menu entry root;</post>
		<vob file="scene3.mpg"></vob>
		<post>call menu entry root;</post>
		...
	</pgc>
</titles>

The <post> instruction may only be specified once within a <pgc>, so
it's a bit more complicated to achieve your aims: We need cells!

Cells are a means to separate parts of an mpeg file to be treated
separately. A bit similar to chapters, but more flexible and with the
option, to put a single command instruction after each cell.

So, to convert the faulty xml above into something working to your
expectations, you'll have to write it like that:

<titles>
	...
	<pgc>
		<vob file="scene2.mpg">
			<cells start="0:00:00.000" chapter="1">
				call menu entry root;
			</cells>
		</vob>
		<vob file="scene3.mpg">
			<cells start="0:00:00.000" chapter="1">
				call menu entry root;
			</cells>
		</vob>
		...
		<post>call menu entry root;</post>
	</pgc>
</titles>

Within a <cell>-tag you specify the start-time (related to the parent
<vob>-file) and an optional end-time (ommited here, since you want to
have the complete <vob>-file). With "chapter=0|1" you may mark you cell
as a chapter ("1") oder not ("0").
Within a cell, you may include one command statement which is executed
after the cell has been played. This works for all but the last cell,
that's why you may not forget to specify an overall <post>-instruction
to return after the last cell has been played.

That way, you will get a working DVD with the navigation, you wanted.
With a more advanced technique, there would have been no need to specify
two titles, but I guess we should leave this alone until you get back
from your holiday. ;-)

hth
Wolfgang
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFGK1WXgUafbxFH+p8RAvwHAKC/x4urXxfi6l7ENvos1OK6OMlZxQCePK/S
+6+Ymkl4m0fQWdIAXcx5U0A=
=8Qsn
-----END PGP SIGNATURE-----

On Sunday 22 April 2007, Wolfgang Wershofen wrote:
> Anne Wilson schrieb:
>
> The <post> instruction may only be specified once within a <pgc>, so
> it's a bit more complicated to achieve your aims: We need cells!
>
> Cells are a means to separate parts of an mpeg file to be treated
> separately. A bit similar to chapters, but more flexible and with the
> option, to put a single command instruction after each cell.
>
> So, to convert the faulty xml above into something working to your
> expectations, you'll have to write it like that:
>
> <titles>
> 	...
> 	<pgc>
> 		<vob file=3D"scene2.mpg">
> 			<cells start=3D"0:00:00.000" chapter=3D"1">
> 				call menu entry root;
> 			</cells>
> 		</vob>
> 		<vob file=3D"scene3.mpg">
> 			<cells start=3D"0:00:00.000" chapter=3D"1">
> 				call menu entry root;
> 			</cells>
> 		</vob>
> 		...
> 		<post>call menu entry root;</post>
> 	</pgc>
> </titles>
>
> Within a <cell>-tag you specify the start-time (related to the parent
> <vob>-file) and an optional end-time (ommited here, since you want to
> have the complete <vob>-file). With "chapter=3D0|1" you may mark you cell
> as a chapter ("1") oder not ("0").
> Within a cell, you may include one command statement which is executed
> after the cell has been played. This works for all but the last cell,
> that's why you may not forget to specify an overall <post>-instruction
> to return after the last cell has been played.
>
> That way, you will get a working DVD with the navigation, you wanted.
> With a more advanced technique, there would have been no need to specify
> two titles, but I guess we should leave this alone until you get back
> from your holiday. ;-)
>
Hi, Wolfgang.  Sorry for the delay in continuing this.  After two weeks=20
holiday there is a great deal of catching up to do.  Now I'm trying to get =
my=20
mind back into this particular groove :-)

I'm not sure that I understand your sentence "With "chapter=3D0|1" you may =
mark=20
you cell as a chapter ("1") oder not ("0")."

Is this what you mean:

	<titleset>
		<menus>
			<pgc entry=3D"root" pause=3D"inf">
				<vob file=3D"airport.mpg"></vob>
				<button name=3D"Shanghai">jump title 1 chapter 1;</button>
				<button name=3D"Menu">jump vmgm menu entry title;</button>
			</pgc>
		</menus>
		<titles>
			<pgc>
				<vob file=3D"scene1.mpg"/>
				<post>call menu entry root;</post>
			</pgc>
		</titles>
	</titleset>
	<titleset>
		<menus>
			<pgc entry=3D"root" pause=3D"inf">
				<vob file =3D"yunan.mpg"></vob>
				<button name=3D"all">jump title 2 chapter 1;</button>
				<button name=3D"1kunming">jump title 3 chapter 1;</button>
				<button name=3D"2sforest">jump title 3 chapter 2;</button>
				<button name=3D"3lijiang">jump title 3 chapter 3;</button>
				<button name=3D"4sjtm">   jump title 3 chapter 4;</button>
				<button name=3D"5naxi">   jump title 3 chapter 5;</button>
				<button name=3D"6temple"> jump title 3 chapter 6;</button>
				<button name=3D"7lijiang">jump title 3 chapter 7;</button>
				<button name=3D"8kunming">jump title 3 chapter 8;</button>
				<button name=3D"9menu">jump vmgm menu entry title;</button>
			</pgc>
		</menus>
		<titles>
			<pgc>
				<vob file=3D"scene2.mpg"></vob>
				<vob file=3D"scene3.mpg"></vob>
				<vob file=3D"scene4.mpg"></vob>
				<vob file=3D"scene5.mpg"></vob>
				<vob file=3D"scene6.mpg"></vob>
				<vob file=3D"scene7.mpg"></vob>
				<vob file=3D"scene8.mpg"></vob>
				<vob file=3D"scene9.mpg"></vob>
				<post>jump vmgm menu entry title;</post>
			</pgc>
		</titles>=20
		<titles>
			<pgc>
				<button name=3D"all">jump title 2 chapter 1;</button>
				<vob file=3D"scene2.mpg">
					<cells start=3D"0:00:00.000" chapter=3D"1">
						call menu entry root;
					</cells>
				</vob>
				<vob file=3D"scene3.mpg">
					<cells start=3D"0:00:00.000" chapter=3D"1">
						call menu entry root;
					</cells>
				</vob>
				<vob file=3D"scene4.mpg">
					<cells start=3D"0:00:00.000" chapter=3D"1">
						call menu entry root;
					</cells>
				</vob>
				<vob file=3D"scene5.mpg">
					<cells start=3D"0:00:00.000" chapter=3D"1">
						call menu entry root;
					</cells>
				</vob>
				<vob file=3D"scene6.mpg">
					<cells start=3D"0:00:00.000" chapter=3D"1">
						call menu entry root;
					</cells>
				</vob>
				<vob file=3D"scene7.mpg">
					<cells start=3D"0:00:00.000" chapter=3D"1">
						call menu entry root;
					</cells>
				</vob>
				<vob file=3D"scene8.mpg">
					<cells start=3D"0:00:00.000" chapter=3D"1">
						call menu entry root;
					</cells>
				</vob>
				<vob file=3D"scene9.mpg"></vob>
				<post>call menu entry root;</post>
			</pgc>
		</titles>=20
	</titleset>

I can't remember whether titles are numbered within the titleset, in which=
=20
case I shall have to change the 2's to 1's and 3's to 2's.

I'll experiment a bit, while you look at this, thanks.

Anne

On Thursday 17 May 2007, Anne Wilson wrote:
> On Sunday 22 April 2007, Wolfgang Wershofen wrote:
> > Anne Wilson schrieb:
> >
> > The <post> instruction may only be specified once within a <pgc>, so
> > it's a bit more complicated to achieve your aims: We need cells!
> >
> > Cells are a means to separate parts of an mpeg file to be treated
> > separately. A bit similar to chapters, but more flexible and with the
> > option, to put a single command instruction after each cell.
> >
> > So, to convert the faulty xml above into something working to your
> > expectations, you'll have to write it like that:
> >
> > <titles>
> > 	...
> > 	<pgc>
> > 		<vob file=3D"scene2.mpg">
> > 			<cells start=3D"0:00:00.000" chapter=3D"1">
> > 				call menu entry root;
> > 			</cells>
> > 		</vob>
> > 		<vob file=3D"scene3.mpg">
> > 			<cells start=3D"0:00:00.000" chapter=3D"1">
> > 				call menu entry root;
> > 			</cells>
> > 		</vob>
> > 		...
> > 		<post>call menu entry root;</post>
> > 	</pgc>
> > </titles>
> >
> > Within a <cell>-tag you specify the start-time (related to the parent
> > <vob>-file) and an optional end-time (ommited here, since you want to
> > have the complete <vob>-file). With "chapter=3D0|1" you may mark you ce=
ll
> > as a chapter ("1") oder not ("0").
> > Within a cell, you may include one command statement which is executed
> > after the cell has been played. This works for all but the last cell,
> > that's why you may not forget to specify an overall <post>-instruction
> > to return after the last cell has been played.
> >
> > That way, you will get a working DVD with the navigation, you wanted.
> > With a more advanced technique, there would have been no need to specify
> > two titles, but I guess we should leave this alone until you get back
> > from your holiday. ;-)
>
> Hi, Wolfgang.  Sorry for the delay in continuing this.  After two weeks
> holiday there is a great deal of catching up to do.  Now I'm trying to get
> my mind back into this particular groove :-)
>
> I'm not sure that I understand your sentence "With "chapter=3D0|1" you may
> mark you cell as a chapter ("1") oder not ("0")."
>
> Is this what you mean:
>
> 	<titleset>
> 		<menus>
> 			<pgc entry=3D"root" pause=3D"inf">
> 				<vob file=3D"airport.mpg"></vob>
> 				<button name=3D"Shanghai">jump title 1 chapter 1;</button>
> 				<button name=3D"Menu">jump vmgm menu entry title;</button>
> 			</pgc>
> 		</menus>
> 		<titles>
> 			<pgc>
> 				<vob file=3D"scene1.mpg"/>
> 				<post>call menu entry root;</post>
> 			</pgc>
> 		</titles>
> 	</titleset>
> 	<titleset>
> 		<menus>
> 			<pgc entry=3D"root" pause=3D"inf">
> 				<vob file =3D"yunan.mpg"></vob>
> 				<button name=3D"all">jump title 2 chapter 1;</button>
> 				<button name=3D"1kunming">jump title 3 chapter 1;</button>
> 				<button name=3D"2sforest">jump title 3 chapter 2;</button>
> 				<button name=3D"3lijiang">jump title 3 chapter 3;</button>
> 				<button name=3D"4sjtm">   jump title 3 chapter 4;</button>
> 				<button name=3D"5naxi">   jump title 3 chapter 5;</button>
> 				<button name=3D"6temple"> jump title 3 chapter 6;</button>
> 				<button name=3D"7lijiang">jump title 3 chapter 7;</button>
> 				<button name=3D"8kunming">jump title 3 chapter 8;</button>
> 				<button name=3D"9menu">jump vmgm menu entry title;</button>
> 			</pgc>
> 		</menus>
> 		<titles>
> 			<pgc>
> 				<vob file=3D"scene2.mpg"></vob>
> 				<vob file=3D"scene3.mpg"></vob>
> 				<vob file=3D"scene4.mpg"></vob>
> 				<vob file=3D"scene5.mpg"></vob>
> 				<vob file=3D"scene6.mpg"></vob>
> 				<vob file=3D"scene7.mpg"></vob>
> 				<vob file=3D"scene8.mpg"></vob>
> 				<vob file=3D"scene9.mpg"></vob>
> 				<post>jump vmgm menu entry title;</post>
> 			</pgc>
> 		</titles>
> 		<titles>
> 			<pgc>
> 				<button name=3D"all">jump title 2 chapter 1;</button>
> 				<vob file=3D"scene2.mpg">
> 					<cells start=3D"0:00:00.000" chapter=3D"1">
> 						call menu entry root;
> 					</cells>
> 				</vob>
> 				<vob file=3D"scene3.mpg">
> 					<cells start=3D"0:00:00.000" chapter=3D"1">
> 						call menu entry root;
> 					</cells>
> 				</vob>
> 				<vob file=3D"scene4.mpg">
> 					<cells start=3D"0:00:00.000" chapter=3D"1">
> 						call menu entry root;
> 					</cells>
> 				</vob>
> 				<vob file=3D"scene5.mpg">
> 					<cells start=3D"0:00:00.000" chapter=3D"1">
> 						call menu entry root;
> 					</cells>
> 				</vob>
> 				<vob file=3D"scene6.mpg">
> 					<cells start=3D"0:00:00.000" chapter=3D"1">
> 						call menu entry root;
> 					</cells>
> 				</vob>
> 				<vob file=3D"scene7.mpg">
> 					<cells start=3D"0:00:00.000" chapter=3D"1">
> 						call menu entry root;
> 					</cells>
> 				</vob>
> 				<vob file=3D"scene8.mpg">
> 					<cells start=3D"0:00:00.000" chapter=3D"1">
> 						call menu entry root;
> 					</cells>
> 				</vob>
> 				<vob file=3D"scene9.mpg"></vob>
> 				<post>call menu entry root;</post>
> 			</pgc>
> 		</titles>
> 	</titleset>
>
> I can't remember whether titles are numbered within the titleset, in which
> case I shall have to change the 2's to 1's and 3's to 2's.
>
> I'll experiment a bit, while you look at this, thanks.
>
I've had no success so far.  (I removed the accidentally pasted button line=
 in=20
<titles>).  I keep getting=20

STAT: fixed 3 VOBUS
STAT: fixed 183 VOBUS
ERR:  Titles already defined

As far as I can see I have to define the titles twice - once for playing=20
straight through then returning to menu, and once returning to menu after=20
each chapter.  I suspect that I have to use one <titles> </titles> wrapper=
=20
over both sets, but two <pcg> sets (i.e. drop one </titles> <titles>).  If=
=20
that's so, how do I refer to each <pcg> set?

Anne

On 5/20/07, Anne Wilson <cannewilson@...> wrote:
> I've had no success so far.  (I removed the accidentally pasted button line in
> <titles>).  I keep getting
>
> STAT: fixed 3 VOBUS
> STAT: fixed 183 VOBUS
> ERR:  Titles already defined
>
> As far as I can see I have to define the titles twice - once for playing
> straight through then returning to menu, and once returning to menu after
> each chapter.  I suspect that I have to use one <titles> </titles> wrapper
> over both sets, but two <pcg> sets (i.e. drop one </titles> <titles>).  If
> that's so, how do I refer to each <pcg> set?

Each new <pgc> tag is seen as a title (and each <vob> inside a new
chapter), and each titleset starts with title 1 (and each title from
chapter 1). If you put your 'play all' block inside the first pgc, it
will be title 1 of that titleset. Each individual-play scene needs its
own <pgc> and will increment from there: title 2, title 3, ...

Joe

On Monday 21 May 2007, Joe Friedrichsen wrote:
> On 5/20/07, Anne Wilson <cannewilson@...> wrote:
> > I've had no success so far.  (I removed the accidentally pasted button
> > line in <titles>).  I keep getting
> >
> > STAT: fixed 3 VOBUS
> > STAT: fixed 183 VOBUS
> > ERR:  Titles already defined
> >
> > As far as I can see I have to define the titles twice - once for playing
> > straight through then returning to menu, and once returning to menu aft=
er
> > each chapter.  I suspect that I have to use one <titles> </titles>
> > wrapper over both sets, but two <pcg> sets (i.e. drop one </titles>
> > <titles>).  If that's so, how do I refer to each <pcg> set?
>
> Each new <pgc> tag is seen as a title (and each <vob> inside a new
> chapter), and each titleset starts with title 1 (and each title from
> chapter 1). If you put your 'play all' block inside the first pgc, it
> will be title 1 of that titleset. Each individual-play scene needs its
> own <pgc> and will increment from there: title 2, title 3, ...
>
Thanks, Joe.  I thought I had understood you, but I'm still getting

STAT: fixed 3 VOBUS
STAT: fixed 183 VOBUS
ERR:  Unknown chapter cmd '2'


Here is the relevant portion of the .xml - can you tell me where I'm=20
misunderstanding?

	<titleset>
		<menus>
			<pgc entry=3D"root" pause=3D"inf">
				<vob file=3D"airport.mpg"></vob>
				<button name=3D"Shanghai">jump title 1 chapter 1;</button>
				<button name=3D"Menu">jump vmgm menu entry title;</button>
			</pgc>
		</menus>
		<titles>
			<pgc>
				<vob file=3D"scene1.mpg"/>
				<post>call menu entry root;</post>
			</pgc>
		</titles>
	</titleset>
	<titleset>
		<menus>
			<pgc entry=3D"root" pause=3D"inf">
				<vob file =3D"yunan.mpg"></vob>
				<button name=3D"all">jump title 1 chapter 1;</button>
				<button name=3D"1kunming">jump title 2 chapter 1;</button>
				<button name=3D"2sforest">jump title 3 chapter 1;</button>
				<button name=3D"3lijiang">jump title 4 chapter 1;</button>
				<button name=3D"4sjtm">   jump title 5 chapter 1;</button>
				<button name=3D"5naxi">   jump title 6 chapter 1;</button>
				<button name=3D"6temple"> jump title 7 chapter 1;</button>
				<button name=3D"7lijiang">jump title 8 chapter 1;</button>
				<button name=3D"8kunming">jump title 9 chapter 1;</button>
				<button name=3D"9menu">jump vmgm menu entry title;</button>
			</pgc>
		</menus>
		<titles>
			<pgc entry=3D"root">
				<vob file=3D"scene2.mpg"></vob>
				<vob file=3D"scene3.mpg"></vob>
				<vob file=3D"scene4.mpg"></vob>
				<vob file=3D"scene5.mpg"></vob>
				<vob file=3D"scene6.mpg"></vob>
				<vob file=3D"scene7.mpg"></vob>
				<vob file=3D"scene8.mpg"></vob>
				<vob file=3D"scene9.mpg"></vob>
				<post>jump vmgm menu entry title;</post>
			</pgc>
			<pgc>
				<vob file=3D"scene2.mpg">
					<cell start=3D"0:00:00.000" chapter=3D"1">
						call menu entry root;
					</cell>
				</vob>
			</pgc>
			<pgc>
				<vob file=3D"scene3.mpg">
					<cell start=3D"0:00:00.000" chapter=3D"2">
						call menu entry root;
					</cell>
				</vob>
			</pgc>
			<pgc>
				<vob file=3D"scene4.mpg">
					<cell start=3D"0:00:00.000" chapter=3D"3">
						call menu entry root;
					</cell>
				</vob>
			</pgc>


Thanks

Anne

On 5/21/07, Anne Wilson <cannewilson@...> wrote:
> Thanks, Joe.  I thought I had understood you, but I'm still getting
>
> STAT: fixed 3 VOBUS
> STAT: fixed 183 VOBUS
> ERR:  Unknown chapter cmd '2'
>
>
> Here is the relevant portion of the .xml - can you tell me where I'm
> misunderstanding?

Under a <cell> tag, the chapter element doesn't set the chapter
number, but whether or not that cell is a chapter. It's a boolean
(true/false), so the only acceptable values for chapter (under <cell>)
are 0 (not a new chapter) and 1 (new chapter). The man page says:

<cell [start="timestamp"] [end="timestamp"] [chapter="1|on|yes" |
program="1|on|yes"] [pause="seconds|inf"] />

[[ Besides, each of your single-play vobs were in separate pgc's, so
the chapter count starts over at 1 each time (since each pgc is a new
title). It doesn't make sense to increment the chapters between
titles. ]]

Change all of your non-1's to 1, and I think it'll work.

Joe

On Monday 21 May 2007, Joe Friedrichsen wrote:
>
> Under a <cell> tag, the chapter element doesn't set the chapter
> number, but whether or not that cell is a chapter. It's a boolean
> (true/false), so the only acceptable values for chapter (under <cell>)
> are 0 (not a new chapter) and 1 (new chapter). The man page says:
>
> <cell [start=3D"timestamp"] [end=3D"timestamp"] [chapter=3D"1|on|yes" |
> program=3D"1|on|yes"] [pause=3D"seconds|inf"] />
>
> [[ Besides, each of your single-play vobs were in separate pgc's, so
> the chapter count starts over at 1 each time (since each pgc is a new
> title). It doesn't make sense to increment the chapters between
> titles. ]]
>
> Change all of your non-1's to 1, and I think it'll work.
>
Not quite.  I'm a little nearer, but I'm tying myself in knots trying to=20
understand 'call' and 'jump' commands.  The man page doesn't help much.

Each time I got an error I tried to correct it, and it would seem as though=
 I=20
got a little further, or sometimes just a different error message.

Let's start again.

Main menu has three buttons, to three titlesets.

Button 1 takes to a screen with two buttons, i.e. play scene1.mpg and back =
to=20
main menu.

Button 2 goes to a screen with 10 buttons, i.e. play all, play scene2.mpg .=
=2E.=20
play scene9.mpg and back to main menu.  I have two titlesets here - the fir=
st=20
lists the mpgs, scene2.mpg .. scene9.mpg, and ends

				<post>call vmgm menu entry title;</post>

Individual scenes are handled in cells eg

			<pgc>
				<vob file=3D"scene8.mpg">
					<cell start=3D"0:00:00.000" chapter=3D"1">
						call menu entry root;
					</cell>
				</vob>
			</pgc>

scene9.mpg should also return to that titleset's menu, but I'm not there ye=
t. =20
The current entry for this is=20

			<pgc>
				<vob file=3D"scene9.mpg"></vob>
				<post>call menu entry title;</post>
			</pgc>

Everything processes as it should until the end of scene9.mpg.  The latest=
=20
error message is

ERR:  Cannot find PGC with entry title
ERR:  in VTS pgc 7, <post>

Changing 'title' to 'root' produced

ERR:  Cannot 'call' a menu from another menu, use 'jump' instead
ERR:  in VTSM pgc 0, button 9menu

I'm going round in circles.  I know it's because I don't understand what I'=
m=20
doing.  <sigh>  I do appreciate all the help I'm getting.

Anne

On 5/22/07, Anne Wilson <cannewilson@...> wrote:
> Not quite.  I'm a little nearer, but I'm tying myself in knots trying to
> understand 'call' and 'jump' commands.  The man page doesn't help much.

Both commands have the same effect: they move playback to a certain
place (either to a menu or to a title/chapter). 'call' can only be
used in the <titles> section of the xml and 'jump' only in the <menus>
section. In other words, videos can only 'call' and menus can only
'jump'.

Looking at your most recent (uninterrupted) xml file snippet, I
noticed that you have a <pgc entry="root"> under a <titles> tag for
the group of vobs that comprise the 'play all' title. That is
certainly not allowed (only menu <pgc>'s can have entry attributes,
see the man page). This may be a small bug on dvdauthor's part to not
point out that syntax error, but since it's explained in the man page,
user beware :-)

Please post the entirety of your xml file, and we'll look over it
section by section. Also, please describe what the third button on
your main menu is supposed to do (you neglected to mention it).

Thanks :-)
Joe

On Wednesday 23 May 2007, Joe Friedrichsen wrote:
> On 5/22/07, Anne Wilson <cannewilson@...> wrote:
> > Not quite.  I'm a little nearer, but I'm tying myself in knots trying to
> > understand 'call' and 'jump' commands.  The man page doesn't help much.
>
> Both commands have the same effect: they move playback to a certain
> place (either to a menu or to a title/chapter). 'call' can only be
> used in the <titles> section of the xml and 'jump' only in the <menus>
> section. In other words, videos can only 'call' and menus can only
> 'jump'.
>
> Looking at your most recent (uninterrupted) xml file snippet, I
> noticed that you have a <pgc entry=3D"root"> under a <titles> tag for
> the group of vobs that comprise the 'play all' title. That is
> certainly not allowed (only menu <pgc>'s can have entry attributes,
> see the man page). This may be a small bug on dvdauthor's part to not
> point out that syntax error, but since it's explained in the man page,
> user beware :-)
>
> Please post the entirety of your xml file, and we'll look over it
> section by section. Also, please describe what the third button on
> your main menu is supposed to do (you neglected to mention it).
>
To start at the end - the third button handles more titles in exactly the s=
ame=20
way as the second button.  I haven't mentioned it much because once the=20
problem is solved for the second set of titles, the same solution will hand=
le=20
the last one.

Here's the complete file

<dvdauthor dest=3D"/home/anne/recordings/Video/China2001_1">
	<vmgm>
		<menus>
			<video format=3D"pal">
			</video>
			<pgc entry=3D"title" pause=3D"inf">
				<vob file=3D"main.mpg"></vob>
				<button name=3D"1Shanghai">jump titleset 1 menu;</button>
				<button name=3D"2Yunan">jump titleset 2 menu;</button>
				<button name=3D"3Shanghai">jump titleset 3 menu;</button>
			</pgc>
		</menus>
</vmgm>
	<titleset>
		<menus>
			<pgc entry=3D"root" pause=3D"inf">
				<vob file=3D"airport.mpg"></vob>
				<button name=3D"Shanghai">jump title 1 chapter 1;</button>
				<button name=3D"Menu">jump vmgm menu entry title;</button>
			</pgc>
		</menus>
		<titles>
			<pgc>
				<vob file=3D"scene1.mpg"/>
				<post>call menu entry root;</post>
			</pgc>
		</titles>
	</titleset>
	<titleset>
		<menus>
			<pgc entry=3D"root" pause=3D"inf">
				<vob file =3D"yunan.mpg"></vob>
				<button name=3D"all">jump title 1 chapter 1;</button>
				<button name=3D"1kunming">jump title 2 chapter 1;</button>
				<button name=3D"2sforest">jump title 3 chapter 1;</button>
				<button name=3D"3lijiang">jump title 4 chapter 1;</button>
				<button name=3D"4sjtm">   jump title 5 chapter 1;</button>
				<button name=3D"5naxi">   jump title 6 chapter 1;</button>
				<button name=3D"6temple"> jump title 7 chapter 1;</button>
				<button name=3D"7lijiang">jump title 8 chapter 1;</button>
				<button name=3D"8kunming">jump title 9 chapter 1;</button>
				<button name=3D"9menu">call vmgm menu entry title;</button>
			</pgc>
		</menus>
		<titles>
			<pgc>
				<vob file=3D"scene2.mpg"></vob>
				<vob file=3D"scene3.mpg"></vob>
				<vob file=3D"scene4.mpg"></vob>
				<vob file=3D"scene5.mpg"></vob>
				<vob file=3D"scene6.mpg"></vob>
				<vob file=3D"scene7.mpg"></vob>
				<vob file=3D"scene8.mpg"></vob>
				<vob file=3D"scene9.mpg"></vob>
				<post>call vmgm menu entry title;</post>
			</pgc>
			<pgc>
				<vob file=3D"scene2.mpg">
					<cell start=3D"0:00:00.000" chapter=3D"1">
						call menu entry root;
					</cell>
				</vob>
			</pgc>
			<pgc>
				<vob file=3D"scene3.mpg">
					<cell start=3D"0:00:00.000" chapter=3D"1">
						call menu entry root;
					</cell>
				</vob>
			</pgc>
			<pgc>
				<vob file=3D"scene4.mpg">
					<cell start=3D"0:00:00.000" chapter=3D"1">
						call menu entry root;
					</cell>
				</vob>
			</pgc>
			<pgc>
				<vob file=3D"scene5.mpg">
					<cell start=3D"0:00:00.000" chapter=3D"1">
						call menu entry root;
					</cell>
				</vob>
			</pgc>
			<pgc>
				<vob file=3D"scene6.mpg">
					<cell start=3D"0:00:00.000" chapter=3D"1">
						call menu entry root;
					</cell>
				</vob>
			</pgc>
			<pgc>
				<vob file=3D"scene7.mpg">
					<cell start=3D"0:00:00.000" chapter=3D"1">
						call menu entry root;
					</cell>
				</vob>
			</pgc>
			<pgc>
				<vob file=3D"scene8.mpg">
					<cell start=3D"0:00:00.000" chapter=3D"1">
						call menu entry root;
					</cell>
				</vob>
			</pgc>
			<pgc>
				<vob file=3D"scene9.mpg"></vob>
				<post>call menu entry root;</post>
			</pgc>
		</titles>=20
	</titleset>
	<titleset>
		<menus>
			<pgc entry=3D"root" pause=3D"inf">
				<vob file=3D"shanghai.mpg"></vob>
				<button name=3D"all">jump title 2 chapter 1;</button>
				<button name=3D"children">jump title 1 chapter 1;</button>
				<button name=3D"oldtown"> jump title 1 chapter 2;</button>
				<button name=3D"shopping">jump title 1 chapter 3;</button>
				<button name=3D"bund">    jump title 1 chapter 4;</button>
				<button name=3D"pearls">  jump title 1 chapter 5;</button>
				<button name=3D"circus">  jump title 1 chapter 6;</button>
				<button name=3D"view">    jump title 1 chapter 7;</button>
				<button name=3D"menu">    jump vmgm menu entry title;</button>
			</pgc>
		</menus>
		<titles>
			<pgc>
				<vob file=3D"scene10.mpg"></vob>
				<vob file=3D"scene11.mpg"></vob>
				<vob file=3D"scene12.mpg"></vob>
				<vob file=3D"scene13.mpg"></vob>
				<vob file=3D"scene14.mpg"></vob>
				<vob file=3D"scene15.mpg"></vob>
				<vob file=3D"scene16.mpg"></vob>
				<post>call vmgm menu entry title;</post>
			</pgc>
		</titles>=20
		<titles>
			<pgc>
				<vob file=3D"scene10.mpg">
					<cell start=3D"0:00:00.000" chapter=3D"1">
						call menu entry root;
					</cell>
				</vob>
				<vob file=3D"scene11.mpg">
					<cell start=3D"0:00:00.000" chapter=3D"1">
						call menu entry root;
					</cell>
				</vob>
				<vob file=3D"scene12.mpg">
					<cell start=3D"0:00:00.000" chapter=3D"1">
						call menu entry root;
					</cell>
				</vob>				=09
				<vob file=3D"scene13.mpg">
					<cell start=3D"0:00:00.000" chapter=3D"1">
						call menu entry root;
					</cell>
				</vob>
				<vob file=3D"scene14.mpg">
					<cell start=3D"0:00:00.000" chapter=3D"1">
						call menu entry root;
					</cell>
				</vob>
				<vob file=3D"scene15.mpg">
					<cell start=3D"0:00:00.000" chapter=3D"1">
						call menu entry root;
					</cell>
				</vob>

				<vob file=3D"scene16.mpg"></vob>
				<post>call menu entry title;</post>
			</pgc>
		</titles>=20
	</titleset>
</dvdauthor>

Thanks

Anne

On 5/23/07, Anne Wilson <cannewilson@...> wrote:
> To start at the end - the third button handles more titles in exactly the same
> way as the second button.  I haven't mentioned it much because once the
> problem is solved for the second set of titles, the same solution will handle
> the last one.

Great. Thanks :-)

> Here's the complete file
>
> <dvdauthor dest="/home/anne/recordings/Video/China2001_1">
>         <vmgm>
>                 <menus>
>                         <video format="pal">
>                         </video>
>                         <pgc entry="title" pause="inf">
>                                 <vob file="main.mpg"></vob>
>                                 <button name="1Shanghai">jump titleset 1 menu;</button>
>                                 <button name="2Yunan">jump titleset 2 menu;</button>
>                                 <button name="3Shanghai">jump titleset 3 menu;</button>
>                         </pgc>
>                 </menus>
> </vmgm>
>         <titleset>
>                 <menus>
>                         <pgc entry="root" pause="inf">
>                                 <vob file="airport.mpg"></vob>
>                                 <button name="Shanghai">jump title 1 chapter 1;</button>
>                                 <button name="Menu">jump vmgm menu entry title;</button>
>                         </pgc>
>                 </menus>
>                 <titles>
>                         <pgc>
>                                 <vob file="scene1.mpg"/>
>                                 <post>call menu entry root;</post>
>                         </pgc>
>                 </titles>
>         </titleset>
>         <titleset>
>                 <menus>
>                         <pgc entry="root" pause="inf">
>                                 <vob file ="yunan.mpg"></vob>
>                                 <button name="all">jump title 1 chapter 1;</button>
>                                 <button name="1kunming">jump title 2 chapter 1;</button>
>                                 <button name="2sforest">jump title 3 chapter 1;</button>
>                                 <button name="3lijiang">jump title 4 chapter 1;</button>
>                                 <button name="4sjtm">   jump title 5 chapter 1;</button>
>                                 <button name="5naxi">   jump title 6 chapter 1;</button>
>                                 <button name="6temple"> jump title 7 chapter 1;</button>
>                                 <button name="7lijiang">jump title 8 chapter 1;</button>
>                                 <button name="8kunming">jump title 9 chapter 1;</button>
>                                 <button name="9menu">call vmgm menu entry title;</button>

Menus cannot use call; they can only jump. 9menu's command needs to be 'jump'.

>                         </pgc>
>                 </menus>
>                 <titles>
>                         <pgc>
>                                 <vob file="scene2.mpg"></vob>
>                                 <vob file="scene3.mpg"></vob>
>                                 <vob file="scene4.mpg"></vob>
>                                 <vob file="scene5.mpg"></vob>
>                                 <vob file="scene6.mpg"></vob>
>                                 <vob file="scene7.mpg"></vob>
>                                 <vob file="scene8.mpg"></vob>
>                                 <vob file="scene9.mpg"></vob>
>                                 <post>call vmgm menu entry title;</post>
>                         </pgc>
>                         <pgc>
>                                 <vob file="scene2.mpg">
>                                         <cell start="0:00:00.000" chapter="1">
>                                                 call menu entry root;
>                                         </cell>
>                                 </vob>
>                         </pgc>
>                         <pgc>
>                                 <vob file="scene3.mpg">
>                                         <cell start="0:00:00.000" chapter="1">
>                                                 call menu entry root;
>                                         </cell>
>                                 </vob>
>                         </pgc>
>                         <pgc>
>                                 <vob file="scene4.mpg">
>                                         <cell start="0:00:00.000" chapter="1">
>                                                 call menu entry root;
>                                         </cell>
>                                 </vob>
>                         </pgc>
>                         <pgc>
>                                 <vob file="scene5.mpg">
>                                         <cell start="0:00:00.000" chapter="1">
>                                                 call menu entry root;
>                                         </cell>
>                                 </vob>
>                         </pgc>
>                         <pgc>
>                                 <vob file="scene6.mpg">
>                                         <cell start="0:00:00.000" chapter="1">
>                                                 call menu entry root;
>                                         </cell>
>                                 </vob>
>                         </pgc>
>                         <pgc>
>                                 <vob file="scene7.mpg">
>                                         <cell start="0:00:00.000" chapter="1">
>                                                 call menu entry root;
>                                         </cell>
>                                 </vob>
>                         </pgc>
>                         <pgc>
>                                 <vob file="scene8.mpg">
>                                         <cell start="0:00:00.000" chapter="1">
>                                                 call menu entry root;
>                                         </cell>
>                                 </vob>
>                         </pgc>
>                         <pgc>
>                                 <vob file="scene9.mpg"></vob>
>                                 <post>call menu entry root;</post>
>                         </pgc>
>                 </titles>
>         </titleset>
>         <titleset>
>                 <menus>
>                         <pgc entry="root" pause="inf">
>                                 <vob file="shanghai.mpg"></vob>
>                                 <button name="all">jump title 2 chapter 1;</button>

I don't think that title 2 chapter 1 is the target you intend for
'play all'. Maybe title 1 chapter 1.

>                                 <button name="children">jump title 1 chapter 1;</button>
>                                 <button name="oldtown"> jump title 1 chapter 2;</button>
>                                 <button name="shopping">jump title 1 chapter 3;</button>
>                                 <button name="bund">    jump title 1 chapter 4;</button>
>                                 <button name="pearls">  jump title 1 chapter 5;</button>
>                                 <button name="circus">  jump title 1 chapter 6;</button>
>                                 <button name="view">    jump title 1 chapter 7;</button>
>                                 <button name="menu">    jump vmgm menu entry title;</button>

And maybe these targets need to be updated as well.

>                         </pgc>
>                 </menus>
>                 <titles>
>                         <pgc>
>                                 <vob file="scene10.mpg"></vob>
>                                 <vob file="scene11.mpg"></vob>
>                                 <vob file="scene12.mpg"></vob>
>                                 <vob file="scene13.mpg"></vob>
>                                 <vob file="scene14.mpg"></vob>
>                                 <vob file="scene15.mpg"></vob>
>                                 <vob file="scene16.mpg"></vob>
>                                 <post>call vmgm menu entry title;</post>
>                         </pgc>
>                 </titles>
>                 <titles>
>                         <pgc>
>                                 <vob file="scene10.mpg">
>                                         <cell start="0:00:00.000" chapter="1">
>                                                 call menu entry root;
>                                         </cell>
>                                 </vob>
>                                 <vob file="scene11.mpg">
>                                         <cell start="0:00:00.000" chapter="1">
>                                                 call menu entry root;
>                                         </cell>
>                                 </vob>
>                                 <vob file="scene12.mpg">
>                                         <cell start="0:00:00.000" chapter="1">
>                                                 call menu entry root;
>                                         </cell>
>                                 </vob>
>                                 <vob file="scene13.mpg">
>                                         <cell start="0:00:00.000" chapter="1">
>                                                 call menu entry root;
>                                         </cell>
>                                 </vob>
>                                 <vob file="scene14.mpg">
>                                         <cell start="0:00:00.000" chapter="1">
>                                                 call menu entry root;
>                                         </cell>
>                                 </vob>
>                                 <vob file="scene15.mpg">
>                                         <cell start="0:00:00.000" chapter="1">
>                                                 call menu entry root;
>                                         </cell>
>                                 </vob>
>
>                                 <vob file="scene16.mpg"></vob>
>                                 <post>call menu entry title;</post>
>                         </pgc>
>                 </titles>
>         </titleset>
> </dvdauthor>

What errors do you encounter now?

Joe

Anne Wilson wrote:
> Here's the complete file
> 
OK lets have a look

> <dvdauthor dest="/home/anne/recordings/Video/China2001_1">
> 	<vmgm>
> 		<menus>
> 			<video format="pal">
> 			</video>
> 			<pgc entry="title" pause="inf">
> 				<vob file="main.mpg"></vob>
> 				<button name="1Shanghai">jump titleset 1 menu;</button>
> 				<button name="2Yunan">jump titleset 2 menu;</button>
> 				<button name="3Shanghai">jump titleset 3 menu;</button>
> 			</pgc>
> 		</menus>
> </vmgm>
> 	<titleset>
> 		<menus>
> 			<pgc entry="root" pause="inf">
> 				<vob file="airport.mpg"></vob>
> 				<button name="Shanghai">jump title 1 chapter 1;</button>
> 				<button name="Menu">jump vmgm menu entry title;</button>
> 			</pgc>
> 		</menus>
> 		<titles>
> 			<pgc>
> 				<vob file="scene1.mpg"/>
> 				<post>call menu entry root;</post>
> 			</pgc>
> 		</titles>
> 	</titleset>
> 	<titleset>
> 		<menus>
> 			<pgc entry="root" pause="inf">
> 				<vob file ="yunan.mpg"></vob>
> 				<button name="all">jump title 1 chapter 1;</button>
> 				<button name="1kunming">jump title 2 chapter 1;</button>
> 				<button name="2sforest">jump title 3 chapter 1;</button>
> 				<button name="3lijiang">jump title 4 chapter 1;</button>
> 				<button name="4sjtm">   jump title 5 chapter 1;</button>
> 				<button name="5naxi">   jump title 6 chapter 1;</button>
> 				<button name="6temple"> jump title 7 chapter 1;</button>
> 				<button name="7lijiang">jump title 8 chapter 1;</button>
> 				<button name="8kunming">jump title 9 chapter 1;</button>
> 				<button name="9menu">call vmgm menu entry title;</button>

This should be a 'jump' command, as you can only use 'call' from titles.

> 			</pgc>
> 		</menus>
> 		<titles>
> 			<pgc>
> 				<vob file="scene2.mpg"></vob>
> 				<vob file="scene3.mpg"></vob>
> 				<vob file="scene4.mpg"></vob>
> 				<vob file="scene5.mpg"></vob>
> 				<vob file="scene6.mpg"></vob>
> 				<vob file="scene7.mpg"></vob>
> 				<vob file="scene8.mpg"></vob>
> 				<vob file="scene9.mpg"></vob>
> 				<post>call vmgm menu entry title;</post>
> 			</pgc>
> 			<pgc>
> 				<vob file="scene2.mpg">
> 					<cell start="0:00:00.000" chapter="1">
> 						call menu entry root;
> 					</cell>
> 				</vob>
> 			</pgc>
> 			<pgc>
> 				<vob file="scene3.mpg">
> 					<cell start="0:00:00.000" chapter="1">
> 						call menu entry root;
> 					</cell>
> 				</vob>
> 			</pgc>
> 			<pgc>
> 				<vob file="scene4.mpg">
> 					<cell start="0:00:00.000" chapter="1">
> 						call menu entry root;
> 					</cell>
> 				</vob>
> 			</pgc>
> 			<pgc>
> 				<vob file="scene5.mpg">
> 					<cell start="0:00:00.000" chapter="1">
> 						call menu entry root;
> 					</cell>
> 				</vob>
> 			</pgc>
> 			<pgc>
> 				<vob file="scene6.mpg">
> 					<cell start="0:00:00.000" chapter="1">
> 						call menu entry root;
> 					</cell>
> 				</vob>
> 			</pgc>
> 			<pgc>
> 				<vob file="scene7.mpg">
> 					<cell start="0:00:00.000" chapter="1">
> 						call menu entry root;
> 					</cell>
> 				</vob>
> 			</pgc>
> 			<pgc>
> 				<vob file="scene8.mpg">
> 					<cell start="0:00:00.000" chapter="1">
> 						call menu entry root;
> 					</cell>
> 				</vob>
> 			</pgc>
> 			<pgc>
> 				<vob file="scene9.mpg"></vob>
> 				<post>call menu entry root;</post>
> 			</pgc>
> 		</titles> 
> 	</titleset>
> 	<titleset>
> 		<menus>
> 			<pgc entry="root" pause="inf">
> 				<vob file="shanghai.mpg"></vob>
> 				<button name="all">jump title 2 chapter 1;</button>

I think you mean title 1 here for the play all

> 				<button name="children">jump title 1 chapter 1;</button>
> 				<button name="oldtown"> jump title 1 chapter 2;</button>
> 				<button name="shopping">jump title 1 chapter 3;</button>
> 				<button name="bund">    jump title 1 chapter 4;</button>
> 				<button name="pearls">  jump title 1 chapter 5;</button>
> 				<button name="circus">  jump title 1 chapter 6;</button>
> 				<button name="view">    jump title 1 chapter 7;</button>
> 				<button name="menu">    jump vmgm menu entry title;</button>

These probably need to be changed to title 2

> 			</pgc>
> 		</menus>
> 		<titles>
> 			<pgc>
> 				<vob file="scene10.mpg"></vob>
> 				<vob file="scene11.mpg"></vob>
> 				<vob file="scene12.mpg"></vob>
> 				<vob file="scene13.mpg"></vob>
> 				<vob file="scene14.mpg"></vob>
> 				<vob file="scene15.mpg"></vob>
> 				<vob file="scene16.mpg"></vob>
> 				<post>call vmgm menu entry title;</post>

did you really want to go back to the title menu or should this be 'call menu entry root' to stay in this titleset

> 			</pgc>
> 		</titles> 
> 		<titles>

BIG PROBLEM only 1 titles section allowed per titleset. each 'pgc' becomes a title in this section

> 			<pgc>
> 				<vob file="scene10.mpg">
> 					<cell start="0:00:00.000" chapter="1">
> 						call menu entry root;
> 					</cell>
> 				</vob>
> 				<vob file="scene11.mpg">
> 					<cell start="0:00:00.000" chapter="1">
> 						call menu entry root;
> 					</cell>
> 				</vob>
> 				<vob file="scene12.mpg">
> 					<cell start="0:00:00.000" chapter="1">
> 						call menu entry root;
> 					</cell>
> 				</vob>					
> 				<vob file="scene13.mpg">
> 					<cell start="0:00:00.000" chapter="1">
> 						call menu entry root;
> 					</cell>
> 				</vob>
> 				<vob file="scene14.mpg">
> 					<cell start="0:00:00.000" chapter="1">
> 						call menu entry root;
> 					</cell>
> 				</vob>
> 				<vob file="scene15.mpg">
> 					<cell start="0:00:00.000" chapter="1">
> 						call menu entry root;
> 					</cell>
> 				</vob>
> 
> 				<vob file="scene16.mpg"></vob>
> 				<post>call menu entry title;</post>
> 			</pgc>
> 		</titles> 
> 	</titleset>
> </dvdauthor>
> 
> Thanks
> 
> Anne
> 
> 

see how this works now

Andy.

On Wednesday 23 May 2007, Andy Clay wrote:
>
> BIG PROBLEM only 1 titles section allowed per titleset. each 'pgc' becomes
> a title in this section
>
That drew my attention to the fact that I'd not paid enough attention to th=
e=20
last set of scenes.  I'd been too busy concentrating on the second one.  I=
=20
hadn't separated the scenes into pgc groups either.  After that, processing=
=20
completed, but it's a long way from right yet.  See my answer to Joe.

Anne

On Wednesday 23 May 2007, Joe Friedrichsen wrote:
> On 5/23/07, Anne Wilson <cannewilson@...> wrote:
> > To start at the end - the third button handles more titles in exactly t=
he
> > same way as the second button.  I haven't mentioned it much because once
> > the problem is solved for the second set of titles, the same solution
> > will handle the last one.
>
> Great. Thanks :-)
>
> > Here's the complete file
> >
> > <dvdauthor dest=3D"/home/anne/recordings/Video/China2001_1">
> >         <vmgm>
> >                 <menus>
> >                         <video format=3D"pal">
> >                         </video>
> >                         <pgc entry=3D"title" pause=3D"inf">
> >                                 <vob file=3D"main.mpg"></vob>
> >                                 <button name=3D"1Shanghai">jump titlese=
t 1
> > menu;</button> <button name=3D"2Yunan">jump titleset 2 menu;</button>
> > <button name=3D"3Shanghai">jump titleset 3 menu;</button> </pgc>
> >                 </menus>
> > </vmgm>
> >         <titleset>
> >                 <menus>
> >                         <pgc entry=3D"root" pause=3D"inf">
> >                                 <vob file=3D"airport.mpg"></vob>
> >                                 <button name=3D"Shanghai">jump title 1
> > chapter 1;</button> <button name=3D"Menu">jump vmgm menu entry
> > title;</button> </pgc>
> >                 </menus>
> >                 <titles>
> >                         <pgc>
> >                                 <vob file=3D"scene1.mpg"/>
> >                                 <post>call menu entry root;</post>
> >                         </pgc>
> >                 </titles>
> >         </titleset>
> >         <titleset>
> >                 <menus>
> >                         <pgc entry=3D"root" pause=3D"inf">
> >                                 <vob file =3D"yunan.mpg"></vob>
> >                                 <button name=3D"all">jump title 1 chapt=
er
> > 1;</button> <button name=3D"1kunming">jump title 2 chapter 1;</button>
> > <button name=3D"2sforest">jump title 3 chapter 1;</button> <button
> > name=3D"3lijiang">jump title 4 chapter 1;</button> <button name=3D"4sjt=
m"> =20
> > jump title 5 chapter 1;</button> <button name=3D"5naxi">   jump title 6
> > chapter 1;</button> <button name=3D"6temple"> jump title 7 chapter
> > 1;</button> <button name=3D"7lijiang">jump title 8 chapter 1;</button>
> > <button name=3D"8kunming">jump title 9 chapter 1;</button> <button
> > name=3D"9menu">call vmgm menu entry title;</button>
>
> Menus cannot use call; they can only jump. 9menu's command needs to be
> 'jump'.
>
> >                         </pgc>
> >                 </menus>
> >                 <titles>
> >                         <pgc>
> >                                 <vob file=3D"scene2.mpg"></vob>
> >                                 <vob file=3D"scene3.mpg"></vob>
> >                                 <vob file=3D"scene4.mpg"></vob>
> >                                 <vob file=3D"scene5.mpg"></vob>
> >                                 <vob file=3D"scene6.mpg"></vob>
> >                                 <vob file=3D"scene7.mpg"></vob>
> >                                 <vob file=3D"scene8.mpg"></vob>
> >                                 <vob file=3D"scene9.mpg"></vob>
> >                                 <post>call vmgm menu entry title;</post>
> >                         </pgc>
> >                         <pgc>
> >                                 <vob file=3D"scene2.mpg">
> >                                         <cell start=3D"0:00:00.000"
> > chapter=3D"1"> call menu entry root; </cell>
> >                                 </vob>
> >                         </pgc>
> >                         <pgc>
> >                                 <vob file=3D"scene3.mpg">
> >                                         <cell start=3D"0:00:00.000"
> > chapter=3D"1"> call menu entry root; </cell>
> >                                 </vob>
> >                         </pgc>
> >                         <pgc>
> >                                 <vob file=3D"scene4.mpg">
> >                                         <cell start=3D"0:00:00.000"
> > chapter=3D"1"> call menu entry root; </cell>
> >                                 </vob>
> >                         </pgc>
> >                         <pgc>
> >                                 <vob file=3D"scene5.mpg">
> >                                         <cell start=3D"0:00:00.000"
> > chapter=3D"1"> call menu entry root; </cell>
> >                                 </vob>
> >                         </pgc>
> >                         <pgc>
> >                                 <vob file=3D"scene6.mpg">
> >                                         <cell start=3D"0:00:00.000"
> > chapter=3D"1"> call menu entry root; </cell>
> >                                 </vob>
> >                         </pgc>
> >                         <pgc>
> >                                 <vob file=3D"scene7.mpg">
> >                                         <cell start=3D"0:00:00.000"
> > chapter=3D"1"> call menu entry root; </cell>
> >                                 </vob>
> >                         </pgc>
> >                         <pgc>
> >                                 <vob file=3D"scene8.mpg">
> >                                         <cell start=3D"0:00:00.000"
> > chapter=3D"1"> call menu entry root; </cell>
> >                                 </vob>
> >                         </pgc>
> >                         <pgc>
> >                                 <vob file=3D"scene9.mpg"></vob>
> >                                 <post>call menu entry root;</post>
> >                         </pgc>
> >                 </titles>
> >         </titleset>
> >         <titleset>
> >                 <menus>
> >                         <pgc entry=3D"root" pause=3D"inf">
> >                                 <vob file=3D"shanghai.mpg"></vob>
> >                                 <button name=3D"all">jump title 2 chapt=
er
> > 1;</button>
>
> I don't think that title 2 chapter 1 is the target you intend for
> 'play all'. Maybe title 1 chapter 1.
>
> >                                 <button name=3D"children">jump title 1
> > chapter 1;</button> <button name=3D"oldtown"> jump title 1 chapter
> > 2;</button> <button name=3D"shopping">jump title 1 chapter 3;</button>
> > <button name=3D"bund">    jump title 1 chapter 4;</button> <button
> > name=3D"pearls">  jump title 1 chapter 5;</button> <button name=3D"circ=
us">=20
> > jump title 1 chapter 6;</button> <button name=3D"view">    jump title 1
> > chapter 7;</button> <button name=3D"menu">    jump vmgm menu entry
> > title;</button>
>
> And maybe these targets need to be updated as well.
>
> >                         </pgc>
> >                 </menus>
> >                 <titles>
> >                         <pgc>
> >                                 <vob file=3D"scene10.mpg"></vob>
> >                                 <vob file=3D"scene11.mpg"></vob>
> >                                 <vob file=3D"scene12.mpg"></vob>
> >                                 <vob file=3D"scene13.mpg"></vob>
> >                                 <vob file=3D"scene14.mpg"></vob>
> >                                 <vob file=3D"scene15.mpg"></vob>
> >                                 <vob file=3D"scene16.mpg"></vob>
> >                                 <post>call vmgm menu entry title;</post>
> >                         </pgc>
> >                 </titles>
> >                 <titles>
> >                         <pgc>
> >                                 <vob file=3D"scene10.mpg">
> >                                         <cell start=3D"0:00:00.000"
> > chapter=3D"1"> call menu entry root; </cell>
> >                                 </vob>
> >                                 <vob file=3D"scene11.mpg">
> >                                         <cell start=3D"0:00:00.000"
> > chapter=3D"1"> call menu entry root; </cell>
> >                                 </vob>
> >                                 <vob file=3D"scene12.mpg">
> >                                         <cell start=3D"0:00:00.000"
> > chapter=3D"1"> call menu entry root; </cell>
> >                                 </vob>
> >                                 <vob file=3D"scene13.mpg">
> >                                         <cell start=3D"0:00:00.000"
> > chapter=3D"1"> call menu entry root; </cell>
> >                                 </vob>
> >                                 <vob file=3D"scene14.mpg">
> >                                         <cell start=3D"0:00:00.000"
> > chapter=3D"1"> call menu entry root; </cell>
> >                                 </vob>
> >                                 <vob file=3D"scene15.mpg">
> >                                         <cell start=3D"0:00:00.000"
> > chapter=3D"1"> call menu entry root; </cell>
> >                                 </vob>
> >
> >                                 <vob file=3D"scene16.mpg"></vob>
> >                                 <post>call menu entry title;</post>
> >                         </pgc>
> >                 </titles>
> >         </titleset>
> > </dvdauthor>
>
> What errors do you encounter now?
>
None in processing, but still problems in playback.  I seem to have lost=20
my 'play all' menu buttons, so I must be using an old copy of the menu=20
screen.  I'll sort that this evening.

More important is that the scenes do not return to the menu after playing. =
=20
The final scene in each group returns to its menu, but all the others stall=
 -=20
fade out and stop.  This is true of the Yunan set and the Shanghai set. =20
The 'call menu entry root;' command isn't working.

Anne

On 5/24/07, Anne Wilson <cannewilson@...> wrote:
> On Wednesday 23 May 2007, Joe Friedrichsen wrote:
> > What errors do you encounter now?
> >
> None in processing, but still problems in playback.  I seem to have lost
> my 'play all' menu buttons, so I must be using an old copy of the menu
> screen.  I'll sort that this evening.

Ok. Though I would think that dvdauthor would complain if the dvd xml
had more buttons than the menu. The 'cannot find button FOO' error...

> More important is that the scenes do not return to the menu after playing.
> The final scene in each group returns to its menu, but all the others stall -
> fade out and stop.  This is true of the Yunan set and the Shanghai set.
> The 'call menu entry root;' command isn't working.

I must admit that I've forgotten why you've chosen the cell approach
for your single-play scenes:

  <pgc>
    <vob file="scene2.mpg">
      <cell start="0:00:00.000"
       chapter="1"> call menu entry root; </cell>
    </vob>
  </pgc>

Each single-play scene is its own title since each is inside a <pgc>
tag, so I don't see why defining cells is necessary. Have you tried
simplifying the xml and dropping the cells altogether?

  <pgc>
    <vob file="scene2.mpg" />
    <post> call menu entry root; </post>
  </pgc>

Joe

On Thursday 24 May 2007, Joe Friedrichsen wrote:
> On 5/24/07, Anne Wilson <cannewilson@...> wrote:
> > On Wednesday 23 May 2007, Joe Friedrichsen wrote:
> > > What errors do you encounter now?
> >
> > None in processing, but still problems in playback.  I seem to have lost
> > my 'play all' menu buttons, so I must be using an old copy of the menu
> > screen.  I'll sort that this evening.
>
> Ok. Though I would think that dvdauthor would complain if the dvd xml
> had more buttons than the menu. The 'cannot find button FOO' error...
>
> > More important is that the scenes do not return to the menu after
> > playing. The final scene in each group returns to its menu, but all the
> > others stall - fade out and stop.  This is true of the Yunan set and the
> > Shanghai set. The 'call menu entry root;' command isn't working.
>
> I must admit that I've forgotten why you've chosen the cell approach
> for your single-play scenes:

Just taking the guidance that was there at the time :-)
>
>   <pgc>
>     <vob file="scene2.mpg">
>       <cell start="0:00:00.000"
>        chapter="1"> call menu entry root; </cell>
>     </vob>
>   </pgc>
>
> Each single-play scene is its own title since each is inside a <pgc>
> tag, so I don't see why defining cells is necessary. Have you tried
> simplifying the xml and dropping the cells altogether?
>
>   <pgc>
>     <vob file="scene2.mpg" />
>     <post> call menu entry root; </post>
>   </pgc>
>
OK, Joe.  I'll try that in the morning.

Anne

On Thursday 24 May 2007, Joe Friedrichsen wrote:
> On 5/24/07, Anne Wilson <cannewilson@...> wrote:
> > On Wednesday 23 May 2007, Joe Friedrichsen wrote:
> > > What errors do you encounter now?
> >
> > None in processing, but still problems in playback.  I seem to have lost
> > my 'play all' menu buttons, so I must be using an old copy of the menu
> > screen.  I'll sort that this evening.
>
> Ok. Though I would think that dvdauthor would complain if the dvd xml
> had more buttons than the menu. The 'cannot find button FOO' error...
>
> > More important is that the scenes do not return to the menu after
> > playing. The final scene in each group returns to its menu, but all the
> > others stall - fade out and stop.  This is true of the Yunan set and the
> > Shanghai set. The 'call menu entry root;' command isn't working.
>
> I must admit that I've forgotten why you've chosen the cell approach
> for your single-play scenes:
>
>   <pgc>
>     <vob file=3D"scene2.mpg">
>       <cell start=3D"0:00:00.000"
>        chapter=3D"1"> call menu entry root; </cell>
>     </vob>
>   </pgc>
>
> Each single-play scene is its own title since each is inside a <pgc>
> tag, so I don't see why defining cells is necessary. Have you tried
> simplifying the xml and dropping the cells altogether?
>
>   <pgc>
>     <vob file=3D"scene2.mpg" />
>     <post> call menu entry root; </post>
>   </pgc>
>
It's late, so I can't do any more tonight.  The latest is that in the Ynan=
=20
section, all but one of the scenes return to the menu, but they are mapped =
to=20
the wrong button.  I'll sort that in the morning, then see whether I can se=
e=20
any difference in the one that doesn't return.  Once the mapping is sorted =
It=20
should be easier to identify the culprit.

The menu for Shanghai doesn't work at all, so I'll have to rebuild the spum=
ux,=20
I think.  I'll report back when I've done all that.

Anne

On Thursday 24 May 2007, Joe Friedrichsen wrote:
> On 5/24/07, Anne Wilson <cannewilson@...> wrote:
> > On Wednesday 23 May 2007, Joe Friedrichsen wrote:
> > > What errors do you encounter now?
> >
> > None in processing, but still problems in playback.  I seem to have lost
> > my 'play all' menu buttons, so I must be using an old copy of the menu
> > screen.  I'll sort that this evening.
>
> Ok. Though I would think that dvdauthor would complain if the dvd xml
> had more buttons than the menu. The 'cannot find button FOO' error...
>
> > More important is that the scenes do not return to the menu after
> > playing. The final scene in each group returns to its menu, but all the
> > others stall - fade out and stop.  This is true of the Yunan set and the
> > Shanghai set. The 'call menu entry root;' command isn't working.
>
> I must admit that I've forgotten why you've chosen the cell approach
> for your single-play scenes:
>
>   <pgc>
>     <vob file=3D"scene2.mpg">
>       <cell start=3D"0:00:00.000"
>        chapter=3D"1"> call menu entry root; </cell>
>     </vob>
>   </pgc>
>
> Each single-play scene is its own title since each is inside a <pgc>
> tag, so I don't see why defining cells is necessary. Have you tried
> simplifying the xml and dropping the cells altogether?
>
>   <pgc>
>     <vob file=3D"scene2.mpg" />
>     <post> call menu entry root; </post>
>   </pgc>
>
OK - re-spumuxed with button order corrected.  I'm almost there.

Everything behaves as it should, with one exception.  In the Yunan section,=
=20
the button 3lijiang plays the chapter, but the return to menu doesn't happe=
n. =20
I can't see anything different about this chapter.  Could you look through =
it=20
once again and see if you can spot the error:

<dvdauthor dest=3D"/home/anne/recordings/Video/China2001_1">
	<vmgm>
		<menus>
			<video format=3D"pal">
			</video>
			<pgc entry=3D"title" pause=3D"inf">
				<vob file=3D"main.mpg"></vob>
				<button name=3D"1Shanghai">jump titleset 1 menu;</button>
				<button name=3D"2Yunan">jump titleset 2 menu;</button>
				<button name=3D"3Shanghai">jump titleset 3 menu;</button>
			</pgc>
		</menus>
</vmgm>
	<titleset>
		<menus>
			<pgc entry=3D"root" pause=3D"inf">
				<vob file=3D"airport.mpg"></vob>
				<button name=3D"Shanghai">jump title 1 chapter 1;</button>
				<button name=3D"Menu">jump vmgm menu entry title;</button>
			</pgc>
		</menus>
		<titles>
			<pgc>
				<vob file=3D"scene1.mpg"/>
				<post>call menu entry root;</post>
			</pgc>
		</titles>
	</titleset>
	<titleset>
		<menus>
			<pgc entry=3D"root" pause=3D"inf">
				<vob file =3D"yunan2.mpg"></vob>
				<button name=3D"all">jump title 1 chapter 1;</button>
				<button name=3D"1kunming">jump title 2 chapter 1;</button>
				<button name=3D"2sforest">jump title 3 chapter 1;</button>
				<button name=3D"3lijiang">jump title 4 chapter 1;</button>
				<button name=3D"4sjtm">   jump title 5 chapter 1;</button>
				<button name=3D"5naxi">   jump title 6 chapter 1;</button>
				<button name=3D"6temple"> jump title 7 chapter 1;</button>
				<button name=3D"7lijiang">jump title 8 chapter 1;</button>
				<button name=3D"8kunming">jump title 9 chapter 1;</button>
				<button name=3D"9menu">jump vmgm menu entry title;</button>
			</pgc>
		</menus>
		<titles>
			<pgc>
				<vob file=3D"scene2.mpg"></vob>
				<vob file=3D"scene3.mpg"></vob>
				<vob file=3D"scene4.mpg"></vob>
				<vob file=3D"scene5.mpg"></vob>
				<vob file=3D"scene6.mpg"></vob>
				<vob file=3D"scene7.mpg"></vob>
				<vob file=3D"scene8.mpg"></vob>
				<vob file=3D"scene9.mpg"></vob>
				<post>call vmgm menu entry title;</post>
			</pgc>
			<pgc>
				<vob file=3D"scene2.mpg"></vob>
				<post>call menu entry root;</post>

			</pgc>
			<pgc>
				<vob file=3D"scene3.mpg"></vob>
				<post>call menu entry root;</post>
			</pgc>
			<pgc>
				<vob file=3D"scene4.mpg"></vob>
				<post>call menu entry root;</post>
			</pgc>
			<pgc>
				<vob file=3D"scene5.mpg"></vob>
				<post>call menu entry root;</post>
			</pgc>
			<pgc>
				<vob file=3D"scene6.mpg"></vob>
				<post>call menu entry root;</post>
			</pgc>
			<pgc>
				<vob file=3D"scene7.mpg"></vob>
				<post>call menu entry root;</post>
			</pgc>
			<pgc>
				<vob file=3D"scene8.mpg"></vob>
				<post>call menu entry root;</post>
			</pgc>
			<pgc>
				<vob file=3D"scene9.mpg"></vob>
				<post>call menu entry root;</post>
			</pgc>
		</titles>=20
	</titleset>
	<titleset>
		<menus>
			<pgc entry=3D"root" pause=3D"inf">
				<vob file=3D"shanghai2.mpg"></vob>
				<button name=3D"all">jump title 1 chapter 1;</button>
				<button name=3D"children">jump title 2 chapter 1;</button>
				<button name=3D"oldtown"> jump title 3 chapter 1;</button>
				<button name=3D"shopping">jump title 4 chapter 1;</button>
				<button name=3D"bund">    jump title 5 chapter 1;</button>
				<button name=3D"pearls">  jump title 6 chapter 1;</button>
				<button name=3D"circus">  jump title 7 chapter 1;</button>
				<button name=3D"view">    jump title 8 chapter 1;</button>
				<button name=3D"menu">    jump vmgm menu entry title;</button>
			</pgc>
		</menus>
		<titles>
			<pgc>
				<vob file=3D"scene10.mpg"></vob>
				<vob file=3D"scene11.mpg"></vob>
				<vob file=3D"scene12.mpg"></vob>
				<vob file=3D"scene13.mpg"></vob>
				<vob file=3D"scene14.mpg"></vob>
				<vob file=3D"scene15.mpg"></vob>
				<vob file=3D"scene16.mpg"></vob>
				<post>call vmgm menu entry title;</post>
			</pgc>
			<pgc>
				<vob file=3D"scene10.mpg"></vob>
				<post>call menu entry root;</post>
			</pgc>
			<pgc>
				<vob file=3D"scene11.mpg"></vob>
				<post>call menu entry root;</post>
			</pgc>
			<pgc>
				<vob file=3D"scene12.mpg"></vob>
				<post>call menu entry root;</post>
			</pgc>
			<pgc>
				<vob file=3D"scene13.mpg"></vob>
				<post>call menu entry root;</post>
			</pgc>
			<pgc>
				<vob file=3D"scene14.mpg"></vob>
				<post>call menu entry root;</post>
			</pgc>
			<pgc>
				<vob file=3D"scene15.mpg"></vob>
				<post>call menu entry root;</post>
			</pgc>
			<pgc>
				<vob file=3D"scene16.mpg"></vob>
				<post>call menu entry root;</post>
			</pgc>
		</titles>=20
	</titleset>
</dvdauthor>

Thanks

Anne

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Joe Friedrichsen schrieb:
> On 5/24/07, Anne Wilson <cannewilson@...> wrote:
>> On Wednesday 23 May 2007, Joe Friedrichsen wrote:
>>> What errors do you encounter now?
>>>
>> None in processing, but still problems in playback.  I seem to have lost
>> my 'play all' menu buttons, so I must be using an old copy of the menu
>> screen.  I'll sort that this evening.
> 
> Ok. Though I would think that dvdauthor would complain if the dvd xml
> had more buttons than the menu. The 'cannot find button FOO' error...
> 
>> More important is that the scenes do not return to the menu after playing.
>> The final scene in each group returns to its menu, but all the others stall -
>> fade out and stop.  This is true of the Yunan set and the Shanghai set.
>> The 'call menu entry root;' command isn't working.
> 
> I must admit that I've forgotten why you've chosen the cell approach
> for your single-play scenes:
> 
>   <pgc>
>     <vob file="scene2.mpg">
>       <cell start="0:00:00.000"
>        chapter="1"> call menu entry root; </cell>
>     </vob>
>   </pgc>
> 

It was my suggestion to use cells because of the description, how Anne
would like to navigate in the DVD. And my thoughts already went one step
further, how one could achieve a "play-all" and "single chapter" mode
for the same title without the need to replicate it.

The problem is, that Anne didn't really follow the example in my posting
from Apr 22nd, where I put all <vob>s into one <pgc> and defined each
<vob> as a cell to have the cell commands available.

> Each single-play scene is its own title since each is inside a <pgc>
> tag, so I don't see why defining cells is necessary. Have you tried
> simplifying the xml and dropping the cells altogether?
> 
>   <pgc>
>     <vob file="scene2.mpg" />
>     <post> call menu entry root; </post>
>   </pgc>
> 

Jepp, this will also work in this particular case. The only difference
between this and the (correct) cell approach would be the behaviour when
pressing the "Next/Previous"-Chapter button on the remote.
With cells, one would advance to the next or previous chapter within the
title, while the above will return to the menu with the "Next"-button
and replay the title with the "Previous"-button.

cu
Wolfgang
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFGVsWkgUafbxFH+p8RAnVxAKDLBD9s6v2rTBScyKSO6hgwKuOKZgCePOPD
6W92ERJUooHOngWLlZee4/s=
=LsLv
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Anne Wilson schrieb:
> Hi, Wolfgang.  Sorry for the delay in continuing this.  After two weeks 
> holiday there is a great deal of catching up to do.  Now I'm trying to get my 
> mind back into this particular groove :-)

Hi Anne,

I took a couple days off myself, so please excuse my late replies. Hope
you'll find something useful in my comments.

> 
> I'm not sure that I understand your sentence "With "chapter=0|1" you may mark 
> you cell as a chapter ("1") oder not ("0")."

A cell must not neccessarily define a chapter, that's why you have to
tell dvdauthor, whether you want the beginning of the cell to also serve
as the beginning of a new chapter (chapter="1") or not (chapter="0")

> 
> Is this what you mean:
> 
(... correct xml definitions omitted ...)
> 	<titleset>
> 		<titles>
> 			<pgc>
> 				<vob file="scene2.mpg"></vob>
> 				<vob file="scene3.mpg"></vob>
> 				<vob file="scene4.mpg"></vob>
> 				<vob file="scene5.mpg"></vob>
> 				<vob file="scene6.mpg"></vob>
> 				<vob file="scene7.mpg"></vob>
> 				<vob file="scene8.mpg"></vob>
> 				<vob file="scene9.mpg"></vob>
> 				<post>jump vmgm menu entry title;</post>
> 			</pgc>
> 		</titles> 
> 		<titles>
The two lines above are wrong. Within a titleset, you may only specify
one <titles>-section. Every <pgc> therein marks a title. Just delete
both lines.

> 			<pgc>
> 				<button name="all">jump title 2 chapter 1;</button>
I guess the above line is a copy/paste error. <button>-tags are only
allowed within a <menu> definition, not within <titles>.

> 				<vob file="scene2.mpg">
> 					<cells start="0:00:00.000" chapter="1">
> 						call menu entry root;
> 					</cells>
> 				</vob>
> 				<vob file="scene3.mpg">
> 					<cells start="0:00:00.000" chapter="1">
> 						call menu entry root;
> 					</cells>
> 				</vob>
Jepp, you got the right impression on how to use the chapter-parm within
the <cell>-tag.

(... correct xml definitions omitted ...)
> 				<vob file="scene9.mpg"></vob>
> 				<post>call menu entry root;</post>
> 			</pgc>
> 		</titles> 
> 	</titleset>
> 
> I can't remember whether titles are numbered within the titleset, in which 
> case I shall have to change the 2's to 1's and 3's to 2's.

Not 100% sure, but I guess, from within the titleset-menu, the titles in
that titleset are numbered beginning from 1.

hth
Wolfgang
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFGVsh6gUafbxFH+p8RAmPtAJ9bZkwuyFwnwOFnnB7Yf1fViTjJMgCfT7DU
gdEYywOLAvlV/M0fmrB9xko=
=zZ1Q
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Joe Friedrichsen schrieb:
> On 5/20/07, Anne Wilson <cannewilson@...> wrote:
>> I've had no success so far.  (I removed the accidentally pasted button line in
>> <titles>).  I keep getting
>>
>> STAT: fixed 3 VOBUS
>> STAT: fixed 183 VOBUS
>> ERR:  Titles already defined
>>
>> As far as I can see I have to define the titles twice - once for playing
>> straight through then returning to menu, and once returning to menu after
>> each chapter.  I suspect that I have to use one <titles> </titles> wrapper
>> over both sets, but two <pcg> sets (i.e. drop one </titles> <titles>).  If
>> that's so, how do I refer to each <pcg> set?
> 
> Each new <pgc> tag is seen as a title (and each <vob> inside a new
> chapter), and each titleset starts with title 1 (and each title from
> chapter 1). If you put your 'play all' block inside the first pgc, it
> will be title 1 of that titleset. Each individual-play scene needs its
> own <pgc> and will increment from there: title 2, title 3, ...

No, the last sentence is not true. The way, Anne defined the <vob>s as
<cell>s, you only need one second <pgc> and may access each chapter
therein separately.

cu
Wolfgang
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFGVslHgUafbxFH+p8RAjJIAKDBbL92AdP0IEyXsFb9nkDjtOD6JACcDdbU
kWtoc0KAuZLm6c1/IBgiRG4=
=+wEQ
-----END PGP SIGNATURE-----

On Friday 25 May 2007, Wolfgang Wershofen wrote:
>
> It was my suggestion to use cells because of the description, how Anne
> would like to navigate in the DVD. And my thoughts already went one step
> further, how one could achieve a "play-all" and "single chapter" mode
> for the same title without the need to replicate it.
>
> The problem is, that Anne didn't really follow the example in my posting
> from Apr 22nd, where I put all <vob>s into one <pgc> and defined each
> <vob> as a cell to have the cell commands available.
>
Entirely possible, though certainly not deliberate.  If so, it was caused b=
y=20
tiredness, stress and time constraints.  Sorry if I've caused extra work fo=
r=20
you and Joe by such a mistake.

Anne

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Anne Wilson schrieb:
> 
> Here's the complete file

Anne, I'll keep this intact, see my comments below the lines, I have
something to say about. ;-)

> 
> <dvdauthor dest="/home/anne/recordings/Video/China2001_1">
> 	<vmgm>
> 		<menus>
> 			<video format="pal">
> 			</video>
> 			<pgc entry="title" pause="inf">
> 				<vob file="main.mpg"></vob>
> 				<button name="1Shanghai">jump titleset 1 menu;</button>
> 				<button name="2Yunan">jump titleset 2 menu;</button>
> 				<button name="3Shanghai">jump titleset 3 menu;</button>
> 			</pgc>
> 		</menus>
> </vmgm>
> 	<titleset>
> 		<menus>
> 			<pgc entry="root" pause="inf">
> 				<vob file="airport.mpg"></vob>
> 				<button name="Shanghai">jump title 1 chapter 1;</button>
> 				<button name="Menu">jump vmgm menu entry title;</button>
> 			</pgc>
> 		</menus>
> 		<titles>
> 			<pgc>
> 				<vob file="scene1.mpg"/>
> 				<post>call menu entry root;</post>
> 			</pgc>
> 		</titles>
> 	</titleset>
> 	<titleset>
> 		<menus>
> 			<pgc entry="root" pause="inf">
> 				<vob file ="yunan.mpg"></vob>
> 				<button name="all">jump title 1 chapter 1;</button>
> 				<button name="1kunming">jump title 2 chapter 1;</button>
> 				<button name="2sforest">jump title 3 chapter 1;</button>
> 				<button name="3lijiang">jump title 4 chapter 1;</button>
> 				<button name="4sjtm">   jump title 5 chapter 1;</button>
> 				<button name="5naxi">   jump title 6 chapter 1;</button>
> 				<button name="6temple"> jump title 7 chapter 1;</button>
> 				<button name="7lijiang">jump title 8 chapter 1;</button>
> 				<button name="8kunming">jump title 9 chapter 1;</button>
> 				<button name="9menu">call vmgm menu entry title;</button>
The above must be "jump vmgm menu entry title", just as in the first
titleset.

> 			</pgc>
> 		</menus>
> 		<titles>
> 			<pgc>
> 				<vob file="scene2.mpg"></vob>
> 				<vob file="scene3.mpg"></vob>
> 				<vob file="scene4.mpg"></vob>
> 				<vob file="scene5.mpg"></vob>
> 				<vob file="scene6.mpg"></vob>
> 				<vob file="scene7.mpg"></vob>
> 				<vob file="scene8.mpg"></vob>
> 				<vob file="scene9.mpg"></vob>
> 				<post>call vmgm menu entry title;</post>
Are you sure, you want to return to the vmgm menu and not to the
titleset menu? Code "call menu entry root" for the latter.

> 			</pgc>
> 			<pgc>
> 				<vob file="scene2.mpg">
> 					<cell start="0:00:00.000" chapter="1">
> 						call menu entry root;
> 					</cell>
> 				</vob>
> 			</pgc>
> 			<pgc>
You define every vob as a new title and thus prevent the cell-command to
be executed. As I said in a previous posting, the cell-command of the
last cell defined in a title is not executed. Either replace the
<cell>-tag with a normal <post> instruction or delete all </pgc><pgc>
couples between the <vob>s to define only one single title (as you did
in the third titleset). With this, you'll have to change the targets in
your menu as well from "title x chapter 1" to "title 2 chapter x".


> 				<vob file="scene3.mpg">
> 					<cell start="0:00:00.000" chapter="1">
> 						call menu entry root;
> 					</cell>
> 				</vob>
> 			</pgc>
> 			<pgc>
> 				<vob file="scene4.mpg">
> 					<cell start="0:00:00.000" chapter="1">
> 						call menu entry root;
> 					</cell>
> 				</vob>
> 			</pgc>
> 			<pgc>
> 				<vob file="scene5.mpg">
> 					<cell start="0:00:00.000" chapter="1">
> 						call menu entry root;
> 					</cell>
> 				</vob>
> 			</pgc>
> 			<pgc>
> 				<vob file="scene6.mpg">
> 					<cell start="0:00:00.000" chapter="1">
> 						call menu entry root;
> 					</cell>
> 				</vob>
> 			</pgc>
> 			<pgc>
> 				<vob file="scene7.mpg">
> 					<cell start="0:00:00.000" chapter="1">
> 						call menu entry root;
> 					</cell>
> 				</vob>
> 			</pgc>
> 			<pgc>
> 				<vob file="scene8.mpg">
> 					<cell start="0:00:00.000" chapter="1">
> 						call menu entry root;
> 					</cell>
> 				</vob>
> 			</pgc>
> 			<pgc>
> 				<vob file="scene9.mpg"></vob>
> 				<post>call menu entry root;</post>
> 			</pgc>
> 		</titles> 
> 	</titleset>
> 	<titleset>
> 		<menus>
> 			<pgc entry="root" pause="inf">
> 				<vob file="shanghai.mpg"></vob>
> 				<button name="all">jump title 2 chapter 1;</button>
I guess, this should be "jump title 1 chapter 1" for the play-all function?

> 				<button name="children">jump title 1 chapter 1;</button>
> 				<button name="oldtown"> jump title 1 chapter 2;</button>
> 				<button name="shopping">jump title 1 chapter 3;</button>
> 				<button name="bund">    jump title 1 chapter 4;</button>
> 				<button name="pearls">  jump title 1 chapter 5;</button>
> 				<button name="circus">  jump title 1 chapter 6;</button>
> 				<button name="view">    jump title 1 chapter 7;</button>
And these shoud be "jump title 2 chapter x" as well.

> 				<button name="menu">    jump vmgm menu entry title;</button>
> 			</pgc>
> 		</menus>
> 		<titles>
> 			<pgc>
> 				<vob file="scene10.mpg"></vob>
> 				<vob file="scene11.mpg"></vob>
> 				<vob file="scene12.mpg"></vob>
> 				<vob file="scene13.mpg"></vob>
> 				<vob file="scene14.mpg"></vob>
> 				<vob file="scene15.mpg"></vob>
> 				<vob file="scene16.mpg"></vob>
> 				<post>call vmgm menu entry title;</post>
Again the question, whether you really want to return to the vmgm menu
instead of the titleset-menu, see previous titleset as well.

> 			</pgc>
> 		</titles> 
> 		<titles>
Delete the two lines above. (It's getting FAQ... ;-)

> 			<pgc>
> 				<vob file="scene10.mpg">
> 					<cell start="0:00:00.000" chapter="1">
> 						call menu entry root;
> 					</cell>
> 				</vob>
> 				<vob file="scene11.mpg">
> 					<cell start="0:00:00.000" chapter="1">
> 						call menu entry root;
> 					</cell>
> 				</vob>
> 				<vob file="scene12.mpg">
> 					<cell start="0:00:00.000" chapter="1">
> 						call menu entry root;
> 					</cell>
> 				</vob>					
> 				<vob file="scene13.mpg">
> 					<cell start="0:00:00.000" chapter="1">
> 						call menu entry root;
> 					</cell>
> 				</vob>
> 				<vob file="scene14.mpg">
> 					<cell start="0:00:00.000" chapter="1">
> 						call menu entry root;
> 					</cell>
> 				</vob>
> 				<vob file="scene15.mpg">
> 					<cell start="0:00:00.000" chapter="1">
> 						call menu entry root;
> 					</cell>
> 				</vob>
> 
> 				<vob file="scene16.mpg"></vob>
> 				<post>call menu entry title;</post>
> 			</pgc>
> 		</titles> 
> 	</titleset>
> </dvdauthor>
> 

Apply the mentioned changes and this should work. It's not too far
away... ;-)

hth
Wolfgang
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFGVs8lgUafbxFH+p8RAmSQAKDUalUreci8PtRYm5LVO66BGjRokACghZA0
7pQUCO438plTwKQf2hou7kI=
=/7lO
-----END PGP SIGNATURE-----

On Friday 25 May 2007, Wolfgang Wershofen wrote:
> Anne Wilson schrieb:
> > Hi, Wolfgang.  Sorry for the delay in continuing this.  After two weeks
> > holiday there is a great deal of catching up to do.  Now I'm trying to
> > get my mind back into this particular groove :-)
>
> Hi Anne,
>
> I took a couple days off myself, so please excuse my late replies. Hope
> you'll find something useful in my comments.
>
> > I'm not sure that I understand your sentence "With "chapter=3D0|1" you =
may
> > mark you cell as a chapter ("1") oder not ("0")."
>
> A cell must not neccessarily define a chapter, that's why you have to
> tell dvdauthor, whether you want the beginning of the cell to also serve
> as the beginning of a new chapter (chapter=3D"1") or not (chapter=3D"0")
>
The really important thing is that between the various people who have repl=
ied=20
to me, a lot of important information has been imparted.  I'm beginning to=
=20
understand a lot better how things work.

I don't really want to re-do everything under the cells arrangement, as I'v=
e=20
already spent so much time on this, but I'll experiment more with that when=
=20
I've more time.

Once my final problem is sorted I'll keep that as a working example.  Equal=
ly=20
important, I'll try to write up a how-to that incorporates all the useful=20
hints, tips and explanations that I've gathered.  I may even make it=20
available on a website :-)

Meanwhile, have you any idea why one chapter out of 16 should misbehave, no=
t=20
returning to menu?  I put the whole xml file in my reply to Joe this mornin=
g.

Anne

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Anne Wilson schrieb:
> On Wednesday 23 May 2007, Joe Friedrichsen wrote:
(...)

>> What errors do you encounter now?
>>
> None in processing, but still problems in playback.  I seem to have lost 
> my 'play all' menu buttons, so I must be using an old copy of the menu 
> screen.  I'll sort that this evening.
> 
> More important is that the scenes do not return to the menu after playing.  
> The final scene in each group returns to its menu, but all the others stall - 
> fade out and stop.  This is true of the Yunan set and the Shanghai set.  
> The 'call menu entry root;' command isn't working.

This is due to the fact, that you defined each "chapter" as a title by
surrounding it with a <pgc></pgc>. The <cell>, you defined is also the
last cell in the title and the cell-command of the last <cell> is not
executed. I don't know, why this is (maybe Scott can say something about
this?), but it's a fact.

hth
Wolfgang
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFGVtBXgUafbxFH+p8RAtEdAKC+tz3I9CdwMGecs+idgGlck+BAAgCeKdxH
0dgZCtLBaZdAZva9hpDjBP8=
=vFbu
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Anne Wilson schrieb:
> On Friday 25 May 2007, Wolfgang Wershofen wrote:
>> It was my suggestion to use cells because of the description, how Anne
>> would like to navigate in the DVD. And my thoughts already went one step
>> further, how one could achieve a "play-all" and "single chapter" mode
>> for the same title without the need to replicate it.
>>
>> The problem is, that Anne didn't really follow the example in my posting
>> from Apr 22nd, where I put all <vob>s into one <pgc> and defined each
>> <vob> as a cell to have the cell commands available.
>>
> Entirely possible, though certainly not deliberate.  If so, it was caused by 
> tiredness, stress and time constraints.  Sorry if I've caused extra work for 
> you and Joe by such a mistake.

It was not your fault (at least not entirely ;-)
I guess there was a misunderstanding of my cell-approach in one of Joe's
replies during my absence, that made you define each chapter as a cell
and a title, which doesn't make much sense.

cu
Wolfgang
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFGVtI7gUafbxFH+p8RAp8fAJ9WCP+DZknfrka1kON43ugRFbib0wCeMiy5
JIYlPyVZD6Pzn9DEySRr7ms=
=kez2
-----END PGP SIGNATURE-----

On Friday 25 May 2007, Wolfgang Wershofen wrote:
>
> Apply the mentioned changes and this should work. It's not too far
> away... ;-)
>
Most of the changes you mention have already been found and fixed, over the=
=20
last few days.  I'll have another go at this cell method as soon as I get a=
=20
bit of spare time :-)

Anne

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Anne Wilson schrieb:
> OK - re-spumuxed with button order corrected.  I'm almost there.
> 
> Everything behaves as it should, with one exception.  In the Yunan section, 
> the button 3lijiang plays the chapter, but the return to menu doesn't happen.  
> I can't see anything different about this chapter.  Could you look through it 
> once again and see if you can spot the error:
> 
(... xml definition omitted ...)

I can't see anything different in this chapter as well. Maybe something
is odd with this particular mpeg file.

Did you already try to swap the mpeg files in the titles (e.g. specify
scene4.mpg for the third title and scene3.mpg for the fourth one)?
If it's mpeg-related, the error should then occur for the third title
(button "2sforest").

Did you see any warnings or error messages in the output of dvdauthor,
concerning scene4.mpg? Please post the output, if you are not sure.

hth
Wolfgang
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFGVtRZgUafbxFH+p8RApGhAJ0Zzs52YDyDuSrb7OMNj6ANYZg4CQCgsyDe
bKHL0t08TcAMViGbqPo8dew=
=9V6u
-----END PGP SIGNATURE-----

On 5/25/07, Wolfgang Wershofen <wolfgang@...> wrote:
> Joe Friedrichsen schrieb:
> > Each new <pgc> tag is seen as a title (and each <vob> inside a new
> > chapter), and each titleset starts with title 1 (and each title from
> > chapter 1). If you put your 'play all' block inside the first pgc, it
> > will be title 1 of that titleset. Each individual-play scene needs its
> > own <pgc> and will increment from there: title 2, title 3, ...
>
> No, the last sentence is not true. The way, Anne defined the <vob>s as
> <cell>s, you only need one second <pgc> and may access each chapter
> therein separately.

Ah, now it makes sense :-) When I saw <cell>s inside <pgc>s, I didn't
understand why someone would want that since omitting the <cell>s and
using <post> commands would give the same behavior for that specific
structure.. If there were only one <pgc> though, then using <cell>s
makes perfect sense.

Joe

On Friday 25 May 2007, Wolfgang Wershofen wrote:
> Anne Wilson schrieb:
> > OK - re-spumuxed with button order corrected.  I'm almost there.
> >
> > Everything behaves as it should, with one exception.  In the Yunan
> > section, the button 3lijiang plays the chapter, but the return to menu
> > doesn't happen. I can't see anything different about this chapter.  Cou=
ld
> > you look through it once again and see if you can spot the error:
>
> (... xml definition omitted ...)
>
> I can't see anything different in this chapter as well. Maybe something
> is odd with this particular mpeg file.
>
Maybe so.

> Did you already try to swap the mpeg files in the titles (e.g. specify
> scene4.mpg for the third title and scene3.mpg for the fourth one)?
> If it's mpeg-related, the error should then occur for the third title
> (button "2sforest").

I hadn't thought of that.  I'd just assume that it was another silly mistak=
e=20
in the xml file.  The problem moves with the scene, so it must be=20
mpeg-related.

> Did you see any warnings or error messages in the output of dvdauthor,
> concerning scene4.mpg? Please post the output, if you are not sure.
>
Absolutely nothing out of the ordinary - that scene reported just the same =
as=20
all the others.  I guess that means that I have to re-build the mpeg.

Anne

On Friday 25 May 2007 13:19:37 Wolfgang Wershofen wrote:
> Anne Wilson schrieb:
> > OK - re-spumuxed with button order corrected.  I'm almost there.
> >
> > Everything behaves as it should, with one exception.  In the Yunan
> > section, the button 3lijiang plays the chapter, but the return to menu
> > doesn't happen. I can't see anything different about this chapter.  Could
> > you look through it once again and see if you can spot the error:
>
> (... xml definition omitted ...)
>
> I can't see anything different in this chapter as well. Maybe something
> is odd with this particular mpeg file.
>
> Did you already try to swap the mpeg files in the titles (e.g. specify
> scene4.mpg for the third title and scene3.mpg for the fourth one)?
> If it's mpeg-related, the error should then occur for the third title
> (button "2sforest").
>
> Did you see any warnings or error messages in the output of dvdauthor,
> concerning scene4.mpg? Please post the output, if you are not sure.
>
I finally have a working layout - completely working, but not without 
jiggery-pokery.

Originally the scene had been constructed like this:

lav2yuv 04_lijiang1.eli 04_lijiang2.eli fade4.avi | yuvscaler -O DVD | 
yuvdenoise | mpeg2enc -f 8 -I 1 -q 7 -o scene4.m2v
lav2wav 04_lijiang1.eli 04_lijiang2.eli fade4.avi | mp2enc -v 2 -o scene4.mp2
mplex -f 8 scene4a.m2v scene4a.mp2 -o scene4.mpg

and fade4 had been created with

ypipe -v 2 "lav2yuv -v 2 -o -25 04_lijiang2.eli" "lav2yuv -v 2 -f 25 
white_screen_large_sound.avi" | transist.flt -o 0 -O 255 -d 25 | yuv2lav -v 
0 -f a -q 80 -o Fade4.avi
lav2wav -R Fade4.avi > fade4.wav
lavaddwav Fade4.avi fade4.wav fade4.avi

All this is exactly how all the other, well-behaved, scenes had been 
constructed.

In the first place I reconstructed the fade4.avi, then the whole mpg.  Nothing 
had changed.  By trial and error I discovered that if I left out the 
fade4.avi the resulting mpg would play throug then return to menu correctly.  
Adding back the fade4.avi resulted in a stop at the end of the scene.

As a workaround I then rebuilt the scene4.mpg without the fade4.avi, built 
fade4.avi into another mpg, and put them both together as one <pgc> group.  
Technically, of course, it's wrong, but practically, no-one will be aware of 
a one-second chapter, and it now behaves perfectly.

The practical problem is solved, but the mystery remains.

Anne

Shouldn't the second parameter of findptssec in dvdifo.c be a
pts_t rather than an int?

I occasionally run into a situation where dvdauthor crashes after
displaying the "INFO: Generating..." message but before starting to
fix the VOBUs. The cause of the crash looks to be secunit returning
zero because numsec returned a negative number due to the pts parameter
of findptssec going negative.
-- 
roger ivie
rivie@...