View Full Version : madVR - high quality video renderer (GPU assisted)
LenniePaz
2nd January 2025, 02:18
I think it should be:
if (mk3d) "your profile with black bar detection"
else "3D"
The profile is named 3D.
YGPMOLE
2nd January 2025, 02:39
I finally got the PJ switching from SDR profile to HDR profile and back using Jvccontrol (https://www.avsforum.com/threads/jvccontrol-free-jvc-projector-ip-control-software.3018764/#replies) (a command line utility that sends a 2 digit remote control code to the PJ via network).
My HDR profile is SDR BT.2020 Power Gamma 2.4 calibrated (to use the madVR Tone Mapping)
report bt 2020 to display flag with the same profile.
Do I need to do that?
YGPMOLE
2nd January 2025, 02:43
[QUOTE=LenniePaz;2012403]I made a profile called 3D with black bar detection disabled
if (mk3d) "3D"
else "your profile with black bar detection enabled"
Sorry: I was editing my previous post and you were quoting it...
LenniePaz
2nd January 2025, 03:09
I created a profile called "enabled", and another called "disabled". I'm still not getting a green check mark.
Drybonz
2nd January 2025, 04:16
I've been getting a bright, white strobe light effect with some older, dvd era content when I have smooth motion on. If I turn smooth motion off, it immediately stops. Is this a known issue? Can anything be done about it? Thanks for the help.
huhn
2nd January 2025, 08:43
I finally got the PJ switching from SDR profile to HDR profile and back using Jvccontrol (https://www.avsforum.com/threads/jvccontrol-free-jvc-projector-ip-control-software.3018764/#replies) (a command line utility that sends a 2 digit remote control code to the PJ via network).
My HDR profile is SDR BT.2020 Power Gamma 2.4 calibrated (to use the madVR Tone Mapping)
Do I need to do that?
if your PJ works correctly report bt 2020 should set it into wide gamut mode so try it.
lvqcl
2nd January 2025, 15:12
LenniePaz
if (fileExt = "mk3d") "3d_profile" else "normal_profile"
GoldenSW
2nd January 2025, 21:46
Could you please help me confirm whether my settings in the "calibration" category are correct or not for SDR and HDR playback?
I will write what might be relevant in my setup.
Display: LG G4 OLED
GPU: RTX 2080
OS: Windows 11 24H2
Software: MPC-HC 2.3.9 (https://github.com/clsid2/mpc-hc/releases/tag/2.3.9), latest madVR test build and NVIDIA drivers
The goal is to send the unaltered HDR data to the display.
Naturally, I enabled "passthrough HDR to display" ✓ and "send HDR metadata to the display" ✓.
It's worth noting the G4 has excellent factory calibration so I do not want madVR to interfere with that in any way in SDR or HDR.
In "calibration" I selected:
HDR
- this display is already calibrated ✓
- disable GPU gamma ramps ✓
- the display is calibrated to the following primaries / gamut: BT.2020
- the display is calibrated to the following transfer function / gamma: pure power curve 2.20
- report BT.2020 to display (Nvidia only) ✓
This is for Windows HDR set to Off
SDR
- this display is already calibrated ✓
- disable GPU gamma ramps ✓
- the display is calibrated to the following primaries / gamut: BT.709
- the display is calibrated to the following transfer function / gamma: pure power curve 2.20
- report BT.2020 to display (Nvidia only) ✗
Thank you!
huhn
3rd January 2025, 05:00
madVR will not do anything by default in terms of calibration.
but it is technically impossible to send unaltered data...
It's worth noting the G4 has excellent factory calibration so I do not want madVR to interfere with that in any way in SDR or HDR.
you should never believe such stuff ever.
spectmajor
3rd January 2025, 09:49
@GoldenSW You don't have to use different profiles for HDR and SDR, the TV will recognize the source automatically. Here is my settings for G4 (see the attachment).
Turn every enhancement stuffs off on the TV and set the color space to auto detect. Don't use Windows HDR, that's correct.
If you are planning to use gamma 2.2, set the TV to 2.2 also, but for a dark viewing conditions 2.4 (BT.1886 on the TV) is the correct one.
You should also use madvr's dynamic tone mapping if you are planning to watch 4000 nits movies. LG's tone mapping algorithm only works up to about ~1000 nits. I mean the next step would be 2000 nits, and there the highlights are overexposed with LG's algorithm. It's easy to see on test videos.
(On Windows 11 you must use the latest beta version.)
Drybonz
4th January 2025, 06:18
I've been getting a bright, white strobe light effect with some older, dvd era content when I have smooth motion on. If I turn smooth motion off, it immediately stops. Is this a known issue? Can anything be done about it? Thanks for the help.
Looks like it is a problem with 25fps films. Flashing with smooth motion on. Any help is appreciated. Thanks.
Megalith
19th January 2025, 00:01
What is the latest version of madVR, and what is the official download link?
Schwartz
19th January 2025, 14:20
See the first post?
You can get the beta version from here: https://www.videohelp.com/software/madVR
shaolin95
19th January 2025, 16:34
Hi guys!
Can you please help me with the steps to accomplish an aspect ratio changing like this?
https://ibb.co/02XQWcx
I would like to have it done this way so that even at 16:9 it switches my JVC to Mode D anamorphic but I am having a hard time figuring this out from that screenshot I found.
Thanks!!
flossy_cake
20th January 2025, 03:05
Hi guys!
Can you please help me with the steps to accomplish an aspect ratio changing like this?
https://ibb.co/02XQWcx
I would like to have it done this way so that even at 16:9 it switches my JVC to Mode D anamorphic but I am having a hard time figuring this out from that screenshot I found.
Thanks!!
Have a look at the tips.txt file that comes with madVR
In my older version of tips.txt its saying srcAR contains the aspect ratio, so try changing AR to srcAR in your script
edit: OP says "AR, uncroppedAR, encodedAR" so I guess those ones should be tried first
Amuat
21st January 2025, 15:47
I was thinking of giving madVR a try after using MPCVR for quite some time now. Does the newest version cope with the latest Windows 11 and NVidia drivers? Seems like people are having quite a few problems.
Asmodian
22nd January 2025, 15:32
I was thinking of giving madVR a try after using MPCVR for quite some time now. Does the newest version cope with the latest Windows 11 and NVidia drivers? Seems like people are having quite a few problems.
You do need to use specific options for frames presented in advanced and the when and how shall the GPU be flushed.
1971camaroguy
23rd January 2025, 18:58
This is a longshot, I'm building a madVR machine as a passthrough from my zidoo player. I have CIH motorized screen masking using somfy shade motors with a 2:35 screen. I want to try and automate the masking based on video aspect ratio but not having any luck finding a way to do it. Has anyone done this in thier setup?
Megalith
26th January 2025, 09:51
I'm losing my mind trying to figure this out. Why does my TV randomly flash black (as if it's trying to change the refresh rate) when I'm watching a video in full-screen mode with madVR? This seems guaranteed to happen if I move the mouse in a way that brings up the user interface of my player (MPC-BE). And no, I don't have madVR configured to change into any special mode (e.g., exclusive) when I go full-screen with it.
The weird thing is how this doesn't happen when G-SYNC is on, but it will if I set MPC-BE to Fixed Refresh under NVIDIA CP. (For some reason, madVR activates G-SYNC unlike other renderers.)
I'm avoiding madVR for now and using the MPC Video Renderer...
huhn
26th January 2025, 11:32
true full screen exclusive forces a resync there no other way this can work only not using FSE is fixing that.
Megalith
26th January 2025, 18:43
Right, but I have FSE turned off.
huhn
26th January 2025, 18:54
in rare cases nvcontrol center -> adjust desktop colour settings content type reported to display.
but this is super rare.
a player can in theory also tell madVR to use FSE while FSE is disabled again very unlikely to be the case 99% of all user don't even know this option exists and that good this way.
madVR is treated as a game by the GPU driver not it's choice.
clsid
26th January 2025, 19:12
Another possibility is that Windows is outputting Dolby Vision to your TV when running in desktop mode. Then it switches to HDR10 when you go fullscreen with madvr. Showing player seekbar triggers desktop mode again.
But usually the TV OSD shows such mode switches.
647830
26th January 2025, 20:21
I have important frame drops and need advice from experts here.
My set-up is the following:
Windows 10 22H2 build 19045.5247
GPU NVidia GTX1080 (385.28), CPU i7-7700 3.6GHz, JVC DLA-RS46
MPC-BE 1.8.2, LAV Filter 0.78, MadVR 0.92.17, 113 beta
I am playing a 2160p 24Hz UHD with Dolby Atmos 7.1 sound track.
During the first 25 min or so all works well, my rendering timings look ok at c. 30ms.
https://i.postimg.cc/wBynrf7W/Good.png
Then suddenly the clock deviation increases, decoder queue changes, I have a lot of frame repeats, sound is distorded and clock deviation deviates a lot:
https://i.postimg.cc/KzY3FThs/not-working.jpg
After a few minutes, it gets back to "normal".
I am wondering what to do, I have tried several things without success. Can it be that the filters applied are too demanding for my GPU? or should I consider looking at other things please?
Any help much appreciated and many thanks for your advice.
clsid
26th January 2025, 20:58
Win10 Settings > System > Display > Graphics Settings > disable on "Hardware-Accelerated GPU Scheduling"
If that does not help, then lower CPU queue size in madvr to 8.
If that does not help, then change the hardware decoder from D3D11 native to D3D11 copyback or DXVA2 copyback.
If that does not help, then set NVIDIA to high performance power mode and complain to NVIDIA.
647830
26th January 2025, 21:46
Win10 Settings > System > Display > Graphics Settings > disable on "Hardware-Accelerated GPU Scheduling"
If that does not help, then lower CPU queue size in madvr to 8.
If that does not help, then change the hardware decoder from D3D11 native to D3D11 copyback or DXVA2 copyback.
If that does not help, then set NVIDIA to high performance power mode and complain to NVIDIA.
Thank you clsid.
For the first one, I don't have this option in my win10 (maybe due to the NV driver I have which is old but supposed to work for HTPC?). I did lower the CPU queue to 8, not solving the issue. DXVA2 copyback no change either. My NV was already set at "high performance power mode".
I can complain to NV, but not sure it will move the needle. Any other idea please?
and, last question, is there a graphic card / GPU on earth which works well for HTPC with not issue, good sync to avoid CustomRes, etc. ??
Best
mclingo
27th January 2025, 01:42
For the last year or less I've been getting playback glitches, just aclittle stutter here, just enough to annoy me though. I've tried everything I even built a new PC and it continued so I'm pretty sure it's madvr and not my hardware. The thing is, it showed none of these Issues in madVR itself. I've been experimenting with other players and they've all had their own problems however I've just tried the latest kodi 21, I've not tried the stock kodi it for years and I'm pleasantly surprised. It's done HDR for a while but the tone mapping settings do a fairly decent job of Brightening up the picture in the same way madvr has done for me... Main thing is no glitching, Just perfectly smooth playback with all file types, resolutions and refresh rates.
The sort of stutters as I'm talking about are those that you'll only see very rarely in a panning shot and even then it's less than a second but it's just enough to take me out of the experience, there's a good chance that most people won't see these and just think there are no issues with madvr at all but I think it's been broken for a while with Windows 11. I was tempted to go back to Windows 10 but with it finishing support soon I just still want to have that concern about security updates and stuff. I'll be keeping madvr for 3D mvc play back, but other than that it's dead to me. I'll probably try again in 6 months or so to see if anything has changed or if version 1.0 is ever finally released. Thanks for all the help I've had on here, see you all in a bit.
Nemo1985
27th January 2025, 11:12
Hello, I'm impressed that noone speak about the amd driver issues with madvr.
The latest driver I could use without issues were the 24.3, I updated the driver back in october (and kept doing so) still nowadays ED2 as dither method hangs up the application for half of a minute with mpc-hc.
I also tried the bet version of madvr but with no changes.
How is it possible that noone with radeon 6xxx video card has this issue?
Even changing the dither method to something else doesn't solve the problem, instead of hanging when a video is loaded it hangs after it's played.
Reference: https://github.com/clsid2/mpc-hc/issues/3223
I wonder, amd is notorious for their bugged video driver, madvr is not updated in ages, is there any solution to solve the issue?
mclingo
27th January 2025, 12:05
sounds like an issue specific to your setup, i've had AMD cards for 15+ years and never had that issue, didnt have it on my last card 5700 and I dont have it on my 7800xt
Try asking on here, the only issue I am aware of with 5000/6000 cards is the following which was fixed with 7000 series.
https://forum.doom9.org/showthread.php?t=176013
Known limitations of Radeon RX 5000 and 6000 GPUs (other generations like RX 7000 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.
You can check this issue yourself: Download this short MBAFF sample file
The Hardware Deinterlacer should be aware that the characters above "WWW.D88.COM" are
progressive and should not be deinterlaced, otherwise you will see flickering like in this picture
See here for more details
• 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.
This issue can be best seen on displays which want full range 0-255, like TVs in PC Mode (PC
mode for full 4:4:4/RGB support, so you do not use color subsampling like 4:2:2 or 4:2:0)
Also overriding the range for test purposes in MPC-BE (video tab -> Output range) does not
take effect.
Dear AMD, if any of your driver programmers read this: Please fix this fundamental video bugs.
These are present since RX 5000 series launch.
Nemo1985
27th January 2025, 12:39
sounds like an issue specific to your setup, i've had AMD cards for 15+ years and never had that issue, didnt have it on my last card 5700 and I dont have it on my 7800xt
Try asking on here, the only issue I am aware of with 5000/6000 cards is the following which was fixed with 7000 series.
https://forum.doom9.org/showthread.php?t=176013
Known limitations of Radeon RX 5000 and 6000 GPUs (other generations like RX 7000 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.
You can check this issue yourself: Download this short MBAFF sample file
The Hardware Deinterlacer should be aware that the characters above "WWW.D88.COM" are
progressive and should not be deinterlaced, otherwise you will see flickering like in this picture
See here for more details
• 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.
This issue can be best seen on displays which want full range 0-255, like TVs in PC Mode (PC
mode for full 4:4:4/RGB support, so you do not use color subsampling like 4:2:2 or 4:2:0)
Also overriding the range for test purposes in MPC-BE (video tab -> Output range) does not
take effect.
Dear AMD, if any of your driver programmers read this: Please fix this fundamental video bugs.
These are present since RX 5000 series launch.
Thank you for the answer, I need to fully disagree, as stated on my previous post I didn't have the issue with older drivers, I do with current (let's say after april 2024), clearly is a driver issue as most of the stuff you pasted up there are drivers issues. I'm glad you didn't have a single issue in 15 years of AMD, I'm sure it's a record, still statistically a single example is not significant, I can claim that I had issues and describe what they were. Also it's not a "issue of my specific setup" since on the github link there is at least another user with the same issue with the same series of video card and again change the dither method solve this issue but it creates another one. Probably the series 7 is not affected, well done amd for not introducing bugs on the "newest" video cards.
huhn
27th January 2025, 13:06
I have important frame drops and need advice from experts here.
My set-up is the following:
Windows 10 22H2 build 19045.5247
GPU NVidia GTX1080 (385.28), CPU i7-7700 3.6GHz, JVC DLA-RS46
MPC-BE 1.8.2, LAV Filter 0.78, MadVR 0.92.17, 113 beta
I am playing a 2160p 24Hz UHD with Dolby Atmos 7.1 sound track.
During the first 25 min or so all works well, my rendering timings look ok at c. 30ms.
https://i.postimg.cc/wBynrf7W/Good.png
Then suddenly the clock deviation increases, decoder queue changes, I have a lot of frame repeats, sound is distorded and clock deviation deviates a lot:
https://i.postimg.cc/KzY3FThs/not-working.jpg
After a few minutes, it gets back to "normal".
I am wondering what to do, I have tried several things without success. Can it be that the filters applied are too demanding for my GPU? or should I consider looking at other things please?
Any help much appreciated and many thanks for your advice.
your decoder queue or subtitle queue is the issue. check your CPU load or try a risky decoder like d3d11 native.
if it is the subtitles starving the decoder try the same part without subtitles.
Hello, I'm impressed that noone speak about the amd driver issues with madvr.
The latest driver I could use without issues were the 24.3, I updated the driver back in october (and kept doing so) still nowadays ED2 as dither method hangs up the application for half of a minute with mpc-hc.
I also tried the bet version of madvr but with no changes.
How is it possible that noone with radeon 6xxx video card has this issue?
Even changing the dither method to something else doesn't solve the problem, instead of hanging when a video is loaded it hangs after it's played.
Reference: https://github.com/clsid2/mpc-hc/issues/3223
I wonder, amd is notorious for their bugged video driver, madvr is not updated in ages, is there any solution to solve the issue?
the solution is not using ED2.
AMD had a copyback bug with openCL for the entire life time of the products series this is nothing in comparison.
hell nvidia had openCL bugs for many many years making it run so slow it was utterly unusable.
mclingo
27th January 2025, 14:06
Thank you for the answer, I need to fully disagree, as stated on my previous post I didn't have the issue with older drivers, I do with current (let's say after april 2024), clearly is a driver issue as most of the stuff you pasted up there are drivers issues. I'm glad you didn't have a single issue in 15 years of AMD, I'm sure it's a record, still statistically a single example is not significant, I can claim that I had issues and describe what they were. Also it's not a "issue of my specific setup" since on the github link there is at least another user with the same issue with the same series of video card and again change the dither method solve this issue but it creates another one. Probably the series 7 is not affected, well done amd for not introducing bugs on the "newest" video cards.
I hear you, i've had so many issues i've wanted to blame on drivers only to find its a local issue, i've had some really odd shit going on where I had to do a full system restore to fix a problem with MADVR as a full AMD driver wipe using DDU didnt work, that was after a BSOD using MADVR.
i've had it ED2 turn on for years with no issues, assuming you are using D3D11 and not DXVA copy back / native in lav?
That being said i've scrapped MADVR for 2d playback now as I keep getting stutters which I cant fix, only use it for 3d MVC now. (also did it with an NVIDIA card I bunged in to test)
Seegs108
27th January 2025, 16:37
Can someone explain what happens within madVR when you choose to output in full 0-255 when playing back limited 16-235 video, as most consumer video is encoded for? Does madVR scale the content so 16 values are now 0 on the output and 235 is now 255 and the content between is scaled to the new dynamic range of the output? Playing back a Pluge test pattern to set Brightness and Contrast show video correctly clips and crushes at 16 and 235 through madVR even when outputting Full 0-255 and I would just like to know how madVR manages to make this happen.
huhn
27th January 2025, 16:45
ycbcr video are 16-235 16-240 16-240 and it converting that to RGB 0-255.
literally part of the ycbcr -> rgb spec.
Seegs108
27th January 2025, 16:58
ycbcr video are 16-235 16-240 16-240 and it converting that to RGB 0-255.
literally part of the ycbcr -> rgb spec.
Yes, but you can output in RBG 16-235 if you wanted to as well. I'm asking how it converts 16-235 content to 0-255 specifically. The former sounds more straight forward than the latter. Can you link to the standard/spec on how this conversion is done?
huhn
27th January 2025, 17:08
it can output any level you want.
the shader that does this are not shared.
will be in the ball park of this:
sampler s0 : register(s0);
#define const_1 ( 16.0 / 255.0)
#define const_2 (255.0 / 219.0)
float4 main(float2 tex : TEXCOORD0) : COLOR
{
// original pixel
float4 c0 = tex2D(s0, tex);
return ((c0 - const_1) * const_2);
}
limited range RGB and limited range YCbCr have nothing to do with each other. there are direct conversation to both and even if you use limited you can just use a shader likes how atop to get full range RGB. the produced error if 16 or 32 bit float is used for using the 2 step over the direct way is neglectable. madVR always does limited range first. it even converts full range RGB to limited it's just how it works.
https://www.compression.ru/download/articles/color_space/ch03.pdf
647830
28th January 2025, 14:34
your decoder queue or subtitle queue is the issue. check your CPU load or try a risky decoder like d3d11 native.
if it is the subtitles starving the decoder try the same part without subtitles.
.
Thank you huhn, i have disables subtitles, tried another decoder but without success. It is indeed a decoder queue issue apparently but don't understand why. On some movies, no issue at all, on others it is awful. looks like it is happening on 4K 24Hz movies with Dolby Atmos only.
Any other recommendation? If not I will reset my PC and restart from scratch ... but have no backup.
huhn
28th January 2025, 15:10
what hardware are you using?
GCRaistlin
28th January 2025, 16:06
Epson EH-TW9200, Radeon HD7850, Crimson 17.7.1, Win81x64, MPC-HC and MPC-HC64
In exclusive mode, madVR recognizes 24 Hz screen refresh rate as 23 Hz. As a result, when I play a 24p video I get one dropped frame every 40 seconds instead of every 14 minutes (at least that's what debug OSD says). 50 Hz mode and 60 Hz mode are recognized just fine. What can be done about that?
647830
29th January 2025, 08:34
what hardware are you using?
Windows 10 22H2 build 19045.5247
GPU NVidia GTX1080 (385.28), CPU i7-7700 3.6GHz, JVC DLA-RS46 (X35)
huhn
29th January 2025, 10:43
is the video in question AV1 encoded?
or are you using CUVID?
647830
29th January 2025, 10:57
is the video in question AV1 encoded?
or are you using CUVID?
MediaInfo says:
Video
ID : 4113 (0x1011)
Menu ID : 1 (0x1)
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
Codec ID : 36
Duration : 1 h 39 min
Bit rate : 94.2 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate : 24.000 FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.473
Stream size : 65.7 GiB (94%)
Writing library : ATEME Titan File 3.9.4 (4.9.4.12)
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709
I am not using CUVID.
GCRaistlin
29th January 2025, 23:49
Epson EH-TW9200, Radeon HD7850, Crimson 17.7.1, Win81x64, MPC-HC and MPC-HC64
In exclusive mode, madVR recognizes 24 Hz screen refresh rate as 23 Hz. As a result, when I play a 24p video I get one dropped frame every 40 seconds instead of every 14 minutes (at least that's what debug OSD says). 50 Hz mode and 60 Hz mode are recognized just fine. What can be done about that?
The solution is [x] hack Direct3D to make 24.000 Hz and 60.000 Hz work
older Windows 10 versions, and also Windows 8.1, like to switch to 23.976 Hz and 59.940 Hz in FSE mode, even if madVR asks for 24.000 Hz and 60.000 Hz.
huhn
30th January 2025, 04:51
MediaInfo says:
Video
ID : 4113 (0x1011)
Menu ID : 1 (0x1)
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
Codec ID : 36
Duration : 1 h 39 min
Bit rate : 94.2 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate : 24.000 FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.473
Stream size : 65.7 GiB (94%)
Writing library : ATEME Titan File 3.9.4 (4.9.4.12)
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709
I am not using CUVID.
you are using D3D11 native so it is not a PCIe bandwidth issue.
the file is HEVC 95 mbit that's nothing for a 1000 series hardware decoder.
the hags issues should result in glitches and maybe drops not repeats and audio distortion and is an win 11 issue.
maybe try your luck with the mpc-be internal decoder instead of lavfilter.
there is also reports of mpc-be not working with madVR but that's also on win 11.
this looks more like a decoder issue then a madVR one.
mclingo
30th January 2025, 12:26
The solution is [x] hack Direct3D to make 24.000 Hz and 60.000 Hz work
I get this issue when i'm using wireless headphones, is there anything wireless or bluetooth in your audio stack, although mine doesnt settle to normal after a while so it wont be that i'm guessing.
clsid
30th January 2025, 15:33
Win11 24H2 had some audio bugs in update from earlier this month. Latest update supposedly fixes (some of) them.
The audio hardware provides the reference clock during playback. So issues with unstable clock deviation are indeed likely coming from audio stack. Such as a buggy driver. But there are also power saving options in Windows that can for example temporarily turn off USB/Bluetooth audio device during inactivity, causing delays when receiving sound again.
In case of audio issues always check DPC Latency (https://resplendence.com/latencymon).
clsid
30th January 2025, 15:34
Disabling Hardware-Accelerated GPU Scheduling has worked for several people to fix the sudden presentation glitch stuttering problems on Win11 24H2.
Bedouille69
30th January 2025, 16:50
Disabling Hardware-Accelerated GPU Scheduling has worked for several people to fix the sudden presentation glitch stuttering problems on Win11 24H2.
Yes it's the only fix and it requires a reboot to be effective.
647830
31st January 2025, 08:14
Thank you for all your replies. However I have win10 1806 (Oct '18) precisely to try avoiding such issues. So the problem is likely elsewhere. Maybe an HDCP issue? My PC is connected to my AVR through HDMI so it is GTX1080 (2.2 compliant) connected to my AVR (also 2.2 compliant). My NVCP shows a supported HDCP link, but in windows settings / sound, under my AVR it says HDCP not supported. Strange. I will also investigate latency as suggested. Looks like it is a sound issue through HDMI although i am not sure.
huhn
31st January 2025, 12:40
it's clearly a decoding issue if there would be a sound issue the queue wouldn't drop.
just use a NULL renderer to test.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.