madVR - high quality video renderer (GPU assisted)

[djfred93]

For a 720p video to a 1080p screen, NNEDI3 image doubling factor 2.0X isn't use, right ?

[truexfan81]

can someone please tell me what i am doing wrong here?


if (srcWidth <= 1919) and (srcHeight <= 1070) "Profile 3"
else if (srcFps<=30) and (!srcInterlaced) "Profile 1"
else "Profile 2"

also madshi looking in the profile settings and your example post i don't see the option for adding the deband filter to the profiles

the problem i am having is it will not go to Profile 3 unless i force it with a kb shortcut

[kerimcem]

chorme= NNEDI3(32) image= lancos3(ar)= sd blurry less sharpness(vob,mp4,avi files)
default settings (ar)= best
jin3(ar) jin3(ar)= best
chorme=bubic75ar image=c.room (ar) best
I did not like so NNEDI3 thanks...

[sneaker_ger]

Please try the test builds I posted a few posts above.

You mean the collection with 6 builds? All 6 of them share the problem.

[noee]

That's weird! I wish I could reproduce that here...

Well, this file I'm testing with is a bit different, M2TS container, VC-1 1080i, low bitrate (~11Mbps) and I am using DXVA2 for decoding (LAV->WMV9 DMO). I'll try copy-back mode to see if that makes any difference.

I've got some recent 480i material I can try out too...

[cyberbeing]

Why does every *** bug not occur on my PC? I'm getting a little bit frustrated right now...

:(

The only time it opens instantly here when I manually launch madHcCtrl.exe into the tray before attempting to access madVR settings offline.

If madHcCtrl.exe is not running, clicking "Edit Settings" launches madHcCtrl.exe without a tray icon, the delay for a few seconds occurs, madHcCtrl.exe closes, and finally the madVR settings gui appears.

[noee]

@madshi

I found it! I set LAV to copy-back mode instead of native DXVA and deint times are now the same as .86! Seems like a CPU thing, maybe since using DXVA for decode in this case, the CPU was stuck down at low-idle because there's simply no CPU load....?

[cca]

Regarding DXVA2 , I did notice that if used on my 5850 it will increase the rendering times regardless of the mode used (native/copy back). The explanation is simple, the GPU stays locked in a particular clock rate when DXVA2 is used and cannot raise to a higher clock state if the load demands it. I found this to be very evident when NNEDI is used, raises rendering time about 10ms.

Sent from my Nexus 7 using Tapatalk

[huhn]

Why does every *** bug not occur on my PC? I'm getting a little bit frustrated right now...

after some more testing on my gaming pc:
for the - creating Direct3d Device failed (80070005) error
this only happens when madvr change the refresh rate. it is not crashing when the refresh rate stays!

[madshi]

Hi madshi. In Windows XP, versions 0.87.0, 0.87.1, when you open any video - black screen. In version 0.86.11 - okay, all right. What is the reason?
Which GPU? Are you using default settings or any custom settings? Does it occur only when deinterlacing is used? Or also without?

Phew, that took a while. None of those comes close to 0.86.11 times unfortunately (scroll to see all):

Default Software:
Deinterlace: 18.99 ms
Split: 19.22 ms
Rendering: 8.19 ms
Present: 0.46 ms
Dropped Frames: 20
Delayed Frames: 0

Default DXVA2 Native:
Deinterlace: 14.63 ms
Split: 17.75 ms
Rendering: 8.16 ms
Present: 0.57 ms
Dropped Frames: 26
Delayed Frames: 2

No Crop Software:
Deinterlace: 19.82 ms
Split: 19.88 ms
Rendering: 9.81 ms
Present: 0.46 ms
Dropped Frames: 33
Delayed Frames: 1

No Crop DXVA2 Native:
Deinterlace: 11.21 ms
Split: 14.25 ms
Rendering: 6.97 ms
Present: 0.26 ms
Dropped Frames: 8
Delayed Frames: 1

No Shared Textures Software:
Deinterlace: 17.32 ms
Split: 18.44 ms
Rendering: 7.74 ms
Present: 0.44 ms
Dropped Frames: 7
Delayed Frames: 1

No Shared Textures DXVA2 Native:
Deinterlace: 11.69 ms
Split: 14.84 ms
Rendering: 6.77 ms
Present: 0.32 ms
Dropped Frames: 7
Delayed Frames: 1

DeintThread Setting Textures Software:
Deinterlace: 18.87 ms
Split: 18.92 ms
Rendering: 8.35 ms
Present: 0.42 ms
Dropped Frames: 18
Delayed Frames: 1

DeintThread Setting DXVA2 Native:
Deinterlace: 11.27 ms
Split: 14.76 ms
Rendering: 6.65 ms
Present: 0.28 ms
Dropped Frames: 8
Delayed Frames: 0

No Backbuffer+1 Software:
Deinterlace: 17.06 ms
Split: 17.18 ms
Rendering: 8.37 ms
Present: 0.56 ms
Dropped Frames: 16
Delayed Frames: 1

No Backbuffer+1 DXVA2 Native:
Deinterlace: 11.93 ms
Split: 14.89 ms
Rendering: 7.31 ms
Present: 0.28 ms
Dropped Frames: 11
Delayed Frames: 1

ConfigCopyback Software:
Deinterlace: 18.48 ms
Split: 18.91 ms
Rendering: 7.28 ms
Present: 0.37 ms
Dropped Frames: 21
Delayed Frames: 1

ConfigCopyback DXVA2 Native:
Deinterlace: 10.49 ms
Split: 14.27 ms
Rendering: 6.46 ms
Present: 0.25 ms
Dropped Frames: 8
Delayed Frames: 1


Repeated for reference:

0.86.11 Software:
Deinterlace: 8.29 ms
Split: 9.15 ms
Rendering: 4.70 ms
Present: 0.17 ms
Dropped Frames: 14
Delayed Frames: 0

0.86.11 DXVA2 Native:
Deinterlace: 7.58 ms
Split: 8.08 ms
Rendering: 5.02 ms
Present: 0.16 ms
Dropped Frames: 8
Delayed Frames: 0

EDIT: I found the issue. These slow rendering times only occur when Smooth Motion is enabled. Otherwise, 0.87.1 is fine in both decoding modes (although still a bit worse than 0.86.11), as shown here:

0.86.11 Software:
Deinterlace: 7.78 ms
Split: 8.97 ms
Rendering: 2.84 ms
Present: 0.15 ms
Dropped Frames: 8
Delayed Frames: 0

0.87.1 Software:
Deinterlace: 9.02 ms
Split: 11.64 ms
Rendering: 2.49 ms
Present: 0.14 ms
Dropped Frames: 12
Delayed Frames: 1
Hmmmm... Interesting. That was an Intel GPU? I have an Intel GPU here, too. But I can't seem to reproduce these problems. Maybe can you upload your settings.bin somewhere?

If it's any consolation, I don't seem to have any of these bugs either with my Radeon 5850. Debugging is such a nasty job...
It wouldn't be so bad if I could actually reproduce any of these bugs. But the ratio of bugs I can reproduce versus those I can't is shocking. Never had such a bad ratio yet. Never ever. I think I could reproduce 1-2 out of a hundred bugs reported since I released v0.87.0.

For a 720p video to a 1080p screen, NNEDI3 image doubling factor 2.0X isn't use, right ?
That depends on your image doubling settings.

can someone please tell me what i am doing wrong here?

if (srcWidth <= 1919) and (srcHeight <= 1070) "Profile 3"
else if (srcFps<=30) and (!srcInterlaced) "Profile 1"
else "Profile 2"

also madshi looking in the profile settings and your example post i don't see the option for adding the deband filter to the profiles

the problem i am having is it will not go to Profile 3 unless i force it with a kb shortcut
Looks alright to me. Are you actually testing with SD videos? Does the madVR debug OSD report that the source is really less than 1919 wide and less than 1070 high?

chorme= NNEDI3(32) image= lancos3(ar)= sd blurry(vob,mp4,avi files)
default settings (ar)= best
jin3(ar) jin3(ar)= best
chorme=bubic75ar image=c.room (ar) best
I did not like so NNEDI3 thanks...
Ok, that's fine. I guess it's a matter of taste.

You mean the collection with 6 builds? All 6 of them share the problem.
Ok, then please try disabling dithering completely and compare v0.87.1 that way with v0.86.11, both with dithering disabled. Does that change anything?

:(

The only time it opens instantly here when I manually launch madHcCtrl.exe into the tray before attempting to access madVR settings offline.

If madHcCtrl.exe is not running, clicking "Edit Settings" launches madHcCtrl.exe without a tray icon, the delay for a few seconds occurs, madHcCtrl.exe closes, and finally the madVR settings gui appears.
madHcCtrl is normally already started when you start video playback. Which tray icon settings are you using? Anyway, I tried them all and the problem still doesn't seem to occur on my PC.

@madshi

I found it! I set LAV to copy-back mode instead of native DXVA and deint times are now the same as .86! Seems like a CPU thing, maybe since using DXVA for decode in this case, the CPU was stuck down at low-idle because there's simply no CPU load....?
So are you saying that with copy-back there's no problem, but when using DXVA native decoding, v0.87.1 is slower than v0.86.11?

after some more testing on my gaming pc:
for the - creating Direct3d Device failed (80070005) error
this only happens when madvr change the refresh rate. it is not crashing when the refresh rate stays!
Can you give me step-by-step-guide to reproducing this bug? Which refresh rate modes to enter into the listing? Which refresh rate to manually select before starting video playback? Which madVR settings to use? Windowed mode or FSE mode? Etc etc. There are thousands of variations. Maybe I just need to do exactly the same thing as you. But so far I've not been able to reproduce the problem.

[michkrol]

can someone please tell me what i am doing wrong here?

if (srcWidth <= 1919) and (srcHeight <= 1070) "Profile 3"
else if (srcFps<=30) and (!srcInterlaced) "Profile 1"
else "Profile 2"

also madshi looking in the profile settings and your example post i don't see the option for adding the deband filter to the profiles

the problem i am having is it will not go to Profile 3 unless i force it with a kb shortcut

I don't see anything wrong there. FWIW my profiles work correctly with similar rules. Check what size madVR reports in OSD (CTRL+J).
As for the debanding profile, select "processing" on the left and click create profile group.

[shimaflarex]

You mean the collection with 6 builds? All 6 of them share the problem.

I have the same issue: image freezing when skipping to the next video file on FSE mode.
My GPU is an Intel HD 4000, driver 10.18.10.3345, Windows 8.1
I can "unfreeze" the image by pressing Ctrl+Alt+Del, and quitting the Windows Security screen with ESC.

[DragonQ]

Hmmmm... Interesting. That was an Intel GPU? I have an Intel GPU here, too. But I can't seem to reproduce these problems. Maybe can you upload your settings.bin somewhere?
Intel HD4000, driver 10.18.10.3379. Can't see a settings.bin file anywhere, how do I create it?

[Leader]

Which GPU? Are you using default settings or any custom settings? Does it occur only when deinterlacing is used? Or also without?

GPU - NVIDIA GeForce GT430.

I'm using the default settings. Have not changed anything, just unpack and set renderer, that is registered in the system and it all.

[James Freeman]

I have the same issue: image freezing when skipping to the next video file on FSE mode.

Moreover, when pressing Ctrl+C to close video, MPC-HC stuck at full screen with frozen image and I can't do anything to close it, only Ctrl+Alt+Del to close task.

[truexfan81]

if (srcWidth <= 1919) and (srcHeight <= 1070) "Profile 3"

thanks guys, it should have been >= for both of those lol

[madshi]

I have the same issue: image freezing when skipping to the next video file on FSE mode.
My GPU is an Intel HD 4000, driver 10.18.10.3345, Windows 8.1
I can "unfreeze" the image by pressing Ctrl+Alt+Del, and quitting the Windows Security screen with ESC.
I also have HD4000 and Windows 8.1. Why does the problem not occur on my PC? :( Can you upload your settings somewhere? Either look for a settings.bin in the madVR older. Or if there is none, export the registry key HKEY_CURRENT_USER\madshi\madVR.

Intel HD4000, driver 10.18.10.3379. Can't see a settings.bin file anywhere, how do I create it?
See above.

GPU - NVIDIA GeForce GT430.

I'm using the default settings. Have not changed anything, just unpack and set renderer, that is registered in the system and it all.
Not sure what's going on there. Anybody else still on XP with an NVidia GPU? Might make sense to wait until all the bugs are fixed. I'm not in a position to test on XP, anymore. Maybe fixing the other bugs will also fix the problem you're seeing.

Moreover, when pressing Ctrl+C to close video, MPC-HC stuck at full screen with frozen image and I can't do anything to close it, only Ctrl+Alt+Del to close task.
Not on my PC... :( Can you play with the settings to see if it might depend on them somehow? E.g. maybe it only occurs with Smooth Motion FRC enabled? Or only when switching refresh rates? Or only when using native or copyback DXVA decoding? Or only when using deinterlacing? Or something like that...

[huhn]

Can you give me step-by-step-guide to reproducing this bug? Which refresh rate modes to enter into the listing? Which refresh rate to manually select before starting video playback? Which madVR settings to use? Windowed mode or FSE mode? Etc etc. There are thousands of variations. Maybe I just need to do exactly the same thing as you. But so far I've not been able to reproduce the problem.
i reproduce this on two pc:

htpc my tv supports nearly all display modes between 23-60.

the display modes i use on my htpc are: 1080p23, 1080p24, 1080p50, 1080p59, 1080p60.

madvr is at total default settings mpc hc version is 1.7.1 from 20.1.2014
my display is normally at 60 fps.

i start a 1440x1080i60 transportstream

madvr switches to 1080p59

i press SHIFT + CONTROL + ALT + T

madvr switches to 1080p23 and gives a error.

this doesn't happen with the madvr options because for some reason it's not changing the refresh rate with the options.

on my gaming pc i do the same but with 60 hz 144 hz because my monitor can't do 23 and so on i think it's pretty hard to reproduce this a normal 60 hz monitor.

[noee]

So are you saying that with copy-back there's no problem, but when using DXVA native decoding, v0.87.1 is slower than v0.86.11?

All else being equal, yes that is exactly what I'm seeing here. For this 1080i VC1 video, with DXVA native deint is ~19ms and many dropped frames. With DXVA cb, deint is ~8ms (same as .86) and no drops.

I'm not so sure, however, that this is not related to my "platform". I'm starting a test now using another process to load the CPU/GPU while running DXVA native to see what happens...

[shimaflarex]

I also have HD4000 and Windows 8.1. Why does the problem not occur on my PC? :( Can you upload your settings somewhere? Either look for a settings.bin in the madVR older. Or if there is none, export the registry key HKEY_CURRENT_USER\madshi\madVR.

Here:
https://www.dropbox.com/s/6yts9i1bhq5oqck/settings.bin

[Thunderbolt8]

also got the FSE screen video switching bug, none of the test builds changed anything in that regard (24p movie on 60Hz screen, no dxva, deinterlacing, smoothmotion etc. just software decoding)

[DragonQ]

I also have HD4000 and Windows 8.1. Why does the problem not occur on my PC? :( Can you upload your settings somewhere? Either look for a settings.bin in the madVR older. Or if there is none, export the registry key HKEY_CURRENT_USER\madshi\madVR.

See above.
My settings are here (http://www.aotplaza.com/Files/HTPC/MadVR%20Settings.reg).

[iSunrise]

It wouldn't be so bad if I could actually reproduce any of these bugs. But the ratio of bugs I can reproduce versus those I can't is shocking. Never had such a bad ratio yet. Never ever. I think I could reproduce 1-2 out of a hundred bugs reported since I released v0.87.0.
There´s just a bigger mismatch now, because of different graphics card manufacturer and your new development platform, where you also have to take Intel drivers and OS (8.1 vs. 7) into account, too. Were you ever on AMD before? Because I remember you still have been using your NV 9400M for development until recently.

You also did quite a hefty release (to surprise us, which I like), but I guess the OpenCL features alone should have probably been beta-tested on AMD vs. NV before releasing them. That´s a problem that was almost a given and entirely not your fault per se.

Everyone that reports bugs should include their driver versions, especially when on an Intel HDxxxx. Because I always see people reporting problems, but they never mention their drivers.

We´re not in a rush, just a step at a time, I know this from experience.

[huhn]

he uses a amd hd 7770 atm

[dansrfe]

Could it be a difference in overlay vs windowed of rendering times on intel vs nvidia GPUs? I noticed a difference when Aero was enabled on Windows 7 before but it might not be related.

[aufkrawall]

So I did a clean install of Windows 7 (replaced Windows 8).
Everything is working fine now (no more dropped frames etc. during a short try), except that there is a problem with defining a custom resolution via Custom Resolution Utility.
I use it to force the display to stay at 75Hz. To do so set up a custom resolution and disable the checkbox "Include extension block" on Nvidia hardware.
In windowed mode now madVR reports 75Hz, but Windows still offers only 60Hz resolution. I don't know why this is that way, maybe oddness of Nvidia driver.
The problem is that madVR fails to enter FSE this way. The Nvidia Control Panels reports 75Hz only.
Could you please extend the refreshrate lookup so that madVR can also detect such custom resolutions, making FSE working?

Edit: Ok, Geforce Experience is causing this.

[leeperry]

Oh wow, :thanks: for the new builds!

NNEDI/Error Diffusion are working just fine on W7SP1 with a HD7850 and the latest drivers, it's just that the backbuffer queues never really fill completely when I have NNEDI enabled...yet GPU load barely reaches 60% and I'm not noticing any dropped frame.

I'm currently having troubles getting any kind of DXVA2(in LAV) to work in FS as when going from windowed to FSW(with the latest stable build of PotP) the picture is vertically stretched, then after a second the AR is applied and playback finally starts. OTOH with FSE, the backbuffer queues never fill and it's stuttering like hell. Need to run more tests I guess.

Either way, PQ is pretty dang astounding and it would appear that FSE isn't nearly as vital on W7 as it was on XP. I haven't gone through all previous pages yet but it seems that the backbuffer queues problem is being investigated.

[cyberbeing]

madHcCtrl is normally already started when you start video playback. Which tray icon settings are you using? Anyway, I tried them all and the problem still doesn't seem to occur on my PC.

Yes, and when you exit playback madHcCtrl is closed, as would be the normal case of accessing madVR settings outside of playback. My current tray icon setting is "show tray icon on local pc" and "Lan access" disabled.

I investigated with Sysinternals Process Monitor and the delay occurs right before/at the following, when accessing settings outside of playback (madHcCtrl.exe closed):

madHcCtrl.exe CreateFile C:\Program Files (x86)\madVR\settings.bin

[AngelGraves13]

I don't notice any difference with NNEDI on or off. What's the point of it?

Also, OpenCL still does not work on NVIDIA.

[huhn]

nnedi is opencl and read how it works it's not used on hd source.

it's only used when you upscale quiet a bit.
like FHD on UHD sceens or SD on FHD screens

[AngelGraves13]

nnedi is opencl and read how it works it's not used on hd source.

it's only used when you upscale quiet a bit.
like FHD on UHD sceens or SD on FHD screens

So it doesn't work on NVIDIA. Got it. Just freezes the image and goes black.

Doesn't NVIDIA support OpenCL same as AMD?

[huhn]

just have a look at the last pages. madshi is working hard to fix problems like that. it's working on old nvidia card but not on newer ones and he doesn't have a new nvidia gpu so he can't reproduce this problem. which make it really hard to fix.

ofc nvidia supports opencl but i would be surprised if this "support" is not that good. i think nvidia is more focused on cuda but it's just a guess :-)

[Mangix]

What's weird is that SVP, FLACCL, and oclHashcat all work just fine with the latest drivers. If madVR's OpenCL stuff is not working then it must be some feature that's failing.

[Soukyuu]

As madshi mentioned, it's the directX <-> openCL interop that is making troubles, not openCL itself.

[AngelGraves13]

just have a look at the last pages. madshi is working hard to fix problems like that. it's working on old nvidia card but not on newer ones and he doesn't have a new nvidia gpu so he can't reproduce this problem. which make it really hard to fix.

ofc nvidia supports opencl but i would be surprised if this "support" is not that good. i think nvidia is more focused on cuda but it's just a guess :-)

I did...just says it doesn't work yet.

[huhn]

these programs use cpu -> opencl -> cpu

madvr uses direct x -> opencl -> direct x

this wasn't supported for a long time on amd.

[romulous]

Apologies if this is already a known issue, but video playback fails with all 0.87.x versions so far when I enter fullscreen mode on a second display (not using any of the new features of 0.87.x, and FSE mode disabled). Returning to 0.86.11 makes it work again.

So, install 0.87.x over the top of 0.86.11. Open video player (windowed mode on first display), file-->open to open a video file, player enters fullscreen mode on display two, video does not play. Un-fullscreen video player back to first display, video still does not play (though it will play if I simply leave the player in windowed mode to start with). Uninstall 0.87.x, reinstall 0.86.11, all works again.

Just to be clear - it isn't moving from one video file to another in FSE mode that a few people have reported. It's just simply opening a single video file into a fullscreen window to begin with.

Edit: I should have mentioned - fullscreen the player to the primary display is fine, it is only when I go fullscreen on another display. The video plays in windowed mode, enter fullscreen, the video pauses and the player suddenly hits 100% CPU. I return to windowed mode, playback is still frozen and player is still at 100% CPU.

[cyberbeing]

Is it expected for OpenCL dither to increase madVR CPU load significantly when scaling? GPU load also seems to change a lot, depending on output size. Are you dithering after resize rather than prior? It would also seem that GPU load exactly doubles if you enable Smooth Motion on top of OpenCL dither, which I find a bit strange.

720p -> 720p OpenCL dither = 3.72% madVR.ax CPU load | GPU load 10%
720p -> 720p OpenCL dither disabled = ~1.28% madVR.ax CPU load | GPU load 5%

720p -> 360p OpenCL dither = 3.31% madVR.ax CPU load | GPU load 8%
720p -> 360p OpenCL dither disabled = ~1.28% madVR.ax CPU load | GPU load 5%

720p -> 1080p OpenCL dither = 6.68% madVR.ax CPU load | GPU load 22%
720p -> 1080p OpenCL dither disabled = ~1.28% madVR.ax CPU load | GPU load 8%

1080p -> 1080p OpenCL dither = 8.03% madVR.ax CPU load | GPU load 25%
1080P -> 1080p OpenCL dither disabled = ~1.28% madVR.ax CPU load | GPU load 10%

1080P -> 540p OpenCL dither = 5.23% madVR.ax CPU load | GPU load 13%
1080P -> 540p OpenCL dither disabled = ~1.28% madVR.ax CPU load | GPU load 10%

360p -> 360p OpenCL dither + Smooth Motion = 3.7% madVR.ax CPU load | GPU load 10%
360p -> 360p OpenCL dither disabled + Smooth Motion = ~1.28% madVR.ax CPU load | GPU load 3%

360p -> 1080p OpenCL dither + Smooth Motion = 12.47% madVR.ax CPU load | GPU load 45%
360p -> 1080p OpenCL dither disabled + Smooth Motion = ~1.28% madVR.ax CPU load | GPU load 12%

360p -> 1080p OpenCL dither = 12.47% madVR.ax CPU load | GPU load 22%
360p -> 1080p OpenCL dither disabled = ~1.28% madVR.ax CPU load | GPU load 8%

...or is this behavior yet another NVIDIA OpenCL quirk?

GTX 770, 321.10 driver, Win7 SP1 x64, madVR 0.87.1

[drew_afx]

MadVR also using CPU as openCL device for dithering?
Honestly, seeing even high end AMD GPUs are now being utilized to 60% with these new features, getting some CPU usage is a good thing, IMHO. Especially for future APUs and integrated graphics, it might be able to use higher settings which is impossible atm.

[JarrettH]

Maybe I don't understand this correctly, but with NNEDI, what are the chances of upscaling a video by precisely 2x? Does that mean your video would need to be half of the 1920 pixel width (960) to work?

[fairchild]

Hopefully at some point someone can explain how to setup a profile+script to use NNEDI to say just do less than 720p content (not sure if it benefits 720p to 1080p) to get max image quality. I guess the purpose of NNEDI is to get even more quality out of your image/chroma scaling when going from say a DVD which is at 720x480 to a 1920x1080 screen.

Edit: kinda figured it out a bit, for lower res media, then can use the following options which bypasses using NNEDI for 720p and up content. (since difference is probably sooooo minute anyway)

use NNEDI3 to double luma if scaling 2.0x 64 neurons (bypasses 720p)
use NNEDI3 to quadruple luma if scaling is 3.0x 16 neurons

I played with the neurons options and it seems to definitely increase load/rendering times, but not sure if there is much of a visible difference from defaults which are 64 for double and 16 for quadruple. Left the chroma NNEDI3 options disabled.

[ThurstonX]

Maybe I don't understand this correctly, but with NNEDI, what are the chances of upscaling a video by precisely 2x? Does that mean your video would need to be half of the 1920 pixel width (960) to work?

If I understand it correctly, nnedi will double a small video, then whatever scaling method you've selected will take that and stretch it to the target rectangle size. That's just from reading along the past few pages.

If you double past the target size, then the downscaling method will kick in.

I'm sure someone who understands it better will correct that, or elaborate, as needed.

[oddball]

OpenCL dither = blank screen
NNED13 enabled anywhere = blank screen

Nvidia GTX560Ti latest drivers. Latest nightly build MPC-HC x86 internal filters only.

Am I doing something wrong?

[dansrfe]

madshi,

You've said that you recommend we select a "cheap" upscaler algorithm such as Lanczos3 AR when NNEDI3 is selected. What happens when NNEDI3 is not in use and only Lanczos3 AR is used to upscale Luma? In that case wouldn't you recommend it switches to another algorithm, such as Jinc3 AR, automatically?

[QBhd]

I wanted to say again... everything is great with 87.1... I had found a bug lastnight with 87.0 (it had been reported and I was going to confirm it, but I was too tired).... but is is now solved. Profiles were being selected, proved by the highlighted profile in settings while running (very nice touch by the way!!) however they were not actually running. Now all is fixed, awesome work madshi

[Shiandow]

OpenCL dither = blank screen
NNED13 enabled anywhere = blank screen

Nvidia GTX560Ti latest drivers. Latest nightly build MPC-HC x86 internal filters only.

Am I doing something wrong?

Unfortunately that is normal behaviour for Nvidia cards. If you switch back to an older driver (327.26 or earlier I think) then you might be able to get OpenCL dithering to work, but that's about it. It's probably best to wait until it becomes clear why this happens.

[ryrynz]

madVR v0.87.0 released
I had to do some minor compromises to implement this on a GPU with decent performance, so quality might be ever so slightly lower than when doing error diffusion sequentially via CPU, but I think it's not too bad.

Because of the GPU performance requirement for error diffusion and the slight improvement in quality with it being done on the CPU, what's the chances of this ever being an option that could be enabled on the CPU in MadVR?

[nevcairiel]

Is it expected for OpenCL dither to increase madVR CPU load significantly when scaling? GPU load also seems to change a lot, depending on output size. Are you dithering after resize rather than prior? It would also seem that GPU load exactly doubles if you enable Smooth Motion on top of OpenCL dither, which I find a bit strange.

Dithering should be one of the very last steps in rendering, after scaling, after smoothmotion.

Dithering reduces the bitdepth of the image, so doing it any earlier defeats its purpose.


You've said that you recommend we select a "cheap" upscaler algorithm such as Lanczos3 AR when NNEDI3 is selected. What happens when NNEDI3 is not in use and only Lanczos3 AR is used to upscale Luma? In that case wouldn't you recommend it switches to another algorithm, such as Jinc3 AR, automatically?

Thats what profiles are for. :)

[huhn]

found a new bug very easy to trigger:

use default madvr settings with 87.1
start a file
change the refresh rate in windows
playback only works in fullscreen now

most likely related to the video-film mode refresh rate bug

i got direct3d failed errors in fullscreen when control + j is used

-resetting direct3d device failed (80070005)
-creating direct3d device failed (80070005)

i can't catch these with a screen shoot sorry.

everything is default so it uses exclusive fullscreen.

[truexfan81]

I have to say i love this profile stuff. :D

Profiles for Scaling, profiles for deband/deinterlace.
Now i can watch any file i want to without having to ever manually change settings.

madshi thank you so much :-)