jeff_rigby
Banned
This is just confirming what we already should know since the choice to use Playready by all US CE platforms was decided sometime in 2011 when Sony announced they were to use Playready and Playready was chosen as the common DRM to be used by all Cable companies to support DLNA CVP2 = Vidipath = RUI (Playready and WMDRM10 which is a subset of Playready for DTCP-IP). Anyone who wishes to become part of the DLNA CVP2 ecosystem must use Playready DRM.
Sony Job posting 10/31/2014 Principal Engineer specializing in PlayReady
"enhance the implementation and support integration."
DRM in HTML5 <video>ME and modern IPTV apps have three parts: 1) at the lowest level embedded routines only the platform holder knows which include the codec, hidden keys and Metadata routines the player must run under. 2) Middle ware ( Microsoft describes this as a thin C++ layer) that exposes the C-ENC (Common Encryption) APIs to Javascript for the HTML5 <video> ME (Media Extensions) and to the 3) Playready DRM in IPTV apps . The DRM Middleware and Playready routines in apps are routinely changed to keep them secure but the embedded routines usually stay the same and every effort is used to keep them secure by the platform owner.
So PS4 Middleware (nearly done) and embedded routines are likely done (had to wait till the Xtensa DPU routines were in place with I think Firmware 2.0 if this thread is accurate) but the full DRM scheme is not finished . In any case DLNA CVP2 certification comes after Playready and WMDRM10 DRM are in place. Since Vita got DLNA support it likely is further along and has Playready Middleware and embedded routines finished.
The PS4 and XB1 as media hubs will be special cases as they can Playready sideload and stream inside the home using DTCP-IP and likely stream outside the home using Playready. This will use the Encoder that Share 2.0 exposes for games.
A significant OS change is coming for Playstation platforms PS3, PS4 and Vita with all current IPTV apps not using the Playstation software stacks for DRM except possibly Sony apps. Edit: Apparently DRMtoday has the PS4 supporting Marlin and Playready, Sony using Marlin till Playready is ready and/or Marlin will be used in China, Korea and Japan?
In the PS4 it means all IPTV apps were/are X-86 and didn't use the DPU codecs and Trustzone processor. DLNA should be a low power app and not use the X-86 CPUs or AMD GPU, same for the blu-ray player and IPTV apps as well as DLNA CVP2 which additionally should use a second low power GPU for the UI which Xtensa DPUs can support. This is the reason for the PS4's unexpectedly high power use, same for the XB1. They are both at nearly the same state for Players, codecs and DRM.
In the PS3 it means all the DTCP-IP DRM routines tied to the DLNA player and DRM for the IPTV player are being changed. To reduce the OS size and insure DRM the DLNA player, HTML5 player and blu-ray-DVD player should be the same using the same Metadata rules and DRM. It's not clear when or if this has already been done. Edit: According to DRM today; the PS3 is still using Marlin which means a significant firmware update to the PS3 is coming or DRM today is out of date.
If DRMtoday is accurate the coming firmware update should have DLNA and HTML5 updates to support DLNA CVP2. For DLNA it means the three box model with the PS3 able to be controlled by a second screen DLNA controller. The PS3 XMB may be updated to a openGL desktop like the PS4 (my prediction since late 2011) or the DLNA CVP2 app and browser only will support OpenGL.
• Keeping implementation on target to meet a tight schedule
• Supporting the integration of software components with client applications being designed and implemented on parallel schedules
"Tight schedule and parallel schedules" = Getting close to a roadmap deadline yeah!
Sony Job posting 10/31/2014 Principal Engineer specializing in PlayReady
The primary role involves securing a well-known DRM solution to be used on PLAYSTATION®3, PlayStation®4 and PSVita™ for multimedia applications. You will be part of a small team composed of other software engineers based in London. You will work with this team to enhance the implementation and support integration. This is a contract role with the possibility to extend its duration.
Responsibilities
• Porting and securing of software components on multiple platforms such as PLAYSTATION®3, PlayStation®4 and PSVita™.
• Keeping implementation on target to meet a tight schedule
• Supporting the integration of software components with client applications being designed and implemented on parallel schedules
"enhance the implementation and support integration."
DRM in HTML5 <video>ME and modern IPTV apps have three parts: 1) at the lowest level embedded routines only the platform holder knows which include the codec, hidden keys and Metadata routines the player must run under. 2) Middle ware ( Microsoft describes this as a thin C++ layer) that exposes the C-ENC (Common Encryption) APIs to Javascript for the HTML5 <video> ME (Media Extensions) and to the 3) Playready DRM in IPTV apps . The DRM Middleware and Playready routines in apps are routinely changed to keep them secure but the embedded routines usually stay the same and every effort is used to keep them secure by the platform owner.
So PS4 Middleware (nearly done) and embedded routines are likely done (had to wait till the Xtensa DPU routines were in place with I think Firmware 2.0 if this thread is accurate) but the full DRM scheme is not finished . In any case DLNA CVP2 certification comes after Playready and WMDRM10 DRM are in place. Since Vita got DLNA support it likely is further along and has Playready Middleware and embedded routines finished.
The PS4 and XB1 as media hubs will be special cases as they can Playready sideload and stream inside the home using DTCP-IP and likely stream outside the home using Playready. This will use the Encoder that Share 2.0 exposes for games.
A significant OS change is coming for Playstation platforms PS3, PS4 and Vita with all current IPTV apps not using the Playstation software stacks for DRM except possibly Sony apps. Edit: Apparently DRMtoday has the PS4 supporting Marlin and Playready, Sony using Marlin till Playready is ready and/or Marlin will be used in China, Korea and Japan?
In the PS4 it means all IPTV apps were/are X-86 and didn't use the DPU codecs and Trustzone processor. DLNA should be a low power app and not use the X-86 CPUs or AMD GPU, same for the blu-ray player and IPTV apps as well as DLNA CVP2 which additionally should use a second low power GPU for the UI which Xtensa DPUs can support. This is the reason for the PS4's unexpectedly high power use, same for the XB1. They are both at nearly the same state for Players, codecs and DRM.
In the PS3 it means all the DTCP-IP DRM routines tied to the DLNA player and DRM for the IPTV player are being changed. To reduce the OS size and insure DRM the DLNA player, HTML5 player and blu-ray-DVD player should be the same using the same Metadata rules and DRM. It's not clear when or if this has already been done. Edit: According to DRM today; the PS3 is still using Marlin which means a significant firmware update to the PS3 is coming or DRM today is out of date.
If DRMtoday is accurate the coming firmware update should have DLNA and HTML5 updates to support DLNA CVP2. For DLNA it means the three box model with the PS3 able to be controlled by a second screen DLNA controller. The PS3 XMB may be updated to a openGL desktop like the PS4 (my prediction since late 2011) or the DLNA CVP2 app and browser only will support OpenGL.
• Keeping implementation on target to meet a tight schedule
• Supporting the integration of software components with client applications being designed and implemented on parallel schedules
"Tight schedule and parallel schedules" = Getting close to a roadmap deadline yeah!