Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Editor: Video renderer no longer available in Chrome
See original GitHub issueDescribe the bug
The editor’s video renderer relies on a global SharedArrayBuffer constructor. Previously, this was compatible with Chrome and not Firefox.
However API changes have made this condition fail in Chrome too without certain headers present. AFAIK, the video renderer is not visible in any modern browser.
To Reproduce
In Chrome (currently v102.0.5005.61), run 'SharedArrayBuffer' in window. It will evaluate to false, and the video renderer UI will not appear on https://threejs.org/editor
Expected behavior
The video renderer will be visible and functional in the editor on Chrome at least. I have to read more deeply about the new security restrictions, but hopefully this is an easy fix.
Platform:
- Device: 2018 MacBook Pro
- OS: MacOS 11.6
- Browser: Chrome 102.0.5005.61
- Three.js version: r141
Issue Analytics
- State:
- Created a year ago
- Comments:11 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Or we can just use a version without SharedArrayBuffer: https://github.com/ffmpegwasm/ffmpeg.wasm/issues/137#issuecomment-1014956114
Ah, I see… Feel free to do a PR so we can give it a try 👍