This thread should be closed ;)

Topics: Windows 10 UWP
Coordinator
May 21, 2015 at 7:24 PM
Edited Aug 31, 2015 at 5:03 PM
This thread should be closed ;)
Marked as answer by ibennett on 8/31/2015 at 10:03 AM
May 27, 2015 at 9:22 AM
How will subtitles embedded in a MKV container be surfaced by the Player Framework? Is that support upcoming?
Coordinator
May 27, 2015 at 3:19 PM
PombeirP wrote:
How will subtitles embedded in a MKV container be surfaced by the Player Framework? Is that support upcoming?
What format are the embedded captions?
May 27, 2015 at 4:00 PM
Is adaptive streaming supported in Windows 10 now?
If no is it planned?
Coordinator
May 27, 2015 at 4:37 PM
zayass wrote:
Is adaptive streaming supported in Windows 10 now?
If no is it planned?
HLS and DASH are supported natively by the platform. Smooth Streaming requires the client SDK which has not yet been ported.
May 27, 2015 at 4:57 PM
Edited May 27, 2015 at 4:58 PM
I too would love to know whether compatible embedded MKV subs (SRT, ASS, SSA, webvtt) will show up in AvailableCaptions or similar.

Also, what is the blessed mechanism for playing sidecar SRT, ASS and SSA files? Will there be new PF plugins, parallel to the webvtt plugin, or will there be a new sidecar caption playback mechanism?

Lastly, which video and audio codecs are supported over HLS and DASH?

Thanks!
Coordinator
May 27, 2015 at 10:05 PM
Edited May 28, 2015 at 12:08 PM
mfeingol wrote:
I too would love to know whether compatible embedded MKV subs (SRT, ASS, SSA, webvtt) will show up in AvailableCaptions or similar.

Also, what is the blessed mechanism for playing sidecar SRT, ASS and SSA files? Will there be new PF plugins, parallel to the webvtt plugin, or will there be a new sidecar caption playback mechanism?

Lastly, which video and audio codecs are supported over HLS and DASH?

Thanks!
Support for MKV is actually being provided by the underlying MediaElement of the Windows 10 Media Foundation. As such, support for embedded captions would have to be provided directly by the platform and lighting up the associated transport controls in PF is not currently supported. For this type of scenario, it would be best to use the platform's MediaElement and transport controls.

For a list of supported audio codecs, please see: https://msdn.microsoft.com/en-us/library/windows/apps/hh986969.aspx
May 30, 2015 at 3:50 AM
ibennett wrote:
Support for MKV is actually being provided by the underlying MediaElement of the Windows 10 Media Foundation. As such, support for embedded captions would have to be provided directly by the platform and lighting up the associated transport controls in PF is not currently supported. For this type of scenario, it would be best to use the platform's MediaElement and transport controls.
That raises two separate questions. :-)

1) Is it documented how to leverage native platform support for SRT/ASS using MediaElement?
2) So if we're happy Player Framework users, and we want to be able to play both sidecar WEBVTT and embedded SRT, do we have to choose between one or the other?
For a list of supported audio codecs, please see: https://msdn.microsoft.com/en-us/library/windows/apps/hh986969.aspx
No mention of captions here, sadly.
Coordinator
Jun 1, 2015 at 1:29 PM
Edited Jun 1, 2015 at 1:34 PM
mfeingol wrote:
ibennett wrote:
Support for MKV is actually being provided by the underlying MediaElement of the Windows 10 Media Foundation. As such, support for embedded captions would have to be provided directly by the platform and lighting up the associated transport controls in PF is not currently supported. For this type of scenario, it would be best to use the platform's MediaElement and transport controls.
That raises two separate questions. :-)

1) Is it documented how to leverage native platform support for SRT/ASS using MediaElement?
2) So if we're happy Player Framework users, and we want to be able to play both sidecar WEBVTT and embedded SRT, do we have to choose between one or the other?
For a list of supported audio codecs, please see: https://msdn.microsoft.com/en-us/library/windows/apps/hh986969.aspx
No mention of captions here, sadly.
To answer your question on supported captions formats, the following formats are currently supported by the platform:

Embedded CEA-608 and CEA-708, In-Band TTML and WebVTT, Out-of-Band TTML and WebVTT.

If you are using Player Framework, you must use out-of-band WebVTT or TTML.

Let's retarget platform discussions to the following forum:

https://go.microsoft.com/fwlink/p/?linkid=535000
Aug 24, 2015 at 7:34 AM
It has seemed in the past that Microsoft has pushed developers towards using the Player Framework if they are building rich/robust streaming applications; but the release notes for Player Framework 3.0 say that "once all of the features have been included in the [Windows 10 UWA] platform, you should plan to move your media apps to use the platform’s native capabilities." Is this a shift? I just want to confirm that my team should plan to move to the native Windows 10 MediaElement in the future?
Coordinator
Aug 25, 2015 at 2:25 PM
Sparkyish wrote:
It has seemed in the past that Microsoft has pushed developers towards using the Player Framework if they are building rich/robust streaming applications; but the release notes for Player Framework 3.0 say that "once all of the features have been included in the [Windows 10 UWA] platform, you should plan to move your media apps to use the platform’s native capabilities." Is this a shift? I just want to confirm that my team should plan to move to the native Windows 10 MediaElement in the future?
Eventually most of the commonly used Player Framework functionality should be available in the Windows platform and we will continue to make investments on providing better and better playback experiences on Windows. Player Framework will probably morph into even more of a wrapper around the platform relying more and more on native functionality. We will also eventually, probably, lean more heavily on the community to innovate in this open source project.

With all of this said, I think it does make sense to shift to native functionality if and when the platform has support for the features that you need.
Aug 30, 2015 at 9:25 PM
Hi,

Your PlayReady sample is not working on Windows 10 regarding to new PlayReady DRM . Will you update your sample ?

Best regards,
Osman
Coordinator
Aug 31, 2015 at 5:01 PM
karabasosman wrote:
Hi,

Your PlayReady sample is not working on Windows 10 regarding to new PlayReady DRM . Will you update your sample ?

Best regards,
Osman
The PlayReady "sample" is not meant to be part of the samples package for Windows 10 and will be removed. For Windows 10. the PlayReady client is part of the platform. You can find details on how to make use of PlayReady in your UWP apps here:

https://msdn.microsoft.com/en-us/library/windows/apps/xaml/dn705883.aspx