From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>,
linux-media@vger.kernel.org
Subject: Re: Kernel error "Unknown pixelformat 0x00000000" occurs when I start capture video
Date: Tue, 8 Jan 2019 13:16:21 -0200 [thread overview]
Message-ID: <20190108131621.59a825b7@coco.lan> (raw)
In-Reply-To: <386743082.UsI2JZZ8BA@avalon>
Em Tue, 08 Jan 2019 16:54:41 +0200
Laurent Pinchart <laurent.pinchart@ideasonboard.com> escreveu:
> Hello,
>
> On Tuesday, 8 January 2019 16:45:37 EET Mauro Carvalho Chehab wrote:
> > Em Sun, 6 Jan 2019 01:05:16 +0500 Mikhail Gavrilov escreveu:
> > > Hi folks!
> > > Every time when I start capture video from external capture card
> > > Avermedia Live Gamer ULTRA GC553
> > > (https://www.avermedia.com/gaming/product/game_capture/live_gamer_ultra_gc
> > > 553)
> >
> > What's the driver used by this device?
> >
> > A quick browsing at the Avermedia page you pointed, it indicates that this
> > should be using the UVC driver:
> >
> > "The LGU takes full advantage of UVC technology, which
> > basically standardizes video drivers across Windows and Mac.
> > In other words, all you need to do is plug your LGU to
> > your PC or Mac and it’s ready to record and stream."
> >
> > So, I *suspect* that it uses the uvcvideo driver, but better to
> > double check.
>
> Given the full kernel log part of the original message,
>
> [ 5.184850] uvcvideo: Unknown video format
> 30313050-0000-0010-8000-00aa00389b71
Hmm... according with:
https://gix.github.io/media-types/
It seems to be this one ('P010'):
{30313050-0000-0010-8000-00AA00389B71} (MFVideoFormat_P010)MFMS
{30313050-0000-0010-8000-00AA00389B71} (MEDIASUBTYPE_P010)DSMS
YUV planar 4:2:0 10 bits.
If so, there's a description here:
https://docs.microsoft.com/en-us/windows/desktop/medfound/10-bit-and-16-bit-yuv-video-formats
Thanks,
Mauro
next prev parent reply other threads:[~2019-01-08 15:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-05 20:05 Kernel error "Unknown pixelformat 0x00000000" occurs when I start capture video Mikhail Gavrilov
2019-01-08 14:45 ` Mauro Carvalho Chehab
2019-01-08 14:54 ` Laurent Pinchart
2019-01-08 15:16 ` Mauro Carvalho Chehab [this message]
2019-01-08 15:55 ` Laurent Pinchart
2019-01-08 15:18 ` Mikhail Gavrilov
2019-01-08 15:58 ` Laurent Pinchart
2019-01-08 16:11 ` Mikhail Gavrilov
2019-01-08 18:49 ` Mauro Carvalho Chehab
2019-01-08 19:00 ` Mauro Carvalho Chehab
2019-01-09 3:51 ` Mikhail Gavrilov
2019-01-09 12:03 ` Mauro Carvalho Chehab
2019-01-08 21:29 ` Laurent Pinchart
2019-01-09 12:19 ` Sakari Ailus
2019-01-09 13:01 ` P010 fourcc format support - Was: " Mauro Carvalho Chehab
2019-01-09 16:42 ` Ayaka
2019-01-09 16:52 ` Nicolas Dufresne
2019-01-09 17:28 ` Mauro Carvalho Chehab
2019-01-09 18:20 ` Nicolas Dufresne
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=20190108131621.59a825b7@coco.lan \
--to=mchehab+samsung@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=mikhail.v.gavrilov@gmail.com \
/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).