Re: [Mjpeg-users] lavrec quicktime

2003-07-14 Thread Ronald Bultje
Hi Kevin, On Mon, 2003-07-14 at 15:52, Dehoff, Kevin wrote: > lavrec -f q -w -g 640x480 -i n -q 100 -s test.mov Use -d2 or -d1 instead of -g (...). :). Ronald -- Ronald Bultje <[EMAIL PROTECTED]> --- This SF.Net email sponsored by: Parasof

[Mjpeg-users] --E b a y-- Auction Course.....imitative electronic deception

2003-07-14 Thread Vito Shipley
np o rk

[Mjpeg-users] Ignore my previous message

2003-07-14 Thread Giles Jones
I was recording with lavrec and the -fA option, don't know how that got in there! Doh! Driver is working great, good work! -- G. O. Jones --- --- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing & mor

[Mjpeg-users] Buz field order problem

2003-07-14 Thread Giles Jones
Hi folks. Until recently I was using a CVS version of the driver with a Gentoo 2.4.19/20 kernel. It worked fine, but I tried this driver with the CK 2.4.20 kernel I'm using now and it didn't work too well (lots of dropped frames). I'm now using 0.9.4 and it appears to have a problem with interl

AW: [Mjpeg-users] lavrec quicktime

2003-07-14 Thread Bernhard Frühmesser
Hello, I can capture at full size with my DC10+ when I use the Quicktime-Format, I use this cmd: Lavrec -f q -g 768x576 (for PAL) -d1 -s -c 2 -a 16 -q 85 test.mov It works fine. There is something in the HOWTO about the DC10+ features about the capture size and so on Bernhard

[Mjpeg-users] lavrec quicktime

2003-07-14 Thread Dehoff, Kevin
Hi. I've just recently started using the mjpeg tools to pull some videos off an analog camera through a DC10+ card. Because I want to do some higher-level editing, I need the files in the quicktime format in order to use cinelerra. However, every time I try and capture, I only get a resolut

[Mjpeg-users] Re: mjpegtools compile problem (fwd)

2003-07-14 Thread Gernot Ziegler
Hej Raena ! No prob; I'll just take the help of mjpeg-users now to accelerate the process :-) Follow the INSTALL file instructions, but put jpeg-mmx either in the same directory that libmovtar sits in, or into /usr/local/src/jpeg-mmx there is abug in configure.in that you might have triggered...