madVR - high quality video renderer (GPU assisted)

[Megalith]

Right, but I have FSE turned off.

[huhn]

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]

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]

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.


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:



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]

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]

Originally Posted by clsid

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]

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]

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]

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]

Originally Posted by mclingo

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]

Originally Posted by 647830

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.


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:



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.

Originally Posted by Nemo1985

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]

Originally Posted by Nemo1985

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]

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]

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]

Originally Posted by huhn

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]

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/...space/ch03.pdf

[647830]

Originally Posted by huhn

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]

what hardware are you using?

[GCRaistlin]

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]

Originally Posted by huhn

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)