From: Florent Audebert <florent.audebert@anevia.com>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: linux-media@vger.kernel.org
Subject: Re: HVR-1300 analog inputs
Date: Mon, 06 Jun 2011 18:45:06 +0200 [thread overview]
Message-ID: <4DED0412.4030708@anevia.com> (raw)
In-Reply-To: <BANLkTi=zUfg9hAN8X9nrPEOMgtUzsKrbOw@mail.gmail.com>
On 06/01/2011 05:49 PM, Devin Heitmueller wrote:
> On Wed, Jun 1, 2011 at 11:36 AM, Florent Audebert
> <florent.audebert@anevia.com> wrote:
>> I'm experimenting around with an Hauppauge HVR-1300 (cx88_blackbird) analog
>> inputs (PAL-I signal).
>>
> You probably won't be able to go any higher than a width of 720. That
> said, it looks like either the driver is not responding properly or
> the application doesn't realize that the driver returned it's maximum
> field width (the V4L2 API specifies that in the S_FMT call that if the
> calling application specifies an invalid width, the driver can return
> a valid width and the application should recognize and use that
> value).
Thanks for your answer.
I've tried using mplayer as suggested in another post. Resolution is
alright with both composite and s-video (PAL-I). I suppose something
went wrong with qv4l2.
Nonetheless, I have vertical lines when using s-video at MPEG device
output (more visible in white areas)[1].
Reading from capture device is alright whether s-video (input=2) or
composite (input=1) is selected. I've tested it like this:
mplayer tv:// -tv driver=v4l2:input=1:normid=4:device=/dev/video0
Note that I am using media_build.git and mplayer trunks.
Any idea why I'm getting those vertical lines with s-video from decoder
output only ?
Regards,
[1] http://bit.ly/iEm8xd
--
Florent Audebert
next prev parent reply other threads:[~2011-06-06 16:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 15:36 HVR-1300 analog inputs Florent Audebert
2011-06-01 15:49 ` Devin Heitmueller
2011-06-01 21:48 ` linuxtv
2011-06-06 16:45 ` Florent Audebert [this message]
2011-06-06 16:55 ` Devin Heitmueller
2011-06-06 17:17 ` Florent Audebert
2011-06-06 17:22 ` Devin Heitmueller
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=4DED0412.4030708@anevia.com \
--to=florent.audebert@anevia.com \
--cc=dheitmueller@kernellabs.com \
--cc=linux-media@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.