Knowledge Base

Problem

When using EthoVision XT alongside Noldus MediaRecorder with a Basler GigE camera, users experience camera or acquisition issues such as dropped frames, display errors, or instability. Switching video processing from GPU to CPU resolves the problem.

Details

Reported with a Basler acA1300-60gm camera, MediaRecorder 6.5, and EthoVision 17.5 connected via an Intel CT 1000 GigE adapter. Symptoms include camera instability or acquisition errors during live recording/tracking sessions. The issue is related to GPU-accelerated video processing conflicting with the camera or MediaRecorder configuration. Switching to CPU-based video processing in EthoVision's video settings resolves the issue. See also: 'GPU Rendering Issues in EthoVision XT – Switching to CPU Video Processing'.

Solution

1. In EthoVision XT, go to the Video Settings (accessible from the main menu or acquisition settings).
2. Change the video processing mode from GPU to CPU.
3. Save the settings and restart EthoVision if prompted.
4. Retest camera detection and acquisition with MediaRecorder running alongside EthoVision.
5. If the issue persists after switching to CPU processing, check the GigE network adapter configuration and ensure the Basler Pylon drivers are up to date.
6. Also verify that only one GPU is active in the system; systems with two GPUs can cause additional acquisition conflicts (see 'Two GPUs Installed in System Cause Camera or Acquisition Issues After EthoVision Upgrade').