From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: peter@easthope.ca
Cc: linux-media@vger.kernel.org
Subject: Re: JVC camera and Hauppauge PVR-150 framegrabber.
Date: Fri, 24 Mar 2017 07:21:04 -0300 [thread overview]
Message-ID: <20170324072052.74cbf218@vento.lan> (raw)
In-Reply-To: <E1crCiL-0001oB-BQ@dalton.invalid>
Em Thu, 23 Mar 2017 17:04:21 -0700
peter@easthope.ca escreveu:
> With a manual setting of the device path and ID, the V4L2 Test Bench
> produced this image from a JVC TK-1070U camera on a microscope.
> http://easthope.ca/JVCtoPVR150screen.jpg
>
> Setting the device in the Test Bench each time it is opened becomes
> tedious and no /etc/*v4l* exists. Can the default configuration be
> adjusted permanently without recompiling? How?
>
> Although too dark, the image from the microscope slide is faintly
> visible. The upper half of the image is on the bottom of the screen
> and the lower half is at the top. On a VCR I might try adjusting
> vertical sync. Is there an equivalent in the Test Bench?
You could use v4l2-ctl to set all parameters you need in order to
get a good quality image.
It is possible to automatically call it by adding a udev rule.
This link explains how to do things like that (although their
examples are for different use cases):
https://www.mythtv.org/wiki/Device_Filenames_and_udev
Some of examples have a directive like:
PROGRAM="..."
With basically makes udev to run a program or script when the device
gets detected.
Thanks,
Mauro
prev parent reply other threads:[~2017-03-24 10:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-24 0:04 JVC camera and Hauppauge PVR-150 framegrabber peter
2017-03-24 10:21 ` Mauro Carvalho Chehab [this message]
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=20170324072052.74cbf218@vento.lan \
--to=mchehab@s-opensource.com \
--cc=linux-media@vger.kernel.org \
--cc=peter@easthope.ca \
/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