From: Frej Drejhammar <frej.drejhammar@gmail.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: video4linux-list@redhat.com, Trent Piepho <xyzzy@speakeasy.org>
Subject: Re: [PATCH 0 of 2] cx88: Enable additional cx2388x features. Version 2
Date: Sun, 16 Mar 2008 16:09:59 +0100 [thread overview]
Message-ID: <kod9eemd4.fsf@liva.fdsoft.se> (raw)
In-Reply-To: <200803161442.37610.hverkuil@xs4all.nl> (Hans Verkuil's message of "Sun, 16 Mar 2008 14:42:37 +0100")
Hi Hans,
> 1) Should we really expose these settings to the user? I have my
> doubts whether the average user would know what to do with this, ...
That was my initial take on it, therefore the first version of the
patch just added a module parameter. I reasoned that chroma AGC was
something you just needed to enable once depending on the quality of
your video-source. Then Trent Piepho suggested that the functionality
should really be exposed as controls. I think he has a point, consider
for example living in a place such as southern Germany where you could
receive both German PAL and French SECAM broadcasts. If you then also
used a composite/s-video external video source you would want to be
able to change the setting depending on your input and the channel you
tune to.
> ... and I also wonder whether it makes enough of a difference in
> picture quality.
For me it does, fiddling with the saturation and hue controls I never
managed to get neutral color reproduction. The colors were either
washed out or saturated to look like a fifties technicolor movie. The
color killer does not make a very large impact for black and white
material (the only time it is needed), frankly I'm not sure if its not
just the placebo effect. I can live without color killer but
definitely not without chroma AGC.
> Note that a change like 'Chroma AGC must be disabled if SECAM is
> used' is a bug fix and should clearly go in.
But rather pointless as it currently cannot be enabled...
> 2) Chroma AGC and color killer is also present in other chips
> (cx2584x, cx23418, possibly other similar Conexant chips). So if we
> decide on allowing these controls I would prefer making this a
> standard control, rather than a private one.
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.
> Personally I think these controls are too low-level, but that's just
> my opinion. Most chips contains a whole array of similar tweaks that
> you can do, and exposing them all is not the way to go.
Personally I'm against dumbing down the driver and not exposing
features which are useful. An argument against your stance is that the
V4L2-spec defines V4L2_CID_AUTOGAIN, V4L2_CID_AUTO_WHITE_BALANCE and
V4L2_CID_HUE_AUTO (half of the functionality of chroma AGC) which are
similar functions. Also consider the MPEG controls, most of which are
fairly obscure if you are not familiar with the MPEG specs.
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 15:10 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 [this message]
2008-03-16 20:28 ` Trent Piepho
2008-03-16 21:05 ` Frej Drejhammar
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=kod9eemd4.fsf@liva.fdsoft.se \
--to=frej.drejhammar@gmail.com \
--cc=hverkuil@xs4all.nl \
--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