Skip to main content

Notifications

VidRedi DVR's notification system keeps you informed about system events, errors, and important status changes.

Understanding Notifications

The notification system alerts you to:

  • Recording start/stop events
  • System errors and warnings
  • Storage warnings (low disk space)
  • Channel status changes
  • Pipeline failures
  • Network connectivity issues
  • Hardware problems (DeckLink card issues)

Notification Types

Informational Notifications

These notifications provide status updates:

  • "Recording started on Channel 1"
  • "Download completed for package ABC"
  • "Channel activated successfully"

Action Required: Usually none, just informational

Warning Notifications

These indicate potential issues:

  • "Low disk space warning (10% remaining)"
  • "Audio channel mismatch detected"
  • "Network latency increasing"

Action Required: Review and potentially take preventive action

Error Notifications

These indicate problems that need attention:

  • "Pipeline failed to start on Channel 2"
  • "DeckLink card not detected"
  • "Recording failed due to disk full"

Action Required: Investigate and resolve the issue

Critical Notifications

These indicate serious problems requiring immediate attention:

  • "System storage critical (less than 5% free)"
  • "Multiple channel failures detected"
  • "Hardware error detected"

Action Required: Immediate investigation and resolution needed

Viewing Notifications

Notification Panel

Access notifications through the interface:

  1. Notification Icon: Usually in the header/toolbar
  2. Click to View: Opens the notification panel
  3. Badge Counter: Shows number of unread notifications

Notification Details

Each notification includes:

  • Timestamp: When the event occurred
  • Severity Level: Info, Warning, Error, Critical
  • Source: Which channel or component triggered it
  • Message: Description of the event
  • Details: Additional technical information

Managing Notifications

Marking as Read

  • Click on a notification to mark it as read
  • Use "Mark all as read" to clear unread status
  • Read notifications may be automatically archived after a period

Dismissing Notifications

  • Dismiss individual notifications you've addressed
  • Some notifications auto-dismiss when the issue is resolved
  • Critical notifications may require acknowledgment

Clearing Notifications

  • Clear old notifications to keep the list manageable
  • Option to clear all read notifications at once
  • Some systems may auto-clear after a set period

Notification Settings

Configuring Notifications

You may be able to customize:

  • Which events trigger notifications
  • Notification severity levels to display
  • Sound alerts for certain notification types
  • Email notifications for critical events (if configured)

Filtering Notifications

Filter the notification view by:

  • Severity: Show only warnings and errors
  • Source: Notifications from specific channels
  • Time Period: Recent notifications or specific date range
  • Type: System vs. channel notifications

Common Notification Scenarios

Recording Notifications

"Recording Started"

  • Confirms a recording has begun
  • Check recording indicator on the channel

"Recording Stopped"

  • Indicates recording has ended
  • Verify the package in the library

"Recording Failed to Start"

  • Check channel configuration
  • Verify source is active
  • See Troubleshooting for pipeline issues

Storage Notifications

"Low Disk Space"

  • Review current storage usage
  • Delete or archive old content
  • Empty trash to free space
  • See Managing the Library

"Disk Space Critical"

  • Immediate action required
  • Stop non-essential recordings
  • Free space immediately
  • Check for runaway recordings

Hardware Notifications

"DeckLink Card Not Detected"

  • Check physical card installation
  • Verify drivers are installed
  • Restart system if necessary
  • See Troubleshooting

"DeckLink Input Signal Lost"

  • Check video source is active
  • Verify cable connections
  • Check input selection on source device

Pipeline Notifications

"Pipeline Failed"

  • Check channel configuration
  • Review logs for detailed error messages
  • Press 'D' on the channel for debugging info
  • See Troubleshooting

"Pipeline Restarted"

  • System automatically recovered from an error
  • Monitor the channel to ensure it stays stable

Network Notifications

"Network Stream Connection Lost"

  • Check network connectivity
  • Verify stream source is still available
  • Check firewall settings

"Download Failed"

  • Verify URL is still valid
  • Check network connectivity
  • Check for access restrictions on the source

Notification Best Practices

Regular Monitoring

  1. Check Daily: Review notifications at least once per day
  2. Address Warnings Promptly: Don't let warnings become errors
  3. Investigate Patterns: Recurring notifications may indicate underlying issues

Proactive Response

  1. Storage Management: Address low space warnings before they become critical
  2. Channel Health: Investigate channel issues before they affect recordings
  3. System Maintenance: Use notifications to guide maintenance tasks

Record Keeping

  1. Note Critical Events: Keep a log of serious issues and resolutions
  2. Track Patterns: Document recurring problems
  3. Reference for Troubleshooting: Past notifications can help diagnose new issues

Integration with Logging

Notifications are also recorded in system logs:

  • More detailed information available in logs
  • Useful for troubleshooting
  • See Troubleshooting - Logs for log file locations