Skip to content
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

ffmpeg-core unpkg NotSameOriginAfterDefaultedToSameOriginByCoep #16

Open
dvnrsn opened this issue May 22, 2022 · 5 comments
Open

ffmpeg-core unpkg NotSameOriginAfterDefaultedToSameOriginByCoep #16

dvnrsn opened this issue May 22, 2022 · 5 comments

Comments

@dvnrsn
Copy link

dvnrsn commented May 22, 2022

The initial problem faced running this app is an inability to successfully fetch from unpkg

image

However, disabling the cross origin leads to the SharedArayBuffer problem as described in installation. Does this mean the ffmpeg core needs to be loaded from same origin?

  const ffmpeg = createFFmpeg({
    corePath: "node_modules/@ffmpeg/core/dist/ffmpeg-core.js",

Doing so creates a problem that I originally faced trying this out in codesandbox

image

@dvnrsn
Copy link
Author

dvnrsn commented May 22, 2022

Related ffmpegwasm/ffmpeg.wasm#263

@dvnrsn
Copy link
Author

dvnrsn commented May 22, 2022

"why it doesn't work in my local environment" section
https://github.com/ffmpegwasm/ffmpeg.wasm#why-it-doesnt-work-in-my-local-environment

@dvnrsn
Copy link
Author

dvnrsn commented May 22, 2022

Was able to resolve this in nextJS context by moving all scripts (ffmpeg-core.js, wasm, worker, min) to public/. This does not seem preferable but working for now.

@0x-sen
Copy link

0x-sen commented Jan 10, 2023

The same error

1 similar comment
@402329651
Copy link

The same error

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

No branches or pull requests

3 participants