@Vladd1980 commented on GitHub (Feb 16, 2025):
Это невозможно в последних версиях, и в этом случае у вас не будет выбора, поскол…
@NickM-27 commented on GitHub (Feb 17, 2025):
To be clear, this ability exists now, you can already define a stream to only be used for live view https://docs.frigate.video/configuration/live#sett…
@JakeMHughes commented on GitHub (Feb 17, 2025):
I thought I tried this but was unable to get the live_stream config working without also defining that stream under a role, but I just tried again…
@NickM-27 commented on GitHub (Feb 16, 2025):
You can use jsmpeg by setting
@NickM-27 commented on GitHub (Feb 16, 2025):
This is not possible in the latest versions, and in this case you would not have a choice because h265 is not supported by webrtc in the current version
@hawkeye217 commented on GitHub (Feb 16, 2025):
The ability to define additional go2rtc streams and use them in Frigate's live view has already been implemented for the next version of Frigate…
@hawkeye217 commented on GitHub (Feb 19, 2025):
The Review pane and the timeline is intentionally designed around a 24 hour period.
To examine tracked objects over a larger range, use the date…
webrtc.filter.candidates: [] by default
@NickM-27 commented on GitHub (Feb 14, 2025):
Oh, my bad 😆 sure this seems like a fine change then
webrtc.filter.candidates: [] by default
@NickM-27 commented on GitHub (Feb 14, 2025):
Then I disagree, stun:8555 should be the default so that webrtc has a chance of working outside the local network by default. And per the Frigate…
webrtc.filter.candidates: [] by default
@felipecrs commented on GitHub (Feb 14, 2025):
Sorry @NickM-27, I think you got confused. lol
This is not about webrtc.candidates, this is about webrtc.filter.candidates.
And this is not…
webrtc.filter.candidates: [] by default
@felipecrs commented on GitHub (Feb 14, 2025):
A heads-up, I noticed the workaround/alternative is not currently working. You write:
webrtc.filter.candidates: [] by default
@felipecrs commented on GitHub (Feb 14, 2025):
There is a non-negligible chance this will reduce WebRTC negotiation time for all users. I.e. will make camera streams open faster through WebRTC.