From: Hans de Goede <hdegoede@redhat.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: libv4l conversion problem
Date: Mon, 18 Oct 2010 09:59:09 +0200 [thread overview]
Message-ID: <4CBBFE4D.7000604@redhat.com> (raw)
In-Reply-To: <4CB6E671.2060706@mlbassoc.com>
Hi,
On 10/14/2010 01:16 PM, Gary Thomas wrote:
> Hans,
>
> Please forgive the direct email; try as I might, I could not
> find any other vehicle to discuss this (feel free to steer me
> to the proper place).
>
There indeed is a lack of a mailinglist or forum for
v4l-utils. This has been discussed before and it was decided
that given the low amount of discussion around v4l-utils we will
just use the linux-media mailing list for this (added to the CC).
> I'm working with the latest code (0.8.1) on an embedded ARM
> system which has a camera that can only deliver UYVY422 data.
Ok, so when you say UYVY422, I assume that this is packed data,
right, so not some planar format, right? libv4l supports
converting UYVY422 packed data to:
RGB24
BGR24
YUV420 (planar)
YVU420 (planar)
> The problem I have is that most everything else, e.g. I'm trying
> to run cheese, wants YUYV422.
cheese specifically should be happy with almost any YUV or RGB
format as it uses gstreamer. I know for a fact that it works
happily with libv4l's YUV420 (planar) output.
> Should the library be able to handle this case (device only
> does UYUV and application wants YUYV)?
It does not support converting to packed yuv formats, but it does
support conversion to planar yuv formats. At least for cheese
this should work fine.
> Any suggestions how I move forward?
Make sure that your gstreamer is compiled with libv4l support.
Regards,
Hans
parent reply other threads:[~2010-10-18 7:56 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <4CB6E671.2060706@mlbassoc.com>]
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=4CBBFE4D.7000604@redhat.com \
--to=hdegoede@redhat.com \
--cc=gary@mlbassoc.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.