From: Anne W. <can...@go...> - 2007-04-13 14:59:11
|
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> force="yes" start="00:00:00:00" image="airport.jpg" highlight="airport_h.png" autooutline="infer" outlinewidth="6" autoorder="rows"> </spu> </stream> </subpictures> I then tried to use it so - spumux airport.xml < Airport.mpg > airport.mpg DVDAuthor::spumux, version 0.6.14. Build options: gnugetopt iconv freetype fribidi Send bugs to <dvd...@li...> ERR: text not allowed here What am I doing wrong? Thanks Anne |
From: Anne W. <can...@go...> - 2007-04-13 15:52:44
|
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 |
From: Giacomo C. <co...@na...> - 2007-04-13 16:26:27
|
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 |
From: Anne W. <can...@go...> - 2007-04-13 16:34:07
|
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 |
From: Anne W. <can...@go...> - 2007-04-13 17:53:02
|
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 <dvd...@li...> 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 |
From: Ben H. <be...@de...> - 2007-04-13 22:34:50
|
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 <dvd...@li...> >=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 |
From: Joe F. <pen...@gm...> - 2007-04-14 02:42:39
|
On 4/13/07, Ben Hutchings <be...@de...> 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 |
From: Roger I. <ri...@ri...> - 2007-06-10 23:41:48
|
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 ri...@ri... |
From: Anne W. <can...@go...> - 2007-04-14 12:04:19
|
On Saturday 14 April 2007, Joe Friedrichsen wrote: > On 4/13/07, Ben Hutchings <be...@de...> 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 |
From: Joe F. <pen...@gm...> - 2007-04-14 16:38:50
|
On 4/14/07, Anne Wilson <can...@go...> wrote: > On Saturday 14 April 2007, Joe Friedrichsen wrote: > > On 4/13/07, Ben Hutchings <be...@de...> 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 |
From: Anne W. <can...@go...> - 2007-04-14 17:05:49
|
On Saturday 14 April 2007, Joe Friedrichsen wrote: > On 4/14/07, Anne Wilson <can...@go...> 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 |
From: Joe F. <pen...@gm...> - 2007-04-14 18:18:40
|
On 4/14/07, Anne Wilson <can...@go...> 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 |
From: Anne W. <can...@go...> - 2007-04-14 19:22:58
|
On Saturday 14 April 2007, Joe Friedrichsen wrote: > On 4/14/07, Anne Wilson <can...@go...> 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 |
From: Joe F. <pen...@gm...> - 2007-04-14 20:26:05
|
On 4/14/07, Anne Wilson <can...@go...> 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 |
From: Anne W. <can...@go...> - 2007-04-14 21:05:18
|
On Saturday 14 April 2007, Joe Friedrichsen wrote: > On 4/14/07, Anne Wilson <can...@go...> 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 <dvd...@li...> 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 |
From: Joe F. <pen...@gm...> - 2007-04-14 21:28:45
|
On 4/14/07, Anne Wilson <can...@go...> wrote: > spumux airport_spu.xml < Airport.mpg > airport.mpg > DVDAuthor::spumux, version 0.6.14. > Build options: gnugetopt iconv freetype fribidi > Send bugs to <dvd...@li...> > > 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 |
From: Joe F. <pen...@gm...> - 2007-04-14 21:15:21
|
On 4/14/07, Joe Friedrichsen <pen...@gm...> 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 <dvd...@li...> 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 |
From: Anne W. <can...@go...> - 2007-04-15 10:13:09
|
On Saturday 14 April 2007, Joe Friedrichsen wrote: > On 4/14/07, Joe Friedrichsen <pen...@gm...> 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 <dvd...@li...> > > 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 |
From: Anne W. <can...@go...> - 2007-04-15 11:38:19
Attachments:
gimp.jpg
|
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 |
From: Joe F. <pen...@gm...> - 2007-04-15 17:41:33
|
On 4/15/07, Anne Wilson <can...@go...> 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 |
From: Anne W. <can...@go...> - 2007-04-15 19:16:51
|
On Sunday 15 April 2007, Joe Friedrichsen wrote: > On 4/15/07, Anne Wilson <can...@go...> 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 |
From: Joe F. <pen...@gm...> - 2007-04-15 22:52:33
|
On 4/15/07, Anne Wilson <can...@go...> 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 |
From: Anne W. <can...@go...> - 2007-04-16 12:26:18
|
On Sunday 15 April 2007, Joe Friedrichsen wrote: > On 4/15/07, Anne Wilson <can...@go...> 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 <xbi...@fr...>, 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 |
From: Joe F. <pen...@gm...> - 2007-04-16 15:13:57
|
On 4/16/07, Anne Wilson <can...@go...> 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 |
From: Anne W. <can...@go...> - 2007-04-16 15:35:36
|
On Monday 16 April 2007, Joe Friedrichsen wrote: > On 4/16/07, Anne Wilson <can...@go...> 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 |