madVR - high quality video renderer (GPU assisted)

[sneaker_ger]

Windows 7 error message:
https://abload.de/img/madvr_092_crashx8upp.png
Playback works until you hit "ok" - then player closes.

madvr log (https://www.sendspace.com/file/9h9a4w)

LAV Video is set to software decoding.

[Raimu]

Huh. MPC-HC blows up on the start of a movie file on my PC too. I reset madvr and MPC-HC (installed 1.7.13, reset settings and reconfigured to use madvr), but it doesn't help.

I'm using Win10 15063 and a Nvidia 770GTX (driver 385.12)

[kostik]

Have a crash also :( win10 Nvidia 940M , tried dxva2 copy-back&&cuvid , tried running on intel graphics 520 , crashes on start. Once I point the mouse on the movie frame to double click to go to full screen, it crashes.
It crashes right away when the mouse is on the frame of the video before I clicking anything

[madshi]

I can reproduce the "two identical display modes" problem. But no crashes here. :(

Edit: Does both the 64bit and 32bit version of the media player crash for you guys?

[sneaker_ger]

Both 32 bit and 64 bit crash.

[madshi]

Ok, while the crash window is open, can you try to press Ctrl+Alt+Shift+Pause/Break? Does that get you a freeze report text file on your desktop?

(Probably not, but worth a try.)

[MS-DOS]

Nope, didn't generate one.

[sneaker_ger]

No freeze report.

It's a bit weird.
With 1.7.13 stable: "actual" crash with some Windows message.
With 1.7.13.89: the error message (see screenshot) appears but playback works normally in background. Once you click "ok" player closes.

[Neo-XP]

madVR v0.92.0 crashes MPC-BE when opening any video file.

I tried to reinstall it completely (uninstall, remove all files and then install again), but it does not help. Even after restoring default settings with the .bat afterwards.

[kostik]

I can reproduce the "two identical display modes" problem. But no crashes here. :(

Edit: Does both the 64bit and 32bit version of the media player crash for you guys?

Yes. I tried 32bit ,,, same issue

[v0lt]

madshi
Thanks for the new version, but I'm getting a crash of MPC-BE x64 on Windows 7 and 8.1.

For Win7:
http://jpegshare.net/thumbs/3e/31/3e311390f3df8616ef15960a547adaa6.jpg (http://jpegshare.net/3e/31/3e311390f3df8616ef15960a547adaa6.png.html)

[ABDO]

thanks is not enough for your great and hard work in madvr, from my heart thank you @madshi for your time and effort you spent to make this amazing work Available for us.:thanks:

[kostik]

Ok, while the crash window is open, can you try to press Ctrl+Alt+Shift+Pause/Break? Does that get you a freeze report text file on your desktop?

(Probably not, but worth a try.)

This is what I get in Event Viewer:

Faulting application name: mpc-be64.exe, version: 1.5.1.2822, time stamp: 0x599510c4
Faulting module name: madVR64.ax, version: 0.92.0.0, time stamp: 0x5995c42e
Exception code: 0xc0000005
Fault offset: 0x00000000000101ce
Faulting process id: 0x3ce4
Faulting application start time: 0x01d3177ffe9d4fb0
Faulting application path: C:\Program Files\MPC-BE x64\mpc-be64.exe
Faulting module path: C:\Madvr\madVR64.ax
Report Id: d068031a-12ce-4701-8148-13ded3606cfd
Faulting package full name:
Faulting package-relative application ID:


MPC-HC Debug:
Stack:

madvr64+0x101ce
madvr64+0x12674
madvr64+0x54244
mpc_hc64+0xb2c0d
mpc_hc64+0xb305e
mpc_hc64+0x5b3794
mpc_hc64+0x5b571a
mpc_hc64+0x5ae93d
mpc_hc64+0x5af434
user32!UserCallWinProcCheckWow+0x292
user32!DispatchMessageWorker+0x19f
mpc_hc64+0x5caea2
mpc_hc64+0x5cb7ff
mpc_hc64+0x7c4a5e
mpc_hc64+0x76ab63
kernel32!BaseThreadInitThunk+0x14
ntdll!RtlUserThreadStart+0x21

[madshi]

madVR v0.92.1 released

http://madshi.net/madVR.zip

* fixed: depending on madVR settings, v0.92.0 crashed right at initialization
* fixed: "display modes" were listed twice in the settings dialog
Was finally able to reproduce the crash after restoring default settings.

(Note to devs: I know some of you are waiting for me to add dev features for you. Will do that soon now, just wanted to get v0.92.x out the door, first.)

[kostik]

madVR v0.92.1 released

http://madshi.net/madVR.zip

* fixed: depending on madVR settings, v0.92.0 crashed right at initialization
* fixed: "display modes" were listed twice in the settings dialog
Was finally able to reproduce the crash after restoring default settings.

(Note to devs: I know some of you are waiting for me to add dev features for you. Will do that soon now, just wanted to get v0.92.x out the door, first.)

Works! Thanks! Great work! The Best!

[MS-DOS]

Thanks, madshi, no more crashes.
Can confirm D3D11 DXVA hardware decoding not working on Win 7, black screen and playback doesn't start. Oh well :)

[dvd1]

The GT 730 is rather old and only has DDR3 memory. It seems like a fairly slow GPU, by today's standards. madVR might still run smoothly, maybe you need to tune down some settings a bit, but it depends a lot on which movie resolution and frame rate we're talking about, whether you need upscaling o
576i 50 frame rate to 1080p 50 frame rate, 720p to 1080p 24 or50 frame rate 1080p to 1080p 24 or 50 frame rate on tv FULLHD 42p
What madVR filters do you recommend?
thank you

[clsid]

D3D11 hardware decoding is not compatible with Windows 7 yet because it uses some features that are only available in 8.1+. It will fall back to software decoding. Nevcairiel has said that he will attempt to make it work on 7 later.

The black screen with latest madvr is a bug in lav/madvr.

[madshi]

576i 50 frame rate to 1080p 50 frame rate, 720p to 1080p 24 or50 frame rate 1080p to 1080p 24 or 50 frame rate on tv FULLHD 42p
What madVR filters do you recommend?
That's really hard to say. You'll need to do some experimenting to find filter combinations that are fast enough with your GPU. I'd recommend setting chroma upscaling to Bilinear, because luma/image upscaling is so much more important and you need every bit of GPU power for that. For luma/image upscaling you can try if "NGU Anti-Aliasing" works at "low" quality level 720p24 content. I kinda doubt it, but you can try. If not, try maybe Lanczos3 AR instead.

In order to get the best possible quality, you may have to use different settings for different situations. E.g. 576i50 -> 1080p50 is quite demanding because the GPU has to render 50 frames per second. 720p24 -> 1080p24 is *much* easier. So for 720p24 upscaling you can use higher quality scaling algorithms. You can use profiles to setup different algorithms for different situations/video files.

The black screen with latest madvr is a bug in lav/madvr.
Well, we've intentionally not blocked anything, just in case we get lucky and it works in Windows 7. I highly doubt it will work. If we find out that it won't work, then we'll simply block the feature in Windows 7 to fix the black screen.

[Manni]

Anyway, with v0.92.0 you can try actually measuring and optimizing the timings even further. That should easily get you into the "one frame drop/repeat every 1.x days" range, at least. Tutorial to follow soon.


Looking forward to testing, but I can't see the custom res tab in display modes (0.92.1). Is it there in this build?


Have you tried unchecking the "show native res modes, only" checkbox? ;)

I completely missed that, of course that solves the issue, thanks :)

[madshi]

Looking forward to testing, but I can't see the custom res tab in display modes (0.92.1). Is it there in this build?
It should be there. It requires you to open the settings dialog on the same PC the monitor is connected to. You can't do this remotely. Furthermore, the monitor must be "active", so basically the OS must show it in the OS display configuration dialog. Is that the case?

[Manni]

It should be there. It requires you to open the settings dialog on the same PC the monitor is connected to. You can't do this remotely. Furthermore, the monitor must be "active", so basically the OS must show it in the OS display configuration dialog. Is that the case?

Thanks, that's probably the issue, I'm using TeamViewer to the HTPC at the moment (not switching the PJ too early/often). I'm sure it will appear when the PJ is active later tonight, otherwise I'll let you know.

[v0lt]

@madshi
Thanks.
I got a strange picture in D3D11 mode for Sony_4K_HDR_Camp.mp4. Other HDR files are displayed normally.
http://jpegshare.net/thumbs/f7/96/f796513181e541d68341e160484e7348.jpg (http://jpegshare.net/f7/96/f796513181e541d68341e160484e7348.jpg.html)

[madshi]

Is that with LAV or with MPC-BE decoders? It seems that the decoder is reporting weird HDR metadata to madVR. E.g. max luminance is reported as "1 nits".

[Siso]

@madshi, the sample is reuploaded again :) http://www101.zippyshare.com/v/oe86z81X/file.html

[v0lt]

I used LAV Video Decoder to test DXVA11.
Win8.1 is not my main system, so now I can not test how it will be on the MPC-BE decoder.

[Sunset1982]

Display modes is still shown twice here with 0.92.1 and custom modes tab is only there for 1 sec and then its gone....

did a default settings reset and a comlete new installation of the new madvr version

[FDisk80]

The Edit Timing for custom modes window is not set to be always on top. So it is opening behind the video when in full screen.

Other than that, AMAZING stuff! :)

[Dorohedoro]

Wow Madshi thank you so much for answering all those questions!! And of course I'm going to purchase/donate when the time comes, you gave us a top notch product and in my case a lot of hours of quality movie viewing.
Thank you so much!

[Asmodian]

Thanks for this update madshi, very impressive changes!

I really like the new DX11 DXVA decoding, not for myself but for those with lower end systems and mobile. It is great to avoid most of the qualifications around DXVA2 native decoding.

:thanks:

Is that with LAV or with MPC-BE decoders? It seems that the decoder is reporting weird HDR metadata to madVR. E.g. max luminance is reported as "1 nits".

Yes, this file was found to have broken metadata when you first added HDR support. A max nits of 1 is not correct. ;)

[FDisk80]

Is the Pixel Clock not saving the changes?
I'm trying to set vertical back porch to 35 and pixel clock to 74.11 for a perfect 23.976hz result but the pixel clock is dropping back to 74.10 after applying it.
Only vertical back porch is applied but that results in 23.972hz.

[Manni]

It should be there. It requires you to open the settings dialog on the same PC the monitor is connected to. You can't do this remotely. Furthermore, the monitor must be "active", so basically the OS must show it in the OS display configuration dialog. Is that the case?

Thanks, that's probably the issue, I'm using TeamViewer to the HTPC at the moment (not switching the PJ too early/often). I'm sure it will appear when the PJ is active later tonight, otherwise I'll let you know.

I'm on the JVC now, with the JVC as the active display, and still no custom res tab in the display modes screen (set-up in my sig below, although I also have a Vertex between the AVR and the JVC, which shouldn't make any difference). It briefly appears for a fraction of a second, then it goes away (I missed it initially).

EDIT: just to clarify, nVidia sees my display as Denon AVR, MadVR sees the Denon AVR, I tell it i's an AVR, and then I configure the JVC (Digital Projector) as being attached to the Denon. The OS only sees a Generic PNP Monitor, although for Audio it sees the Denon AVR, which is my HDMI Audio Out (Default). Maybe I'm having the issue because the display isn't connected directly to the GPU?

[Neo-XP]

Noob questions :

1. What is the advantage of using perfect 23.976hz instead of 60hz with smooth motion ?
1a. The panning shots seem more fluid with the smooth motion solution, is that correct ?

2. Does it change something to use ReClock or not with smooth motion enabled ?

3. Is this new "custom modes" feature of madVR created to replace ReClock ?
3a. As I see it, they work very differently. Can they work together ?

4. I guess if I use smooth motion, I don't need to use the new "custom modes" feature at all ?

[x7007]

What happens when there are Repeated Frames ? I have steady repeated frames of 30 with MP4 file WEBRIP , normal movies MKV 1080P are working properly.

[huhn]

1. with 23p you don't have to use smoothmotion and at least i can see the difference between smoothmotion and true 23p but not everyone can and they have the same smoothness.
the advantage of smoothmotion is that you are never repeating or dropping frames for sync.

1a. if this is the case your TV maybe unable to do 23p properly this a a very common issue with TV even more expensive one have this problem commonly. some TV lose this ability in PC mode like mine where smoothmotion is now clearly better than 23p.

2. you can do that but you should not use both at the same time. smoothmootion on it's own is all you need no need to touch the audio too.

3. "yes".
3a. yes they can but a good custom resolution makes reclock obsolete.

4. yes.

[huhn]

x7007 OSD plz.

my blind guess is the file reports 60 FPS but only has 30 FPS.

[x7007]

x7007 OSD plz.

my blind guess is the file reports 60 FPS but only has 30 FPS.

If the movie is 30 , what can I do to fix it ? because it clearly sees it as 60 . you are correct

Thank you madshi ! for the Full Windowed D3D11 10 Bit mode !! I so long waited for it, hate full screen exclusive so annoying when using TV and the annoying black screen switching like 1-2 seconds or when you are 60 Hz it's like 2-3 seconds.

Also HDR works great now, I always had Black Screen when going to Full windowed mode in HDR, now it works perfect , without the need to enable Windows 10 1703 HDR mode .

http://i.imgur.com/Og7lGyH.jpg

[huhn]

my guess is maybe correct but i can't say it for sure without a sample.


one dropped frame every 15 sec wow.

[imhh11]

thank you so much for enabling 10 bit fullscreen windowed. Now HDR works perfectly !!
I'll donate for sure once the version 1.0 is out .

[Manni]

Further feedback on 0.92.1 (set-up in sig below):

- Using the latest 385.28, there is an improvement re HDR in 0.92.1 as I can now get the HDR Metadata (MadVR set to pass through / send metadata) but the display doesn't switch to HDR automatically. Not a problem for me as I disable the JVC mode and switch manually to a custom mode, but I thought I'd try and let you know.
- The new 10bit path without FSE works great. That's really nice as on the JVCs FSE led to a few seconds black screen every time you used the player interface, for example, to select audio/subtitle track. Hopefully it will be possible to do without FSE for 3D too at some point.
- I enabled non-native resolutions in the custom res experimental tool (as the custom res tab doesn't work yet for me in MadVR) and created a custom res with the 1080p23 EDID. Unfortunately, that didn't seem to translate into any improvement for 1080p23FP (still 1 frame drop/repeat every 3mn or so). Does 1080p23(FP) need a custom res distinct from 1080p23(2D)? I couldn't see such in the tool. Also, while there is no gain, when I return to MyMovies after playback of a 3D film there is a weird corruption on the screen. The screen is still in 1080p23FP, the MadVR OSD flickers on the left (even if MPC-BE isn't running anymore) and the bottom third of the screen flickers on the top third. Is there a way to reset If I exit MyMovies, the display returns to 4K23 and all is fine again. None of this happens without a 1080p23 custom res. As there doesn't seem to be a way to revert to default timings, I'll wait for a fix for the custom res tab to see where that gets me.

Great work from you (and Nevcariel for the LAV part) in this build, thanks!

[madshi]

@madshi
Thanks.
I got a strange picture in D3D11 mode for Sony_4K_HDR_Camp.mp4. Other HDR files are displayed normally.
http://jpegshare.net/thumbs/f7/96/f796513181e541d68341e160484e7348.jpg (http://jpegshare.net/f7/96/f796513181e541d68341e160484e7348.jpg.html)
This appears to be a "bug" in LAV, but I'm not completely sure. At least it seems that LAV reports the HDR metadata differently when using software decoding vs D3D11 DXVA decoding. I have a detection for "invalid" HDR metadata in madVR which fires with LAV in software decoding mode, but not in D3D11 DXVA mode. I'll discuss this with nevcairiel.

@madshi, the sample is reuploaded again :) http://www101.zippyshare.com/v/oe86z81X/file.html
Thanks!

Display modes is still shown twice here with 0.92.1 and custom modes tab is only there for 1 sec and then its gone....
Are you sure it's really 0.92.1? Did you replace "mvrSettings32/64.dll"? Maybe your browser gave you an old version of the zip?

The Edit Timing for custom modes window is not set to be always on top. So it is opening behind the video when in full screen.
Actually it *is* set to be always on top! However, in fullscreen, it's possible that the media player (or even madVR) might try to make sure that the video surface is always on top, and if multiple windows are on top, only one can win.

Is the Pixel Clock not saving the changes?
I'm trying to set vertical back porch to 35 and pixel clock to 74.11 for a perfect 23.976hz result but the pixel clock is dropping back to 74.10 after applying it.
Only vertical back porch is applied but that results in 23.972hz.
Strange! I've just tested it here, and modifying the pixel clock works just fine here. Generally, the edit field is dropping back to the old value if interpreting your modified result failed for whatever reason. E.g. did you enter a "," for the decimal instead of a "."?

I'm on the JVC now, with the JVC as the active display, and still no custom res tab in the display modes screen (set-up in my sig below, although I also have a Vertex between the AVR and the JVC, which shouldn't make any difference). It briefly appears for a fraction of a second, then it goes away (I missed it initially).

EDIT: just to clarify, nVidia sees my display as Denon AVR, MadVR sees the Denon AVR, I tell it i's an AVR, and then I configure the JVC (Digital Projector) as being attached to the Denon. The OS only sees a Generic PNP Monitor, although for Audio it sees the Denon AVR, which is my HDMI Audio Out (Default). Maybe I'm having the issue because the display isn't connected directly to the GPU?
Hmmmm... I didn't test with an AVR. Does the "identification" tab have an EDID block in it? The display mode functionality requires the EDID information to be available.

If all else fails, can you try directly connecting the JVC to the PC? Just temporarily, of course.

1. What is the advantage of using perfect 23.976hz instead of 60hz with smooth motion ?
1a. The panning shots seem more fluid with the smooth motion solution, is that correct ?
True 23.976hz and 60hz with smooth motion should look very similar, except that 60hz smooth motion should have slightly more blur and maybe a little ghosting. So true 23.976hz is definitely better. However, not all displays handle 23.976hz input correctly. Some judder that way. So it's possible that 60hz with smooth motion might look better in your case.

3. Is this new "custom modes" feature of madVR created to replace ReClock ?
3a. As I see it, they work very differently. Can they work together ?
Yes, it's supposed to replace ReClock. I don't think there's any need to use ReClock, anymore, if the "custom modes" feature works for you.

4. I guess if I use smooth motion, I don't need to use the new "custom modes" feature at all ?
Yes, if you're only interested in 23fps/24fps movies and if you use 60hz smooth motion, then custom modes are not of interest for you. Neither is ReClock.

[nevcairiel]

This appears to be a "bug" in LAV, but I'm not completely sure. At least it seems that LAV reports the HDR metadata differently when using software decoding vs D3D11 DXVA decoding. I have a detection for "invalid" HDR metadata in madVR which fires with LAV in software decoding mode, but not in D3D11 DXVA mode. I'll discuss this with nevcairiel.

The Sony sample has broken HDR metadata, I wouldn't worry too much about it.

[madshi]

thank you so much for enabling 10 bit fullscreen windowed. Now HDR works perfectly !!
I'll donate for sure once the version 1.0 is out .
Glad to hear that! :)

Further feedback on 0.92.1 (set-up in sig below):

- Using the latest 385.28, there is an improvement re HDR in 0.92.1 as I can now get the HDR Metadata (MadVR set to pass through / send metadata) but the display doesn't switch to HDR automatically. Not a problem for me as I disable the JVC mode and switch manually to a custom mode, but I thought I'd try and let you know.
- The new 10bit path without FSE works great. That's really nice as on the JVCs FSE led to a few seconds black screen every time you used the player interface, for example, to select audio/subtitle track. Hopefully it will be possible to do without FSE for 3D too at some point.
Nice!

3D doesn't work for you without FSE? I'm pretty sure it worked for me, the last time I tested it. Although Nvidia is more picky than AMD and Intel. E.g. IIRC, it works with Nvidia only on the primary monitor, but with AMD and Intel also on secondary.

- I enabled non-native resolutions in the custom res experimental tool (as the custom res tab doesn't work yet for me in MadVR) and created a custom res with the 1080p23 EDID. Unfortunately, that didn't seem to translate into any improvement for 1080p23FP (still 1 frame drop/repeat every 3mn or so). Does 1080p23(FP) need a custom res distinct from 1080p23(2D)? I couldn't see such in the tool.
I don't really know. I'm not even sure if the custom modes generally affect D3D11 FSE or not. D3D11 FSE is somewhat "special".

Also, while there is no gain, when I return to MyMovies after playback of a 3D film there is a weird corruption on the screen. The screen is still in 1080p23FP, the MadVR OSD flickers on the left (even if MPC-BE isn't running anymore) and the bottom third of the screen flickers on the top third. Is there a way to reset If I exit MyMovies, the display returns to 4K23 and all is fine again. None of this happens without a 1080p23 custom res. As there doesn't seem to be a way to revert to default timings, I'll wait for a fix for the custom res tab to see where that gets me.
Don't know what to say about that.

[madshi]

The Sony sample has broken HDR metadata, I wouldn't worry too much about it.
Yes, but I did implement detection for broken HDR metadata in madVR, and it works when LAV is using software decoding. But somehow the D3D11 DXVA decoder reports the broken HDR metadata differently, so my detection fails. There must be a reason for that?

Here's my code:

if ((m_HDR.white_point_x != 0.0) && (m_HDR.white_point_x != 1.0) && (m_HDR.max_display_mastering_luminance > 1.0))"
It seems one of these conditions doesn't apply with the D3D11 DXVA decoder?

[madshi]

custom mode tutorial:

http://madvr.com/crt/CustomResTutorial.html

Also linked in first post of this thread.

[nussman]

HEVC 10bit works fine now with LAV DXVA D3D11 and madVR with AMD Polaris (Win 8.1 here).
Thanks madshi and nev. :)

[nevcairiel]

Yes, but I did implement detection for broken HDR metadata in madVR, and it works when LAV is using software decoding. But somehow the D3D11 DXVA decoder reports the broken HDR metadata differently, so my detection fails. There must be a reason for that?

I suppose it depends where you implemented that? Because in the D3D11 case I implement the IMediaSample, so if you have it in there, it wouldn't work.

Otherwise, the exact same data is being fed to you.

It reports a value of 1 nit, which seems to match the broken data.

[Manni]

Hmmmm... I didn't test with an AVR. Does the "identification" tab have an EDID block in it? The display mode functionality requires the EDID information to be available.

If all else fails, can you try directly connecting the JVC to the PC? Just temporarily, of course.


Yes, there is a (populated) raw EDID data. I'll try a direct connection with the PJ and will report back.


3D doesn't work for you without FSE? I'm pretty sure it worked for me, the last time I tested it. Although Nvidia is more picky than AMD and Intel. E.g. IIRC, it works with Nvidia only on the primary monitor, but with AMD and Intel also on secondary.

No, for me 3D only works with FSE. I tried without and I get weird colors/corrupted picture without (although as far as MPC-BE is concerned, it "plays"). I might try again without a custom 1080p23 timing, I can't remember if I tried before of after attempting the custom timings, but I think it was before.


Don't know what to say about that.

It would be great if the final tool (custom res tab) allowed to go back to the default timings after further testing. It's not because there is no crash that there cannot be a reason to revert we will only come accross later.

[madshi]

I suppose it depends where you implemented that? Because in the D3D11 case I implement the IMediaSample, so if you have it in there, it wouldn't work.
Oh, doh! You got me there... :o

It would be great if the final tool (custom res tab) allowed to go back to the default timings after further testing. It's not because there is no crash that there cannot be a reason to revert we will only come accross later.
You should be able to go back at any time by clicking on the custom mode, then pressing the "delete" button. At least that's how it's supposed to work.

[huhn]

custom mode tutorial:

http://madvr.com/crt/CustomResTutorial.html

Also linked in first post of this thread.

how about some even more advanced test.

like frame skipping: https://www.testufo.com/#test=frameskipping

or a test to check if a TV has a properly working 23p mode.

you use the same test and check the brightness of the squares. it should be very obvious on a TV that is doing a 3:2 pullup.