All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arne Caspari <arne@unicap-imaging.org>
To: "Daniel Glöckner" <daniel-gl@gmx.net>
Cc: video4linux-list@redhat.com
Subject: Re: RAW/Bayer format FOURCCs
Date: Wed, 07 May 2008 14:50:44 +0200	[thread overview]
Message-ID: <1210164644.20718.2.camel@localhost> (raw)
In-Reply-To: <20080505150632.GA955@daniel.bse>

Daniel, 

Thank you very much for your informative post. I will look into the
information you provided. 


 /Arne


On Mon, 2008-05-05 at 17:06 +0200, Daniel Glöckner wrote:
> On Mon, May 05, 2008 at 09:35:47AM +0200, Arne Caspari wrote:
> > I am looking for the correct FOURCC to use for a RAW Bayer format: RGGB
> > 16 bit. 
> > 
> > In the v4l2 specification, there is V4L2_PIX_FMT_SBGGR8 ( 'BA81' ) for
> > BGGR 8 bit and V4L2_PIX_FMT_SBGGR16 ( 'BA82' ) for BGGR 16 bit. I do not
> > really see a pattern in the FOURCC assignment here. Does anybody know
> > what the correct FOURCC should look like? 
> 
> There is no pattern.
> 
> The BA8x FourCCs were invented by Luca Risolia:
> http://marc.info/?l=linux-video&m=108062090927323
> 
> The BYRx FourCCs are used by CineForm's products when they put raw
> pictures into AVI and MOV. David Newman's post on dvinfo.net is probably
> the source for the fourcc.org entries. Looking at CineForm's NEO player
> I see up to BYR3. Some update logs on the CineForm website mention BYR4.
> 
>   Daniel


--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

      reply	other threads:[~2008-05-07 13:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-05  7:35 RAW/Bayer format FOURCCs Arne Caspari
2008-05-05 15:06 ` Daniel Glöckner
2008-05-07 12:50   ` Arne Caspari [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=1210164644.20718.2.camel@localhost \
    --to=arne@unicap-imaging.org \
    --cc=daniel-gl@gmx.net \
    --cc=video4linux-list@redhat.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 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.