linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Frank Schäfer" <fschaefer.oss@googlemail.com>
To: hverkuil@xs4all.nl
Cc: Hans de Goede <hdegoede@redhat.com>, linux-media@vger.kernel.org
Subject: Re: qv4l2-bug / libv4lconvert API issue
Date: Wed, 03 Oct 2012 19:41:20 +0300	[thread overview]
Message-ID: <506C6AB0.2010608@googlemail.com> (raw)
In-Reply-To: <201210031432.39578.hverkuil@xs4all.nl>

Am 03.10.2012 15:32, schrieb Hans Verkuil:
> On Wed 3 October 2012 12:22:48 Frank Schäfer wrote:
>> Hi Hans,
>>
>> Am 30.09.2012 11:54, schrieb Hans de Goede:
>>> Hi,
>>>
>>> On 09/28/2012 07:09 PM, Frank Schäfer wrote:
>>>> Hi,
>>>>
>>>> Am 27.09.2012 21:41, schrieb Hans de Goede:
>>>>> Hi,
>>>>>
>>>>> On 09/27/2012 03:20 PM, Frank Schäfer wrote:
>>>>>
>>>>> <snip>
>>>>>
>>>>>>> What you've found is a qv4l2 bug (do you have the latest version?)
>>>>>> Of course, I'm using the latest developer version.
>>>>>>
>>>>>> Even if this is just a qv4l2-bug: how do you want to fix it without
>>>>>> removing the format selction feature ?
>>>>> Well, if qv4l2 can only handle rgb24 data, then it should gray out the
>>>>> format selection (fixing it at rgb24) when not in raw mode.
>>>> So you say "just remove this feature from qv4l2".
>>>> I prefer fixing the library / API instead.
>>> No I'm suggesting to keep the feature to select which input format
>>> to use when in raw mode, while at the same time disabling the feature)
>>> when in libv4l2 mode. What use is it to ask libv4l2 for say YUV420 data
>>> and then later ask libv4lconvert to convert this to RGB24, when you could
>>> have asked libv4l2 for RGB24 right away.
>> I assume the idea behind input format selction when using libv4l2 is to
>> provide a possibilty to test libv4l2 ?
> The main reason why I show all formats is that the driver reports all these
> formats, so one should be able to select them in order to test the driver.
>
> And I'm using libv4l2convert so that I can actually see a picture. For formats
> like MPEG that are unsupported by libv4l2convert I just dump the 'image' as is.

Yes, but for pure testing of the driver output formats, it is better to
open the device in raw mode and convert the picture for GUI-output with
a v4lconvert_convert() call.

> It is counterintuitive if a YUV format is converted to a proper picture using
> qv4l2 -r, but that it is all wrong with qv4l2.

I'm not sure I understand what you mean...

Regards,
Frank

> I'm all for improving the library.
>
> Regards,
>
> 	Hans


      reply	other threads:[~2012-10-03 17:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-26 21:04 qv4l2-bug / libv4lconvert API issue Frank Schäfer
2012-09-27 10:26 ` Hans de Goede
2012-09-27 13:20   ` Frank Schäfer
2012-09-27 19:41     ` Hans de Goede
2012-09-28 17:09       ` Frank Schäfer
2012-09-30  9:54         ` Hans de Goede
2012-10-03 10:22           ` Frank Schäfer
2012-10-03 12:32             ` Hans Verkuil
2012-10-03 16:41               ` Frank Schäfer [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=506C6AB0.2010608@googlemail.com \
    --to=fschaefer.oss@googlemail.com \
    --cc=hdegoede@redhat.com \
    --cc=hverkuil@xs4all.nl \
    --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;
as well as URLs for NNTP newsgroup(s).