-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
docs: remove webrtc not support H.265 tips #20769
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
base: master
Are you sure you want to change the base?
Conversation
Clarified the WebRTC requirements and removed the note about H.265 support.
✅ Deploy Preview for frigate-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
The current documentation has been updated as a supplement to PR #19688 to avoid misunderstandings. Additionally, if necessary, browser support details can be specified in the documentation, but incorrect statements must not be used. |
|
I would prefer to have browser-specific information in the docs rather than remove these statements altogether. |
docs/docs/configuration/live.md
Outdated
|
|
||
| - For access through Tailscale, the Frigate system's Tailscale IP must be added as a WebRTC candidate. Tailscale IPs all start with `100.`, and are reserved within the `100.64.0.0/10` CIDR block. | ||
|
|
||
| - Note that some browsers may not support H.265 (HEVC). You can check your browser's current version for H.265 compatibility [here](https://caniuse.com/hevc). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would be good to call out that H.265 playback is not universal. A browser might support H.265 HLS playback but not WebRTC for example.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's unfortunate. Currently, I haven't found any official documentation clearly stating whether WebRTC H.265 is officially supported :(
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Safari requires a developer flag to be enabled. Chrome on MacOS and Windows has added support, not sure about linux or any other browsers
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is all already documented in go2rtc https://github.com/AlexxIT/go2rtc?tab=readme-ov-file#codecs-madness
Updated the link for H.265 compatibility check to point to the new resource.
Clarified the WebRTC requirements and removed the note about H.265 support.
Proposed change
Remove webrtc not support H.265 tips
Type of change
Additional information
Checklist
enlocale.ruff format frigate)