• Support Home
  • Getting Started
    • Connecting Your Camera
    • 3rd Party Software Getting Started Guides
  • Tech Ref Manuals
    • Arena SDK Documentation
    • HTP003S – Helios2+ ToF 3D
    • HLT003S – Helios2 ToF 3D
    • HLS003S – Helios ToF 3D
    • HLF003S – Helios Flex ToF 3D
    • ATX245S – Atlas10 24.5 MP
    • ATX204S – Atlas10 20.4 MP
    • ATX162S – Atlas10 16.2 MP
    • ATX124S – Atlas10 12.3 MP
    • ATX081S – Atlas10 8.1 MP
    • ATX051S – Atlas10 5.0 MP
    • ATL314S – Atlas 31.4 MP
    • ATL196S – Atlas 19.6 MP
    • ATL168S – Atlas 16.8 MP
    • ATL120S – Atlas 12.3 MP
    • ATL089S – Atlas 8.9 MP
    • ATL071S – Atlas 7.1 MP
    • ATL050S – Atlas 5.0 MP
    • ATL028S – Atlas 2.8 MP
    • ATP200S – Atlas IP67 20 MP
    • ATP120S – Atlas IP67 12.3 MP
    • ATP089S -Atlas IP67 8.9 MP
    • ATP071S – Atlas IP67 7.1 MP
    • ATP028S – Atlas IP67 2.8 MP
    • TRI200S – Triton 20.0 MP
    • TRI120S – Triton 12.3 MP
    • TRI122S – Triton 12.2 MP
    • TRI089S – Triton 8.9 MP
    • TRI071S – Triton 7.1 MP
    • TRI064S – Triton 6.3 MP
    • TRI054S – Triton 5.4 MP
    • TRI050S-P/Q – Triton 5.0 MP Polarized
    • TRI050S – Triton 5.0 MP
    • TRI032S – Triton 3.2 MP
    • TRI028S – Triton 2.8 MP
    • TRI023S – Triton 2.3 MP
    • TRI016S – Triton 1.6 MP
    • TRI005S – Triton 0.5 MP
    • TRI004S – Triton 0.4 MP
    • TRI02KA – Triton 2K Line Scan
    • PHX200S – Phoenix 20.0 MP
    • PHX120S – Phoenix 12.3 MP
    • PHX122S – Phoenix 12.2 MP
    • PHX089S – Phoenix 8.9 MP
    • PHX064S – Phoenix 6.3 MP
    • PHX050S-P/Q – Phoenix 5.0 MP Polarized
    • PHX050S – Phoenix 5.0 MP
    • PHX032S – Phoenix 3.2 MP
    • PHX023S – Phoenix 2.3 MP
    • PHX016S – Phoenix 1.6 MP
    • PHX004S – Phoenix 0.4 MP
  • Application Notes
    • Bandwidth Sharing in Multi-Camera Systems
    • Combine Helios 3D Point Cloud with RGB Color
    • I2C Support on LUCID Cameras
    • Using Helios2 with the Point Cloud Library for Dimensioning
    • Using GPIO on LUCID Cameras
    • Using PTP & Scheduled Action Commands
    • Helios2 And Triton Synchronization
    • Product Change Notifications (PCN)
  • Knowledge Base
  • Contact Support
  • Log In
  • Support Home
  • Getting Started
    • Connecting Your Camera
    • 3rd Party Software Getting Started Guides
  • Tech Ref Manuals
    • Arena SDK Documentation
    • HTP003S – Helios2+ ToF 3D
    • HLT003S – Helios2 ToF 3D
    • HLS003S – Helios ToF 3D
    • HLF003S – Helios Flex ToF 3D
    • ATX245S – Atlas10 24.5 MP
    • ATX204S – Atlas10 20.4 MP
    • ATX162S – Atlas10 16.2 MP
    • ATX124S – Atlas10 12.3 MP
    • ATX081S – Atlas10 8.1 MP
    • ATX051S – Atlas10 5.0 MP
    • ATL314S – Atlas 31.4 MP
    • ATL196S – Atlas 19.6 MP
    • ATL168S – Atlas 16.8 MP
    • ATL120S – Atlas 12.3 MP
    • ATL089S – Atlas 8.9 MP
    • ATL071S – Atlas 7.1 MP
    • ATL050S – Atlas 5.0 MP
    • ATL028S – Atlas 2.8 MP
    • ATP200S – Atlas IP67 20 MP
    • ATP120S – Atlas IP67 12.3 MP
    • ATP089S -Atlas IP67 8.9 MP
    • ATP071S – Atlas IP67 7.1 MP
    • ATP028S – Atlas IP67 2.8 MP
    • TRI200S – Triton 20.0 MP
    • TRI120S – Triton 12.3 MP
    • TRI122S – Triton 12.2 MP
    • TRI089S – Triton 8.9 MP
    • TRI071S – Triton 7.1 MP
    • TRI064S – Triton 6.3 MP
    • TRI054S – Triton 5.4 MP
    • TRI050S-P/Q – Triton 5.0 MP Polarized
    • TRI050S – Triton 5.0 MP
    • TRI032S – Triton 3.2 MP
    • TRI028S – Triton 2.8 MP
    • TRI023S – Triton 2.3 MP
    • TRI016S – Triton 1.6 MP
    • TRI005S – Triton 0.5 MP
    • TRI004S – Triton 0.4 MP
    • TRI02KA – Triton 2K Line Scan
    • PHX200S – Phoenix 20.0 MP
    • PHX120S – Phoenix 12.3 MP
    • PHX122S – Phoenix 12.2 MP
    • PHX089S – Phoenix 8.9 MP
    • PHX064S – Phoenix 6.3 MP
    • PHX050S-P/Q – Phoenix 5.0 MP Polarized
    • PHX050S – Phoenix 5.0 MP
    • PHX032S – Phoenix 3.2 MP
    • PHX023S – Phoenix 2.3 MP
    • PHX016S – Phoenix 1.6 MP
    • PHX004S – Phoenix 0.4 MP
  • Application Notes
    • Bandwidth Sharing in Multi-Camera Systems
    • Combine Helios 3D Point Cloud with RGB Color
    • I2C Support on LUCID Cameras
    • Using Helios2 with the Point Cloud Library for Dimensioning
    • Using GPIO on LUCID Cameras
    • Using PTP & Scheduled Action Commands
    • Helios2 And Triton Synchronization
    • Product Change Notifications (PCN)
  • Knowledge Base
  • Contact Support
  • Log In
home/Knowledge Base/Camera Features/Pixel Formats – Line Scan

Pixel Formats – Line Scan

114 views 0 September 29, 2025 Updated on December 3, 2025

Looking for Area Scan or 3D Pixel Formats? Visit our Area Scan Pixel Format and our 3D Pixel Format pages for more information.

Introduction

Understanding pixel formats allow you to understand how images are put together. More specifically,  understanding these pixel formats will help you if you need to extract specific information from the pixels in the image that you receive from the camera. 

Jump to:

Linescan ROI
Linescan ROI

Color linescan: CFA_RBGG* pixel formats
CFA_RBGG8
CFA_RBGG10
CFA_RBGG10p
CFA_RBGG10Packed
CFA_RBGG12
CFA_RBGG12p
CFA_RBGG12Packed
CFA_RBGG16

Color linescan: CFA1by2_RB* pixel formats
CFA1by2_RB8
CFA1by2_RB10
CFA1by2_RB10p
CFA1by2_RB10Packed
CFA1by2_RB12
CFA1by2_RB12p
CFA1by2_RB12Packed
CFA1by2_RB16

Color linescan: CFA4by1_WBGR* pixel formats

CFA4by1_WBGR8
CFA4by1_WBGR10
CFA4by1_WBGR10p
CFA4by1_WBGR10Packed
CFA4by1_WBGR12
CFA4by1_WBGR12p
CFA4by1_WBGR12Packed
CFA4by1_WBGR16

Linescan ROI

Linescan ROI

The Region of Interest feature allows you to specify a section of the line sensor used for image acquisition.  ROI allows a custom width and height for image size and a custom X offset for image position.

The location and the size of the Region of Interest is defined by setting an offset X and a width in pixels. For example, setting Offset X as 10 and width as 2030 would result in a Region of Interest as shown below.

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 ...
... 2032 2033 2034 2035 2036 2037 2038 2039 2040 2041 2042 2043 2044 2045 2046 2047

Color linescan pixel formats

CFA_RBGG* pixel formats

On the TRT04KG, these raw pixel formats are associated with the two rows of 3.5 μm pixels.

CFA_RBGG8

Byte 0
7 6 5 4 3 2 1 0
7 0
Byte 1
7 6 5 4 3 2 1 0
7 0
Byte 2
7 6 5 4 3 2 1 0
7 0
Byte 3
7 6 5 4 3 2 1 0
7 0
Byte n
7 6 5 4 3 2 1 0
7 0
Byte n+1
7 6 5 4 3 2 1 0
7 0
Byte n+2
7 6 5 4 3 2 1 0
7 0
Byte n+3
7 6 5 4 3 2 1 0
7 0

CFA_RBGG10

Byte 0
7 6 5 4 3 2 1 0
7 0
Byte 1
pad pad pad pad pad pad 9 8
7 0
Byte 2
7 6 5 4 3 2 1 0
7 0
Byte 3
pad pad pad pad pad pad 9 8
7 0
Byte n
7 6 5 4 3 2 1 0
7 0
Byte n+1
pad pad pad pad pad pad 9 8
7 0
Byte n+2
7 6 5 4 3 2 1 0
7 0
Byte n+3
pad pad pad pad pad pad 9 8
7 0

CFA_RBGG10p

Byte 0
7 6 5 4 3 2 1 0
7 0
Byte 1
5 4 3 2 1 0 9 8
7 0
Byte 2
3 2 1 0 9 8 7 6
7 0
Byte 3
1 0 9 8 7 6 5 4
7 0
Byte n+4
9 8 7 6 5 4 3 2
7 0
Byte n
7 6 5 4 3 2 1 0
7 0
Byte n+1
5 4 3 2 1 0 9 8
7 0
Byte n+2
3 2 1 0 9 8 7 6
7 0
Byte n+3
1 0 9 8 7 6 5 4
7 0
Byte n+4
9 8 7 6 5 4 3 2
7 0

CFA_RBGG10Packed

Byte 0
9 8 7 6 5 4 3 2
7 0
Byte 1
pad pad 1 0 pad pad 1 0
7 0
Byte 2
9 8 7 6 5 4 3 2
7 0
Byte m
9 8 7 6 5 4 3 2
7 0
Byte n+1
pad pad 1 0 pad pad 1 0
7 0
Byte n+2
9 8 7 6 5 4 3 2
7 0

CFA_RBGG12

Byte 0
7 6 5 4 3 2 1 0
7 0
Byte 1
pad pad pad pad 11 10 9 8
7 0
Byte 2
7 6 5 4 3 2 1 0
7 0
Byte 3
pad pad pad pad 11 10 9 8
7 0
Byte n
7 6 5 4 3 2 1 0
7 0
Byte n+1
pad pad pad pad 11 10 9 8
7 0
Byte n+2
7 6 5 4 3 2 1 0
7 0
Byte n+3
pad pad pad pad 11 10 9 8
7 0

CFA_RBGG12p

Byte 0
7 6 5 4 3 2 1 0
7 0
Byte 1
3 2 1 0 11 10 9 8
7 0
Byte 2
11 10 9 8 7 6 5 4
7 0
Byte n
7 6 5 4 3 2 1 0
7 0
Byte n+1
3 2 1 0 11 10 9 8
7 0
Byte n+2
11 10 9 8 7 6 5 4
7 0

CFA_RBGG12Packed

Byte 0
11 10 9 8 7 6 5 4
7 0
Byte 1
3 2 1 0 3 2 1 0
7 0
Byte 2
11 10 9 8 7 6 5 4
7 0
Byte n
11 10 9 8 7 6 5 4
7 0
Byte n+1
3 2 1 0 3 2 1 0
7 0
Byte n+2
11 10 9 8 7 6 5 4
7 0

CFA_RBGG16

Byte 0
7 6 5 4 3 2 1 0
7 0
Byte 1
15 14 13 12 11 10 9 8
7 0
Byte 2
7 6 5 4 3 2 1 0
7 0
Byte 3
15 14 13 12 11 10 9 8
7 0
Byte n
7 6 5 4 3 2 1 0
7 0
Byte n+1
15 14 13 12 11 10 9 8
7 0
Byte n+2
7 6 5 4 3 2 1 0
7 0
Byte n+3
15 14 13 12 11 10 9 8
7 0

Related pixel formats

The pixel sequence for the CFA_RBGG pixel format assumes that the ReverseX and ReverseY nodes, which flip the image in different directions, are False. The pixel format details for different values of ReverseX and ReverseY are shown below.

ReverseXReverseYRow 1Row 2Pixel Format
FalseFalseRBGGCFA_RBGG
TrueFalseBRGGCFA_BRGG
FalseTrueGGRBCFA_ GGRB
TrueTrueGGBRCFA_GGBR

CFA1by2_RB* pixel formats

On the TRT04KG, these raw pixel formats are associated with a row of 3.5 μm pixels.

CFA1by2_RB8

Byte 0
7 6 5 4 3 2 1 0
7 0
Byte 1
7 6 5 4 3 2 1 0
7 0
Byte 2
7 6 5 4 3 2 1 0
7 0
Byte 3
7 6 5 4 3 2 1 0
7 0

CFA1by2_RB10

Byte 0
7 6 5 4 3 2 1 0
7 0
Byte 1
pad pad pad pad pad pad 9 8
7 0
Byte 2
7 6 5 4 3 2 1 0
7 0
Byte 3
pad pad pad pad pad pad 9 8
7 0

CFA1by2_RB10p

Byte 0
7 6 5 4 3 2 1 0
7 0
Byte 1
5 4 3 2 1 0 9 8
7 0
Byte 2
3 2 1 0 9 8 7 6
7 0
Byte 3
1 0 9 8 7 6 5 4
7 0
Byte n+4
9 8 7 6 5 4 3 2
7 0

CFA1by2_RB10Packed

Byte 0
9 8 7 6 5 4 3 2
7 0
Byte 1
pad pad 1 0 pad pad 1 0
7 0
Byte 2
9 8 7 6 5 4 3 2
7 0

CFA1by2_RB12

Byte 0
7 6 5 4 3 2 1 0
7 0
Byte 1
pad pad pad pad 11 10 9 8
7 0
Byte 2
7 6 5 4 3 2 1 0
7 0
Byte 3
pad pad pad pad 11 10 9 8
7 0

CFA1by2_RB12p

Byte 0
7 6 5 4 3 2 1 0
7 0
Byte 1
3 2 1 0 11 10 9 8
7 0
Byte 2
11 10 9 8 7 6 5 4
7 0

CFA1by2_RB12Packed

Byte 0
11 10 9 8 7 6 5 4
7 0
Byte 1
3 2 1 0 3 2 1 0
7 0
Byte 2
11 10 9 8 7 6 5 4
7 0

CFA1by2_RB16

Byte 0
7 6 5 4 3 2 1 0
7 0
Byte 1
15 14 13 12 11 10 9 8
7 0
Byte 2
7 6 5 4 3 2 1 0
7 0
Byte 3
15 14 13 12 11 10 9 8
7 0

Related pixel formats

The pixel sequence for the CFA1by2_RB pixel format assumes that the ReverseX node, which flips the image horizontally, is False. The pixel format details for different values of ReverseX are shown below:

ReverseXRow 1Pixel Format
FalseRBCFA1by2_RB
TrueBRCFA1by2_BR

CFA4by1_WBGR* pixel formats

On the TRT04KG, these raw pixel formats are associated with the four rows of 7 μm pixels.

CFA4by1_WBGR8

Byte 0
7 6 5 4 3 2 1 0
7 0
Byte 1
7 6 5 4 3 2 1 0
7 0
Byte 2
7 6 5 4 3 2 1 0
7 0
Byte 3
7 6 5 4 3 2 1 0
7 0
Byte n
7 6 5 4 3 2 1 0
7 0
Byte n+1
7 6 5 4 3 2 1 0
7 0
Byte n+2
7 6 5 4 3 2 1 0
7 0
Byte n+3
7 6 5 4 3 2 1 0
7 0
Byte 2n
7 6 5 4 3 2 1 0
7 0
Byte 2n+1
7 6 5 4 3 2 1 0
7 0
Byte 2n+2
7 6 5 4 3 2 1 0
7 0
Byte 2n+3
7 6 5 4 3 2 1 0
7 0
Byte 3n
7 6 5 4 3 2 1 0
7 0
Byte 3n+1
7 6 5 4 3 2 1 0
7 0
Byte 3n+2
7 6 5 4 3 2 1 0
7 0
Byte 3n+3
7 6 5 4 3 2 1 0
7 0

CFA4by1_WBGR10

Byte 0
7 6 5 4 3 2 1 0
7 0
Byte 1
pad pad pad pad pad pad 9 8
7 0
Byte 2
7 6 5 4 3 2 1 0
7 0
Byte 3
pad pad pad pad pad pad 9 8
7 0
Byte 2n
7 6 5 4 3 2 1 0
7 0
Byte 2n+1
pad pad pad pad pad pad 9 8
7 0
Byte 2n+2
7 6 5 4 3 2 1 0
7 0
Byte 2n+3
pad pad pad pad pad pad 9 8
7 0
Byte 4n
7 6 5 4 3 2 1 0
7 0
Byte 4n+1
pad pad pad pad pad pad 9 8
7 0
Byte 4n+2
7 6 5 4 3 2 1 0
7 0
Byte 4n+3
pad pad pad pad pad pad 9 8
7 0
Byte 6n
7 6 5 4 3 2 1 0
7 0
Byte 6n+1
pad pad pad pad pad pad 9 8
7 0
Byte 6n+2
7 6 5 4 3 2 1 0
7 0
Byte 6n+3
pad pad pad pad pad pad 9 8
7 0

CFA4by1_WBGR10p

Byte 0
7 6 5 4 3 2 1 0
7 0
Byte 1
5 4 3 2 1 0 9 8
7 0
Byte 2
3 2 1 0 9 8 7 6
7 0
Byte 3
1 0 9 8 7 6 5 4
7 0
Byte 4
9 8 7 6 5 4 3 2
7 0
Byte 1.25n
7 6 5 4 3 2 1 0
7 0
Byte 1.25n+1
5 4 3 2 1 0 9 8
7 0
Byte 1.25n+2
3 2 1 0 9 8 7 6
7 0
Byte 1.25n+3
1 0 9 8 7 6 5 4
7 0
Byte 1.25n+4
9 8 7 6 5 4 3 2
7 0
Byte 2.5n
7 6 5 4 3 2 1 0
7 0
Byte 2.5n+1
5 4 3 2 1 0 9 8
7 0
Byte 2.5n+2
3 2 1 0 9 8 7 6
7 0
Byte 2.5n+3
1 0 9 8 7 6 5 4
7 0
Byte 2.5n+4
9 8 7 6 5 4 3 2
7 0
Byte 3.75n
7 6 5 4 3 2 1 0
7 0
Byte 3.75n+1
5 4 3 2 1 0 9 8
7 0
Byte 3.75n+2
3 2 1 0 9 8 7 6
7 0
Byte 3.75n+3
1 0 9 8 7 6 5 4
7 0
Byte 3.75n+4
9 8 7 6 5 4 3 2
7 0

CFA4by1_WBGR10Packed

Byte 0
9 8 7 6 5 4 3 2
7 0
Byte 1
pad pad 1 0 pad pad 1 0
7 0
Byte 2
9 8 7 6 5 4 3 2
7 0
Byte 1.5n
9 8 7 6 5 4 3 2
7 0
Byte 1.5n+1
pad pad 1 0 pad pad 1 0
7 0
Byte 1.5n+2
9 8 7 6 5 4 3 2
7 0
Byte 3n
9 8 7 6 5 4 3 2
7 0
Byte 3n+1
pad pad 1 0 pad pad 1 0
7 0
Byte 3n+2
9 8 7 6 5 4 3 2
7 0
Byte 4.5n
9 8 7 6 5 4 3 2
7 0
Byte 4.5n+1
pad pad 1 0 pad pad 1 0
7 0
Byte 4.5n+2
9 8 7 6 5 4 3 2
7 0

CFA4by1_WBGR12

Byte 0
7 6 5 4 3 2 1 0
7 0
Byte 1
pad pad pad pad 11 10 9 8
7 0
Byte 2
7 6 5 4 3 2 1 0
7 0
Byte 3
pad pad pad pad 11 10 9 8
7 0
Byte 2n
7 6 5 4 3 2 1 0
7 0
2n+1
pad pad pad pad 11 10 9 8
7 0
Byte 2n+2
7 6 5 4 3 2 1 0
7 0
Byte 2n+3
pad pad pad pad 11 10 9 8
7 0
Byte 4n
7 6 5 4 3 2 1 0
7 0
4n+1
pad pad pad pad 11 10 9 8
7 0
Byte 4n+2
7 6 5 4 3 2 1 0
7 0
Byte 4n+3
pad pad pad pad 11 10 9 8
7 0
Byte 6n
7 6 5 4 3 2 1 0
7 0
6n+1
pad pad pad pad 11 10 9 8
7 0
Byte 6n+2
7 6 5 4 3 2 1 0
7 0
Byte 6n+3
pad pad pad pad 11 10 9 8
7 0

CFA4by1_WBGR12p

Byte 0
7 6 5 4 3 2 1 0
7 0
Byte 1
3 2 1 0 11 10 9 8
7 0
Byte 2
11 10 9 8 7 6 5 4
7 0
Byte 1.5n
7 6 5 4 3 2 1 0
7 0
Byte 1.5n+1
3 2 1 0 11 10 9 8
7 0
Byte 1.5n+2
11 10 9 8 7 6 5 4
7 0
Byte 3n
7 6 5 4 3 2 1 0
7 0
Byte 3n+1
3 2 1 0 11 10 9 8
7 0
Byte 3n+2
11 10 9 8 7 6 5 4
7 0
Byte 4.5n
7 6 5 4 3 2 1 0
7 0
Byte 4.5n+1
3 2 1 0 11 10 9 8
7 0
Byte 4.5n+2
11 10 9 8 7 6 5 4
7 0

CFA4by1_WBGR12Packed

Byte 0
11 10 9 8 7 6 5 4
7 0
Byte 1
3 2 1 0 3 2 1 0
7 0
Byte 2
11 10 9 8 7 6 5 4
7 0
Byte 1.5n
11 10 9 8 7 6 5 4
7 0
Byte 1.5n+1
3 2 1 0 3 2 1 0
7 0
Byte 1.5n+2
11 10 9 8 7 6 5 4
7 0
Byte 3n
11 10 9 8 7 6 5 4
7 0
Byte 3n+1
3 2 1 0 3 2 1 0
7 0
Byte 3n+2
11 10 9 8 7 6 5 4
7 0
Byte 4.5n
11 10 9 8 7 6 5 4
7 0
Byte 4.5n+1
3 2 1 0 3 2 1 0
7 0
Byte 4.5n+2
11 10 9 8 7 6 5 4
7 0

CFA4by1_WBGR16

Byte 0
7 6 5 4 3 2 1 0
7 0
Byte 1
15 14 13 12 11 10 9 8
7 0
Byte 2
7 6 5 4 3 2 1 0
7 0
Byte 3
15 14 13 12 11 10 9 8
7 0
Byte 2n
7 6 5 4 3 2 1 0
7 0
Byte 2n+1
15 14 13 12 11 10 9 8
7 0
Byte 2n+2
7 6 5 4 3 2 1 0
7 0
Byte 2n+3
15 14 13 12 11 10 9 8
7 0
Byte 4n
7 6 5 4 3 2 1 0
7 0
Byte 4n+1
15 14 13 12 11 10 9 8
7 0
Byte 4n+2
7 6 5 4 3 2 1 0
7 0
Byte 4n+3
15 14 13 12 11 10 9 8
7 0
Byte 6n
7 6 5 4 3 2 1 0
7 0
Byte 6n+1
15 14 13 12 11 10 9 8
7 0
Byte 6n+2
7 6 5 4 3 2 1 0
7 0
Byte 6n+3
15 14 13 12 11 10 9 8
7 0

Related pixel formats

The pixel sequence for the CFA4by1_WBGR pixel format assumes that the ReverseY node, which flips the image vertically, is False. The pixel format details for different values of ReverseY are shown below:

ReverseYRow 1Row 2Row 3Row 4Pixel Format
FalseWBGRCFA4by1_WBGR
TrueRGBWCFA4by1_RGBW

CFA2by1_WB* pixel formats

On the TRT04KG, these raw pixel formats are associated with the two rows of 7 μm pixels.

CFA2by1_WB8

Byte 0
7 6 5 4 3 2 1 0
7 0
Byte 1
7 6 5 4 3 2 1 0
7 0
Byte 2
7 6 5 4 3 2 1 0
7 0
Byte 3
7 6 5 4 3 2 1 0
7 0
Byte n
7 6 5 4 3 2 1 0
7 0
Byte n+1
7 6 5 4 3 2 1 0
7 0
Byte n+2
7 6 5 4 3 2 1 0
7 0
Byte n+3
7 6 5 4 3 2 1 0
7 0

CFA2by1_WB10

Byte 0
7 6 5 4 3 2 1 0
7 0
Byte 1
pad pad pad pad pad pad 9 8
7 0
Byte 2
7 6 5 4 3 2 1 0
7 0
Byte 3
pad pad pad pad pad pad 9 8
7 0
Byte 2n
7 6 5 4 3 2 1 0
7 0
Byte 2n+1
pad pad pad pad pad pad 9 8
7 0
Byte 2n+2
7 6 5 4 3 2 1 0
7 0
Byte 2n+3
pad pad pad pad pad pad 9 8
7 0

CFA2by1_WB10p

Byte 0
7 6 5 4 3 2 1 0
7 0
Byte 1
5 4 3 2 1 0 9 8
7 0
Byte 2
3 2 1 0 9 8 7 6
7 0
Byte 3
1 0 9 8 7 6 5 4
7 0
Byte 4
9 8 7 6 5 4 3 2
7 0
Byte 1.25n
7 6 5 4 3 2 1 0
7 0
Byte 1.25n+1
5 4 3 2 1 0 9 8
7 0
Byte 1.25n+2
3 2 1 0 9 8 7 6
7 0
Byte 1.25n+3
1 0 9 8 7 6 5 4
7 0
Byte 1.25n+4
9 8 7 6 5 4 3 2
7 0

CFA4by1_WBGR10Packed

Byte 0
9 8 7 6 5 4 3 2
7 0
Byte 1
pad pad 1 0 pad pad 1 0
7 0
Byte 2
9 8 7 6 5 4 3 2
7 0
Byte 1.5n
9 8 7 6 5 4 3 2
7 0
Byte 1.5n+1
pad pad 1 0 pad pad 1 0
7 0
Byte 1.5n+2
9 8 7 6 5 4 3 2
7 0

CFA2by1_WB12

Byte 0
7 6 5 4 3 2 1 0
7 0
Byte 1
pad pad pad pad 11 10 9 8
7 0
Byte 2
7 6 5 4 3 2 1 0
7 0
Byte 3
pad pad pad pad 11 10 9 8
7 0
Byte 2n
7 6 5 4 3 2 1 0
7 0
2n+1
pad pad pad pad 11 10 9 8
7 0
Byte 2n+2
7 6 5 4 3 2 1 0
7 0
Byte 2n+3
pad pad pad pad 11 10 9 8
7 0

Related pixel formats

The pixel sequence for the CFA2by1_WB pixel format assumes that the ReverseY node, which flips the image vertically, is False. The pixel format details for different values of ReverseY are shown below:

ReverseYRow 1Row 2Pixel Format
FalseWBCFA2by1_WB
TrueBWCFA2by1_BW

Was this helpful?

Yes  No
Related Articles
  • Using GigE Vision RDMA Streaming Protocol in GigE Vision 3.0
  • Pixel Formats – 3D
  • Pixel Formats – Area Scan
  • Using QOI with LUCID Cameras
  • Using Multiple Helios Cameras Simultaneously
  • Shading Correction Control (Atlas10)

Didn't find your answer? Contact Us

  Pixel Formats – Area Scan

Pixel Formats – 3D  

© 2024 LUCID Vision Labs Inc.
Looking to purchase our cameras?
Visit the LUCID Webstore at thinklucid.com
Manage Consent

We use cookies to process e-commerce purchases securely and to understand how our site is used. Your privacy matters — click ‘Accept’ to continue.

Functional Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
  • Manage options
  • Manage services
  • Manage {vendor_count} vendors
  • Read more about these purposes
View preferences
  • {title}
  • {title}
  • {title}
Manage Consent
To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
Functional Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
  • Manage options
  • Manage services
  • Manage {vendor_count} vendors
  • Read more about these purposes
View preferences
  • {title}
  • {title}
  • {title}