Troubleshooting
This page covers problems you can diagnose from the Dashboard. Hardware, installers, and on-disk logs are in Management troubleshooting.
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 VidRedi. Not every codec is supported or available.
3. Resource Constraints
Problem: System lacks resources (CPU, memory, disk I/O).
Solution:
- Reduce the number of simultaneous channels if you can
- Reduce recording quality/bitrate if acceptable
- If the machine stays at capacity, an administrator should check Management troubleshooting
4. Configuration Errors
Problem: Invalid pipeline configuration.
Solution:
- Use channel wizard templates (recommended)
- Review error messages in logs for specific issues
- Reset the channel to a template and reconfigure
5. Storage Issues
Problem: Cannot write to storage location.
Solution:
- Check free space in the header stats panel
- Delete old packages and empty Trash. See Library
- If the disk still will not write, an administrator should check Management troubleshooting
Debugging Pipelines
Press D while a channel is selected to view debugging information:
- Current pipeline status
- Error messages
- Buffer states
- Resource usage
Check Configuration → Logs for detailed error messages. On-disk locations are listed in Management troubleshooting.
Network Stream Problems
Network-related issues affect streaming and download channels.
Stream Connection Failures
Symptoms:
- Cannot connect to network stream
- Connection drops repeatedly
- Timeout errors
Solutions:
- Confirm the SRT or RIST address and port from another trusted machine on the same network.
- For HLS, open the playlist URL in a browser and confirm it returns a playlist.
- For a protected stream, confirm the username and password on the source.
- For the web interface, see Sign In and Profile. After 10 failed sign-ins from one address in 15 minutes, wait for the window to expire.
If the address is correct and the stream still fails, an administrator should check firewall rules and routing. See Management troubleshooting.
Bandwidth Issues
Symptoms:
- Buffering or stuttering playback
- Dropped frames
- Quality degradation
Solutions:
- Lower bitrate settings if possible
- Reduce number of simultaneous streams
- Use a wired connection instead of WiFi
HLS Download Issues
Symptoms:
- Downloads fail to start
- Incomplete downloads
- Slow download speeds
Solutions:
-
Verify HLS URL:
- Test the URL in a web browser
- Check that the m3u8 playlist is accessible
-
Check for Geo-Restrictions:
- Some streams may be region-locked
- Check if access is allowed from your location
-
Review Download Logs:
- Check for specific error messages
- Look for HTTP error codes (403, 404, etc.)
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
When to Hand Off to an Administrator
Stop here and use Management troubleshooting when:
- A DeckLink card is not detected
- The installer or an upgrade failed
- You need on-disk logs, firewall rules, or system resource tools
- The machine is consistently at CPU, memory, or disk capacity
If you cannot resolve an issue, see Support.