All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-media@vger.kernel.org
Subject: Re: NTSC/PAL resolution support for "EasyCap" device
Date: Fri, 03 Jun 2016 13:35:08 +0200	[thread overview]
Message-ID: <1464953708.2432.51.camel@hadess.net> (raw)
In-Reply-To: <1495486.1uKbyyPPu6@avalon>

On Fri, 2016-06-03 at 14:08 +0300, Laurent Pinchart wrote:
> 
<snip>
> > Full lsusb below.
> 
> Thanks. The device only advertises two resolutions, 640x480 and
> 352x288.

As I read.

> > > If the device doesn't expose resolutions other than the above
> > > two, the
> > > box could be lying, or the device could use non-standard
> > > extensions to UVC
> > > to support additional resolutions. The first step would be to try
> > > the
> > > camera in a  Windows machine to see if additional resolutions are
> > > available (without installing any additional device-specific
> > > software).
> > 
> > I should be able to find a Windows somewhere, but which application
> > should I use to see if those resolutions are indeed available?
> 
> My (lack of) Windows knowledge doesn't allow me to answer that
> question, but 
> I'm sure searching online will give you answers.

"AMCap" seems to be the simplest software for that purpose, and it only
shows "640x480".

> > BTW, given the price of the device, I'd be fine getting one for you
> > to
> > test (6€ from eBay, shipping included).
> 
> Thanks, but I'm already overwhelmed with work, I'd rather have you
> performing 
> the tests. Beside, I have no Windows machine :-)

I've started the process of yelling at the vendor.

Cheers

      reply	other threads:[~2016-06-03 11:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1464691129.3878.59.camel@hadess.net>
2016-06-02 22:37 ` NTSC/PAL resolution support for "EasyCap" device Laurent Pinchart
2016-06-03 10:53   ` Bastien Nocera
2016-06-03 11:08     ` Laurent Pinchart
2016-06-03 11:35       ` Bastien Nocera [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=1464953708.2432.51.camel@hadess.net \
    --to=hadess@hadess.net \
    --cc=laurent.pinchart@ideasonboard.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.