Bernhard Praschinger wrote:
> Hallo
>
> I have got a bug report from Petr, he found in the mjpegtools RC2.
>
> The patches look ok for me
>
> Here is his mail:
> I tried to compile the RC2 and encountered the following problems:
>
> 2) mjpegtools-1.9.0rc2/utils/cpu_accel.c:364,368:
> implic
Hallo
> Thank you for your help. I tried your suggestion of -i n:0 but same
> result, blank record without error. You asked what input on the bt8x8 card
> I'm capturing from - the answer is composite. xawtv picks up image or
> video played on the camera OK indicating use of composite1, overlay mod
Am Mittwoch, den 09.05.2007, 16:08 +1000 schrieb Mark Heath:
> By the way, which frame rate converter is considered the *best* at
> the moment?
Motion compensated is the only one which makes sense:
These are the needed steps (and they allready can be done with the
mjpeg-tools...)
1. deinterla
Erm, just a tip. If you must use a BTTV-card for capturing (you really
should look for some other solution if you do captures on a regular
basis...) you must be aware of an intensional(!) bug inside the driver:
YUV 4:2:0 is broken with BTTV-cards. YUV 4:2:0 doesn't retain correct
interlacing on BT
On Wed, 9 May 2007, Petr Cerny wrote:
> > missing #include
>
> If you don't like malloc.h, probably posix_memalign() could be of use.
If you look more closely at the code you will see that the
reference to memalign() (for which malloc.h is needed) is in the
posix_memal
