Yes? Maybe? I've written a custom "Tech"[1] implementation to handle WebRTC's WHEP[2] protocol with quite a bit of LLM assistance. It works well with standard video (just playing equirect video as-is), but initializing Pannellum with has been flaky. Native video playback is super resilient, but Pannellum (and all alternatives I found) use WebGL to do the spherical 3D playback, which has some quirks in our use-case. From what I understand so far, with videos, you always get metadata with the first frames, but with WebRTC, the video is a bit "late" (by design[3]). It seems to be the issue with initializing the WebGL context, as it's not that tolerant to "resizing" that effectively has to happen after the first frame is received. That's why `setTimeout(init, 2000)` works. If you `init` immediately, it breaks. If you load the page and press play immediately, it breaks. You have to load the page, wait for 2+ seconds, and only then press play for it to work. Surprisingly, some workarounds I've tried were very Firefox friendly, but none of them worked well on Chrome and Safari. It's not a showstopper, but I do need to dive deeper into it to understand it and be able to workaround it. [1] https://videojs.org/guides/tech/ [2] https://dev.to/dolbyio/what-is-whep-intro-to-webrtc-streaming-part-2-3d99 [3] https://github.com/ossrs/srs/issues/3950#issuecomment-1982040069