Understand the current status of MoQ Players

[nicolaslevy]

Let's understand and compare what players are there:

• MoQT draft version support
• Language
• Packaging capabilities
• ABR or any implementaiton?
• What control messages support,
• any other ideas?

[nicolaslevy]

Key insight: We have different drafts of WARP, MOQT, etc... a player can Have MoQT 05 and WRAP 01 for example... that makes things difficut... Interop effots are in the way: https://github.com/moq-wg/moq-transport/wiki/Interop

Agreements:

• Understand current ecosystem, take a look at: https://github.com/moq-wg/moq-transport/wiki/Interop
  • Undesrtand the MoQ Interop and add it to the Whiteboard: https://www.ietf.org/archive/id/draft-cenzano-moq-media-interop-00.html#name-video-h264-in-avcc-with-wcp
• Currently moq-js works with draft 05. What is needed to go to draft 06?
  • We can check current draft PR from moq-rs moq-transport draft-06 initial wire format updates englishm/moq-rs#8
  • Diff MoQT 05 vs 06 moq-wg/moq-transport@draft-ietf-moq-transport-05...draft-ietf-moq-transport-06

[nicolaslevy]

I updated the Whiteboard wiht the Information from the Interop draft. All the red areas are the new ones.

From the draft intro sounds that in the future LOC and WCP (a packaging format optimized for WebCodecs) could be merged.

The protocol defines a low overhead packaging format optimized for WebCodecs called WCP that is extensible to other formats such as FMP4. This is not LoC [LOC], but will eventually be merged with that specification.

Some ideas to discuss:

• As we saw in Mikes presentation https://github.com/facebookexperimental/moq-encoder-player uses WCP. This could be a interesting experiment to do in moq-js: implement WCP try to play video from moxygen.
• Also, this week a track selection feature PR was merged into moq-js. Now the user can choose a rendition (track) to watch. What I noticed is that the UI of the player is decoupled. Maybe we can also do some UI work to have a play /pause button (sending unsubscribe messages) and the track selector in the Player UI. Maybe this can be a low hanging fruit to start coding in moq-js ;)

[nicolaslevy]

After yesterday meeting we agreed to create this 4 Tickets in the moq-js player as low hanging fruits:

• Add Basic Player (UI) Controls englishm/moq-js#7
• Add Mute/Unmute Functionality to the Player englishm/moq-js#6
• Add Pause/Resume Functionality englishm/moq-js#5
• Decouple the Player from the Web Application englishm/moq-js#4