-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[Camera Support]: Adding Transcoded AAC Audio to go2rtc stream Corrupts all recording segments shortly after startup #7515
Comments
I'd suggest a config like this cameras:
entryway_doorbell_frigate:
ffmpeg:
output_args:
record: preset-record-generic-audio-aac
inputs:
- path: rtsp://nas_local_ip:8554/entryway_doorbell_frigate?audio&video
input_args: preset-rtsp-restream
roles:
- record
- detect so that way the transcoding occurs on the frigate side |
I'm seeing the same issue with that config. It works initially but starts giving
|
Thanks for trying it, in that case it seems the audio that is being sent is just corrupted after streaming for some time |
Gotcha. So this could potentially an issue with go2rtc then? I know the hass and nest integrations in go2rtc are still pretty new I had some new errors pop up in my log just now that I'll share in case that spark any other ideas:
|
I'd think it's more than likely an issue with the doorbells stream, but I suppose it could be go2rtc as well.
Looks like stream is not stable. |
Okay, thanks for clarifying. My doorbell is ~15 feet from my router and I haven't noticed any abnormalities viewing it through the google home app, apple home app (via starling home hub), or home assistant, so it seems to me like go2rtc is the remaining variable but there's a lot of hoops being jumped through to reach this setup so that's hard to pin down. Thanks for your help! I'll keep tinkering to see if I can unearth anything but I'm definitely on the nascent edge of integrating this doorbell so hopefully someone else can help iron out the final kinks over time. |
I'd suggest making an issue on go2rtc, also try keeping an MSE stream open (with the AAC transcoding enabled in go2rtc config) and see if the stream fails / shows errors. |
Attempting to view the MSE stream option from my go2rtc stream links ( |
Found home-assistant/core#86610 which is likely related to this issue |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Describe the problem you are having
I recently integrated my Nest Doorbell Wired (2nd Generation) with frigate and I was successful at bringing in the video stream via go2rtc's home assistant integration but the default mp4 stream from go2rtc did not include audio, so I configured go2rtc to transcode AAC audio into the stream with ffmpeg so that my recordings in frigate would include audio.
When I comment out the
"ffmpeg:entryway_doorbell_frigate#audio=aac"
line of my go2rtc config and leave my stream as just video with no audio, everything runs and records fine. My problem is when I enable the AAC transcoding for the stream, my recording will work for a bit (usually 5-10 minutes but sometimes longer) when frigate starts but it eventually starts discarding every recording with a log saying "WARNING : Discarding a corrupt recording segment: /tmp/cache/entryway_doorbell_frigate-.mp4" every 10 seconds until I restart frigate.Version
0.12.1-367D724
Frigate config file
Relevant log output
FFprobe output from your camera
Frigate stats
Operating system
Debian
Install method
Docker Compose
Coral version
USB
Network connection
Wired
Camera make and model
Nest Doorbell Wired (2nd Generation)
Any other information that may be helpful
My docker host is a NAS running OpenMediaVault 6.6.0-2 on top of Debian 11 with an i5-6500 CPU and 8GB of RAM
Here's my docker-compose:
The text was updated successfully, but these errors were encountered: