madVR - high quality video renderer (GPU assisted)

[Damien147]

I don't have a high cpu load problem with DXVA2(copy-back).I have jerky ''skippy'' slow down playback problem with DXVA2(copy-back).Only with HEVC,other sources play smoothly with DXVA2(copy-back).

[ryrynz]

I recommend continuing this discussion somewhere else.

[Damien147]

DXVA2(native)HEVC black screen points Madvr and AMD users.For else I am going somewhere else if it's not Madvrs problem.

[QBhd]

I recommend continuing this discussion somewhere else.

Indeed... this is taking far to long and not really a madVR issue

QB

[Damien147]

Guys sorry but I didn't know that it wasn't Madvrs fault.For dxva(copyback) I'm going to Lav thread but DXVA2(native)HEVC black screen points Madvr and AMD users.EVR plays 10bit HEVC with DXVA2(native) as intended,no black screen.Two more AMD users here reported it.
Madshis priority is NGU pixart,not that.All I said is to keep it in mind.Have a nice day:)

[huhn]

http://bugs.madshi.net/view_all_bug_page.php?project_id=4&dummy=bla/

and don't even know if madVR support p010 from DXVA.

[Damien147]

The ''skippy'' DXVA2(copy-back) gives me P010 in OSD.Gonna report it,thanks.

[MS-DOS]

I just tested two HEVC 2160p 60 fps samples on my RX 480 out of curiosity. Results:

1. HEVC 2160p 60fps 8-bit (https://www.youtube.com/watch?v=bgnDEZAjLhI) (link in the description):

madVR, DXVA native - All good
madVR, DXVA copyback - Slideshow
EVR CP, DXVA native - All good
EVR CP, DXVA copyback - Slideshow

2. HEVC 10-bit 59.940fps (Korean ATSC 3.0 satellite TV capture sample) (http://kodi.wiki/view/Samples):

madVR, DXVA native - Black screen
EVR CP, DXVA native - All good

Conclusion: The slowdown is not madVR related. The black screen probably is, OSD reports P010 plus a lot of dropped frames and presentation glitches.

[MultiAnon]

anyone know what the latest AMD driver that works with madVR is? (im using a r9 290)

[HillieSan]

I just tested two HEVC 2160p 60 fps samples on my RX 480 out of curiosity. Results:

1. HEVC 2160p 60fps 8-bit (https://www.youtube.com/watch?v=bgnDEZAjLhI) (link in the description):

madVR, DXVA native - All good
madVR, DXVA copyback - Slideshow
EVR CP, DXVA native - All good
EVR CP, DXVA copyback - Slideshow

2. HEVC 10-bit 59.940fps (Korean ATSC 3.0 satellite TV capture sample) (http://kodi.wiki/view/Samples):

madVR, DXVA native - Black screen
EVR CP, DXVA native - All good

Conclusion: The slowdown is not madVR related. The black screen probably is, OSD reports P010 plus a lot of dropped frames and presentation glitches.

Thanks a lot! I was already wondering, because I got black screen since madvr 0.91.1 or 0.91.3 (test update). The slideshow happend before. Since then I have also updated the AMD drivers a few times. So, I cannot tell if it is a driver or madvr issue. I agree with Damien147 that the issue points to madvr.

[strumf666]

anyone know what the latest AMD driver that works with madVR is? (im using a r9 290)
I am using the Crimson ReLive Edition 17.2.1 (R9 290x) and no problems so far.

[tranfa]

As huhn and I have both suggested, please upload it (zipped) to some external file host. Attaching files to this forum doesn't work very well.



Sorry you're right.
Here is the first file:
http://www.filedropper.com/madvr-log30hz
And here is the second:
http://www.filedropper.com/madvr-log25hz

[MultiAnon]

I am using the Crimson ReLive Edition 17.2.1 (R9 290x) and no problems so far.

Turns out i was using an older version of madVR, updated to the newest version, and now i have no problems.

[tranfa]

I reproduced your problem and by adding p50 solved it.



EDIT:So your resolution is 3840x2160?Then try :

3840x2160p24, 3840x2160p25, 3840x2160p29, 3840x2160p30, 3840x2160p50

or

2160p24, 2160p25, 2160p29, 2160p30, 2160p50

Nope: I still have 30hz for 25fps material with this input.

Unsurprisingly, I don't have 50hz among the allowed one for 2160p in my TV/video card/driver.

[huhn]

because you need HDMI 2.0 for 2160p50/60 on the GPU and TV.

[tranfa]

because you need HDMI 2.0 for 2160p50/60 on the GPU and TV.

Sure, so "unsurprisingly"; but this is not the issue....

[Georgel]

Here's a new NGU pixart test build:

http://madshi.net/nguPixArt.zip

Actually, the zip contains 2 different test builds. Both builds are almost identical to each other and to the previous build with only one key difference: The NGU "very high" algorithm has been tuned. The "low", "medium" and "high" algorithms haven't changed at all. So if you want to test the new builds, please use "very high" for all your tests.

The new builds have slightly different priorities to before: The old NGU pixart test build put highest priority on anti-aliasing capabilities, which proved to be working well. However, it resulted in some artifacts sometimes, and in results maybe not always looking very natural. The tuned NGU pixart "very high" algo now compromises a little bit. I've traded in a bit of anti-aliasing capability for more natural looking results and more sharpness. The 2 new builds are very near to each other. One build has ever so slightly higher anti-aliasing abilities, the other one is ever so slightly sharper.

Included in the zip is also a little image quality comparison, with screenshots taken with: NNEDI3-256, standard NGU very high, the original NGU pixart very high, and the 2 new NGU very high variants. Please check out the images and let me know which algorithm you prefer. Please also double check with your own content to verify your preferences.

Here's my own subjective quality evaluation, based on the screenshot images in the zip:

anti-aliasing abilities: NGU-pixart-old > NGU-pixart-2 > NGU-pixart-3 > NNEDI3-256 (see kitchen and americanDad images)
natural look: NGU-pixart-3 > NGU-pixart-2 > NNEDI3-256 > NGU-pixart-old (see potatoes and suzumiya images)
sharpness: NGU-pixart-3 > NGU-pixart-2 > NNEDI3-256 > NGU-pixart-old (see castle and americanDad images)

Overall, I prefer NGU pixart 2/3 over the other options, but I can't decide if I prefer pixart 2 or 3. With some images I prefer 2, with some 3.

What are your thoughts?

Hey, @madshi

Tested and yes, it seems like the third variation does a pretty good job at eliminating the aberrations from the old pixart module.

I would personally prefer maybe even more anti aliasing if that were possible as I like my images very anti aliased for anime, but I think that it is going in the right direction.

Too much sharpness can easily result in jagged edges with anime, especially when we're talking about old shows, bad encodings and such.

[Damien147]

I just tested two HEVC 2160p 60 fps samples on my RX 480 out of curiosity. Results:

1. HEVC 2160p 60fps 8-bit (https://www.youtube.com/watch?v=bgnDEZAjLhI) (link in the description):

madVR, DXVA native - All good
madVR, DXVA copyback - Slideshow
EVR CP, DXVA native - All good
EVR CP, DXVA copyback - Slideshow

2. HEVC 10-bit 59.940fps (Korean ATSC 3.0 satellite TV capture sample) (http://kodi.wiki/view/Samples):

madVR, DXVA native - Black screen
EVR CP, DXVA native - All good

Conclusion: The slowdown is not madVR related. The black screen probably is, OSD reports P010 plus a lot of dropped frames and presentation glitches.

Yes,it seems that the black screen problem is there only with 10bit HEVC.About the ''slideshow'' it seems that it gets worst with Madvr in comparison with EVR.



Nope: I still have 30hz for 25fps material with this input.

Unsurprisingly, I don't have 50hz among the allowed one for 2160p in my TV/video card/driver.

Too bad because I found source to reproduce your problem (25fps movie with 30hz) and If I added p50 solved it{(particular 25fps sources playing in 50hz)(other 25 fps sources played in 25hz)}

[tranfa]

Too bad because I found source to reproduce your problem (25fps movie with 30hz) and If I added p50 solved it{(particular 25fps sources playing in 50hz)(other 25 fps sources played in 25hz)}

Thank you anyway for trying.

[Asmodian]

Yes,it seems that the black screen problem is there only with 10bit HEVC.About the ''slideshow'' it seems that it gets worst with Madvr in comparison with EVR.

That the "slideshow" is worse with madVR compared to EVR is expected, madVR uses more memory bandwidth than EVR. If copyback is noticeably slower than native your GPU is starved for memory bandwidth.

[Damien147]

....and I can't do anything about that.Right?Thanks for the info.

[cork_OS]

Some pictures to check algo's anti-aliasing possibilities: G1610 (https://i.imgur.com/SZMscvc.jpg) (groundtruth (https://i.imgur.com/7fC4xct.jpg), maybe), Mario Party (http://i57.tinypic.com/w7mzqg.png) (taken here (https://forum.doom9.org/showthread.php?p=1736810#post1736810)).

[leeperry]

anyone know what the latest AMD driver that works with madVR is? (im using a r9 290)

13.12 should be the fastest if running W7/W8 on a r9 2x0 or older, BTW I'll be upgrading to W8.1 very soon(I want 10bit support and have to run x64 so I can go 2160p60 down the road) so I guess I can stick to 13.12 with my 7850? No option to output 10bit in Windows with those though but mVR doesn't care apparently and will force it anyway? :o

[Anima123]

Madshi, if you would consider keeping the low level configuration of current NGU series, I'd be appreciated?

With my newly bought gig XPS 15 9560, which only has a 1050 card, and can barely handle 720p -> 1080p @ 24fps fluently with medium level, so keeping the low level is quite important to me, especially when the SuperXBR is to be replaces.

It would be great if you can do the magic to improve the quality of the low level a little bit.

[huhn]

13.12 should be the fastest if running W7/W8 on a r9 2x0 or older, BTW I'll be upgrading to W8.1 very soon(I want 10bit support and have to run x64 so I can go 2160p60 down the road) so I guess I can stick to 13.12 with my 7850? No option to output 10bit in Windows with those though but mVR doesn't care apparently and will force it anyway? :o

the 13.12 driver doesn't support proper settings for high bit deep.
this has nothing to do with windows 7 or 8+.

[Damien147]

13.12 should be the fastest if running W7/W8 on a r9 2x0 or older, BTW I'll be upgrading to W8.1 very soon(I want 10bit support and have to run x64 so I can go 2160p60 down the road) so I guess I can stick to 13.12 with my 7850? No option to output 10bit in Windows with those though but mVR doesn't care apparently and will force it anyway? :o

I think some user here with rx 460 and W8.1 didn't have 10bit support.Why don't you go to win10 straight away?It's better.

[leeperry]

the 13.12 driver doesn't support proper settings for high bit depth.
this has nothing to do with windows 7 or 8+.

so for mVR to output 10bit Windows must also be set to 10bit? This might indeed be a problem as 13.12 don't provide a bit depth option, I thought 13.12 would allow mVR to force 10bit provided that the OS supports it.

I think some user here with rx 460 and W8.1 didn't have 10bit support.Why don't you go to win10 straight away?It's better.
madshi advises sticking to W8.1 but W7SP1 works like a charm for me tbh, too bad I can't get 10bit to work due to a bs Windows update that refuses to install.....but 8.1 comes with native UASP USB3 so that's also great coz USB3 is quite a crap shot on W7 and again AMD have given up on x86 drivers so even though Reclock is still stuck in x86-land I got no choice than to go x64 if I wanna be able to output 2160p60 with an AMD 4x0 later on.

And FWIR UHD rules coz it's 3x720p, IIRC mVR has 3X optimisations?

[Damien147]

I guess win10 will make you more future proof but you know your needs best.You can ask nussman user here for W8.1 and 10bit with the amd rx 460 he has.

[Asmodian]

And FWIR UHD rules coz it's 3x720p, IIRC mVR has 3X optimisations?

Madshi was going to look into a 3x version of NGU but it turned out that it would be the same speed as 4x NGU so it was never implemented. I would still like to see it for exactly that; 720p to 4K upscaling.

[huhn]

so for mVR to output 10bit Windows must also be set to 10bit? This might indeed be a problem as 13.12 don't provide a bit depth option, I thought 13.12 would allow mVR to force 10bit provided that the OS supports it.

windows doesn't have a 10 bit option.
and yes you can send 10 bit to the GPU driver you simply have no control over what it is doing with it.

I wanna be able to output 2160p60 with an AMD 4x0 later on

good luck with this.

[leeperry]

Is there any way to check that 10bit got enabled apart from mVR's OSD? Test patterns maybe? That's what this guy does (http://uk.rtings.com/tv/reviews/samsung/ku6500):
can display a 10 bit gradient smoothly, which is the same as the other Samsung TVs released this year. Some minor issues can be seen in the darker shades, mostly in the green, but this should not be visible while watching normal content.
AMD 4x0's support HDMI 2.0b so I don't see why 2160p60 would be an issue, eventually my goal is to go 3x720p@60Hz with FRC :devil:

[huhn]

yes and this TV is 8 bit. what every they do they don't judge the native bit deep of the screen they judge the dithering and if i'm not mistaken without AFRC because the screen doesn't have it.
every TV supports 12 bit input that's totally normal.

some TV tell you the input type most didn't. just use a newer driver you have to do that with an RX 4x0 card anyway.

AMD 4x0's support HDMI 2.0b so I don't see why 2160p60 would be an issue, eventually my goal is to go 3x720p@60Hz with FRC

well because that's the reason i don't have a RX 480 anymore. no picture no fun. so good luck not everyone is affected.

[ryrynz]

madshi advises sticking to W8.1

Nah, he just says 8.1 works well, but then so does 10. You can easily configure things if you have problems you have with how 10 does things.
Seems rather weird to embrace software development on one hand and completely ignore it with the other. 10 has been near enough to perfect for me on my HTPC, no way I'd buy 8.1 for a new build.

[sarah180]

Hey @madshi. I would like to request that you restore the ability to do nearest-neighbor upscaling. It seems to have been removed in recent versions.

I have an actual use case for this, and am sticking with an older version as a result. Although nearest-neighbor is not generally a desirable algorithm for most realistic images, it can be desirable when displaying media containing pixel artwork. It is also quite useful as a means to demonstrate to people the differences between different interpolation kernels on real media, something I have occasion to do in an educational capacity.

My suspicion is that was removed because you imagine that nobody uses it and you could save real estate. I can testify that I use it regularly (though not for photographic content). Perhaps you could combine nearest-neighbor and bilinear upscaling under a shared radio button and name it something like "Simple," much as you folded C-R and M-N under the "Cubic" banner. (Another idea would be to combine NN, bilinear and DXVA2 under a "Native" or "GPU" grouping.)

Thank you for all your hard work on publishing madVR for free: it is a fantastic offering. I know you can't fulfill the requests of everybody, but I hope you will at least consider restoring this functionality. It would brighten my day.

[HillieSan]

Is there any way to check that 10bit got enabled apart from mVR's OSD? Test patterns maybe? That's what this guy does (http://uk.rtings.com/tv/reviews/samsung/ku6500):

AMD 4x0's support HDMI 2.0b so I don't see why 2160p60 would be an issue, eventually my goal is to go 3x720p@60Hz with FRC :devil:

This is why I bought an AMD RX 480. It's working great without FRC and without tuning. Drivers have improved. But this is also thanks to the performance improvements of NGU over NNEDI3.

[oddball]

I have a couple of problems since buying a 4K TV.

1. If I put in the display capability options '2160p23, 1080p23' while set to 2160p resolution it upscales 1080 to 2160. If I set the resolution before playback to 1080 it downscales 2160p to 1080p. This only appears to occur on x264 reencodes. If I playback the original H.264 blurays in a remux, it switches correctly between the two at any given fps. I do not wish for 1080 x264 encodes to upscale to 2160 as I lose some motion options on the TV (It's complicated to explain here but I have my reasons).

2. If Windows 10 scaling slider is used at 2160 then 1080p plays with a large portion of the video cut off (zoomed in on the top left hand corner). If I set the output in Windows to 1080 and play a 4K clip with scaling on then the video shrinks into the top left corner of the display. This only happens for blurays that switch to 1080 or 2160 and not the x264 encodes which upscale/downscale depending on the initial resolution set in Windows.

I am using DX11 FSE on a AMD Radeon RX480 with latest drivers outputting 4:4:4 full RGB 12bit at 60Hz when at 1080.

[Damien147]

Madshi suggests to keep native resolution when using display modes.
For keeping resolution no matter what you play you do 3840x2160p23, 3840x2160p25 ....and on
For changing resolution you do 1080p23, 2160p23....and on


For 2. you mean it overscans?Check if your TV has fit to screen option and set it to ON.It removes any scaling from TVs part.

[oddball]

Madshi suggests to keep native resolution when using display modes.
For keeping resolution no matter what you play you do 3840x2160p23, 3840x2160p25 ....and on
For changing resolution you do 1080p23, 2160p23....and on


For 2. you mean it overscans?Check if your TV has fit to screen option and set it to ON.It removes any scaling from TVs part.


No overscan is off on the TV. This is zooming the video or shrinking the video depending on what the inititial resolution in Windows is set to. Scaling affects video playback when switching between resolutions at playback.

I have just found it sometimes does it on x264 encodes too. Some 1080 encodes get scaled to 2160 and some switch to 1080 and get zoomed with Windows scaling enabled (currently at 250%).

I shall post state from one that switches and one that gets upscaled.

This one switches to 1080 correctly (with the scaling zoom problem)

Format : Matroska
Format version : Version 4 / Version 2
Overall bit rate : 5 282 kb/s
Writing application : mkvmerge v8.3.0 ('Over the Horizon') 64bit
Writing library : libebml v1.3.1 + libmatroska v1.4.2

Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4
Format settings, CABAC : Yes
Format settings, ReFrames : 4 frames
Codec ID : V_MPEG4/ISO/AVC
Bit rate : 4 792 kb/s
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Variable
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Language : English
Default : Yes
Forced : No
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709

This one gets upscaled instead to 2160p (no scaling zoom issues).

General
Format : Matroska
Format version : Version 4 / Version 2
Overall bit rate : 7 298 kb/s
Writing application : mkvmerge v8.3.0 ('Over the Horizon') 64bit
Writing library : libebml v1.3.1 + libmatroska v1.4.2

Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4.1
Format settings, CABAC : Yes
Format settings, ReFrames : 5 frames
Codec ID : V_MPEG4/ISO/AVC
Duration : 1 h 47 min
Bit rate : 5 787 kb/s
Width : 1 920 pixels
Height : 808 pixels
Display aspect ratio : 2.40:1
Frame rate mode : Constant
Frame rate : 23.976 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.156
Stream size : 4.33 GiB (79%)
Writing library : x264 core 148 r2744 b97ae06
Encoding settings : cabac=1 / ref=5 / deblock=1:0:0 / analyse=0x3:0x133 / me=umh / subme=7 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=1 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=0 / chroma_qp_offset=-2 / threads=18 / lookahead_threads=3 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=3 / b_pyramid=2 / b_adapt=1 / b_bias=0 / direct=1 / weightb=1 / open_gop=0 / weightp=2 / keyint=250 / keyint_min=23 / scenecut=40 / intra_refresh=0 / rc_lookahead=40 / rc=2pass / mbtree=1 / bitrate=5787 / ratetol=1.0 / qcomp=0.60 / qpmin=0 / qpmax=69 / qpstep=4 / cplxblur=20.0 / qblur=0.5 / ip_ratio=1.40 / aq=1:1.00
Language : English
Default : Yes
Forced : No

[Mistery 73]

Good morning
I had a doubt for upscalare 1080p to 4K with madVR need to set your video card to 3840x2160 and 2160p madVR use the modes list etc.?

[Damien147]

@oddball

I don't know.

1.Check TVs resolution with the info button to see if the resolution is correct.

2.Disable scaling from gpu.

3.Check underscan/overscan in amd radeon settings.The default behavior is 0% though from now on.


@Mistery 73

Not sure if I get you.
You set resolution to 3840x2160 in video card and for display modes if you wanna use them for everything you do 3840x2160px

[oddball]

@oddball

I don't know.

1.Check TVs resolution with the info button to see if the resolution is correct.

2.Disable scaling from gpu.

3.Check underscan/overscan in amd radeon settings.The default behavior is 0% though from now on.

OK. BTW I tried forcing 1920x1080p23 but it won't hold it just switches back to 1080p23. Same goes for 3840x2160p23 when the display is set to 2160 it defaults back to 2160p23. GPU scaling is already off but I will try with it on. OK made no difference. MadVR wants to upscale some 1080 movies to 2160 and others it switches to 1080 (then zooms the video so most of it is cut off if scaling is applied at 2160 on the Windows display settings).

EDIT I have more info.

The movies that are being upscaled to 2160 (but displaying correctly on the TV) are being received by the TV as BT2020.
The movies that are switching to 1080 and getting zoomed by Windows scaling are not showwing BT2020.

Does this clue anyone in?

EDIT2: OK I set MadVR to 8 bit and although it now does not say BT2020 on the movies that upscale it continues to upscale them so not the cause that I can see.

[Mistery 73]

Damien
Where does it Set the resolution 3840x2160 in madVR

[Damien147]

OK. BTW I tried forcing 1920x1080p23 but it won't hold it just switches back to 1080p23. Same goes for 3840x2160p23 when the display is set to 2160 it defaults back to 2160p23. GPU scaling is already off but I will try with it on. OK made no difference. MadVR wants to upscale some 1080 movies to 2160 and others it switches to 1080 (then zooms the video so most of it is cut off if scaling is applied at 2160 on the Windows display settings).

As I said earlier

For keeping native resolution no matter what you play you do 3840x2160p23, 3840x2160p25 ....and on
For changing resolution you do 1080p23, 2160p23....and on




Damien
Where does it Set the resolution 3840x2160 in madVR


You go in---->devices---->your monitor or TV----->display modes


You do that only if you wanna use 24p
Example : 3840x2160p23, 3840x2160p25,

[oddball]

OK I managed to figure out one part of the scaling issue but it's still not right. When it switches to 1080p (for those movies it allows it to) the 1080 scaling was at set above 100% I moved it back to 100% during playback and applied it. Now instead of zooming 1080 when switching from 2160 it is shifted to the right of the TV display by one half. The left half is black.

For now I will have to leave the display at 1080 in Windows settings as it is mostly HD stuff I play and only switch to 2160 when I want to play UHD/4K videos. But this is really annoying. I am not sure if it's a bug in Windows display otions, driver bug(s), a MadVR issue, The TV scaling or a combination of all of them.

[Damien147]

I had a thing some time ago and TV with AMD was reporting the wrong resolution of 4096x2160 instead of 3840x2160.Make sure that this isn't happening to you.Whatever happens set video card to 3840x2160 and then when playing the files you want check what resolution TV reports.

Skip this video to 12:01 and go fullscreen to check what happens https://www.youtube.com/watch?v=HKRcpCQJW8M (there is a download link also if you want to test with Madvr.)




For now I will have to leave the display at 1080 in Windows settings as it is mostly HD stuff I play and only switch to 2160 when I want to play UHD/4K videos. But this is really annoying. I am not sure if it's a bug in Windows display otions, driver bug(s), a MadVR issue, The TV scaling or a combination of all of them.

Native resolution is always best and you lose Madvrs ''magic'' by doing that.

[oddball]

OK this is just damn weird and I think it's either a Windows 10 bug or a driver bug.

If I set the TV to be the 'center' display everything works. It switches to the correct resolution from MadVR and scaling does not move the video or zoom it in any way shape or form. But here's the rub. My TV is off to the right of me and my secondary monitor is off to the left. So it's the wrong way around when mousing from left to right (I have to traverse the TV display as screen 2 to get to screen 3 on my left). The other snag is when I finish playing a video and exit the resolution stays at the last resolution played. So the TV will stay at 1080 if the last movie played was 1080 and visa versa for 2160. For some reason it's not switching back to what the default resolution was.

[Damien147]

You can use win key+p to switch between displays.Choose the correct side in amd radeon settings.
Set resolution to 3840x2160 in video card/windows and make sure restore original display mode... is ticked in Madvrs display modes.

[oddball]

OK a hard reset fixed the switching issues. Scaling is still screwed but I can just leave the TV at 1080 since I am not using it as a PC monitor anyhow. Windows scaling is a bit busted for multiple displays if switching resolutions on-the-fly. Just a quick note. When I say Windows scaling I mean text DPI (the slider).

[Damien147]

Yeah,I use win+p a lot and TVs DPI is set to 300%.It *ucks some icons or programs up.

[ryrynz]

Damien
Where does it Set the resolution 3840x2160 in madVR
Display rate changer? Simple profile stuff, you know this?