rwxsh · HackerTrans

4 yıl öncediscuss

I have the Avegant Glyph, which is fixed, and I it is uncomfortable. It's natural to move your head to change your view, but that doesn't work with these devices. In practice I use a Quest instead, but even Daydream was more comfortable for media consumption.

rwxsh

5 yıl öncediscuss

The modern equivalent is the Web Platform Tests[1], which are far more extensive than the Acid tests were. Browser conformance is tracked continuously[2].

[1] https://github.com/web-platform-tests/wpt [2] https://wpt.fyi/

rwxsh

5 yıl öncediscuss

I probably shouldn't nitpick here, but Chrome's WebCodecs team is a subset of the Media team. Color simply wasn't the first priority to implement.

What has changed is that more functionality got pulled into WebCodecs as it became clear that existing web platform objects (eg. ImageBitmap) were not an ideal fit.

rwxsh

5 yıl öncediscuss

> Project leaders from Ffmpeg, Google, Mozilla, Microsoft (and probably Nvidia and AMD) need to all get together and decide on a single method.

Speaking non-officially as a browser implementer, VUI isn't always reliable as a source of color, both because the encoders don't always know, and the decoders don't always extract it reliably. The container is a more reliable place to put it (eg. MP4 'colr' box).

Browsers do differ in behavior when these sources of metadata differ. It currently looks likely that WebCodecs will require implementations to use app-provided color metadata over in-band metadata, which would be good for interoperability!

rwxsh

5 yıl öncediscuss

Rust has this, it's `let ... = match { ... };`.

comments