![]() ![]() For example, usually, on Android, if multiple applications have an active MediaSession (as in the Android one), the latest to activate will have the keys so applications will usually ask for it back when focused in case of their are competing). Use these samples to see the media playback APIs used in context or as a. I would recommend leaving some leeway for implementations to deal with these cases. Media casting, Shows you how to cast media to remote devices from a Universal. Different web browsers may have different video-playback capabilities (supported. We don't really mention this in the Media Session API but it is kind of implicit that being the active session gives you media keys access (or is it mentioned?). However, things will be a bit odd with regards to media keys. ![]() If for some reasons, a user has a device in multiple room it their home, they should be able to control them simultaneously. The Playback API is low-latency API intended for client-side use in fetching video or playlist data from web pages or mobile apps. I agree with above and I think we should allow multiple remote playbacks. It would apply for the default or a specified media session. In term of specs, when the state switches to connected, the remotely played element would be removed from whatever media session it is on and when it's back to disconnected, it would be back. The API enables a page, which has an media element such as a video or audio file, to initiate and control playback of that media on a connected remote device. What we do today is that a remotely played element is removed from the default media session and added back when it is no longer played remotely. Going back to this old discussion, we might want to use Chrome Android behaviour as an example. If the protocols would allow it, I think this could be expanded to allow all members simultaneously to start remote playback, but not for now. I think in practice this would mean that remote playback doesn't work great with multi-element media session, but that doesn't seem terrible, given that things one would expect to play remotely are unlikely to be part of some composed media experience. (Spec would be made to match, of course.) Status of this document This section describes the status of this document at the time of its publication. Then, if one tries to play a (previously paused) media element that's in a remote session, it would either replace the existing element, both would play remotely, or it would throw an exception, depending on what seems possible to implement. The Open Screen Protocol is a suite of network protocols that allow user agents to implement the Presentation API and the Remote Playback API in an interoperable fashion. Would it make sense to only allow remote playback if there's at most one playing element in the session, to make it impossible for the members of a session to split into a local and a remote group? Then the original session could be allowed to represent the remote playback, and if necessary this could be web-exposed on the media session itself as some new state. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |