Skip to main content

Troubleshooting

This section covers common issues you may encounter with VidRedi DVR and their solutions.

One of the most common hardware issues is when the system cannot detect your Blackmagic DeckLink card.

Symptoms:​

  • Channel fails to start with hardware error
  • No DeckLink inputs available in configuration
  • Error messages mentioning DeckLink device not found

Solutions:​

1. Verify Physical Installation​

  • Power down the system completely
  • Check the card is properly seated in the PCIe slot
  • Verify power connections if the card requires additional power
  • Restart the system

2. Check Driver Installation​

# Check if the card is visible to the system
lspci | grep Blackmagic

# Expected output: You should see your DeckLink card listed

If the card is visible but drivers aren't working:

  1. Verify Desktop Video is installed:

    dpkg -l | grep desktopvideo

  2. Reinstall Blackmagic Desktop Video if necessary:

    • Download latest version from Blackmagic Design website
    • Uninstall old version: sudo dpkg -r desktopvideo
    • Install new version: sudo dpkg -i <desktop-video-package>.deb

  3. Check Firmware:

    • Use BlackmagicFirmwareUpdater to check if the card firmware is up to date
    • Update firmware if an update is available
    • Restart the system after updating firmware

3. Check Card Permissions​

Ensure the user running VidRedi has permissions to access the DeckLink device:

# Check device permissions
ls -l /dev/blackmagic/*

# Add user to video group if needed
sudo usermod -a -G video vidredi

# Log out and back in for group changes to take effect

4. Check for Conflicts​

  • Ensure no other applications are using the DeckLink card
  • Close Media Express or other Blackmagic software
  • Restart VidRedi DVR

Pipeline Failures​

Pipeline failures occur when the video processing pipeline cannot be created or fails during operation.

Symptoms:​

  • Channel fails to start
  • Recording stops unexpectedly
  • Error messages about pipeline initialization
  • "Pipeline failed" notifications

Common Causes and Solutions:​

1. Format Mismatch​

Problem: Channel configuration doesn't match the input signal.

Solution:

  • Verify input signal format (resolution, frame rate)
  • Update channel configuration to match
  • Use the channel wizard templates as a starting point

2. Missing Codecs or Plugins​

Problem: Required plugins are not installed.

Solution:

Ensure you are using the latest version of the VidRedi. Note that not every codec is supported or available to VidRedi.

3. Resource Constraints​

Problem: System lacks resources (CPU, memory, disk I/O).

Solution:

  • Check system resource usage: top or htop
  • Reduce number of simultaneous channels
  • Upgrade hardware if consistently at capacity
  • Reduce recording quality/bitrate if acceptable

4. Configuration Errors​

Problem: Invalid pipeline configuration.

Solution:

  • Use channel wizard templates (recommended)
  • Review error messages in logs for specific issues
  • Reset channel to default configuration and reconfigure

5. Storage Issues​

Problem: Cannot write to storage location.

Solution:

  • Check disk space: df -h
  • Verify write permissions on recording directory
  • Check for disk errors: dmesg | grep -i error

Debugging Pipelines​

Press D while a channel is selected to view debugging information:

  • Current pipeline status
  • Error messages
  • Buffer states
  • Resource usage

Check the logs for detailed error messages (see Logs section below).

Network Problems and Debugging​

Network-related issues affect streaming and download channels.

Common Network Issues:​

1. Stream Connection Failures​

Symptoms:

  • Cannot connect to network stream
  • Connection drops repeatedly
  • Timeout errors

Solutions:

  1. Verify Network Connectivity:

    # Ping the stream server
    ping <server-address>

    # Check route to server
    traceroute <server-address>

  2. Check Firewall Rules:

    # Check if ports are blocked
    sudo iptables -L -n | grep <port>

    # Allow required ports if needed
    sudo ufw allow <port>/tcp

  3. Test Stream URL Directly:

    # For RTSP streams
    gst-launch-1.0 rtspsrc location=<rtsp-url> ! fakesink

    # For HLS streams
    curl -I <hls-url>

  4. Check Credentials:

    • Verify username/password if required
    • Check for authentication errors in logs
    • Review Authentication and User Management for default login details and user access guidance

2. Bandwidth Issues​

Symptoms:

  • Buffering or stuttering playback
  • Dropped frames
  • Quality degradation

Solutions:

  1. Monitor Network Usage:

    # Install iftop if not available
    sudo apt-get install iftop

    # Monitor bandwidth usage
    sudo iftop -i <interface>

  2. Reduce Quality:

    • Lower bitrate settings if possible
    • Reduce number of simultaneous streams

  3. Network Optimization:

    • Use wired connection instead of WiFi
    • Ensure network equipment (switches, routers) can handle bandwidth
    • Check for network congestion

3. HLS Download Issues​

Symptoms:

  • Downloads fail to start
  • Incomplete downloads
  • Slow download speeds

Solutions:

  1. Verify HLS URL:

    • Test the URL in a web browser
    • Check that the m3u8 playlist is accessible

  2. Check for Geo-Restrictions:

    • Some streams may be region-locked
    • Check if access is allowed from your location

  3. Review Download Logs:

    • Check for specific error messages
    • Look for HTTP error codes (403, 404, etc.)

Logs and Where They're Located​

Logs are essential for troubleshooting detailed issues.

Log Locations​

VidRedi logs are typically located in:

  • Application logs: Check the application's data directory
  • System logs: /var/log/syslog or /var/log/messages
  • Package logs: /packages/videoId/logs/ - Each folder corresponds to a process ID from the main application log, and the files under it contain everything that was logged for that package

Viewing Logs​

# View recent application logs (adjust path as needed)
tail -f /path/to/vidredi/logs/application.log

# View system logs
sudo tail -f /var/log/syslog

# View package-specific logs
tail -f /packages/<videoId>/logs/<processId>/*.log

# Search for errors
grep -i error /path/to/vidredi/logs/*.log

Understanding Log Levels​

Winston log levels (from most to least verbose):

  • silly: Extremely detailed debug information
  • debug: Debug information
  • info: General informational messages
  • warn: Warning messages
  • error: Error messages

Debugging Statistics (D Key)​

Press D on any active channel to display real-time debugging information:

  • Pipeline state
  • Buffer fill level
  • Frame drops

This information is valuable for quick diagnostics without diving into logs.

Audio Issues​

No Audio on Playback​

Causes:

  • Audio channels not configured correctly
  • Source doesn't provide expected audio channels
  • Audio codec not supported

Solutions:

  • Verify audio channel configuration matches source
  • Check source is providing audio
  • Test with fewer audio channels
  • Review codec support

Audio/Video Sync Issues​

Causes:

  • Pipeline timing problems
  • Source sync issues
  • Buffer configuration

Solutions:

  • Check debugging info (press D)
  • Restart the channel
  • Review pipeline configuration
  • Reduce number of audio channels if unnecessary

Performance Issues​

High CPU Usage​

Causes:

  • Too many channels running
  • Inefficient encoding settings
  • Software encoding instead of hardware

Solutions:

  • Reduce number of simultaneous channels
  • Use hardware encoding if available
  • Optimize encoding settings
  • Upgrade CPU

Dropped Frames​

Causes:

  • Insufficient system resources
  • Disk I/O bottleneck
  • Network issues (streaming channels)

Solutions:

  • Monitor system resources
  • Use faster storage (SSD/NVMe)
  • Reduce recording quality/bitrate
  • Fix network issues

Getting Additional Help​

If you cannot resolve an issue:

  1. Collect Information:

    • Exact error messages
    • Relevant log entries
    • System configuration
    • Steps to reproduce the issue

  2. Check Logs:

    • Application logs
    • System logs

  3. Contact Support:

    • Email: [email protected]
    • Include collected information
    • Provide log excerpts (not entire log files)