madVR - high quality video renderer (GPU assisted)

[Mordred]

you could change/add to the name FPS=60. that may work.
the frame rate can be stored at different parts of a file and a splitter/decoder has to choice one.
Ho-lee shit. I figured there was no chance this would work, but like magic, MadVR now reporting 60fps and it plays smooth as silk. File already had 60fps in the name, but clearly that wasn't the magic invocation. Thanks for the tip!

[huhn]

I gave it a try (windowed overlay) - sadly no dice, same issue happens. I have a 1070 and am using Win10.

can you share a screen of the OSD control+R?

[NDUS]

can you share a screen of the OSD control+R?


Here it is during the first 3ish seconds of the video being transferred or played on the 60hz monitor:
https://i.imgur.com/lfPmO82.png

After the 3ish seconds:
https://i.imgur.com/I0wlxT8.png

I discovered that if I change the monitor's orientation in Windows from Portrait (Flipped) to Landscape, it correctly takes the 59.997fps setting in MadVR and keeps it. Pic:
https://i.imgur.com/bhLD4LI.png

But because this monitor is to be used in portrait, I still have a problem.

Here is the MadVR display modes window with the monitor in Portrait mode:
https://i.imgur.com/NBDfvcS.png (has no standard modes)

And in Landscape mode:
https://i.imgur.com/F4ndIx7.png (has standard modes)

[huhn]

overlay rendering doesn't work with d3d11 it's part of d3d9.

[NDUS]

overlay rendering doesn't work with d3d11 it's part of d3d9.

Ah, thanks. I disabled Direct3D 11 presentation. Now when I play something on the 60hz monitor while it's in portrait mode, the image is either completely black, or severely "offset" - ie. a small corner of the video is visible in the bottom right of the video player frame. I can't take a screenshot of this 'coz of how overlay works.

When I use overlay mode (and D3D9) in Landscape mode, it works normally.

[huhn]

some progress at least.
there are more ways to avoid the windows DWM this was just the easiest i know.

you could add the issue with wrongly rendered overlay to the bug tracker.: http://bugs.madshi.net/my_view_page.php

but for your problem try next FSE(fullscreen exclusive) i would start with d3d9 and than i would try a compatibility trick to get the old FSE back. for windowed playback there is only overlay rendering which can workaround issue with the DWM.

the windows DWM issue can be very hard to fix so i prefered to just workaround them.
there are simple things it can't do like 2 different refreshrate at the same time for now.
but sometimes it is still working good enough so it doesn't get noticed so a windows update or new GPU driver can help or make it even worse.

[el Filou]

What GPU and driver is this? NVIDIA says that since 461.09 they (finally) support "Multi-Plane Overlays" that can help with these situations (OS can now give apps their own plane with their own refresh rate in windowed mode instead of having only one owned by the DWM) : https://nvidia.custhelp.com/app/answers/detail/a_id/5159/ but it's only supported in Turing and later.
My very old Radeon and my 1050 Ti don't support that (DxDiag shows it when you Save All Information to a .txt under "MPO MaxPlanes".

[NDUS]

some progress at least.
there are more ways to avoid the windows DWM this was just the easiest i know.

you could add the issue with wrongly rendered overlay to the bug tracker.: http://bugs.madshi.net/my_view_page.php

but for your problem try next FSE(fullscreen exclusive) i would start with d3d9 and than i would try a compatibility trick to get the old FSE back. for windowed playback there is only overlay rendering which can workaround issue with the DWM.

the windows DWM issue can be very hard to fix so i prefered to just workaround them.
there are simple things it can't do like 2 different refreshrate at the same time for now.
but sometimes it is still working good enough so it doesn't get noticed so a windows update or new GPU driver can help or make it even worse.

I tried your suggestions - the last one worked (setting "Disable Full Screen Optimization" in compatibility settings for MPC-HC.) Sucks that it's the only solution, but oh well. Thanks for the help, at least it's working.

I never anticipated these kinds of problems would exist with a two-monitor setup, lol. It seems like mixed refresh rate monitors is something that a Microsoft engineer would have tried at some point.

(...) but it's only supported in Turing and later.


Ah - I have a 1070. Yet another reason to join the rat race for a GPU!

[GCRaistlin]

How do I make the mouse cursor visible in fullscreen exclusive mode (MPC-HC)?

[huhn]

the FSE inmpc-hc is not the same FSE as in madVR just use that instead the cursor should show.
but that would only be the case with a really old mpc-hc version so the cursor should be there.

[Pastol]

Hi guys. do you know if madvr passthrough hdr works in beta insider program for windows? And which latest drivers are able to passthrough HDR ?
Sory for bad english. I hope it is understandable

[huhn]

should work with all latest driver.

[GCRaistlin]

the FSE inmpc-hc is not the same FSE as in madVR just use that instead the cursor should show.
but that would only be the case with a really old mpc-hc version so the cursor should be there.

The fact is that a time ago, "with the really old MPC-HC versions", the cursor was visible. But with new ones it is not. Is it expected?

[huhn]

i only remember a missing cursor in old MPC-HC FSE but madVR FSE should totally superseed it and a cursor should be present.

[GCRaistlin]

huhn
MPC-HC x64 1.9.10 (default settings, only video renderer is changed to madVR) + madVR 0.92.17 (default settings except [x] enable automatic fullscreen exclusive mode) = no cursor in fullscreen mode.

[huhn]

shouldn't be the case.
could be a custom cursor madVR can't handle up to buggy GPU driver or windows issues.

are you using intel by any chance?

[GCRaistlin]

No, AMD HD7850 + Crimson 17.7.1 (the latest one for it).

[el Filou]

So they're still updating the driver for Windows 7 and Windows 10, but not for Windows 8.x ? Bummer.

[ttnuagmada]

maybe someone here can help. Im using MPC-BE/Lav/MadVR/XYsubfilter

I've tried different versions of everything but MadVR, but, for the LIFE of me, I cannot keep it from displaying whatever the default subtitles are anytime i open a video. I have it set to load forced subtitles only in every single location I can find. I have tried uninstalling and reinstalling everything. I have tried different versions of BE/LAV/XY. I am about to blow my brains out.

[brazen1]

Try this in LAV Splitter:

Audio: eng

Subtitles: eng:eng|f;eng:off;*:eng

In Subtitles Selection Mode select Advanced.
Check Enable Automatic Forced Subtitles Stream.

In MPC-BE Subtitles menu select Forced Subtitles (auto)
OR
Do what I do and avoid PGS subs because they display in the video real estate and use .srt subs from subscene that display below the video in the black bar. Name the .srt same as the video and it should display automatically.
I know nothing about XYsubfilter or any possible conflicts because I have no use for it.

[VBB]

@ttnuagmada - Hey, nice to see you here. You should check our OLED thread (https://forum.doom9.org/showthread.php?t=176215), since you're the first one with a C1. We'd love to hear some feedback :)

[Asmodian]

I have it set to load forced subtitles only in every single location I can find.

It sounds like everything is working as intended, at least if you are watching MKV's. A subtitle track marked as "default" in a mkv counts as forced subtitles. :(

Perhaps it would be good practice to not set any subtitle tracks as default when muxing matroska files.

[Megalith]

Is http://madshi.net/madVRhdrMeasure131.zip the latest version? I updated to it but am still getting the annoying message about having to update my build.

[zveroboy]

http://madshi.net/madVRhdrMeasure131.zip



404 Not Found :angry:

[JaylumX]

404 Not Found :angry:

I do not know what has happened to v131 in the link but if you change it to v130, the link will work.

[SamuriHL]

Um, 131 doesn't exist. 130 is the latest beta build. And it will expire at the end of May.

[Perenista]

Not sure if you have been following, if not take a look at this: I explained in these two links a bug probably from madVR, or D3D11 related. I thought this was MPC-BE's fault.

https://forum.doom9.org/showthread.php?p=1940912#post1940912

https://forum.doom9.org/showthread.php?p=1941893#post1941893

I was told to disable D3D11, which I did, first for h.264, then for MPEG-2, and now for good.

And so far the problems I reported have not returned. In fact they returned only when I tried today for the first time a DVDRip, which uses a different codec: MPEG-2. They haven't been seen ever since D3D11 was enabled and playing h.264 videos.

Even so, I keep using madVR. And was using when the bug occured in MPC-BE.

[huhn]

it's not a bug madVR simple can't deint with d3d11 it was never implemented.

[Megalith]

My bad; madVRhdrMeasure130 is indeed the latest version. But it's already expired.

[SamuriHL]

No it hasn't.

Sent from my SM-G998U1 using Tapatalk

[interpolation]

I've been reading about resizable BAR.
https://www.guru3d.com/articles-pages/pcie-resizable-bar-performance-amd-and-nvidia-benchmarks,1.html
Does this have any effect on madvr performance now or in the future? I figure I would ask before flashing my motherboard and GPU BIOS to try and get my system compatible.

[huhn]

there is no harm in updating this feature (if you know what you are doing) but madVR currently does not support it. if it makes sense to support it is not know until someone tested it.

if you have a zen 2/3 CPU updating the bios is generally not a bad idea just be aware of the risk.

[Gser]

it's not a bug madVR simple can't deint with d3d11 it was never implemented.

I don't understand. Deinterlacing works fine for me in d3d11.

[huhn]

with d3d11 native >decode< as a source madVR can't deint at all.
d3d11 output has nothing todo with that.

[Asmodian]

I've been reading about resizable BAR.
https://www.guru3d.com/articles-pages/pcie-resizable-bar-performance-amd-and-nvidia-benchmarks,1.html
Does this have any effect on madvr performance now or in the future? I figure I would ask before flashing my motherboard and GPU BIOS to try and get my system compatible.

No, it does not. At least, not that I can measure.

It don't think it is relevant for madVR. How often does madVR need to read or write from chunks of memory larger than 256MB? How much performance increase would madVR get from being able to combine two transfers into one?

[Megalith]

No it hasn't.

Sent from my SM-G998U1 using Tapatalk

So why do I keep getting a message about needing to update madVR after installing version 130? Or do I have to do more than just overwrite the previous build?

[VBB]

The message is misleading, as there is no newer version at this time. Those who follow madshi's posts on AVS know that he's planning to implement a registration feature into future (beta) releases. We expect him to upload build 131 very soon, because 130 will expire at the end of May.

[SamuriHL]

You're seeing a WARNING that the build WILL expire. You will know when it's expired as it will cease to work at all at that time. That will happen at the end of May. In theory, madshi will release a new beta build before that happens.

[lazostat]

I open a HDR 2k movie and the brightness go high automatically. It resets when i make if full screen. Is this happening cause of madVR or wmpc? Cause when i open with bsplayer, nothing happens.

[Siso]

I'm wondering - do I need the new beta builds if I play only x264 content? Is 92.17 ok, or I should use beta 113 for example?

[el Filou]

The "betas" only have 'feature' changes that concern HDR. Build 113 also has small rendering performance changes where madshi said you could push the GPU utilization higher before it starts dropping frames, but as a caveat smooth motion crashes with it. More recent builds also had rendering changes that broke older GPU drivers/Windows versions, so can be risky too.
So if you never watch HDR and you're not running dangerously close to max GPU utilization, there is no need to use anything more recent than the 92.17 release.

[Siso]

Got it, too bad there isn't any new official build since 92.17.

[SamuriHL]

There is. You just need to spend 7 to 13 grand to get it. :D I'm hysterical. :)

[Asmodian]

I was really surprised the first monetization of madVR was as part of a hardware project.

It would be so cheap to release a "pro" version of madVR and hardware projects, especially those involving cutting edge compute, are expensive and hard to deliver (QA, warehouses, etc.). There would be some support costs, but the per-user costs would be so much lower with a pure software business model.

madVR seems so perfect for a pure software model too, given how many people have GPUs already. An Envy is a very niche market even compared to those with 3090s/Titans/6900XTs. :p

There is probably something I am missing.

[ryrynz]

There is probably something I am missing.

I doubt you missed it, the simple fact is it's not tied to hardware and thus can't be sold for 7-13K :)

I'm fine with things as they are more or less, the early 2010's were fun, one of the only things I'd love to have is better seeking and playback performance.
Maybe there will be some backporting eventually, I don't expect anything significant this year, some optimizations and fixes would be nice but I think Windows madVR is basically brickwalled.
Asking about a new stable build yields no answer, so that's that I guess.

[SamuriHL]

I wouldn't go that far. It's certainly taken a back seat to Envy because that's how they make their money. But madvr serves a purpose within the framework of that model. Which is to help improve the Envy. Right now the focus is on improving HDR, as it has been for the past couple years. And honestly, there have been some really nice improvements in that area in the past few builds. And more to come as the curve situation is figured out. PC development has stalled a bit at the moment as they were working on geometry shaping on the Envy (for the extreme, anyway). Now that it's implemented and the latest beta is about to expire, we'll see if focus is shifted back to the PC world for a bit. That is unknown. I would expect to see at least a new build with a new expiration at a minimum before the end of the month, but, honestly that's just a guess. I know it's not awesome to be considered the red-headed step-child of the video rendering world, but, we get fed once in a while. :D LOL

[ryrynz]

Beta test releases which expire aren't actual releases though :P So if you get some use out of the tonemapping all well and good I guess. But who's to say those features won't be disabled in a new test build relegating the test build to exactly what it's intended for, testing new features. Time will tell, it's been two years now.

[chros]

It's clear now that nothing major will happen, for wharever reason they are scared sh1tless that madvr is in the way of the sales of envy. And no reg system will change that.
The current situation tells you everything: they don't even care to compile a new build to get rid of the annoying message. That's basically like spit on the face of those testers...

[SamuriHL]

Well....you can always switch to one of the madvr competitors. :D LMAO

[nghiabeo20]

Well....you can always switch to one of the madvr competitors. :D LMAO

What is a worthy one? I switched to mpv since MPC development stopped, and never look back, though I understand madvr IQ is better.