Nicholas Butko
Nicholas Butko
/facetoface
The goal is to prepare the user appropriately for which kind of permissions will be requested before requesting them.
> @nbutko had a preference for being able to get access to MediaStreams/MediaTracks for mixing the recording (e.g. adding watermarks, custom audio tracks, and encoding to non-webm format) It's also...
> Given this, I think there still needs to be some opaque way of capturing a recording. Canvas taint provides a good existing model for this.
We are advocating for consistency of experience across Desktop 3D (canvas, no camera feed), Mobile WebAR (canvas, camera feed), and headset (WebXR). Particularly, we would like to take existing flows...
> Headsets are the only devices that implement layers at this point, but there's no reason to expect that they'll always be unavailable to mobile AR. True, they don't provide...
As an example of what's currently supported and expected by developers on the web, this is the 8th Wall Media Recorder API, which is widely used by 8th Wall's developers:...
Here's an example of that API in action: https://www.8thwall.com/alivenow/freefire You can take a photo or record a video. Recorded videos include overlayed 2D UI elements and a custom end card....
> There are other developers for whom capturing their DOM Overlay elements is a requirement. I would try to assess what the true product requirement is here -- is it...
Currently recording with 8th Wall's recorder allows overlay of 2D content by drawing to a foreground canvas (usually with a 2D context) which gets composited over the 3d canvas. This...