deramat fadila natthaniuel
Xena Donovan
I built a PC yesterday with the Asrock J5005-ITX motherboard. It's advertised as having HDMI 2.0 and supporting 4k @ 60hrz. This is true but I can't seem to get 4k for Netflix. I've updated Windows 10 and all of my drivers. Also, I installed HEVC video Extension from Device Manufactures but I still can't get it to works. I'm getting this error message in the netflix app: Error code: U7361-1255-C00D7159. I just wanted to know if this CPU supports 4k / UHD Netflix.
So did you guys get the Asrock J5005 to stream Netflix in 4K. I downloaded and updated my BIOS to 1.30 and I still can't get it to stream Netflix in 4K. Did you need to use the Microsoft HEVC video extension. Also I was only able to do the BIOS update by the instant flash. Shorting the TXE pins did not work for me. Any help would be appreciated.
Thank you but it still doesn't work for me. I have a LG OLED B7 and I tried all the HDMI ports but I can only stream Netflix in 1080p. Netflix will stream in 4K when I use the app on my TV but the app on the computer can only stream in 1080p. There
Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.
I have a Roku Ultra 4802RW, and am able to receive Dolby Atmos when watching Apple TV+ and Amazon Prime, but cannot receive when watching Netflix or Disney Plus. For Netflix / Disney+, I do not see Dolby Atmos in any of the descriptions (and have the Netflix Premium package), only 5.1.
Netflix customer service pointed me to Roku, and Roku customer service created a ticket and never responded.. I feel like my system set-up is correct, since Atmos is playing on multiple services, so I'm not sure what's wrong. Any ideas on how to resolve?
@Namarillo The 4801 will passthrough Dolby Atmos if it's available. But your issue might be the content. Amazon has very little Atmos content, regardless of the player used. I get Atmos with no issue on my Ultra 4800 on Disney, but I am connected directly to my Yamaha AVR, not passing through the TV.
You didn't mention if the Apple TV+ and MAX were using the TV's internal apps or from your Roku. If they were the TV apps, be aware that some TVs might not passthrough DD+ (which is what is used for online Atmos streaming) from an externally connected device, such as your Roku. I would expect a TV that supports eARC to not have that restriction, but one never knows.
You can generally look at the details of a piece of content for an audio description such as "5.1", "Dolby Digital Plus 5.1", "Dolby Surround", or "Dolby Atmos". If the content does not specifically say it includes a surround sound format, then it likely does not.
In the Netflix app, shows and movies that should be available in Dolby Atmos (per the Dolby.com website and other websites), like The Irishman, Ozark, Mank, Roma, etc.. all show 5.1. Not a single movie or show has the Atmos designation in Netflix. The same with Disney Plus - Get Back, The Little Mermaid, etc.. only show 5.1, even though the dolby and disney sites say it's available in Atmos. For some reason, those 2 apps on Roku do not recognize that my system is Atmos enabled.
@Sean6 I have my Ultra 4800 connected to a Yamaha AVR and an LG Nano85 display. I don't use Netflix, but for Disney+ I tried two different titles. One was the latest Indiana Jones movie and the other was The Little Mermaid (animated version, not the new live one). Both displayed Atmos on my AVR and the display switched to Dolby Vision. I can't say why you're not getting Atmos on these services but it's working elsewhere. But the Ultra 480x models do support Atmos in both Netflix (I've used it in the past and seen Atmos) and Disney+.
Will you be able to look into this issue further? As stated, within Netflix, shows that should have the Atmos designation do not show this. I was to see the Atmos designation on shows when I connected my Roku output to my Denon 2800 receiver, but since I'm using Sonos (instead of speakers connected through the receiver), it downgrades the audio output.
I have my Roku connected by HDMI to a TCL P735 and this with HDMI by eARC to a Bose Soundbar 700. Applications like Apple TV+ and HBOMax work well and the audio output verified on the bar is Dolby Digital 5.1, but channels like Disney + or Amazon Prime Video only gives PCM 2.0.
I've tried changing the Roku to a Samsung QN85A and a Bose Soundbar 900 and the result is the same, Dolby Digital 5.1 on Apple and HBOMax and PCM 2.0 on Disney and Prime Video.
Now as a point-of-note., you will need to Search the Microsoft Store for "HEVC Video Extensions from the Device Manufacturer" as well as the "HEVC Video Extensions"., as both of these will be needed.
IF this doesn't enable Netflix HDR (which honestly I don't recall if it does or doesn't., as I run a Native 12bit Desktop that somewhat makes the difference to HDR10 fairly 'Minimal' without being on a WCG Display, such-as Quantum Colour from Samsung) then it's likely because they're just using the Intel and NVIDIA Codec SDKs as opposed to simply supporting the Native Format.
This is likely the case, and so I'd strongly recommend that you suggest to Netflix that they support the AMD AMF (Advanced Media Framework) SDK from GPUOpen that provides extensive support for Video Codecs across all UVD and VCE Devices., which as a note is Radeon HD 5000 or newer)
We're now in 2019 with still no way of playing Netflix in 4K on a Vega-card. I was hoping that adding support for mobile Vega in the drivers, and the release of the Radeon VII would have changed it for the better, but alas...
(which is great if you're Display also supports the DTB Standard for HDR/WCG, as opposed to just Natively providing such... there's another thread about this on the Radeon Pro Series GPU... the issue with such is Half AMD and Half Microsoft fault., which given neither of them seem to talk to each other directly is infuriating, to say the least)
Sure, they have their Workstation (Radeon Pro) Hardware ... but they don't really have any Prosumer Hardware., not unless you count the Radeon VII, which is in such short supply it might as well be Faery Dust.
Look at it this way, Navigation is "Pretty" but not very Intuitive... there's a basic Blog-Style Comments Section, but no real way to properly discuss with other Developers outside of coming on the forums (which again aren't exactly intuitive) or discussing directly on GitHub.
Intel and NVIDIA both have these... I mean they're bare bones, unlike Microsofts' which are frankly the Gold Standard for such; but AMD literally has NONE. You get the Source Code, and maybe a few Samples; beyond that, well it's basically "Figure it out on your own"., which is fine for Developers like myself who are going to extensively use and alter the source in order to have a fully-custom variant of their Open Source API / Libraries in our Projects; but for those who just want to "Plug-and-Play" Support., yeah; that's a BAD approach.
Getting back to how infrequently said Update appear., well again the issue here is that there's basically no reason for Developers to keep it bookmarked or keep coming back to the site (which is as a note NO LONGER listed in the Developer.AMD.com area of their Website, so now it just looks like AMD simply no longer have any GPU SDK / Libraries / Tools, heck all of the things listed on the Developer area of their Website are basically Linux SDK / Buildchain Tools for the AMD64 Platform; that's basically it).
Where-as what you want are Developers constantly coming back, not just for Regular SDK / Library / Tool Updates; but also for Whitepapers, Blog Posts on "Best Practises", etc. You want a community to engage with your Products, well you HAVE to engage with that Community to showcase that you haven't abandoned them... it's a two-way street.
The same was true in regards to how, they've STILL not updated their Entire Litany of Tools / Libraries / API to use DirectX 12., let alone any Vulkan versions... yet all of the "Optimisation" Blogs they've put out have been focused on Vulkan, none for DirectX 12 (yes, I know they're basically very similar; but it doesn't hurt to list it as DirectX 12 / Vulkan with little nodes to the differences); and well we're also talking about their GCN Architecture being better suited to the Low-Level APUs., so WHY?! wasn't everything DirectX 12 to begin with, THEN later supporting DirectX 11.2/11.3/11.4?
90f70e40cf