Hello,
We get the same problem with using the decimation register. We are not
driver experts, but suspect that the V4L driver must be patched. Is there
anyone on this list who could help with that? Thanks.
Chris
At 10:49 AM 6/20/2002 +0200, you wrote:
On Wed, 19 Jun 2002 21:21:50 +0800
"Kevin Liao" <kevinliao@xxxxxxxxxx> wrote:
> I had ever applied your patch one month ago. But I saw very strange result
> for my BT878A. For example, the original sequence of even field for NTSC in
> one second was:
>
> 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28
> 29 30
>
> If I set btv->decimation to 10, 5 even fields should be dropped. Therefore
> the ideal output sequence (25 fields) should look be:
>
> 1 2 3 4 5 7 8 9 10 11 13 14 15 16 17 19 20 21 22 23 25 26 27 28 29
>
> Right? BUT, here comes the surprise! The real result I got for my BT878A
> was:
>
> 1 2 3 4 3 7 8 9 10 9 13 14 15 16 15 19 20 21 22 21 25 26 27 28 27
>
> That is, though the number of total even fields is still 25, 5 of them are
> repeated! I got actually 20 even fields. The worst thing is that you guys
> could image that what the above sequence looks like. And I had also tried
> different values of btv->decimation but it just didn't work at all. So,
> finally I give up the patch.
>
> Regards,
> Kevin
Quite interesting! I tested with PAL signal (25 fps), but was unable to
"number" the image.
I sometime get a "night club" effect :-), which might be the same thing as
you.
I think that's a software bug (in my code probably).
Benoit.
