[madshi]

Originally Posted by mrmarioman

I figure it out. Nothing to do with madvr. Sorry. I had to change a few settings from my Samsung TV. It has an option for 'Colour space', and it was set to 'auto'. I changed it to 'Native' and voila, colours now look right. Funny enough if I go back to 'auto' they also look good now.
I also had to change the 'hdmi black level' setting -which is an option for 16-235 or 0-255- from full to limited. Or else I would get washed out blacks. Now it looks great. Thanks for your time.

Glad to hear you got it solved. It's always difficult to diagnose these kind of problems remotely because every TV behaves differently, and some have rather weird options...

Originally Posted by steakhutzeee

I use a 1920*1080 full hd monitor, and mpc-be. Zoom settings in madvr are configured to move subs to the bottom.

I tried with ISR, VSFilter and XySubFilter but subs are not showed in the black bars, but on top of video. How can i solve?

As i can see (using xysubfilter), the subs are on top of video for a portion of time, then go in black bars, then returns on the video area... don't know why...

There are various different issues at play here:

1) VSFilter does its thing before madVR is involved, so the subtitle placement it totally out of madVR's control.
2) I think MPC-BE's ISR doesn't fully support madVR's subtitle positioning options. You *may* have more luck with MPC-HC's ISR. IIRC kasper93 had invested some time to make it work. But I'm not sure how well it's working.
3) The ideal solution would be XySubFilter or AssFilterMod. However, there's a bug in XySubFilter when playing *external* text subtitles which have italic subs in them. You can workaround this issue by either removing the italic sub, or by muxing them into the MKV. It's on my to do list to try to fix this in XySubFilter, but since I don't know the XySubFilter source code at all, it's very hard for me, so I've been pushing this back for a long time already...

Originally Posted by Fabulist

Content type reported to the display does nothing when I change it because HDMI Content Type is disabled on the TV. Therefore, the TV ignores such signals from the PC. I do not really need it since I can force the best HDMI Content Type for movies from the TV instead of waiting for NVIDIA's CP signal. Now, changing the HDMI Content Type to anything but "Graphics" and "Photos" gives an unnatural image. Graphics and Photo modes have a less dynamic image, showing less vibrant and not so rich colours (as if the gamut range is crippled) and although the TV's main menu settings seem unchanged, brightness and gamma seems lower as well. Cinema is a weird mode that is disabled from factory defaults (so it won't activate on its own) and can be forced on, but it seems a bit washed out and dark, brightness and gamma are too low and it forces warm colours, looks similar to the so called "THX Cinema" mode, which is complete crap. Game is a mode I cannot force on but it should be able to activate automatically - I do not know under which circumstances it activates and what it does but I am pretty sure it will not do any good for movies with madVR. Lastly, NVIDIA's CP "Auto" Content type will always sent a "Graphics" signal when madVR is playing and the TV will treat it as such if I have everything turned on. If I force the content type from NVIDIA's CP to "Movies" the TV will treat it as "Off" (no mode) by default unless I have Cinema mode on, which is not a factory setting.

Sounds complicated. But if you look at "el Filou"'s recent posts, he also reported issues with black & white levels, and for him the "content type" was involved in finding a solution.

For me it's extremely difficult to help in this case because every TV behaves differently, and some have really weird options. E.g. look at mrmarioman's recent post. He had to switch a very specific option in this TV to make it work.

Originally Posted by Fabulist

The HDMI RGB Range has 3 settings: Auto, Full, Normal. For some reason the TV means "Full" = 16-235 and "Normal" = 0-255. This is an inconsistency which I never really noticed since I always used "Auto", until recently that I started fiddling with NVIDIA's CP output and madVR's settings. The TV's "Normal" (0-255) will force a 3rd black crushing level when activated which is slightly more unnatural than the black crushing NVIDIA's CP / madVR does when set to their equivalent "0-255" - as if there is a loss in quality. Auto seems to almost always use "Full" (16-235) or Limited for everything else, and this is what it defaults to when receiving signal directly from the blu-ray disc or any signal in general, in all my tests it never switched to its 0-255 levels. This mode does nothing when YCbCr signal is sent.

Well, I would need to have my hands on your PC and TV to figure out what's going on exactly. I can't really solve this issue remotely. It's possible that your TV is simply broken in such a way that it can't properly handle RGB input with correct black & white levels from your GPU, for some reason. Or maybe it needs a very specific set of options to be activated.

In any case, as the other users already indicated, THX and Cinema modes are *usually* the most accurate modes. If you don't like them that could mean that they're broken on your TV. Or it could mean that you're so used to the "wrong" modes that the accurate modes look bad to you now. It's impossible for me to judge. When using THX or Cinema modes, if you disregard the warm colors and bad "look" to your eyes, do the black & white levels at least work correctly? If so, that would be a clue as to why they might not work correctly in the other modes.

Originally Posted by leandronb

Hi guys. I noticed that in recent madvr versions image upscaling and doubling are now on the same page, most guides i checked was on older versions, so i am wondering which option should i choose.
I have a GTX 1070 and was using dxva2 on most options, very low render time but i read that i was losing some image quality. So which settings are considered the best to use on a good gpu?
Also if i have a good gpu, is there a reason to not use dxva2 on image downscaling? Isn't downscaling only used when the window is not on fullscreen?
Edit: I use a 1080p display.
I also notice how little resources dxva2 uses. I put every possible setting on dxva2 and only chroma upscaling on nnedi 128 neurons gives me 0,3ms render time, gpu is almost at idle.
I already tried some settings but it seems that it doesn't make much difference.
I tried one that uses NGU and other settings enabled that put my 1070 to really work hard but not really sure if I saw any difference.
I tried with 720p and 1080p sources, all with high bitrates.

When playing 1080p sources on a 1080p display, none of the image up- and downscaling options have any effect because image scaling is simply not used. However, chroma upscaling is still active, but differences in chroma upscaling quality can be difficult to see, unless you test with specific scenes and know exactly what you're looking for.

720p playback on a 1080p display is a different situation. There image upscaling is the most important setting. But it's not a very large upscaling factor, so the difference between different upscaling algorithms will not be as large as when e.g. playing an SD video, or when upscaling to a 4K display.

I don't recommend DXVA scaling. Try NGU Standard or NGU Sharp for image doubling with "High" quality. And I'd recommend SSIM1D downscaling. Downscaling in your situation will only be active if you play 4K content. For chroma upscaling I'd suggest NGU Anti-Alias Medium quality.

Originally Posted by mrmojo666

Is HLG support in the backlog ?

It's on my to do list.

Originally Posted by Jasch

AMD CP is set to RGB Full 4:4:4, madvr 0-255 10bit or more.
all automatic switching + hdr let madvr dec.

Playing 1080p 8bit everything fine.
4k50 looks good for me, madvr says 10bit but Avr still says 8bit
4k23 HDR, HDR working says 10 bit, AVR still says 8bit.(colors looking right)

If i set AMD CP to 10bit
1080p 8bit colors are wrong(AVR says 10bit)
4k50 madvr says 10bit, AVR 8bit(Colors i.o)
4k23 HDR, madvr and AVR report 10bit(Colors i.o).

I think HDMI doesn't have enough bandwidth to do 10bit RGB at 50fps, but I'm not sure right now. It definitely doesn't work for 60fps. So that's probably the reason why you're getting 8bit at 50fps. I'm not sure if the AMD driver dithers down to 8bit in this situation. So if you really want to use 4Kp50, then it might make sense to use a profile to enforce madVR to output 8bit at 50fps, so you get madVR's high quality 8bit dithering.

1080p 8bit colors looking wrong sounds like a driver issue. You're not using anything DXVA, right? If you're using DXVA anything, check if disabling DXVA solves that. (DXVA copyback is safe to use, though).

Originally Posted by dvd1

when the frame 40.00ms is equal to average stats rendering 40.00 ms

graphics card at the limit?

Yes.

Originally Posted by dvd1

http://madshi.net/madVR/NGU/clown4xNguSharp.png I do not like
http://madshi.net/madVR/NGU/clown4xNguSoft.pnghow much do I like, what are the settings to observe them?
sd to 1080p

The settings for the 2nd image are NGU Standard with a bit of grain added (in the upscaling refinement settings).

Please note that this test image is very sharp, sharper than most movies, and the upscaling factor is very large (400%). The difference between various upscaling algos will be much smaller if you have a smaller upscaling factor, and if the video is softer.

Originally Posted by Pat357

There seems to be something very counter-intuitive about the new custom mode creation interface.
With v0.92.4, I can not longer create a new custom mode or optimize an existing mode.
When I try to add a custom mode I press add then fill in 47 or something.
The next screen shows the timings for the standard modes.
I select the first and press test.
Unlike with the previous version, there is no longer an apply button to select and confirm.
All I get is the TEST and CANCEL button!
With v0.92.3 there was an additional APPLY button and if pressed I was asked to reset the GPU.
What happened to the APPLY button??

I'm sorry, that's my fault. I wanted to improve the user interface for Nvidia users, and I actually did, but in the process I accidently broke optimization capability for Nvidia users. This will be fixed in the next build.

Let me explain the reasons for the change: The Nvidia custom mode API requires me to "test" a new mode before it can be saved/applied. In the old GUI you could test a mode, and then "apply" it. The "apply" button internally had to first invoked testing, only afterwards I could tell the Nvidia driver to save the mode. This was somewhat ugly and I wasn't sure it would always work right.

The new GUI now works more similar to how Nvidia's own custom mode control panel works: You first have to "test" a new mode, then in the small window that appears while testing the mode, you can "save" the mode, if it works. This "save" button has the same effect as the old "apply" button, except that the "save" button works directly, without having to internally "test" first, because we're already in "test" mode in that moment.

The bug is that the "save" button in the small window doesn't prepare the registry for measurements / optimization, while the "apply" button does.

Originally Posted by Stereodude

I have a problem with madVR freezing when watching the premier of Star Trek Discovery recorded from my local CBS (1080i) station. 91.11 and 92.4 both do it. EVR does not freeze. The video and overlay will freeze and audio keeps playing. The spots for freezing are not consistent. The file is clean with no MPEG-2 errors.

It seems to be an issue with the "automatically detect hard coded black bars" feature. With it off (unchecked) playback is okay. This is probably the first IVTC'able 1080i60 content with hard coded black bars I've ever played. The feature seems to work fine in 1080p24 Blu-ray content as I haven't ever had a lockup like this before. Similarly, full screen 16:9 1080i60 (without hard coded black bars) IVTC's fine with no freezes.

I'm using MPC-HC 1.7.13 x64 / Win 8.1 Pro / Nvidia 1080.

How quickly does the freeze occur? After a couple of seconds of playback? Or minutes? Or hours?

Can you try to create a freeze report by pressing Ctrl+Alt+Shift+Pause/Break? If you can get a freeze report, please upload it to pastebin for me to look at. Thanks.

Originally Posted by kingpage

Madshi, would there be plan to bring NGU to MPDN as well? Or is there a way I could interface your files with the render script there?

Unfortunately no plans for that. There will "soon" (sorry, no ETA) be support for applying madVR algorithms in Avi/VapourSynth scripts. So in theory you could create a Avi/VapourSynth script using madVR to upscale the video via NGU and then play that script with MPDN (if MPDN supports "playing" Avi/VapourSynth scripts). However, it's not very comfortable because you'd have to adjust the script for any new movie you're playing. Still, if you absolutely need it, it would work this way.

Originally Posted by arrgh

I was traveling for more than 2 weeks and had therefore no Chance to test or to answer; now I have catched up and updated to the newest Software Versions of madVR, LAV and MPC-BE;
the Problem still persists; 2D is fine; 3D is playing fine (TV is set to 23p/3D mode), but when I close the player the refresh rate is not reverted to 50p (my standard for PAL-TV) and MPC-BE stays open with a black full screen; only a restart of the PC helps since I can not bring other windows on top;

when I switch off the "3D toggle" for my TV in the Windows controls, then I get a side by side picture on the screen; the TV informs me that a 3D-signal was recognized and I could manually switch to 3D mode; still, if I close the player it hangs too;

I switched to 32 bit LAV and MPC-BE and could use the Tracer tool, but only with MPC-BE in a window; otherwise I can not access the tool; it seems that the outcome is the same like in x64 and full sreen... MPC-BE hangs; TV stays in 23p;

https://mega.nz/#!bgFhiBpb!sNYjbZgMI...KuZRy3LGAXPofc

had no time yet to look into Win8.1; but the studder was on a regular basis every maybe 2 sec;

forgot to mention in the title : Intel KBL i5 7200U / hd620 graphics

I can't see anything interesting in the freeze report. From what I can see, madVR is already freed and mostly gone. So it's hard to say why MPC is frozen. However, there's still some hope to analyze this further: If you can repeat this with an MPC build with matching PDB debug symbols for MPC (and ideally also for LAV), the freeze report will also tell us what MPC (and LAV) are doing in the freeze situation. That information may help to figure out where the media player is stuck and maybe why.