Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: implement audio watchdog for RTSP source monitoring #365

Merged
merged 1 commit into from
Jan 5, 2025

Conversation

tphakala
Copy link
Owner

@tphakala tphakala commented Jan 5, 2025

  • Added audioWatchdog struct to track the last time data was received from the RTSP source.
  • Introduced a goroutine that checks for data reception every 5 seconds and triggers a restart if no data is received for 60 seconds.
  • Updated processAudio method to integrate the watchdog, ensuring it updates the last data time upon receiving audio data.
  • Enhanced error handling to wait for the watchdog to finish before returning errors related to data reception.

- Added audioWatchdog struct to track the last time data was received from the RTSP source.
- Introduced a goroutine that checks for data reception every 5 seconds and triggers a restart if no data is received for 60 seconds.
- Updated processAudio method to integrate the watchdog, ensuring it updates the last data time upon receiving audio data.
- Enhanced error handling to wait for the watchdog to finish before returning errors related to data reception.
Copy link
Contributor

coderabbitai bot commented Jan 5, 2025

Caution

Review failed

The pull request is closed.

Walkthrough

The changes introduce an audioWatchdog mechanism in the RTSP audio processing system to monitor data reception. This new struct provides thread-safe tracking of the last time audio data was received, with a background goroutine that checks for data stagnation. If no data is detected for 60 seconds, the system will log a message and trigger a restart of the audio source, enhancing the reliability of the audio input monitoring process.

Changes

File Change Summary
internal/myaudio/ffmpeg_input.go - Added audioWatchdog struct for monitoring data reception
- Implemented update() method to track last data time
- Added timeSinceLastData() method to calculate time since last data
- Modified processAudio() to integrate watchdog monitoring

Sequence Diagram

sequenceDiagram
    participant RTSP as RTSP Source
    participant FFmpeg as FFmpegProcess
    participant Watchdog as AudioWatchdog

    FFmpeg->>Watchdog: Start Monitoring
    loop Every 5 seconds
        Watchdog->>Watchdog: Check Time Since Last Data
        alt No Data for 60+ seconds
            Watchdog-->>FFmpeg: Trigger Restart
        end
    end
    RTSP->>FFmpeg: Send Audio Data
    FFmpeg->>Watchdog: Update Last Data Time
Loading

Poem

🐰 Watchful Rabbit's Audio Tale 🎧

In streams of sound, a guardian stands tall,
Tracking data's pulse, preventing its fall
Five seconds tick, sixty seconds the test
When silence creeps in, our watchdog knows best
Restart the flow, keep the music alive! 🎵


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 175dd9c and 674d620.

📒 Files selected for processing (1)
  • internal/myaudio/ffmpeg_input.go (3 hunks)

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@tphakala tphakala merged commit e519b56 into main Jan 5, 2025
11 of 12 checks passed
@tphakala tphakala deleted the rtsp-fixes branch January 5, 2025 11:55
@joriws
Copy link

joriws commented Jan 10, 2025

I don't think currently implemented watchdog works ok. It detects "No data" from RTSP stream but system does not get up after "triggering restart". At least on container environment.

image

docker logs 1a7dc11461da

🐦 BirdNET-Go build date: 2025-01-06T08:16:09Z, using config file: /root/.config/birdnet-go/config.yaml
BirdNET GLOBAL 6K V2.4 FP32 model initialized, using 1 threads of available 1 CPUs
System details: linux debian 12.8 on unknown hardware
Starting analyzer in realtime mode. Threshold: 0.88, overlap: 1.5, sensitivity: 1, interval: 15
HTTP server started on port 8080 (AutoTLS: false)
2025/01/07 16:59:58 failed to connect to MQTT broker: connection timeout
2025/01/07 16:59:58 Starting ffmpeg with command: /usr/bin/ffmpeg -rtsp_transport tcp -i rtsp://192.168.9.142:554/stream1 -loglevel error -vn -f s16le -ar 48000 -ac 1 -hide_banner pipe:1
2025/01/07 16:59:58 Clip retention policy: age
[2025-01-07T16:59:58+02:00] [INFO] ⇨ http server started on [::]:8080
2025/01/07 17:00:03 Cloudflare Access is disabled
2025/01/07 17:00:03 Cloudflare Access is disabled
2025/01/07 17:00:03 Cloudflare Access is disabled
2025/01/07 17:00:03 Retrieved 5 detections in 742.452µs
2025/01/07 17:00:03 Total time for processing all notes: 350ns
2025/01/07 17:00:51 Human detected with confidence 0.742/0.500 from source rtsp://@192.168.9.142:554/stream1
2025/01/07 17:00:53 Human detected with confidence 0.856/0.500 from source rtsp://@192.168.9.142:554/stream1
2025/01/07 17:01:48 Human detected with confidence 0.711/0.500 from source rtsp://@192.168.9.142:554/stream1
2025/01/07 17:01:50 Human detected with confidence 0.707/0.500 from source rtsp://@192.168.9.142:554/stream1

.......

2025/01/09 14:38:23 Human detected with confidence 0.514/0.500 from source rtsp://@192.168.9.142:554/stream1
2025/01/09 14:39:16 Human detected with confidence 0.609/0.500 from source rtsp://@192.168.9.142:554/stream1
2025/01/09 14:40:04 Human detected with confidence 0.645/0.500 from source rtsp://@192.168.9.142:554/stream1
2025/01/09 14:43:43 No data received from RTSP source rtsp://@192.168.9.142:554/stream1 for 60 seconds, triggering restart
2025/01/09 18:04:25 Cloudflare Access is disabled
2025/01/09 18:04:25 Cloudflare Access is disabled
2025/01/09 18:04:25 Cloudflare Access is disabled
2025/01/09 18:04:25 Retrieved 5 detections in 399.928µs
2025/01/09 18:04:25 Total time for processing all notes: 916.392µs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants