From: Hans Verkuil <hverkuil@xs4all.nl>
To: Stefan Witzel <s.witzel@gmx.de>, linux-media@vger.kernel.org
Subject: Re: Enforcing color profile
Date: Mon, 17 Aug 2020 15:34:00 +0200 [thread overview]
Message-ID: <0fa5da29-a058-2678-e616-65c921c6389a@xs4all.nl> (raw)
In-Reply-To: <7486393e-56b5-e460-b542-02c72525139b@gmx.de>
On 17/08/2020 14:09, Stefan Witzel wrote:
> Hello,
>
> I am not a V4L developer so if this is not the right place to bring up
> the issue please tell me who to contact instead.
> The page [1] documents a problem with a particular device "Elgato Cam
> Link 4K" which provides various format options among which most software
> does not consciously pick the one which it implicitly expects leading to
> problems. There is a software workaround, transcoding and looping
> through a virtual device and a hardware fix flashing the problematic
> profiles away.
> However it appears to me that the most satisfactory solution is hinted
> at in the sentence
>
>> I couldn't find any option in V4L to force selection of 'YUYV 4:2:2', so instead
>
> So my question is: what changes would be necessary to allow v4l2-ctl to
> enforce a particular format and who would be the right person to ask to
> make such changes?
It's there already:
v4l2-ctl -v pixelformat=YUYV
That will do the trick.
If you plug in the device and run 'v4l2-ctl -V', which pixelformat does it
report? I would expect it to be YUYV since that's first in the list.
If apps like Discord pick YU12 instead, then that's weird. That's something that
the application does, and v4l2-ctl won't help with that. I.e., it appears to be
an application bug.
One other alternative is that the device has broken 4:2:0 support, i.e. it reports
these formats, but they don't actually work. You can use qv4l2 or qvidcap to test
if these 4:2:0 formats are working.
Regards,
Hans
>
> Best regards,
> Stefan
>
>
> [1] https://assortedhackery.com/patching-cam-link-to-play-nicer-on-linux/
>
next prev parent reply other threads:[~2020-08-17 13:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-17 12:09 Enforcing color profile Stefan Witzel
2020-08-17 13:34 ` Hans Verkuil [this message]
2020-08-17 14:50 ` Stefan Witzel
2020-09-01 13:37 ` Stefan Witzel
2020-09-01 14:33 ` Mauro Carvalho Chehab
2020-09-21 14:43 ` Stefan Witzel
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=0fa5da29-a058-2678-e616-65c921c6389a@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=s.witzel@gmx.de \
/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.