From: Frej Drejhammar <frej.drejhammar@gmail.com>
To: Trent Piepho <xyzzy@speakeasy.org>
Cc: video4linux-list@redhat.com
Subject: Re: [PATCH 0 of 2] cx88: Enable additional cx2388x features. Version 2
Date: Sun, 16 Mar 2008 22:05:11 +0100 [thread overview]
Message-ID: <k1w6a2xdk.fsf@liva.fdsoft.se> (raw)
In-Reply-To: <Pine.LNX.4.58.0803161258550.20723@shell4.speakeasy.net> (Trent Piepho's message of "Sun, 16 Mar 2008 13:28:06 -0700 (PDT)")
Trent,
> One of the things you should do it make the control inactive when in
> SECAM mode. V4L2 has a flag to indicate controls that don't apply
> to the device's current mode.
I guess it is the V4L2_CTRL_FLAG_INACTIVE flag (in the flag field of
struct v4l2_queryctrl) you are referring to, correct?
> CAGC makes a difference for me too. Some of my channels are over
> saturated and some are under saturated and CAGC fixes them. I don't
> recall if I posted pictures last time CAGC came up, but it really
> does make a difference.
Good that I'm not the only one who wants/needs it :)
> I haven't ever been able to notice an effect from color killer.
> Maybe if you had poor reception from a B&W source? Not much black
> and white on broadcast TV these days.
So maybe I should just skip the color killer then...
>> A quick grep shows that the bttv-driver also exposes chroma AGC as
>> a private control. Cx2584x has chroma AGC enabled by default. Maybe
>> the right thing to do is to enable chroma AGC by default for PAL
>> and NTSC? Chroma AGC is something you'll find on most VCRs and
>> TVs, and then it is on by default.
>
> That's what I would do. Have a standard control for CAGC and turn
> it on by default.
Then that's what I'll do. Expect a revised version of the patch which
enables CAGC by default for PAL+NTSC and implements the
V4L2_CTRL_FLAG_INACTIVE by the end of the week.
> If I wanted to be told I wasn't worthy to use my hardware, I'd run
> windows!
Hear, hear! :)
Regards,
--Frej
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next prev parent reply other threads:[~2008-03-16 21:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-16 12:49 [PATCH 0 of 2] cx88: Enable additional cx2388x features. Version 2 Frej Drejhammar
2008-03-16 12:49 ` [PATCH 1 of 2] cx88: Add user control for chroma AGC Frej Drejhammar
2008-03-16 12:49 ` [PATCH 2 of 2] cx88: Add user control for color killer Frej Drejhammar
2008-03-16 13:42 ` [PATCH 0 of 2] cx88: Enable additional cx2388x features. Version 2 Hans Verkuil
2008-03-16 15:09 ` Frej Drejhammar
2008-03-16 20:28 ` Trent Piepho
2008-03-16 21:05 ` Frej Drejhammar [this message]
2008-03-16 23:27 ` Vanessa Ezekowitz
2008-03-17 10:33 ` Hans Verkuil
2008-03-17 13:14 ` Mauro Carvalho Chehab
2008-03-17 16:17 ` Frej Drejhammar
[not found] ` <47DDB7A7.6000400@foks.us>
2008-03-17 1:40 ` Trent Piepho
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=k1w6a2xdk.fsf@liva.fdsoft.se \
--to=frej.drejhammar@gmail.com \
--cc=video4linux-list@redhat.com \
--cc=xyzzy@speakeasy.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox