Julien Beisel

@jaronwanderley Is is still not working ? I have no issue and I can't reproduce the bug.

You can try that on Linux : - Quit any running instance of Chrome. - Run your favorite terminal emulator. - In the terminal, run commands like below ``` google-chrome...

You have to set your `Cross-Origin-Opener-Policy` header to `same-origin` and `Cross-Origin-Embedder-Policy` to `require-corp`

I would first store it in the FS: ``` javascript await ffmpeg.run("-formats", ">", "formatList.txt") ``` And then read it: ``` javascript let check = ffmpeg.FS('readFile', 'formatList.txt'); ```

@hoomanaskari I agree, using CORP and COEP is an issue regarding the use of external resources. However, I think an appropriate configuration of your back-end should let you use Stripe...

@hoomanaskari Hi, thanks for the reply, I was wrong: we can't use Stripe on our website as well... I'm thinking about workarounds. Do you think you can only cross-isolate a...

+1 It would indeed be interesting to know the future of the project. However, I think it is stable and we are using it in production without worries.

Chrome 92 was just released and do need cross-origin-isolation. I think the doc has to be updated : https://ffmpegwasm.github.io/

You need to enable Cross Origin Isolation for that : https://web.dev/cross-origin-isolation-guide/ I don't know how to set headers in my local environnement, my workaround is to launch Chrome with this...

@Guisch I'm late to the party but thank you so much for figuring this out! I spent 30mn debugging my code without knowing what to do.