Contact Us

You can always reach out to Zivid via customersuccess@zivid.com. If you prefer to perform some local troubleshooting we have a number of troubleshooting guides, as well as a set of FAQ.

If the issue is not listed in our Knowledge Base, or if you still encounter it, please contact us at customersuccess@zivid.com.

Tip

To speed up the support case and to maximize the chance of solving your issue it is recommended to provide a standalone reproducer and steps on how to use it.

To help us determine the cause and find a solution, please provide the following:

Log Files

Windows

Launch the Command Prompt (press Win + R keys on the keyboard, then type cmd and press Enter) and navigate to:

%LOCALAPPDATA%\Local\Zivid\API\Log

Send us a couple of log files created just after the issue occurred.

Ubuntu

Open a terminal window by pressing Ctrl + Alt + T keys on the keyboard and navigate to:

$XDG_CACHE_HOME/Zivid/API/Log

Caution

If $XDG_CACHE_HOME is not set use $HOME/.cache.

Send us a couple of log files created just after the issue occurred.

More info on log files

A log file is created when a Zivid application is made, e.g., when starting Zivid Studio.

The log file is named with Unix timestamp in milliseconds + process id, e.g., “Zivid-1651849596421-20912.log”. To retrieve the date and time when the log file is created, convert the Unix timestamp (1651849596421) with Unix Timestamp Conversion a human-readable date and time.

When the log file reaches 50 MB in size, then the log file rotates up to 2 times. This means a new blank log file is begun, and the old log is renamed to <log>.1, and then <log>.2, with up to a max of 2 old files for a single process. The log files are deleted after 30 days, or if the entire log directory is above 1000 MB. The oldest files are deleted until the size of the log files in the directory is below 1000 MB. The maximum log file and log directory size and the number of days before log files are deleted can be configured. Contact us at customersuccess@zivid.com for assistance.

System Info

Launch Zivid Studio, then click on the buttons in the following order:

Help → About Zivid Studio → System Info → Copy to Clipboard

Operating System

• Ubuntu (18.04, 20.04, 22.04)

• Windows 10

Get the exact Windows build version

To get the exact build version open Settings by pressing Win + I keys on the keyboard, and then navigate to System → About. Scroll down a bit and copy Windows Specifications.

ZDF file

If the issue is related to artifacts in the point cloud or color image, providing a .zdf file will go a long way. To maximize the effectiveness of Zivid’s support, enable Diagnostics before capturing, to collect additional data when saving a .zdf file.

There are three ways to capture with diagnostics enabled.

1. From Zivid Studio:

   In Zivid Studio the setting is at the bottom of the control panel.

   

2. From the SDK:

   Enable the diagnostics setting as any other setting.

   C++

   Zivid::Settings::Diagnostics
   

   C#

   Zivid.NET.Settings.Diagnostics
   

   Python

   zivid.Settings.Diagnostics
   

3. With a config file:

   Using this config file will overwrite the settings to always enable diagnostics. Remember to disable it again in the config file after the debugging session.

   1. Download the Config.yml file.

      The config file contains the following information:

      __version__:
          serializer: 1
          data: 13
      Configuration:
          Capture:
              Diagnostics:
                  Enabled: Always
      

   2. Place the config file in the following directory:

      Windows

      mkdir %LOCALAPPDATA%\Zivid\API
      move %HOMEPATH%\Downloads\Config.yml %LOCALAPPDATA%\Zivid\API\
      

      Ubuntu

      mkdir --parents "${XDG_CONFIG_HOME-$HOME/.config}"/Zivid/API
      mv ~/Downloads/Config.yml "${XDG_CONFIG_HOME-$HOME/.config}"/Zivid/API/
      

   Caution

   Zivid configuration files must use .yml file extension ( not .yaml).