Skip to content

Conversation

@ZhaiSoul
Copy link
Contributor

@ZhaiSoul ZhaiSoul commented Nov 3, 2025

Clarified the WebRTC requirements and removed the note about H.265 support.

Proposed change

Remove webrtc not support H.265 tips

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New feature
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code
  • Documentation Update

Additional information

  • This PR fixes or closes issue: fixes #
  • This PR is related to issue:

Checklist

  • The code change is tested and works locally.
  • Local tests pass. Your PR cannot be merged unless tests pass
  • There is no commented out code in this PR.
  • UI changes including text have used i18n keys and have been added to the en locale.
  • The code has been formatted using Ruff (ruff format frigate)

Clarified the WebRTC requirements and removed the note about H.265 support.
@netlify
Copy link

netlify bot commented Nov 3, 2025

Deploy Preview for frigate-docs ready!

Name Link
🔨 Latest commit 59353f8
🔍 Latest deploy log https://app.netlify.com/projects/frigate-docs/deploys/690ad53ea9716400081c484c
😎 Deploy Preview https://deploy-preview-20769--frigate-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@hawkeye217
Copy link
Collaborator

See https://caniuse.com/hevc

@ZhaiSoul
Copy link
Contributor Author

ZhaiSoul commented Nov 3, 2025

See https://caniuse.com/hevc

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.

@hawkeye217
Copy link
Collaborator

I would prefer to have browser-specific information in the docs rather than remove these statements altogether.


- 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).
Copy link
Collaborator

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.

Copy link
Contributor Author

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 :(

Copy link
Collaborator

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

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated the link for H.265 compatibility check to point to the new resource.
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.

3 participants