-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
feat(media): add crossOrigin prop to @remotion/media Audio & Video components
#5989
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: main
Are you sure you want to change the base?
Conversation
|
@hnbnh is attempting to deploy a commit to the Remotion Team on Vercel. A member of the Team first needs to authorize it. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
@remotion/media Audio & Video components
JonnyBurger
left a comment
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.
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 .
ffd4838 to
7eaafd1
Compare
7eaafd1 to
8858207
Compare
crossOriginfor@remotion/media<Audio> & <Video> #5987