VideoHelp Forum

Our website is made possible by displaying online advertisements to our visitors. Consider supporting us by disable your adblocker or try DVDFab and copy, convert or make Blu-rays and DVDs! :)
+ Reply to Thread
Results 1 to 8 of 8
Thread
  1. Member
    Join Date
    Dec 2008
    Location
    United Kingdom
    Search Comp PM
    dvdauthor version is 0.6.14
    I have a problem with the DVD built with the attached files.

    On the TrekDays menu there are 15 buttons in a grid and they are set up to wrap from left to right and top to bottom. They are defined in order along the first row, then the second, then the third. The problem is that the last three buttons on the bottom row are not selectable...

    Code:
    1 2 3 4 5
    6 7 8 9 A
    x B C D E
    The x is a back button, 1-E are the title select buttons. Any attempt to select C, D, or E results in 1, 2, or 3 being selected respectively. For example going down from 9 jumps to 2, or going up from 5 jumps to 3, etc.

    I have attached the dvdauthor xml file and all of the spumux files, if anyone can see the problem, or even build the DVD and get it working or has the same problem I'd appreciate finding out (either way). I can provide the mask files if anyone wants, though it should be possible to build it with all-opaque/white masks for testing purposes.

    Many thanks,
    J

    nepaldvd.xml
    menu_trekdays.spumux

    menu_main.spumux
    menu_trekking.spumux
    menu_pokhara.spumux
    menu_kathmandu.spumux
    Quote Quote  
  2. I'm not sure if this is your problem, but:
    Code:
    <button x0="0" y0="400" x1="193" y1="468" name="Back"
    setting x0=0 is a bad idea. Due to overscan you should use at least x0=16.
    Quote Quote  
  3. Member
    Join Date
    Dec 2008
    Location
    United Kingdom
    Search Comp PM
    I tried with x0=100 and the problem with the last three buttons persists.

    I think you are mentioning this for visual reasons. However, the button highlight (white "<< Back" text) is within safe areas, the text is on a bar that extends all the way to the left on the background video. That area in the highlight is completely transparent and the only reason the button dimensions extend there is for the benefit of pointer-based systems.

    Have you ever managed to author a DVD with more than 12 buttons on a menu? I understand that you can have up to 18 in 16:9 (36 in 4:3), so I'm wondering if this is a dvdauthor problem or something strange about my xml that causes the button problem?

    J

    menu_trekdays_buttons.png
    Quote Quote  
  4. I have used up to 20 buttons on a 4:3 menu (never tried more yet) without any problems.
    I understand that you can have up to 18 in 16:9 (36 in 4:3)
    It's a little bit more complicated...
    The problem is, that DVD players automatically scale the video (menu or movie), but not the subpictures. Therefore you have to do the scaling.
    On a 4:3 menu only one subpicture for the buttons is necessary (no need to scale anything). On a 16:9 menu there are more 'possibilities'. The subpicture for the 16:9 menu itself is always necessary, then either one subpicture for the letterbox OR one subpicture for the pan&scan mode (then 18 buttons are possible). If you allow both letterbox AND pan&scan mode, you need two additional subpictures (thus you have three in total) and therefore you may only use up to 12 buttons.

    [Edit]
    I've just tried 15 buttons on a 16:9 menu with GfD (Letterbox only). It works without a problem.
    The relevant part of the author.xml:
    Code:
    <vmgm>
        <menus>
        <video format="pal"></video>
          <subpicture>
            <stream id="0" mode="widescreen" />
            <stream id="1" mode="letterbox" />
          </subpicture>
          <pgc entry="title">
          <pre> { if (g1 eq 0) g1=1; button=g1*1024; } </pre>
            <vob file="F:\Filme\Volume8\Temp\MMMenuL.mpg" pause="inf"/>
            <button name="MMB1">jump titleset 1 menu;</button>
            <button name="MMB2">jump titleset 2 menu;</button>
            <button name="MMB3">jump titleset 3 menu;</button>
            <button name="MMB4">jump titleset 4 menu;</button>
            <button name="MMB5">jump titleset 5 menu;</button>
            <button name="MMB6">jump titleset 6 menu;</button>
            <button name="MMB7">jump titleset 7 menu;</button>
            <button name="MMB8">jump titleset 8 menu;</button>
            <button name="MMB9">jump titleset 9 menu;</button>
            <button name="MMB10">jump titleset 10 menu;</button>
            <button name="MMB11">jump titleset 11 menu;</button>
            <button name="MMB12">jump titleset 12 menu;</button>
            <button name="MMB13">jump titleset 13 menu;</button>
            <button name="MMB14">jump titleset 14 menu;</button>
            <button name="MMB15">jump titleset 15 menu;</button>
          </pgc>
        </menus>
    </vmgm>
    The MMMenuL.mpg was created by adding two subpicture streams (MMSpu.xml + MMSpuL.xml) to the raw menu image (single frame mpeg file created by png2yuv + mpeg2enc).
    Code:
    "D:\Program Files\dvdauthor\spumux.exe" "F:\Filme\Volume8\Temp\MMSpu.xml" <"F:\Filme\Volume8\Temp\MMBackg.mpg" > "F:\Filme\Volume8\Temp\MMMenu.mpg"
    
    "D:\Program Files\dvdauthor\spumux.exe" -s1 "F:\Filme\Volume8\Temp\MMSpuL.xml" <"F:\Filme\Volume8\Temp\MMMenu.mpg" > "F:\Filme\Volume8\Temp\MMMenuL.mpg"
    The MMSpu.xml looks like:
    Code:
    <subpictures>
      <stream>
        <spu start="00:00:00.0"
             highlight="F:\Filme\Volume8\Temp\MMHigh.png"
             select="F:\Filme\Volume8\Temp\MMAct.png"
             force="yes"
             autoorder="rows">
       <button name="MMB1" x0="93" y0="60" x1="251" y1="89"/>
       <button name="MMB2" x0="269" y0="60" x1="427" y1="89"/>
       <button name="MMB3" x0="445" y0="60" x1="603" y1="89"/>
       <button name="MMB4" x0="93" y0="108" x1="251" y1="137"/>
       <button name="MMB5" x0="269" y0="108" x1="427" y1="137"/>
       <button name="MMB6" x0="445" y0="108" x1="603" y1="137"/>
       <button name="MMB7" x0="93" y0="156" x1="251" y1="185"/>
       <button name="MMB8" x0="269" y0="156" x1="427" y1="185"/>
       <button name="MMB9" x0="445" y0="156" x1="603" y1="185"/>
       <button name="MMB10" x0="93" y0="204" x1="251" y1="233"/>
       <button name="MMB11" x0="268" y0="204" x1="437" y1="233"/>
       <button name="MMB12" x0="444" y0="204" x1="613" y1="233"/>
       <button name="MMB13" x0="92" y0="300" x1="261" y1="329"/>
       <button name="MMB14" x0="268" y0="300" x1="437" y1="329"/>
       <button name="MMB15" x0="444" y0="300" x1="613" y1="329"/>
        </spu>
      </stream>
    </subpictures>
    and the MMSpuL.xml
    Code:
    <subpictures>
      <stream>
        <spu start="00:00:00.0"
             highlight="F:\Filme\Volume8\Temp\MMHighL.png"
             select="F:\Filme\Volume8\Temp\MMActL.png"
             force="yes"
             autoorder="rows">
       <button name="MMB1" x0="93" y0="117" x1="251" y1="139"/>
       <button name="MMB2" x0="269" y0="117" x1="427" y1="139"/>
       <button name="MMB3" x0="445" y0="117" x1="603" y1="139"/>
       <button name="MMB4" x0="93" y0="153" x1="251" y1="175"/>
       <button name="MMB5" x0="269" y0="153" x1="427" y1="175"/>
       <button name="MMB6" x0="445" y0="153" x1="603" y1="175"/>
       <button name="MMB7" x0="93" y0="189" x1="251" y1="211"/>
       <button name="MMB8" x0="269" y0="189" x1="427" y1="211"/>
       <button name="MMB9" x0="445" y0="189" x1="603" y1="211"/>
       <button name="MMB10" x0="93" y0="225" x1="251" y1="247"/>
       <button name="MMB11" x0="268" y0="225" x1="437" y1="247"/>
       <button name="MMB12" x0="444" y0="225" x1="613" y1="247"/>
       <button name="MMB13" x0="92" y0="297" x1="261" y1="319"/>
       <button name="MMB14" x0="268" y0="297" x1="437" y1="319"/>
       <button name="MMB15" x0="444" y0="297" x1="613" y1="319"/>
        </spu>
      </stream>
    </subpictures>
    Quote Quote  
  5. Member
    Join Date
    Dec 2008
    Location
    United Kingdom
    Search Comp PM
    Thanks for your wonderful explanation, this helped me to understand what's going on and what dvdauthor and spumux actually do a little better.

    I managed to get all 15 buttons working simply by adding widescreen="nopanscan" in all of the <video> tags in my dvdauthor xml.

    J
    ---

    I have some other questions that are really just my technical curiosity...

    I initially thought that menu buttons were a single subpicture track and the player could crop it to only display certain areas, but now I'm inferring that spumux inserts the button highlights as a single subpicture track and dvdauthor then cuts it up according to the button information and puts the different (cropped) parts to different trakcs, is this correct?

    From this, I'm wondering if it's technically possible to have overlapping buttons (or at least where the bounding rectangles overlap) by initially putting them on separate tracks with multiple spumux executions (like you did above)?
    Quote Quote  
  6. ...I initially thought that menu buttons were a single subpicture track and the player could crop it to only display certain areas...
    This is IMHO the correct assumption. But for different display modes (widescreen, letterbox or pan&scan) the player can be forced to use a specific subpicture track.

    ...if it's technically possible to have overlapping buttons...
    Yes, but these are never shown together as the player has to be in one 'mode': widescreen, letterbox or pan&scan. You cannot show two subpicture tracks within one menu at the same time.

    One more hint:
    If you just use video... widescreen=nopanscan, the button highlights are displaced if shown on a 4:3 TV in letterbox mode. That's why Gfd uses two different subpicture tracks with different button positions as shown above.
    Quote Quote  
  7. Member
    Join Date
    Dec 2008
    Location
    United Kingdom
    Search Comp PM
    Oh... I thought that nopanscan was some kind of directive to the DVD player to never display the content in pan&scan mode, forcing letterbox mode on 4:3 displays (and at the same time telling dvdauthor that it only needs to create normal and letterbox scaled sub-pictures). This would be a desirable side-effect... is it possible to enforce this?

    I really wish there was more complete documentation for dvdauthor xml format (including what all the different settings mean and how they affect the output) so I knew what everything does. I've had to patch it all together so far from the man page, examples found on the web, and output from various GUIs (none of which seemed to do exactly what I wanted which is why I ended up doing it manually).

    J
    Quote Quote  
  8. ...to never display the content in pan&scan mode
    Yes. Correct.
    ...that it only needs to create normal and letterbox scaled sub-pictures
    But you have to provide these scaled sub-pictures. dvdauthor doesn't create them itself. As long as you use this DVD only by yourself on a 16:9 TV, there is no problem. If you play this DVD on a 4:3 TV it is shown letterboxed, but then the subpictures are not shown correctly. The dvdplayer will automatically scale the video (reduce the vertical resolution to 75%), but not the subpicture (which contains the highlight for the buttons).
    Quote Quote  



Similar Threads