madVR - high quality video renderer (GPU assisted)

[tp4tissue]

There are three places where conversions can happen before the display and they do not interact. The display can be doing conversions internally too, but we cannot control these.

1) LAV video can do a conversion if the render does not support the source format. When using madVR this should never be needed and it is not ideal.
2) madVR will output RGB at whatever bitdepth is set.
3) The GPU driver will do a conversion to whatever you set in its control panel.

madVR will never change what it outputs based on what the GPU is set to and the GPU will never change its output based on what madVR sends it. All these steps simply convert any input to their configured output format without a lot of smarts involved. For example the GPU is happy to convert madVR's 8 bit output to 10 bit. You know for sure what the GPU is outputting based on what it is set to in its drivers.

Also, I can send my TV 8 bit RGB HDR and it will say HDR10, that is just a brand label for the metadata standard, it works with 8 bit RGB too. :)

So if the NvidiaCP is on 8 bit rgb, and the TV is popped into NVHDR, MADVR set to 10 bit.

What am I seeing, still 8 bit HDR ?

[iSeries]

So if the NvidiaCP is on 8 bit rgb, and the TV is popped into NVHDR, MADVR set to 10 bit.

What am I seeing, still 8 bit HDR ?

8bit. Whatever the GPU output format is set to to is what your TV is receiving (the first line in madVR stats will tell you)

[madjock]

So if the NvidiaCP is on 8 bit rgb, and the TV is popped into NVHDR, MADVR set to 10 bit.

What am I seeing, still 8 bit HDR ?

Yes. :) You can get nVidia to 12Bit either easy or hard depending what drivers you use, whether that does anything you can see is another matter.

[iSeries]

whether that does anything you can see is another matter.

Indeed, and may actually do more harm than good anyway - definitely for my TV there is more banding at 12bit than 8bit (LG C8).

[tp4tissue]

8bit. Whatever the GPU output format is set to to is what your TV is receiving (the first line in madVR stats will tell you)

Yes. :) You can get nVidia to 12Bit either easy or hard depending what drivers you use, whether that does anything you can see is another matter.

Indeed, and may actually do more harm than good anyway - definitely for my TV there is more banding at 12bit than 8bit (LG C8).



OK guys, tahnx, I am understands now.. My TV has been Lying to me, that cheatn' whore..


Which driver are y'all guys using for 12 bit ? (nvidia)


Does 10 bit work on all drivers ? (nvidia)

[iSeries]

OK guys, tahnx, I am understands now.. My TV has been Lying to me, that cheatn' whore..


Which driver are y'all guys using for 12 bit ? (nvidia)


Does 10 bit work on all drivers ? (nvidia)

385.28 probably works easiest if you are using a custom resolution. With later drivers (not sure when it started), madVR could only create 8bit custom resolutions, which means needing CRU to create it. I found 416.35 to work great if not using a custom resolution (or if creating an 8bit custom res with madVR, or creating a 12bit custom res with CRU). I believe the latest driver will only kick into HDR if madVR sends 10bit, regardless of whether the GPU driver is set to 12bit or 8bit.

You should look and carefully compare 12bit vs 8bit. Many TVs will show colour banding with 12bit input which isn't there when given 8bit.

[Alexkral]

Stop using SVP and set the right frequency of your display and your graphics card. This is my experience and it works well.

The fact is that I really like the enhanced temporal resolution. It feels a bit weird at start, but once you get used to it you really appreciate the inprovement (though I admit that for some content it will always look too weird). I have even modified the base avisynth script to get rid of most artifacts.
For HDR that's a problem that you don't know very well where to start. Obviously it's not very reasonable to ask madshi to support tonemapping for input that doesn't identify itself as HDR, and ffdshow is no longer being developed, so there's not an easy solution. I'm testing now DmitriRender and it seems better than SVP in both performance and visual quality. Unfortunately it doesn't support HDR metadata passthrough either, but at least the developer says he's working on it.

[huhn]

just frame match and let the TV do it.

doing 5/1 instead of 5/2 interpolation is massively better anyway even through i would use neither.

[Warner306]

Just realised that NGU causes quite a lot of coil whine, even when using it only for chroma. I bought a 1070 in black friday and didn't notice until I enabled NGU for my monitor the other day. What puzzled me is that I do GPU intense work and never had coil whine until this, I did a comparison rendering with GPU with Redshift and GPU-Z report is the same than with NGU, with further testings I found that the trigger was Memory Controller Load, at 25% it makes the buzz noise below or above doesn't, the problem is that NGU very high (above 25%) heats my card like a toaster (running it in a mATX case)

Coil whine is defect of the fan, so NGU can exasperate it, but not cause it. Using very high can push some GPUs into overdrive.

[Warner306]

Yes but there are no numbers on this ?

I did try the HDR set you mention, but I could not get the clipping ones to work, or rather get my TV to adjust once in HDR mode, unsure if this was me, or that adjusting for black crush is broken for me on my TV as I read is common in HDR mode.

The numbers are at the top and bottom of the pattern. That pattern is really only for those with 8-bit displays. It is not a great pattern, but it is the only 8-bit HDR10 black clipping pattern I could find. I was able to calibrate black clipping by using it.

It is mostly useful to select the output SDR gamma curve for HDR -> SDR. With most HDR displays, it is not advisable to change the brightness or contrast controls because you can offset the display's tone mapping, which is based on the default settings for both.

[madjock]

With most HDR displays, it is not advisable to change the brightness or contrast controls because you can offset the display's tone mapping, which is based on the default settings for both.

Thats the part I struggle with, I have lots of presets and Movie is usually a favorite, but unsure what is right or wrong. I turn off all processing and motion options, but when I tried any HDR calibration items, especially black and white I could not achieve anything near the finesse of adjusting for clipping on an SDR display.

[hannes69]

Coil whine is defect of the fan, so NGU can exasperate it, but not cause it..
No.
My passive GPU has coil whine as well. That has nothing to do with a fan.
Additionally the coil whine seems to be triggered by the kind of electric load caused by NGU, it doesn´t depend on the strength of the load but on the 'sort' of load.
Nothing to do against it - beside of some nasty (and maybe not working) decoupling tricks with glue, plastic spray etc.
Coil whine is part of NGU (on the hardware side) ;)
Madshi should implement a totally new scaler that is better in all regards than all other recent scalers and of course coil-whine-proof ;)

[Asmodian]

It isn't the fan it is the chokes or coils in the power delivery circuits, hence "coil whine".

The power circuits are contently turning off and on because they use PWM to control power output. Anytime this on/off cycle matches a resonate frequency or harmonic of the coils they can vibrate audibly. Almost any load can cause coil whine if you have coils that can vibrate audibly. The GPU core and memory also use different power circuits so it isn't surprising to have memory load (power draw) cause whine if it is one of those coils that is resonating.

Coil whine is not "part of NGU". NGU is simply a somewhat heavy, but not 100%, load on the card. I do not have any coil whine with NGU (or anything else) because the power circuitry on my card, or my previous one, does not resonate at any audible frequencies under any loads I have run so far. Don't blame NGU, blame whoever made your GPU for selecting chokes that can whine.

[tp4tissue]

It isn't the fan it is the chokes or coils in the power delivery circuits, hence "coil whine".

The power circuits are contently turning off and on because they use PWM to control power output. Anytime this on/off cycle matches a resonate frequency or harmonic of the coils they can vibrate audibly. Almost any load can cause coil whine if you have coils that can vibrate audibly. The GPU core and memory also use different power circuits so it isn't surprising to have memory load (power draw) cause whine if it is one of those coils that is resonating.

Coil whine is not "part of NGU". NGU is simply a somewhat heavy, but not 100%, load on the card. I do not have any coil whine with NGU (or anything else) because the power circuitry on my card, or my previous one, does not resonate at any audible frequencies under any loads I have run so far. Don't blame NGU, blame whoever made your GPU for selecting chokes that can whine.


It isn't always the choke, the Core itself is susceptible to piezoelectric effects given the right frequency of operation.

Capacitors also, but usually only big ones.

[Asmodian]

Woah! I have never head of that, the core resonating at audible frequencies enough to make noise!?! It seems like that would be really bad. Do GPUs have capacitors big enough to make noise?

It wouldn't be coil whine either, the coils in that description are the chokes. ;)

Anyway my point still stands, this is not NGU's fault, it is simply a common defect in the hardware that can be triggered by NGU or any other GPU load.

[tp4tissue]

385.28 probably works easiest if you are using a custom resolution. With later drivers (not sure when it started), madVR could only create 8bit custom resolutions, which means needing CRU to create it. I found 416.35 to work great if not using a custom resolution (or if creating an 8bit custom res with madVR, or creating a 12bit custom res with CRU). I believe the latest driver will only kick into HDR if madVR sends 10bit, regardless of whether the GPU driver is set to 12bit or 8bit.

You should look and carefully compare 12bit vs 8bit. Many TVs will show colour banding with 12bit input which isn't there when given 8bit.


Is there a 10bit 8bit gradient test pattern confirmed to distinguish noticeably in Madvr..

[hannes69]

Anyway my point still stands, this is not NGU's fault, it is simply a common defect in the hardware that can be triggered by NGU or any other GPU load.

Yes, you can read in the net here and there about coil whine in PSUs and GPU boards, sometimes more often with certain manufacturers and models, so to speak a kind of hardware defect.
But many people in this thread here reported independantly about coil whine in combination with NGU. And many confirmed that the whine only can be triggered by NGU. So you have coil whine by using NGU with e.g. 85% GPU load and you have no coil whine when using any other scaler with 85% GPU load.
So NGU seems to trigger a kind of 'load distribution' or whatever you call it that triggers coil whine.
A perfect coil should not produce any noise of course. But we don´t live in a perfect world ;)
My GPU NEVER makes any noise (independant of load) with the exception of NGU (-> coil whine).
Interesting physical phenomena :)
Of course I don´t blame NGU or madshi. The coil should be mute in all possible situations, but NGU seems to be a strong trigger for unknown reasons.

[Asmodian]

madVR is a very spiky load. After the buffers are full it renders one frame as fast as possible then idles until the next frame needs to be rendered. NGU simply needs more work done by the GPU so these odd peaks last longer. I think this is why NGU seems to trigger coil whine in a way that many GPU bound applications do not.

[Warner306]

It isn't the fan it is the chokes or coils in the power delivery circuits, hence "coil whine".

The power circuits are contently turning off and on because they use PWM to control power output. Anytime this on/off cycle matches a resonate frequency or harmonic of the coils they can vibrate audibly. Almost any load can cause coil whine if you have coils that can vibrate audibly. The GPU core and memory also use different power circuits so it isn't surprising to have memory load (power draw) cause whine if it is one of those coils that is resonating.

Coil whine is not "part of NGU". NGU is simply a somewhat heavy, but not 100%, load on the card. I do not have any coil whine with NGU (or anything else) because the power circuitry on my card, or my previous one, does not resonate at any audible frequencies under any loads I have run so far. Don't blame NGU, blame whoever made your GPU for selecting chokes that can whine.

That is informative. I've never experienced coil whine, either. I did have an idea of what it sounds like, but the GPU has always managed to arrive in working order. I would have hoped this would be less common in new GPUs by this point.

[Warner306]

Is there a 10bit 8bit gradient test pattern confirmed to distinguish noticeably in Madvr..

Come on man, you are bordering on spamming this thread with random stuff.

There is one gradient test in the madVR guide in my signature that can be of some help, but you might have to find some blue skies in UHD Blu-rays to prove or disprove banding.

[actarusfleed]

Hi, I've tried to do the same thing on two different PCs...
I've installed only MPC-HC and last official build of Madvr.
I set a code to change automatically profiles but do not works ...

https://audioquality.it/cloud/forum/codee.jpg

if (deintFps <= 25) and (srcWidth > 1920) "2160p24"
else if (deintFps <= 25) and ((srcWidth <= 1920) and (srcHeight > 1080)) "1080p24"
else if (deintFps > 25) and (srcWidth > 1920) "2160p60"
else if (deintFps > 25) and ((srcWidth <= 1920) and (srcHeight > 1080)) "1080p60"

Surely I've missed something ....

Any help?
thank you

[Alexkral]

just frame match and let the TV do it.

doing 5/1 instead of 5/2 interpolation is massively better anyway even through i would use neither.

That's unusable because of the input lag, and yes 5/1 is kind of what I'm doing.

[Asmodian]

if (deintFps <= 25) and (srcWidth > 1920) "2160p24"
else if (deintFps <= 25) and ((srcWidth <= 1920) and (srcHeight > 1080)) "1080p24"
else if (deintFps > 25) and (srcWidth > 1920) "2160p60"
else if (deintFps > 25) and ((srcWidth <= 1920) and (srcHeight > 1080)) "1080p60"

I think these greater than signs should be less than or equal to signs.

However, I would also rewrite it simpler:
If (deintFps < 26) and ((srcWidth <= 1920) and (srcHeight <= 1080)) "1080p24"
else if ((srcWidth <= 1920) and (srcHeight <= 1080)) "1080p60"
else if (deintFps < 26) "2160p24"
else "2160p60"

Remember, if an If statement validates it doesn't continue to the next statement so you only need to account for content in the next rule that doesn't match an earlier one.

[austonrush]

Hi, I've tried to do the same thing on two different PCs...
I've installed only MPC-HC and last official build of Madvr.
I set a code to change automatically profiles but do not works ...

if (deintFps <= 25) and (srcWidth > 1920) "2160p24"
else if (deintFps <= 25) and ((srcWidth <= 1920) and (srcHeight > 1080)) "1080p24"
else if (deintFps > 25) and (srcWidth > 1920) "2160p60"
else if (deintFps > 25) and ((srcWidth <= 1920) and (srcHeight > 1080)) "1080p60"

Surely I've missed something ....

Any help?
thank you

I run 9 profiles for my scaling algorithms and below is my profile rules. I only run 4 processing profiles based on sd, hd, fullhd and 4k.

This allows me to max out and also micro adjust for 24fps versus 60fps on each resolution type.

if ((srcHeight <= 540) and (deintFps < 25)) "SD 24fps"
else if ((srcHeight <= 540) or (fileName = "*.avi")) "SD 60fps"
else if ((filename = "*3D*") and (srcHeight <= 720)) "HD 3D"
else if ((srcheight <= 720) or (fileName = "*720p*")) and (deintFps < 30) "HD 24fps"
else if ((srcheight <= 720) or (fileName = "*720p*")) "HD 60fps"
else if ((filename = "*3D*") and (srcheight <= 1080)) "FullHD 3D"
else if ((srcheight <= 1080) or (fileName = "*1080p*")) and(deintFps < 25) "FullHD 24fps"
else if ((srcheight <= 1080) or (fileName = "*1080p*")) "FullHD 60fps"
else if ((srcheight <= 2160) or (fileName = "*2160p*")) and(deintFps < 61) "4k"

If anyone knows a better way to activate a 3d playback profile other than with the filename please let me know!?

[madjock]

Hi, I've tried to do the same thing on two different PCs...
I've installed only MPC-HC and last official build of Madvr.
I set a code to change automatically profiles but do not works ...

Any help?
thank you

I am confused, are you saying your profile has not changed the refresh rate ?, as it is a 23.976 file running at 60, you need to setup the refresh rate for that.

[mclingo]

Is there a 10bit 8bit gradient test pattern confirmed to distinguish noticeably in Madvr..

https://forum.doom9.org/showthread.php?t=172128

[brazen1]

I'm hoping you folks can help me edit my profile(s). I like the idea of more madVR control based on FPS @austonrush exampled a couple posts up. (Side note - is FPS the same as Hz and refresh rate in this regard?) 2160p 23/24FPS allows more aggressive settings in Scaling vs 2160p 60FPS for example. Since I don't use a profile separating the two, I use less aggressive settings to meet the demands of 2160p 60FPS but desire to use higher settings for 2160p 23/24 FPS. I'd like this to automate based on a profile. I'd prefer not to add something in a file name to trigger and use metadata instead if possible (as I presently am) but will only if necessary. I'm only interested in separating 2160p 23/24 FPS and 2160p 60 FPS for SCALING at this time but would welcome others. Here are my present profiles:

DISPLAY profile for calibration tab based on BT.2020 vs BT.709

if (HDR) "BT.2020"
else "BT.709"

PROPERTIES profile based on 10-bit vs 8-bit native bitdepth setting (both currently set to 8bit and really not in use at this time but may be in the future)

If (deintFps <= 30) "10-bit"
else "8-bit"

PROCESSING profile based on 2160p, 1080p, 720p, and SD resolutions

if (srcWidth > 1920) "2160p"
else if (srcWidth <= 1920) and (srcHeight > 1080) "2160p"

else if (srcWidth > 1280) and (srcWidth <= 1920) "1080p"
else if (srcWidth <= 1280) and ((srcHeight > 720) and (srcHeight <= 1080)) "1080p"

else if (srcWidth > 960) and (srcWidth <= 1280) "720p"
else if (srcWidth <= 960) and ((srcHeight > 540) and (srcHeight <= 720)) "720p"

else if (srcWidth <= 960) and (srcHeight <= 540) "SD"


SCALING profile based on 2160p,1080p, 720p, and SD resolutions

if (srcWidth > 1920) "2160p"
else if (srcWidth <= 1920) and (srcHeight > 1080) "2160p"

else if (srcWidth > 1280) and (srcWidth <= 1920) "1080p"
else if (srcWidth <= 1280) and ((srcHeight > 720) and (srcHeight <= 1080)) "1080p"

else if (srcWidth > 960) and (srcWidth <= 1280) "720p"
else if (srcWidth <= 960) and ((srcHeight > 540) and (srcHeight <= 720)) "720p"

else if (srcWidth <= 960) and (srcHeight <= 540) "SD"


RENDERING profile based on 3D, 2160p, 1080p, 720p, and SD resolutions

if (3D) "3D"
else if (srcWidth <= 720) and (srcHeight <= 576)"SD"
else if (srcWidth <= 1280) and (srcHeight <= 720)"720p"
else if (srcWidth <= 1920) and (srcHeight <= 1080)"1080p"
else if (srcWidth <= 3840) and (srcHeight <= 2160)"2160p"


*EDIT*
Maybe this will help others? I edited my '2160p' profile to '2160p 24fps' and used more aggressive settings.
I added another profile '2160p 60fps' and retained the old calmer settings.
I edited the SCALING rules to this: If someone knows of something more elegant...

if (srcWidth > 1920) and (deintFps < 25) "2160p 24fps"
else if (srcWidth <= 1920) and (srcHeight > 1080) "2160p 24fps"
else if (srcheight <= 2160) and (deintFps > 59) "2160p 60fps"

else if (srcWidth > 1280) and (srcWidth <= 1920) "1080p"
else if (srcWidth <= 1280) and ((srcHeight > 720) and (srcHeight <= 1080)) "1080p"

else if (srcWidth > 960) and (srcWidth <= 1280) "720p"
else if (srcWidth <= 960) and ((srcHeight > 540) and (srcHeight <= 720)) "720p"

else if (srcWidth <= 960) and (srcHeight <= 540) "SD"

Now I can control 2160p 60fps and 24fps separately.

[Oguignant]

hello, what is the latest version of nvidia drivers that work with madvr + hdr

[Klaus1189]

hello, what is the latest version of nvidia drivers that work with madvr + hdr

https://forum.doom9.org/showthread.php?t=176013

[giulianoprs]

Little curiosity, in devices / properties I set in the automatic "BIT", according to you is wrong? my tv is a plasma panasonic g20 is 8 bit.
When I look at the OS with a fullHD movie it tells me:
D3D11 fullscreen windowed (10BIT)
h264, 8 bit, 4: 2: 0 -> NV12, 8 bit, 4: 2: 0
do you think it's right or wrong?

[huhn]

technically plasma are 1 bit but as far as i know newer plasma panel except 12 bit which is then dithered.

but what so ever it shouldn't matter for the panel more if the processing can handle that properly and what i hear Panasonic didn't really do a great job back then.

so i recommend to set it to 8 bit just to be save.

[Mykola]

Have somebody compared scaling capabilities in modern GPU-s? I have found this, but it is three years old: https://github.com/zachsaw/MPDN_Extensions/wiki/DXVA-HD-Scaler

[madjock]

Have somebody compared scaling capabilities in modern GPU-s? I have found this, but it is three years old: https://github.com/zachsaw/MPDN_Extensions/wiki/DXVA-HD-Scaler

Warners guide has a lot of info on scaling and what is Low/Meds/High, it is not based on GPUs as such but I think it does explain how taxing they all are.

As far as I am aware the newer cards as it the 2070s and the likes are still at such an early stage all these things are based on using 10XX GPUs for the most part.

https://forum.kodi.tv/showthread.php?tid=259188&pid=2238942#pid2238942

[Warner306]

Have somebody compared scaling capabilities in modern GPU-s? I have found this, but it is three years old: https://github.com/zachsaw/MPDN_Extensions/wiki/DXVA-HD-Scaler

This is what it looked like the last time I tried researching this topic. I can't guarantee all settings are accurate and madVR might even tell you what is being used if you select DXVA2:

https://forum.kodi.tv/showthread.php?tid=222576&pid=1966608#pid1966608

[YGPMOLE]

In a house of a friend of mine I tried to use madVR with an Nvidia GTX 1070 and we didn't get HDR Tone Mapping switch on a LG OLED C7.

O.S.: Windows 10 x64, HDR off (greyed out, not selectable)

LAV Video setting: Hardware decoding DX3D11 (but I also tried copy-back and Nvidia Cudic).

madVR settings are: HDR passthrough, output 10bit, metadata to the display, fullscreen exclusive.

Driver: the latest (15-01-2019).

The on-screen display shows output DX3D11, P010, 1000nits BT2020->DCPI3.

The same .mkv file played with a Zidoo (chinese mediaplayer) switches the display in HDR mode.

I use AMD, so I didn't know what else do: any suggestion?

[brazen1]

Try nVidia 385.28 driver.
If Windows HDR switch is greyed out, either Windows build is outdated/corrupt and/or GPU driver is broken.

[tp4tissue]

Try nVidia 385.28 driver.
If Windows HDR switch is greyed out, either Windows build is outdated/corrupt and/or GPU driver is broken.

Also, if you got multimonitor, try it with only 1 connected. Sometimes it doesn't detect correctly.

[mrmojo666]

on my system to get HDR autoswitch working, amd requires that bitdepth 10 or 12 bit is setup in driver settings

[madjock]

on my system to get HDR autoswitch working, amd requires that bitdepth 10 or 12 bit is setup in driver settings

It is an nVidia card he is using so should be easier as you do not need 10bit or FSE.

@YGPMOLE

The feed is not going through an older AVR is it ?, as if it is only 1.4, then you cannot get HDR to work correctly, try direct from the source to the TV to take things out of the loop.

[iSeries]

The same .mkv file played with a Zidoo (chinese mediaplayer) switches the display in HDR mode.

On the TV itself, is HDMI ULTRA HD Deep Color turned on for the HDMI port the PC is connected to?

[madjock]

On the TV itself, is HDMI ULTRA HD Deep Color turned on for the HDMI port the PC is connected to?

You would think they would have used the same HDMI that they used the media player with ? I think I can still get HDR with it at Standard or Optimised on my Phillips, I managed to break it yesterday by trying to put True-HD and HDR down a HDMI 1.4 port, that stopped it for me, still get all the correct numbers and words on the OSD, but no HDR as it does not have the correct specs.

Guess I need a new AVR as 2 displays in Windows when one is not real due to it just being DP->HDMI to AVR to get HI-RES Audio and HDR straight via HDMI to TV, you would not believe how that screws a system.

KODI is basically a waste of time and no idea why, its as if HDR knocks it out to the 2nd display, really strange as 1080p files upscaled to 2160p 23 don't, but 2160p HDR 23 does...work that one out.

[YGPMOLE]

Hi Guys! Thank you all for the tips, but:

@brazen1 I have been back in the thread, found the same suggestion from Madshi and used, but it doesn't solve.

@tp4tissue We already used this way, but still not working.

@madjock The cable was straight to the TV.

@iSeries This could be a possibility, for what I remember we didn't pull off any cable, but we just used the HTPC or the Zidoo with the file on a NAS, so we should have been using two different HDMI input port on the OLED.

I'll keep you posted! meanwhile, thank you again!!!

[Warner306]

I would expect it is the driver. Try 19.1.1.

Also, check the identification tab under devices and see if HDR support is indicated for the connected display.

What is the GPU set to?

[mclingo]

YGPMOLE is asking about a friend who has an NV card, he uses AMD and doesnt have an issue, as i read it.

[YGPMOLE]

@mclingo You're right, maybe Warner306 miss the initial request.

However, he told me that the HDMI input are both in Deep Color mode, so for now neither this option solved the problem. I don't know if he also did a physical switch between the two cables, eventually I'll personally try next sunday, after that I'm going to try a format and a clean install. Thank you all!

[Manni]

Wow, everything seems to be working with 417.71 (although CRU is still needed). Even the Asio4All bug is gone, and REW can work without FlexAsio.

Let's hope they don't break anything soon!

[theDongerr]

Wow, everything seems to be working with 471.71 (although CRU is still needed). Even the Asio4All bug is gone, and REW can work without FlexAsio.

Let's hope they don't break anything soon!

Is that an official endorsement? Will you be updating your sig line?

[Manni]

Is that an official endorsement? Will you be updating your sig line?

I need a bit more time to asses, but yes, that will happen if nothing comes up :)

Still have to check 3D.

[Manni]

So here is how 417.71 seems to be working for me after a bit more testing time:

- 12 minutes between frame drops in 3D (vs 3 minutes with 385.28)
- 12bits RGB Full with custom res (CRU), survives a reboot (as long as default refresh rate is 23p)
- Asio4all working with REW
- All seems good (but I'm ready to backtrack at any time)!
- Sig updated :)

[madshi]

So here is how 417.71 seems to be working for me after a bit more testing time:

- 12 minutes between frame drops in 3D (vs 3 minutes with 385.28)
- 12bits RGB Full with custom res (CRU), survives a reboot (as long as default refresh rate is 23p)
- Asio4all working with REW
- All seems good (but I'm ready to backtrack at any time)!
- Sig updated :)
But HDR passthrough only activates under very specific conditions (must be windowed, can't be FSE, must be fullscreen, can't be windowed, must be D3D11, can't be D3D9, must be 10bit, can't be 8bit) which is bad, and HDR metadata is not properly passed through, as far as I can see.