Re: [Mjpeg-users] pulldown or yuvfps
Hallo > > > Most efficient would be to create a custom soft-pulldown that goes from > > > 18 to > > > 25 or 50 since you are using pal. Something like 2:3:3:3:2:3:3:3:3 will > > > convert 18 to 25. It would be a lot easier if you used NTSC framerates. > > > > Well not being a programer neither leaving in US/Canada It's gonna be a > > little difficult... > You'll need to be a programmer to add custom soft-pulldown support to > mpeg2enc. NTSC just makes the pulldown a nicer sequence that will be smoother > to watch. BTW: There are only some framerates allowed and storable in MPEG. (24, 24000:1001, 25, 30, 3:1001, 50, 6:1001) To store your stream you have to create somewhow to a framerate mpeg allowes. The way yuvfps does it is not that bad. To create you own style you "just" have to replace or extent the void resample(...) in yuvfps. Might be a interresting idea to be able to tell yuvfps you own resampling style. auf hoffentlich bald, Berni the Chaos of Woodquarter Email: [EMAIL PROTECTED] www: http://www.lysator.liu.se/~gz/bernhard --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ Mjpeg-users mailing list Mjpeg-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mjpeg-users
Re: [Mjpeg-users] Color / No color
On Tuesday 25 January 2005 17:25, Bernhard Praschinger wrote: > > Captures produced by lavrec always end up in B/W. OTOH, I can take xawtv > > and see my camcorders life feed in color! > > > > Specs: > > lavrec -v2 -fa -iP -a0 -d2 record.avi > > Which input do you have selected in XAWTV ? S-Video > If it is Composite -i p (PAL Composite) is the correct input -i P is the > PAL SVHS input. > Which card do you have ? DC30+ > Try using -i p once. S-Video is my problem child. Composite works fine. And right now I can't ever reproduce it, as lavrec captures nothing anymore from S-Video. (For more info, see the thread "DC30+ identified as DC10?"). I still haven't worked out what's the underlying problem here. It's capturing black only now. xawtv is black now too. ... /Rebooting/ Don't forget to physically disconnect composite first. Connecting S-Video in itself is not enough. I don't know why, but it helps. ... Ok. lavrec captures again. In B/W. No color. xawt does full color. > BTW: If you use the precompiled Suse mjpegtools package you don't have > tool like mpeg2enc and mp2enc. You can either get the whole package from > SF, or install the mjpegtools src package from the Suse disk, and enable > the build of mp2enc and mpeg2enc and compile. I will most definitely try these. Thanks for the pointers. Koos -- 43rd Law of Computing: Anything that can go wr fortune: Segmentation violation -- Core dumped --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ Mjpeg-users mailing list Mjpeg-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mjpeg-users
Re: [Mjpeg-users] pulldown or yuvfps
> Might be a interresting idea to be able to tell yuvfps you own > resampling style. Doesn't it exist in Kino ? That could be another option for me, to convert the all lot in DV then use the Fx slow down to get a proper speed. Results prove a bit choppy but not sure that I have a choice right now.. cheers E --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ Mjpeg-users mailing list Mjpeg-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mjpeg-users
Re: [Mjpeg-users] freebsd port: "undefined reference to quicktime_read_audio"
On Sat, 22 Jan 2005 09:36:05 -0800 (PST)
"Steven M. Schultz" <[EMAIL PROTECTED]> wrote:
> The latest version of libquicktime is 0.9.4 and it is necessary to
> use the cvs version of mjpegtools if you want quicktime support. You
> could try configuring mjpegtools using "--without-libquicktime" but
> a lot of fixes and improvements have been made in mjpegtools since
> 1.6.2 so getting the cvs version is a good idea.
>
> Cheers,
> Steven Schultz
>
>
Hi Steven,
took your advice and cvs'ed the files. But running autoconf259 produces errors
and the configure script produced doesn't run either (no wonder I think).
These are the errors:
# autoconf259
configure.ac:18: error: possibly undefined macro: AM_INIT_AUTOMAKE
If this token and others are legetimate, please use m4_pattern_allow
[no idea what that means - I never used autoconf before ,-{ ]
configure.ac:19: error: possibly undefined macro:AM_MAINTAINER_MODE
configure.ac:70: error: possibly undefined macro:AC_PROC_LIBTOOL
configure.ac:75: error: possibly undefined macro:AM_PROC_CC_STDC
configure.ac:85: error: possibly undefined macro:AM_PROC_AS
configure.ac:105: error: possibly undefined macro:AC_DEFINE
configure.ac:162: error: possibly undefined macro:AM_CONDITIONAL
configure.ac:301: error: possibly undefined macro:AM_PATH_GTK
configure.ac:311: error: possibly undefined macro:AM_PATH_SDL
#
I'd like to use mjpegtools, but I stumble from one obstacle into another
CVS-version of mjpegtools was 1.7.0.
Cheers,
Sebastian
---
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
___
Mjpeg-users mailing list
Mjpeg-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mjpeg-users
Re: [Mjpeg-users] freebsd port: "undefined reference to quicktime_read_audio"
On Tue, 25 Jan 2005, Sebastian Singer wrote:
> took your advice and cvs'ed the files. But running autoconf259 produces
> errors and the configure script produced doesn't run either (no wonder I
> think).
>
> These are the errors:
> # autoconf259
> configure.ac:18: error: possibly undefined macro: AM_INIT_AUTOMAKE
> configure.ac:19: error: possibly undefined macro:AM_MAINTAINER_MODE
> configure.ac:70: error: possibly undefined macro:AC_PROC_LIBTOOL
> configure.ac:75: error: possibly undefined macro:AM_PROC_CC_STDC
> configure.ac:85: error: possibly undefined macro:AM_PROC_AS
> configure.ac:105: error: possibly undefined macro:AC_DEFINE
> [no idea what that means - I never used autoconf before ,-{ ]
It means that autoconf could not find the automake or libtool or aclocal
macros.
AM_INIT_AUTOMAKE is defined in init.m4 and that is found in a 'aclocal'
directory.
Look in /usr/share _and_ /usr/local/share
You may need to have symlinks like these:
lrwxrwxr-x 1 root wheel 11 Dec 24 09:06 aclocal -> aclocal-1.8
drwxr-xr-x 2 smswheel 2048 Jan 12 15:31 aclocal-1.8
(1.8 is the automake version, not the autoconf version!)
Make similar symlinks for the version of automake that you have.
> CVS-version of mjpegtools was 1.7.0.
What version of automake do you have installed (automake --version)?
Then make the 'aclocal' symlinks mentioned above - there should
be some progress (before the next problem ;)).
Cheers,
Steven Schultz
---
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
___
Mjpeg-users mailing list
Mjpeg-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mjpeg-users
[Mjpeg-users] pulldown or yuvfps
Gday I was wondering what could be the most efficient method to slow down a movie. I have here some Super 8mm material that I reshoot frame by frame in ppm files. The original are playing at a nominal rate of 18 fps. Once encoded in mpeg2, grany is almost running through the TV screen. I thought that pulldown would be an option to bring 18 to 24 but obviously not since mpeg2enc is complaining about the rate Is ther a way I can go around that ? ++ WARN: [mpeg2enc] 3:2 movie pulldown with frame rate set to decode rate not display rate ++ WARN: [mpeg2enc] 3:2 Setting frame rate code to display rate = 5 (30.000fps) INFO: [mpeg2enc] Encoding MPEG-2 video to test_pulldown2.mpeg 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: 5 = 30.0++ WARN: [mpeg2enc] 3:2 movie pulldown with frame rate set to decode rate not di splay rate ++ WARN: [mpeg2enc] 3:2 Setting frame rate code to display rate = 5 (30.000 fps) INFO: [mpeg2enc] Encoding MPEG-2 video to test_pulldown2.mpeg 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: 5 = 30.0 INFO: [mpeg2enc] Bitrate: 7500 KBit/s INFO: [mpeg2enc] Quality factor: 8 (Quantisation = 9) (1=best, 31=worst) INFO: [mpeg2enc] Field order for input: none/progressive INFO: [mpeg2enc] Sequence unlimited length INFO: [mpeg2enc] Search radius: 16 INFO: [mpeg2enc] GOP SIZE RANGE 6 TO 15 INFO: [mpeg2enc] Setting colour/gamma parameters to "unspecified" INFO: [mpeg2enc] Progressive format frames = 1 INFO: [mpeg2enc] 3:2 Pulldown selected frame decode rate = 24.000 fps **ERROR: [mpeg2enc] Sample rate is greater than permitted in specified Level INFO: [mpeg2enc] Bitrate: 7500 KBit/s INFO: [mpeg2enc] Quality factor: 8 (Quantisation = 9) (1=best, 31=worst) INFO: [mpeg2enc] Field order for input: none/progressive INFO: [mpeg2enc] Sequence unlimited length INFO: [mpeg2enc] Search radius: 16 INFO: [mpeg2enc] GOP SIZE RANGE 6 TO 15 INFO: [mpeg2enc] Setting colour/gamma parameters to "unspecified" INFO: [mpeg2enc] Progressive format frames = 1 INFO: [mpeg2enc] 3:2 Pulldown selected frame decode rate = 24.000 fps **ERROR: [mpeg2enc] Sample rate is greater than permitted in specified Level here is the line I am using cat *.ppm | ppmtoy4m -F 18000:1000 -L | y4mscaler -I sar=1:1 -O size=720x576 -O chromass=420_MPEG2 -O sar=PAL | yuvdenoise -b 20,20,680,536 -r 16 -t 2 -c 80 -F -L 160 | mpeg2enc -r 16 -I 0 -B 96 -g 6 -G 15 -a 1 -H -4 2 -2 1 -F 2 -f 8 -M 2 -p -o test_pulldown.mpeg Or either using yuvfps ? Any suggestion welcome Thanks a lot E --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ Mjpeg-users mailing list Mjpeg-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mjpeg-users
Re: [Mjpeg-users] Color / No color
Hallo > Are there any particulars involved wrt color / BW? > Captures produced by lavrec always end up in B/W. OTOH, I can take xawtv and > see my camcorders life feed in color! > > Specs: > lavrec -v2 -fa -iP -a0 -d2 record.avi Which input do you have selected in XAWTV ? If it is Composite -i p (PAL Composite) is the correct input -i P is the PAL SVHS input. Which card do you have ? Try using -i p once. > SuSE 9.2 > kernel-default-2.6.8-24.10 > mjpegtools-1.6.2-54.1 BTW: If you use the precompiled Suse mjpegtools package you don't have tool like mpeg2enc and mp2enc. You can either get the whole package from SF, or install the mjpegtools src package from the Suse disk, and enable the build of mp2enc and mpeg2enc and compile. auf hoffentlich bald, Berni the Chaos of Woodquarter Email: [EMAIL PROTECTED] www: http://www.lysator.liu.se/~gz/bernhard --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ Mjpeg-users mailing list Mjpeg-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mjpeg-users
Re: [Mjpeg-users] y4mscaler v8.1
>> This minor update does two.five things: >> >>o Implement Keys' 4th-order cubic kernel --- as 'cubicK4' --- >> as suggested by Nicholas Boos. >> >>o Make 'cubicK4' the default kernel. > > Oh, so the default is cubicK4 rather than sinc:6 (which I believe > was mentioned as the default in 8.0) now? Yes --- although due to programmer blotz (noticed by Nicholas), 8.0 was still using 'linear' as the actual default. > One major use I make of y4mscaler is downscaling HD (1920x1080) for > 16:9 704x480 DVD. For that which of sinc:6 or cubicK4 is supposed > to be better? Or is the difference not likely to be noticeable? Well, to be honest, I have very little idea. If you have a lot of sharp edges (i.e. stuff that likes to ring), you'll probably notice a difference. I just put a bunch of 'worst-case' sample test cases up on the site: http://www.mir.com/DMG/Software/step-rings-table.html Alas, there is no perfect filter, -matt m. --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ Mjpeg-users mailing list Mjpeg-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mjpeg-users
Re: [Mjpeg-users] pulldown or yuvfps
> I was curious how the Super8 conversion was going - good to hear it's > progressed to the stage of encoding the data. almost there.. > The duplicated frames will compress very well but I agree that the > motion will not be as smooth. Well, can not have everything > camera Edouard finally decided on (was it the 1280x960 or the 1024x768 > model?). 1392*1038 Marlin AVT, using coriander, very nice camera, I am still working on the external trigger : an optical switch linked to the claw of the projector. > > > cat *.ppm | ppmtoy4m -F 18000:1000 -L | > > After that and before mpeg2enc add: > > y4mscaler -I sar=1:1 -O infer=exact -O sar=59:54 -O size=704x576 -S > option=sinc:6 > > Alternatively you could use > > y4mscaler -I sar=1:1 -O sar=PAL -O preset=DVD -S option=sinc:6 > > but that will pad to 720 with 8 pixels on each side I think (won't > be visible on a TV set of course due to overscan). Ok thanks, the first command line I sent was not properly thought after, my immediate concern was the fps rate. My mistake on this one. > Perhaps 'yuvfps' needs to be modified in a way that the pull-up > pattern could be specified - that would seem to be a good thing > to have about now ;) Or something that can actually cope with 18 fps to 25 fps or 24 fps, would be nice E --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ Mjpeg-users mailing list Mjpeg-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mjpeg-users
Re: [Mjpeg-users] pulldown or yuvfps
On Tue, 25 Jan 2005, E.Chalaron wrote: HI! I see this item was delayed in the queue for quite some time. I saw a reply long before the actual start of the thread arrived. Strange. >INFO: [mpeg2enc] Aspect ratio code: 1 = 1:1 pixels Oops - but I think I know what caused that problem... > here is the line I am using > > cat *.ppm | ppmtoy4m -F 18000:1000 -L | y4mscaler -I sar=1:1 -O size=720x576 > -O chromass=420_MPEG2 -O sar=PAL | yuvdenoise -b 20,20,680,536 -r 16 -t 2 -c It's probably necessary to specify the output SAR (-O sar=) before you give the size (-O size). That's so that y4mscaler knows what output sample aspect to use when doing the scaling. Try putting put the -O sar before the -O size thus: y4mscaler -I sar=1:1 -O sar=PAL -O size=720x576 -O chromass=420_MPEG2 I would use 704x576 instead of 720x576 y4mscaler -I sar=1:1 -O sar=PAL -O size=704x576 -O chromass=420_MPEG2 Why? Because 704x576 using 59:54 pixels *exactly* represents a 4/3 image and 720x576 59:54 does NOT. So if you're coming from 1024x768 (which is a 4/3 image using 1:1 pixels) it makes sense to go (exactly) to another 4/3 representation (704x576 59:54). But if you really want the 720xN size that's fine (perhaps you're editing the clip into a large show and all the clips need to have the same encoded frame size): y4mscaler -I sar=1:1 -O sar=PAL -O preset=DVD -O chromass=420_MPEG2 If you're not using the latest (8.1) y4mscaler then you really really want to add a "-S option=sinc:5" or similar to the options otherwise you'll end up using a simple 'linear' scaling kernel. -->>The other thing that you probably should add is a "-O infer=exact". For example when scaling one 16/9 picture (1920x1080 1:1) to another (704x480 40:33) with the default "-O infer=simplify" I get: INFO: [y4mscaler] < 1920x1088, SAR 1:1, top-field-first INFO: [y4mscaler] < chroma subsampling: 4:2:0 MPEG-2 (horiz. cositing) INFO: [y4mscaler] < chroma ss ratios: x 1:2 y 1:2 INFO: [y4mscaler] < active region: INFO: [y4mscaler] < 1877.33x1056.00 at 21.33,12.00 INFO: [y4mscaler] < matte region: INFO: [y4mscaler] < 1920x1088 at 0,0 (bg Y'CbCr: 16,128,128) INFO: [y4mscaler] === SCALING parameters: INFO: [y4mscaler] | Scaler: Matto's Generic Scaler INFO: [y4mscaler] | kernels: sinc:6, sinc:6 INFO: [y4mscaler] === TARGET parameters: = INFO: [y4mscaler] > stream: INFO: [y4mscaler] > 704x480, SAR 40:33, top-field-first INFO: [y4mscaler] < chroma subsampling: 4:2:0 MPEG-2 (horiz. cositing) INFO: [y4mscaler] < chroma ss ratios: x 1:2 y 1:2 INFO: [y4mscaler] > active region: INFO: [y4mscaler] > 704x480 at 0,0 (bg Y'CbCr: 16,128,128) INFO: [y4mscaler] > X ratio: 3/8 INFO: [y4mscaler] > Y ratio: 5/11 INFO: [y4mscaler] Output Stream Header: INFO: [y4mscaler] >>> frame size: 704x480 pixels (506880 bytes) Note how the active region was cropped to '1877x1056'. The aspect will be correct but the results weren't the anticipated ones. However adding "-O infer=exact": INFO: [y4mscaler] < 1920x1088, SAR 1:1, top-field-first INFO: [y4mscaler] < chroma subsampling: 4:2:0 MPEG-2 (horiz. cositing) INFO: [y4mscaler] < chroma ss ratios: x 1:2 y 1:2 INFO: [y4mscaler] < active region: INFO: [y4mscaler] < 1920.00x1080.00 at 0.00,0.00 INFO: [y4mscaler] < matte region: INFO: [y4mscaler] < 1920x1088 at 0,0 (bg Y'CbCr: 16,128,128) INFO: [y4mscaler] === SCALING parameters: INFO: [y4mscaler] | Scaler: Matto's Generic Scaler INFO: [y4mscaler] | kernels: sinc:6, sinc:6 INFO: [y4mscaler] === TARGET parameters: = INFO: [y4mscaler] > stream: INFO: [y4mscaler] > 704x480, SAR 40:33, top-field-first INFO: [y4mscaler] < chroma subsampling: 4:2:0 MPEG-2 (horiz. cositing) INFO: [y4mscaler] < chroma ss ratios: x 1:2 y 1:2 INFO: [y4mscaler] > active region: INFO: [y4mscaler] > 704x480 at 0,0 (bg Y'CbCr: 16,128,128) INFO: [y4mscaler] > X ratio: 11/30 INFO: [y4mscaler] > Y ratio: 4/9 INFO: [y4mscaler] Output Stream Header: INFO: [y4mscaler] >>> frame size: 704x480 pixels (506880 bytes) Note the different X and Y ratios AND the fact there is no cropping/padding . The 1920x1080 1:1 goes cleanly into 704x480 40:33 as expected. > Or either using yuvfps ? You might give yuvfps a try and see how it looks. Cheers, Steven Schultz --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over
Re: [Mjpeg-users] pulldown or yuvfps
On Tue, 25 Jan 2005, E.CHALARON wrote: > On Tue, 2005-01-25 at 15:40, Trent Piepho wrote: > > > Most efficient would be to create a custom soft-pulldown that goes from 18 > > to > > 25 or 50 since you are using pal. Something like 2:3:3:3:2:3:3:3:3 will > > convert 18 to 25. It would be a lot easier if you used NTSC framerates. > > Well not being a programer neither leaving in US/Canada It's gonna be a > little difficult... You'll need to be a programmer to add custom soft-pulldown support to mpeg2enc. NTSC just makes the pulldown a nicer sequence that will be smoother to watch. > > Or you could covert to 25fps with yuvfps, but doing that will encode the > > duplicate frames, wasting bits. It won't be as smooth either. > > > Ok I supected so ... It because a soft-pulldown can duplicate fields while yuvfps needs to act on whole frames. With a 2:3:3:etc pulldown, some fields are shown for 40 milliseconds, some for 60 milliseconds. With a frame based duplicator, you'll see some frames for 40 ms and some for 80 ms. Since NTSC has a faster flield rate, it would be 33ms vs 50 ms. > > The pulldown mpeg2enc uses incrases the frame rate by a ratio of 4:5. 24fps > > becomes 30. 18 would become 22.5 > > the difference between 22.5 and 25 is not huge ... No, it's not. You could use yuvcorrect to lie about your framerate, and change it from 18 to 20. Your movie will play about 11% fast now. You don't have audio to worry about, that's nice. Then a 2:3 pulldown will covert 20 to 25. Except. > > > ++ WARN: [mpeg2enc] 3:2 Setting frame rate code to display rate = 5 > > > (30.000fps) > > I assumed with this error that mpeg2enc pulldown will work only for NTSC > and therefore my question. y4mscaler however says to get it in PAL, so I > guess mpeg2enc would have follow. I understand then that -p will not > work in my case at all. It looks like mpeg2enc overrides your framerate with an NTSC one when you use the -p switch. It doesn't have to, it looks like a programming oversight. I wonder if you could just let mpeg2enc make you a 30 fps mpeg file, then change the rate code in the header from 5 to 3 to make it pal again? I don't know enough about mpeg to know if that will work. > > >INFO: [mpeg2enc] Aspe > > This is wrong, your pixels are not 1:1. Pick aspect code 2. > > I use a progressive camera I thought that pixels were 1:1. Probably are, but you used y4mscaler to change them from 1:1 to to 59:54. If you are making a pal DVD, you want your pixels to be 59:54 (or 118:81 if widescreen), or nothing will play it correctly. --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ Mjpeg-users mailing list Mjpeg-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mjpeg-users
Re: [Mjpeg-users] pulldown or yuvfps
>>INFO: [mpeg2enc] Aspect ratio code: 1 = 1:1 pixels > > Oops - but I think I know what caused that problem... ... > It's probably necessary to specify the output SAR (-O sar=) before > you give the size (-O size). That's so that y4mscaler knows > what output sample aspect to use when doing the scaling. (Actually, the problem was the "-a 1" given to mpeg2enc, which overrode the SAR tag output by y4mscaler.) >-->> The other thing that you probably should add is a "-O infer=exact". > For example when scaling one 16/9 picture (1920x1080 1:1) to another > (704x480 40:33) with the default "-O infer=simplify" I get: ... > Note how the active region was cropped to '1877x1056'. The aspect > will be correct but the results weren't the anticipated ones. Heh... I need to take a fresh look at the "simplify" heuristics; it's not doing the intended 'automagic' perfect behavior in this case. -matt m. --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ Mjpeg-users mailing list Mjpeg-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mjpeg-users
Re: [Mjpeg-users] pulldown or yuvfps
>here is the line I am using > >cat *.ppm | ppmtoy4m -F 18000:1000 -L | y4mscaler -I sar=1:1 -O size=720x576 >-O chromass=420_MPEG2 -O sar=PAL | yuvdenoise -b 20,20,680,536 -r 16 -t 2 -c >80 -F -L 160 | mpeg2enc -r 16 -I 0 -B 96 -g 6 -G 15 -a 1 -H -4 2 -2 1 -F 2 -f >8 -M 2 -p -o test_pulldown.mpeg > >Or either using yuvfps ? >Any suggestion welcome Well, no suggestions for your framerate stuff, but for the rest... In general, unless you have a very specific need, don't specify options which override input-stream parameters. The "-I sar=1:1" to y4mscaler is unnecessary --- the correct SAR will be read from the stream which ppmtoy4m creates. (And if that SAR is incorrect, change it by the '-A' option to ppmtoy4m --- i.e., -fix- the source, instead of -overriding- the source.) Same goes for mpeg2enc's "-a 1", "-F 2", and "-I 0". For y4mscaler, you could use "y4mscaler -I norm=PAL -O preset=DVD", and the 'norm=PAL' is only necessary because of the weird framerate. (If it were 25fps, y4mscaler would decide that it's PAL.) If you want to use the 704x576 framesize, (until I make a preset option for it) you could do "y4mscaler -I norm=PAL -O preset=DVD -O size=704x576" The "-O size=" will override the size set by the preset; actual bounds/cropping/etc calculations aren't performed until all of the arguments are processed (and later arguments overwrite earlier ones). -matt m. --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ Mjpeg-users mailing list Mjpeg-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mjpeg-users
Re: [Mjpeg-users] pulldown or yuvfps
On Tue, 25 Jan 2005, Matto Marjanovic wrote: > (Actually, the problem was the "-a 1" given to mpeg2enc, which > overrode the SAR tag output by y4mscaler.) Oops - I didn't spot that one. > The other thing that you probably should add is a "-O infer=exact". ... > >Note how the active region was cropped to '1877x1056'. The aspect > > Heh... I need to take a fresh look at the "simplify" heuristics; > it's not doing the intended 'automagic' perfect behavior in this case. It automagically surprised me :) That's the reason I watch the INFO/WARNING messages very carefully (of course ;)). A "sinc:6" downscale from HD to SD is cpu intense (surprisingly so - completely swamps the decode/encode processes) but the results are excellent. Cheers, Steven Schultz --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ Mjpeg-users mailing list Mjpeg-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mjpeg-users
[Mjpeg-users] more telecine stuff
Thanks all for your advice. Will do something about parameters :-) like RTFM and behaving myself... Anyway I have another small thing here. A 400 ft reel of Super 8 comes to 28800 individual frames, which is obviously too much to handle for bash/cat I know that find . -name \*.tga | xargs -n1 tgatoppm | ppmtoy4m | blabla will work but was wondering if I can get it directly in ppm the following is (of course) sending me back an error find . -name \*.ppm | ppmtoy4m | blabla **ERROR: [ppmtoy4m] Bad Raw PPM magic! An option would be to save in TGA. Any recommandation ? I probably missed something with xargs but not really sure how it works Cheers E --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ Mjpeg-users mailing list Mjpeg-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mjpeg-users
Re: [Mjpeg-users] more telecine stuff
On Wed, 26 Jan 2005, E.Chalaron wrote: > Thanks all for your advice. Will do something about parameters :-) like > Anyway I have another small thing here. > A 400 ft reel of Super 8 comes to 28800 individual frames, which is obviously > too much to handle for bash/cat I was waiting for that issue to come up ;) > the following is (of course) sending me back an error > > find . -name \*.ppm | ppmtoy4m | blabla > **ERROR: [ppmtoy4m] Bad Raw PPM magic! That is because the output of the 'find' is the names of the files, not the contents of the files. > Any recommandation ? I probably missed something with xargs but not really > sure how it works man xargs but you knew that already ;) something like find . -print | xargs cat | pnmtoy4m ... should be about right BUT that doesn't solve the problem because when xargs gathers up the maximum number of filenames that can go into a 'cat command' (xargs reads the NAMES of the files from stdin and contructs "cat file1.ppm file2.ppm ...") it will run the cat command. Perhaps with 1000 filenames (maybe more but still not all of them - if it could do all of them you wouldn't need xargs ;)). What would have been better would have been to capture the files in batches into subdirectories each containing a smaller number of files. If you had subdirectories called 1/, 2/, 3/, etc and each contained just 1000 files it would be a lot easier to deal with. Something like this (just off the top of my head) using subshells (each with its own limit on the number of characters for commandlines): ( (cd 1;cat *.ppm); (cd 2;cat *.ppm); (cd 3;cat *.ppm) ... ) | ... If I'm correct then each subshell inside a ( ) pair has its own limit on commandline size and the result will be a stream of ppm data. Hopefully the above will give some ideas for experimentation (maybe a variation can be used to reorganize the files into subdirectories). Cheers, Steven Schultz --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ Mjpeg-users mailing list Mjpeg-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mjpeg-users
Re: [Mjpeg-users] pulldown or yuvfps
On Tue, 25 Jan 2005, Matto Marjanovic wrote: > The "-I sar=1:1" to y4mscaler is unnecessary --- the correct SAR will > be read from the stream which ppmtoy4m creates. (And if that SAR True - it is un-necessary. But when I use "-I sar=1:1" it is not to _override_ but to _remind_ - it's an explicit pointer to me what's going on. The input, in my case, is already 1:1 but I chose to use the -I sar as a hint to me (not y4mscaler). > -fix- the source, instead of -overriding- the source.) > > Same goes for mpeg2enc's "-a 1", "-F 2", and "-I 0". Now that I agree with 100% (and I think I also made that point). If mpeg2enc isn't giving the expected results then the stream is not properly formed and needs to be fixed. > For y4mscaler, you could use "y4mscaler -I norm=PAL -O preset=DVD", > and the 'norm=PAL' is only necessary because of the weird framerate. > > If you want to use the 704x576 framesize, (until I make a preset > option for it) you could do > "y4mscaler -I norm=PAL -O preset=DVD -O size=704x576" Except when coming from the miniDV camcorder I always use 704x480 (or for very long playing discs the "CVD" 352x480 size). If you're using a Canopus (or other analog -> DV converter) take a look at one of the frames some time - you will _plainly_ see the 704x480 or 704x576 frame inside the 720xN DV frame and 8 pixels of junk/black on each side. Hmmm, not sure what would be a good name for the preset. In Apple's parlance the 704 size is what they call "cropped D1" (D1 being 720x486). Cheers, Steven Schultz --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ Mjpeg-users mailing list Mjpeg-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mjpeg-users
