View Full Version : AMD, Intel and Nvidia driver issues and last recommended version
SamuriHL
11th February 2023, 12:38
No... he's not.
https://www.avsforum.com/threads/improving-madvr-hdr-to-sdr-mapping-for-projector-no-support-questions.2954506/&share_tid=2954506&share_fid=47413&share_type=t&link_source=app
Sent from my SM-G998U1 using Tapatalk
Betroz
11th February 2023, 12:53
No... he's not.
https://www.avsforum.com/threads/improving-madvr-hdr-to-sdr-mapping-for-projector-no-support-questions.2954506/&share_tid=2954506&share_fid=47413&share_type=t&link_source=app
Sent from my SM-G998U1 using Tapatalk
"Oops! We ran into some problems.
The requested page could not be found."
mclingo
11th February 2023, 14:19
There is no new full version to download as such, however the madvr measure downloads do also contain core madvr updates, this is what people are referring to.
mclingo
11th February 2023, 14:21
167 is latest
mclingo
11th February 2023, 14:28
https://www.avsforum.com/threads/improving-madvr-hdr-to-sdr-mapping-for-projector-no-support-questions.2954506/page-799
dont think 167 is official yet, last post madshi made was 166
SamuriHL
11th February 2023, 16:55
Stupid phone didn't paste the link properly. Yes 166 beta is the latest that just got released yesterday. That's 166 builds since the last official release. You simply extract them into the madvr folder to update. They are also time limited so you'll need to update when new builds are released to continue using them.
Sent from my SM-G998U1 using Tapatalk
Betroz
11th February 2023, 17:54
Stupid phone didn't paste the link properly. Yes 166 beta is the latest that just got released yesterday. That's 166 builds since the last official release. You simply extract them into the madvr folder to update. They are also time limited so you'll need to update when new builds are released to continue using them.
Thank you! :)
Then I will just stick to what I got for now.
Klaus1189
15th February 2023, 19:23
Since AMD Ryzen 7000 has an iGPU based on RDNA 3 (AMD Radeon 780M) and bugs seem to be fixed, I thin kit could be a good choice for a budget HTPC. I know higher madVR settings will not work, but it is a good budget option.
I looked at a AM5 Motherboard with HDMI output it says in specs that it supports not only HDMI 2.1 but it says specifically 4K 120 Hz, which sound great for a low cost HTPC.
Intel UHD iGPU in 12th and 13th gen supports HDMI 2.1, but in specs it is always listed as 4K 60 Hz and I do not know if Intel has a good hardware deinterlacer which is frame adaptive.
If anyone has a 12th or 13 gen cpu from intel, please let me know, you colud do a small test for me.
(I am only interested in HDMI, not Displayport for HTPC)
AMD Ryzen 5 7600 and AMD Ryzen 5 7600X cheapest option
Grimsdyke
15th February 2023, 21:25
I wait for AMD's 6700G to see how it performs. And, of course, the price should reasonable too. :D
apophis906
15th February 2023, 22:42
I thought this would be the best place to ask about this issue. So I will randomly have glitches with my 4K playback if using hardware decoding. This is with my own re-encodes so far. This has happened when I had an older i5 board and an evga 1060 6g SC. I upgraded the board and CPU to a 3700x and still had the same issues. I just changed the card out for a evga 2060 KO ultra and it too shows the glitches. These glitches will happen at the same spot when they do happen and changing the encode settings any will usually make it not happen in that movie in that spot again. The other solution I figured out was to find the exact frame that it happened and use a QP file to put an I frame at that spot and it would not happen. So far my solution for the past few months has been to just use software decode since the 3700x has no trouble doing it. The problem is that I have two HTPC's and the second one would randomly show similar glitches but not be repeatable. So stopping the movie and starting it over and it would not have the glitch at that spot again. Unlike with hardware decoding where it always did it. My question is does anyone else have similar glitches with hardware decoding or any idea why I have these glitches. Especially since I have changed the motherboard and CPU as well as video card and still get them. Also the second HTPC has had its OS clean installed again. This happened on 385.28 and the ones I would test all the way up to 517.48 that I am using now. While using software decoding is so far the easiest solution. My problem was the second HTPC that would show the glitches as well as have playback crashes at times. That is the main reason for the upgrade from the 1060 to 2060. This is a pic of the glitch happening and this happens on both HTPC with any version of hardware decoding active.
https://i.postimg.cc/K1Njwtxb/20230215-162857-copy.jpg (https://postimg.cc/K1Njwtxb)
mclingo
16th February 2023, 00:08
Since AMD Ryzen 7000 has an iGPU based on RDNA 3 (AMD Radeon 780M) and bugs seem to be fixed, I thin kit could be a good choice for a budget HTPC. I know higher madVR settings will not work, but it is a good budget option.
I looked at a AM5 Motherboard with HDMI output it says in specs that it supports not only HDMI 2.1 but it says specifically 4K 120 Hz, which sound great for a low cost HTPC.
Intel UHD iGPU in 12th and 13th gen supports HDMI 2.1, but in specs it is always listed as 4K 60 Hz and I do not know if Intel has a good hardware deinterlacer which is frame adaptive.
If anyone has a 12th or 13 gen cpu from intel, please let me know, you colud do a small test for me.
(I am only interested in HDMI, not Displayport for HTPC)
AMD Ryzen 5 7600 and AMD Ryzen 5 7600X cheapest option
Hi, is everything fixed in the 7000 series?, video and audio issues? do you know if anyone has reported any audio dropouts, these plagued 5000 and 6000 users with recievers, albeit mainly in gaming.
Klaus1189
18th February 2023, 12:11
No info yet
ashlar42
18th February 2023, 12:27
Does anybody know what was the last version of Nvidia drivers capable of saving EDID when there are less than 2 bytes available in a block?
For reference: https://www.monitortests.com/forum/Thread-Unable-to-modify-AVR-s-EDID-I-could-previously?pid=14402#pid14402
Klaus1189
18th February 2023, 12:48
How can I test?
ashlar42
19th February 2023, 01:12
How can I test?
If you are asking regarding my question, the only test I can suggest is finding an EDID with less than 2 bytes available in a block and trying to edit it. Don't know if there are other ways.
Bearing in mind that it crashes the driver from CRU (and no F8 recovery either, it's safe mode and reset-all after that).
I don't know if ToastyX has info on that, I've asked.
Sunspark
19th February 2023, 10:44
@Klaus1189 Not the 11-12th gen you wanted, this test you requested is actually with 5th gen (Broadwell). I can state the results however. Using DXVA2 hardware decoding, there are no visible lines on the snooker player's shirt. If I use quicksync HW decoding, software chroma scaling and leave de-interlacing turned off I can see the lines, so this is evidence to me that the hardware decoder handles it automatically. This isn't really a surprise to me, Intel has always been good at video playback, it doesn't have the chroma error in DXVA that AMD and Nvidia had either. Update: Also, Quicksync decoding and turning the adaptive HW deinterlacing option in LAV video decoder on/off also works which is nice too, because that means you can pick and choose which chroma and image scaling algos you want to use in MadVR but the HW will do the deinterlacing instead of doing it in software in MadVR or being required to use DXVA chroma/image scaling if you're using MPCVR (though you could still use the MPCVR shaders for scaling w/ quicksync decoding and hw deinterlacing if using LAV). Hope this helps.
Klaus1189
19th February 2023, 11:24
Are the characters above "WWW.D88.COM" also not flickering? What CPU do you test exactly?
Sunspark
19th February 2023, 11:44
The Chinese characters aren't flickering, no. It does look subtly better using the Quicksync decoding HW deinterlacing than with the DXVA deinterlacing though the difference is quite minimal (and might be erased if one used the MPC decoder instead of LAV, who knows?).
The CPU is an Intel Core i5 5250U.
I also have a Steam Deck which uses a custom AMD RDNA2 APU but I have not yet tested it with video playback. Don't really need to, considering the Intel seems fine to use. I generally just do the chroma upscaling in software, and image scaling using the monitor's built-in scaler.
zealvix
19th February 2023, 17:56
Hi,
"Color levels (full 0-255 vs. limited 16-235) are broken. That means limited 16-235 which is the
standard range for videos are interpreted as 0-255 and this leads to elevated blacks and dimm
whites."
1. is the 7XXX series of radeon cards still affected by above bug?
2. Is the integrated RDNA2 GPUin mobile CPUs affected as well?
3. Does the version of madvr (0.92.17 or beta) make a difference in term of drivers related bugs?
Thanks.
Klaus1189
19th February 2023, 19:09
If you use madVR this bug is circumvented. So you will not see it. But it is in EVR and EVR custom presenter and also in MPC Video Renderer but only when using D3D9, that means if you check D3D11 in options you are fine.
huhn
19th February 2023, 19:46
23.21 has no range issue and "no" deint issue.
the masters is ever so slightly flicker. same for the kanji or Chinese. that's a huge win in my book.
please wait for more tests a sample size of one is way to low.
edit: broken in madVR.
Sunspark
19th February 2023, 21:19
@huhn What are you observing that you say madVR has an issue? It is fine for me with 92.17 and my older hardware/driver combination. Try using quicksync decoding with the adaptive HW deinterlacing checkbox that LAV has.
huhn
19th February 2023, 21:37
AMD deint does not work here at my end that's all.
i would never use quicksync i would never use software chroma scaling because it's bad and expensive compared to hardware/GPU.
i have no clue how intel performance these days i don't have any intel hardware i replaced all PCs in the past 2 years with ryzen CPU.
GTPVHD
8th April 2023, 23:42
https://www.intel.com/content/www/us/en/download/776137/intel-7th-10th-gen-processor-graphics-windows.html
This download installs Intel Graphics Driver 31.0.101.2121 for 7th-10th Gen Intel Core Processor Graphics, and related Intel Atom, Pentium, and Celeron processors.
6th gen Intel Skylake Gen9 integrated GPUs are no longer supported and will not receive any drivers updates.
https://www.intel.com/content/www/us/en/download/762755/intel-6th-10th-gen-processor-graphics-windows.html
End Of Life
6th Generation Intel Processor Graphics is an "End of Life" product as of December 30, 2022. For more support information, see Support Options for Discontinued Intel Graphics Products.
As this Software relates to “End of Life” products, it may contain security vulnerabilities. Intel does not intend to offer updates to mitigate any security vulnerability in this Software, whether currently known or discovered in the future.
mclingo
15th April 2023, 22:46
Hi, anyone still using amd 5000 series GPU running up to date windows 10 / MADVR who can still get 3D MVC to work, cant get 3D to trigger for the life of me, all the usual prerequisites are in place, movie starts, TV goes into 3D mode but movie plays in 2d, cant work it out.
windows 10 22h2
mclingo
15th April 2023, 23:09
seems to be an issue with full screen mode, using MPC-HC, if I double click on the movie to come out of full screen mode 3D MVC triggers, but dies again when I go back into full screen mode, any ideas anyone? - windows 10 22h2
mclingo
15th April 2023, 23:44
so after playing around with driver versions, MADVR versions, LAV filers etc etc nothing work but I played one video and accidentally triggered my on screen keyboard which came up over the top of the movie, bizarrely this fixes it, if I leave OSK on the screen and drag it down to the bottow so I can only see a small corner of it the movie plays fine, this is utterly bizarre, unless someone knows something I dont about 22H2 issues?
mclingo
16th April 2023, 10:08
doesnt seem to be a driver issue so I'll not post on here anymore as 3d work with potplayer and non MADVR renderer.
Sunspark
17th May 2023, 08:28
If you use madVR this bug is circumvented. So you will not see it. But it is in EVR and EVR custom presenter and also in MPC Video Renderer but only when using D3D9, that means if you check D3D11 in options you are fine.
I set up a Windows external drive on a mobile RDNA2 APU. Was pretty surprised when testing video to blacks washed out, but happy to report that MPC Video Renderer doesn't have this problem in Shader mode, even with D3D9.
Unforunately, the drivers from Valve are super busted in some aspects.. one is that they have no hardware acceleration at all for video decoding or encoding with Windows.
Goeggel
19th May 2023, 21:38
I have an issue with stuttering on 4K HDR MKVs with RTX 3080, Marantz SR-6011 and LG OLED65B8. 1080p SDR MKVs are fine. Latest madVR, LAV filters and Nvidia 531.79. Win 10 22H2. Zoom Player and MPC-BE.
Every half a minute or couple of minutes, the picture stumbles / stutters / jumps a few frames. Sound is fine. madVR display info doesn't show any frame drops. The issue is random and and always occurs at different time stamps.
With the same setup and a GTX 980, SDR and HDR were fine. Then I changed to a RTX 2070 Super. At first everything was fine. Then with around Nvidia 512.x and/or a Windows update, SDR and HDR were constantly stuttering. This was solved by:
- Vertical Sync to 'On' for the media player exe.
- In the madVR settings, uncheck 'enable automatic fullscreen exclusive mode
- In the madVR settings, how many video frames shall be presented in advance' to 1
Now with the RTX 3080, what else can I try to solve this stuttering with HDR MKVs?
Furgiuele
22nd May 2023, 01:08
Hello.
After using madvVR on the pc with Jriver Media Player for years, in 2020 I bought the Envy Pro.
But I continued to use the PC as a media server: on the PC madVR performs the upscaling (->4k, chroma, luma, etc.), the hdr is set to pass trough (sending metadata to the display) and the Envy performs the calibration (with 3d lut) and tone mapping.
For years I have had Nvidia 2060 card with 442 driver in my PC and everything worked perfectly.
A few days ago I changed GPU (for 3050) and I had to update the driver.
Since then, when madVR broadcasts HDR signal it gets stuck and if I throw an SDR video, it doesn't show well.
Can someone help me? Is there a Nvidia driver with which this error does not occur?
In the PC I have the latest edition of madVR (166). Is there another remedy?
Thanks.
Klaus1189
22nd May 2023, 17:01
@Goeggel and @Furgiuele: Sounds to me that a new card was installed and a driver was installed. DDU the driver and install driver new. But don't forget to apply the needed settings in driver like VSync for player exe, ...
Crimson Wolf
26th May 2023, 18:04
Some weird video playback issue with 532.03. Whenever I watch a video larger than my screen and downscaling, I would have massive frame drops. For example, watching 4k60 video using mpv via yt-dlp downscaled to 1080p would show Display FPS: 119.982 (specified) ###.### (estimated) , where ###.### would be lower than normal which would cause frame drops constantly. For MPC-HC (madvr), Ctrl-J would start out fine, then constant frame drops, then fine again, then frame drops. It would also happen when watching 4k 24fps/30fps video as well. If watching 1080p video, no frame drops and mpv would show estimated FPS matching my specified.
I just DDU'd and installed the last studio drivers 531.61 and the issue is gone. I was not patient enough to find out if 532.03 was the issue or if it happened earlier.
SamuriHL
28th May 2023, 21:20
I really wish nVidia would do something about the Dolby dropouts. ATMOS tracks are a mess. It really sucks.
ryrynz
29th May 2023, 08:23
I really wish nVidia would do something about the Dolby dropouts. ATMOS tracks are a mess. It really sucks.
I get the odd drouput over E-ARC with any audio which I suspect is related.
SamuriHL
29th May 2023, 13:49
No earc in this case. It's a 3080 connected to an avr.
Sent from my SM-G998U1 using Tapatalk
ryrynz
29th May 2023, 23:40
I had the same audio issue before when running it out from a DP to HDMI adapter to the AVR as well. Thankfully it's not happening terribly often.
SamuriHL
30th May 2023, 18:20
Oh yey more "beta testing" for them. LOL
ryrynz
14th June 2023, 23:57
Oh yey more "beta testing" for them. LOLI did a DDU and haven't had any audio issues since. Everything's peachy.
SamuriHL
16th June 2023, 10:53
I may try it. The dropouts are annoying.
Sent from my SM-G998U1 using Tapatalk
aquanash
26th June 2023, 18:07
I've been running nvidia driver 536.23 for over a week now and everything appears to be okay except they still haven't fixed the HDR switching issue that's been happening in every version after 525.25. I still have to restart the video card every few days to keep HDR switching working. I made sure to use DDU (safe mode) when upgrading.
ryrynz
27th June 2023, 00:55
I did a DDU and haven't had any audio issues since. Everything's peachy.Had one brief audio drop, unsure what caused it. Never had any HDR issues.
ryrynz
30th June 2023, 01:45
No DPC latency fix with these so potential to experience audio drop ours still exist. "Next" driver should resolve it based on tweets, currently in QC testing.
SamuriHL
30th June 2023, 15:02
That would be nice.
ryrynz
18th July 2023, 23:25
Maybe Spotify won't have the occasional hiccup now.. Fingers crossed. Although my latency still appears at the same levels as before being a "potential" issue. Apparently Rebar is a sighted cause for high latency.. as long as my audio doesn't drop through that's all that matters.
Mordred
21st July 2023, 05:54
I've been running nvidia driver 536.23 for over a week now and everything appears to be okay except they still haven't fixed the HDR switching issue that's been happening in every version after 525.25. I still have to restart the video card every few days to keep HDR switching working. I made sure to use DDU (safe mode) when upgrading.
Have you tried the latest driver yet? The reboots to fix HDR are driving me nuts.
Goeggel
24th July 2023, 09:06
I have an issue with stuttering on 4K HDR MKVs with RTX 3080, Marantz SR-6011 and LG OLED65B8. 1080p SDR MKVs are fine. Latest madVR, LAV filters and Nvidia 531.79. Win 10 22H2. Zoom Player and MPC-BE.
Every half a minute or couple of minutes, the picture stumbles / stutters / jumps a few frames. Sound is fine. madVR display info doesn't show any frame drops. The issue is random and and always occurs at different time stamps.
With the same setup and a GTX 980, SDR and HDR were fine. Then I changed to a RTX 2070 Super. At first everything was fine. Then with around Nvidia 512.x and/or a Windows update, SDR and HDR were constantly stuttering. This was solved by:
- Vertical Sync to 'On' for the media player exe.
- In the madVR settings, uncheck 'enable automatic fullscreen exclusive mode
- In the madVR settings, how many video frames shall be presented in advance' to 1
Now with the RTX 3080, what else can I try to solve this stuttering with HDR MKVs?
I am still fighting this issue...
- Installed the latest Nvidia driver with DDU.
- Latest LAV filters
- Also tried with latest beta MadVR
- Installed latest updates for Windows 10 22H2
What else could I try?
Klaus1189
24th July 2023, 20:39
Can you upload a screenshot playing a problematic file with OSD info?
Use external website like Google drive.
Goeggel
27th July 2023, 08:31
Here are the OSD screenshots for 1080p (no stutter) and 2160p (random stutter):
https://imgur.com/a/lIXmdhx
By stutter I mean it looks like a few frames are skipped and as if the movie jumps a tiny bit forward. Sound is always fine.
I let run the 1080p MKV for about 5 minutes and the 2160p MKV for about 15 minutes.
The shown Drop/Rep values for both files were from opening the MKV and then going to fullscreen (MPC-BE player). These two values didn't change during the runtime.
The value for Gltch on the 1080p didn't change during the runtime.
On the 2160p MKV however, Gltch would go higher every now and then. Sometimes I thought the counter went up immediately after a stutter had occured. But sometimes the counter went up and I didn't notice a stutter (they are quite subtle). So I am not sure if it's a coincidence or not.
Grimsdyke
27th July 2023, 13:47
Have you tried to increase the difference between CPU and GPU cache in MadVR -> rendering -> general settings ? In my setups I always have at least a difference of 6.
Would also suggest to use profiles for varying resolutions.
ryrynz
27th July 2023, 21:02
Does turning off subtitles help? Higher madVR caches are a potential workaround.
Goeggel
28th July 2023, 07:49
Have you tried to increase the difference between CPU and GPU cache in MadVR -> rendering -> general settings ? In my setups I always have at least a difference of 6.
Would also suggest to use profiles for varying resolutions.
Which cache settings do you use?
Goeggel
28th July 2023, 07:52
Does turning off subtitles help? Higher madVR caches are a potential workaround.
I will check regarding the subtitles.
With cache, do you mean queue size? I have tested with setting the GPU and CPU queue sliders all the way to the right (highest settings). Unfortunately, the stutter was still there.
ryrynz
28th July 2023, 08:34
Yeah the queues. Well that rules out one avenue of resolving things. Next step will be to try ruling out the software step by step.
Grimsdyke
28th July 2023, 15:36
Just in case your RTX runs into a bottleneck because of whatever reason I would suggest also test reducing the GPU cache/queues down to '8' or '10'.
huhn
28th July 2023, 15:45
the usual:
force vsync in the nvidia control center and use a render queue between 1-3.
nvidia pretty much needs these settings to have a chance of working.
Goeggel
31st July 2023, 09:05
Thank you all for your inputs! I think I maybe got it to work without stuttering. Not 100% sure as I haven't had time to watch a whole 4k MKV, but it looks promising.
Setting the Nvidia power configuration to "Maximale Leistung bevorzugen" (max power) instead of "Normal" (which was working on the 980 and the 2070S) on the media player EXE seems to get rid of the GLTCH and visible stutter for me.
I already had Vsync on the media player EXE and render queue to 1 since the 2070S.
Turning off the subtitles didn't make any difference. I also tried to disable the GPU acceleration in LAV Video filter and let the CPU do the work, but still had the GLTCH numbers going up.
I noticed that I didn't have visual stutter with every GLTCH, but every visual stutter was accompanied with a GLTCH.
What exactly does the GLTCH mean in madVR?
el Filou
31st July 2023, 17:05
Glitches are when another application is using the GPU to draw at the same time as madVR when in (fullscreen) windowed mode.
It could be anything from a desktop app displaying GUI elements to another app displaying an overlay (i.e. Logitech Options does that with my wireless keyboard, or a Windows notification).
Quitting other apps that can use the GPU one at a time until glitches stop increasing could be a way to find out.
You can see which apps use the GPU with Task Manager.
Goeggel
3rd August 2023, 10:39
"Prefer Maximum Performance" / "Maximale Leistung bevorzugen" definitely gets rid of the Gltch and visual stutters for me. Putting it back to "Normal" and the Gltch and stutters are back.
The downside is that on max performance setting the RTX3080 (and the PC as a whole) get now much hotter than before...
I have tried to find out what hogs the GPU on Normal settings to cause the Gltch, but I don't see anything unusual going on.
*MidnightWatcher*
20th August 2023, 16:35
What's the consensus on the best nvidia driver to use currently for 23.976 playback and bitstreaming? Card is a GTX 2070S.
ryrynz
21st August 2023, 02:00
What's the consensus on the best nvidia driver to use currently for 23.976 playback and bitstreaming? Card is a GTX 2070S.Latest. 536.99
suisenken
23rd August 2023, 10:50
Hi, since a few weeks not sure when that start, I get a signal lost when selecting 23.976hz 10bpc 12bpc RGB, unfortunately i see no improvement with the latest driver,
My setup "RTX3080Ti /Marantz 7010/Panasonic Oled TV", No issue when the pc is connected directly to the TV.
Anyone who have "PC + Receiver + TV" have this issue?
Thx
angmav
24th August 2023, 14:00
Yes i have the same issue i thought i was going nuts and there is something wrong with my units
Sent from my iPhone using Tapatalk
Klaus1189
24th August 2023, 15:43
Interesting. Did you update Firmware of your AV Receiver in that time?
Could you please test older GPU drivers? Best thing is to track down what version is first affected.
suisenken
24th August 2023, 19:05
Yes i have the same issue i thought i was going nuts and there is something wrong with my units
Sent from my iPhone using Tapatalk
What HDMI version is your unit and your graphic card?
I Have RTX3080Ti HDMI 2.1 and Marantz 7010 is 2.0a. thx and i suspect that something is broken with the Nvidia driver
suisenken
24th August 2023, 19:25
Interesting. Did you update Firmware of your AV Receiver in that time?
Could you please test older GPU drivers? Best thing is to track down what version is first affected.
No more firmware update on the 7010, it seem to be back to normal with march version according to a post i saw on madvr but i need test and find the version this weekend.
angmav
24th August 2023, 21:37
What HDMI version is your unit and your graphic card?
I Have RTX3080Ti HDMI 2.1 and Marantz 7010 is 2.0a. thx and i suspect that something is broken with the Nvidia driver
I have an rtx3080 hdmi ver2.1 and a denon 8500h which is hdmi 2.0a
Sent from my iPhone using Tapatalk
suisenken
26th August 2023, 16:58
Hi
the issue start with 535.98 before that RGB 10bit and 12bits are working. YCbCr422 is not affected.
I'm going to check with a DP 1.4 to HDMI 2.0b see if that a possible workaround.
RGB 10bit 12bit
536.99 KO KO
536.67 KO KO
536.40 KO KO
536.23 KO KO
535.98 KO KO
532.03 OK OK
531.79 OK OK
I'm wonder if receiver with HDMI 2.1 input have this issue, anyone? will be nice to knows before making a bug report.
nevcairiel
26th August 2023, 17:49
I use a 3070 Ti for my TV, and it runs RGB 10/12-bit just fine.
Klaus1189
26th August 2023, 17:55
HDMI directly to TV or through AVR?
suisenken
28th August 2023, 19:19
connected directly to TV no issue, Panasonic tx-55fz800e, Hdmi 2.0b (HLG), i'm not even sure how to report this, as this issue only happen when its connected to a receiver, but is it only certain generation? this issue is giving me a headache, already 5 drivers update.
Tiraga
1st September 2023, 21:31
On the combination of 3060Ti -> Denon X1700H -> LG OLED B8 i can't get a picture with 10bit and 12bit in 4k24 if i connect the GPU to the TV it works without problems. Need to check the driver version tomorrow.
angmav
6th September 2023, 21:37
I have the same problem i cant get 3840 * 2160 rgb 10 or 12 bit to work ,ycbrcr422 12bit does work running a rtx3080 which is hdmi 2.1
i am running latest nvidia game version running into denon x8500h which is hdmi 2.0 into my jvc nx7 which is hdmi 2.0 every other source accepts 12 bit rgb such as panasonic ub820 and firestick no problem @23hz and 24hz
Sent from my iPhone using Tapatalk
Klaus1189
7th September 2023, 05:04
According to the number of HDMI through AVR 10 bit not working, there seem to be an issue on Nvidias side.
SamuriHL
7th September 2023, 09:36
According to the number of HDMI through AVR 10 bit not working, there seem to be an issue on Nvidias side.While I don't disagree with this assertion, I can offer that I'm using rgb 10 bit on my 3080 to my G2 through my HD fury vrroom without issue. Not sure that helps anyone but it's another data point.
Sent from my SM-G998U1 using Tapatalk
nevcairiel
7th September 2023, 09:40
Works just fine from my 3070 Ti to an LG G1 through a Denon AVR as well. 3840x2160, 10/12-bit, RGB, 120Hz, HDMI 2.1, all working perfectly.
The reports above all have HDMI 2.0 devices in their chain. 4K 10-bit is severely bandwidth constrained on HDMI 2.0. Its possible they are trying to get desktop at 60Hz working, which just doesn't work.
angmav
7th September 2023, 11:02
I have the same problem i cant get 3840 * 2160 rgb 10 or 12 bit to work ,ycbrcr422 12bit does work running a rtx3080 which is hdmi 2.1
i am running latest nvidia game version running into denon x8500h which is hdmi 2.0 into my jvc nx7 which is hdmi 2.0 every other source accepts 12 bit rgb such as panasonic ub820 and firestick no problem @23hz and 24hz
Sent from my iPhone using Tapatalk
I rolled back drivers and now i have 12 bit working again to 531.29 dch and all is good if anyone else is having an issue you might want to try as well
Must be having hdmi 2.0 in the chain causing some sort of issue as it wouldn’t allow to engage hdr as well but now all is working as it should definitely nvidia issue
Sent from my iPhone using Tapatalk
BatKnight
9th September 2023, 15:09
I can confirm that with a RTX 4060 Ti 16GB connected by HDMI to an Denon AVR-X2700H and then to a Sony TV I also get no signal when playing RGB 10bit HDR videos at 23.976Hz with all the latest drivers.
The oldest driver that works is 532.02
Klaus1189
9th September 2023, 16:27
Thanks for Feedback. Since the Denon AVR-X2700H has one 8k60/4k120 Port, same issue there?
Till now only 18gbps (HDMI 2.0) was reported.
Manni
10th September 2023, 13:26
Hi
the issue start with 535.98 before that RGB 10bit and 12bits are working. YCbCr422 is not affected.
I'm going to check with a DP 1.4 to HDMI 2.0b see if that a possible workaround.
RGB 10bit 12bit
536.99 KO KO
536.67 KO KO
536.40 KO KO
536.23 KO KO
535.98 KO KO
532.03 OK OK
531.79 OK OK
I'm wonder if receiver with HDMI 2.1 input have this issue, anyone? will be nice to knows before making a bug report.
Thanks for this, I was wondering why I was getting all these black screen in 4K24p in 10/12bits. I can confirm I have the same issue with a 3090, going through a Denon X8500HA to a JVC NZ8. I am using the HDMI 2.0 input for the HTPC because the 8K input can't be sent to HDMI zone 2.
Reverting to the latest working studio driver (531.61) resolves the issue.
I use a 3070 Ti for my TV, and it runs RGB 10/12-bit just fine.
This is ONLY with 24p. 60p is forced at 8bits with HDMi 2.0, you can't select 10/12bits.
connected directly to TV no issue, Panasonic tx-55fz800e, Hdmi 2.0b (HLG), i'm not even sure how to report this, as this issue only happen when its connected to a receiver, but is it only certain generation? this issue is giving me a headache, already 5 drivers update.
What's your receiver? I understand you're using HDMI 2.0?
Works just fine from my 3070 Ti to an LG G1 through a Denon AVR as well. 3840x2160, 10/12-bit, RGB, 120Hz, HDMI 2.1, all working perfectly.
The reports above all have HDMI 2.0 devices in their chain. 4K 10-bit is severely bandwidth constrained on HDMI 2.0. Its possible they are trying to get desktop at 60Hz working, which just doesn't work.
Again, have you checked at 4K24 10/12bits? 60p (8bits) works fine. I'm using a HDMI 2.0 input on my X8500HA as mentioned above. The whole chain is forced to 2.0 (the JVC EDID is set to an HDMI 2.0 EDID, and I've limited the Denon's bandwidth to HDMI 2.0 by setting it to HDMI Enhanced 4K instead of HDMI Enhanced 8K).
Interestingly, this EDID B (HDMI 2.0) works fine with pre-535.98 drivers. With any more recent drivers, I get a black screen and have to select EDID A (HDMI 2.1) to get a picture. No such issue with other sources (but they are all HDMI 2.0).
Please confirm that you have no issue with your 3070ti with 4K24p 10/12bits (which fits an HDMI 2.0 bandwidth fine) when using a HDMI 2.0 path (not HDMI 2.1).
nevcairiel
10th September 2023, 13:43
I don't use HDMI 2.0, not limiting myself to that when I can use 4k 120Hz 10-bit over HDMI 2.1. Its clearly an issue with HDMI 2.0 only, which wasn't clear at all when the discussion started.
Manni
10th September 2023, 13:58
I don't use HDMI 2.0, not limiting myself to that when I can use 4k 120Hz 10-bit over HDMI 2.1. Its clearly an issue with HDMI 2.0 only, which wasn't clear at all when the discussion started.
Yes, though some of us have reasons to stick to HDMI 2.0 when competitive FPS gaming isn't the primary use of a HTPC :)
As long as I get 10/12bits with 24p content, I'm happy to use the computational power and limit the frame rate to 24p 12bits / 60p 8bits, which fits fine into the HDMI 2.0 bandwidth.
As I said, in my case the HDMI 2.1 input can't be routed to the HDMI Zone 2, which is where my Sony HDMI headphones are located. Hence why I moved the HTPC (for now) to a HDMI 2.0 input.
Also some of use still have a HDMI 2.0 AVR, it doesn't mean they should be able to take advantage of a recent GPU.
This needs to be reported to nVidia now that we know what the factors are:
4K24p 10/12bits RGB through HDMI 2.0 chain including an AVR gives black screen from 535.x
I've ordered a 4070 to resolve another issue, I'll report back if the issue is the same with a 4xxx card.
Does anyone use a 4xxx card and get the same issue?
Please everyone with the issue report to nVidia so that this can get solved (please see link in post below).
Manni
10th September 2023, 14:10
Bug report posted here: https://www.nvidia.com/en-us/geforce/forums/game-ready-drivers/13/526544/black-screen-in-4k24-1012bits-with-ampere-using-hd/
Please post in that thread with your hardware details to make it clear I'm not the only one experiencing this (though I linked to this thread for reference).
SirMaster
11th September 2023, 15:13
Some people I know (including myself) simply use 2 outputs from an HTPC. A dedicated HDMI output directly to their display for video, and a secondary HDMI output (this can be a DP-to-HDMI adapter) to their AVR for audio.
Then we can get the latest video signal support on our displays without needing to worry about the AVR video support.
Manni
12th September 2023, 00:07
Some people I know (including myself) simply use 2 outputs from an HTPC. A dedicated HDMI output directly to their display for video, and a secondary HDMI output (this can be a DP-to-HDMI adapter) to their AVR for audio.
Then we can get the latest video signal support on our displays without needing to worry about the AVR video support.
Thanks for the suggestion, but when you do this you lose the AVR OSD, which I use all the time (especially with immersive audio). That's a compromise too far for me.
I've decided to go back to using the HDMI 2.1 input of the X8500HA for the GPU. The main downside is that I only have LPCM 2.0 sound when using my Sony HDMI Headphones, as I have to use the HDMI Audio Out (TV) of the AVR, which is sadly limited to stereo. The plus side is that I get 4K120 10bits for gaming and 4K60 10bits for video, and of course no HDMI 2.0 bug at 4K24 with the latest drivers. I don't use the headphones very often with the HTPC, so stereo will have to do.
Better than having to wait for nVidia for a fix that might never come, given that it's not a very common issue.
Looks like even the A1H has this limitation to LPCM 2.0 on the HDMI Audio Out (TV) and that the HDMI Zone 2 is also limited to 18Gb/s. Hard to believe for a 2023 model. I'm glad I skipped that "upgrade"...
Manni
12th September 2023, 02:37
I've actually resolved this with a HD Fury VRROOM :)
I inserted the VRROOM between the GPU and the AVR on the 8K (HDMI 2.1) input. The PC sends up to 4K120 10bits RGB with Atmos and the VRROOM simply passes it through to the AVR, but it also extracts the full Audio directly to the Sony HDMI Headphones (along with dummy 1080p60 or 720p60 video for HDMI 1.4 compatibility, as that's the limitation of the Sony HDMI Headphones).
I now get Full HD Audio bitstream up to 7.1 (it works fine when the PC sends Atmos or DTS/X, I guess it just ignores the metadata and processes the core). I get 7.1 bitstreamed, matrixed to Neo:X (or Dolby PLIIz). I don't have to use HDMI Zone 2 or HDMI Audio Out (TV) in the AVR, so no compromise when using the HDMI headphones for picture or sound.
It shouldn't be so complicated, but I'm glad this is fully resolved for me now. I hope nVidia will resolve the HDMI 2.0 bug, but I wouldn't bet on it.
SamuriHL
12th September 2023, 03:15
That's how mine is set up as well. My avr is hdmi 2.0 and non earc. So it gets audio from the vrroom and video is sent to the g2 from the vrroom. Audio is muted by the vrroom to the display.
Sent from my SM-G998U1 using Tapatalk
Klaus1189
22nd September 2023, 11:05
Anybody tested 537.42 for AVR with HDMI 2.0 issue?
Manni
22nd September 2023, 14:44
The 4070 didn't resolve the Atmos drop outs issures I had with the 3090, so the 4070 was sent back and I went back to my 1080ti for use in the HTPC. It's annoying but I'm mostly using it as a HTPC, more rarely with gaming and almost never with video editing anymore, so it's not too bad. The 3090 is now in the E-GPU connected to my Dell XPS 17 (with a discrete 3060 as well), which is what I use for video editing now.
As a result, the 1080ti HTPC uses a HDMI 2.0 input and the 3090 in the EGPU uses the HDMI 2.1 input in the AVR, so that HDMI 2.0 bug is resolved for me and I can't test for it anymore. I don't need the VRROOM for the HTPC source anymore to get sound to my Sony HDMI Headphones, which is nice. I can just use Zone 2, like any other HDMI 2.0 source.
If anyone doesn't have any Atmos drop outs when bitstreaming with a 3xxx or 4xxx, I'd like to know all their settings (lav version and settings, nvidia drivers and settings, OS and settings).
It sometimes goes away for a while when I change something, but it always came back with the 3090/4070, while all is always fine with the 1080i. I assume a 2xxx would be safe too, as this Atmos dropouts nightmare when bitstreaming started with Ampere.
The best I was able to get with the 3090/4090 was one Atmos drop out after 30 to 60 minutes of film, but it's often more than that. Not usable on a HTPC. I guess it's a non issue if you don't bitstream or if you don't go through an AVR, but if you do it's a real pain.
Klaus1189
22nd September 2023, 18:15
Nev fixed in latest nightly an Atmos issue.
https://github.com/Nevcairiel/LAVFilters/commits/master
https://github.com/Nevcairiel/LAVFilters/commit/a9b4374b2375a672608d617c9c396229be1a477b
Did you use this version or an older one? Perhaps this version fixes it for you on 30/40 series?
Manni
22nd September 2023, 20:00
Thanks, I use whatever version is included in jRiver (and the latest stable for other software such as MPC-BE etc). I'll give it a try when I have a moment, if anyone with a 30xx confirms that they can bitstream Atmos and not get any dropouts, and what their settings are. I've spent weeks on this, I'm not keen to swap the GPUs again...
Right now I don't know if anyone is actually able to bitstream Atmos through am AVR with a 30xx without issues.
SamuriHL
22nd September 2023, 21:08
Even with the latest LAV I still get dropouts. It's better, don't get me wrong, but, my 3080 still has issues. Hell, I get dropouts in DTS-HD MA from time to time so who knows. ATMOS is worse, but Nev's fix did improve things.
Manni
22nd September 2023, 22:15
Even with the latest LAV I still get dropouts. It's better, don't get me wrong, but, my 3080 still has issues. Hell, I get dropouts in DTS-HD MA from time to time so who knows. ATMOS is worse, but Nev's fix did improve things.
Thanks for the confirmation. Good to know it’s improved and might be fixable, but improved isn’t good enough. I have zero tolerance for drop outs when I watch a film, so for now it’s the 1080ti.
pirlouy
22nd September 2023, 22:17
Excuse ma curiosity. Dolby Atmos and DTS-HD MA are decoded by apps now ? Is there a reason to use bitstream ?
SamuriHL
23rd September 2023, 01:55
Decoding doesn't give you the DTS:X or ATMOS metadata. So, no to that. We need bistreaming.
Klaus1189
23rd September 2023, 05:29
Have you guys tried internal filters of MPC-BE?
QBhd
23rd September 2023, 05:45
Have you guys tried internal filters of MPC-BE?
I don't have a horse in this race, but isn't Atmos like Vision... the end device needs to have the meta data, so nothing on a PC will be able to decode it. It needs to be passed through. In the case of Dolby Vision, you need to play the video on the TV since nothing can do "pass through", at least audio has bitstreaming to passthrough the needed info.
QB
Klaus1189
23rd September 2023, 05:49
Something wrong is happening when bitstreaming atmos from pc. Perhaps another approach helps.
Manni
23rd September 2023, 12:02
Decoding doesn't give you the DTS:X or ATMOS metadata. So, no to that. We need bistreaming.
Exactly. No bitstreaming, no immersive sound (Atmos, DTS:X, Auro 3D).
Have you guys tried internal filters of MPC-BE?
I don't think there are internal filters in MPC-BE (as long as you mean LAV filters), I think it's MPC-HC that has an internal version of LAV.
When I did initial testing, I only had issues with jRiver, not with MPC-BE, but it might be because I didn't play a full film. Sometimes, you get an Atmos drop out within 10 minutes, sometimes you need to wait around an hour to get one. So at the beginning, I ruled out a few things wrongly simply because the drop outs I had in John Wick 3 (at least 2 or 3 at the same places within the first 30 minutes) went away.
I even had at some point no Atmos drop outs with the 3090 when watching a few of the Lord of the Rings trilogy, so I really thought it was fixed. And then it came back.
You can follow the whole saga of my testing, what I tried and my various false hopes here: https://yabb.jriver.com/interact/index.php/topic,136525.0.html
This makes it really difficult to test, because you'd have to watch at least 4-5 films with each setting to be able to make a positive conclusion.
I spent a few weeks trying to resolve this, I'm not putting the 3090 in the HTPC again without confirmation from someone that they have no Atmos drop outs CONSISTENTLY, and provide their settings with a 3xxx GPU.
If I have some time at some point, I might try the 3090 in the E-GPU with Atmos bitstreamig as it's also wired in the AVR (on the HDMI 2.1 input), but that's not a standard configuration (there is lot more latency with the E-GPU for example) so it might be better or worse than when used in the HTPC.
Very curious to hear from any 3xxx user without any Atmos drop out when bitstreaming through an HDMI 2.1 AVR. No one came forward, so I assume that no one has succeeded.
Klaus1189
23rd September 2023, 14:55
Yeah, because MPC-HC has integrated LAV Filters, it is pointless to test it. MPC-BE has internal filters capable of bitstreaming. This one can be tested.
SamuriHL
23rd September 2023, 14:59
My setup is through a vrroom. The 3080 is input to the vrroom. Hdmi audio out from vrroom to my hdmi 2.0 avr. Audio to the hdmi 2.1 display muted through the vrroom. I have dropouts.
Sent from my SM-G998U1 using Tapatalk
Klaus1189
23rd September 2023, 16:54
With LAV Filters and/or MPC-BE internal Filters
Manni
23rd September 2023, 17:36
Nevcairiel confirmed in the jRiver thread I linked to above that the LAV improvements in the recent version had already been fixed in jRiver MC in a different way, and that the issue fixed (same Atmos drop in the same scene with all hardware) would have happened with the 1080ti as well. So that won't change the drop outs I experience with jRiver with the 3090 (or the 4070) as I was using jRiver to test and the drops don't happen in the same place all the time. However, it might have been why the dropouts in John Wick 3 stopped, as these were always in the same place (and more frequent), so that was indeed an improvement, but it was brought to jRiver MC before this latest LAV Filter version.
In other words, the latest LAV filters would only bring an improvement if you don't use jRiver. If you do, these improvements were brought in earlier.
SamuriHL
23rd September 2023, 17:50
I use JRiver so the newest LAV version probably didn't change anything. I still get dropouts randomly as well. Something about these new RTX cards is just whacked with audio.
Klaus1189
23rd September 2023, 17:51
So do you test MPC-BE internal Filters?? Not LAV or JRiver?
SamuriHL
23rd September 2023, 20:25
I don't have MPC-BE installed and really have no need to. I use JRVR for every day watching which is only in JRiver. I'm sure others can test MPC-BE internal filters. if it changes the equation, that would be interesting.
Klaus1189
24th September 2023, 10:54
Using only one approach and conclude it is a driver issue is not the way to go.
MPC-BE can be installed portable.
Another good choice is Kodi.
SamuriHL
24th September 2023, 14:03
I didn't conclude anything in my case. I simply commented that I get dropouts in my setup. Whether it's a jriver thing, lav filter thing, driver thing, configuration thing, avr thing, or some phase of the moon problem remains to be seen. I'll wait for others to make conclusions about the cause.
Sent from my SM-G998U1 using Tapatalk
Manni
24th September 2023, 15:50
Using only one approach and conclude it is a driver issue is not the way to go.
MPC-BE can be installed portable.
Another good choice is Kodi.
The only one concluding it’s the driver is Jim at jRiver. I certainly don’t, given that the same driver works flawlessly with my 1080ti and doesn’t prevent the 3090 or the 4070 from causing ATMOS drop outs.
The problem with testing other software that you don’t use routinely (like MPC-BE in my case or in SamuriHL’s case) is that tests can be inconclusive or deceptive unless you actually watch many films with that software.
I only watch films with jRiver (apart from bd menus support, though it’s connected) because I want the right forced subs to be played from my bd folders. I’m not going to spend hours and hours watching the same content to test a software that I’m never going to use otherwise.
I did try, and (possibly incorrectly) concluded that there was no drop outs with MPC-BE simply because I had no drop outs at the time for 30-40 minutes, but it doesn’t mean that there is no drop outs.
I even managed to watch a couple of LOTR movies with the 3090 and experienced no drop outs, before they came back with a vengeance.
So apart from spending a week testing and watching many films, there is no way to know.
Someone might want to do this to test your theory, but I won’t. I spent weeks testing this, and I’ll put the 3090 back only when someone reports that it works, and provides all their settings.
Until then, for whatever reason (lost likely an incorrect able hardware issue in ampere and Lovelace as far as I’m concerned) bitstreaming ATMOS isn’t possible on these without drop outs.
No one has come forward saying they have no issue with these. That speaks volume.
nevcairiel
24th September 2023, 22:47
General rule of the internet, people without problems wont usually come to complain :D
Manni
24th September 2023, 23:04
General rule of the internet, people without problems wont usually come to complain :D
Sure, but at least you or someone else could know a friend who is able to bitstream Atmos through an AVR with a 3xxx or 4xxx GPU without any issue... You see what I mean?
Usually when you post about a problem that isn't for everyone, you get at least one person stepping forward and saying "Works fine for me". Nothing like that with this Atmos bitstreaming issue with 3xxx and 4xxx GPUs.
The problem is that the user base is small: you have to have a 3xxx or 4xxx GPU, use a HTPC as a source and bitstream ATMOS through a 2.1 AVR (or a 2.1 switch that goes to a 2.0 AVR and a 2.1 display, as for SamuriHL). How many people fit that description?
That's probably why no one is in a hurry to fix this.
SamuriHL
25th September 2023, 00:34
I wonder if it's related to FRL at all. In my configuration I use my HTPC for gaming so I have gsync/vrr enabled. JRiver sets it to 23.976 when a movie starts but gsync/vrr is still technically enabled. Just throwing another possible idea out there.
Manni
25th September 2023, 00:39
I wonder if it's related to FRL at all. In my configuration I use my HTPC for gaming so I have gsync/vrr enabled. JRiver sets it to 23.976 when a movie starts but gsync/vrr is still technically enabled. Just throwing another possible idea out there.
I disable Gsync in the nVidia CP settings and have vertical sync on. I still have the Atmos drop outs issue with the 3090/4070, even when going through a HDMI 2.0 input in the AVR.
Nothing to do with FRL given that it also happens with 18Gbs speeds (TDMS) and no VRR. Though the bug in the recent nVidia drivers with 4K23 12bits in that configuration (HDMI 2.1 GPU going through HDMI 2.0 AVR input) adds insult to injury and should be avoided, until fixed by nVida (that's DEFINITELY a driver issue).
SamuriHL
25th September 2023, 00:58
I figured I'd at least throw out a possible idea given that it's happening on 3x and 4x series cards. I'm using 10 bit RGB FULL right now for my settings. With gsync enabled.
Charky
25th September 2023, 08:06
3090 (latest drivers) -> Denon X2800H -> LG 65C2.
Atmos setup with dedicated speakers. Everyhing is bitstreamed.
Everything seems to be working normally. No "dropouts", whatever that means. My AVR still display "Atmos" and I didn't hear anything wrong. That goes with both MPC-BE/madvr and Jriver/JRVR (I currently use both, haven't decided on a favorite yet, but I like having several options, considering madvr is dead).
Manni
25th September 2023, 17:33
3090 (latest drivers) -> Denon X2800H -> LG 65C2.
Atmos setup with dedicated speakers. Everyhing is bitstreamed.
Everything seems to be working normally. No "dropouts", whatever that means. My AVR still display "Atmos" and I didn't hear anything wrong. That goes with both MPC-BE/madvr and Jriver/JRVR (I currently use both, haven't decided on a favorite yet, but I like having several options, considering madvr is dead).
Thanks Charky for stepping forward :)
Assuming that you've played a full Atmos film many times (it currently often takes at least one hour to get an Atmos drop out in jRiver), please could you provide more details:
Exact OS version (Win 10 or Win 11, Pro or not, build etc)
Exact Driver version and type (standard or DCH, game ready or studio)
Exact settings in the nVidia Cpanel, especially vsync, gsync, power
Exact settings for resolution (4K, refresh rate, bit depth, RGB or YCC)
Exact setting for bitstreaming in jRiver (which audio device do you select, is it using WASAPI or Direct Sound)
Please focus on jRiver with JRVR. As Nevcairiel/Hendrik requested a log in the jRiver thread, I've done more tests today with both jRiver (using JRVR to rule out madVR) and MPC-BE.
See all the details here: https://yabb.jriver.com/interact/index.php/topic,136525.100.html from post #128.
I get Atmos drop outs around the one hour mark with jRiver, worst results with MPC-BE with internal filters and best results (least dropped frames, no Atmos audio drop) with MPC-BE using the latest version of LAV Filters (0.77.2.3).
This seems to point to an issue specific to jRiver rather than a driver issue, so I suggest you post all the info requested above in the jRiver thread linked above, once you've confirmed that you don't get any audio drop outs, so that NevCairiel/Hendrik gets all the info in the same place.
That way, those interested (most likely jRiver users, like myself, yourself or SamuriHL) can follow that thread and we won't spam the others here as it's likely irrelevant.
Of course, if anyone gets Atmos drop outs using the latest version of LAV 0.77.2.3 and MPC-BE and the latest nVidia drivers, feel free to post here or even to create another thread and link it here.
SamuriHL
25th September 2023, 17:45
Manni do you get any dropouts in DTS formats? I was watching Atomic Blonde last night and I got a bunch of dropouts in the DTS:X track. I've never usually had an issue with DTS based audio.
Manni
25th September 2023, 17:54
Manni do you get any dropouts in DTS formats? I was watching Atomic Blonde last night and I got a bunch of dropouts in the DTS:X track. I've never usually had an issue with DTS based audio.
I could try watching Atomic Blonde, there are worse films to watch again and I'm getting tired of John Wick 3 :)
I haven't experienced dropouts with DTS:X yet, but there are much less DTS:X titles than Atmos titles, so it could just be statistics. I'll re-watch Atomic Blonde with the E-GPU setup that includes the 3090 and I'll let you know.
I assume this was with jRiver using WASAPI, correct? I get dropouts all the time with Direct Sound, even using the 1080ti, so I only use WASAPI with the Denon/nVidia out.
Charky
25th September 2023, 18:07
Here we go.
Exact OS version: Win 11 Pro 22H2 22621.2283
Exact Driver version and type: game ready, 537.42
Exact settings in the nVidia Cpanel: everything default
Exact settings for resolution: 2160p23, RGB 12 bits
Exact setting for bitstreaming in jRiver: default [Wasapi]
I've got a copy of Indiana Jones 5 with an Atmos track i'm supposed to watch this evening. I'll use Jriver and update if I see/hear anything out of the ordinary.
SamuriHL
25th September 2023, 18:20
I could try watching Atomic Blonde, there are worse films to watch again and I'm getting tired of John Wick 3 :)
I haven't experienced dropouts with DTS:X yet, but there are much less DTS:X titles than Atmos titles, so it could just be statistics. I'll re-watch Atomic Blonde with the E-GPU setup that includes the 3090 and I'll let you know.
I assume this was with jRiver using WASAPI, correct? I get dropouts all the time with Direct Sound, even using the 1080ti, so I only use WASAPI with the Denon/nVidia out.
Yup, always WASAPI for me and definitely JRiver. I was testing it with the new madvr settings Javs found and man, what a picture now! If we can get this audio thing figured out that'd be even better.
Manni
25th September 2023, 20:24
Yup, always WASAPI for me and definitely JRiver. I was testing it with the new madvr settings Javs found and man, what a picture now! If we can get this audio thing figured out that'd be even better.
I watched Atomic Blonde, details in the jRiver thread.
Please post any follow-up question or info there, it's a jRiver issue as far as I'm concerned and it's better for Nev/Hendrik if all the info is in the jRiver thread.
Annoying for me to repeat everything in two threads, and here we're spamming those who are not interested in jRiver.
Mordred
8th October 2023, 20:07
I've been running nvidia driver 536.23 for over a week now and everything appears to be okay except they still haven't fixed the HDR switching issue that's been happening in every version after 525.25. I still have to restart the video card every few days to keep HDR switching working. I made sure to use DDU (safe mode) when upgrading.
Just confirming that this is STILL happening with 537.42. Don't know how NVidia still hasn't fixed this issue yet.
Manni
8th October 2023, 22:01
Just confirming that this is STILL happening with 537.42. Don't know how NVidia still hasn't fixed this issue yet.
Did you try to reset your madVR settings to default?
Mordred
9th October 2023, 04:06
Did you try to reset your madVR settings to default?No, but how would that help? Switching in and out of HDR mode works fine for about a week or more and then suddenly it just won't do it. Falling back to 522.25 (the quoted post references a 525.25 that doesn't exist) it'll work perfectly for months without a reboot. I'm sticking with 537.42 for now to see if I can disable the graphics card and then re-enable to get switching back.
Manni
9th October 2023, 16:41
No, but how would that help? Switching in and out of HDR mode works fine for about a week or more and then suddenly it just won't do it. Falling back to 522.25 (the quoted post references a 525.25 that doesn't exist) it'll work perfectly for months without a reboot. I'm sticking with 537.42 for now to see if I can disable the graphics card and then re-enable to get switching back.
I'm only telling you that I had the same issue after swapping GPUs, and that resetting the madVR settings resolved it. It now works fine with the latest drivers (after DDU and clean install).
You can always export your madVR registry settings and save the settings.bin somewhere before deleting them and resetting to default. If it doesn't help, then go back to your previous settings. If it does, redo your settings.
There is something rotten with madVR settings that goes wrong randomly, even when you combine the EDIDs. Resetting and starting from scratch, especially after a GPU swap, is the only thing that worked for me.
Manni
10th October 2023, 14:57
No, but how would that help? Switching in and out of HDR mode works fine for about a week or more and then suddenly it just won't do it. Falling back to 522.25 (the quoted post references a 525.25 that doesn't exist) it'll work perfectly for months without a reboot. I'm sticking with 537.42 for now to see if I can disable the graphics card and then re-enable to get switching back.
Apologies, I just realised that we were in the drivers thread and not in the madVR thread. If you're talking about switching in and out of HDR mode in the OS, then it has indeed nothing to do with madVR settings.
Mordred
11th October 2023, 22:10
Apologies, I just realised that we were in the drivers thread and not in the madVR thread. If you're talking about switching in and out of HDR mode in the OS, then it has indeed nothing to do with madVR settings.So I'm experiencing this issue with DSPlayer Kodi using madVR, so maybe there is something there. Will try exporting madVR settings and resetting to see if that fixes anything.
I also had tried manually enabling HDR mode in Win10 settings because I'd heard that would work, but that just gave me a black screen/no-signal with no way to disable. I had to boot into safe-mode and uninstall the display driver to get a display back. Old Nvidia driver didn't have that problem either.
Manni
12th October 2023, 11:11
So I'm experiencing this issue with DSPlayer Kodi using madVR, so maybe there is something there. Will try exporting madVR settings and resetting to see if that fixes anything.
I also had tried manually enabling HDR mode in Win10 settings because I'd heard that would work, but that just gave me a black screen/no-signal with no way to disable. I had to boot into safe-mode and uninstall the display driver to get a display back. Old Nvidia driver didn't have that problem either.
DSplayer Kodi with madVR support is now quite long in the tooth, so is Windows 10.
I use Windows 11 and the latest drivers, and have no issues switching the OS or madVR to HDR mode.
I occasionally have issues getting madVR to do HDR to SDR tonemapping properly, and that's when resetting madVR defaults to defaults resolves the issue (for a while). Rebooting also helps.
I use jRiver MC as a player, and I never have any of these issues with JRVR as a renderer, so once you've resolved the switching to HDR with the OS, you might want to try a supported, up-to-date player and renderer, it might help you to pinpoint the issue more precisely.
If you have issues switching to HDR with the OS, I'd start with resolving that.
Mordred
14th October 2023, 08:15
Well I'm not going to abandon DSPlayer Kodi since I have it setup exactly the way I want, it works and I don't really need any of the newer features in Kodi. Also not looking to upgrade to Win11 anytime soon.
It's clearly an Nvidia driver problem, and maybe it only affects people like me, but there are definitely others out there since Aquanash from this forum was how I discovered which drivers worked in the first place.
nevcairiel
14th October 2023, 08:38
You can call it a driver problem, but madVR using legacy methods to do HDR output certainly doesn't help it. madVRs focus has been on tone mapping ever since it was created, and pass-through got little to no love.
alexmain
15th October 2023, 16:52
https://www.nvidia.com/en-us/geforce/news/call-of-duty-modern-wafare-3-pc-beta-game-ready-driver/
https://www.nvidia.com/download/driverResults.aspx/212701/en-us/
Nvidia GeForce 537.58 WHQL graphics driver released.
Thanks for sharing it. I hope it will resolve the issue for me, since I still have version 537.42 of my Nvidia drivers.
KrazyLurt
17th October 2023, 16:14
Tried 545.84 just now, it broke scrolling in both Firefox and Chromium for me. Probably a v-sync issue, it usually is. Reverted back to prev. drivers , and it works fine again.
Klaus1189
17th October 2023, 19:40
Windows 10 transparency effects are borked for me with new driver. If enabled the taskbar is deepblack. Which was always the other way round. It was deep black when disabled.
Also the effects do not appear when enabled.
Latest Win10 22H2 19045.3570
Klaus1189
18th October 2023, 09:48
The issues was right there after display flickered during driver install. I did a restart and issues persisted. Today I started normally and issue is gone. strange.
However I discovered that HDR passthrough (yesterdasy and still today) next to fullscreen exclusive/windowed now laos plain windowed works too. Up to now the HDR metadata wouldn't be applied in this mode.
Klaus1189
26th October 2023, 18:10
Stay away from 545.XX branch :(
Manni
27th October 2023, 09:04
Stay away from 545.XX branch :(
Can you be more specific?
Klaus1189
27th October 2023, 11:02
Wrong color on Desktop, deep black taskbar when transparent effects are on. These effects are also not working. Way more dropped frames and presentazion glitches with any renderer and/or filter combo. Same for Kodi. I switched back to latest 537.xx Studio driver. Hope Nvidia doesn't rush out Studio drivers like last 545.xx drivers. This has to be seen by a tester.
I have RTX40xx FE, if that matters.
nevcairiel
27th October 2023, 15:40
What does "wrong color on desktop" even mean?
Its all been perfectly smooth for me with a 40 series card.
Klaus1189
27th October 2023, 16:58
Colors are oversaturated and hurt my eyes. It doesn't make a difference if I use limited or full. It is always the same, same for RGB vs. YCbCr 4:4:4
LG TV adjusts accordingly so image always looks the same. But going back to latest 537.xx driver everything is fine like it was for the past months (over a year) since I have it - day one :)
Much more trouble are the dropped frames, which get worse when I play a 1080i60 file ripped from a blu-ray and use hardware deinterlacer. I get so many dropped frames, but using software deinterlacer and software decoder it is fine. Also in Kodi 21 beta 1.
Same here - going back to 537.xx -> issues are fixed.
Very strange branch ...
huhn
28th October 2023, 08:27
did you ever use an VR application?
i have only queue issues on this driver using a 4060.
whitestar999
28th October 2023, 10:34
I have gone through the driver issues list. I recently got a 2060 & as per my understanding v527.37 game ready driver should be fine for my usage on win 10 22h2. Is this correct or did I miss something/should be aware of? Usage is only going to be playing mainly 1080p sdr videos/hdr videos & some 420p/720p sdr videos(animated content & legacy stuff for which higher resolution not available) on a 1080p non-hdr TV screen for now & on a 4k hdr TV screen in future. If any tips/info then please let me know that too. I currently use 1050Ti with NGU luma upscaling as the most resource heavy option in madvr last official build.
Klaus1189
28th October 2023, 11:50
did you ever use an VR application?
i have only queue issues on this driver using a 4060.
No, I didn't use any VR app/game.
What do you mean with queue issues?
Klaus1189
28th October 2023, 11:51
I have gone through the driver issues list. I recently got a 2060 & as per my understanding v527.37 game ready driver should be fine for my usage on win 10 22h2. Is this correct or did I miss something/should be aware of? Usage is only going to be playing mainly 1080p sdr videos/hdr videos & some 420p/720p sdr videos(animated content & legacy stuff for which higher resolution not available) on a 1080p non-hdr TV screen for now & on a 4k hdr TV screen in future. If any tips/info then please let me know that too. I currently use 1050Ti with NGU luma upscaling as the most resource heavy option in madvr last official build.
Latest 537.xx is fine for me.
whitestar999
28th October 2023, 13:21
Latest 537.xx is fine for me.
So no issues with 537.xx on 22h2 & everything works fine except for that "HDR passthrough works also in window (metadata is used) (besides Fullscreen exclusive + Fullscreen windowed)" fix in 545.84 & the issues in win 10 transparency & worse performance as reported by you in previous posts?
Klaus1189
28th October 2023, 14:10
537.xx is fine, 545 will make trouble, yes.
But in 545.xx HDR colors are also correct in small window, which was never the case before.
(HDR passthrough)
But other major issues there so I do not recommend.
Latest 537.xx Studio and you can use latest and greatest driver, but it is Studio driver.
whitestar999
28th October 2023, 21:51
537.xx is fine, 545 will make trouble, yes.
But in 545.xx HDR colors are also correct in small window, which was never the case before.
(HDR passthrough)
But other major issues there so I do not recommend.
Latest 537.xx Studio and you can use latest and greatest driver, but it is Studio driver.
Got it. So any specific thing/fact I should know about studio driver other than the fact that it updates less frequently than game ready driver.
Klaus1189
29th October 2023, 07:50
No, it is better tested and so more stable and reliable.
huhn
29th October 2023, 19:22
No, I didn't use any VR app/game.
What do you mean with queue issues?
the presentation or renderer queue sometimes glitch out a restart usual fixes this issue. could be utterly unrelated to the driver such issue are not uncommon with madvr for years now.
Klaus1189
29th October 2023, 20:26
OK, how do I notice this behavior? Dropped frames, no video no audio, ...?
Restart of player or pc?
huhn
30th October 2023, 07:58
ahh the video stutters?
just player restart on my side.
Klaus1189
30th October 2023, 09:26
Sometimes during playback or right at start?
huhn
30th October 2023, 17:09
the queue just stay empty sometimes so a playback start.
i recommend you to ignore this.
Klaus1189
30th October 2023, 18:58
Ok, I was just curious
Klaus1189
31st October 2023, 17:36
https://www.nvidia.com/en-us/geforce/news/call-of-duty-modern-warfare-3-geforce-game-ready-driver/
https://www.nvidia.com/download/driverResults.aspx/216299/en-us/
Nvidia GeForce 546.01 WHQL graphics driver released, Win10 bug not yet fixed.
Which one?
GTPVHD
31st October 2023, 19:51
https://blogs.windows.com/windowsexperience/2023/10/31/how-to-get-the-windows-11-2023-update/
https://www.microsoft.com/software-download/windows11
Win11 2023 Update version 23H2 includes WDDM 3.2 and Shader Model 6.8, if anyone wants to test. No WDDM 3.2 graphics drivers have been officially released yet, afaik.
https://microsoft.github.io/DirectX-Specs/d3d/HLSL_ShaderModel6_8.html
Klaus1189
31st October 2023, 20:37
https://www.nvidia.com/en-us/geforce/news/call-of-duty-modern-warfare-3-geforce-game-ready-driver/
https://www.nvidia.com/download/driverResults.aspx/216299/en-us/
Nvidia GeForce 546.01 WHQL graphics driver released, Win10 bug not yet fixed.
Which one?
Again, please let me know.
Klaus1189
1st November 2023, 07:18
Ok thanks.
Klaus1189
2nd November 2023, 18:01
I did some more tests with 545.xx/546.xx branch
I does not look good. DXVA processing time is 2 ... 2,5 times increased compared to 537.xx. No settings changed in MPC-BE and madVR, just driver downgrade.
I tested a DVD rip, interlaced. I use DXVA deinterlacer. It looks not smooth either, but no dropped frame, delayed frame, or presentation glitch according to madVR.
And they released a Studio driver based on 546.xx :scared:
huhn
2nd November 2023, 21:52
DXVA rendertimes have no effect on anything i still have 1 ms and even 15 ms are completely fine.
deint is close to utterly broken not amd level broken yet but close.
looks like NN for line doubling sometimes and sometimes it is inverse telecine.
after reading your rendertimes i was hoping they fixed the scaler that only triggers at 360p and below but nope still low end here bilinear or soemthing.
Klaus1189
3rd November 2023, 18:01
Thanks, I take a look.
Yes, transparency effects are working now. I do further tests.
ashlar42
3rd November 2023, 19:09
Transparency is fixed in W10. Although I have to say I did not experience the bad performance that had been reported for 345.xx ...
whitestar999
4th November 2023, 22:22
Transparency is fixed in W10. Although I have to say I did not experience the bad performance that had been reported for 345.xx ...
You mean 545.xx
KrazyLurt
14th November 2023, 15:17
No scroll bug for me with Firefox 119 or Chromium 119 using Nvidia GeForce 546.17 WHQL.
Manni
14th November 2023, 23:20
Re the discussion we had a while ago here about nVidia HDMI 2.1 GPU getting a black screen in 4K23 in 10/12bits when using an HDMI 2.0 input of the AVR, I found a workaround which is to go back to 532.03 or earlier.
Not ideal of course, but I have no problem getting 10/12bits in 4K23 with the 3090 using that version (or previous ones). It also resolves frame drops in HDR Passthrough with jriver/JRVR. Looks like the architecture change from 535.98 might have broken some stuff with the 3xxx family.
I also noticed that the latest drivers forced the same bit depth on all frame rates (not possible to set a different bit depth for 60p and 23p). No such issue with up to 532.03, though I believe that was broken much later.
So it looks like I’ll stay with 532.03 with the 3090 for as long as it works. This is with win11 pro x64 22H2 or 23H2. YMMV.
ashlar42
4th December 2023, 00:12
I have been experiencing a bug with all drivers supporting RTX 4070 I have tried (and I have tried several), where once I apply custom resolutions through CRU and restart... black screen and no way to get a working computer until I reboot in safe mode and remove the edid override from the registry.
And now I'm stuck with this crappy 23.976 one frame drop every 1.06 hours...
whitestar999
4th December 2023, 09:18
I have been experiencing a bug with all drivers supporting RTX 4070 I have tried (and I have tried several), where once I apply custom resolutions through CRU and restart... black screen and no way to get a working computer until I reboot in safe mode and remove the edid override from the registry.
And now I'm stuck with this crappy 23.976 one frame drop every 1.06 hours...
Is that even noticeable to human eyes or you mean you are not happy with 23.976 fps?
huhn
4th December 2023, 10:34
yes a stutter of nearly 42 ms is very noticable to the human eye.
Manni
4th December 2023, 11:39
I have been experiencing a bug with all drivers supporting RTX 4070 I have tried (and I have tried several), where once I apply custom resolutions through CRU and restart... black screen and no way to get a working computer until I reboot in safe mode and remove the edid override from the registry.
And now I'm stuck with this crappy 23.976 one frame drop every 1.06 hours...
Are you using 4K 10/12 bits output from the 4xxx on a HDMI 2.0 input of your AVR? That’s a known issue of recent drivers. I posted recently the last working one for 3090 (I use 531.61 studio but 532.03 game ready should work too), It should work with the 4070. Alternatively, you can try to use 8bits as a workaround.
One frame drop every hour or so is normal if you’re bitstreaming. Using LPCM should get rid of it, again with recent enough drivers.
Manni
4th December 2023, 12:58
yes a stutter of nearly 42 ms is very noticable to the human eye.
Yeah but we're talking about one frame drop every hour or so here. I do notice them if they happen in a moving shot, but I can live with a couple of drops per film.
ashlar42
4th December 2023, 22:00
Is that even noticeable to human eyes or you mean you are not happy with 23.976 fps?
It means a couple of frame drops for an average movie. When they happen I always notice. It bothers me, especially because it's due to a bug. "Funny" thing is that this started to happen when I had pretty much finished fine tuning 23.976, 24 and 59.94 (25 was fine already).
Are you using 4K 10/12 bits output from the 4xxx on a HDMI 2.0 input of your AVR? That’s a known issue of recent drivers. I posted recently the last working one for 3090 (I use 531.61 studio but 532.03 game ready should work too), It should work with the 4070. Alternatively, you can try to use 8bits as a workaround.
One frame drop every hour or so is normal if you’re bitstreaming. Using LPCM should get rid of it, again with recent enough drivers.
I am using 4K 10 bits on a HDMI 2.1 input of my AVR. Not 2.0.
I will try using 8 bits, as you suggest.
ashlar42
5th December 2023, 00:02
Manni, thank you! Setting the display at 8 bit worked. After fine tuning the custom resolutions I set it at 10 bits and everything works fine, driver 546.17 (on Windows 10).
Manni
5th December 2023, 00:59
Manni, thank you! Setting the display at 8 bit worked. After fine tuning the custom resolutions I set it at 10 bits and everything works fine, driver 546.17 (on Windows 10).
Glad I could help and it’s resolved for you now.
Siso
5th December 2023, 21:04
ashlar42, you have rtx 4070 right? I bought rtx 4070 ti, which driver works best for you, and what settings do you use in nvidia control panel and in madvr presented frames in advance?
ashlar42
5th December 2023, 22:04
ashlar42, you have rtx 4070 right? I bought rtx 4070 ti, which driver works best for you, and what settings do you use in nvidia control panel and in madvr presented frames in advance?
I am using currently 546.17. 1 frame presented in advance for madVR.
As far as settings... I set Vertical Sync to On and kept Power Management Mode at Normal.
Siso
6th December 2023, 00:45
I'm on 546.17 too. Why did you choose normal power management mode? Why not maximum performance? Also in madvr - D3D9 or D3D11? Lav video decoder is set to what?
ashlar42
6th December 2023, 13:56
I'm on 546.17 too. Why did you choose normal power management mode? Why not maximum performance? Also in madvr - D3D9 or D3D11? Lav video decoder is set to what?
madVR set tp D3D11, better decoding performance and 10 bit.
Normal power because I use it mainly for HTPC purposes. I do gaming, but it's secondary. As such, I prefer having a cooler machine, that has fans rotating slowly, so as to avoid unwanted noise.
ashlar42
6th December 2023, 15:16
Glad I could help and it’s resolved for you now.Unfortunately it isn't and I've been kicking myself for the past two hours for my stupidity.
I should have created a system restore point when I had everything working. I didn't. Probably thinking "now I've got the secret recipe"...
I went to "play" with settings relevant to VRR and DLSS 3.5... ended up having the machine crash to black screen and... everything started acting up like it was doing before.
No matter the color bit settings, now I can't use CRU. No matter the driver version (tried the ones you suggested, tried others). I'm so f%$£ fed up with this crap.
Manni
6th December 2023, 16:58
Unfortunately it isn't and I've been kicking myself for the past two hours for my stupidity.
I should have created a system restore point when I had everything working. I didn't. Probably thinking "now I've got the secret recipe"...
I went to "play" with settings relevant to VRR and DLSS 3.5... ended up having the machine crash to black screen and... everything started acting up like it was doing before.
No matter the color bit settings, now I can't use CRU. No matter the driver version (tried the ones you suggested, tried others). I'm so f%$£ fed up with this crap.
The only thing I can suggest is try a HDMI 2.0 input in your AVR and/or change the EDID in your display/PJ to a HDMI 2.0 EDID if you can (EDID B in the latest JVCs), with the driver in my sig if you have a 3xxx GPU. That’s what I had to do to get my 3090 to work reliably with 4K24 12bits.
When it works, make a system image, anything can break it at anytime if you change anything or allow internet updates.
ashlar42
6th December 2023, 22:48
The only thing I can suggest is try a HDMI 2.0 input in your AVR and/or change the EDID in your display/PJ to a HDMI 2.0 EDID if you can (EDID B in the latest JVCs), with the driver in my sig if you have a 3xxx GPU. That’s what I had to do to get my 3090 to work reliably with 4K24 12bits.
When it works, make a system image, anything can break it at anytime if you change anything or allow internet updates.
Yeah, problem is, that way, I'd lose 120Hz for games. Which is not *that* of a dealbreaker but still it's quite annoying, considering I know it can work correctly. Anyway, thanks for all the help.
ashlar42
7th December 2023, 16:41
Ok, crossing fingers, I should have solved my problem. I will list what I did, as a reminder to myself and for other users that might find it useful in the future. I have NO idea if the sequence of things I did is relevant or not. Nvidia drivers have bugs, it could be random for all I know.
In any case. Starting from the regular, standard EDID after clean driver installation, I did the following.
1. Leave Output Color Depth in Nvidia control panel at default setting (Use default colour settings).
2. Opened CRU, deleted some useless resolutions (useless for me) from CTA-861 extension block. Saved and restarted the video driver (with CRU's restart64.exe).
3. Imported the settings I wanted for custom resolutions (remember, they used to work before the mishap with black screens upon restart of the video driver). Restarted the video driver. And... wow, it worked!
4. Set Output Color Depth in Nvidia control panel to Use Nvidia Settings. This doesn't change anything, theoretically, but it probably "saves" something somewhere. So you go from 8bit color depth to 8bit color depth. But that's apparently needed.
5. Restarted the machine.
6. Set Output Color Depth at 10bit. Apply. Done.
7. Create a restore point. I actually did it after #3 and redid it after #6.
Points 4 and 5... I tried to do that because I had already reached successfully #3 but when I went straight from "Use default colour settings" to Nvidia settings at 10 bit... it didn't like it. Black screens, need to reboot, etc.
Again, I stress... this is just what I did, no guarantee it's gonna work for anyone else but I thought it was worth reporting...
I now have 10 bit video playback both in Kodi and madVR (with correctly tuned refresh rates) and VRR and HDR are working for games.
whitestar999
10th December 2023, 04:55
Ok, crossing fingers, I should have solved my problem. I will list what I did, as a reminder to myself and for other users that might find it useful in the future. I have NO idea if the sequence of things I did is relevant or not. Nvidia drivers have bugs, it could be random for all I know.
In any case. Starting from the regular, standard EDID after clean driver installation, I did the following.
1. Leave Output Color Depth in Nvidia control panel at default setting (Use default colour settings).
2. Opened CRU, deleted some useless resolutions (useless for me) from CTA-861 extension block. Saved and restarted the video driver (with CRU's restart64.exe).
3. Imported the settings I wanted for custom resolutions (remember, they used to work before the mishap with black screens upon restart of the video driver). Restarted the video driver. And... wow, it worked!
4. Set Output Color Depth in Nvidia control panel to Use Nvidia Settings. This doesn't change anything, theoretically, but it probably "saves" something somewhere. So you go from 8bit color depth to 8bit color depth. But that's apparently needed.
5. Restarted the machine.
6. Set Output Color Depth at 10bit. Apply. Done.
7. Create a restore point. I actually did it after #3 and redid it after #6.
Points 4 and 5... I tried to do that because I had already reached successfully #3 but when I went straight from "Use default colour settings" to Nvidia settings at 10 bit... it didn't like it. Black screens, need to reboot, etc.
Again, I stress... this is just what I did, no guarantee it's gonna work for anyone else but I thought it was worth reporting...
I now have 10 bit video playback both in Kodi and madVR (with correctly tuned refresh rates) and VRR and HDR are working for games.
Is that correct?
angmav
13th December 2023, 22:35
Can anyone give me any advise i am running win 10 i have a denon x8500h hdmi 2.0 running into jvc rs2000 i cant get 12 bit rgb working anyone with a similar setup got it working if yes what version of nvidia are you running ?
Sent from my iPhone using Tapatalk
Manni
14th December 2023, 00:52
Can anyone give me any advise i am running win 10 i have a denon x8500h hdmi 2.0 running into jvc rs2000 i cant get 12 bit rgb working anyone with a similar setup got it working if yes what version of nvidia are you running ?
Sent from my iPhone using Tapatalk
Use the driver in my sig (or earlier). nVidia broke 4K 10/12bits support for 3xxx series after it when using an HDMI 2.0 input in an AVR, as well as a few other things
Grincho
14th December 2023, 13:04
Use the driver in my sig (or earlier). nVidia broke 4K 10/12bits support for 3xxx series after it when using an HDMI 2.0 input in an AVR, as well as a few other things
Manni, FYI, not only when using HDMI 2.0, but HDMI 2.1 as well. I went from Denon AVR-X7200WA (2015, HDMI 2.0) to Denon AVC-X3800H (2022, HDMI 2.1) thinking that it would solve the issue, but the problem is exactly the same - blank screen on my PJ when switching to 10/12 bit in 4K. I have RTX 4080 GPU.
Therefore, the problem is the same for RTX 3xxx or 4xxx series, HDMI 2.0 or 2.1.
Btw, if you are using DisplayPort-to-HDMI adapter, than AVR can pass 4K with 10/12bits, but in that case the sound is limited to 24-bit 48 kHz (with the direct HDMI connection it is up to 192 kHz).
Grincho
14th December 2023, 13:15
Manni, FYI, not only when using HDMI 2.0, but HDMI 2.1 as well. I went from Denon AVR-X7200WA (2015, HDMI 2.0) to Denon AVC-X3800H (2022, HDMI 2.1) and the problem is exactly the same - blank screen on my PJ. I have RTX 4080 GPU.
Btw, if you are using DisplayPort-to-HDMI adapter, than AVR can pass-through 4K with 10/12bits.
The below information might shed some light on the problem.
If I go to AVR's Setup-General-Information-Video-HDMI, I can see some strange behavior when 10/12bit is chosen with 4K/23,24,30 in nVidia Control Panel:
With 532.03 driver or earlier AVR shows following info. Resolution: 4K24 → 4K24, Pixel Depth: 10bit → 10bit (signal is accepted by the screen).
After 532.03 driver. Resolution: 4K24 3D → 4K24 3D, Pixel Depth: 10bit → 10bit (signal is NOT accepted by the screen, blank screen). See the picture attached.
If you switch to 8bit in NV Control Panel, that strange "3D" flag disappears and the video passes to the display normally.
With any driver AVR shows the following info. Resolution: 4K24 → 4K24, Pixel Depth: 8bit → 8bit. See the picture attached.
So, the drivers newer than 532.03 sending some strange "3D" flag to an AVR when you switch to 10/12bit in 4k23, which a display can't accept.
nevcairiel
14th December 2023, 19:42
Manni, FYI, not only when using HDMI 2.0, but HDMI 2.1 as well. I went from Denon AVR-X7200WA (2015, HDMI 2.0) to Denon AVC-X3800H (2022, HDMI 2.1) thinking that it would solve the issue, but the problem is exactly the same - blank screen on my PJ when switching to 10/12 bit in 4K. I have RTX 4080 GPU.
I use 4K 10-bit just fine with HDMI 2.1 on my 3070 Ti to an LG G1 through a Denon AVC-X4700H, with the latest drivers.
Manni
14th December 2023, 22:21
Manni, FYI, not only when using HDMI 2.0, but HDMI 2.1 as well. I went from Denon AVR-X7200WA (2015, HDMI 2.0) to Denon AVC-X3800H (2022, HDMI 2.1) thinking that it would solve the issue, but the problem is exactly the same - blank screen on my PJ when switching to 10/12 bit in 4K. I have RTX 4080 GPU.
Therefore, the problem is the same for RTX 3xxx or 4xxx series, HDMI 2.0 or 2.1.
Btw, if you are using DisplayPort-to-HDMI adapter, than AVR can pass 4K with 10/12bits, but in that case the sound is limited to 24-bit 48 kHz (with the direct HDMI connection it is up to 192 kHz).
The below information might shed some light on the problem.
If I go to AVR's Setup-General-Information-Video-HDMI, I can see some strange behavior when 10/12bit is chosen with 4K/23,24,30 in nVidia Control Panel:
With 532.03 driver or earlier AVR shows following info. Resolution: 4K24 → 4K24, Pixel Depth: 10bit → 10bit (signal is accepted by the screen).
After 532.03 driver. Resolution: 4K24 3D → 4K24 3D, Pixel Depth: 10bit → 10bit (signal is NOT accepted by the screen, blank screen). See the picture attached.
If you switch to 8bit in NV Control Panel, that strange "3D" flag disappears and the video passes to the display normally.
With any driver AVR shows the following info. Resolution: 4K24 → 4K24, Pixel Depth: 8bit → 8bit. See the picture attached.
So, the drivers newer than 532.03 sending some strange "3D" flag to an AVR when you switch to 10/12bit in 4k23, which a display can't accept.
I use 4K 10-bit just fine with HDMI 2.1 on my 3070 Ti to an LG G1 through a Denon AVC-X4700H, with the latest drivers.
You need to be precise guys when discussing this kind of stuff, we've been through this many times, the issue is very clear:
1) There is no black screen issue with 4K24 at 10/12bits with recent nVidia drivers if you use an HDMI 2.1 GPU with an HDMI 2.1 input in the AVR. I have no issue trying to get 4K24 10/12bits with the latest drivers if I use the single HDMI 2.1 input of my Denon X8500HA. So it's completely normal that Nevcairiel has no issue. He needs to try with a HDMI 2.0 input on the AVR to reproduce this. The issue with recent drivers is also only with 4K24 in 10/12bits, so there is no such issue with 4K60 or 4K24 8bits.
2) The issue only arises if you try to use a HDMI 2.1 GPU with the HDMI 2.0 input of an AVR (not sure if it matters if the AVR is HDMI 2.1 for some of the inputs, or if it would also happen if the AVR is an HDMI 2.0 AVR with no HDMI 2.1 input, I haven't tested that). It's ONLY in that case that you get a black screen with 4K24 10/12bits. Grincho, I don't know if all the inputs on your X3800H are HDMI 2.1, but you need to check. You will get different results depending on each specific input if they are not all HDMI 2.1, as is the case with my X8500HA, where all the inputs have the issue except the single HDMI 2.1 one. You shouldn't get any issue with a recent driver when using a HDMI 2.1 input (like Nevcairiel), and you should get it with any HDMI 2.0 input.
3) The recent drivers are only broken for some things (this 4K24 10/12bits issue with a HDMI 2.0 input, frame drops with JRVR in HDR passthrough) with a 3xxx series. I have no idea if they are also broken with a 4xxx series, I haven't tested for that when I briefly had a 4070 to test other stuff. Quite often, after a while, recent drivers can make things worse for EOL products, so unless you really need to update them for a specific game or software compatibility, it's safer to stick with the latest working version for as long as it works. In my case (3090), it's the driver version in my sig (the game ready version 532.03 just after it also works, the driver breaks when the file size changes significantly, suggesting a new architecture, I've edited my sig to reflect this).
Grincho
15th December 2023, 07:36
You need to be precise guys when discussing this kind of stuff, we've been through this many times, the issue is very clear:
2) The issue only arises if you try to use a HDMI 2.1 GPU with the HDMI 2.0 input of an AVR (not sure if it matters if the AVR is HDMI 2.1 for some of the inputs, or if it would also happen if the AVR is an HDMI 2.0 AVR with no HDMI 2.1 input, I haven't tested that). It's ONLY in that case that you get a black screen with 4K24 10/12bits. Grincho, I don't know if all the inputs on your X3800H are HDMI 2.1, but you need to check. You will get different results depending on each specific input if they are not all HDMI 2.1, as is the case with my X8500HA, where all the inputs have the issue except the single HDMI 2.1 one. You shouldn't get any issue with a recent driver when using a HDMI 2.1 input (like Nevcairiel), and you should get it with any HDMI 2.0 input.
Manni, X3800H has all HDMI inputs 2.1 (it's 2022 model, the latest one). My video card is RTX 4080 (HDMI 2.1). However, my PJ has only HDMI 2.0b inputs (BenQ x3000i).
From reading this thread I've I got information that "4K24 10/12bits blank screen problem" does not happen with AVR HDMI 2.1 input. That's why I sold my old X7200WA with HDMI 2.0b and bought the latest X3800H (all 2.1 inputs) hoping to solve it.
Unfortunately, for me 4K24 10/12bits blank screen issue is the same as before (switching from HDMI 2.0 to 2.1 AVR input didn't help) with drivers newer than 532.02.
I tried with a new HDMI 2.1 certified cable from PC to AVR as well. I tried all HDMI inputs in the new AVR.
The only thing which works is DisplayPort-to-HDMI adapater (or older driver).
I use 4K 10-bit just fine with HDMI 2.1 on my 3070 Ti to an LG G1 through a Denon AVC-X4700H, with the latest drivers.
All your chain is HDMI 2.1. In my case RTX 4080 and AVR-X3800H are 2.1, but my display is 2.0b. I guess this is the reason, why I still have blank screen with 4k/10,12bit and the latest drivers. I can't think of any other reasons.
Seems, that all the devices in the chain should have 2.1 HDMI inputs, not only AVR.
Goeggel
15th December 2023, 09:46
I have a LG OLED TV B8 (HDMI 2.0 I guess), a RTX 3080 and a Denon AVC-X6700H. The RTX is connected to the Denon's 8K port (HDMI 2.1 I guess).
Since the afore mentioned driver version Game Ready 532.03, I also have the "4K24 10/12bits blank screen problem".
Manni
15th December 2023, 14:31
Manni, X3800H has all HDMI inputs 2.1 (it's 2022 model, the latest one). My video card is RTX 4080 (HDMI 2.1). However, my PJ has only HDMI 2.0b inputs (BenQ x3000i).
From reading this thread I've I got information that "4K24 10/12bits blank screen problem" does not happen with AVR HDMI 2.1 input. That's why I sold my old X7200WA with HDMI 2.0b and bought the latest X3800H (all 2.1 inputs) hoping to solve it.
Unfortunately, for me 4K24 10/12bits blank screen issue is the same as before (switching from HDMI 2.0 to 2.1 AVR input didn't help) with drivers newer than 532.02.
I tried with a new HDMI 2.1 certified cable from PC to AVR as well. I tried all HDMI inputs in the new AVR.
The only thing which works is DisplayPort-to-HDMI adapater (or older driver).
All your chain is HDMI 2.1. In my case RTX 4080 and AVR-X3800H are 2.1, but my display is 2.0b. I guess this is the reason, why I still have blank screen with 4k/10,12bit and the latest drivers. I can't think of any other reasons.
Seems, that all the devices in the chain should have 2.1 HDMI inputs, not only AVR.
Yes, if your display doesn't support HDMI 2.1 it makes sense that you also have the issue, because it's the display instead of the AVR that reports an HDMI 2.0 EDID, which causes this issue with a HDMI 2.1 GPU when using the latest drivers.
It's always a good idea to give as much info about the whole chain to get reliable answers. I assumed that with a HDMI 2.1 GPU and HDMI 2.1 AVR you also had an HDMI 2.1 display / PJ.
In order to resolve this, you could try to get a switch between the display and the AVR that sends an HDMI 2.1 EDID but converts the content to TDMS. It might work. My HD Fury VRROOM does that conversion, but I have no idea if it would solve your issue.
If you need the more recent drivers for gaming, it might be a better idea to upgrade the PJ now to an HDMI 2.1 one and at least get 4K120 in the process, which would be useful for gaming.
Grincho
15th December 2023, 15:49
Yes, if your display doesn't support HDMI 2.1 it makes sense that you also have the issue, because it's the display instead of the AVR that reports an HDMI 2.0 EDID, which causes this issue with a HDMI 2.1 GPU when using the latest drivers.
Interesting, that if I connect RTX 4080 (2.1) directly to PJ (2.0b) there is NO issue with 4K24 10/12bits blank screen. Also, as I mentioned before, there is NO blank screen problem if I use DisplayPort-to-HDMI adapter from GPU to AVR.
The problem is definitely with the drivers above 532.03, which affects AVR passing signal to a display somehow. In my previous post (https://forum.doom9.org/showpost.php?p=1995061&postcount=3186) I pointed out to the strangeness about AVR signal info after upgrading from 532.03 driver (it adds some 3D flag to 4K24/10bit signal).
Grincho
15th December 2023, 16:03
In order to resolve this, you could try to get a switch between the display and the AVR that sends an HDMI 2.1 EDID but converts the content to TDMS. It might work. My HD Fury VRROOM does that conversion, but I have no idea if it would solve your issue.
The easiest and cheapest way to resolve this issue is to buy DisplayPort-to-HDMI adapter. I've got DP 1.4 to HDMI 2.1 on Amazon and it works, no blank screen at 4K/24 10bit. However, you are limited to 24-bit 48 kHz sound (it is not an issue for movies or games).
If you need the more recent drivers for gaming, it might be a better idea to upgrade the PJ now to an HDMI 2.1 one and at least get 4K120 in the process, which would be useful for gaming.
Regarding upgrading PJ - I was thinking to do so, but not for the reason of 2.1 (most of PJ are still 2.0b anyway). BenQ x3000i is one of the best current gen 4K PJs in its price range. I was thinking to sell mine, as it is still quite new and on the warranty and get the latest BenQ HT4550i ($1.7k vs $3k), but it also has HDMI 2.0b.
angmav
15th December 2023, 20:03
I have downgraded to 531.61 dch and still have an issue 12 bit 24hz 2160p blank screen
Anyone have an idea what version to use that does work would be appreciated
Sent from my iPhone using Tapatalk
Manni
16th December 2023, 17:53
The easiest and cheapest way to resolve this issue is to buy DisplayPort-to-HDMI adapter. I've got DP 1.4 to HDMI 2.1 on Amazon and it works, no blank screen at 4K/24 10bit. However, you are limited to 24-bit 48 kHz sound (it is not an issue for movies or games).
Regarding upgrading PJ - I was thinking to do so, but not for the reason of 2.1 (most of PJ are still 2.0b anyway). BenQ x3000i is one of the best current gen 4K PJs in its price range. I was thinking to sell mine, as it is still quite new and on the warranty and get the latest BenQ HT4550i ($1.7k vs $3k), but it also has HDMI 2.0b.
I tried a displayport 1.2 to HDMI 2.0 that I had lying around and RGB 4K23 is limited to 8bits, so can't test if it resolves anything.
Can you confirm that you're using RGB 10/12bits at 4K24 and if so please could you post a link to your adapter on Amazon? I don't mind giving it a try but these can really be a lotery, so I'd rather get a known working one.
All the recent JVCs have HDMI 2.1, but it's not the same budget...
huhn
16th December 2023, 23:33
I use 4K 10-bit just fine with HDMI 2.1 on my 3070 Ti to an LG G1 through a Denon AVC-X4700H, with the latest drivers.
you maybe able to forced HDMI 2.0 by changing some settings in the TV to also force this issue. disabling HD ULTRA HD deep colour is maybe enough to force HDMI 2.0 edid.
Grincho
17th December 2023, 15:25
Can you confirm that you're using RGB 10/12bits at 4K24 and if so please could you post a link to your adapter on Amazon? I don't mind giving it a try but these can really be a lotery, so I'd rather get a known working one.
Yes, I can confirm. I bought this no-name Chinese DP 1.4-to-HDMI 2.1 adapter https://www.amazon.com/Displayport-Adapter-Monitor-Converter-Resolution/dp/B0BPXWZVLK/ref=sr_1_18?crid=2ZE4YMXIL0KWQ&keywords=DisplayPort%2B1.4%2Bto%2BHDMI%2B2.1&qid=1702788094&sprefix=displayport%2B1.4%2Bto%2Bhdmi%2B2.1%2Caps%2C363&sr=8-18&th=1.
It uses VMM7100 chipset from Synaptics - the same as in CableMatters adapters, so the firmware update utility for the equivalent CableMatters product can update the firmware on this Chinese adapter too, resolving some issues if you are on the older firmware. Link to the adapter's firmware update: https://kb.cablematters.com/index.php?View=entry&EntryID=160
Grincho
17th December 2023, 16:09
I have downgraded to 531.61 dch and still have an issue 12 bit 24hz 2160p blank screen
Anyone have an idea what version to use that does work would be appreciated
It is a consensus that 4K/24 10/12bits is working in 531.62 (532.02) when you pass through AVR (direct connection GPU to a display works with any drivers). I guess you have some other problem. What's your setup?
angmav
17th December 2023, 19:54
It is a consensus that 4K/24 10/12bits is working in 531.62 (532.02) when you pass through AVR (direct connection GPU to a display works with any drivers). I guess you have some other problem. What's your setup?
Thanks Grincho i will look into
Sent from my iPhone using Tapatalk
Manni
17th December 2023, 21:01
Yes, I can confirm. I bought this no-name Chinese DP 1.4-to-HDMI 2.1 adapter https://www.amazon.com/Displayport-Adapter-Monitor-Converter-Resolution/dp/B0BPXWZVLK/ref=sr_1_18?crid=2ZE4YMXIL0KWQ&keywords=DisplayPort%2B1.4%2Bto%2BHDMI%2B2.1&qid=1702788094&sprefix=displayport%2B1.4%2Bto%2Bhdmi%2B2.1%2Caps%2C363&sr=8-18&th=1.
It uses VMM7100 chipset from Synaptics - the same as in CableMatters adapters, so the firmware update utility for the equivalent CableMatters product can update the firmware on this Chinese adapter too, resolving some issues if you are on the older firmware. Link to the adapter's firmware update: https://kb.cablematters.com/index.php?View=entry&EntryID=160
Thanks, I couldn't find the same no-name in the UK so I ordered the CableMatters, as I've been happy with them in the past. I'll let you know how I get on.
angmav
18th December 2023, 11:26
It is a consensus that 4K/24 10/12bits is working in 531.62 (532.02) when you pass through AVR (direct connection GPU to a display works with any drivers). I guess you have some other problem. What's your setup?
Sorry i am running a rtx 3080
running nvidia 532.02 windows 11 into denon x8500h into hdfury vertex 2 into a jvc rs2000
Sent from my iPhone using Tapatalk
Goeggel
18th December 2023, 14:27
I have filed a driver bug report here regarding the 4K 10bit HDMI 2.0 issue: https://docs.google.com/forms/d/e/1FAIpQLSewHJk1xP-C5elLBRCDLTLpNQZ9eiefrdZmUGP9hMCN6gKssA/viewform
That's the link I got from Nvidia support regarding another issue. The more people fill out the bug report, the higher the chance Nvidia fixes this. Maybe...
Manni
18th December 2023, 17:30
Thanks, I couldn't find the same no-name in the UK so I ordered the CableMatters, as I've been happy with them in the past. I'll let you know how I get on.
Just confirm that the dp 1.4 to HDMI 2.1 adapter cable (CableMatters here) does resolve the 4K24 10/12bits issue with newer drivers. I was able to select 10/12bits while going through a HDMI 2.0 input on my X8500HA receiver without getting a black screen using the latest 546.33 drivers. Unfortunately, it doesn’t help with the frame drops issue when using HDR Passthrough with JRVR, but as I’ve stopped using JRVR for now due to other issues and missing features, that’s not a problem for me. I’m going to watch a few films now, hoping it will also help with the long drops/freeze I get once or twice a film (using bitstreaming) but I’m not holding my breath [EDIT: sadly didn’t help for that]. Anyway, it’s great to be able to use the latest drivers, at least with madVR, so thanks Grincho for DP tip. I would never have thought of that!
skarafaz
19th December 2023, 10:01
Hi! I've just updated my htpc from Windows 10 + nvidia v446.14 driver to Windows 11 + v546.33 nvidia driver (I had to). Madvr is working, but custom modes tab is missing; is this a know issue? Thanks.
huhn
19th December 2023, 18:15
got removed. working as intended.
Manni
20th December 2023, 00:30
Just confirm that the dp 1.4 to HDMI 2.1 adapter cable (CableMatters here) does resolve the 4K24 10/12bits issue with newer drivers. I was able to select 10/12bits while going through a HDMI 2.0 input on my X8500HA receiver without getting a black screen using the latest 546.33 drivers. Unfortunately, it doesn’t help with the frame drops issue when using HDR Passthrough with JRVR, but as I’ve stopped using JRVR for now due to other issues and missing features, that’s not a problem for me. I’m going to watch a few films now, hoping it will also help with the long drops/freeze I get once or twice a film (using bitstreaming) but I’m not holding my breath [EDIT: sadly didn’t help for that]. Anyway, it’s great to be able to use the latest drivers, at least with madVR, so thanks Grincho for DP tip. I would never have thought of that!
Unfortunately the DP to HDMI adapter made my long video+audio freeze worse, so I'm back to 531.61 and direct HDMI connection.
angmav
20th December 2023, 21:46
Sorry i am running a rtx 3080
running nvidia 532.02 windows 11 into denon x8500h into hdfury vertex 2 into a jvc rs2000
Sent from my iPhone using Tapatalk
Thanks sorting out as we speak you are right vertex is the culprit when I disconnect from the chain 12 bit works currently on the vertex 2 forum trying to resolve thanks for your assistance
Sent from my iPhone using Tapatalk
Charky
24th December 2023, 17:24
Hi! I've just updated my htpc from Windows 10 + nvidia v446.14 driver to Windows 11 + v546.33 nvidia driver (I had to). Madvr is working, but custom modes tab is missing; is this a know issue? Thanks.
Mostly invisible tweaks to dynamic tone mapping algorithm aside, madvr is abandonware at this point, and has been for years. Unless it has something you absolutely need, I suggest you move on to another player/renderer, like JRVR or MPV.
Anyway, I never got the madvr "custom modes" tab to show up on Win 11.
So I created a manual resolution manually by following this guide (jump to last page) : https://forum.doom9.org/showthread.php?t=173571
janos666
15th January 2024, 20:32
I noticed that "borderless window" mode often looses it's ability to pass through 10bit and gets stuck at 8bit. Since Win11 always redirects "exclusive fullscreen" mode to "enhanced windowed mode", the only way for me seem to be rebooting and then 10bit works for a while.
I am currently on madVR v0.92.17. I have several issues with later "unofficial" builds when it comes to HDR, especially when trying to display test patterns with ArgyllCMS/DisplayCAL or ColourSpace HDR display characterization (madTPG always gets stuck at 8 bit and often appear with a completely broken tone-response curve and saturation - not quiet like "HDR showed in SDR mode" but something in-between...).
And I currently run with the 546.33 nVidia driver. I rarely skip and updates on these drivers and this 8/10 bit issue has been going on for a long time (months, if not years in case only the frequency of this happening changed some months ago or I was simply blind to it due to the dithering which I now have disabled).
arrgh
17th January 2024, 18:38
...
the 3D implementation from amd and nvidia doesn't matter here madVR doesn't support them it only supports the OS 3D API.
...
very old post... but I have a general question concerning this:
Intel had a very good support for mvc/3D videos.
I'm using an i5-Core 7200U HD620 with an "old" driver and it works very well with madVR and MPC-BE.
Does somebody know what is the latest Intel Graphics and driver combo still supporting 3D? (I have read somewhere that they dropped the mvc support...
Thanks
huhn
17th January 2024, 19:29
i only know nvidia dropped it and removed support (can still be re added).
with AMD AFAIK they may not support 3d anymore but they didn't actively removed it like nvidia did.it may just work until windows removes support same with intel. with arc it may not work i mean it's intel arc...
Emulgator
20th January 2024, 23:39
Encoding: Intel .mvc still works here, software mode, libmfxsw32.dll 8.18.2.17 from 17.02.2018
UHD 750 Hardware encoding: I tried .avc, .hevc, .mvc not yet.
Decoding: should arrive (and leave) with encoding capabilities, I guess ? (Not the other way around, ofc.)
Klaus1189
21st January 2024, 19:00
Hopefully some fixes and not some regressions ;)
Goeggel
29th January 2024, 14:23
I think the Nvidia GeForce 551.23 WHQL driver has finally solved the 4K 10bit HDMI 2.0 issue.
I can now again select 4K RGB Full 10bit for 23Hz.
Output chain: RTX 3080 (HDMI 2.1) -> Denon AVC-X6700H (2.1) -> LG OLED B8 (2.0).
4K RGB Full 10bit for 60Hz reverts to 8bit. Is that because of HDMI specs/bandwidth limitations?
huhn
29th January 2024, 15:17
yes HDMI 2.0 is limited to 8 bit 4K 60 RGB
Manni
29th January 2024, 15:56
I think the Nvidia GeForce 551.23 WHQL driver has finally solved the 4K 10bit HDMI 2.0 issue.
I can now again select 4K RGB Full 10bit for 23Hz.
Output chain: RTX 3080 (HDMI 2.1) -> Denon AVC-X6700H (2.1) -> LG OLED B8 (2.0).
4K RGB Full 10bit for 60Hz reverts to 8bit. Is that because of HDMI specs/bandwidth limitations?
That’s great new, I’ll give it a try.
Manni
31st January 2024, 08:01
I can confirm that 551.33 resolves the 4K23 10/12 bits black screen issue on my 3090 when using an hdmi 2.0 input on my HDMI 2.1 AVR.
Now I need to check if it also resolves the dropped frames in HDR passthrough with jRiver, which is another reason why I was stuck with 532.03.
Thanks Goeggel for reporting this.
potpocki
31st January 2024, 10:59
I think the Nvidia GeForce 551.23 WHQL driver has finally solved the 4K 10bit HDMI 2.0 issue.
I can now again select 4K RGB Full 10bit for 23Hz.
Output chain: RTX 3080 (HDMI 2.1) -> Denon AVC-X6700H (2.1) -> LG OLED B8 (2.0).
4K RGB Full 10bit for 60Hz reverts to 8bit. Is that because of HDMI specs/bandwidth limitations?
I confirm that the problem is resolved. But in any case I get much more banding in 10bits than in 8bits with my oled B8 so I'll stay in 8bits, even for HDR (blade runner 2049 grey sky is a good test).
nevcairiel
8th February 2024, 15:52
If you were having issues with occasional (micro)stutters, maybe give the latest 551.46 hotfix driver a try, as it resolves a slew of vsync related stuttering (and video generally renders against vsyncs for timing)
https://nvidia.custhelp.com/app/answers/detail/a_id/5519?=&linkId=100000240085402
huhn
8th February 2024, 20:23
nice.
are hotfixes always release like this and not over the driver page?
Klaus1189
8th February 2024, 20:25
Yes, sadly
SamuriHL
8th February 2024, 23:43
As long as the fixes make it into the next official driver, as well and don't get forgotten...
huhn
10th February 2024, 09:36
Hi! I've just updated my htpc from Windows 10 + nvidia v446.14 driver to Windows 11 + v546.33 nvidia driver (I had to). Madvr is working, but custom modes tab is missing; is this a know issue? Thanks.
got removed. working as intended.
this information is wrong. i have the custom refresh rate on 204 with driver 551.46. sorry about that.
Charky
10th February 2024, 12:10
OK, I never encountered a driver bug before, but here we are.
RTX 3090 -> Denon X2800H -> LG 65C2
On any driver higher than 546.65, Atmos passthrough is fucked when playing 2160p23 at 12 bits. By fucked I mean no sound at all or a blip of sound every 10 seconds. The AVR display switches back and forth between Atmos and DD+. There's clearly something wrong with the signal.
Same issue with different players (MPC BE/HC, VLC, Jriver), different renderers (madvr, MPC Video Renderer, JRVR, whatever VLC uses).
One time I even rebooted Windows and everything nvidia related had disappeared (like, no NVCP in right click menu on the dektop, no system tray icon)
Same problem with hotfix driver above.
8 bits works, And, weirdly, 60 Hz / 12 bits with passthrough works too. I probably should try more combinations (HDR/SDR, 1080p, etc.) but since 546.65 work perfectly fine, first thing that comes in mind is a driver issue. And that sucks, because I use the very same PC to play games and can't afford to NOT update my drivers for latest games...
Anyone ever seen this or heard of it?
tkol
11th February 2024, 01:27
If you were having issues with occasional (micro)stutters, maybe give the latest 551.46 hotfix driver a try, as it resolves a slew of vsync related stuttering (and video generally renders against vsyncs for timing)
https://nvidia.custhelp.com/app/answers/detail/a_id/5519?=&linkId=100000240085402
would these series of occational stutter and microstutter fixes also be the case for videos(movies and series) or just for gaming?
huhn
11th February 2024, 03:24
that's what he is hoping.
a game or a video renderer is the same thing if it comes to presentation.
SamuriHL
22nd February 2024, 19:28
I like the new unified App. Let's hope they don't screw it up.
Siso
5th March 2024, 21:39
Are the options in nvidia control panel for rtx 4000 cards still the same for madvr? Prefer maximum performance and vsync on, 1 frame in advance in madvr?
SamuriHL
21st May 2024, 16:57
Oh goodie here we go again. Er, I mean, how nice! :D
Klaus1189
21st May 2024, 20:36
for a long time a new HD Audio Driver -> 1.4.0.1
so far so good ...
SamuriHL
21st May 2024, 21:48
That scares me even more. I'll have time to play later this week. I'm working on rewatching House of the Dragon and want Dolby Vision for that so no HTPC. But I have some movies to catch up on this weekend so I'll see if that HD Audio driver helps or hurts ATMOS playback...
Yz345a
28th May 2024, 18:15
I tried the 551.46 hotfix driver, but unfortunately, it didn't help with my issues. I'm still experiencing stutters and microstutters across the board, whether I'm watching videos, movies, or playing games. It's especially noticeable when I'm playing online here (https://soazerbaycandakazino.com/), where the stuttering makes it quite frustrating. Anyone else still having similar problems even with the latest driver update?
Klaus1189
28th May 2024, 19:03
What GPU?
What display?
GSync enabled in driver?
What software?
madVR?
And the other software?
Highest refresh rate correct set in Windows?
Already tried latest driver 555.85?
Manni
29th May 2024, 12:13
That scares me even more. I'll have time to play later this week. I'm working on rewatching House of the Dragon and want Dolby Vision for that so no HTPC. But I have some movies to catch up on this weekend so I'll see if that HD Audio driver helps or hurts ATMOS playback...
I tried the latest and got a shorter drop than the usual freeze I get when bitstreaming ATMOS. Still getting frames dropped with HDR passthrough in jRiver. Kind of given up again on using the HTPC as a primary player. At least with Win 11 and my 3090, it’s not reliable anymore.
SamuriHL
29th May 2024, 19:22
I tried the latest and got a shorter drop than the usual freeze I get when bitstreaming ATMOS. Still getting frames dropped with HDR passthrough in jRiver. Kind of given up again on using the HTPC as a primary player. At least with Win 11 and my 3090, it’s not reliable anymore.
Same results for me. And yea, I'm moving on to other devices for primary viewing myself. With the G2 I don't really need a whole lot of tone mapping anyway. Given that I have it calibrated the built in static tone mapping generally is good enough these days.
Klaus1189
29th May 2024, 20:08
@Manni & @SamuriHL: Would you mind considering an AMD RX7000 card? Even the smallest one will do if this works without any issues.
SamuriHL
29th May 2024, 22:11
No thanks. I use my 3080 for more than simple video playback.
Klaus1189
30th May 2024, 06:55
I mean for a dedicated HTPC use only.
Manni
30th May 2024, 08:39
I mean for a dedicated HTPC use only.
Thanks for the suggestion, but I’m like SamuriHL, my HTPC isn’t dedicated to HTPC use, it’s also used for video editing and gaming. I need to be able to update the OS and drivers, I can’t “freeze” the system in a working state (if that ever happens).
Also, I frequently read issues with AMD as well, so I’m not sure it would resolve the problem and I’m not keen to spend £700+ and hours of tuning to find out that I also have issues with AMD in my rig, even if it’s not the same ones. I used to have nVidia for best compatibility with madVR, but I’m using mostly JRVR with jRiver, so that’s not my priority anymore.
I also have moved to a flat panel, and it’s unlikely I’ll ever move back to projection. With 1,000nits peak, there is no real need for dynamic tonemapping with the vast majority of content mastered at 1,000nits displayed perfectly at 1:1, so I use HDR passthrough and static tonemapping and even with the occasional high nits titles, I get decent results.
I also need DV and HDR10+ support, which are still not supported (at least with jRiver, I’m not interested in the complex alternative solutions) on a HTPC, so I’m happy with network playback on my Oppo 203 clone and Dune using the MyMovies app on iOS as a front-end. HTPC is now a secondary source, that I mainly use to watch 1080p TV Series and a 3D LUT with JRVR.
I’d love to be able to use it as a primary source for SDR content and HDR10 titles, and I’m going to try 546.65 as it seems to be working better, but it’s not the end of the world if I can’t. I love the predictability of non-HTPC sources, even if I lose WOL for my NAS boxes and automatic control for my Vera lights, and if I have to use my iPhone or iPad to select the title I want to watch.
SamuriHL
30th May 2024, 14:58
Yea I'm using an AM6b+ these days. Full DV FEL support.
Manni
30th May 2024, 16:55
Yea I'm using an AM6b+ these days. Full DV FEL support.
It's off-topic here so I'll PM you, but I'm curious about which device you're using. The main downside of the Dune is the absence of FEL with DV (it only processes the RPU instead of falling back to HDR10). No such issue with the Oppo, but it's a bear with network playback, much less reliable than the Dune that's rock solid.
I made some progress today with the HTPC though because I installed 546.65 and I was able to resolve my frame drop issues with madVR, both in SDR and HDR. I still have frame drops with jRiver in HDR passthrough, it's an issue that comes and goes according to the nVidia drivers and there is nothing Hendrik can do about it.
I also have lots of glitches with madVR if I use 119/120p (which I'm trying at the moment to resolve a motion issue with my Samsung). If anyone has any idea how to resolve this (glitches at 4K120 with madVR), please let me know, but it doesn't seem to have any impact on image fluidity (I still have no frame drops/repeats).
128 8 3
and don't flush works for me.
mpv/libplacebo is currently unusable on my 5700 XT when the screen is set to 240 hz it thinks the display is some where between 230-233 HZ and is creating completely unwatchable frame times. this happen after i updated the driver it worked in the past.
so yes everything is as it used to be nothing has to works.
SamuriHL
30th May 2024, 17:51
It's off-topic here so I'll PM you, but I'm curious about which device you're using. The main downside of the Dune is the absence of FEL with DV (it only processes the RPU instead of falling back to HDR10). No such issue with the Oppo, but it's a bear with network playback, much less reliable than the Dune that's rock solid.
I sent you a response on this topic.
I made some progress today with the HTPC though because I installed 546.65 and I was able to resolve my frame drop issues with madVR, both in SDR and HDR. I still have frame drops with jRiver in HDR passthrough, it's an issue that comes and goes according to the nVidia drivers and there is nothing Hendrik can do about it.
I'll have to try that but I'm using JRiver JRVR for everything on my HTPC right now given that it can read the HDR10+ and DV metadata for its dynamic tone mapping. Obviously that does not apply if you're using passthrough.
I also have lots of glitches with madVR if I use 119/120p (which I'm trying at the moment to resolve a motion issue with my Samsung). If anyone has any idea how to resolve this (glitches at 4K120 with madVR), please let me know, but it doesn't seem to have any impact on image fluidity (I still have no frame drops/repeats).
I was never able to get 120 to work properly with madvr or JRVR on my G2. I didn't spent a whole lot of time on it but I suspect it's because I had gsync enabled when running at 120.
Manni
30th May 2024, 20:21
I sent you a response on this topic.
Thanks!
I'll have to try that but I'm using JRiver JRVR for everything on my HTPC right now given that it can read the HDR10+ and DV metadata for its dynamic tone mapping. Obviously that does not apply if you're using passthrough.
Sadly DTM isn't an option as it triggers the SDR mode on my Samsung which is limited to 100nits (I could go up to 200 or 300nits max but I need compatibility for SDR content using other sources).
So HDR passthrough is the only option for me (1,000nits peak with static tonemapping), and DV or HDR10+ metadata isn't available in that mode.
I was never able to get 120 to work properly with madvr or JRVR on my G2. I didn't spent a whole lot of time on it but I suspect it's because I had gsync enabled when running at 120.
Gsync definitely doesn't play well with video content. But with Gsync disabled and vertical sync on, it seems to be working fine at 120p (except the many glitches), at least with 546.65 (I'll try to update again to the latest to see if the driver version makes a difference, or if it's just JRVR that drops frames with HDR passthough. I haven't tested the drops/freezes I get with Atmos, so looking forward to that too before giving a clean bill of health to madVR at 4K120.
Manni
30th May 2024, 20:22
128 8 3
and don't flush works for me.
Thanks but please can you be more specific about what each option refers to (or provide a screenshot)? I assume you mean the rendering options for windowed mode, but the above doesn't make sense to me without further explanation.
queue decode 128, render 8 and present 3 (windowed).
and all windowed settings to no flush.
Manni
30th May 2024, 23:36
queue decode 128, render 8 and present 3 (windowed).
and all windowed settings to no flush.
Thanks a lot, that resolved the glitches issue at 4K120. I went from 15-20 per second to one in a while, maybe every ten minutes if that.
For some reason the rendering stats are not displayed anymore (I only have the present stats), but I can live with that.
Now I only have to check if the Atmos long freezes/drops are gone when bitstreaming…
SamuriHL
31st May 2024, 00:05
Sadly DTM isn't an option as it triggers the SDR mode on my Samsung which is limited to 100nits (I could go up to 200 or 300nits max but I need compatibility for SDR content using other sources).
So HDR passthrough is the only option for me (1,000nits peak with static tonemapping), and DV or HDR10+ metadata isn't available in that mode.
Oh man that sucks. I'm able to output HDR with JRVR's DTM and it does a really good job. I have it set to the max nits my display can do in calibrated HDR mode (~850 or so currently but it can do almost 880 calibrated a different way) which means I need very little tone mapping for most movies.
Gsync definitely doesn't play well with video content. But with Gsync disabled and vertical sync on, it seems to be working fine at 120p (except the many glitches), at least with 546.65 (I'll try to update again to the latest to see if the driver version makes a difference, or if it's just JRVR that drops frames with HDR passthough. I haven't tested the drops/freezes I get with Atmos, so looking forward to that too before giving a clean bill of health to madVR at 4K120.
That would be nice. I'll have to play around with it this weekend.
Thanks a lot, that resolved the glitches issue at 4K120. I went from 15-20 per second to one in a while, maybe every ten minutes if that.
For some reason the rendering stats are not displayed anymore (I only have the present stats), but I can live with that.
Now I only have to check if the Atmos long freezes/drops are gone when bitstreaming…
if you don't flush madVR can't know the renderer stats so this is working as intended.
other should not blindly copy this.
Manni
31st May 2024, 01:27
Oh man that sucks. I'm able to output HDR with JRVR's DTM and it does a really good job. I have it set to the max nits my display can do in calibrated HDR mode (~850 or so currently but it can do almost 880 calibrated a different way) which means I need very little tone mapping for most movies.
Sorry everyone for the slight off topic, last post on this.
It's funny, for me enabling "HDR to HDR" in JRVR with a target of 1,000nits doesn't seem to be working, it still says HDR passthrough. Is there a way to know on the OSD that HDR to HDR TM is enabled? Maybe I'm happy with the results because it is actually doing the tonemapping. Please PM me if you ave any info, otherwise I'll post on jRiver.
For some reason, I don't seem to have the frame drops in 4K120 with JRVR but I need to do more tests. with madVR, I still had a couple of audio drops but they were very short so more bearable.
SamuriHL
31st May 2024, 01:37
Manni I'll hit you up in our PM.
SamuriHL
31st May 2024, 01:57
Brilliant. I just tried JRVR again with 120hz and GSync disabled and it was flawless. I didn't watch long, maybe 3 or 4 minutes but no drops at all. That's with 546.65. I can try going back to the latest driver later this weekend and see if that still holds true. 120 is nice and universal so if that works it'll work for everything. Love it.
Manni
31st May 2024, 02:27
Brilliant. I just tried JRVR again with 120hz and GSync disabled and it was flawless. I didn't watch long, maybe 3 or 4 minutes but no drops at all. That's with 546.65. I can try going back to the latest driver later this weekend and see if that still holds true. 120 is nice and universal so if that works it'll work for everything. Love it.
Glad it worked for you too! Thanks to your PM I got HDR to HDR tonemapping to work in jRiver, but there are quite a few issues, for example HDR10+ metadata is only partially supported and the HDR metadata not always sent, so I'll start a discussion there about HDR passthrough so as not to take this discussion more off-topic than we already have :)
Thanks again for your help and thanks everyone for your patience. Thanks also to Huhn for the help with resolving the madVR glitches at 4K120. Progress today!
SamuriHL
31st May 2024, 02:41
Yea this was good all around. I'll look for your post on JRiver forum and add my experience if it's helpful.
Manni
31st May 2024, 13:21
Yea this was good all around. I'll look for your post on JRiver forum and add my experience if it's helpful.
Thanks, here is the link: https://yabb.jriver.com/interact/index.php/topic,138989.0.html
Anyone with any of these issues with JRVR/jRiver, please contribute to that thread to add a data point and increase the chances of seeing these resolved.
SamuriHL
4th June 2024, 15:51
Oh joy. More testing to do later this week.
zealvix
1st July 2024, 08:53
AMD
Known limitations of Radeon RX 5000 and 6000 GPUs (older generations are fine):
• Hardware deinterlacing is broken in every driver version -> It is poor quality when applied to
interlaced video and it is not adaptive anymore, which is a NO-GO for HTPC usage.
• Color levels (full 0-255 vs. limited 16-235) are broken. That means limited 16-235 which is the standard range for videos are interpreted as 0-255 and this leads to elevated blacks and dimm whites.
Does the above also affect rnda2 APU (e.g 6XXX mobile chips or their rebadged 7XXX chips) when streaming (youtube etc) using browsers (edge, firefox etc) or apps (netflix etc)_ ?
Sunspark
1st July 2024, 09:27
I have limited experience with rdna2 (custom apu 0405) using a Steam Deck. 0-255/16-235 isn't broken on Linux and hardware decoding works (in firefox, but not chrome), however the Windows drivers for this rdna2 variant are unusable for htpc purposes (no hardware decoding at all) and only some players/renderers work properly for the video levels in software decoding mode. I didn't test deinterlacing in either OS.
The Windows drivers are locked by AMD, so it's not a simple matter of forcing an install of one of the other rdna2 variants.
AMD
Known limitations of Radeon RX 5000 and 6000 GPUs (older generations are fine):
• Hardware deinterlacing is broken in every driver version -> It is poor quality when applied to
interlaced video and it is not adaptive anymore, which is a NO-GO for HTPC usage.
• Color levels (full 0-255 vs. limited 16-235) are broken. That means limited 16-235 which is the standard range for videos are interpreted as 0-255 and this leads to elevated blacks and dimm whites.
Does the above also affect rnda2 APU (e.g 6XXX mobile chips or their rebadged 7XXX chips) when streaming (youtube etc) using browsers (edge, firefox etc) or apps (netflix etc)_ ?
depends on the browser. bu as far as i know all sadly do but that was there choice.
my 5700 XT is so utterly broken i had to play around in the registry to make it stop applying image destroying filters.
you can test this by changing visual effect to "adjust for best performance" and opening explorer.
now play a YT video that is pretty dark and move the explorer window partially in front of the video. if the video colors change you are affected.
in typical AMD fashion they forgot the off switch: https://www.amd.com/content/dam/amd/en/images/software/2374653-noise-suppression-screenshot.png
madVR will ignore this issue outside of DXVA2 scaling/processing.
zealvix
2nd July 2024, 09:39
Thanks for the replies.
Do not have any on hand to test, but was interested in getting a 6600H mini pc (can be found cheap) for someone else, which would be a good match for his needs.
But if even video playback on browsers are affected, that is a no go.
Hope the future series would not have this issue, as I always prefer AMD over Intel for mini PCs.
Sunspark
2nd July 2024, 19:03
If you're not playing 3D games, Intel igpus are fine for desktop and video playback needs. Very many secondhand Intel mini PCs are available.
Christiano Mazzutti
10th July 2024, 23:09
Hello, after updating my Intel Xe Graphics drivers, madVR stopped working. Audio comes out, but the screen is black and blinking. Does anyone know how to fix it? Thanks
working driver: 31.0.101.5534
new driver not working: 31.0.101.5762
Klaus1189
11th July 2024, 17:36
Post mediainfo log of file. Do you use hardware acceleration for this codec? What happens if you turn off hardware decoder in player for testing purposes? If it works then Intel needs to fix their driver.
What Player? What filters?
Emulgator
12th July 2024, 11:42
My Intel working driver here: 31.0.101.5534.
Seems to be a good spot for me now.
Previous versions had flipping problems (Hybrid GPU mode nVidia 3080 vs. Intel UHD 750 on i9-11900K here)
You may just roll back to this one.
Later versions seem to generate problems also with madVR:
Originally Posted by wyup View Post
Anybody having problems with latest 31.0.101.5590 Intel Graphics Driver on UHD Graphics 770 and madVR renderer? Image looks like white noise.
@nevcairiel acknowledged reports about this.
Yes. Intel drivers are killing madVR. Everything from gfx_win_101.5590 and forward is broken and even latest beta drivers gfx_win_101.5762 are bad
Christiano Mazzutti
12th July 2024, 20:05
Post mediainfo log of file. Do you use hardware acceleration for this codec? What happens if you turn off hardware decoder in player for testing purposes? If it works then Intel needs to fix their driver.
What Player? What filters?
Intel needs to fix their driver.....
:)
axlns
22nd August 2024, 20:27
RTX20 series cards and stuttering when playing movies in mpc-hc+madvr...
Guys, I think I tried every possible fix I was able to find for this stuttering issue with my RTX2080ti card (setting vsync to on, enabling adaptive power management mode, enabling low latency mode, setting number of present in advance frames to 1 or 3), but nothing helps, still having stuttering which are quite noticeable and very annoying.
when I watch same movie on my ugoos sk1 tv box - it plays it flawlessly (but obviously tv box missing madvr features which are important to me)
I upgraded my HTPC from 1080 to 2080ti and found this stuttering issue and it driving my crazy. and I cant find a way to fix this. I never had it with 1080 card. I even installed windows 11 completely deleting everything from my drive C (so completely "clean" installation) - did not help
maybe someone can suggest a solution? other than going back to 1080 card. would installing older nvidia driver going to help? if so - which version?
I'm using latest MadVR beta for hdr to sdr tone mapping. I have sony-vw760es projector, its HDR compatible, but I found that madVR with tonemapping giving me better picture, so even dont need HDR passtrough..
non-beta version of MadVR giving me same stuttering issues, btw, so its not MadVR beta problem.
hopefully someone can show me correct way to fix this annoying stuttering. thanks in advance!
Klaus1189
22nd August 2024, 21:03
What TV/Monitor/Projector do you use? How is it connected? Did you use same device with GTX 1080? Do you use only the projector? Can you test also another device?
axlns
23rd August 2024, 04:54
What TV/Monitor/Projector do you use? How is it connected? Did you use same device with GTX 1080? Do you use only the projector? Can you test also another device?
thanks for your reply!
my HTPC connected to AVR Denon x8500h, and then AVR connected to Sony VPL-VW760ES projector
nothing else is connected, I use only projector
so I had this HTPC running for a few years on Windows 10 with GF 1080 connected like this and everything was fine with madvr, no stuttering
then maybe a week ago I just swapped GF 1080 with RTX 2080Ti, nothing else changed, still used same Windows 10 OS installed maybe couple of years ago and immediately I get this stuttering issue.
after battling with it for a few hours I decided to fresh install windows 11 reformatting disk C
then I installed latest nvidia driver, latest k-lite codec pack, configured everything as I did before. stuttering was a bit less than right after replacing video card on windows 10, but it was still very noticable.
then I started to google for similar problems, found various suggestions which I tried, but was not able to get rid of stuttering unfortunately.
UPDATE: installing older nvidia driver v. 442.74 fixed stuttering/judder problem completely, but not sure if this is good long term fix...
clsid
23rd August 2024, 12:05
Have you also tried high performance power mode? That usually fixes stuttering as well when its caused by constant P-state switching of the driver.
If you do not use the htpc for gaming, then staying on older driver would be fine. I suspect the newer drivers are more aggressive with trying to power save.
axlns
23rd August 2024, 20:09
Have you also tried high performance power mode? That usually fixes stuttering as well when its caused by constant P-state switching of the driver.
If you do not use the htpc for gaming, then staying on older driver would be fine. I suspect the newer drivers are more aggressive with trying to power save.
yes, I tried that as well. also tried ultimate performance power plan in windows. did not make any difference
yes, I can live for now with old driver, but still would like to find a solution for latest drivers as well.
btw, also tried today JRiver Media Center with JRVR renderer which also have dynamic tone mapping for HDR to SDR - it worked fine with latest driver. but still MadVR is doing better mapping work when using projector, so I prefer MadVR
Klaus1189
23rd August 2024, 20:46
What settings did you adjust in Nvidia options for your player.exe?
axlns
23rd August 2024, 21:02
I tried all combinations of
Vertical Sync = On
Low Latency Mode = On or Ultra
Power Management = Adaptive or Prefer maximum performance
tried them set globally or just for MPC-HC
Klaus1189
23rd August 2024, 21:03
Try to disable low latency mode
axlns
23rd August 2024, 21:08
its disabled by default, stuttering happens when everything has default values, but I also tried changing these settings separately from each other (e.g. leave everything default and change only power mode to prefer maximum performance)
did not make any difference for me
Klaus1189
23rd August 2024, 21:10
Do the stutters get counted on stats of madvr?
axlns
23rd August 2024, 21:11
No, stats showing no dropped/glitched frames
Klaus1189
23rd August 2024, 21:13
What do you have set on present frames in advance?
axlns
23rd August 2024, 21:13
Render times are around 15-17ms
axlns
23rd August 2024, 21:13
I tried setting them to 1 or 3. Still stutters
Klaus1189
23rd August 2024, 21:19
What are stock settings? 8? For me I had to go back to stock settings which is strange.
Try to Backup your settings and Set up madvr new. And only change one thing and test. Then you can change another thing and test.
axlns
23rd August 2024, 21:24
Default was 8. From this point I started to experiment, changing first number of frames to present to 1. Testing, still stuttering.
Then changing these three settings in NV control panel separately.
Will try tomorrow again, from everything default.
Thanks for your help!
Klaus1189
23rd August 2024, 21:25
Ok, also try to disable all flush options in madvr.
mclingo
1st September 2024, 00:52
Hi I have just upgraded from a 5 700 card to a 7800 AMD card and I can no longer get 23.976 playback there is no mention of this in the driver details for this card is there anybody else on here that has a 7000 series card that can achieve 23.976 playback for movies Using lav filters and Madvr
Klaus1189
1st September 2024, 20:59
1.) Did you DDU before upgrading the GPU? I know same chip manufacturer, but sometimes necessary. Alternatively AMD Cleanup Utility (https://www.amd.com/en/resources/support-articles/faqs/GPU-601.html)
2.) What player do you use?
3.) What happens instead.
4.) What refresh rate do you use as default?
mclingo
15th September 2024, 00:48
well i actually fixed this shortly after I posted this and I thought I knew how but it must have been a fluke. I had a crash on my PC (unrelated) and It wouldnt boot, it forced me to do a system restore and didnt give me the date it had chosen, it turned out to be the restore it took just before I installed my new GPU, and guess what.... its borked again, i'm getting frame drops almost exactly every 40 seconds, using 23,976 as an example. I am using MADVR, lav filters and various players, all exibit the same behaviour so it must be something to do with MADVR?
is anyone aware of any players that use a different renderer which can show playback dialog like ctrl+j in madvr, this will tell me if it is just a MADVR issue or a driver or PC issue.
So far i've tried:
using DDU to wipe everything, did that twice in a row.
used AMD cleanup facility
wiped MADVR completly
uninstalled LAV filters
tried old and new AMD drivers
tried removing all entires in CRU utility and then running DDU again, nothing bl00dy works, i'm losing the will to live here :(
huhn
15th September 2024, 01:29
EVR (the graph and the clock)
mpv shift+i
Klaus1189
15th September 2024, 10:02
Also MPC Video Renderer can show what refresh rate is actually set. It shows it in line 2 called "Display:"
huhn
15th September 2024, 10:41
that'S not the actual frame rate relative to the system or audio clock it is just the frame rate.
it's maybe the composition rate. both are static numbers.
Klaus1189
15th September 2024, 10:43
OK, what exactly does he want to see? If he is using 24.000 Hz mode of Windows and he wants to use 23.976 then he will see it this way.
mclingo
15th September 2024, 14:11
I did manage to fix it again thankfully but I'm not really sure how again just a combination of things I throw at it I probably need to rebuild my windows 11 machine completely as I'm still using an image that was built years ago which had windows 11 installed on top of Windows 10, it's a good week to rebuild the thing as I have tonnes of software tweaks and settings steam vr all sorts of stuff on it.
It does seem to be a combination of using ddu and cru reset followed by an older driver then installing the newer driver on top seems to resolve it so I don't really know what's going on here.
So I am back to no frame drops for days again.
I have updated my sig
Klaus1189
15th September 2024, 20:19
@huhn: mpv -> "shift+i" also just shows actual refresh rate, isn't it?
@mclingo: Do you know what exact step fixed it for you?
huhn
15th September 2024, 22:22
at least libplacebo is showing pretty much everything:
https://ibb.co/p46tz1R
mclingo
16th September 2024, 19:03
cheers guys
aron7awol
25th September 2024, 04:06
Thanks a lot, that resolved the glitches issue at 4K120. I went from 15-20 per second to one in a while, maybe every ten minutes if that.
For some reason the rendering stats are not displayed anymore (I only have the present stats), but I can live with that.
Now I only have to check if the Atmos long freezes/drops are gone when bitstreaming…
Just for anyone else reading along (I know you don't really care about madVR these days yourself) setting "after copy to backbuffer" to "flush & wait (sleep)" or “flush” completely eliminates all glitches for me in 119/120Hz, and rendering stats are maintained. With a 4060 and the below settings, everything seems perfect, with Atmos dropouts eliminated by 40X0 card and glitch-free presentation.
Edit: After more testing I prefer the behavior with "don't flush". Despite the glitch counter increasing every once in a while, the motion has actually been more reliably smooth with this config.
huhn
25th September 2024, 06:33
only did a short test yet but i can confirm that they seem to work fantastically.
are your render queue also not filling up?
it also results in insanely stable render times i have +- 0.4ms
aron7awol
25th September 2024, 13:39
You can also try “flush” in that spot rather than “flush and wait”. I’m not sure if one is better than the other, but the glitches should be solved either way.
Edit: presenting 16 frames in advance seems to help keep the queues full. Not sure it makes any difference with playback, though.
huhn
25th September 2024, 15:23
it is staying at 2-3 that not an issue just unusual
Klaus1189
1st October 2024, 18:22
New 565.90 driver has new HD Audio Driver 1.4.2.6 (drivers directly before have 1.4.0.1).
Sounds like some bigger changers too me.
Maybe worth to take a look:
https://us.download.nvidia.com/Windows/565.90/565.90-win11-win10-release-notes.pdf
Klaus1189
1st October 2024, 18:37
Hmm, nothing to read about it (at least nothing that I found) and they write about 1.4.2.3 in pdf but 1.4.2.6 is in installer ...
Klaus1189
22nd October 2024, 18:39
Nvidia GeForce 566.03 causes again deep black task bar (dark theme in Windows 10) -> So transparency effects do not work ... lol
Going back to last Studio driver
Calvi
27th October 2024, 01:42
Has anyone got a solution for HDR not switching after a while on drivers > 525.25?
https://forum.doom9.org/showpost.php?p=1980969&postcount=2969
I ask because "Windows 11 update" updated my driver from 525.25 to 560.94 without me realizing until I noticed HDR stopped switching again, so issue still there for me with 560.94.
Would be good if someone has a fix or workaround.
Also would like to know if this only applies to 1XXX and 2XXX cards or the newer ones as well.
huhn
27th October 2024, 11:33
for mpv that is working as intended because microsoft dosen't want application to switch the HDR setting.
with madVR it should still work because it uses an very outdated API that can still do that.
Calvi
27th October 2024, 12:43
for mpv that is working as intended because microsoft dosen't want application to switch the HDR setting.
How do MS want it to work?
with madVR it should still work because it uses an very outdated API that can still do that.
It only works for a while then stops working until a reboot for any driver past 522.25.
AuRiMaS666
27th October 2024, 15:34
This issue is 2 or more years old and never has been fixed to my knowledge.
https://www.avsforum.com/threads/madvr-hdr-passthrough-shows-incorrect-colors-if-display-has-been-turned-off-requiring-reboot.3260442/
The only workaround would probably still be retarting the display device, described in the thread above, without full PC reboot.
I just gave up and turn on OS HDR manually every time I want watch HDR content.
huhn
27th October 2024, 15:59
How do MS want it to work?
you are supposed to do it yourself.
the old nvidia and AMD api can not be used any other way than automatic.
https://github.com/mpv-player/mpv/issues/15163
Calvi
28th October 2024, 13:00
That’s so stupid.
I don’t want to do it myself.
That’s why I have a computer.
Not having a go at you Huhn, I understand what you are telling me, just disappointed at yet another MS deliberate regression.
I’ll stick to 525.25 for another year or more I guess.
Unless this will work:
https://windowsforum.com/threads/windows-11-24h2-update-simplified-automatic-hdr-switching-coming-soon.340339/#:~:text=This%20update%20introduces%20a%20setting,off%20manually%20all%20the%20time.
huhn
28th October 2024, 22:36
i was expect something like that on the other hand it is Microsoft.
Sunspark
3rd November 2024, 20:06
Crazy amount of CVEs for Nvidia announced. https://nvidia.custhelp.com/app/answers/detail/a_id/5586
SamuriHL
4th November 2024, 01:36
Oh that's special. Hopefully they release a studio driver asap to fix it assuming the oct 15th studio driver does not have the fixes, that is.
nevcairiel
4th November 2024, 12:38
Contrary to popular believe, Studio Drivers and Game Ready Drivers are not actually functionally different, they are just marketing and release cadence.
SamuriHL
5th November 2024, 04:40
I guess I can switch back to grd...
Sent from my SM-S928U1 using Tapatalk
aron7awol
6th November 2024, 07:10
Has anyone got a solution for HDR not switching after a while on drivers > 525.25?
https://forum.doom9.org/showpost.php?p=1980969&postcount=2969
I ask because "Windows 11 update" updated my driver from 525.25 to 560.94 without me realizing until I noticed HDR stopped switching again, so issue still there for me with 560.94.
Would be good if someone has a fix or workaround.
Also would like to know if this only applies to 1XXX and 2XXX cards or the newer ones as well.
It occurs on 3060 Ti and 4060 for me.
I just keep restart64.exe (included in CRU) handy and whenever it happens I run that and it quickly fixes it without a system reboot. IIRC Win+Ctrl+Shift+B does not fix it.
Calvi
6th November 2024, 18:21
Thanks for that.
Klaus1189
12th November 2024, 18:33
Nvidia released driver 566.14 both Studio and Game Ready
Klaus1189
12th November 2024, 19:00
Well going back to Studio Driver 565.90 again. Still transparency effects bug. And also in the November 2024 Studio driver. Nvidia ... really? Are you serious?
If you miss such an obvious bug, what other bugs did you miss. I really don't wanna know...
Klaus1189
5th December 2024, 18:32
566.36 does not show up for me on 4090, only for 4080, maybe also for other GPUs on driver search in germany. Strange. Well I could test, but if you already found one who tested it, then I would like to save the time of installing und going back to my current driver again.
Where did you found it? Techpowerup?
Klaus1189
6th December 2024, 13:56
Nevermind, just saw on another forum Windows 10 taskbar bug is still not fixed in this driver.
https://forums.guru3d.com/threads/geforce-grd-566-36-released-12-5-24.454597/page-2#post-6287009
Another driver forum says it's fixed.
I just tested myself and can confirm it is fixed.
Issues like that are just minor, but why even push the release of the driver instead for fixing it and release it a day later. All I want is a bit more quality control.
Now the current Studio driver is affected and the newer Game Ready is fine. It should be the other way around. They fucked up the Game Ready driver and then they didn't care for testing Studio driver. An issue like that this is very obvious. I will never understand that.
cremor
6th December 2024, 14:14
From Reddit (https://www.reddit.com/r/nvidia/comments/1h7br0d/comment/m0juht9/):
Windows 10 Transparency issue is a Microsoft OS bug, a driver level workaround should be present in 566.36
Klaus1189
6th December 2024, 14:17
So drivers before had also a workaround in it? How about AMD? Do they have also a workaround in the driver if it is a Microsoft bug?
AuRiMaS666
8th December 2024, 20:11
This transparency bug doesn't seem to be Win10 exclusive, as I've ran into it on Win11 24H2 with prior two Nvidia releases (yet to try 566.36).
Thankfully, a quick workaround was to go into System Properties / Performance Options / Visual Effects and apply back and forth between "adjust for best performance/appearance" to make transparency effects behave normally again.
Manni
11th December 2024, 11:13
Never had this transparency bug with my 3090 and Win11 23H2.
However, in RGB Full 10bits 23p I have the wrong levels in SDR (fine in HDR). Levels are fine in both SDR and HDR if I switch to YCC 4:4:4 limited. TV (S90C in game mode) is set to normal/limited. Anyone knows when that started?
SamuriHL
11th December 2024, 13:44
Oh joy. I'm finally getting around to rebuilding my htpc with the 4080 super and this is what I have to look forward to? I also use RGB 10 bit but on an LG G2. Until I can find the cpu I want I won't be able to try it out though. Could be a while as I want a 9800x3d.
Sent from my SM-S928U1 using Tapatalk
Manni
11th December 2024, 13:56
Oh joy. I'm finally getting around to rebuilding my htpc with the 4080 super and this is what I have to look forward to? I also use RGB 10 bit but on an LG G2. Until I can find the cpu I want I won't be able to try it out though. Could be a while as I want a 9800x3d.
Sent from my SM-S928U1 using Tapatalk
Hi there :)
Well, if you use JRVR, I assume that you tomemap SDR Rec-709 content to HDR BT2020, to limit the number of HDMI syncs. It works great and makes this issue moot. However, it doesn't help when using players that have to switch between SDR and HDR according to content, which I occasionally use.
Glad to hear you're about to recommission your HTPC. I've resolved the Atmos micro drops by using a HDMI 2.0 input on my AVR for the 3090 for now. I'll wait until I can get a ProArt 5080 SUPER with 24GB to replace it. No way I'll get a 5080 at that price with 16GB, or a 5090 with that power consomption (and likely 3+ slots and too high for my HTPC case) I'm afraid.
SamuriHL
11th December 2024, 14:39
I don't scale sdr to HDR, no. So I would be impacted for sure. I couldn't care less about the time it takes to handshake res changes. Once it's done it's done and you're watching your video at that point.
I still have the 4080 super sitting here that I've had since July and not been able to use. I've been using my ugoos for local media playback and it's quite frankly been good enough with the calibrated G2. I'm mostly rebuilding it for games but the htpc aspect is nice, as well.
Sent from my SM-S928U1 using Tapatalk
Klaus1189
11th December 2024, 16:55
Never had this transparency bug with my 3090 and Win11 23H2.
However, in RGB Full 10bits 23p I have the wrong levels in SDR (fine in HDR). Levels are fine in both SDR and HDR if I switch to YCC 4:4:4 limited. TV (S90C in game mode) is set to normal/limited. Anyone knows when that started?
The transparency issue is very easy to see in Win 10 but should also be clearly visible in Win11, just toggle on/off in settings of windows and see if it becomes transparent.
What level is wrong exactly? Only in 23 Hz?
huhn
11th December 2024, 17:34
Never had this transparency bug with my 3090 and Win11 23H2.
However, in RGB Full 10bits 23p I have the wrong levels in SDR (fine in HDR). Levels are fine in both SDR and HDR if I switch to YCC 4:4:4 limited. TV (S90C in game mode) is set to normal/limited. Anyone knows when that started?
i just tested it and no issue.
10 bit RGB full range 23HZ
black level normal
Manni
11th December 2024, 21:02
i just tested it and no issue.
10 bit RGB full range 23HZ
black level normal
Thanks for taking the time to check. I double checked again with an SDR mp4 brightness pattern and there is no issue at 4K23 indeed with the latest driver.
Not sure what happened. It might be a madTPG issue with CM. All I know is that when switching to SDR, I got the wrong levels in RGB10 full, and switching to YCC 444 limited fixed it.
I've set the TV to use normal (limited) all the time recently, before it was on auto. Maybe that's what fixed it. I tried going back to auto but still no issue.
I'm using game mode without PC mode, maybe that's part of the problem. Anyway, good to know it's not everyone all the time...
huhn
11th December 2024, 23:23
figuring out that my TV is black crashing at 144 HZ 99% of time who knows what this thing can do at 23p... and everyone has that issue.
and i had a time where it used limited range for chroma and full range for luma which was "interesting" took me like 100H to fix.
Klaus1189
12th December 2024, 04:44
it used limited range for chroma and full range for luma which was "interesting" took me like 100H to fix.
How do you fix that?
huhn
12th December 2024, 16:22
brute forcing different setting over and over again using colorcontrol until it starts acting normal again.
you can ignore this issue there is not a single other user that reported that problem.
i can't even 100% blame the Tv there is still a small chance the GPU is doing that somehow even after an DDU.
Manni
14th December 2024, 01:13
Upgraded to win11 24h2 from 23h2 and am getting the transparency taskbar issue now, so 23h2 was immune apparently.
SamuriHL
14th December 2024, 01:30
I couldn't get the CPU I wanted so I grabbed a 9900x for now just so I can get the machine rebuilt. I'm not looking forward to whatever fresh hell nVidia has cooked up in the latest drivers though.
Manni
14th December 2024, 10:43
I couldn't get the CPU I wanted so I grabbed a 9900x for now just so I can get the machine rebuilt. I'm not looking forward to whatever fresh hell nVidia has cooked up in the latest drivers though.
Should be a nice machine, and unlike me with my 3090 with the 4080 you should be able to use 4K120 without getting Atmos micro audio drops. Apart from the taskbar bug (which is a very minor issue), all works fine in the latest drivers here.
I'm quite happy with the 3090 using a HDMI 2.0 input, as there are no micro audio drops, I resolved the long freeze issue and I can keep my AVR OSD (it goes away with FRL5). I can also use my Sony HDMI headphones without the need of a second VRROOM in the chain to extract audio for the HTPC. I've also found ways to set it up so that I resolve all the motion issues without the need for 4K120, so the only loss is 4:4:4 chroma for 23p video content, which I can live with. I might only upgrade the GPU when I can get an AVR that doesn't have these limitations (and also resolves the QMS bug) as there are no 5080 with enough VRAM and it's unlikely I'll get a 5090. The new AVR might not happen until 2026/2027, but I'm not in a hurry. 4K60 is fine for the games I play, and my HTPC is finally recommissioned and used as my primary source for video content.
SamuriHL
14th December 2024, 15:18
Very nice. I'm looking forward to getting my primary gaming machine back. But this means I'll have to keep the Nvidia drivers updated, which as we know can be like Russian roulette. It's worth the trade off. I'm looking forward to seeing path tracing in Indiana Jones. I haven't started playing it until the machine is done.
Sent from my SM-S928U1 using Tapatalk
nevcairiel
14th December 2024, 23:23
I ordered an Intel B580 for my HTPC to replace the 30 series card in it, as the audio bugs from the 30s cards are annoying me, even when I only bitstream when watching Netflix. The performance should be plenty for what I use it for.
Unless you also do gaming on such a system, very little needs a high-end card anymore as the mid-range ones got so much faster.
pirlouy
15th December 2024, 00:08
Wow, good news for us, a well recognised dev to test the new Intel GPU. I hope you'll come back to tell us if Intel drivers deserve their bad reputation or not !
Manni
15th December 2024, 01:05
I ordered an Intel B580 for my HTPC to replace the 30 series card in it, as the audio bugs from the 30s cards are annoying me, even when I only bitstream when watching Netflix. The performance should be plenty for what I use it for.
Unless you also do gaming on such a system, very little needs a high-end card anymore as the mid-range ones got so much faster.
Please let us know how it goes, especially with JRVR. Unfortunately, I use my HTPC for gaming (including MS flight simulator) and video editing, so going from a 3090 with 24gb of VRAM to a B580 with 12GB VRAM would likely be a serious downgrade, but if it does 4K120 RGB 10bits without any Atmos audio drops it might be a nice stop gap solution while waiting for a decent option in the series 5000.
EDIT: I'd be especially interested to know if the B580 also drops around 1-2 frames per hour, as nVidia does. The B580 is much more expensive in the UK, it's around £350, su much less interesting than the $250 in the U.S.
ryrynz
15th December 2024, 01:31
I ordered an Intel B580 for my HTPC to replace the 30 series card in it, as the audio bugs from the 30s cards are annoying me, even when I only bitstream when watching Netflix. The performance should be plenty for what I use it for.
Been having some issues with the audio myself recently via E-ARC. Did a fresh install with 566.36 disabling the power saving with NVCleaninstall and looks like I might've fixed it.
SamuriHL
15th December 2024, 01:34
I ordered an Intel B580 for my HTPC to replace the 30 series card in it, as the audio bugs from the 30s cards are annoying me, even when I only bitstream when watching Netflix. The performance should be plenty for what I use it for.
Unless you also do gaming on such a system, very little needs a high-end card anymore as the mid-range ones got so much faster.
I don't blame you. If I wasn't into high end gaming I'd probably consider it myself. Or give up on HTPC altogether.
nevcairiel
15th December 2024, 09:46
I don't blame you. If I wasn't into high end gaming I'd probably consider it myself. Or give up on HTPC altogether.
Luckily I have my gaming PC separate from that one. :) This one pulls 99% video duties, and 1% some browsing. I always thought maybe I would game a bit on the TV, but really I never do. And if it ever overcomes me, maybe in-home game streaming over ethernet.
Intel has always been pretty decent with video, the iGPUs just haven't had the performance to run any sort of fancy processing. So we'll see how this one goes.
huhn
15th December 2024, 10:09
i did not expect intel to be competitive with the second GPU series but it looks like they are.
nvidia gave up on normal GPUs and AMD is well AMD...
they are also a consideration for me. but i will wait for other to test first.
SamuriHL
15th December 2024, 14:01
I think everyone here will be interested to see how that goes. I mean that latest card supposedly has 4060 equivalency from what I read so it's not exactly a slouch. That should be plenty powerful enough to run some decent video enhancements. If it has stable clocks and no audio issues that could make a really sweet solution.
Sent from my SM-S928U1 using Tapatalk
SamuriHL
18th December 2024, 04:40
My new system is alive with a 4080 super and 9900x processor. I plan on seeing what trouble I can get up to in jriver soon enough. Lol
Sent from my SM-S928U1 using Tapatalk
Manni
18th December 2024, 18:15
My new system is alive with a 4080 super and 9900x processor. I plan on seeing what trouble I can get up to in jriver soon enough. Lol
Glad to hear, congrats!
Sunspark
21st December 2024, 08:35
I read a comment that said Nvidia's numbering is misleading because the "new" 4060s are really the performance of old 4050s, so take it all with a grain of salt and check benchmarks.
The new Intel cards do seem to be a very capable mid-range. Driver support will make the difference.. as well as manufacturing capacity.. they're not really making many of them.
WuNgUn
2nd January 2025, 03:32
Anyone using a Quadro P4000 with a DP to HDMI convertor to an HDR TV?
The adapter is the Club3D one which reportedly allows HDR pass thru.
However, I'm having mixed results.
In JRMC using their renderer, setting 'use HDR' cause the image to be very dark. Everything black is crushed. Pretty much the same with MadVR renderer. Been testing different drivers, but....
Edit: overlay settings say the the video is outputting in HDR Rec2020 420
nevcairiel
2nd January 2025, 09:39
Sounds like the HDR metadata doesn't get through the adapter properly. I guess your card doesn't have HDMI out on its own?
huhn
2nd January 2025, 10:08
active adapter are terrifying. play around with levels. setting the driver to limited range is maybe all you need.
HDR with missing meta data should elevate blacks not crush it. i guess.
edit. DP can do HDMI 1.4 passively with a simple passive cable that allows UHD 23p if that is all you need this should be far more reliable them active adapter.
wikipedia even states 2.0 in dual mode.
Sounds like the HDR metadata doesn't get through the adapter properly. I guess your card doesn't have HDMI out on its own?
i'm not aware of a single quadro with HDMI. the reference design doesn't have HDMI.
WuNgUn
2nd January 2025, 20:44
UHD 23P would be all I need for movies... But I also do vid editing and other things on my HTPC than needs 60P
I think it IS the Meta data. If I switch metadata off I'm MadVR, the levels look better/not ad washed out. Playing with the gamma and sharpness on the TV has it pretty close, I think....compared to direct streaming it to the TV with the built in Plex.
Thanks for the comments guys
active adapter are terrifying. play around with levels. setting the driver to limited range is maybe all you need.
HDR with missing meta data should elevate blacks not crush it. i guess.
edit. DP can do HDMI 1.4 passively with a simple passive cable that allows UHD 23p if that is all you need this should be far more reliable them active adapter.
wikipedia even states 2.0 in dual mode.
i'm not aware of a single quadro with HDMI. the reference design doesn't have HDMI.
Klaus1189
21st January 2025, 12:04
https://nvidia.custhelp.com/app/answers/detail/a_id/5614
dbcooper
24th January 2025, 04:08
I have an RTX 4070, and recently have noticed that when using an HDMI connection to my TV (typically 4K@23Hz, SDR) I get stuttering after x minutes of playback.
Setting the numbers of frames to present in advance in windowed mode to 1 can alleviate the problem, but frequently it doesn't. Should I revert to an earlier driver? I am using version 566.36 (Game Ready Driver). I don't have any problems with display port on my monitor (4K@60Hz, SDR).
I am using D3D11 decoding and presentation, Windows 11 (2024H2), and MadVR version: madVRhdrMeasure113. Vsync is on for MPC-HC, as is maximum performance mode for GPU power.
https://i.ibb.co/q9wTRgG/Clipboard-01-24-2025-01.png (https://ibb.co/ctd4N85)
dbcooper
24th January 2025, 05:14
Seems that there are many suggestions for Windows 11 2024H2. I will try them out and post details if any of them work.
dbcooper
24th January 2025, 09:49
Disabling Hardware-Accelerated GPU Scheduling seems to have fixed the presentation glitch problem with Windows 11 2024H2. No more stuttering (tested with about 3 hours of video playback).
Klaus1189
31st January 2025, 10:50
Is there any site where I can look up tests for hardware decoding capabilities of dedicated GPUs and iGPUs? I read that some iGPUs can output a 8k 60Hz signal to a 8k DP-Monitor, but suffer already problems on decoding 4k material, probably because of AV1.
huhn
31st January 2025, 12:46
that was this site. not been done anymore.
i get my 5800x3d today(edit: it was an 9800x3d) i can test the iGPU when i'm done building it.
this is the lowest of low iGPU.
intel iGPU decoder where always so blazing fast that the bit rate was irrelevant as long as the resolution was support 60 fps was no problem for them. and intel had one of the more worse ones for video playback because the iGPU had to do actual work.
AMD has the bad ones the first HEVC hardware decoder could barely do 4K 60 it was so low the queue in madVR needs quite sometime to fil up.
Klaus1189
31st January 2025, 13:03
Ok great. But I think you get a AM5 CPU, right?
huhn
31st January 2025, 13:46
yes that a AM5. i don't have an AM4 CPU with an iGPU.
edit: av1 profile 0 4K60 130-156 FPS
no problem what so ever. it tone mapped and downscaled it to 1080 in Realtime using mpcVR.
and there is nothing that is new and worse then this in a desktop PC.
bouwew
1st February 2025, 12:24
I tried the new Nvidia 572-driver, graphics is OK but the new audio driver seems to have a problem: no sound when playing any video with MPC-HC or -BE.
I double-checked the related settings and tried some other ideas but nothing worked. So I rolled-back to the 566-driver.
Maybe later I will try updating only the graphics driver.
I have an RTX3070.
clsid
1st February 2025, 16:08
Check if the correct audio device is still set as default. Windows can sometimes change the order when updating driver.
clsid
1st February 2025, 16:16
The 572 driver now supports RTX Super Resolution with HDR.
Can anyone test latest MPC-HC dev build (https://github.com/clsid2/mpc-hc/releases/tag/2.3.9.23) with a 1080p HDR video to test if it is working properly?
Judging from comments on reddit and nvidia forums, this driver is very buggy.
bouwew
1st February 2025, 17:41
Check if the correct audio device is still set as default. Windows can sometimes change the order when updating driver.
Yes, I had noticed that the default audio device had been reset and I changed it back to the Nvidia device.
I now remember (sorry getting older...) that audio worked initially, my receiver showed PCM. That what with the audio device being reset after the driver-update.
I was expecting DTS/Dolby Digital/DTS HD/etc. so I checked and changed the setting. At starting of a video the correct audio type is shown for a split second on my receiver display, then "decoder off".
Using MPC-HC with the Sanear audio renderer.
Bitstreaming via HDMI via a active HDMI splitter.
strumf666
1st February 2025, 22:19
yes that a AM5. i don't have an AM4 CPU with an iGPU.
edit: av1 profile 0 4K60 130-156 FPS
no problem what so ever. it tone mapped and downscaled it to 1080 in Realtime using mpcVR.
and there is nothing that is new and worse then this in a desktop PC.
Which cpu? Because 5800x3d is am4 and doesn't have na igpu.
huhn
2nd February 2025, 00:00
i wrote the wrong name was a 9800x3d dead anyway.
The 572 driver now supports RTX Super Resolution with HDR.
Can anyone test latest MPC-HC dev build (https://github.com/clsid2/mpc-hc/releases/tag/2.3.9.23) with a 1080p HDR video to test if it is working properly?
Judging from comments on reddit and nvidia forums, this driver is very buggy.
the build in mpcVR i guess?
if someone has a 1080p or lower HDR file i should be able to do that.
edit: it triggers at least i don't have an 1080 file that has something to show only found this in the fast: https://repo.jellyfin.org/test-videos/
Klaus1189
2nd February 2025, 09:47
The 9800X3D is dead already?
huhn
2nd February 2025, 12:07
The 9800X3D is dead already?
yes i can't do more tests. happens.
Klaus1189
2nd February 2025, 19:05
Too bad, how did you test to get the max supported framerate of hardware decoder? For now I can only play some testfiles and see if it plays alright. But to get a max supported framerate, I am lost.
What happened to it?
Do you get a replacement?
pirlouy
2nd February 2025, 19:24
10 Ghz was too much huhn ! :p
huhn
2nd February 2025, 19:49
Too bad, how did you test to get the max supported framerate of hardware decoder? For now I can only play some testfiles and see if it plays alright. But to get a max supported framerate, I am lost.
get DXVA checker: https://bluesky-soft.com/en/dxvac/download/?vs=4.6.1&tp=i&hs=75FF4737C076E60B97106AD898905CB9BFA9A038801791C214E309BB885C8204
install lavfilter set it to the decoder you want to test.
open DXVA checker go to DS/MF Decoder. k-lite codec pack has a tool to open filter setting if i remember correctly.
check decoders -> select media file -> click on the ">" under lavfilter which says "unsupported" -> decode performance
DXVA2/CPU 64 bit -> start
my 4060 with the 1080p AV1 file does over 700 FPS with 50% decoder engine load. it's way of saying i'm bored and the test numbers are nearly for sure to low because the file in question is to short and it doesn't matter at all..
What happened to it?
Do you get a replacement?
10 Ghz was too much huhn ! :p
in idle the PC crashed and that's it the mainbaord said ram and CPU defect. it lived for 3H. i did the typical things to test and nothing just dead.
10 GHZ man i did far more sinister things!
i TDP restricted it(eco mode) and disabled PBO. i know i'm a monster it reached utterly unsustainable 60.5 C under AVX 512 full load using a cheap tower cooler.
i got what i deserved.
it died on a Friday night it is currently frezzing in a DHL pack station for over 24 H. maybe not my smartest move... i'm only following orders.
SamuriHL
2nd February 2025, 21:38
I just got my 9800x3d Friday. Better not die! They aren't exactly easy to get.
Manni
2nd February 2025, 23:49
Latest nvidia 572.16 very buggy with my 3090 indeed. I get sound cut off for 5-10 seconds every 30 seconds, though I'm outputting audio with a DP>HDMI adapter that goes to my AVR. Reverting to 566.14 studio resolves the issue (I assume 566.36 game ready would work too).
Using the DP to HDMI on the 3090 allowed me to resolve the Atmos micro-audio drop on my 3090, so I saved a lot of money as I don't really need/want to upgrade to a 5080 at the moment. I might get a 5080 super with 24gb of VRAM when it's finally released.
The only drawboack of using the DP>HDMI to the AVR for audio is that it confuses the TV as it has two active inputs for the HTPC (the AVR goes to HDMI in 2 and the PC goes to HDMI in 1).
I have to switch off the AVR before putting the HTPC to sleep, and make sure it's off before I switch the PC back on, otherwise I get a black screen which is VERY annoying. If anyone has a solution for this, I'm all ears.
Otherwise, it's nice to be back to 4K119 10bits HDR for all content with 4:4:4 chroma.
Thanks to those who suggested this in another thread, it's a bit of a pain but it will do for now.
huhn
3rd February 2025, 00:18
you only need a device to accept the stream it doesn't have to be the TV.
maybe one of these HD fury vrroom stuff will not disconnect the signal even through it is not sending it to as display.
and the obvious one a monitor. which is very inelegant.
the new driver has a new audio driver so you can update the general driver but keep the old audio driver if you need the new driver for "something".
Manni
3rd February 2025, 01:53
you only need a device to accept the stream it doesn't have to be the TV.
maybe one of these HD fury vrroom stuff will not disconnect the signal even through it is not sending it to as display.
and the obvious one a monitor. which is very inelegant.
the new driver has a new audio driver so you can update the general driver but keep the old audio driver if you need the new driver for "something".
Thanks, yes I know but I need the AVR output to go to the TV because that's the one I use for all my other sources.
Anyway, I found a solution I think, I've disconnect the HDMI Out 1 that bypasses the VRROOM between the AVR and the TV and goes to the eARC input (HDMI 3) on the TV, and I'll use that output when I use the PC HDMI to the HDMI in 1 of the TV.
So all sources > AVR > HDMI Out 2 > TV HDMI input 2
When using the HTPC: Audio goes to AVR with AVR set to HDMI Out 1 (no cable) and TV Input set to HDMI 1 (direct from GPU).
That seems to work, I can still get the audio even when the video isn't connected. I need to do more tests, but it seems like it works better as the TV never gets the same source from two different inputs.
Klaus1189
9th February 2025, 21:09
https://youtu.be/41eZsOYUVx0?si=jXMDW-b2mh6V2pta
huhn
10th February 2025, 00:25
someone should show nvidia this magical device: https://en.wikipedia.org/wiki/IEC_60320#C13/C14_coupler
no microchip, no 10+ lanes 3k+ watt power rating 240 volt and 16 man amps (maybe enough for 3 more generation of GPUs!). already used in the PC space!
why stop there just build a PSU into the GPU it's 600 watts many PSU are smaller anyway. problem solved.
Klaus1189
11th February 2025, 17:53
Very interesting video - watch completely. This is insane ...
GERMAN:
https://www.youtube.com/watch?v=puQ3ayJKWds
EN:
https://www.youtube.com/watch?v=Ndmoi1s0ZaY
Klaus1189
11th February 2025, 20:14
https://www.youtube.com/watch?v=kb5YzMoVQyw
strumf666
14th February 2025, 17:58
Adrenaline 25.2.1 non-whql brought back the prolonged black screen delay before playback for me.
Manni
22nd February 2025, 16:07
Seems to resolve the audio issue I had with 572.16 (frequent audio drop outs), though I'm back to a single HDMI out (no DP out anymore, it was causing too many issues after standby), so it might just be that.
It also looks like, at least with jRiver, it's not necessary to set vsync on in nv panel in order to avoid unreported frame drops. I've only played a short bit of my test clip (Pacific Rim) and I couldn't see any unreported frame drops. With previous drivers, it was obvious and frequent.
If this isn't confirmed, it would be great if jRiver allowed to specify if we want vsync enabled or not, that way we could leave "Use the 3D App setting" option in NV panel.
I only had to disable Gsync, as always. Normal power seems to be working fine too (but that was the case already with previous versions).
huhn
23rd February 2025, 18:46
just use the vsync option for a specific exe there was never a need to use it globally.
and every program decide if vsync is used or not it's just not working for some reason with madVR. forcing vsync in the nv control shouldn't do anything in the first place but it does.
Manni
24th February 2025, 00:59
Getting random black screen and complete loss of HDMI sync with this, even when playing content, so reversing to 566.14.
EDIT: Scratch that, still getting the black outs and HDMI losses of sync, so most likely not the driver.
Klaus1189
5th March 2025, 07:35
http://youtube.com/post/UgkxyemAtz460QjT-24foI-frCMfbu86fKiQ?si=VxUwpuFn9spV6_XK
zealvix
7th March 2025, 04:37
Anyone else getting timeout/crashing issue when using madvr with radeon GPU?
Seems to occur on 24.9.1 onward and persist in latest 25.3.1.
This is on a 7840HS with Radeon 780m.
Didnt see this mentioned in the PDF, or this don't affect dedicated cards such as the new RX 9070/XT ?
huhn
7th March 2025, 04:49
can you be a bit more precise?
like a crash report or something.
the only general crash related to madVR i know of it d3d11 native decode and then skip around the file a lot which 99% of all user don't do.
zealvix
7th March 2025, 06:38
can you be a bit more precise?
like a crash report or something.
the only general crash related to madVR i know of it d3d11 native decode and then skip around the file a lot which 99% of all user don't do.
I am using mpc-hc (from clsid2 github).
When you are already playing a file with madvr, if you try to switch to another file (either by file ->open or just using the page up/down down key to switch to another file in the same directory), it will freeze for awhile before throwing a timeout error (attached).
Pressing NO will usually proceed to the next file (after some additional waiting), but occassionally the whole player will just crash.
There are also occassions where the timeout prompt did not appear at all, and the player just auto close/crash.
Did not occur with MPC Video Renderer.
Same results with both LavFilters 0.79.2 from github or the ones inbuilt in MPC-HC.
Only started from24.9.1 onward and persist in latest 25.3.1.
Downgrading back to 24.8.1 resolves the issue when using madvr.
Just interested to know if there are others encountering the same, and particularly whether it affects dedicated GPU as I am interested in getting a 9060/9070 XT card, and for those you can only use 25.3.1 and newer.
clsid
7th March 2025, 11:27
Solution is simple:
1. Report bug to AMD (https://www.amd.com/en/resources/support-articles/faqs/AMDBRT.html)
2. Report bug to AMD (https://www.amd.com/en/resources/support-articles/faqs/AMDBRT.html)
3. Report bug to AMD (https://www.amd.com/en/resources/support-articles/faqs/AMDBRT.html)
The only reason it still happens is because people are skipping step 1 to 3.
Step 4 is to not use Error Diffusion 2 in Madvr. And step 5 is to disable seekbar preview in MPC-HC until AND driver bug is fixed.
zealvix
7th March 2025, 13:08
Solution is simple:
1. Report bug to AMD (https://www.amd.com/en/resources/support-articles/faqs/AMDBRT.html)
2. Report bug to AMD (https://www.amd.com/en/resources/support-articles/faqs/AMDBRT.html)
3. Report bug to AMD (https://www.amd.com/en/resources/support-articles/faqs/AMDBRT.html)
The only reason it still happens is because people are skipping step 1 to 3.
Step 4 is to not use Error Diffusion 2 in Madvr. And step 5 is to disable seekbar preview in MPC-HC until AND driver bug is fixed.
Already submitted a bug report back on 24.9.1, maybe I should try again now on 25.3.1....
Not using error diffusion 2 in madvr.
For the seekbar preview, are you referring to options -->player -->user interface -->show video preview?
If yes, mine is already disabled (think its disabled by default?), but still getting the timeout error.
Anyway, glad to confirm its not just me then, maybe it should be added to the pdf in the first post as well.
strumf666
14th March 2025, 12:35
Adrenaline 25.2.1 non-whql brought back the prolonged black screen delay before playback for me.
And 25.3.1 made it even worse.
edit: Changing dithering from ED2 to Ordered fixed the black screen delay :)
v0lt
12th April 2025, 06:06
For your information.
On Nvidia video cards with new drivers (572.xx) YUY2 support in MPC Video Renderer for DXVA2 video processor (Direct3D 9) is broken.
You most likely will not notice the problem, because Direct3D 11 is used by default on modern Windows.
PS: There is no problem with the old version of the video driver (566.36).
Klaus1189
17th April 2025, 09:46
576.02 fixes hardware deinterlacing on all RTX50 cards
huhn
17th April 2025, 13:51
can you check if they fixed the chroma subsamppling position?
Klaus1189
17th April 2025, 13:55
Yeah, just instruct me how to do it. Special testfile?
huhn
17th April 2025, 14:11
madVR any sdr file that is not black white.
control+shift+alt+f12 twice until it says Cb
control+shift+alt+t unitl it says video mode
control+shift+alt+d to toggle and see if the images moves
this should work as long as you are not using an native decoder
4000 series is broken.
Klaus1189
17th April 2025, 14:14
Ok, i test. No Native decoder, do you mean I should use a software decoder instead of hardware decoder? Correct me if I unterstood it wrong.
huhn
17th April 2025, 14:25
yes software or copyback not native.
Klaus1189
17th April 2025, 14:38
control+shift+alt+f12 twice until it says Cb -> "decoding matrix: Cb"
control+shift+alt+t unitl it says video mode -> "source type: video"
control+shift+alt+d to toggle and see if the images moves -> "deinterlacing: off" / "deinterlacing: on" / "deinterlacing: autodetect (off)"
I think I am doing something wrong since it tells me "deinterlacing" ...
huhn
17th April 2025, 14:45
you are going great. that's exactly what should happen.
we use deint to toggle between DXVA processing and normal processing while still having access to the Cb channel.
you now just need to look at the image and see if it moves when you toggle deinterlacing on off i'm mostly interested in left right movement
Klaus1189
17th April 2025, 14:55
I pressed pause to see it and indeed moves a bit when deinterlacing toggles. I made screenshots you can compare:
https://drive.google.com/drive/folders/1JfF4g1GZyFavZBsZeFdNTjU2AMjkLvkg?usp=sharing
I hope this is what you wanted to see. I am on latest driver 576.02, maybe 40 series does work also with this version?
dbcooper
17th April 2025, 14:59
Tested the latest Nvidia driver 576.02 on Win11 2024H2. Still stutters and requires hardware accelerated GPU scheduling to be turned off.
Is there a MadVR beta version that fixes this?
Klaus1189
17th April 2025, 15:01
Is that Nvidia issue or Win11 24H2 issue?
dbcooper
17th April 2025, 15:12
Is that Nvidia issue or Win11 24H2 issue?
I think it's a Win11 24H2 issue?
Klaus1189
17th April 2025, 16:05
For your information.
On Nvidia video cards with new drivers (572.xx) YUY2 support in MPC Video Renderer for DXVA2 video processor (Direct3D 9) is broken.
You most likely will not notice the problem, because Direct3D 11 is used by default on modern Windows.
PS: There is no problem with the old version of the video driver (566.36).
I just tested Spring samples and set MPC-VR to D3D9:
All files were played using software decoding except 2:
Spring_HEVC420p10bit.mp4
Spring_VP9_420p10bit.webm
Is this related to that?
huhn
17th April 2025, 23:45
I pressed pause to see it and indeed moves a bit when deinterlacing toggles. I made screenshots you can compare:
https://drive.google.com/drive/folders/1JfF4g1GZyFavZBsZeFdNTjU2AMjkLvkg?usp=sharing
I hope this is what you wanted to see. I am on latest driver 576.02, maybe 40 series does work also with this version?
yes that's the bug nvidia uses the wrong chroma placement and that's the result.
Tested the latest Nvidia driver 576.02 on Win11 2024H2. Still stutters and requires hardware accelerated GPU scheduling to be turned off.
Is there a MadVR beta version that fixes this?
i'm still testing but i have madVR running flawless with hags on rebar on mpo on default power settings and my old custom queue settings.
yes i'm asking for issues sadly i can not reproduce them currently on the new HTPC install.
on my gaming PC with AMD it's a horror show.
Is that Nvidia issue or Win11 24H2 issue?
nearly for sure madVR other programs work kind of.
Klaus1189
18th April 2025, 08:02
Too bad. How is AMD and Intel in this regard?
huhn
18th April 2025, 10:40
as far as i know working just fine. i have not tested intel in for ever.
strumf666
29th April 2025, 20:43
Adrenalin 25.4.1 seems to be working as expected for madvr.
v0lt
30th April 2025, 04:42
I just tested Spring samples and set MPC-VR to D3D9:
All files were played using software decoding except 2:
Spring_HEVC420p10bit.mp4
Spring_VP9_420p10bit.webm
Is this related to that?
No. I wrote about the work of DXVA2 video processor with YUY2 format.
SamuriHL
30th April 2025, 21:46
Let's hope they actually fixed things this time....
Klaus1189
30th April 2025, 22:39
For your information.
On Nvidia video cards with new drivers (572.xx) YUY2 support in MPC Video Renderer for DXVA2 video processor (Direct3D 9) is broken.
You most likely will not notice the problem, because Direct3D 11 is used by default on modern Windows.
PS: There is no problem with the old version of the video driver (566.36).
I just tested Spring samples and set MPC-VR to D3D9:
All files were played using software decoding except 2:
Spring_HEVC420p10bit.mp4
Spring_VP9_420p10bit.webm
Is this related to that?
No. I wrote about the work of DXVA2 video processor with YUY2 format.
Do you have a sample file for YUY2?
I just upgraded to 576.28 and now I just tested Spring samples and set MPC-VR to D3D9:
I retested these:
Spring_HEVC420p10bit.mp4
Spring_VP9_420p10bit.webm
Now working... ...and hardware deinterlacer also still works, so this is 2nd driver for RTX50 cards which has working hardware deinterlacer...
Do you have a sample file for YUY2?
You can use software decoding and force YUY2 output in the decoder.
You can also use the Spring_HEVC422p08bit.mp4 file, which will be output by MPC-BE decoder in YUY2 format by default.
Klaus1189
31st July 2025, 20:55
New 580.88 Nvidia driver has new HD Audio Driver
v0lt
29th August 2025, 18:49
I have updated the D3DVideoDecoderInfo (https://disk.yandex.ru/d/CEWDisB2Cw-Q9A) utility which shows supported D3D11 and D3D12 decoders.
Usage: Run "get_d3d_decoders_txt.cmd" and get the list of decoders in "d3d_decoders.txt".
I wonder if HEVC Rext support for Direct3D 12 has appeared in the new Nvidia drivers?
Klaus1189
29th August 2025, 19:36
=== Direct3D 11 ===
Graphics adapter 0: NVIDIA GeForce RTX 5090
D3D11 video decoders [34]:
MPEG1_AND_MPEG2 (NV12, 420_OPAQUE)
MPEG2 (NV12, 420_OPAQUE)
MPEG1 (NV12, 420_OPAQUE)
VC1_D2010 (NV12, 420_OPAQUE)
VC1 (NV12, 420_OPAQUE)
H264_STEREO_PROGRESSIVE (NV12, 420_OPAQUE)
H264_STEREO (NV12, 420_OPAQUE)
H264 (NV12, 420_OPAQUE)
HEVC_MAIN (NV12, 420_OPAQUE)
HEVC_MAIN10 (P010, 420_OPAQUE)
HEVC_MAIN12 (P010, 420_OPAQUE)
HEVC_MAIN10_422 (420_OPAQUE, YUY2, Y210)
HEVC_MAIN12_422 (420_OPAQUE, Y216)
HEVC_MAIN_444 (AYUV, 420_OPAQUE)
HEVC_MAIN10_444 (Y410, 420_OPAQUE)
HEVC_MAIN12_444 (Y416, 420_OPAQUE)
MPEG4PT2_SIMPLE (NV12, 420_OPAQUE)
MPEG4PT2_ADVSIMPLE_NOGMC (NV12, 420_OPAQUE)
MPEG4pt2_AdvSimple_Nvidia (NV12, 420_OPAQUE)
MJPEG_Nvidia (AYUV, NV12, 420_OPAQUE, YUY2)
MJPEG_420 (AYUV, NV12, 420_OPAQUE, YUY2)
MJPEG_422 (AYUV, NV12, 420_OPAQUE, YUY2)
MJPEG_444 (AYUV, NV12, 420_OPAQUE, YUY2)
JPEG_444 (AYUV, NV12, 420_OPAQUE, YUY2)
VP9 (NV12, 420_OPAQUE)
VP9_10BIT_PROFILE2 (P010, 420_OPAQUE)
AV1_PROFILE0 (NV12, P010, 420_OPAQUE)
7 unknown decoders are not shown.
Graphics adapter 1: Microsoft Basic Render Driver
ERROR: Failed to get ID3D11VideoDevice.
=== Direct3D 12 ===
Graphics adapter 0: NVIDIA GeForce RTX 5090
D3D12 video decoders [14]:
MPEG1_AND_MPEG2 (NV12, 420_OPAQUE) Tier 2
MPEG2 (NV12, 420_OPAQUE) Tier 2
VC1_D2010 (NV12, 420_OPAQUE) Tier 2
VC1 (NV12, 420_OPAQUE) Tier 2
H264_STEREO_PROGRESSIVE (NV12, 420_OPAQUE) Tier 2
H264_STEREO (NV12, 420_OPAQUE) Tier 2
H264 (NV12, 420_OPAQUE) Tier 2
HEVC_MAIN (NV12, 420_OPAQUE) Tier 2
HEVC_MAIN10 (P010, 420_OPAQUE) Tier 2
MPEG4PT2_SIMPLE (NV12, 420_OPAQUE) Tier 2
MPEG4PT2_ADVSIMPLE_NOGMC (NV12, 420_OPAQUE) Tier 2
VP9 (NV12, 420_OPAQUE) Tier 2
VP9_10BIT_PROFILE2 (P010, 420_OPAQUE) Tier 2
AV1_PROFILE0 (NV12, P010, 420_OPAQUE) Tier 2
Graphics adapter 1: Microsoft Basic Render Driver
ERROR: Failed to get ID3D12VideoDevice.
v0lt
29th August 2025, 20:03
@Klaus1189
Thanks. I see that HEVC Rext is still not supported in Direct3D 12. Although D3D11 decoder GUIDs are in the latest Windows 11 SDK.
littleD
6th October 2025, 07:53
=== Direct3D 11 ===
Graphics adapter 0: NVIDIA GeForce RTX 5090
D3D11 video decoders [34]:
MPEG1_AND_MPEG2 (NV12, 420_OPAQUE)
MPEG2 (NV12, 420_OPAQUE)
MPEG1 (NV12, 420_OPAQUE)
VC1_D2010 (NV12, 420_OPAQUE)
VC1 (NV12, 420_OPAQUE)
H264_STEREO_PROGRESSIVE (NV12, 420_OPAQUE)
H264_STEREO (NV12, 420_OPAQUE)
H264 (NV12, 420_OPAQUE)
HEVC_MAIN (NV12, 420_OPAQUE)
HEVC_MAIN10 (P010, 420_OPAQUE)
HEVC_MAIN12 (P010, 420_OPAQUE)
HEVC_MAIN10_422 (420_OPAQUE, YUY2, Y210)
HEVC_MAIN12_422 (420_OPAQUE, Y216)
HEVC_MAIN_444 (AYUV, 420_OPAQUE)
HEVC_MAIN10_444 (Y410, 420_OPAQUE)
HEVC_MAIN12_444 (Y416, 420_OPAQUE)
MPEG4PT2_SIMPLE (NV12, 420_OPAQUE)
MPEG4PT2_ADVSIMPLE_NOGMC (NV12, 420_OPAQUE)
MPEG4pt2_AdvSimple_Nvidia (NV12, 420_OPAQUE)
MJPEG_Nvidia (AYUV, NV12, 420_OPAQUE, YUY2)
MJPEG_420 (AYUV, NV12, 420_OPAQUE, YUY2)
MJPEG_422 (AYUV, NV12, 420_OPAQUE, YUY2)
MJPEG_444 (AYUV, NV12, 420_OPAQUE, YUY2)
JPEG_444 (AYUV, NV12, 420_OPAQUE, YUY2)
VP9 (NV12, 420_OPAQUE)
VP9_10BIT_PROFILE2 (P010, 420_OPAQUE)
AV1_PROFILE0 (NV12, P010, 420_OPAQUE)
7 unknown decoders are not shown.
Graphics adapter 1: Microsoft Basic Render Driver
ERROR: Failed to get ID3D11VideoDevice.
=== Direct3D 12 ===
Graphics adapter 0: NVIDIA GeForce RTX 5090
D3D12 video decoders [14]:
MPEG1_AND_MPEG2 (NV12, 420_OPAQUE) Tier 2
MPEG2 (NV12, 420_OPAQUE) Tier 2
VC1_D2010 (NV12, 420_OPAQUE) Tier 2
VC1 (NV12, 420_OPAQUE) Tier 2
H264_STEREO_PROGRESSIVE (NV12, 420_OPAQUE) Tier 2
H264_STEREO (NV12, 420_OPAQUE) Tier 2
H264 (NV12, 420_OPAQUE) Tier 2
HEVC_MAIN (NV12, 420_OPAQUE) Tier 2
HEVC_MAIN10 (P010, 420_OPAQUE) Tier 2
MPEG4PT2_SIMPLE (NV12, 420_OPAQUE) Tier 2
MPEG4PT2_ADVSIMPLE_NOGMC (NV12, 420_OPAQUE) Tier 2
VP9 (NV12, 420_OPAQUE) Tier 2
VP9_10BIT_PROFILE2 (P010, 420_OPAQUE) Tier 2
AV1_PROFILE0 (NV12, P010, 420_OPAQUE) Tier 2
Graphics adapter 1: Microsoft Basic Render Driver
ERROR: Failed to get ID3D12VideoDevice.
Not Rext but additional color spaces in D3D12 in newest drivers.
=== Direct3D 11 ===
Graphics adapter 0: AMD Radeon(TM) Graphics
D3D11 video decoders [20]:
H264 (NV12)
H264_NoFGT_AMD (NV12)
H264_Multiview_AMD (NV12)
H264_STEREO_PROGRESSIVE (NV12)
H264_STEREO (NV12)
MJPEG_AMD (NV12, YUY2)
HEVC_MAIN (NV12)
HEVC_MAIN10 (NV12, P010)
VP9 (NV12)
VP9_10BIT_PROFILE2 (NV12, P010)
AV1_PROFILE0 (NV12, P010)
9 unknown decoders are not shown.
Graphics adapter 1: NVIDIA GeForce RTX 4050 Laptop GPU
D3D11 video decoders [27]:
MPEG1_AND_MPEG2 (NV12, 420_OPAQUE)
MPEG2 (NV12, 420_OPAQUE)
MPEG1 (NV12, 420_OPAQUE)
VC1_D2010 (NV12, 420_OPAQUE)
VC1 (NV12, 420_OPAQUE)
H264_STEREO_PROGRESSIVE (NV12, 420_OPAQUE)
H264_STEREO (NV12, 420_OPAQUE)
H264 (NV12, 420_OPAQUE)
HEVC_MAIN (NV12, 420_OPAQUE)
HEVC_MAIN10 (P010, 420_OPAQUE)
HEVC_MAIN12 (P010, 420_OPAQUE)
HEVC_MAIN_444 (AYUV, 420_OPAQUE)
HEVC_MAIN10_444 (Y410, 420_OPAQUE)
HEVC_MAIN12_444 (Y416, 420_OPAQUE)
MPEG4PT2_SIMPLE (NV12, 420_OPAQUE)
MPEG4PT2_ADVSIMPLE_NOGMC (NV12, 420_OPAQUE)
MPEG4pt2_AdvSimple_Nvidia (NV12, 420_OPAQUE)
MJPEG_Nvidia (NV12, 420_OPAQUE, YUY2)
VP9 (NV12, 420_OPAQUE)
VP9_10BIT_PROFILE2 (P010, 420_OPAQUE)
AV1_PROFILE0 (NV12, P010, 420_OPAQUE)
6 unknown decoders are not shown.
Graphics adapter 2: Microsoft Basic Render Driver
ERROR: Failed to get ID3D11VideoDevice.
=== Direct3D 12 ===
Graphics adapter 0: AMD Radeon(TM) Graphics
D3D12 video decoders [6]:
H264 (NV12) Tier 2
HEVC_MAIN (NV12) Tier 2
VP9 (NV12) Tier 2
HEVC_MAIN10 (NV12, P010) Tier 2
VP9_10BIT_PROFILE2 (NV12, P010) Tier 2
AV1_PROFILE0 (NV12, P010) Tier 2
Graphics adapter 1: NVIDIA GeForce RTX 4050 Laptop GPU
D3D12 video decoders [17]:
MPEG1_AND_MPEG2 (NV12, 420_OPAQUE) Tier 2
MPEG2 (NV12, 420_OPAQUE) Tier 2
VC1_D2010 (NV12, 420_OPAQUE) Tier 2
VC1 (NV12, 420_OPAQUE) Tier 2
H264_STEREO_PROGRESSIVE (NV12, 420_OPAQUE) Tier 2
H264_STEREO (NV12, 420_OPAQUE) Tier 2
H264 (NV12, 420_OPAQUE) Tier 2
HEVC_MAIN (NV12, 420_OPAQUE) Tier 2
HEVC_MAIN10 (P010, 420_OPAQUE) Tier 2
HEVC_MAIN_444 (AYUV, 420_OPAQUE) Tier 2
HEVC_MAIN10_444 (Y410, 420_OPAQUE) Tier 2
HEVC_MAIN12_444 (Y416, 420_OPAQUE) Tier 2
MPEG4PT2_SIMPLE (NV12, 420_OPAQUE) Tier 2
MPEG4PT2_ADVSIMPLE_NOGMC (NV12, 420_OPAQUE) Tier 2
VP9 (NV12, 420_OPAQUE) Tier 2
VP9_10BIT_PROFILE2 (P010, 420_OPAQUE) Tier 2
AV1_PROFILE0 (NV12, P010, 420_OPAQUE) Tier 2
Graphics adapter 2: Microsoft Basic Render Driver
ERROR: Failed to get ID3D12VideoDevice.
huhn
6th October 2025, 12:37
444 is added which these GPU can do for a decade or longer. this was lossless only in the past.
rext needs 5000 series so does 422.
petran79
10th October 2025, 20:23
I upgraded the system, going from a 1080 GTX to a 5060 RTX Ti 16 GB and that GPU can play videos on high and very high settings without issue or dropped frames and around 30 % lower usage too.
However on Potplayer after a while I notice an issue with madvr where the video slows down and plays as if in interframe blending mode
No such issue on MPC with madvr and same LAV filters.
Klaus1189
12th October 2025, 09:32
@petran79: Sorry for this I can not help you, since I don't use Potplayer.
Klaus1189
12th October 2025, 09:35
Not Rext but additional color spaces in D3D12 in newest drivers.
=== Direct3D 11 ===
Graphics adapter 0: AMD Radeon(TM) Graphics
D3D11 video decoders [20]:
H264 (NV12)
H264_NoFGT_AMD (NV12)
H264_Multiview_AMD (NV12)
H264_STEREO_PROGRESSIVE (NV12)
H264_STEREO (NV12)
MJPEG_AMD (NV12, YUY2)
HEVC_MAIN (NV12)
HEVC_MAIN10 (NV12, P010)
VP9 (NV12)
VP9_10BIT_PROFILE2 (NV12, P010)
AV1_PROFILE0 (NV12, P010)
9 unknown decoders are not shown.
Graphics adapter 1: NVIDIA GeForce RTX 4050 Laptop GPU
D3D11 video decoders [27]:
MPEG1_AND_MPEG2 (NV12, 420_OPAQUE)
MPEG2 (NV12, 420_OPAQUE)
MPEG1 (NV12, 420_OPAQUE)
VC1_D2010 (NV12, 420_OPAQUE)
VC1 (NV12, 420_OPAQUE)
H264_STEREO_PROGRESSIVE (NV12, 420_OPAQUE)
H264_STEREO (NV12, 420_OPAQUE)
H264 (NV12, 420_OPAQUE)
HEVC_MAIN (NV12, 420_OPAQUE)
HEVC_MAIN10 (P010, 420_OPAQUE)
HEVC_MAIN12 (P010, 420_OPAQUE)
HEVC_MAIN_444 (AYUV, 420_OPAQUE)
HEVC_MAIN10_444 (Y410, 420_OPAQUE)
HEVC_MAIN12_444 (Y416, 420_OPAQUE)
MPEG4PT2_SIMPLE (NV12, 420_OPAQUE)
MPEG4PT2_ADVSIMPLE_NOGMC (NV12, 420_OPAQUE)
MPEG4pt2_AdvSimple_Nvidia (NV12, 420_OPAQUE)
MJPEG_Nvidia (NV12, 420_OPAQUE, YUY2)
VP9 (NV12, 420_OPAQUE)
VP9_10BIT_PROFILE2 (P010, 420_OPAQUE)
AV1_PROFILE0 (NV12, P010, 420_OPAQUE)
6 unknown decoders are not shown.
Graphics adapter 2: Microsoft Basic Render Driver
ERROR: Failed to get ID3D11VideoDevice.
=== Direct3D 12 ===
Graphics adapter 0: AMD Radeon(TM) Graphics
D3D12 video decoders [6]:
H264 (NV12) Tier 2
HEVC_MAIN (NV12) Tier 2
VP9 (NV12) Tier 2
HEVC_MAIN10 (NV12, P010) Tier 2
VP9_10BIT_PROFILE2 (NV12, P010) Tier 2
AV1_PROFILE0 (NV12, P010) Tier 2
Graphics adapter 1: NVIDIA GeForce RTX 4050 Laptop GPU
D3D12 video decoders [17]:
MPEG1_AND_MPEG2 (NV12, 420_OPAQUE) Tier 2
MPEG2 (NV12, 420_OPAQUE) Tier 2
VC1_D2010 (NV12, 420_OPAQUE) Tier 2
VC1 (NV12, 420_OPAQUE) Tier 2
H264_STEREO_PROGRESSIVE (NV12, 420_OPAQUE) Tier 2
H264_STEREO (NV12, 420_OPAQUE) Tier 2
H264 (NV12, 420_OPAQUE) Tier 2
HEVC_MAIN (NV12, 420_OPAQUE) Tier 2
HEVC_MAIN10 (P010, 420_OPAQUE) Tier 2
HEVC_MAIN_444 (AYUV, 420_OPAQUE) Tier 2
HEVC_MAIN10_444 (Y410, 420_OPAQUE) Tier 2
HEVC_MAIN12_444 (Y416, 420_OPAQUE) Tier 2
MPEG4PT2_SIMPLE (NV12, 420_OPAQUE) Tier 2
MPEG4PT2_ADVSIMPLE_NOGMC (NV12, 420_OPAQUE) Tier 2
VP9 (NV12, 420_OPAQUE) Tier 2
VP9_10BIT_PROFILE2 (P010, 420_OPAQUE) Tier 2
AV1_PROFILE0 (NV12, P010, 420_OPAQUE) Tier 2
Graphics adapter 2: Microsoft Basic Render Driver
ERROR: Failed to get ID3D12VideoDevice.
I retested my RTX50 card with v0lt's tool:
I have updated the D3DVideoDecoderInfo (https://disk.yandex.ru/d/CEWDisB2Cw-Q9A) utility which shows supported D3D11 and D3D12 decoders.
Usage: Run "get_d3d_decoders_txt.cmd" and get the list of decoders in "d3d_decoders.txt".
I wonder if HEVC Rext support for Direct3D 12 has appeared in the new Nvidia drivers?
Here is the result:
=== Direct3D 11 ===
Graphics adapter 0: NVIDIA GeForce RTX 5090
D3D11 video decoders [34]:
MPEG1_AND_MPEG2 (NV12, 420_OPAQUE)
MPEG2 (NV12, 420_OPAQUE)
MPEG1 (NV12, 420_OPAQUE)
VC1_D2010 (NV12, 420_OPAQUE)
VC1 (NV12, 420_OPAQUE)
H264_STEREO_PROGRESSIVE (NV12, 420_OPAQUE)
H264_STEREO (NV12, 420_OPAQUE)
H264 (NV12, 420_OPAQUE)
HEVC_MAIN (NV12, 420_OPAQUE)
HEVC_MAIN10 (P010, 420_OPAQUE)
HEVC_MAIN12 (P010, 420_OPAQUE)
HEVC_MAIN10_422 (420_OPAQUE, YUY2, Y210)
HEVC_MAIN12_422 (420_OPAQUE, Y216)
HEVC_MAIN_444 (AYUV, 420_OPAQUE)
HEVC_MAIN10_444 (Y410, 420_OPAQUE)
HEVC_MAIN12_444 (Y416, 420_OPAQUE)
MPEG4PT2_SIMPLE (NV12, 420_OPAQUE)
MPEG4PT2_ADVSIMPLE_NOGMC (NV12, 420_OPAQUE)
MPEG4pt2_AdvSimple_Nvidia (NV12, 420_OPAQUE)
MJPEG_Nvidia (AYUV, NV12, 420_OPAQUE, YUY2)
MJPEG_420 (AYUV, NV12, 420_OPAQUE, YUY2)
MJPEG_422 (AYUV, NV12, 420_OPAQUE, YUY2)
MJPEG_444 (AYUV, NV12, 420_OPAQUE, YUY2)
JPEG_444 (AYUV, NV12, 420_OPAQUE, YUY2)
VP9 (NV12, 420_OPAQUE)
VP9_10BIT_PROFILE2 (P010, 420_OPAQUE)
AV1_PROFILE0 (NV12, P010, 420_OPAQUE)
7 unknown decoders are not shown.
Graphics adapter 1: AMD Radeon(TM) Graphics
D3D11 video decoders [20]:
H264 (NV12)
H264_NoFGT_AMD (NV12)
H264_Multiview_AMD (NV12)
H264_STEREO_PROGRESSIVE (NV12)
H264_STEREO (NV12)
MJPEG_AMD (NV12, YUY2)
HEVC_MAIN (NV12)
HEVC_MAIN10 (NV12, P010)
VP9 (NV12)
VP9_10BIT_PROFILE2 (NV12, P010)
AV1_PROFILE0 (NV12, P010)
9 unknown decoders are not shown.
Graphics adapter 2: Microsoft Basic Render Driver
ERROR: Failed to get ID3D11VideoDevice.
=== Direct3D 12 ===
Graphics adapter 0: NVIDIA GeForce RTX 5090
D3D12 video decoders [23]:
MPEG1_AND_MPEG2 (NV12, 420_OPAQUE) Tier 2
MPEG2 (NV12, 420_OPAQUE) Tier 2
VC1_D2010 (NV12, 420_OPAQUE) Tier 2
VC1 (NV12, 420_OPAQUE) Tier 2
H264_STEREO_PROGRESSIVE (NV12, 420_OPAQUE) Tier 2
H264_STEREO (NV12, 420_OPAQUE) Tier 2
H264 (NV12, 420_OPAQUE) Tier 2
HEVC_MAIN (NV12, 420_OPAQUE) Tier 2
HEVC_MAIN10 (P010, 420_OPAQUE) Tier 2
HEVC_MAIN10_422 (YUY2, Y210, 420_OPAQUE) Tier 2
HEVC_MAIN12_422 (Y216, 420_OPAQUE) Tier 2
HEVC_MAIN_444 (AYUV, 420_OPAQUE) Tier 2
HEVC_MAIN10_444 (Y410, 420_OPAQUE) Tier 2
HEVC_MAIN12_444 (Y416, 420_OPAQUE) Tier 2
MPEG4PT2_SIMPLE (NV12, 420_OPAQUE) Tier 2
MPEG4PT2_ADVSIMPLE_NOGMC (NV12, 420_OPAQUE) Tier 2
MJPEG_420 (NV12) Tier 2
MJPEG_422 (YUY2) Tier 2
MJPEG_444 (AYUV) Tier 2
JPEG_444 (AYUV) Tier 2
VP9 (NV12, 420_OPAQUE) Tier 2
VP9_10BIT_PROFILE2 (P010, 420_OPAQUE) Tier 2
AV1_PROFILE0 (NV12, P010, 420_OPAQUE) Tier 2
Graphics adapter 1: AMD Radeon(TM) Graphics
D3D12 video decoders [6]:
H264 (NV12) Tier 2
HEVC_MAIN (NV12) Tier 2
VP9 (NV12) Tier 2
HEVC_MAIN10 (NV12, P010) Tier 2
VP9_10BIT_PROFILE2 (NV12, P010) Tier 2
AV1_PROFILE0 (NV12, P010) Tier 2
Graphics adapter 2: Microsoft Basic Render Driver
ERROR: Failed to get ID3D12VideoDevice.
What are the "unknown decoders" which are not shown?
ryrynz
17th October 2025, 09:21
Haven't had audio drop outs in quite a while.. after installing 581.57 I experienced one playing back video (MPC-VR). It uses the same audio driver as 581.29 so unsure what would be causing it. RTX 3060.
Manni
17th October 2025, 10:00
Haven't had audio drop outs in quite a while.. after installing 581.57 I experienced one playing back video (MPC-VR). It uses the same audio driver as 581.29 so unsure what would be causing it. RTX 3060.
Ampere causes audio dropouts when bitsreaming Atmos over HDMI 2.1 to an AVR (or possibly a TV). If you're not bitstreaming, if you're not playing Atmos or if you're using an HDMI 2.0 input on your 2.1 AVR (or a HDMI 2.0 AVR), there shouldn't be any audio drops with the latest version of LAV.
I replaced my 3090 with a 5090 in my HTPC (and my 3060 with a 3000 Pro in my laptop) partially because of this issue with Ampere.
This isn't an issue with Ada Lovelace or Blackwell, only with Ampere (nVidia acknowledged the issue but never fixed it).
ryrynz
17th October 2025, 22:18
I used to use bitstreaming, but I turned it off after all the issues.. using LAV + MPC Audio / Video over HDMI to my Yamaha AVR, I reverted back to 581.29 and there's been no audio drop outs yet. So looks fixed.
*edit* nope. Wonder what triggered it. Trying a clean install and rollback LAV.
No drop outs so far, wonder if the updated ffmpeg in LAV 0.80.0-8 may have been responsible. On 581.57 now.
pirlouy
23rd October 2025, 14:22
I know a lot of people here use nVidia GPU. I plan to buy a Radeon 9060 XT (16GB). I wanted to be sure there are no side effects with AMD drivers. I don't use any post-processing thing, I only need good 23.976 Hz support and correct H264 & H265 (4k) hardware decoding.
I use a bit of deinterlacing too for DVB. I think Huhn mentionned problems, but I hope it's able to keep fluid 50i fps, quality is not that important (it's for sport).
So if someone thinks I'm about to make a mistake, please stop me !
huhn
23rd October 2025, 22:25
deint is so broken you really want to use something else to deint.
and yes there are major issues because i have one https://bugs.madshi.net/view.php?id=741 that's not funny
also error diffusion doesn't work properly.
else similar to nvidia
pirlouy
24th October 2025, 12:57
I'm still surprised you take time to report problem to madshi. I though madVR was dead for years. Anyway madVR has always used too much ressources even with bilinear and other lowest settings, so I didn't use it for a long time (in fact the day I really invested in mpv). SmoothMotion is still a unique great feature though (mpdn is even more dead). I remember the day madshi talked about it, that is would be easy to do, and 2 weeks later he delivered. Good memories.
So madVR crashes or problem with error diffusion should not bother me. For deinterlacing, I can do without it (5060ti is 100 € more than 9060XT). As long as 23,976 Hz (24 and 25 also) is working fine, it should be OK.
huhn
24th October 2025, 13:16
in feb i killed one of his new scaler so i still talk with him.
the 5000 series is pretty much a general rip of but the bugs are still killing me.
lavfilter yadif it is for you i guess.
ryrynz
7th November 2025, 04:33
On 581.57 now.
Updated to 581.80. Found I have to perform a clean install or the audio dropouts come back, even restarted as well and it still happened. NVcleaninstall with default MSI interrupts and the audio timeout disabled which is what I always use. Just an FYI for anyone experiencing the same.
Klaus1189
4th December 2025, 17:54
Nvidia GeForce 591.44 both GRD and SD released
aarv
11th December 2025, 16:06
In new Nvidia driver 591.44, the doublerate deinterlace with hardware decoding seems to be malfunctioning, it only single frameate motion and picture is degraded to single field quality.
return to 581.94 is back to normal
Klaus1189
10th January 2026, 09:49
In new Nvidia driver 591.44, the doublerate deinterlace with hardware decoding seems to be malfunctioning, it only single frameate motion and picture is degraded to single field quality.
return to 581.94 is back to normal
What GPU? Both my RTX40 and RTX50 card did not have this issue with that driver version.
strumf666
25th January 2026, 14:18
Adrenalin 26.1.1 seems to works as expected.
huhn
25th January 2026, 16:30
you have to be a bit more precise.
levels are still broken in d3d9 deint is broken in d3d11 but works in d3d9.
the QC AMD...
clsid
25th January 2026, 16:49
d3d11 deint needs future frames. MPCVR has option for that.
huhn
25th January 2026, 16:52
which doesn't work.
just to be clear works on nvidia.
strumf666
30th January 2026, 20:26
you have to be a bit more precise.
levels are still broken in d3d9 deint is broken in d3d11 but works in d3d9.
the QC AMD...
As I said, "working" as in the previous version :P
I am mostly interested in getting a 10 bit output HDR/SDR, which kind of works. Happy to test anything specific if needed.
v0lt
8th February 2026, 11:21
RTX 5060. Nvidia driver 591.74. Windows 10 22H2.
DXVA2 Video Processor isn't working for the YUY2 format (black screen).
I disabled D3D11 in the MPC VR settings, and the other settings are default.
Can anyone verify this?
Other formats and modes work.
On the Intel UHD 750, everything works fine with YUY2.
Klaus1189
8th February 2026, 11:27
I have Win11 and 591.86 installed. Does that help? If so, I have the Spring samples. What file should I test? Only thing is to diable D3D11 in MPC-VR, right?
huhn
8th February 2026, 13:43
black screen with mpcVR.
"works" in partly in evr and madVR so it should work they use the same DXVA2?
test on a 4060.
v0lt
8th February 2026, 13:49
What file should I test? Only thing is to diable D3D11 in MPC-VR, right?
Any file. Disable hardware acceleration and disable all YUV formats except YUY2 for the software decoder.
black screen with mpcVR.
"works" in partly in evr and madVR so it should work they use the same DXVA2?
test on a 4060.
Thanks.
It breaks later, after DXVA2 VP has already processed and the converted frame is output using IDirect3DDevice9Ex.
And this only happens for YUY2.
huhn
8th February 2026, 14:46
btw. AYUV is broken and interpreted in the wrong order.
i just had to test it. AYUV issues with video renderer is just a classic.
v0lt
9th February 2026, 20:23
btw. AYUV is broken and interpreted in the wrong order.
Thanks.
Fixed conversion of 'AYUV' format using shaders for DX9 in MPC-VR 0.9.20.2501.
I created a test version that enabled AYUV for DXVA2 VP (https://disk.yandex.ru/d/Nvc6gzTx0ebkxw). And it looks like support for this format has been fixed in the new drivers.
huhn
9th February 2026, 22:53
well doesn't work for 4000 series.
the way it breaks is very very interesting.
win 11
951.59
4060.
i test the 9060 xt next.
edit: can't/doesn't work it is using shaders.
Klaus1189
26th February 2026, 20:10
"We have discovered a bug in the Game Ready and Studio 595.59 WHQL drivers and have removed the downloads temporarily while our team investigates. For users that have already installed this driver and are experiencing issues with fan control, please roll back to 591.86 WHQL."
https://www.nvidia.com/en-us/geforce/news/resident-evil-requiem-geforce-game-ready-driver/
Klaus1189
26th February 2026, 20:34
Here you can see what is going on:
https://www.nvidia.com/en-us/geforce/forums/game-ready-drivers/13/582871/geforce-grd-59559-feedback-thread-released-22626/
Schwartz
21st April 2026, 19:14
For anything RTX 3XXX series or below, I recommend sticking to driver version 566. Much smaller driver size (we're talking hundreds of MBs), and nothing new is being introduced for the older gens really.
DJ Bobo
20th June 2026, 14:52
I have the iGPU that comes with the Ryzen 4300G (Vega 6 I think), and it seems to suffer from the same issue with the black levels as the RX 5000 & 6000 mentionned in this thread.
I am running the Adrenalin driver, Version 23.11.1.
Can you guys recommend a driver version where I don't have to enable the 235 to 255 shader manually in MPC-HC?
PowerDVD 21 does not have such a setting, so it is (mostly) broken there.
The standard Windows 11 Player does not have this issue interestingly, and (always?) has the proper black levels.
EDIT: downgraded to 21.2.1; Now the black levels are fine everywhere. Earlier versions are fine in MPC-HC and PowerDVD, but not in the browser (i.e. Youtube). The HW AVC decoder seems to be broken though (stutters sometimes)
Same behaviour up to version 21.11.3
It breaks starting 21.12.1, which coincidentally introduces 10-bit HEVC hardware encoding -- what a bummer!
GTPVHD
15th August 2026, 09:34
https://www.intel.com/content/www/us/en/download/785597/intel-arc-graphics-windows.html
Intel Graphics Driver 32.0.101.8974 (WHQL Certified) released.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.