Announcement: Our new CyberLink Feedback Forum has arrived! Please transfer to our new forum to provide your feedback or to start a new discussion. The content on this CyberLink Community forum is now read only, but will continue to be available as a user resource. Thanks!
CyberLink Community Forum
where the experts meet
| Advanced Search >
Quote So I guess it is safe to say that I am out of luck if I want to play 4K on an AMD rig huh?

I need to see if I can get a refund then! Ridiculous! I have the latest AMD Threadripper chipset, AND complicating matters, a GTX 1080 GPU that doesn't appear to be supported either!

Appreciate the information from this thread everyone...


Pretty much. Cyberlink's response was more or less it's Nvidia's problem if they don't support Intel's proprietary instruction set and why should we care... It's all a bit lazy, as Netflix was clearly able to negotiate an agreement to support 4k on Nvidia hardware.

If you do go down the Intel route, bear in mind that your mobo must have HDMI 2.0 (good luck finding that info). It's probably less hassle to buy a cheap 4k player and use that instead.

And Cyberlink, however much you spam me I will not be upgrading to PDVD18 until you fix this!
If you follow that logic through, uhd bluray isn't viable on pc...
Quote Hello,
So many people keep making this assumption, that it is just about HDCP 2.2. The DRM protection for UHD BDs is different and more complex, because it is a different media format and technology, one that is known for being compromised, i.e. ripping. The UHD BD playback on a PC requires CPU level content protection, on top of the HDCP 2.2 for the output connections. An extra level of DRM protection in the hardware. It isn't CyberLink that created that security requirement, by the way.

FYI, PowerDVD already supports the same HDR video playback over HDCP 2.2 that Netflix does: https://www.cyberlink.com/support/product-faq-content.do?id=21821&prodId=1&prodVerId=-1&CategoryId=-1&keyword=hdr

Dave


I think it's more about PlayReady 3.0 support than hdcp2.2. As I understand it, you need a combination of an end to end hdcp2.2 handshake and PlayReady 3.0 hardware drm. Intel's implementation of PlayReady 3 is SGX (built into Kaby Lake onwards), which is supported by PowerDVD. However, AMD and Nvidia also have their own implementations (SME for Ryzen), which haven't made it into PowerDVD yet.
Quote


It sounds like NVIDIA/AMD supports Netflix 4K, and then they of course support 4K blu-ray.
Then, powerdvd cannot use NVIDIA/AMD GPU, it is powerdvd's responsibility.

Why would you think Netflix 4K is identical to 4K blu-movie disc specification?
One is online video streaming with its DRM, another one is local movie disc playback and has its DRM.
Yes, they both apply HDCP 2.2. So, that's everything?

Per your statement, Netflix streaming (playback app/service) should support NVIDIA/AMD GPUs at the begining or later after Netflix updates their 4K video streaming mechanism on Netflix side.

Why all those news or annoucement reversely said NVIDIA/AMD GPU supports Netflix streaming by new drivers? http://nvidia.custhelp.com/app/answers/detail/a_id/4583/~/4k-uhd-netflix-content-on-nvidia-gpus
https://www.theinquirer.net/inquirer/news/3031654/amds-latest-radeon-adrenalin-edition-drivers-quietly-bring-in-4k-netflix-streaming-support
http://www.hexus.net/ce/news/audio-visual/117782-amd-adds-netflix-4k-acceleration-latest-driver-release/


My point is simply that either: (1) Intel's SGX drm scheme is baked into UHD bluray on PC and other brands are locked out; or (2) further work is needed to support AMD and Nvidia's implementations of PlayReady 3.0. It would be helpful to have some clarity from Cyberlink either way, as PlayReady 3.0 is the scheme MS devised to bring 4k content to the pc. If the goalposts have moved, it will massively impact on building choices, as SGX doesn't play nicely with other GPUs and you may be better off buying a standalone player.
Quote If I found it obvious, I wouldn't have asked. Despite their priorities, NVidia has to listen to their customers to some extent, and to that extent, I would like my voice heard on this issue. Accoridngly, could you (or someone else knowledgeable), tell me what I should say to them? Is it as simple as asking for playthrough support for UHD BDs, or should I be asking for support for more specific technological demands for this type of playback?

Thanks


I'm not convinced that Nvidia's the problem. You can stream UHD Netflix with Nvidia and AMD now, but Cyberlink still only supports Intel's drm solution for UHD bluray.
Quote Hello,

No, NVIDIA cards do not support UHD playback yet. It is not "locked out" as you suggest though. See this thread and join his voice to make the request.

https://forum.cyberlink.com/forum/posts/list/76081.page

Dave


Has Cyberlink ever confirmed that the problem is at Nvidia's end? The reason I ask is Nvidia and AMD both support UHD playback on Netflix over hdcp 2.2. My understanding is that Cyberlink only supports Intel's SGX hardware, drm for uhd, so it seems a little odd to ask Nvidia and AMD to add Intel's proprietary solution when both brands have their own similar solution and this is clearly acceptable to the big studios...
Hi all

Can anyone confirm whether I'll be able to play UHD blu-rays with an AMD Ryzen 1700 and a GTX 1080? It looks like it's still locked down to Intel hardware, which seems a bit bonkers in this day and age...

Thanks!
It's not an option in PowerDVD, for the reasons nullack mentioned. Media companies came down very heavily on the maker of a well known DVD decryption software last year, so I can't see Cyberlink touching this with a bargepole.
I can't speak for PowerDVD 15, but I have this in PowerDVD 14 with all DVDs and blu-rays (playing from disc). The volume jumps up to 100% immediately (in PowerDVD and in the Windows volume settings), but output volume doesn't increase dramatically. I keep my windows volume at about 30% normally, so it's a big problem if I forget to turn it back down on exit.

This is using RCA output on a Xonar STX in WASAPI mode.
Go to:   
Powered by JForum 2.1.8 © JForum Team