From: linuxtv <linuxtv@hubstar.net>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: Florent Audebert <florent.audebert@anevia.com>,
linux-media@vger.kernel.org
Subject: Re: HVR-1300 analog inputs
Date: Wed, 01 Jun 2011 22:48:54 +0100 [thread overview]
Message-ID: <4DE6B3C6.5020706@hubstar.net> (raw)
In-Reply-To: <BANLkTi=zUfg9hAN8X9nrPEOMgtUzsKrbOw@mail.gmail.com>
Only FYI,
I am using the HVR-1300 with the build-media.git repo (sorry I forget
the correct name). UK PAL-I capturing fine at full res. Using mtythv and
tested using smplayer on /dev/video0 (or video1). (Full UK PAL res).
I know that won't directly help, but at least you know that is can/does
work at full res.
On 01/06/11 16:49, Devin Heitmueller wrote:
> On Wed, Jun 1, 2011 at 11:36 AM, Florent Audebert
> <florent.audebert@anevia.com> wrote:
>
>> Hi,
>>
>> I'm experimenting around with an Hauppauge HVR-1300 (cx88_blackbird) analog
>> inputs (PAL-I signal).
>>
>> Using qv4l2 (trunk) and 2.6.36.4, I successfully get a clean image on both
>> composite and s-video inputs with resolutions of 640x480 or less.
>>
>> With any higher resolutions, I have thin horizontal lines at moving
>> positions (seems to cycle)[1].
>>
>> I've tried various settings using qv4l2 on /dev/video0 and /dev/video1 with
>> no success.
>>
>> Is there a way to get higher encoding resolution from this board ?
>>
> 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).
>
> Devin
>
>
next prev parent reply other threads:[~2011-06-01 21:49 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 [this message]
2011-06-06 16:45 ` Florent Audebert
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=4DE6B3C6.5020706@hubstar.net \
--to=linuxtv@hubstar.net \
--cc=dheitmueller@kernellabs.com \
--cc=florent.audebert@anevia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox