From: Nicolas Dufresne <nicolas@ndufresne.ca>
To: Anatolij Gustschin <agust@denx.de>,
Florian Boor <florian.boor@kernelconcepts.de>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: MT9M131 on I.MX6DL CSI color issue
Date: Fri, 12 Jan 2018 09:59:34 -0500 [thread overview]
Message-ID: <1515769174.3084.27.camel@ndufresne.ca> (raw)
In-Reply-To: <20180112105840.75260abb@crub>
Le vendredi 12 janvier 2018 à 10:58 +0100, Anatolij Gustschin a écrit :
> On Fri, 12 Jan 2018 01:16:03 +0100
> Florian Boor florian.boor@kernelconcepts.de wrote:
> ...
> > Basically it works pretty well apart from the really strange
> > colors. I guess its
> > some YUV vs. RGB issue or similar. Here [1] is an example generated
> > with the
> > following command.
> >
> > gst-launch v4l2src device=/dev/video4 num-buffers=1 ! jpegenc !
> > filesink
> > location=capture1.jpeg
> >
> > Apart from the colors everything is fine.
> > I'm pretty sure I have not seen such an effect before - what might
> > be wrong here?
>
> You need conversion to RGB before JPEG encoding. Try with
>
> gst-launch v4l2src device=/dev/video4 num-buffers=1 ! \
> videoparse format=5 width=1280 height=1024 framerate=25/1
> ! \
> jpegenc ! filesink location=capture1.jpeg
>
> For "format" codes see gst-inspect-1.0 videoparse.
A properly written driver should never permit this.
Nicolas
next prev parent reply other threads:[~2018-01-12 14:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 0:16 MT9M131 on I.MX6DL CSI color issue Florian Boor
2018-01-12 9:58 ` Anatolij Gustschin
2018-01-12 10:06 ` Anatolij Gustschin
2018-01-15 10:40 ` Florian Boor
2018-01-17 10:31 ` Daniel Glöckner
2018-01-17 12:58 ` Florian Boor
2018-01-18 4:03 ` Daniel Glöckner
2018-01-18 16:31 ` Florian Boor
2018-01-20 15:02 ` Daniel Glöckner
2018-01-22 14:52 ` Florian Boor
2018-01-30 17:13 ` Florian Boor
2018-01-12 14:59 ` Nicolas Dufresne [this message]
2018-01-15 12:49 ` Philipp Zabel
2018-01-15 14:41 ` Florian Boor
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=1515769174.3084.27.camel@ndufresne.ca \
--to=nicolas@ndufresne.ca \
--cc=agust@denx.de \
--cc=florian.boor@kernelconcepts.de \
--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