Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
pretty sure thats right:Right. I don't think this is going to work with TVs and dv gaming. I think something is missing like having to be a validated dv pc to work with certain monitors.
pretty sure thats right:
View attachment 728802
View attachment 728803
just like my amp supports VRR but not freesync/gsync
we're combining two different ecosystems...
to make it work with my setup i have vid to the tv via hdmi and then audio to the amp via dp>hdmi. no cert on the amp so they will not engage but it works with consoles.That is odd. Gsync at least should be VRR compatible. Alternatively use eARC for audio, then the whole VRR compatibility should not even matter.
it allows windows to feed it the right hdr/dv profiles. yeah you get hdr but you wont get DV unless setup correctly AND with the right equipment. windows DV is supposed to work now(on insider) but i cant get it working...I'm not clear on what the HDR certification info actually does. My LG C8 has always shown "not found" but worked fine in HDR (gaming and desktop).
lol wouldnt that be nice ehIt would be better if Microsoft fixed gamma of SDR desktop so no profiles are needed.
did it, now it says my tv is certified but still trying to figure how to get it to work, everything still just says hdr10. (though there are posts say that may be normal)https://github.com/balu100/dolby-vision-for-windows
Haven't tried this, but I'm gonna keep an eye on it for the update once the new Windows feature goes live.
Hey, that's how I got it to work...yeah, if you want DV to "just work", its a tv, blu-ray player and an avr. DO NOT add a PC into the mix...
ive been fucking with my setup since before xmas...
been playing with it; still cant get it working but if i enable hdr, netflix (in edge browser) now shows DV but the color is all f'd up.
on a side note, while trying to fix this i got my atmos working in browser finally. used dell's oem Dolby Access app and license package to install the app and now it works! (bought license, never worked and app wouldnt install)
I give three shits. To get it working in gaming, and frankly that's all I would give a shit about, is impossible. So this update does nothing. I wanted to use dv on my pc for gaming only and it does not work. Oh well. I'll push out my three shits in the bowl tonight.
HDFury devices can allow you to play Dolby Vision content on a Samsung TV. Specifically, HDFury devices can be used to output Dolby Vision content as LLDV (Low Latency Dolby Vision), which can then be displayed on the Samsung TV as HDR10, according to a Zidoo forum thread. While Samsung TVs don't natively support Dolby Vision, HDFury devices can effectively trick the TV into displaying Dolby Vision content using this method.
Elaboration:
- HDFury and LLDV:
HDFury devices, such as the Vertex 2, can be configured to output Dolby Vision content as LLDV. This is a specific profile of Dolby Vision that is designed to be displayed on HDR10-compatible TVs.- EDID Manipulation:
The HDFury device uses EDID (Extended Display Identification Data) manipulation to tell the Samsung TV that the incoming signal is HDR10, even though it's actually LLDV.- Improved Picture Quality:
While HDR10 is the standard for Samsung TVs, LLDV can provide a slightly better picture quality due to its dynamic tone mapping capabilities, which HDR10 lacks, according to a Reddit user.- Alternatives:
If you have an AVR (Audio Video Receiver) that supports HDR10+, an HDFury device might not be necessary, according to a Reddit user.- No Guarantee:
It's important to note that HDFury devices can be finicky, and not all HDMI cables are compatible, according to a Reddit user.- Licensing Issues:
Samsung's choice to use HDR10+ instead of Dolby Vision is primarily due to licensing fees associated with Dolby Vision, according to a video on YouTube.
Dune HD players do support Dolby Vision, including both MEL (Minimum Enhancement Layer) and FEL (Full Enhancement Layer) profiles. However, it's possible that the issue is with specific file formats or configurations within your Dune player.
Here's a more detailed explanation:
Dune HD players are known for their extensive media format support, including Dolby Vision.
Both MEL and FEL profiles are part of Dolby Vision, and Dune players support them.
Ensure the Dolby Vision content you are trying to play is in a supported file format (e.g., MKV, MP4, TS, M2TS, ISO, or movie folder structure).
Verify that your HDMI settings on your TV and Dune player are configured correctly to support Dolby Vision. Some TVs require specific HDMI formats or settings to enable Dolby Vision.
Ensure your TV supports Dolby Vision and is correctly configured to recognize and display it.
Check for and install any available software updates for your Dune player, as updates can include bug fixes and compatibility improvements.
Dune HD players extract and transmit the Dolby Vision RPU (Render Processing Unit) metadata to your TV, ensuring proper Dolby Vision picture quality.
Dolby FEL (Full Enhancement Layer) does not require an internet connection. It's a feature used in physical disc releases of Dolby Vision content, specifically profile 7, and is applied locally on the disc. Streaming services do not utilize either FEL or MEL. While streaming services do use Dolby Vision, they don't employ these enhancement layers
Streaming services commonly use Dolby Vision Profile 5. This profile is tailored for streaming and uses Dolby's proprietary IPT color space and dynamic metadata (RPU) to enhance color, brightness, and contrast. Major platforms like Netflix, Disney+, and Amazon Prime Video use this version of Dolby Vision to deliver HDR content to their subscribers. Dolby Vision Profile 7 is a more advanced version found on physical media like 4K Blu-rays, requiring specialized equipment.
Yeah, the different profiles are what trips up DV playback on some devices. Shield Pro is one of the few streaming devices that can handle Profile 7, afaik.
Streaming services tend to offer Dolby Vision with an HDR compatibility layer, allowing it to fallback to regular HDR for non-DV devices. I'm not clear on if this format really offers any advantages over regular HDR. Some services like Disney also seem to offer a DV version without the HDR compatibility layer. I've noticed that this version tends to be higher bitrate than the version with the HDR compatibility layer. For example, episode 11 of Andor season 2 is 15.2 Mb/s video on the DV stream w/o the HDR compatibility layer. Version with the compatibility layer is 11.1 Mb/s.
"The Shield lacks a secondary video decoder to process the second layer on profile 7 videos, so it will only apply the dynamic metadata onto the base layer. For many movies out there, this is fine as the secondary layer contains no extra information (MEL). But for the ones that have residue video information on the secondary layer (FEL), this information is ignored on the Shield"
The shield is capable to play Dolby Vision profile 7. It just discards the FEL (Full Enhancement Layer). To explain it: Dolby Vision Profile 7 has 3 layers. The Base Layer (BL) plays just fine on the shield, its like a HDR10 fallback. Then it also has a enhancement layer (EL), this can be either FEL or MEL (full/minimal) enhancement layer. This part has additional information that enhances the quality. It also has RPU (Reference Processing Unit), this part makes sure that the BL and the EL layer are matching with each other.
The Shield ignores the EL and RPU and just plays the BL layer, which gives less quality.
If you let the dolby vision profile 7 on the shield be live converted to dolby vision profile 8.1, you won't get the FEL layer with the most important information. It will extract the HDR10 base layer (BL) and merges it with the RPU metadata to create a Profile 8.1 stream. The FEL is discarded because Profile 8.1 does not support enhancement layers (FEL or MEL) because it is a single-layer format. The resulting stream contains HDR10 video with dynamic metadata, but it lacks the extra color and brightness detail provided by the FEL.
And besides that, the Shield still has the infamous red push problem, which is a real big problem.
If you want as much picture quality as possible, your best bet is to use a Ugoos AM6b+ with CoreELEC, it can handle all the dolby vision profiles and layers like FEL.
The red push problem refers to an issue where red tones in HDR10/Dolby Vision content are oversaturated, this leads to inaccurate color reproduction.
The Nvidia Shield processes the color in HDR modes and it seems to push red tones too aggressively. That is why the color red appear overly vivid or intense, resulting in unnatural-looking skin tones and overall color balance.
It is not always noticeable, but it is something that is there and just makes the picture less accurate.
Interesting! I'm obviously a bit out of date. I've been using the Shield for a few years now, and I've been looking for a reason to replace it so I can retire it to my family's cabin where we've just been using the TV apps.I believe these all work, in addition to a few disc players that can also stream
Most of the models I mentioned are already dated, and corelec is shifting gears to a different product too I think, so it's functionality will probably be frozen at its current state, though that works for now. The emphasis of media boxes is mostly on streamed shows, which aren't FEL uhd discs, and dolby vision FEL chip requirements and licensing requirements don't help.
I think Dolby Vision and HDR 10+ mastering are sliding output values on a per scene basis (perhaps even area/object basis within each scene using tracking software) to help compensate for how limited HDR ranges are on current displays. Kind of like a human micromanaged and strictly defined dynamic tone mapping that is restricted to baked in values per scene. As it is now, that requires people to sort of compose (master) the pre existing scenes.
Hopefully as we get more capable hdr screens in the future, and hdr 4000 capable ones (ultimately hdr 10,000), we won't have to rely on dolby vision and hdr 10+ to spice up the output. I also wonder if AI will have a more prominent role in tone mapping HDR (and sdr to hdr) at some point, to get results comparable to dolby vision FEL, or better.
As much as people bemoan samsung's lack of dolby vision support, they are trying to make a comparable license free version with HDR 10+. I've also read that they and google, and some other partenered companies are trying to make a license free tech comparable to dolby atmos. The lack of licensing fees not only helps consumers with it being less restrictive, but also content creators.
https://www.cepro.com/news/samsung-google-eclipsa-spatial-audio-release-2025-tvs-soundbars/145192/
nope, doesnt work, doesnt even see i have 4k...some swear it works in chrome but i havent got that far yet...
https://github.com/balu100/dolby-vision-for-windows
Haven't tried this, but I'm gonna keep an eye on it for the update once the new Windows feature goes live.
Warning: `video_hex` of '2618039182697c' is already enabled with LLDV-HDMI
Yeah, I did some more research after your post. The Ugoos am6B+ seems to be the golden goose. It's still produced, and I believe it's the unit CoreELEC focused their efforts on. Sounds like it was a bit of a happy accident that the DV profiles and licenses for that specific chipset were opened up. They are moving on to other projects, but it sounds like they have the AM6B+ in a really good state where it can play everything. I have a lot of UHD Blu Ray rips, so I ordered one to give it a shot. Been looking to move away from Plex with their recent changes, so it's a good time to give Kodi a try. No AV1 decoding or streaming apps on the CoreELEC build, so it's just a pure media server streamer. I'll keep the Shield Pro around for streaming apps (or maybe move it to the cabin and get something with the AV1 chip) and look into Emby for remote streaming.
HDR10+ is a nice option to have. It does do dynamic metadata, but it doesn't give the colorist full control like DV. Some TV manufacturers like Panasonic are supporting both HDR10+ and Dolby Vision. While Samsung did make HDR10+ royalty free, it's not totally free. Anyone who wants to use their certification mark has to pay an annual fee. The Dolby Vision royalty fee is said to be less than $3 per TV set. I think most people would pay that given the option. Still, between DV, Atmos, and other options, the fees could start to add up. Maybe TV manufacturers could start adding these things as a feature users can pay to enable in software. Let the customer decide what they need and want to pay for. That's probably a pipe dream![]()
There are two Dune brand players (not all of their lines) that also have chips that work with the corelec "hack", one is all dune linux based, another has a dual boot option between Android os for streaming svcs and dunes Linux os. (And both auto boot corelec from a SD card or USB flash drive, respectively).
Seen those, but from what I gathered they play DV similar to the Shield Pro, ie w/o the FEL layer.
To play HDR content on your PC with MadVR, you'll need to configure both Windows and MadVR. First, ensure Windows HDR settings are disabled, as this can interfere with MadVR's tone mapping. Then, configure MadVR to either passthrough HDR metadata to your display or to perform its own tone mapping using pixel shaders, ensuring "output video in HDR format" is enabled.
Detailed Steps:
- 1. Disable Windows HDR:
In Windows settings, navigate to System > Display and turn off "Use HDR" and "HDR video streaming".
- 2. Install MadVR:
Download and install the K-Lite Codec Pack, including MPC-HC and MadVR.
- 3. Configure MadVR:
- Open the MadVR application (usually found under K-Lite Codec Pack).
- Navigate to "Devices" and select your display device.
- Under "Properties", set PC levels to 0-255 and bitdepth to 10 bit or higher.
- Under "Calibration", select "This display is already calibrated".
- 4. Configure Kodi (if using Kodi):
- Open Kodi and go to Settings > Player Settings > DSPlayer.
- Set "Video Renderer" to MadVR.
- 5. Test HDR playback:
- Play an HDR video and use Ctrl+J to view rendering stats in MadVR.
- Ensure your GPU and display are capable of supporting HDR and that you're using an HDMI 2.x port.
- If the colors look washed out, you may need to adjust your TV's settings or verify proper HDMI Black Level or Ultra Deep Color settings.
Important Considerations:
- Display settings: Ensure your TV's HDR mode is enabled and that you're using the correct HDMI input.
- GPU and HDMI: Make sure your GPU and HDMI port support HDR and that you're using the appropriate cables.
- Windows HDR settings: Disabling Windows HDR is crucial to avoid conflicts with MadVR.
- Tone mapping: MadVR can either pass the HDR metadata to your display for tone mapping or perform its own tone mapping using pixel shaders.
- Testing: Use test videos to verify that your HDR setup is working correctly.
- Updating MadVR: You can update MadVR by downloading a new version and copying the files into the relevant directory.
Just to update the somewhat off-topic DV FEL playback as pertains to a few stand alone players, from what I've gathered, the uggos AM6B+ is the best, least caveats and fastest functionality both due to the player specs and the fact that the corelec dev is developing specifically for it.
That's the conclusion I came to as well, so I've got the AM6B+ on the way. Plan is to use that purely for playing on local network from my personal server, and keep the Shield Pro for streaming apps. The way I look at it, AM6B+ is basically a Blu-Ray player without the hassle of discs. The Dune players look a bit nicer aesthetically, but I should be able to hide the AM6B+ well enough that it'll be a non-issue. I'm also looking forward to trying out Kodi, as the interface looks better than Plex or Emby. I'll keep my server running one of Plex or Emby for remote streaming. Plex has kinda gone to shit with the price hikes and data harvesting, so it'll probably be Emby.
Mine arrives tomorrow.
tossing in the towel for now. cant get DV to work correctly and Atmos is causing stupid drops when switching between even the most basic formats (like during youtube commercials) and is getting annoying, turned it back to dts:x.