View Full Version : madVR - high quality video renderer (GPU assisted)
mzso
25th March 2019, 23:05
As far as I can tell, FFmpeg/LAV supports those "T2" ones fine, only "Pro" formats are not supported (10-bit).
Not my experience. FFmpeg/ffplay can't use them ("Invalid data found when processing input") . Also I get a black screen during playback in media players with LAV.
MPC-BE internal filter also gives black screen. MPV gives a spam of "Error while decoding frame!" errors.
el Filou
25th March 2019, 23:34
I kind of borked the comment, but the problem is with the official codecs, not LAV video. Can you check in MPC's 'pin info' tab in the filter properties, the format (and other info) that the official decoder outputs, and compare it to what LAV outputs?
nevcairiel
25th March 2019, 23:42
Not my experience. FFmpeg/ffplay can't use them ("Invalid data found when processing input") . Also I get a black screen during playback in media players with LAV.
MPC-BE internal filter also gives black screen. MPV gives a spam of "Error while decoding frame!" errors.
All I know is that the video in your zip plays fine. Perhaps your earlier videos were somehow corrupt.
mzso
26th March 2019, 00:51
All I know is that the video in your zip plays fine. Perhaps your earlier videos were somehow corrupt.
Well, those are the very ones I tried, and the t2 one doesn't work with LAV and the others.
Can you check in MPC's 'pin info' tab in the filter properties, the format (and other info) that the official decoder outputs, and compare it to what LAV outputs?
Well, I don't know what specifically are you looking for, here's everything:
Filter : UMRG Decoder DMO - CLSID : {94297043-BD82-4DFD-B0DE-8177739C6D20}
- Connected to:
CLSID: {E1A8B82A-32CE-4B0D-BE0D-AA68C772E423}
Filter: madVR
Pin: Input
- Connection media type:
Video: RGB24 1600x1200 59.999fps
AM_MEDIA_TYPE:
majortype: MEDIATYPE_Video {73646976-0000-0010-8000-00AA00389B71}
subtype: MEDIASUBTYPE_RGB24 {E436EB7D-524F-11CE-9F53-0020AF0BA770}
formattype: FORMAT_VideoInfo {05589F80-C356-11CE-BF01-00AA0055595A}
bFixedSizeSamples: 1
bTemporalCompression: 0
lSampleSize: 0
cbFormat: 88
VIDEOINFOHEADER:
rcSource: (0,0)-(1600,1200)
rcTarget: (0,0)-(1600,1200)
dwBitRate: 0
dwBitErrorRate: 0
AvgTimePerFrame: 166670
BITMAPINFOHEADER:
biSize: 40
biWidth: 1600
biHeight: 1200
biPlanes: 1
biBitCount: 24
biCompression: 0
biSizeImage: 5760000
biXPelsPerMeter: 0
biYPelsPerMeter: 0
biClrUsed: 0
biClrImportant: 0
pbFormat:
0000: 00 00 00 00 00 00 00 00 40 06 00 00 b0 04 00 00 ........@...°...
0010: 00 00 00 00 00 00 00 00 40 06 00 00 b0 04 00 00 ........@...°...
0020: 00 00 00 00 00 00 00 00 0e 8b 02 00 00 00 00 00 .........‹......
0030: 28 00 00 00 40 06 00 00 b0 04 00 00 01 00 18 00 (...@...°.......
0040: 00 00 00 00 00 e4 57 00 00 00 00 00 00 00 00 00 .....äW.........
0050: 00 00 00 00 00 00 00 00 ........
- Enumerated media type 0:
Set as the current media type
- Enumerated media type 1:
Video: RGB32 1600x1200 59.999fps
AM_MEDIA_TYPE:
majortype: MEDIATYPE_Video {73646976-0000-0010-8000-00AA00389B71}
subtype: MEDIASUBTYPE_RGB32 {E436EB7E-524F-11CE-9F53-0020AF0BA770}
formattype: FORMAT_VideoInfo {05589F80-C356-11CE-BF01-00AA0055595A}
bFixedSizeSamples: 1
bTemporalCompression: 0
lSampleSize: 0
cbFormat: 88
VIDEOINFOHEADER:
rcSource: (0,0)-(1600,1200)
rcTarget: (0,0)-(1600,1200)
dwBitRate: 0
dwBitErrorRate: 0
AvgTimePerFrame: 166670
BITMAPINFOHEADER:
biSize: 40
biWidth: 1600
biHeight: 1200
biPlanes: 1
biBitCount: 32
biCompression: 0
biSizeImage: 7680000
biXPelsPerMeter: 0
biYPelsPerMeter: 0
biClrUsed: 0
biClrImportant: 0
pbFormat:
0000: 00 00 00 00 00 00 00 00 40 06 00 00 b0 04 00 00 ........@...°...
0010: 00 00 00 00 00 00 00 00 40 06 00 00 b0 04 00 00 ........@...°...
0020: 00 00 00 00 00 00 00 00 0e 8b 02 00 00 00 00 00 .........‹......
0030: 28 00 00 00 40 06 00 00 b0 04 00 00 01 00 20 00 (...@...°..... .
0040: 00 00 00 00 00 30 75 00 00 00 00 00 00 00 00 00 .....0u.........
0050: 00 00 00 00 00 00 00 00 ........
Filter : ULH4 Decoder DMO - CLSID : {94297043-BD82-4DFD-B0DE-8177739C6D20}
- Connected to:
CLSID: {E1A8B82A-32CE-4B0D-BE0D-AA68C772E423}
Filter: madVR
Pin: Input
- Connection media type:
Video: YV24 1600x1200 59.999fps
AM_MEDIA_TYPE:
majortype: MEDIATYPE_Video {73646976-0000-0010-8000-00AA00389B71}
subtype: Unknown GUID Name {34325659-0000-0010-8000-00AA00389B71}
formattype: FORMAT_VideoInfo {05589F80-C356-11CE-BF01-00AA0055595A}
bFixedSizeSamples: 1
bTemporalCompression: 0
lSampleSize: 0
cbFormat: 88
VIDEOINFOHEADER:
rcSource: (0,0)-(1600,1200)
rcTarget: (0,0)-(1600,1200)
dwBitRate: 0
dwBitErrorRate: 0
AvgTimePerFrame: 166670
BITMAPINFOHEADER:
biSize: 40
biWidth: 1600
biHeight: 1200
biPlanes: 1
biBitCount: 24
biCompression: YV24
biSizeImage: 5760000
biXPelsPerMeter: 0
biYPelsPerMeter: 0
biClrUsed: 0
biClrImportant: 0
pbFormat:
0000: 00 00 00 00 00 00 00 00 40 06 00 00 b0 04 00 00 ........@...°...
0010: 00 00 00 00 00 00 00 00 40 06 00 00 b0 04 00 00 ........@...°...
0020: 00 00 00 00 00 00 00 00 0e 8b 02 00 00 00 00 00 .........‹......
0030: 28 00 00 00 40 06 00 00 b0 04 00 00 01 00 18 00 (...@...°.......
0040: 59 56 32 34 00 e4 57 00 00 00 00 00 00 00 00 00 YV24.äW.........
0050: 00 00 00 00 00 00 00 00 ........
- Enumerated media type 0:
Set as the current media type
- Enumerated media type 1:
Video: RGB24 1600x1200 59.999fps
AM_MEDIA_TYPE:
majortype: MEDIATYPE_Video {73646976-0000-0010-8000-00AA00389B71}
subtype: MEDIASUBTYPE_RGB24 {E436EB7D-524F-11CE-9F53-0020AF0BA770}
formattype: FORMAT_VideoInfo {05589F80-C356-11CE-BF01-00AA0055595A}
bFixedSizeSamples: 1
bTemporalCompression: 0
lSampleSize: 0
cbFormat: 88
VIDEOINFOHEADER:
rcSource: (0,0)-(1600,1200)
rcTarget: (0,0)-(1600,1200)
dwBitRate: 0
dwBitErrorRate: 0
AvgTimePerFrame: 166670
BITMAPINFOHEADER:
biSize: 40
biWidth: 1600
biHeight: 1200
biPlanes: 1
biBitCount: 24
biCompression: 0
biSizeImage: 5760000
biXPelsPerMeter: 0
biYPelsPerMeter: 0
biClrUsed: 0
biClrImportant: 0
pbFormat:
0000: 00 00 00 00 00 00 00 00 40 06 00 00 b0 04 00 00 ........@...°...
0010: 00 00 00 00 00 00 00 00 40 06 00 00 b0 04 00 00 ........@...°...
0020: 00 00 00 00 00 00 00 00 0e 8b 02 00 00 00 00 00 .........‹......
0030: 28 00 00 00 40 06 00 00 b0 04 00 00 01 00 18 00 (...@...°.......
0040: 00 00 00 00 00 e4 57 00 00 00 00 00 00 00 00 00 .....äW.........
0050: 00 00 00 00 00 00 00 00 ........
- Enumerated media type 2:
Video: RGB32 1600x1200 59.999fps
AM_MEDIA_TYPE:
majortype: MEDIATYPE_Video {73646976-0000-0010-8000-00AA00389B71}
subtype: MEDIASUBTYPE_RGB32 {E436EB7E-524F-11CE-9F53-0020AF0BA770}
formattype: FORMAT_VideoInfo {05589F80-C356-11CE-BF01-00AA0055595A}
bFixedSizeSamples: 1
bTemporalCompression: 0
lSampleSize: 0
cbFormat: 88
VIDEOINFOHEADER:
rcSource: (0,0)-(1600,1200)
rcTarget: (0,0)-(1600,1200)
dwBitRate: 0
dwBitErrorRate: 0
AvgTimePerFrame: 166670
BITMAPINFOHEADER:
biSize: 40
biWidth: 1600
biHeight: 1200
biPlanes: 1
biBitCount: 32
biCompression: 0
biSizeImage: 7680000
biXPelsPerMeter: 0
biYPelsPerMeter: 0
biClrUsed: 0
biClrImportant: 0
pbFormat:
0000: 00 00 00 00 00 00 00 00 40 06 00 00 b0 04 00 00 ........@...°...
0010: 00 00 00 00 00 00 00 00 40 06 00 00 b0 04 00 00 ........@...°...
0020: 00 00 00 00 00 00 00 00 0e 8b 02 00 00 00 00 00 .........‹......
0030: 28 00 00 00 40 06 00 00 b0 04 00 00 01 00 20 00 (...@...°..... .
0040: 00 00 00 00 00 30 75 00 00 00 00 00 00 00 00 00 .....0u.........
0050: 00 00 00 00 00 00 00 00 ........
huhn
26th March 2019, 01:26
so on my system:
ut-teszt-t2 = RGB sample
RGB sample:
on my system the RGB sample can't be send into EVR directly if the native decoder UMRG decoder dmo is used it needs a color space converter or MPC hc will fallback to "video renderer" i didn't even know that there could be a fallback renderer.
lavfilter with either madVR or EVR gave me a black screen if 64 BIT is used it work fine for both on 32 bit.
if lavfilter is blocked the first decoder for this file my system is going to use is AVI Decompressor (UMRG) no colorspace converter nothing works totally fine.
so the odd things here on my system are the native decoder needing a color space converter and lav filter as decoder giving a black screen on 64 bit.
BTW. lav splitter -> prefer UMRG de... -> prefer colorspace converter -> madVR works.
at least to me it looks like UMRG decoder is kind of picky with the need of the color space converter.
amayra
26th March 2019, 01:31
i read last week about "Vulkan Working To Expose Video Encode/Decode (https://www.phoronix.com/scan.php?page=news_item&px=Vulkan-GDC-2019-Highlights)" is this can be any useful to madvr if madshi or nevcairiel add it to lav if they add vulkan support ?
nevcairiel
26th March 2019, 01:57
lavfilter with either madVR or EVR gave me a black screen if 64 BIT is used it work fine for both on 32 bit.
I can confirm that. Should make it easy to find and fix it.
mzso
26th March 2019, 02:52
if lavfilter is blocked the first decoder for this file my system is going to use is AVI Decompressor (UMRG) no colorspace converter nothing works totally fine.
I can't follow this line. Where does the "AVI Decompressor (UMRG)" filter come from? I have it but it's not loaded by default. To me it also loads a colorspace converter for EVR.
So you mean that with this unidentified filter it works without a colorspace converter for you?
It works for me too with madVR if I add the colorspace filter as well.
huhn
26th March 2019, 03:23
of cause you have it: https://docs.microsoft.com/en-us/windows/desktop/directshow/avi-decompressor-filter
this works fine for me and this is what happens on my system with disabled internal filter and lavfilter blocked but no preferred filter.
Filters currently loaded:
- Default DirectSound Device
- madVR
- Audio Switcher
- AVI Decompressor (UMRG)
- LAV Splitter (internal) (low merit)
- File Source (Async.)
i have quite a lot of dshow filter installed for testing but in this case it doesn't use anything special.
that the UMRG decoder dmo needs a colorspace converter is odd to me. of cause you could argue if madVR can't handle the stream the color space converter should be loaded like it is with EVR.
i have no clue who is responsible for loader these "in between filter" but i'm sure we both can both agree it would be great if the UMRG decoder dmo doesn't need this color space filter and that the output of the decoder can be rendered directly.
jmone
26th March 2019, 09:09
Has any one got a stutter free playback on a RTX without using Exclusive Mode?
I just upgraded from a 1070 to 2070 to get some more headroom with the HDR processing being worked on, but I too get stutters every second (queues are fine, no dropped/repeated frames reported) in Windowed Mode but it is fine in Exclusive Mode. I'd much rather not use Exclusive Mode as with the long sync times on my JVC PJ it gets pretty irritating.
Thanks
Nathan
chros
26th March 2019, 10:22
Has any one got a stutter free playback on a RTX without using Exclusive Mode?
You can give this trick (https://www.avsforum.com/forum/26-home-theater-computers/2364113-guide-building-4k-htpc-madvr-81.html#post57758796) a try, maybe ...
Nicog
26th March 2019, 10:50
You can give this trick (https://www.avsforum.com/forum/26-home-theater-computers/2364113-guide-building-4k-htpc-madvr-81.html#post57758796) a try, maybe ...
I have same issue than you jmone (very painful with JVC Projector in HDR in FSE).
This tip, chros, I tried it also (vertical sync -> Fast + window overlay) : it has effectively killed the stuttering, but at the price of horrible tearings in the picture. Maybe some solutions exists to kills that, but I didn't found it.
huhn
26th March 2019, 11:08
the image is "bad" you are not supposed to use fast you are supposed to use on.
fast sync disables vsync until the frame rate is higher then the display rate this is not going to happen and makes no sense for video playback.
Nicog
26th March 2019, 11:15
the image is "bad" you are not supposed to use fast you are supposed to use on.
fast sync disables vsync until the frame rate is higher then the display rate this is not going to happen and makes no sense for video playback.
Thanks for info.
I tried at first "on" but it was without effect. Maybe I had to restart madvr. I'll try again...
jmone
26th March 2019, 12:12
I'll also test when back in a few days. I also have the Zotac Mini, and MC25 with a beta build of madVR
cremor
26th March 2019, 15:56
Has any one got a stutter free playback on a RTX without using Exclusive Mode?
Yes, I have no problems in windowed or full screen windowed using a RTX 2070.
When I had problems, it was either because of the already mentioned vsync setting (resetting it to the default value fixed it for me) or because of G-Sync. I solved the G-Sync problem by forcing it off via NVidia Inspector.
Z'Hadum
26th March 2019, 21:37
Hello everybody,
sorry for this stupid question:
Is it possible to pass any of the madvr variables to a batch file through the
"command line to execute when this profile is activated" field?
What would be the syntax?
Some thing like
mySimpleBatch.bat %croppedSrcHeight% %croppedSrcWidth% %fps%
So I can use this variables in the Batch file with %1 %2 %3 ....
:thanks:
JonnyRedHed
27th March 2019, 02:16
Maybe given the age and performance of your card you're the first one to notice an issue with this setting.. create the log and pass it to madshi over at http://bugs.madshi.net
Thanks, I'll look into that. Although I'm not very good at this sort of thing.
Nicog
27th March 2019, 08:12
the image is "bad" you are not supposed to use fast you are supposed to use on.
fast sync disables vsync until the frame rate is higher then the display rate this is not going to happen and makes no sense for video playback.
It seems it works! I tried jsut few minutes, on my favourite test movie, and that looks OK!
Many many thanks to all of you!
chros
27th March 2019, 15:34
I just opened a new thread: Which display for MadVR only? (https://forum.doom9.org/showthread.php?t=176233)
ryrynz
27th March 2019, 21:45
Is it possible to pass any of the madvr variables to a batch file
Nope.
jmone
28th March 2019, 09:06
Thanks! Changing VSYNC to "ON" fixed the issue on my RTX2070. Windowed Mode now works perfectly!
https://cdn.wccftech.com/wp-content/uploads/2018/10/FastSync.png
jmone
28th March 2019, 09:39
...and using the same madVR tweaked custom settings I posted earlier still works in giving me hours of no dropped/repeated frames with my X7500 PJ.
nghiabeo20
28th March 2019, 09:54
Sorry, I'm late. Could anyone please confirm that the new Envy is a hardware? I thought it would be a complete rewrite for madVR!
huhn
28th March 2019, 10:23
go to the link that'S all available informations.
madjock
28th March 2019, 11:30
go to the link that'S all available informations.
Why do you use capital letters after an apostrophe, this concerns me more than Envy specs. :)
ryrynz
28th March 2019, 11:42
English isn't his first language. Envy is OT, search the thread if anyone has questions.
curael
28th March 2019, 11:54
Hi MadVR folks!
Alright so, I just got done upgrading my rig. I did a brand new 1809 Win10 install, added my old RTX 2080, seated a 9600K i5 and 16 gigs of ram.
I then copied over my AppData folder for Kodi after installing the latest Kodi DSplayer installer.. And all settings are intact. How ever, I am getting insane stuttering in all my videos. No dropped frames, no repeated frames.. Just.. Stuttering! Like every 3rd second, the video stutters hard. And I can't see any indication of what does it. I'm on the newest NVIDIA driver so I suppose I could try rolling back to the previous one, which was what I ran on the old rig. Here's what I've tried so far from traversing this thread and the Kodi DSPlayer thread over at Kodi.tv:
I've taken off "Focus Assist" in Windows.
I've disabled the Game Bar in Windows.
I've set Exclusive Mode, which fixed it on my old rig with the RTX 2080.. - Then was suggested windowed mode with v-sync, still didn't work.
I've tried copy-back, D11.
Disabled DPI scaling for Kodi.exe just to be sure..
Disabled the "in-game overlay" from NVIDIA Experience.
CTRL + J reports everything fine and as it's always looked in MadVR. 20ms render time, no dropped ques or dropped frames.. Correct Hz on display and correct fps.. I still get judder.
I am honestly at a loss and it's SO annoying that a new build is actually performing worse than my 8 year old 3570K i5 build. I used to have no stuttering on the RTX 2080 as long as I enabled Fullscreen Exclusive, how ever, this is not doing it this time..
Any suggestions friends? Off the top of your head ofc. Anything you guys have tried that made it work?
/CuraeL
madjock
28th March 2019, 11:58
so I suppose I could try rolling back to the previous one
Surely worth a try now ?
ryrynz
28th March 2019, 12:45
I suppose I could try rolling back to the previous one
Why are you posting when you haven't even tried that? You could've done that in the time it took you to write that post :P
curael
28th March 2019, 12:45
Surely worth a try now ?
Certainly! Will do when I get back from the office later on. I was just trying to pick your brains for other possible solutions.
I will report back!
Why are you posting when you haven't even tried that? You could've done that in the time it took you to write that post :P
Thanks for your very helpful post. :) I will try it when I get home. I was trying to save some time by telling you guys what I have already done last night to combat the issue. I simply don't think rolling back will work as I'd assume most other RTX users on here are on the latest driver. So it wasn't the first thing I did. I configured Win10 and Kodi instead to see if I could fix the issue that way. There is of course the possibility that the current driver is the culprit, but I just can't deduct that from the current state of this thread in regards to RTX.
I'll get back to you. :)
/CuraeL
ryrynz
28th March 2019, 12:47
Test with another media player as well. Given what you've changed already I'm not sure anyone is going to know what's causing it..
I think you got some good troubleshooting ahead of you.
curael
28th March 2019, 12:50
Test with another media player as well. Given what you've changed already I'm not sure anyone is going to know what's causing it..
I think you got some good troubleshooting ahead of you.
I was afraid you'd say that. :D I'm gonna install MPC-BE when I get home and set up another set of LAV filters and see what happens. God I hate madVR when things go south. But I love it so much once it's actually stable on the build. :D I wouldn't want to live without it.
I'll surely troubleshoot. ^^,
Thanks again!
TheProfosist
28th March 2019, 13:20
https://miku.hatsune.my/potplayer-with-seeking-gui-in-madvr-exclusive-mode.jpg Screenshot from google. Try tick\untick some checkboxes from general settings section. Or if you on Win10 just use windowed mode and dont care about it.
which settings would even matter?
also is exclusive mode in Win10 known to be an issue?
Nicog
28th March 2019, 13:53
Hi MadVR folks!
Alright so, I just got done upgrading my rig. I did a brand new 1809 Win10 install, added my old RTX 2080, seated a 9600K i5 and 16 gigs of ram.
I then copied over my AppData folder for Kodi after installing the latest Kodi DSplayer installer.. And all settings are intact. How ever, I am getting insane stuttering in all my videos. No dropped frames, no repeated frames.. Just.. Stuttering! Like every 3rd second, the video stutters hard. And I can't see any indication of what does it. I'm on the newest NVIDIA driver so I suppose I could try rolling back to the previous one, which was what I ran on the old rig. Here's what I've tried so far from traversing this thread and the Kodi DSPlayer thread over at Kodi.tv:
I've taken off "Focus Assist" in Windows.
I've disabled the Game Bar in Windows.
I've set Exclusive Mode, which fixed it on my old rig with the RTX 2080.. - Then was suggested windowed mode with v-sync, still didn't work.
I've tried copy-back, D11.
Disabled DPI scaling for Kodi.exe just to be sure..
Disabled the "in-game overlay" from NVIDIA Experience.
CTRL + J reports everything fine and as it's always looked in MadVR. 20ms render time, no dropped ques or dropped frames.. Correct Hz on display and correct fps.. I still get judder.
I am honestly at a loss and it's SO annoying that a new build is actually performing worse than my 8 year old 3570K i5 build. I used to have no stuttering on the RTX 2080 as long as I enabled Fullscreen Exclusive, how ever, this is not doing it this time..
Any suggestions friends? Off the top of your head ofc. Anything you guys have tried that made it work?
/CuraeL
For me with the 2 lasts drivers I have stuttering (419.67 / 419.35). The previous one from end of Feb is OK (417.xx).
TheProfosist
28th March 2019, 15:28
alright so I have made some progress I started by uninstalling, reinstalling, and reseting MPC-HC and madVR.
The stuttering has mostly been fixed I just get a little blip every now and then say every couple minutes at most. some time during fast actions or pans. I'm not using smooth motion just matching frame rate could this be buffer related? This seems more frequent than the 1 stutter every 4min or so that the madVR UI is suggesting.
I did fix exclusive mode as well.
both the stuttering and exclusive mode seem to have been related to having HDR enabled in Win10 at an OS level.
I have not yet tweaked scaling algorithms or anything like that yet. Just on default settings.
When playing back 4K HDR BD content I'm still getting stuttering on pans that should be smooth. This is with HDR turned off at the OS level and HDR set to pass through. Colors look very muted So I don't think it is actually doing HDR with this setup.
So its looking like most of my issues have been related to HDR.
TheProfosist
28th March 2019, 15:50
I have same issue than you jmone (very painful with JVC Projector in HDR in FSE).
This tip, chros, I tried it also (vertical sync -> Fast + window overlay) : it has effectively killed the stuttering, but at the price of horrible tearings in the picture. Maybe some solutions exists to kills that, but I didn't found it.
looking like more HDR related issues then...
That setting was supposed to be flipped to on
I tried forced V-Sync with HDR content with HDR enabled at the OS level and still stuttered. I forced Vsync to On for MPC-HC as well as my madVR folder.
With these forced on and OS HDR disabled the playback is much less stutters but it is still stuttery and the colors are all muted so The display either sint getting HDR or doesn't know it is.
This testing was done playing back 4K HDR BD Content
curael
28th March 2019, 16:38
For me with the 2 lasts drivers I have stuttering (419.67 / 419.35). The previous one from end of Feb is OK (417.xx).
Hell yee boiiii. 418.XX from the 13th of February is stutter free along with Fullscreen Exclusive!
GeForce Game Ready Driver WHQL 418.91 February 13, 2019
Wooooohoooo we back! That smooth smooth playback.
Love ya'll! Thanks so much. To think a new driver once again broke stuff. My gosh.
Klaus1189
28th March 2019, 17:57
Hi,
I don't have a Nvidia RTX but I am collecting driver related stuff here:
AMD, Intel and Nvidia driver issues and last recommended version (https://forum.doom9.org/showthread.php?t=176013)
What driver exactly is the last one without stutters, so I can add this info for other RTX users.
See in the thread for the complete list of the drivers and its release date.
curael
28th March 2019, 18:17
Hi,
I don't have a Nvidia RTX but I am collecting driver related stuff here:
AMD, Intel and Nvidia driver issues and last recommended version (https://forum.doom9.org/showthread.php?t=176013)
What driver exactly is the last one without stutters, so I can add this info for other RTX users.
See in the thread for the complete list of the drivers and its release date.
This was the one I just installed. And I left out the first x19.xx cause I felt like 18 would be a better bet, from what I was advised in the previous post. (17.xx) Sorry, I'm not about to scuff my installation again by installing newer drivers. All I can say is that I'm on the 3rd latest driver and it works as expected for MadVR. Anything 19 is now something I'll stay away from. Madshi or NVIDIA will have to optimize. Given Madshi haven't released for a good while now, I reckon it'd have to be NVIDIA. Fat chance.
Klaus1189
28th March 2019, 18:53
I just updated that info here:
https://forum.doom9.org/showthread.php?t=176013
419.67 GRD 2019-03-25 stuttering issues
419.67 CRD 2019-03-20 stuttering issues
419.35 GRD 2019-03-05 stuttering issues
419.17 GRD 2019-02-22
418.91 GRD 2019-02-14 NO stuttering issues
Did anyone test 419.17 about the stutter issues?
SirMaster
28th March 2019, 20:04
Probably dumb question.
How can I tell whether my D3D11 is actually running in Native or Copy-Back mode?
I know how to get D3D11 Native, but I understand some madVR options will trigger it into copy-back mode.
SamuriHL
28th March 2019, 20:20
You have to select the GPU in LAV Video settings with D3D11 set. That will force copy-back. Not selecting the GPU selects Native.
SirMaster
28th March 2019, 20:35
You have to select the GPU in LAV Video settings with D3D11 set. That will force copy-back. Not selecting the GPU selects Native.
I understand that's how you can manually change between native and copy-back.
But I thought that even if you select native, that enabling certain features in madVR like some HDR to SDR tone mapping settings (restore highlight details?) and such would automatically force madVR into copy-back mode.
Is this simply incorrect? You are suggesting that if I have Automatic (Native) selected that it will never go into copy-back mode no matter what processing settings in madVR I choose? I was always under the impression that D3D11 in madVR could auto-switch when needed. I just want to be able to "tell" when I am no longer in native mode.
Asmodian
28th March 2019, 20:48
No, madVR features that require copy back simply do not work when using native. There is no automatic switch.
SirMaster
28th March 2019, 20:53
No, madVR features that require copy back simply do not work when using native. There is no automatic switch.
Thanks!
Is there a way to know what features need copy-back to work? Other than trying to determine if your video looks like it changed when toggling a feature?
el Filou
28th March 2019, 21:28
madVR features that don't work with DXVA/D3D11 native are: IVTC; black bars detection.
Asmodian
28th March 2019, 21:32
Also the measure frame brightness for HDR tone mapping.
SirMaster
28th March 2019, 21:35
madVR features that don't work with DXVA/D3D11 native are: IVTC; black bars detection.
Are you sure that's really all?
I am certain that for DXVA (Native) vs. DXVA (copy-back) that under devices -> hdr the dropdown called (highlight recovery strength:) does not work in DXVA (Native), but it does work in DXVA (copy-back).
You are saying it should work in D3D11 Native?
https://i.postimg.cc/K8B4fVWf/hdr.png
Also the measure frame brightness for HDR tone mapping.
*EDIT* you beat me.
el Filou
28th March 2019, 22:29
Nope, I also thought that before and it may have been the case at some point in the past, but all the HDR features now work with DXVA native. You can check easily with ShowRenderSteps.
Luminance measure has to work because madshi himself recommends D3D11 native for the standalone measurement tool.
Highlights recovery is also easy to check even without ShowRenderSteps because it uses quite a lot of processing power (at least on my GPU :))
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.