madVR - high quality video renderer (GPU assisted)

[maxkolonko123]

I was able to use a perfect pixel clock after reinstalling my drivers. Previously, the best I could do was one frame drop every 19 minutes.

I ran DDU and reinstalled the drivers (which was scary because the GPU was not detected and I had to look at Windows Update to see the drivers were downloading).

My stock clock improved from one frame drop every three minutes to one frame drop every 12 minutes. And, as stated, custom modes would now accept more modes.

So I think a lot of problems with custom modes comes down to improper driver installation.

Do I need to re run test mode again for custom modes or I can use the one already calculated there before fresh drivers?

[clsid]

Do it again.

[SamuriHL]

So I think a lot of problems with custom modes comes down to improper driver installation.

Hmmmm, that's quite interesting. I'm thinking a windows reinstall is in my future. That could prove interesting.

[maxkolonko123]

Hmmmm, that's quite interesting. I'm thinking a windows reinstall is in my future. That could prove interesting.

Nah nah sir I can't be bothered to deal with that anymore hehe it is never a fun. But maybe a second OS on diff partition, clean just to check and see, would be way easier then reinstall everything etc for no reason if it won't make any difference

[SamuriHL]

Nah nah sir I can't be bothered to deal with that anymore hehe it is never a fun. But maybe a second OS on diff partition, clean just to check and see, would be way easier then reinstall everything etc for no reason if it won't make any difference

In my case I have other reasons to do a clean install. I do think in my case it'll end up helping my madvr performance a bit and allow me to crank up some settings that I've had to relax which will impact my overall PQ. Right now I have madvr dialed in fairly well for my 1060 but if a reinstall can give me a little bit more performance, then I will surely put it to good use. LOL

[maxkolonko123]

In my case I have other reasons to do a clean install. I do think in my case it'll end up helping my madvr performance a bit and allow me to crank up some settings that I've had to relax which will impact my overall PQ. Right now I have madvr dialed in fairly well for my 1060 but if a reinstall can give me a little bit more performance, then I will surely put it to good use. LOL

Fair play, let us know if did improve after fresh windows :)

[Warner306]

I would start with the driver rather than reinstall the entire OS. It is unlikely madVR performance will improve at all. It is mostly worried about your GPU.

[SamuriHL]

Fair play, let us know if did improve after fresh windows :)

I would start with the driver rather than reinstall the entire OS. It is unlikely madVR performance will improve at all. It is mostly worried about your GPU.

Well, I needed a clean Windows install anyway, so, it was time.

Full clean install, clean driver install, and reinstalled J River MC24. Kept most of my madvr settings although for some reason it didn't pick up the same devices. I say this only because I don't know if it's relevant or not. Exact same device names but madvr detected them as new and greyed out the old ones. Anyway, set those up again and left everything else the same in madvr as it was before. I'm still getting some drops/repeated frames when bitstreaming, but, it's certainly a hell of a lot better out of the box than it was. We're talking 1 every 5 or so minutes. That's before attempting any custom res settings so this gives me hope that I may be able to solve the issue when I get some time later. Rendering times for the settings I have are around 15ms which is good. Haven't played with 3D yet to see how that goes. I'm not recommending people go reinstall windows, however. Simply saying that I needed to anyway and now that I have it certainly has improved things. Most likely, as you said, it's all driver related.

[MrDVader]

I have a JVC DLA-RS400 projector which up-converts to 4k and can do HDR, albeit, badly (the HDR that is).

However, my existing HTPC setup is not ideal for 4k due to HDMI cable length and aging HD7950 graphics card.

So, is it possible to down convert but retain the wide color gammet content? If so, how should I setup the MadVR HDR settings? I'm running win7 to a 1080p Denon receiver (which prevents passing 4k to the projector.

[oldpainlesskodi]

@Madshi

I have been following your work on the AVS forum re HDR to SDR conversion with corrective tone mapping - what are the chances of MadVR being able to trigger HDR, but perform the same corrective type of processing (as some suspect the OS HDR Toggle does)?

Would be amazing if possible, as so many HDR releases are badly mastered.

K

[mclingo]

interesting request, what about having a virtual HDR mode that conversts SDR to something that looks like HDR, now that would be cool. :)

[ryrynz]

Sony TVs can already do this, but it's not on the same level that this (https://arstechnica.com/information-technology/2017/05/sdr-to-hdr-conversion/) is on. It takes between three and 10 minutes to convert one minute of SDR footage. If they offered a cloud service madVR could tie into to make changes to the video that would be very cool.. but also a long way off, maybe madVR might do something many years from now.

[mclingo]

I meant a FAUX HDR mode like LG and SAMSUNG TV's have, VIVID with bells on, just adds a bit extra to the image, obviously nowhere near as good as real HDR mode but it would be a nice addition,

[maxkolonko123]

interesting request, what about having a virtual HDR mode that conversts SDR to something that looks like HDR, now that would be cool. :)

Clean gpu driver installation after DDU, without changing a thing in madvr 1.2h expected frame drop, but i see drops occure more often when check osd.

But now any of the custom mode wont work for me, only EDID one, the rest give me blank screen, or is getting rejected by gpu.

[mparade]

I assume that is the problem because the x265 command-line changed some time in the past. Now it must be "--transfer smpte2084" or simply "--transfer 16".

I tested your proposal. Your assumption was right. Now my LG C6V switch to HDR mode. MadVR recognize the input as HDR, but the the colors are totally wrong on my TV. Some colors are too red, some are too blue....and with a lot of artifacts. I still do not know where the problem lies. After converting the HDR source to SDR the video displayed is quite acceptable.

[nevcairiel]

Its quite possible that your TV doesn't like non-BT2020 HDR, since that would likely never exist in the wild.

[mclingo]

Clean gpu driver installation after DDU, without changing a thing in madvr 1.2h expected frame drop, but i see drops occure more often when check osd.

But now any of the custom mode wont work for me, only EDID one, the rest give me blank screen, or is getting rejected by gpu.


sorry if this is a silly question but have you set MADVR to passthru to display and meta data is ticked?

NVIDIA card or AMD?, are you going through a receiver, is it defo fully HDR passthrough compatible?,

[maxkolonko123]

sorry if this is a silly question but have you set MADVR to passthru to display and meta data is ticked?

NVIDIA card or AMD?, are you going through a receiver, is it defo fully HDR passthrough compatible?,


What have HDR passtrough to do with none HDR movie?? pc to tv for video pc to avr for sound, nvidia card.

but like i said it has nothing to do with hdr, i just cant set any custom display mode apart EDID one

[mclingo]

sorry I misread the issue you are having.

[maxkolonko123]

Clean gpu driver installation after DDU, without changing a thing in madvr 1.2h expected frame drop, but i see drops occure more often when check osd.

But now any of the custom mode wont work for me, only EDID one, the rest give me blank screen, or is getting rejected by gpu.


Ok, so basically just to have a check and compare stuff, i decided to remove 23p and 24p string from madvr so basically movie is played with display refresh rate which is 59hz, and results are : 1 frame drop expect every 2.xx hour, 0 dropped frames whatsoever after 20min playback in madvr OSD !! when literally i usually get like 20droped by 20min with matching refresh rate 23.97fps

[maxkolonko123]

sorry I misread the issue you are having.

it's ok :)

[Warner306]

I have a JVC DLA-RS400 projector which up-converts to 4k and can do HDR, albeit, badly (the HDR that is).

However, my existing HTPC setup is not ideal for 4k due to HDMI cable length and aging HD7950 graphics card.

So, is it possible to down convert but retain the wide color gammet content? If so, how should I setup the MadVR HDR settings? I'm running win7 to a 1080p Denon receiver (which prevents passing 4k to the projector.

You can calibrate your display for a wide color gamut in SDR mode (e.g. BT.2020), but the brightness will still be lacking. And your AVR may not passthrough the gamut. You would have to test. You would be referring to the HDR -> SDR conversion feature of madVR, which will passthrough the original gamut if you set this display is already calibrated to DCI-P3 or BT.2020 and set HDR to convert to SDR with pixel shader math.

However, before you test, you will need a graphics card with a 10-bit HEVC decoder, as your current card will not be able to downscale 4K -> 1080p, nor will it be able to decode it.

[Warner306]

Clean gpu driver installation after DDU, without changing a thing in madvr 1.2h expected frame drop, but i see drops occure more often when check osd.

But now any of the custom mode wont work for me, only EDID one, the rest give me blank screen, or is getting rejected by gpu.

You can only use the optimized EDID mode, or that is the only one you can set to measure the timings? If that is all you can accept to measure the timings, then there is no problem. What about the optimized modes? Can you select any of them? And are you certain you are still dropping frames with an expected frame drop every 1.2 hours? You shouldn't need a custom mode and madVR shouldn't be that inaccurate. You should do more testing.

I wouldn't sacrifice frame rate matching for a few dropped frames that are hardly noticeable.

[maxkolonko123]

You can only use the optimized EDID mode, or that is the only one you can set to measure the timings? If that is all you can accept to measure the timings, then there is no problem. What about the optimized modes? Can you select any of them? And are you certain you are still dropping frames with an expected frame drop every 1.2 hours? You shouldn't need a custom mode and madVR shouldn't be that inaccurate. You should do more testing.

I wouldn't sacrifice frame rate matching for a few dropped frames that are hardly noticeable.

I couldn't use any other for measure timing then EDID/CTA so after playing a movie and checking measured timings I can only use optimized EDID mode, can't choose any other after measured timings even when it shows 90% compatibility, from CVT to optimized pixel clock none of them can be accepted.

CVT v1-v2 blank screen till prob 20sec is gone to accept it, every pixel clock end up with disturbed image on TV, even when quickly disconnect hdmi cable and connect back i can see time to accept this mode i click yes then getting error about gpu rejecting this mode.

At the moment i have in custom mode " current timings " currently used by the GPU..... current timings,mesured timings and EDID/CTA all 3 shows same numbers and 1 frame drop every 1.07hours see screnshot -> https://imgur.com/a/OzZ5c


I won't sacrifice it either but i just want to find why is like that, i even choose in nvidia control panel to max performance from adaptive mode, it did more time to expected frame drop but yet still after playing movie for some time and checking osd i see noted drops there

[Warner306]

I won't sacrifice it either but i just want to find why is like that, i even choose in nvidia control panel to max performance from adaptive mode, it did more time to expected frame drop but yet still after playing movie for some time and checking osd i see noted drops there

That sucks. I am sorry I encouraged you to reinstall your drivers, as this fixed my issue.

Your new stock clock looks good and there doesn't appear to be a need for a custom mode. I have no explanation as to why you are dropping frames with an expected frame drop every hour or so.

[huhn]

are you using a 3d LUT?

[maxkolonko123]

are you using a 3d LUT?

where i can check it ? but i doubt that i do if u mean external 3d lut file

i got tick displaye is calibrated, disable gpu ramps, bt.709, pure power curve 2.20

[mparade]

Has madVR been improved considering the type of 3D input recently? I have FTAB sources to send to madVR with "--frame-packing 4" option signalled in the stream itself or can a simple naming rule be working with madVR to treat such a 3D format properly? Or still only AVC&MVC-3D is working?

I converted my BD3Ds to FTAB format while saving 50-60% storage space using some "transparent" x264 encoding settings so it would be great to be able to watch them using the astonishing capabilitites of madVR.

Any help would be appreciated.

[mparade]

Its quite possible that your TV doesn't like non-BT2020 HDR, since that would likely never exist in the wild.

I think so because all bt2020 HDR sources are being displayed properly.

[nevcairiel]

Has madVR been improved considering the type of 3D input recently? I have FTAB sources to send to madVR with "--frame-packing 4" option signalled in the stream itself or can a simple naming rule be working with madVR to treat such a 3D format properly? Or still only AVC&MVC-3D is working?

H.264 MVC is the only supported 3D format.

[brazen1]

I think butchering a rip so that it can semi play on hardware and other player software that wasn't designed to handle 3D frame packed MVC in the name of saving disc space and then asking that madVR pick up the slack is futile.

[Polopretress]

Hello.
MadVr est compatible with 32 and 64 bits configuration.
But what is the root to use 32 or 64 bits ? The player or , for example, Lav filters ?

[Asmodian]

Everything. 32 bit and 64 bit do not mix. 64 bit player, LAV, and madVR or 32 bit player, LAV, and madVR.

[Polopretress]

Yes, i thought it was the case and not possible to run a mixed configuration but it seems to be possible (it works) to run player 64 bits with lav32 bits.
As madVR is 32/64 bits, i wonder which is the mode (32 or 64 bits) selected by madVR in this case.

I made this stupid test to use a 64bits player on a 32 bits htpc because i have noticed that for some HEVC 10 bits movies, the CPU decoder was more speedy and did not reproduce some drops with a "queue decoder" at 1 in the CTRL J.
With full 32 bits htpc , on some video 4k hevc 10 bits, even if the CPU is still at 40%, "queue decoder" at 1 can be observed while it is not the case when i replace the player only by 64 bits version (this is true with potplayer an dmpc-be)

I try to find an explanation of the root cause.(why drop with "queu decoder" at 1 while the CPU is still at 40%)
An then secondary, in such mixed configuration , what is the selection of madVR?

It is reproducible with I7 4770 / 4790 / Ryzen 5 and hardware decoder set to "none" in lav video with the following movie for example :
http://4kmedia.org/lg-new-york-hdr-uhd-4k-demo/

[nevcairiel]

Yes, i thought it was the case and not possible to run a mixed configuration but it seems to be possible (it works) to run player 64 bits with lav32 bits.

No it is not possible. If you truely are you using a 64-bit player, then you must also have installed 64-bit LAV.

[sneaker_ger]

I made this stupid test to use a 64bits player on a 32 bits htpc because i have noticed that for some HEVC 10 bits movies, the CPU decoder was more speedy
[...]
I try to find an explanation of the root cause.(why drop with "queu decoder" at 1 while the CPU is still at 40%)
An then secondary, in such mixed configuration , what is the selection of madVR?
[...]
It is reproducible with I7 4770 / 4790 / Ryzen 5 and hardware decoder set to "none" in lav video with the following movie for example :
http://4kmedia.org/lg-new-york-hdr-uhd-4k-demo/
Yes, that's normal. The 64 bit HEVC software decoder in LAV is much more optimized than the 32 bit variant. For me it's about 75% speedup.

[lvqcl]

I wonder what "a 64bits player on a 32 bits htpc" means.

[LigH]

Running x86-64 (AMD64) Windows applications requires both a CPU with x86-64 instruction set and a 64-bit code variant of a Windows operating system (optional and common as private user OS since Vista, more or less mandatory since 8).

Thanks to the extended compatibility in the x86-64 architecture developed by AMD (in contrast to the Itanium IA-64 architecture by intel which is incompatible to x86 / IA-32), 32-bit x86 processes still run in a SysWoW64 (Windows on Windows-64) environment, but all DLL's used by a 32-bit process must also be programmed for 32-bit x86 architecture, and all DLL's used by a 64-bit process must be programmed for 64-bit x86-64 architecture. Windows will check the DLL header and refuse to load libraries not matching the bitness of the calling process.

To be able to load the 64-bit variant of madVR (and LAV Filters), you have to run a 64-bit player application on a 64-bit Windows.

64-bit code can already be faster simply because CPU registers in 64-bit mode have a) twice the width and b) twice the number, compared to the 32-bit mode. Every instruction which can avoid RAM access by using data still stored in another CPU register is a little improvement.

[tyrindor]

Anyone have any idea why I get audio drops when "MPC Audio Renderer" is selected in MPC-BE during DTS-HD and TrueHD tracks? It does not happen if I bitstream using LAV instead, but LAV doesn't offer exclusive WASAPI or the ability to uncheck "Use System Channel Layout" which is needed for me to get proper Dolby Surround emulation on 2.0 tracks.

I have noticed that the debug overlay says I am getting a repeat frame every 4-7 minutes. That's about how often the audio drops for a split second. I've tried exclusive fullscreen on/off, and 2160p23 is set in MadVR.

[LigH]

@tyrindor: Why do you believe that madVR is the reason? It appears to me that the most it does is reporting issues, and rather indirectly (as a video renderer, it does not process audio at all).

[tyrindor]

@tyrindor: Why do you believe that madVR is the reason? It appears to me that the most it does is reporting issues, and rather indirectly (as a video renderer, it does not process audio at all).

I don't really know what the reason is, I was hoping someone here would know. I am running a typical setup and bitstreaming lossless codecs, so I figured someone else might have experienced this. I have no idea if it's related to the frame repeat every few minutes or not.

[madshi]

Sorry for the long absence, everyone. Have been busy with commercial work, still am, but hope to get back to madVR development soon(ish).

I hope it can add 2d to SBS function，thank you!!!!
What do you mean exactly?

Anyone know of a player that can capture screenshots with the HDR data preserved? From some searching it seems there's JPEG-HDR and RGBE PNG for formats but not sure what the limitations might be.
I'm not aware of any player which supports that. Currently also the madVR screenshot interfaces don't really support transporting all the necessary information to the media player. I guess I could add that if there were a media player developer interested in adding this kind of functionality. However, creating such screenshots would only be one step, you'd also need software to actually render such screenshots properly. Is there any software that does? It would probably have to do tone mapping, gamut mapping and all that kind of stuff...

I would like to know how to use the control function for the videoprojector, in particular I would like at the end of the playback to return to position 1 of the lens. thank you
That's not too easy because "end of playback" is difficult to detect for madVR, and changing the lens position takes a LONG time. E.g. let's assume you have a playlist with 2 files in it. At the end of the first file madVR might think that playback has ended. But you wouldn't want the lens to return to position 1 now, would you? So basically madVR would have to add extra stuff, e.g. wait for 20 seconds and only then restore the original lens position.

Currently madVR only supports setting the lens position to a specific slot, but it doesn't support restoring the original lens position (or even activate a specific lens position). If I were to implement this kind of functionality, I wouldn't want to offer a "after playback activate lens memory 1", instead I would offer "after playback restore original lens memory", which makes more sense to me.

But since you're the first user to ask for this, I'm not sure how high the demand for this really is. Usually, I require at least 3 users to ask for a specific feature before I put it on my to do list (unless I really want the feature myself).

1. I would know why madVR, when i use NGU 4x, after oversize, downscale image two times in luma y with some source resolutions?
This could be a bug. Unfortunately you cropped some important lines from the OSD away, so the information I got is rather minimal. I'd need to know how to reproduce this issue on my PC exactly. So which display resolution, do you have? Which movie resolution? Which exact scaling settings? Etc etc...

2. Always with NGU 4x, with Low or Medium quality, chromaupsampling seems forced to Bicubic60 during the doubling/quadrupling process. Can i use "chroma settings" for entire chroma upsampling ?
NGU Low or Medium settings practically get Bicubic60 chroma upscaling "for free", that's why it's forced in this situation, to get the best possible speed. I understand if you care more about quality than speed. But in that case you should really spend your GPU power on using NGU High quality instead of increasing the chroma upscaling quality, because luma quality is *much* more important.

If your GPU is too slow for NGU High quality, then you need to save any GPU power you possibly can, and getting Bicubic60 "for free" should make you happy. If your GPU is fast enough for NGU High quality, then use that and don't worry about chroma quality too much.

Hi, I have a question about HDR: MediaInfo for Dunkirk UHD Blu-ray says:
However, madVR's OSD is regularly showing much higher values than 323 cd/m2, and even the credits at the end with pale white text on black show 170-200 cd/m2.
Is the OSD 'correcting' the values somehow, or is MediaInfo reporting wrong values?
maxCLL shows the highest RGB component, not really the true luminance of the brightest pixel, so it can differ from what madVR measures. However, as far as I understand, although maxCLL can be higher than the peak luminance, it shouldn't be lower. So if maxCLL says 323nits and madVR measures more, then most likely maxCLL was set incorrectly when the movie was authored/encoded. Of course it's also possible that MediaInfo has a bug, but I'd rather guess that the movie is badly authored/encoded.

I'd love to see if any possible please would be "activate only if it doesn't drop frames" for luma quadrupling because I'm never really sure whether I can afford it and those "set and forget" options are wonderful.
It's on my to do list to look into things like that, but it's not too easy because performance measurements aren't always fully reliable. So it will take some time to implement a proper solution for that.

Can you work with this for implementing DV in madvr maybe? ^^

https://www.dolby.com/us/en/technologies/dolby-vision/dolby-vision-bitstreams-within-the-iso-base-media-file-format-v2.0.pdf
https://www.dolby.com/us/en/technologies/dolby-vision/dolby-vision-bitstreams-within-the-mpeg-2-transport-stream-format-v1.1.pdf
https://www.dolby.com/us/en/technologies/dolby-vision/dolby-vision-streams-within-the-mpeg-dash-format-v1.1.pdf
https://www.dolby.com/us/en/technologies/dolby-vision/dolby-vision-streams-within-the-http-live-streaming-format-v1.1.pdf
These are helpful (I already had them, though), but the real problem is not *my* interest in DV. The real problem is that I can't do anything, as long as no splitter/decoder transports the DV information to me. So you're barking up the wrong tree here. You don't need to convince *me*. You need to convince a splitter/decoder dev. If you find one who's interested in implementing DV, I might look into it, too. But without an interested splitter/decoder dev, there's literally nothing I can do.

madVR lags too much on my HTPC.It consumes 75% of CPU but only 2% of GPU.I tried to reinstall the video card driver and the OS,but that didn't work.Is there anyone who knows how to solve this problem?Thanks!

My HTPC:
CPU: AMD Phenom II x4 965
Video card: R7 360 2gb
RAM: 8GB DDR3
MB: GIGABYTE GA-970A-DS3P
It seems that "uploading" 10bit+ textures to your GPU causes the CPU consumption. This transfer is done through the PCIe bus. This could be a bad setting in your BIOS, or a bad BIOS firmware, or a bug in the GPU BIOS, or a problem with the OS installation of the GPU driver. It's really hard to pinpoint. I had one user in the past who had a similar problem and he updated some firmware (not sure if it was the mainboard BIOS or the GPU BIOS) which fixed the problem for him. I'm not sure if it's the same for you.

You can probably work around the issue by forcing LAV Video Decoder to only send 8bit video frames to madVR (by unchecking all 10bit+ formats in the LAV configuration), but obviously that's not a good thing to do for image quality.

hi, i want to ask, for a samsung monitor (32chg70) madvr reports the bitdepth of the monitor is 8bit, and the windows 10 reports it a 10bit.
Where does Windows 10 report the display bitdepth? It doesn't to do that for me.

Hi, madshi. In the latest 0.92.12 whenever I try to take a screenshot when paused, the potplayer crashed. And taking a screenshot when playing will get me an abnormal image(strange colors like a thermal image of the original one).

I haven't changed any settings and it can just take screenshots without any problem in older 0.92.X versions.

I use WIN10 with RX480.

Maybe the problem in changelog of 0.92.11 "screenshots in paused state sometimes crashed madVR" is still not fixed? Just a guess.

Anyone have some ideas or the same problem?

----------

And another problem.

I use lav 0.71 with latest madVR in D3D11 native mode, and the picture is always(no matter what video) split into the top and bottom part. The top part is the picture content turned into a flat size, and the bottom part is often a green image.

While D3D11 CB can just play normally.

Is there any idea about the problem?

nevcairiel said it sounds like a driver problem and madVR handles the processing of "native" frames. So I report it here.
Have you tried reinstalling or updating the GPU driver?

Does the screenshot problem go away if you use "copyback" decoding or software decoding?

I have an LG E6 and an HTPC with an Nvidia GTX1050 GPU (390.65 driver). In Nvidia control panel, if I select 2160p YCbCr 4:2:2 and tell MadVR I have a 10-bit capable display all works well for HDR video.

I noticed by accident that if I change Nvidia video mode to RGB 8-bit then when I play a 60Hz HDR test clip (eg. LG's "Chess") I was getting "sparkles", showing HDMI errors.

I noticed that MadVR was outputting 10-bit depth even when using RGB and 4K/60 RGB 10-bit is not allowed by HDMI 2.0.
Are we talking about HDR passthrough, as in switching the TV into HDR mode? For Nvidia GPUs I use a custom API to do that, which bypasses some of the OS and GPU driver safety checks. So that might explain why the GPU tries to output something which is impossible to output. I guess I could add a safety check to prevent madVR from trying to output 4Kp60 10bit. Will add that to my do to list...

[madshi]

I'm reading a lot and hardly trying to figure out how I know when I simply need to enable deinterlacing and when I need IVTC.

I never seen IVTC turned on automatically, don't know why.

But in my dvd profile, how I know if I only need deinterlacing or IVTC?
Ok, so here comes a full blown explanation, hopefully it will put the topic to rest:

With default settings ("disable automatic source type detection" unchecked), madVR always uses DXVA deinterlacing. The exact DXVA deinterlacing algorithm is provided by the GPU hardware/driver. It's supposed to automatically detect the source type and internally switch between whatever deinterlacing technique is needed for best results, even per pixel. Since the algorithm is provided by the GPU, not by madVR, the quality will depend on the GPU manufacturer, GPU model, maybe even OS and driver version.

There's one thing DXVA deinterlacing cannot technically do, which is decimation. DXVA deinterlacing *can* (at least in theory) detect telecined movies and deinterlace them correctly, e.g. from 60i to 30p. However, from those 30p only 24p are unique, the other 6p are duplicates. Removing those is called "decimation".

Because I wasn't happy with the lack of decimation support, and with the general state of the DXVA film mode deinterlacing, I added a "forced film mode" to madVR. If you want to use it, you have to enable it manually. Of course you should do that only for true movie content. Otherwise you'll get nasty artifacts.

Practically, most PAL movie DVDs don't need any deinterlacing at all. But there are exceptions. Using forced film mode should work for both those PAL movie DVDs which don't need deinterlacing, and also for the exceptions.

NTSC movie DVDs and ATSC movie broadcasts almost always need deinterlacing. For those forced film mode should work great and shoudl be able to restore the original 24p.

Forced film mode doesn't work for natively interlaced content (e.g. sports, concerts etc), and also for field blended stuff. Sometimes you can't know if forced film mode will work or not. In that case you'll simply have to try. If it doesn't work, you'll probably see that immediately.

Got a madVR / Driver Stopped Responding crash here, latest version and latest 18.2.2 AMD drivers on a R9 270X. Windows 8.1.
The crash occured when I was seeking a passthrough Twitch stream in MPC-HC, while a second instance of MPC-HC had a movie paused.

https://pastebin.com/ZvprjHaD
This is a crash in the AMD GPU driver, in the moment when madVR tries to release the D3D11 "compute" device. Currently the compute device is only used for error diffusion and for the "measure frame luminance" HDR feature. Did you happen to use either of those?

Generally, if you only got this problem once, it's probably safe to ignore it. If you get it often (or once in a while), try disabling the mentioned features. If that still doesn't help, try also disabling the "use D3D11 for presentation" option in madVR.

Also, try updating the GPU driver.

What about image refinements or smoothmotion?
Are there some possible improvements to do?

What about a reclock alternative since custom resolutions are still problematic with old and current hardware?
I've on my to do list to look into AdaptiveSharpen some more.

Reclock is mainly an audio renderer, which is not something I'm interested in developing.

Well, since I began of dreaming I would also ask madshi what he think about upscale detection and about upscale reversion possibility.
I'm not sure if upscales can be easily detected and reverted. I mean if I *knew* a certain video was upscaled with a specific algorithm from resolution X to resolution Y, I could probably find an algorithm to fix that. But I would have to know all the details. And I don't think I can get them from just looking at the pixels.

Hi, madshi. About the problem, I have tried various settings in the screenshots tab.

I find that if I draw subtitiles(uncheck "don't draw" by default), then it will crash whatever other settings are(even if there aren't any subtitles). Can this be helpful to you? Anyone have the same situation?
Interesting. Which subtitle renderer are you using? Does switching to a different renderer help?

And a question: Do I have to re-optimize the custom timing everytime when I update the graphic card driver? (RX480 in my situation)
As long as the custom timings survive the GPU driver update, probably not.

PS: A tiny UI visual suggestion. The "color & gamma" tab in "devices" settings: the beginning position of the first letter "c" is some space backward compared to the other tabs' title.:)
True. Thanks!

Hi. someone with experience to create a 3dlut for HDR content with Calman? Is there any guide or manual to consult?
Do you want that 3dlut to convert the HDR content to SDR for you? Or do you just want to calibrate your display, but still passthrough HDR content to the display? I'm not sure if Calman supports either of these two options, to be honest. HDR calibration is a difficult topic. My preferred approach would be to let madVR convert the HDR content to SDR and then run the result through a normal SDR 3dlut (though maybe for BT.2020 or DCI-P3 gamut).

I wanted to know if any of you could help me about the subtitles of blu ray scaled to 3840x2160, in practice when the fixed subtitles come out the image slows down by going for a few seconds, increasing the rendering and after the subtitles disappear it is replaced, this it happens even if I use JINC as IMAGE UPSCALING.
My video card is AMD RX480, media player JRIVER, os WINDOWS 10.
I don't really understand your explanation of what's happening. Can you explain in more detail?

I have a stable madVR crash on a movie file when the following settings are enabled
That's a weird one. It crashes while trying to upload the video frame to the GPU. Does this crash occur with all video files, or only some? Does it occur regardless of madVR settings, or do some madVR settings play a role in the crash (if so which)?

Do you know if madvr's madTPG works with the new autocal feature on the new 2018 lg oled tvs?
I'm not sure I understand the question. Are you asking if the LG TVs are able to remote control madTPG? If so, as far as I'm aware, the answer is no.

8GB RAM and task manager says 38% usage.
MPC-HC CPU usage goes up to 70% with madVR and QS in LAV.
With copy-back it's ~45%

With EVR the Sony HEVC 59/60fps Videos work up until ~25 seconds and sometimes one minute. Then the sound starts to stutter and slowly the Frame rate in the MPC-HC statistics window is going down.

The attachment is:
4K H.264-AVC MPEG-4 [60.000fps][8-35Mbps][8bits][DD 5.1 (AC-3)] Big Buck Bunny
in madVR.

With EVR this movies video is smooth but sound is totally out of sync. Sync Offset, dropped and Jitter show all 0.
According to your screenshot your decoder is too slow.

Does the scripting support unc path
Probably. Why don't you simply try?

I have been following your work on the AVS forum re HDR to SDR conversion with corrective tone mapping - what are the chances of MadVR being able to trigger HDR, but perform the same corrective type of processing (as some suspect the OS HDR Toggle does)?
What do you mean with "corrective tone mapping" and "corrective type of processing"? I'm not really sure what you mean/want exactly.

what about having a virtual HDR mode that conversts SDR to something that looks like HDR, now that would be cool. :)
Not planned.

yes and if that happens with "let madVR decide" i see this as a real problem and it should be changed to at least 3.0. quadrupling for 20 missing pixel is just a total overkill.
I agree, quadrupling for less than a 3.0x upscale is total overkill, and even a negative at times. However, I thought "let madVR decide" for quadrupling was 2.4x so quadrupling should not have activated. :confused:
2.4 default for double again mode (or NGU AA). For direct 4x "if any upscaling is needed" by default.
Please feel free to suggest better "let madVR decide" settings, I'm open for suggestions. Obviously the reason for choosing different setings for "direct 4x" is that it performs dramatically better than "double twice".

I've been doing further testing and managed to capture better screenshots (download and present them at 1:1 resolution) to exemplify my findings:

NV HDR triggered by madVR (output 10 bit) BANDING (http://www.helloutro.com/banding.png)
NV HDR triggered by madVR (output 8 bit) NO BANDING (http://www.helloutro.com/nobanding8bitNVHDR.png)
OS HDR enabled at Windows 10 (output 10 bit) NO BANDING (no screenshot available, too bright)
This looks like a madVR bug to me. There's a technical limition in the OS right now which supports 10bit in fullscreen windowed mode - but only if the OS HDR switch is turned on. So as long as the OS HDR switch is turned off, madVR should not even try to switch to 10bit in windowed mode. If you want the OS HDR switch to be off, you have to use FSE mode to get 10bit. Or alternatively use 8bit and trust madVR's high quality dithering. It might actually look better than 10bit, depending on your display. Worth a test, at least.

[mclingo]

good to have you back MADSHI, hope everything's going well on the commercial side, thanks again for you continued support.

[madshi]

Big thanks to everyone who is helping with madVR support work. I really apprecate it. You're making it much easier for me to handle the overall madVR workload. So you're indirectly contributing to madVR development.

I planned to add a list of users who helped with support work a lot, but then I feared I might forget someone who might then be disappointed, so I decided not to list any user names. But please rest assured that I read all posts in this thread, and your support work is not going unnoticed. Thank you again!

:thanks:

Next madVR build will come maybe in a week or two or so, I'm not sure right now. It will feature improved HDR tone mapping quality and an additional "low" RCA quality level (which will fuse with NGU medium quality).

FYI, although I didn't have much time for madVR recently, I did start working on a totally new algorithm (not scaling related) last year, and I've been working on it ever since. I even hired external help for some things I didn't know how to do myself (I'm not a math genius, unfortunately). I'm not completely sure yet if I can manage to make it work. It might end up being much too slow, or too low quality, but I'm hopeful. If it works out as well as I hope, it could be a relatively big thing. But it's going to take several more weeks at least. Sorry, no more information at this point.

[huhn]

where i can check it ? but i doubt that i do if u mean external 3d lut file

i got tick displaye is calibrated, disable gpu ramps, bt.709, pure power curve 2.20

you shouldn't have one.

[Asmodian]

I'm not sure I understand the question. Are you asking if the LG TVs are able to remote control madTPG? If so, as far as I'm aware, the answer is no.

I do not believe madTPG would need to support AutoCal, that feature is talking to the TV over the network, not HDMI. madTPG would be the pattern generator but not the display.
Portrait Displays to Provide Auto Calibration for 2018 LG OLED and SUPER UHD TVs (https://www.prnewswire.com/news-releases/portrait-displays-to-provide-auto-calibration-for-2018-lg-oled-and-super-uhd-tvs-300577373.html)


Please feel free to suggest better "let madVR decide" settings, I'm open for suggestions. Obviously the reason for choosing different setings for "direct 4x" is that it performs dramatically better than "double twice".

I still think using 2.4x would be more appropriate, direct 4x does take a little more GPU power than 2x and it would be consistent. Upscaling to 4x and then downscaling to 2.05x is not ideal.

Thanks for all your work, as always great stuff. :)

[Warner306]

"This looks like a madVR bug to me. There's a technical limition in the OS right now which supports 10bit in fullscreen windowed mode - but only if the OS HDR switch is turned on. So as long as the OS HDR switch is turned off, madVR should not even try to switch to 10bit in windowed mode. If you want the OS HDR switch to be off, you have to use FSE mode to get 10bit. Or alternatively use 8bit and trust madVR's high quality dithering. It might actually look better than 10bit, depending on your display. Worth a test, at least."

FSE is now required for 10-bit HDR passthrough, from madVR to GPU to display? I didn't know FSE was a requirement. This could be a problem for users getting occasional black screens on playback stop, or having FSE fail completely at playback start with Windows 10, which reverts to windowed mode without the user knowing, unless they read the message from madVR that FSE has failed. It's not that big of deal, but I'd like to know that FSE is required for full, 10-bit HDR passthrough, as most users are using windowed mode and madVR is reporting 10-bits during HDR playback. As a result, they appear to be getting banding.

Getting people to believe that they're not missing anything with 8-bits with dithering seems to be the bigger challenge. If FSE is problematic, they don't want to downgrade to 8-bits because their display is 10-bits and they think they need to take advantage of those extra bits.

Edit: The user I was talking to was using 12-bits at the GPU with AMD card for GPU passthrough, so this was actually a full 10-bit pipeline form madVR to the GPU to the display, not 8-bits at the GPU as previously reported. I assuming it is still necessary to have a complete 10-bit pipeline with AMD cards for HDR passthrough from madVR to the display?

[Warner306]

And one more thing...I assume the Windows OS is sending the metadata to the display untouched and isn't altering it to change the tone mapping, just like the private APIs do? So the Windows HDR calibration tool (which is simple as can be) only applies to the Windows desktop and not to video playback?

[Warner306]

"I have been following your work on the AVS forum re HDR to SDR conversion with corrective tone mapping - what are the chances of MadVR being able to trigger HDR, but perform the same corrective type of processing (as some suspect the OS HDR Toggle does)?"

This user wants to know if you can somehow send the PQ transfer function to the display to trigger HDR mode and use madVR's adjustable and sometimes superior tone mapping to replace the display's tone mapping? Sounds technically impossible, but would be nice.

Edit: I forgot about "process HDR content by using pixel shader math" as pointed out by Asmodian. How far would that get him? Are all of the YCbCr values tone mapped and stripped of illegal color values and then sent to the display to be tone mapped again? Does the metadata remain the same? Is this recommended?