Robert Suetterlin wrote:
>
> Hello everyone,
>
> I already applied with this problem and already got an answer which (of
>course :) did not satisfy me fully.
>
> Again: My problem is, that my bttv (card? driver? whatever?) drops first fields. So
>when I grab a field the dirver? knows it must grab two fields and grabs the second
>fields of consecutive frames. It could also be that it grabs field two of frame x and
>field one of frame x+1.
> I have two problems: 1) How can I diagnose/detect this error easily (i.e.
>should I measure the time it takes to grab fields, is there an ioctl, or do I have to
>change to vl4-two, ...)?
> 2) Is this a general or known problem with other people and how can I fix it?
>
> Point two was already answered in the following way: Try all bttv-cards and see if
>the error vanishes with one of them. Point one was hinted to: try v4l-two, this
>allows for example to grab single fields.
>
> These answers did not satisfy me fully as I already stated above, but still there
>were some hints. And I have a few more refined questions.
> Trying every one of the 40-something drivercards is not such a good idea in my
>opinion, what is the big difference anyway? Number of composite or svhs connectors,
>does the card have Teletext or not, or an radio reciever...
> So question one: What is the difference in card-type, can I define a new
>card-type (and how), should I look this up in the source code myself?
> And two: Is it advisable to change to v4l-two (as it allows better
>diagnostics, or why?), how to do it, or where to get information on this?
>
> Thank You,
>
> Robert S. {:).
Don't go to v4l2 - it is even worse there. At one stage I tried
desparately to track down the source of this problem, but without
success. Windows doesn't seem to have this problem though, so there
MUST be a solution... I just wish I could find it :-<
-justin
--
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject.
