-
Notifications
You must be signed in to change notification settings - Fork 589
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
Inconsistent 2 way audio #1573
Comments
Forgot to note, the only error/warning I see in logs for go2rtc is |
Only one RTSP source can take two way audio. Even if you don't need a microphone, it will still be busy. Setting RTSP not to occupy the microphone:
|
While that is good to know, the inconsistency issue still occurs with just a single camera in the stream. Maybe I'll retry it with ffmpeg since theres a snippet in the docs regarding glitchy cameras and when I tested it previously, I did have multiple streams configured on one camera |
With ffmpeg source you won't get two way audio. |
Ohhh, I was under the impression that the snippet below for RTSP was still in regards of two way audio
|
So curiously, I think frigate may be the cause for the issue. On frigate I configured the go2rtc stream but I never configured it in frigates "Cameras" section and its consistently allowing my mic to work. If I configure it in the cameras section in frigate, that's when the inconsistency issue happens. im curious if frigates "detect" or "record" roles are consuming the receive audio function (since you mentioned only one consumer at a time) so then I am unable to access it in frigates live view I'll play with it some more, but in the mean time I just set it up with the mic in home assistant directly (skipping frigate) so it will work like that for now |
One more time. It doesn't matter if you consume sound. And whether you need two way audio or not. Simply connecting to RTSP in "two way audio support mode" will already block the ability to connect to the camera in that mode from another location. By default go2rtc will always connects to RTSP camera in two way audio mode. |
And I understood that. Ultimately I want two way audio to work through frigate, but for a camera to appear on frigates "live view" you need to add it to the cameras section in frigate config. By doing so you have to configure a role - detect,record,or audio. no matter which one you pick frigate will always be connected to the camera and it counts as that one connection So for example, if I configure the camera in frigate like below with no other connection
then if I dont load the UI and just go to go2rtc page - gortc will always show 1 consumer on the stream. If I do load frigate UI it will show 2 connected consumers ( it doesnt reuse the other stream) And finally if I configure the only stream with backchannel=0, it seems to apply that same config when I access the camera through frigrate UI Basiaclly I believe you solved my first original issue by providing information, but I need to reach out to frigate team to find out ow I can only enable two way for live view |
I am trying to configure two way audio for a camera I picked up off amazon from a no-name brand Anpviz with varying amounts of success, but I finally got it working but the issue I am seeing now is that it only works sometimes
Basically after I make changes to the config and restart I'll have about 40% chance for the mic portion ( me speaking to computer and it plays on camera speaker) to work. then if I restart again, even if it was working before it may not work again despite the config being the same.
Something Ive observed is if I quickly probe the camera immediately after a restart the probe will include the line "audio, sendonly, PCMU/8000, G726/8000, MPEG4-GENERIC/16000" - but in the times where the mic does not work Ill notice that no longer shows up in the probe. Another observation is if I ave two streams with the exact same config, sometimes it will work on one stream but not the other
Heres everyting I have
Camera audio: G.711ulaw (tried multiple encodings this is the only one that came out clear, others like AAC nothing worked and some just crackled)
go2rtc version: 1.9.8 via frigate (I was using 1.9.2 but noticed a bit better consistency on he newer version)
go2rtc config:
camera probe when working:
and finally a probe when it is not working
The text was updated successfully, but these errors were encountered: