public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <j.w.r.degoede@hhs.nl>
To: kilgota@banach.math.auburn.edu
Cc: video4linux-list@redhat.com
Subject: Re: Apparent inconsistency in the labels of Bayer tilings
Date: Mon, 24 Nov 2008 09:15:24 +0100	[thread overview]
Message-ID: <492A629C.1010808@hhs.nl> (raw)
In-Reply-To: <Pine.LNX.4.64.0811231522510.6135@banach.math.auburn.edu>

kilgota@banach.math.auburn.edu wrote:
> 
> Thanks for the recommendation about gettimeofday. I will try putting 
> that in. Right now, I wonder if you know something about the following:
> 
> In order to make your Bayer demosaicing algorithm work, I had to do the 
> following because otherwise the colors were mapped backwards:
> 
> 1. create new entries in your libv4lconvert-priv.h like this
> 
> #ifndef V4L2_PIX_FMT_SBGGR8
> #define V4L2_PIX_FMT_SBGGR8 v4l2_fourcc('B','G','G','R')
> #endif
> 

Erm, that one is defined in linux/videodev2.h and has been for a long time:
#define V4L2_PIX_FMT_SBGGR8  v4l2_fourcc('B', 'A', '8', '1') /*  8  BGBG.. 
GRGR.. */

But I see I did not include it in libv4lconvert-priv.h, my bad.

Anyways to which fourcc you define V4L2_PIX_FMT_SBGGR8 should not matter, as 
for the meaning of the defines, as the command above shows in v4l BGGR means 
first line: BGBG.. second line: GRGR.., and then third line BGBG.. again, etc.

That seems pretty straightforward to me, how are libgphoto's defines supposed 
to be interpreted?

> #ifndef BAYER_TILE_BGGR
> #define BAYER_TILE_BGGR V4L2_PIX_FMT_SBGGR8
> #endif
> 
> and then use these. But in libgphoto2 the same photo from the same 
> camera has to use
> 
> BAYER_TILE_RGGB
> 
> So in other words when changing over the Bayer algorithm I also had to 
> change the label for the tiling from RGGB over to BGGR.
> 
> What gives? Do you happen to know? The two labels clearly disagree to 
> such an extent that they cannot both be right. Of course, the whole 
> thing is a matter of convention, presumably settled a long time ago by 
> someone who was neither of us. Also, the labeling of the Bayer tiles in 
> Gphoto was done long before I came along and thus I am not responsible 
> for it. So I explicitly do not give and do not have an opinion about who 
> is right.

The v4l convention also stems from before I came a long, I merely added the 
other 3 possible bayer patterns to the list.

Regards,

Hans


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

  parent reply	other threads:[~2008-11-24  8:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.208512.1227000563.24145.sqcam-devel@lists.sourceforge.net>
     [not found] ` <Pine.LNX.4.64.0811181216270.2778@banach.math.auburn.edu>
2008-11-19  0:20   ` [sqcam-devel] Advice wanted on producing an in kernel sq905 driver Adam Baker
2008-11-19  7:46     ` Antonio Ospite
2008-11-19  8:42     ` Hans de Goede
     [not found]       ` <alpine.LNX.1.10.0811192005020.2980@banach.math.auburn.edu>
2008-11-20  9:38         ` Hans de Goede
     [not found]           ` <Pine.LNX.4.64.0811201130410.3570@banach.math.auburn.edu>
2008-11-20 19:37             ` Hans de Goede
     [not found]               ` <Pine.LNX.4.64.0811201657020.3763@banach.math.auburn.edu>
2008-11-21  8:37                 ` Hans de Goede
     [not found]               ` <Pine.LNX.4.64.0811202306360.3930@banach.math.auburn.edu>
2008-11-21 10:54                 ` Hans de Goede
     [not found]                   ` <Pine.LNX.4.64.0811211244120.4475@banach.math.auburn.edu>
2008-11-21 21:25                     ` Hans de Goede
     [not found]                       ` <Pine.LNX.4.64.0811211929220.4832@banach.math.auburn.edu>
2008-11-23  9:36                         ` Report on time needed for completing v4l Bayer interpolation Hans de Goede
     [not found]                           ` <Pine.LNX.4.64.0811231522510.6135@banach.math.auburn.edu>
2008-11-24  8:15                             ` Hans de Goede [this message]
2008-11-21 21:57                     ` [sqcam-devel] Advice wanted on producing an in kernel sq905 driver Adam Baker
2008-11-21 23:39                       ` Adam Baker
     [not found]                       ` <Pine.LNX.4.64.0811211658290.4727@banach.math.auburn.edu>
2008-11-22  0:05                         ` Adam Baker
     [not found]                           ` <Pine.LNX.4.64.0811211955490.4832@banach.math.auburn.edu>
2008-11-22 21:55                             ` The userspace-kernelspace thing. Continuation of sq905 driver discussion Adam Baker
2008-11-24 11:26                         ` [sqcam-devel] Advice wanted on producing an in kernel sq905 driver Hans de Goede
     [not found]     ` <alpine.LNX.1.10.0811191937370.2980@banach.math.auburn.edu>
2008-11-20  7:48       ` Hans de Goede
     [not found] ` <492A8E76.3070701@redhat.com>
     [not found]   ` <Pine.LNX.4.64.0811241446210.6862@banach.math.auburn.edu>
2008-11-25  0:02     ` Adam Baker
     [not found]       ` <Pine.LNX.4.64.0811241929420.7049@banach.math.auburn.edu>
2008-11-25 20:57         ` Adam Baker
2008-11-25  8:03     ` Hans de Goede

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=492A629C.1010808@hhs.nl \
    --to=j.w.r.degoede@hhs.nl \
    --cc=kilgota@banach.math.auburn.edu \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox