KhronosGroup
KHR_texture_video
This is a proposal for an extension to standardize the way that video textures can be assigned in gltf. Currently video textures are supported by most standard 3D players on the web, but the configuration of the texture requires custom javascript unique to each player. This extension intends to standardize that.
There is an MPEG extension MPEG_texture_video, which serves the same purpose but defines the details of how the video format looks like and how it is fed dynamically. Please consider using that extension.
Regarding the vendor extensions MPEG_texture_video and related extensions, it looks like there were two parallel efforts on video textures around the same time. I could see a potential consolidation where we make one extension that defines how video textures are referenced and time-controlled (e.g. linkage from texture and autoplay / connection to KHR_animation_pointer) and potentially another set of extensions that add to that support for specific formats and codecs and provide the rest of the details that this extension provides.
I would like to make sure that the video texture control is designed to work well with KHR_animation_pointer (and the upcoming interactivity work that ties heavily with that). If some example jsons were added to the MPEG_texture_video set of specs it might make it easier to understand whether it can already work well with KHR_animation_pointer or, if not, how it could be adapted to do so.
@dwrodger the following is an example of MPEG_texture_video which might help for better understanding. The format description, codecs, mime-type, tracks, and other information can be exposed via MPEG_media extension as shown in the example.
@gurdep Those JSON files you linked are just small sections, do you have any links to complete example glTF files?
@gurdep Those JSON files you linked are just small sections, do you have any links to complete example glTF files?
You may ask the MPEG group for complete glTF files at their official github repository.
Since many video container format, like webm in given example, could also include audio tracks, should the behavior of audio tracks in video files be standardized here?
Behaviors might include some of these:
- default audio track
- muted or not
- volume
- should video autoplay be blocked by browser for having audios, or should it fallback to muted autoplay
