Skip to content

Conversation

@hnbnh
Copy link

@hnbnh hnbnh commented Nov 26, 2025

@vercel
Copy link
Contributor

vercel bot commented Nov 26, 2025

@hnbnh is attempting to deploy a commit to the Remotion Team on Vercel.

A member of the Team first needs to authorize it.

@vercel
Copy link
Contributor

vercel bot commented Nov 26, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
remotion Ready Ready Preview Comment Nov 28, 2025 3:07pm

@hnbnh hnbnh changed the title feat(media): add crossOrigin prop to Audio feat(media): add crossOrigin prop to @remotion/media Audio & Video components Nov 26, 2025
Copy link
Member

@JonnyBurger JonnyBurger left a comment

Choose a reason for hiding this comment

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

Thanks for submitting a PR!

With using the new media tags, the URL will always be fetch()-ed and played with a custom implementation.

There is no underlying <video> or <audio> tag. Therefore the documentation and implementation in its current state is wrong.

Assets must be CORS-enabled to make use of the new @remotion/media tags.
If they are not, they fall back to the HTML5 tags: https://www.remotion.dev/docs/media/fallback#when-a-fallback-is-attempted

The only way this PR can make sense if we add support for the crossOrigin prop in case of a fallback. This prop should then be added under https://www.remotion.dev/docs/media/video#fallbackoffthreadvideoprops and https://www.remotion.dev/docs/media/audio#fallbackhtml5audioprops .

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.

Support crossOrigin for @remotion/media <Audio> & <Video>

2 participants