jeff_rigby
Banned
Continued from this thread.
The four proposals by the FCC DSTAC for a Cable TV Downloadable Security scheme are:
1) Virtual Head end which abstracts Cable features to APIs and streams with DTCP-IP and the second proposal in this scheme is a Vidipath app (Used with Cable TV Gateways, first DVRs and then direct from a cable modem with DLNA) PDF on Sony's passage has the center and lower path page 12 with a Cable TV downloadable security scheme using Vidipath.
For the PS3 a PDF on Passage was just released at the latest FCC DSTAC (Downloadable Security Technical Advisory Committee) meeting. Page 12 has a chart showing a PS3 being used as a Vidipath STB.
Top path is RVU which the PS3 already supports.
Direct Attach End to End (center path) which is all IPTV direct from a cable modem . The future but Cable can't currently support more than a small percentage of their customers going all IPTV.
Sony is definitely supporting Vidipath, page 12 bottom path (Traditional Cable TV with the DLNA CVP2 FCC mandate where a DVR with tuners converts a RF channel to IPTV streams )
2) HTML5 <video> EME MSE ( direct IPTV from a cable modem) from the browser or an APP. An APP may be required for special features not supported by the browser. The example given was gesture control but Gesture and Voice control are or will be part of some browsers.
[HTML5 app written by the Cable company using Sony's passage and network tuners to ?emulate a Vidipath Cable TV DVR?. The Sony job posting makes more sense with this proposal
Key here with HTML5 EME MSE is that multiple DRMs could be used. Vidipath's difference is that one DRM, Playready, is used by all Vidipath platforms and that allows sharing media across all connected platforms in the home.
Second Sony Passage Paper to the FCC DSTAC is about using clear QAM tuners (USB, PC Card and Network tuners) with PCs, PS4, Phones and Tablets as the client using the DSS (Downloadable Security Scheme) (page 10 and 11). A picture of the PS3 labeled PS4 on page 11 is using a Hauppauge USB Tuner. Also on that page is a HD Homerun network tuner feeding a home WiFi router to portables.
The 2010 Leaked Xbox 720 powerpoint (XB1) has the HD Homerun listed third row down, third column from the left. These two tuners were chosen by the W3C's TV working group as standards and their control schemes will be used as the APIs for the Network and USB tuner control standards supported by W3C extensions to Javascript. HTML5 TV tuner Control will work for both Cable TV and Antenna TV.
Comcast just signed an agreement with Sony to use Passage. This plus last year's Sony Job posting for a Sony representative to help cable companies with Vidipath, Miracast and more mean it's likely soon.
After Jan 2015 Microsoft is not charging for the use of their Playready server. They would only do that if they think it would become a standard used by Cable TV. This also gives us that Microsoft knows this is coming in 2015. The current listed DTCP-IP DRM for Vidipath is WMDRM10 which is a subset of Playready versions lower than 3. Vidipath's Cable TV FCC mandate was delayed by a Tivo suit to June 2015 and it was always planned for Vidipath to be upgraded to support HEVC and OTT 4K media by 2016. WMDRM10 is not secure enough to support what content owners want for 1080P and higher resolutions like 4K; thus Playready ND and Playready ports 2.5-3 (see Playready ports below).
Vidipath was supposed to be implemented June 2014 with Playready for OTT VOD from the cloud and the subset WMDRM10 supporting 1080i and lower resolutions for in home streaming (DTCP-IP) which were the limits of Cable TV broadcast at that time. There are now two versions of Playready in home streaming 1) WMDRM10 now called WMDRM ND and 2) Playready ND. Playready can Digital bridge between the two and media can tell Playready whether it's Master quality requiring the highest DRM security to lowest (500K pixels) not requiring DRM.
It appears Playready ND and WMDRM10 ND used for DTCP-IP can coexist. This paper from Microsoft section 8 deals with DTCP WMDRM ND media being issued a Playready ND license. Section 13 sets the same "local" home networking restrictions for Playready ND that are set for WMDRM ND when used with DTCP-IP.
From Microsoft's Playready 3 site: Supporting In-Home Content Distribution with PlayReady for Network Devices page 14
In addition the PS4 and XB1 will be DVRs and media servers of 1080P and 4K blu-ray using Playready ND or side loaded media from the cloud to Playready receivers. 4K will be downscaled to 1080P for platforms that don't support 4K or Playready 3.
Sony Delays in implementing Vidipath:
The current PS4 DLNA player is a placeholder for the final DLNA player. It does not support DRM and was built as a game mode app. The reason for the PS4 DLNA delay is the wait for Playready 3, HEVC and 4K blu-ray standards to be released. The reason the PS3 hasn't received any visible update to features is nearly the same; a wait for Playready, HTML5 <Video> ME (C-ENC format), HEVC and other standards to evolve. All these are part of what's required for Vidipath.
Sony's Playstation APPs are built with webkit native libraries and webkit and are called WebMAF. It was originally Firefox/Mozilla using Gnome native libraries but a Geko engine. A version of WebMAF using webkit instead of Geko was developed in 2009 and this is what Sony uses since 2012 when they ported Webkit to the PS3 and Vita. Since HTML5 <video> ME hadn't yet been created, Sony created Trilithium in 2008 which is the video player (assumption is that it uses the same APIs as Gstreamer) and some pixel/window frame manipulation routines seen in the PS3 XMB. Combining C++, WebMAF/Webkit and Trilithium allows Sony to create IPTV Apps. Trilithium has to be retired in favor of HTML5 <video> ME (embedded Playready with C-ENC format) and maybe WebGL. ALL IPTV apps on the PS3 created in 2012 have not been updated since 2012. Spotify is a WebMAF app just released a few months ago to the PS3 and it's a WEBMAF app without Video...which seems to indicate that DRM and Video player are the holdouts for updating IPTV apps on the PS3.
Playready ports:
Playready Porting has several versions based on the underlying security scheme with the higher being more secure as seen in the chart below. All versions of Playready stream and negotiate keys in the same manner but Playready knows higher porting versions like "3" are more secure and content owners of 4K media may require 3. The XB1 and PS4 support TEE level (Playready 3) DRM required for 4K media including the HDMI chip's HDCP with the PS4 supporting all ARM recommendations allowing on-line transaction support.
The PS3 did/does not have embedded playready support; it's currently being ported to the PS3. The purple block on the left represents Playready support provided by the player; I.E. Netflix would have playready in the app software. The next block labeled 2.5 has embedded Playready with various levels of support/security which the PS3 should support. The next to last is probably Intel which has it's own version of a security processor. The one on the far right is ARM TEE level DRM which is supported by all AMD's APUs and I think all ARM phones and tablets since sometime after 2006. The XB1 and PS4 have ARM blocks managed by a ARM trustzone processor in the APU and Southbridge respectively using Xtensa stream processors for Codecs and more.
Supporting In-Home Content Distribution with PlayReady for Network Devices
Xbox 360 and PS3 are now DLNA 1.5
Vidipath STBs are DLNA 2.0 and Playready porting kit 2.5
PS3 is getting Playready porting kit 2.5 which just leaves HTML5 and DLNA firmware updates to be a Vidipath STB
DLNA® Announces 3.0 Certification Program and Updated Guidelines includes HEVC
It appears the XB1 and likely the PS4 will be DLNA 3.0 and Playready porting kit 3.0 Notice the 3.0 The porting kit is directly tied to the type of embedded hardware supporting DRM. It in turn reports to Playready and Playready ND the robust level of DRM security it can support, the higher the better with 3.0 required for 4K media and DLNA 3.0 having HEVC support for 4K media.
Timing:
Sony Vaio Computers with Window 8.1 will get firmware updates to support Windows 10 with Playready 3.0 October 2015 and Windows 8.0 computers will get firmware updates to support Windows 10 November 2015. These release dates must be tied to a Microsoft roadmap which should also apply to embedded platforms like the PS4 and XB1.
1080P version from a newly Remastered 4K blu-ray of Spartacus will arrive on October 6th in the US. 4K version likely in 2016
The Fifth Element and Léon The Professional will both be released with a 1080P image from a new 4K remaster and will feature a newly mixed Dolby Atmos soundtrack. They will be available on October 27th. 4K version likely in 2016
The four proposals by the FCC DSTAC for a Cable TV Downloadable Security scheme are:
1) Virtual Head end which abstracts Cable features to APIs and streams with DTCP-IP and the second proposal in this scheme is a Vidipath app (Used with Cable TV Gateways, first DVRs and then direct from a cable modem with DLNA) PDF on Sony's passage has the center and lower path page 12 with a Cable TV downloadable security scheme using Vidipath.
For the PS3 a PDF on Passage was just released at the latest FCC DSTAC (Downloadable Security Technical Advisory Committee) meeting. Page 12 has a chart showing a PS3 being used as a Vidipath STB.
Top path is RVU which the PS3 already supports.
Direct Attach End to End (center path) which is all IPTV direct from a cable modem . The future but Cable can't currently support more than a small percentage of their customers going all IPTV.
Sony is definitely supporting Vidipath, page 12 bottom path (Traditional Cable TV with the DLNA CVP2 FCC mandate where a DVR with tuners converts a RF channel to IPTV streams )
2) HTML5 <video> EME MSE ( direct IPTV from a cable modem) from the browser or an APP. An APP may be required for special features not supported by the browser. The example given was gesture control but Gesture and Voice control are or will be part of some browsers.
[HTML5 app written by the Cable company using Sony's passage and network tuners to ?emulate a Vidipath Cable TV DVR?. The Sony job posting makes more sense with this proposal
http://www.cablelabs.com/downloadable-security-and-the-future-of-cablecards/ said:
Key here with HTML5 EME MSE is that multiple DRMs could be used. Vidipath's difference is that one DRM, Playready, is used by all Vidipath platforms and that allows sharing media across all connected platforms in the home.
Second Sony Passage Paper to the FCC DSTAC is about using clear QAM tuners (USB, PC Card and Network tuners) with PCs, PS4, Phones and Tablets as the client using the DSS (Downloadable Security Scheme) (page 10 and 11). A picture of the PS3 labeled PS4 on page 11 is using a Hauppauge USB Tuner. Also on that page is a HD Homerun network tuner feeding a home WiFi router to portables.
The 2010 Leaked Xbox 720 powerpoint (XB1) has the HD Homerun listed third row down, third column from the left. These two tuners were chosen by the W3C's TV working group as standards and their control schemes will be used as the APIs for the Network and USB tuner control standards supported by W3C extensions to Javascript. HTML5 TV tuner Control will work for both Cable TV and Antenna TV.
Comcast just signed an agreement with Sony to use Passage. This plus last year's Sony Job posting for a Sony representative to help cable companies with Vidipath, Miracast and more mean it's likely soon.
After Jan 2015 Microsoft is not charging for the use of their Playready server. They would only do that if they think it would become a standard used by Cable TV. This also gives us that Microsoft knows this is coming in 2015. The current listed DTCP-IP DRM for Vidipath is WMDRM10 which is a subset of Playready versions lower than 3. Vidipath's Cable TV FCC mandate was delayed by a Tivo suit to June 2015 and it was always planned for Vidipath to be upgraded to support HEVC and OTT 4K media by 2016. WMDRM10 is not secure enough to support what content owners want for 1080P and higher resolutions like 4K; thus Playready ND and Playready ports 2.5-3 (see Playready ports below).
Vidipath was supposed to be implemented June 2014 with Playready for OTT VOD from the cloud and the subset WMDRM10 supporting 1080i and lower resolutions for in home streaming (DTCP-IP) which were the limits of Cable TV broadcast at that time. There are now two versions of Playready in home streaming 1) WMDRM10 now called WMDRM ND and 2) Playready ND. Playready can Digital bridge between the two and media can tell Playready whether it's Master quality requiring the highest DRM security to lowest (500K pixels) not requiring DRM.
It appears Playready ND and WMDRM10 ND used for DTCP-IP can coexist. This paper from Microsoft section 8 deals with DTCP WMDRM ND media being issued a Playready ND license. Section 13 sets the same "local" home networking restrictions for Playready ND that are set for WMDRM ND when used with DTCP-IP.
From Microsoft's Playready 3 site: Supporting In-Home Content Distribution with PlayReady for Network Devices page 14
This outlines a model similar to Vidipath except using Playready ND instead of WMDRM10 and confirms the XB1 and PS4 will be streaming 4K media in the home (from Cable TV and OTT) and supports both as 4K blu-ray players with digital bridge.
http://www.cepro.com/article/fox_home_entertainment_proposes_blu-ray_movie_servers_as_uhd_digital_bridge/ said:
In addition the PS4 and XB1 will be DVRs and media servers of 1080P and 4K blu-ray using Playready ND or side loaded media from the cloud to Playready receivers. 4K will be downscaled to 1080P for platforms that don't support 4K or Playready 3.
Sony Delays in implementing Vidipath:
The current PS4 DLNA player is a placeholder for the final DLNA player. It does not support DRM and was built as a game mode app. The reason for the PS4 DLNA delay is the wait for Playready 3, HEVC and 4K blu-ray standards to be released. The reason the PS3 hasn't received any visible update to features is nearly the same; a wait for Playready, HTML5 <Video> ME (C-ENC format), HEVC and other standards to evolve. All these are part of what's required for Vidipath.
Sony's Playstation APPs are built with webkit native libraries and webkit and are called WebMAF. It was originally Firefox/Mozilla using Gnome native libraries but a Geko engine. A version of WebMAF using webkit instead of Geko was developed in 2009 and this is what Sony uses since 2012 when they ported Webkit to the PS3 and Vita. Since HTML5 <video> ME hadn't yet been created, Sony created Trilithium in 2008 which is the video player (assumption is that it uses the same APIs as Gstreamer) and some pixel/window frame manipulation routines seen in the PS3 XMB. Combining C++, WebMAF/Webkit and Trilithium allows Sony to create IPTV Apps. Trilithium has to be retired in favor of HTML5 <video> ME (embedded Playready with C-ENC format) and maybe WebGL. ALL IPTV apps on the PS3 created in 2012 have not been updated since 2012. Spotify is a WebMAF app just released a few months ago to the PS3 and it's a WEBMAF app without Video...which seems to indicate that DRM and Video player are the holdouts for updating IPTV apps on the PS3.
Playready ports:
Playready Porting has several versions based on the underlying security scheme with the higher being more secure as seen in the chart below. All versions of Playready stream and negotiate keys in the same manner but Playready knows higher porting versions like "3" are more secure and content owners of 4K media may require 3. The XB1 and PS4 support TEE level (Playready 3) DRM required for 4K media including the HDMI chip's HDCP with the PS4 supporting all ARM recommendations allowing on-line transaction support.
The PS3 did/does not have embedded playready support; it's currently being ported to the PS3. The purple block on the left represents Playready support provided by the player; I.E. Netflix would have playready in the app software. The next block labeled 2.5 has embedded Playready with various levels of support/security which the PS3 should support. The next to last is probably Intel which has it's own version of a security processor. The one on the far right is ARM TEE level DRM which is supported by all AMD's APUs and I think all ARM phones and tablets since sometime after 2006. The XB1 and PS4 have ARM blocks managed by a ARM trustzone processor in the APU and Southbridge respectively using Xtensa stream processors for Codecs and more.
Supporting In-Home Content Distribution with PlayReady for Network Devices
Xbox 360 and PS3 are now DLNA 1.5
Vidipath STBs are DLNA 2.0 and Playready porting kit 2.5
PS3 is getting Playready porting kit 2.5 which just leaves HTML5 and DLNA firmware updates to be a Vidipath STB
DLNA® Announces 3.0 Certification Program and Updated Guidelines includes HEVC
It appears the XB1 and likely the PS4 will be DLNA 3.0 and Playready porting kit 3.0 Notice the 3.0 The porting kit is directly tied to the type of embedded hardware supporting DRM. It in turn reports to Playready and Playready ND the robust level of DRM security it can support, the higher the better with 3.0 required for 4K media and DLNA 3.0 having HEVC support for 4K media.
Timing:
Sony Vaio Computers with Window 8.1 will get firmware updates to support Windows 10 with Playready 3.0 October 2015 and Windows 8.0 computers will get firmware updates to support Windows 10 November 2015. These release dates must be tied to a Microsoft roadmap which should also apply to embedded platforms like the PS4 and XB1.
1080P version from a newly Remastered 4K blu-ray of Spartacus will arrive on October 6th in the US. 4K version likely in 2016
The Fifth Element and Léon The Professional will both be released with a 1080P image from a new 4K remaster and will feature a newly mixed Dolby Atmos soundtrack. They will be available on October 27th. 4K version likely in 2016
