• 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
  • App 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
  • Knowledge Base
  • PCNs
  • 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
  • App 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
  • Knowledge Base
  • PCNs
  • Contact Support
  • Log In
home/Knowledge Base/Arena Software/Opening Raw Images in ArenaView MP

Opening Raw Images in ArenaView MP

2 views 0 February 20, 2026

Introduction

ArenaView MP (AVMP) lets you save images in common image formats such as PNG, JPG, and TIFF. You can also save images in raw image format; because raw images contain the pixel values for the image, AVMP will create an accompanying JSON file that contains details for the raw file. When you open a raw file in AVMP, it needs both the raw image file and the accompanying JSON file.

Setting the working directory

Before you can save an image, you will be prompted to set the working directory in ArenaView MP. Do the following:

  1. From the menu bar, select Controls > AVMP.
  2. In the pane that opens, click on the green folder symbol.
  3. Choose a directory for the folder of saved images.

Images will then be saved in the folder in the working directory you have chosen.

Saving images

To save an image in a specific format, follow these steps:

  1. Start streaming or press the snap button to get an image.
  2. Do either of the following:
    • From the menu bar, select File > Save As.
    • In the window with the image/stream, right-click on the image and select Save As.
  3. This opens the following file dialog. In the dropdown, pick the format to save the image as.

When saving a QOI capture as a raw image, it will save as its non-compressed equivalent. For example, if you save a QOI_Mono8 raw image, it will save a Mono8 raw image instead.

Additional options

There are several more settings and controls available under Controls > Save & Load > Save Image. For most of these settings, you need to stream from a camera or have a window open with an image from the camera.

File name pattern

You can adjust the file pattern used for savings images:

For more syntax help, click on the question mark character shown in the UI above.

File format settings

Additionally, for different image formats you can adjust settings related to compression, quality, and subsampling.

  • File Format: Available file formats are TIFF, PNG, JPEG, RAW, and BMP.
  • Format-specific settings  that appear include JPEG subsampling and compression settings for TIFF and PNG.
  • Save Raw Data Only: This forces raw image into JPEG, PNG, BMP, and TIFF files, and can result in corruption.

The file format settings that are configured here are applied to all quick actions (i.e., when using ‘Save’ instead of ‘Save As’ or clicking the pink floppy symbol). There are several quick ways to save images by doing one of the following:

  • Clicking the pink floppy symbol .
  • From the menu bar, selecting File > Save.
  • In the window with the image/stream right-click on the image and click Save.

Opening images

To open an image, do the following:

  1. From the top ribbon, select File > Open Raw.
  2. Choose the desired image format.
  3. Navigate to the file and double-click it.

If you are opening a raw image, it will open in ArenaView MP in a new window. Other images will be opened in your OS’s native image viewer.

Example

When you unzip open the example files below in AVMP, the raw data appears. You can control the pitch/yaw, the panning, and the distance from the focal point just like you would if you were streaming directly from the camera.

Example files for HTW003S-001

Example file opened in ArenaView MP. To obtain the view above, ensure that the settings Controls > Image Processing > Time-of-Flight Processing > Channel Selection is set to Intensity.

Raw images

The raw image file contains the image data as it was obtained from the camera. Not all of this information is preserved when the image is saved in a standard image format.

To open a raw image, you need the accompanying JSON file for it. AVMP creates the JSON file when you save the raw image. It has the same name as the raw image but with the .json extension appended to it. For example, if a raw image has the filename “TRI050S_image.raw” then the JSON file has the name “TRI050S_image.raw.json”. If ArenaView MP cannot find the JSON file, then an error will result.

Raw images that contain the following pixel formats cannot be opened:

  • All line scan CFA pixel formats
  • XYTPFrame
  • RawFrameEncoded

Attempting to open raw images with these pixel formats will fail and result in an error.

If you attempt to open a raw video in ArenaView MP, it will only show the first frame of the video. This is because raw videos are just raw images appended together. Playback of raw videos is not supported in ArenaView MP.

Recreating the JSON file

A raw image only contains the raw pixel data of the image, so the JSON file is needed to correctly view it. If you do not have the JSON file, then you can reconstruct it if you know the height, width, and pixel format used for the image.

For example, here is the JSON file for a raw image taken from a TRI050S:

{
    "height": 2048,
    "pixelformat": "Mono8",
    "width": 2448
}

This is the format used for all raw images. As mentioned in the previous section, the JSON file should have the exact same name as the raw image file, plus the .json file extension appended to it.

If you only know two of the specific values, then it may still be possible to reconstruct the JSON. For example, if you only know the values of the height and pixel format, you can perform some calculations to figure out the width:

File Size (bytes) = Width × Height × Pixel Format Size (bytes)

Understanding the pixel format makes things easier as many pixel formats take up the same size in bytes. The following articles describe the layout and size of different pixel formats:

  • Pixel Formats – Area Scan
  • Pixel Formats – Line Scan
  • Pixel Formats – 3D

Was this helpful?

Yes  No
Related Articles
  • Solving driver-related RDMA streaming issues with Ubuntu 22.04
  • Using Multiple Helios Cameras Simultaneously
  • Troubleshooting Network Timeouts (Linux)
  • How to create an Ubuntu docker image and container with Arena SDK
  • Troubleshooting timeouts caused by incomplete images (Windows)
  • Tonemapping images from LUCID’s TRI054S-CC IMX490

Didn't find your answer? Contact Us

  Solving driver-related RDMA streaming issues with Ubuntu 22.04

© 2026 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}