Requirements for multi-device timing while streaming.
@pthatcherg ya está trabajando en esto.
Desde el 26/8/2019.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
This issue tracks discussion of protocol changes to allow multi-device synchronization of media playback while streaming. This was discussed at the Berlin F2F [1].
It's assumed that if there's one sender and one receiver the current protocol is sufficient to play out audio and video on the receiver with lip sync.
However, once there are multiple receivers, we'll need some timing metadata to be exchanged between the sender and receivers. Here are a few possible scenarios (not exhaustive):
- Sending audio to one device and video to another.
- Sending audio to multiple devices.
- Sending video to multiple devices.
- Sending audio and video to multiple devices (possibly with multiple audio and video tracks).
- Scenarios involving text tracks or metadata cues.
- Scenarios involving non-1.0-rate playback.
Not all of these may be in scope, however. Items 1 and 4 were pointed out as important in Berlin.
Next steps are to research what's feasible from an implementation point of view, and study the proposals in the following groups:
Multi-Device Timing CG Timing Object: https://webtiming.github.io/timingobject/
Media Timed Events TF: https://github.com/WICG/datacue/blob/master/explainer.md
[1] https://www.w3.org/2019/05/23-webscreens-minutes.html#x29
- Lenguaje dominante
- Bikeshed
- Estrellas
- 115
- Forks
- 21
- Merge medio
- 5 h 2 min
- PR fusionados (30 d)
- 2
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de w3c/openscreenprotocol
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 18/100
w3c/openscreenprotocol#380 ·
-
osp-application
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
w3c/openscreenprotocol#377 ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 38/100
w3c/openscreenprotocol#376 ·
-
osp-application
Dificultad 2/5 1-3 horas Aptitud para principiantes 55/100
w3c/openscreenprotocol#375 ·
-
osp-application question
Dificultad 5/5 Más de una semana Aptitud para principiantes 30/100
w3c/openscreenprotocol#374 ·