madVR - high quality video renderer (GPU assisted)

[Siso]

BT.1886 is terrible (IMO).
No two displays will result in the same curve.

Black Compensated Gamma curve makes sure that from a certain point all displays are equal.
Each display has different black level, but above say 10 nit (variable by user) they are all equal, that's why compensated gamma cure is much closer to reference than BT.1886.
How much should the black compensated gamma curve compress the shadows?
This is a personal taste but the result always looks much more contrasty than 1886 without crushing/clipping any black steps at the bottom.

The sRGB curve is a Black Compensated 2.2 Gamma curve, and IMO it looks better than BT.1886 on a 1000:1 typical LCD display.
If you want to discuss this let's start a new thread and I will gladly show you with pictures and HCFR plots my claims.

Looking forward to see your claims :) A new thread will be good.

[James Freeman]

Come to the SDR Display EOTF (Gamma 2.2/2.4 or BT.1886) (http://forum.doom9.org/showthread.php?p=1768660#post1768660) thread.

[Megalith]

Does anyone have any thoughts on what madVR will be able to achieve with a GTX 1080? What will we be able to max out with that card?

[aufkrawall]

It won't be much faster than a Titan X, NNEDI3 64 1080p60 -> 4k (Jinc AR for chroma) with SuperRes 3 (+ deband & smooth motion) will probably work, maybe even SR4. But likely not much more. Maybe even less.

[ryrynz]

It won't be much faster than a Titan X

Hard to speculate when it's an entirely new architecture. Perhaps a thread should be started with links to test videos where certain profiles can be benchmarked.

[mrjones]

It won't be much faster than a Titan X, NNEDI3 64 1080p60 -> 4k (Jinc AR for chroma) with SuperRes 3 (+ deband & smooth motion) will probably work, maybe even SR4. But likely not much more. Maybe even less.


A Frame rate increase of 30% for an OC 1080 , when compared to a Titan X - would that not translate into more extreme settings for MADVR?

[ryrynz]

A Frame rate increase of 30% for an OC 1080 , when compared to a Titan X - would that not translate into more extreme settings for MADVR?

It would hence my previous post but this is getting off topic, a benchmarking thread might be useful.

[Uoppi]

OK, I found out using blacklevel tag can make the washed-out picture of a suboptimal encode look better whereas levels seems to do nothing to it.

Some questions though:
1) How does blacklevel work exactly - it compresses/expands the range of blacks below/above 16?
2) When correcting a washed-out picture using blacklevel, should whitelevel or some other parameter be adjusted too to compensate (and if yes, how/why exactly in relation to blacklevel?)

[QBhd]

OK, I found out using blacklevel tag can make the washed-out picture of a suboptimal encode look better whereas levels seems to do nothing to it.

Some questions though:
1) How does blacklevel work exactly - it compresses/expands the range of blacks below/above 16?
2) When correcting a washed-out picture using blacklevel, should whitelevel or some other parameter be adjusted too to compensate (and if yes, how/why exactly in relation to blacklevel?)

Most of the time, it's a bad encode that has been improperly expanded. Why not just adjust the Source input levels on the fly. Ctrl+Alt+Shift+I during playback will toggle through all the levels. If I notice a file is washed out, it's the first thing I do (I even set up a button on my remote for this) and it's almost always a double expanded source. Although I did see a triple expanded source once!

QB

[chros]

Most of the time, it's a bad encode that has been improperly expanded. Why not just adjust the Source input levels on the fly. Ctrl+Alt+Shift+I during playback will toggle through all the levels. If I notice a file is washed out, it's the first thing I do (I even set up a button on my remote for this) and it's almost always a double expanded source. Although I did see a triple expanded source once!
Agreed!

[Uoppi]

Hmm, I did try all possible "level" tags but surprisingly none of them had any effect on the picture. Adjusting "blacklevel" to -50 made a clear difference but I'm not at all sure if that's the same thing as switching "level".

Sure enough, the encode has just the black level wrong because other than being washed out (sort of like overlaid with a greyish veil or something), it's looking good and has decent bitrate too.

Anyway, I'd prefer tags as those keyboard commands are cumbersome when using a smartphone as the remote.

[QBhd]

Hmm, I did try all possible "level" tags but surprisingly none of them had any effect on the picture. Adjusting "blacklevel" to -50 made a clear difference but I'm not at all sure if that's the same thing as switching "level".

Sure enough, the encode has just the black level wrong because other than being washed out (sort of like overlaid with a greyish veil or something), it's looking good and has decent bitrate too.

Anyway, I'd prefer tags as those keyboard commands are cumbersome when using a smartphone as the remote.

You can easily change the KB shortcut in madVR to something that is easier to work with.

QB

[ashlar42]

madshi, would you be so kind as to provide a full explanation about the video and audio clock calculations?

I know the refresh rate is displaying the refresh rate after deviation is taken into account, so if one knows the exact timings he used, he can get to the percentage of deviation. Is this right? How do you come up with the value for "display"? Why is it shown as an absolute value instead of a percentage, as it happens for the audio clock?

What about the audio clock deviation? Both audio and video are measured against the system clock, right?

I'm using a GTX 660 with HDMI audio onboard and I'm seeing very similar values in deviation (based on the above assumptions) for both audio and video. Meaning if I input exact timings for the resolutions/refreshes needed I see excellent results when bitstreaming (1 frame drop/repeat every x days or every 18 hours at the worst), which kinda makes sense according to your previous descriptions. If the two clocks (video and audio) deviate by a similar amount, playback is smooth.
I'd just like to understand the process fully.

Thanks so much for your help and for all the work you put in madVR.

[Uoppi]

You can easily change the KB shortcut in madVR to something that is easier to work with.

QB

Sure. Still I prefer not to use keyboard at all but have the most frequently needed Kodi functions displayed as easily accessible buttons on my smartphone remote (self-customized Unified Remote remote). And the remote's getting a bit crowded :D.

Really strange the "levels" tag has no effect whatsoever (none from these makes a difference: levels=PC|TV|fullrange|limited|doubleExp|tripleExp). Picture remains unbearably grey, unlike with "blacklevel" which does work.

EDIT: Using the level tag does change the level (verified by CTRL+ALT+shift+i) but the black level doesn't change at all at any of the settings. :(

[chros]

Really strange the "levels" tag has no effect whatsoever (none from these makes a difference: levels=PC|TV|fullrange|limited|doubleExp|tripleExp). Picture remains unbearably grey, unlike with "blacklevel" which does work.

EDIT: Using the level tag does change the level (verified by CTRL+ALT+shift+i) but the black level doesn't change at all at any of the settings. :(
I just tried it for you: it's working as it should for me with v0.90.17 using filename: "foo levels=tripleExp.mkv"

[Uoppi]

I just tried it for you: it's working as it should for me with v0.90.17 using filename: "foo levels=tripleExp.mkv"

I'm on the latest madVR and Kodi DSplayer but no luck.

I have no idea if it should matter but anyway I even tried setting the whole chain to full RGB (I usually have GPU on full while madVR, Kodi & TV are on limited). OSD tells me levels are changed but picture looks the same. Which, like I said, seems very odd as the blacklevel tag does work. Could the "culprit" be Kodi, which has its own range setting?

[Stereodude]

This 2.4 vs 2.2 battle is overall stupid.

Rec709 movies are supposed to be seen with 2.2 gamma.

If you want to raise the gamma anyway, enable "dynamic contrast" on your TV, just be sure it's originally calibrated to 2.2.

Unless ur TV is very old or a monitor calibrating to 2.4 has no point as modern TVs with dynamic contrast can handle "dynamic" higher gamma better than pure 2.4 gamma (atleast 2013+ models), basically less black/white crush.
It's not anywhere nearly as clear cut as you're suggesting. When they used CRTs for mastering when calibrated were not really delivering a 2.2 gamma. As such, you can't really claim they're supposed to be seen with 2.2 gamma. When mastering monitors were switched from CRTs to other display types I don't know.

[StinDaWg]

I have an odd but very specific bug to report. Using the latest AMD drivers (5/23 I believe), madVR v0.90.20, and HD7750.

When playing back 1080i content (either regular or film deinterlacing, doesn't matter), I get 1 line pixel flickering around all 4 borders, unless "use a separate device for presentation" is checked. This only affects D3D9 exclusive mode. Windowed and D3D11 are fine.

Edit: It's not just 1080i29.97 videos, it's also doing it on 720p29.97 videos.

Also, NNEDI3 isn't working at all. It just ignores the settings and uses whatever is set for image upscaling (Jinc, Lanczos, ect). Super-XBR works though.

[QBhd]

I have an odd but very specific bug to report. Using the latest AMD drivers (5/23 I believe) and HD7750.

When playing back 1080i content (either regular or film deinterlacing, doesn't matter), I get 1 line pixel flickering around all 4 borders, unless "use a separate device for presentation" is checked. This only affects D3D9 exclusive mode. Windowed and D3D11 are fine.

No help from me... but wow, that really is a very odd and specific bug :P

QB

[Uoppi]

Could someone else using Kodi DSplayer kindly check if the different "levels" tags make any difference to the picture (i.e. blacks)?

And as I'm out of luck with this, I'd like to know if finetuning blacks using the "blacklevel" tag is essentially the same thing as changing levels via the "level" tag? (Changing levels via the tv remote for every clip is too cumbersome and not a satisfactory option for me.)

[QBhd]

Could someone else using Kodi DSplayer kindly check if the different "levels" tags make any difference to the picture (i.e. blacks)?

And as I'm out of luck with this, I'd like to know if finetuning blacks using the "blacklevel" tag is essentially the same thing as changing levels via the "level" tag? (Changing levels via the tv remote for every clip is too cumbersome and not a satisfactory option for me.)

It should just be an odd occurrence. If most of what you are watching is wrong levels, then maybe you have the wrong setup...

QB

[Uoppi]

It should just be an odd occurrence. If most of what you are watching is wrong levels, then maybe you have the wrong setup...

QB

Don't know what could be wrong with the setup. Black levels are calibrated OK and it's just this specific washed-out encode.

Anyway, shoud be easy to test with DSplayer and keyboard command CTRL + SHIFT + ALT + i. Wondering if it works for someone else.

[huhn]

I have an odd but very specific bug to report. Using the latest AMD drivers (5/23 I believe), madVR v0.90.20, and HD7750.

When playing back 1080i content (either regular or film deinterlacing, doesn't matter), I get 1 line pixel flickering around all 4 borders, unless "use a separate device for presentation" is checked. This only affects D3D9 exclusive mode. Windowed and D3D11 are fine.

do you have a sample?

[leeperry]

Is the "cleanup image borders by cropping" option not a good solution? It is probably meant to clean up faded or distorted edges of analogue captures but it could work well here too?

It does but manually only so ideally I'd like to remux MKV music videos out of those big captured TS files and tag them accordingly in order to hide all borders/logos leftovers once and for all.

Anyway, my long delay when closing PotP or changing the frame rate in Reclock was due to some sloppy USB audio drivers from CEntrance and strangely it was still hiccuping when the DAC was disconnected, it really only stopped acting up after I uninstalled them.

Also, ever since I upgraded from mVR .19 to .20 I found the picture too sharp, I just did some A/B comparisons on very sharp and realistic looking 1080p30 content and as much as toggling the new deringer in .19 outrageously improves the picture as if it was cleaning fog from the camera optics .20 looks way oversharp and digital. I'll try to find some test patterns if need be, I'll stick to .19 for now.

[ashlar42]

madshi, would you be so kind as to provide a full explanation about the video and audio clock calculations?

I know the refresh rate is displaying the refresh rate after deviation is taken into account, so if one knows the exact timings he used, he can get to the percentage of deviation. Is this right? How do you come up with the value for "display"? Why is it shown as an absolute value instead of a percentage, as it happens for the audio clock?

What about the audio clock deviation? Both audio and video are measured against the system clock, right?

I'm using a GTX 660 with HDMI audio onboard and I'm seeing very similar values in deviation (based on the above assumptions) for both audio and video. Meaning if I input exact timings for the resolutions/refreshes needed I see excellent results when bitstreaming (1 frame drop/repeat every x days or every 18 hours at the worst), which kinda makes sense according to your previous descriptions. If the two clocks (video and audio) deviate by a similar amount, playback is smooth.
I'd just like to understand the process fully.

Thanks so much for your help and for all the work you put in madVR.

Some more info. I'm trying, together with user hannes69 from Kodi forums, to understand exactly the process behind the numbers madVR displays.

Considering you have stated in the past that:

1) "display" shows the refresh rate adjusted for the video clock deviation measured against the system clock

2) "clock deviation" shows the deviation for the audio clock, again measured against the system clock.

I'll make an example of what we found for a 59.940 video content played back with bitstreaming audio at 59.940 display refresh rate.

Display: 59.94174
Clock Deviation: +0.00276%
1 frame drop every 3.17 hours
movie 59.940 fps

audio clock deviation 27.6ppm
video clock deviation: (59.94174 - 59.94) / 59.94 = 29.03ppm
total deviation: video clock dev - audio clock dev = 28.86ppm - 27.6ppm = 1.43ppm

frames in 3.17 hours = (3600 * 59.940) * 3.17 = 684,035.28

1 frame dropped every 684,035.28 frames. Accuracy of 1 / 684,035 = 0.0000014619, that is 1.46ppm (I guess this is well within the margin of error in madVR approximations once it reaches the x.xx hours stage).

The above tells me that you are using the approximation of 59.940 in the internal calculations, and not the 60/1.001 value. Is this correct?
If using the 60/1.001 value we would have:

audio clock deviation 27.6ppm
video clock deviation: (59.94174 - (60/1.001)) / (60/1.001) = 28.03ppm
total deviation: video clock dev - audio clock dev = 28.03ppm - 27.6ppm = 0.43ppm

frames in 3.17 hours = (3600 * (60/1.001)) * 3.17 = 684,035.96

1 frame dropped every 684,036 frames. Accuracy of 1 / 684,036 = 0.0000014619, that is again 1.46ppm

0.43ppm clock difference audio/video seems too low if compared to what drop/repeats at every 3.17 hours indicate, while 1.43 is very similar.
So, are you using 59.940 for internal calculations? Does this hold true for 23.976 as well?

Sorry, I know we are reaching the human limits of geekiness here... but we would really love to fully understand the underlying math :)

I also can't understand why my clock deviation sits constantly at about 0.00276% at 59.940 refresh rate while going down to 0.00242% at 23.976 refresh rate. It's the audio clock measured against the system clock. Why should display refresh rate influence the deviation? I have been checking and checking but the difference between the two refresh rates stays there... It's audio and video through HDMI on a GTX660, if it matters.

[Werewolfy]

madVR v0.90.20 released

http://madshi.net/madVR.zip

* tweaked deringing algorithm some more
* added workaround for weird crash with latest AMD beta drivers
Not much time for madVR this weekend, so only small changes. Feedback about the tweaked deringing algo welcome.

Thanks for the new version, the tweaked deringing algo is definitely better. Much less artifacts and deringing is still very powerful. Ok sometimes it removes some details but a lot less that others deringing algo I've seen so far so it doesn't bother me, I know it won't never be perfect.

The only real artifact that remains is the one I showed you... Do you need a sample of this video?

But I admit I find that the pros of deringing outperform the cons that remain this time :)

[leeperry]

Houston, we have a problem(that's with .19 BTW):

http://thumbnails116.imagebam.com/48648/3c0d65486479708.jpg (http://www.imagebam.com/image/3c0d65486479708) http://thumbnails115.imagebam.com/48648/423fd3486479709.jpg (http://www.imagebam.com/image/423fd3486479709)

Seems boiling down to FS(whatever E or W) + SSIM 2D + black bars detection as either going 1D or disabling the latter works fine, here's a MKV sample (https://mega.nz/#!Xxx0gaYQ!fShBxbO0z3Xi2xGgWSwfmxIgpeOAtXWEFGDlix9h4n0).

So I captured a big .TS file off DVB-T2 and only this music video in the sample gave that first problem but once I enable doubling they all go bananas like this in FS: http://thumbnails116.imagebam.com/48649/440f09486480480.jpg (http://www.imagebam.com/image/440f09486480480)

:thanks:

PS: Oh and I wish I could get black bars to never ever appear not even for a few secs as I'm not watching a movie but simply rolling music videos in big .TS captured files, am I missing an option here? :o

[huhn]

i get the green screen with always - 2x supersampling image doubling + SSIM 2D target resolution 1920x1080p.
crop black boarder doesn't have an effect on this for me.

this doesn't happen with "always - if upscale is needed" only with "always - 2x supersampling". i guess this has something to do with the 1440x1080p 16/9 source that is displayed at 1920x1080p.

i'm doing this in mpc-hc window mode so the resolution is the problem not FS. i'm on UHD.

i'm using madVR 90.20 and 960 gtx 368.22

[baii]

I have an odd but very specific bug to report. Using the latest AMD drivers (5/23 I believe), madVR v0.90.20, and HD7750.

When playing back 1080i content (either regular or film deinterlacing, doesn't matter), I get 1 line pixel flickering around all 4 borders, unless "use a separate device for presentation" is checked. This only affects D3D9 exclusive mode. Windowed and D3D11 are fine.

Edit: It's not just 1080i29.97 videos, it's also doing it on 720p29.97 videos.

Also, NNEDI3 isn't working at all. It just ignores the settings and uses whatever is set for image upscaling (Jinc, Lanczos, ect). Super-XBR works though.

The driver probably broke opencl. I haven't bothered to upgrade to any of the crimson AMD driver , after testing 5-6 versions for almost half year and none of them can just "work".

[MariaX9]

After some Days of testing, i am now using this Settings.

Processing
- artifact removal: medium/high,
- reduce ringing artifacts, reduce dark halos
everything other is deafult

Sacling algorithms
- Chroma: super-xbr 100 AR, SR 2
- Downscaling: SSIM 2D 100% AR, LL, AB 75%
- Doubling: luma/chroma always 2x, super-xbr AB25
- Upscaling: Jinc, AR
- Refinement: sharpen edges 0.5, crispen edges 1.0, AB 100%, AR, SR 2

I usually watch 480p and 720p Content. The only settings im not sure about, are the Downscaling AB strength and all the Settings at Refinement. May someone has any suggestions?

[foozoor]

This CrossBilateral mpv shader works very well.
https://gist.github.com/igv/a015fc885d5c22e6891820ad89555637
I hope you will port it inside madVR soon!

Could you bring the one-pass AdaptiveSharpen back into madVR?
https://gist.github.com/igv/8a77e4eb8276753b54bb94c1c50c317e
It uses much less gpu and looks pretty good.

[Shiandow]

This CrossBilateral mpv shader works very well.
https://gist.github.com/igv/a015fc885d5c22e6891820ad89555637
I hope you will port it inside madVR soon!

Looks like that's pretty much a verbatim copy of the latest version of the Bilateral chroma scaler I wrote. Well, except for the lines referring to the originals (https://github.com/zachsaw/MPDN_Extensions/tree/master/Extensions/RenderScripts/Bilateral). They could have at least mentioned my name somewhere...

Anyway madshi did say he was interested in the new Bilateral scaler, so with any luck there might be a MadVR version soon.

[mzso]

Hi!

I don't see it mentioned, but ProgDVB recently added madVR support. (according to the topic search) So if anyone who has a PC tuner wants try or test they can do. (There's a free version)

Formerly I had trouble finding a well working free tuner app that had madVR, which beside the lack of the usual quality improvement you can expect from madVR meant that I got fugly aliasing on downscaling thanks to the crappy Nvidia/AMD drivers and EVR.

MadVR support at first was pretty buggy, with crashes and wrong aspect ratio. Now to the only issue that remains is that for some reason it has a low-res OSD, compared to the HD one with EVR.

[jkauff]

I don't see anything in the Settings, but I thought I'd ask: is there any way to set the font size of the OSD? The old size was too small, and the new size is too large. I'd like something a little smaller so it fits in the black border area of SD movies on a 1920x1080 display.

[Asmodian]

I don't see anything in the Settings, but I thought I'd ask: is there any way to set the font size of the OSD? The old size was too small, and the new size is too large. I'd like something a little smaller so it fits in the black border area of SD movies on a 1920x1080 display.

Currently there is no way to adjust the font for the OSD.

[e-t172]

madshi: while doing some experiments with 3DLUTs and calibration curves, I've noticed that the "disable GPU gamma ramps" option does absolutely nothing if a 3DLUT with calibration curves built-in is loaded. madVR will always load the calibration from the 3DLUT into the GPU gamma ramps, no matter what. I guess in a way that makes sense (if one generates a 3DLUT with calibration information, it's because one wants it to be loaded), but it's very confusing to have a checkbox that does nothing. How about graying out the checkbox when a 3DLUT that contains calibration information is loaded?

(When using a 3DLUT that does not contain calibration curves - e.g. when not using ArgyllCMS collink -a nor -H options - the "disable GPU gamma ramps" option does what it says on the tin.)

[huhn]

even with an 3D LUT loaded that ignored this setting it should still be possible to select.

for example you are creating a new 3D LUT. the 3D LUT will be unloaded automaticly but the new 3D LUT can be created with or with out the gamma ramp depending on the setting selected.

[e-t172]

Yes. That's why I suggested graying out the option if a 3DLUT that contains calibration information is loaded. The checkbox is still useful when a 3DLUT that does not contain calibration information is loaded.

(That said, if you ask me, using 3DLUTs without integrated calibration curves is quite error-prone and seems like a very good way to shoot yourself in the foot by accidentally messing up the gamma ramps, but that's just my opinion.)

[JarrettH]

How does a 3D LUT impact performance? I noticed my render times going up and down sharply while using one.

[huhn]

depends. i had no notable performance issues at 1080p but with UHD a 3D LUT eats my GPU from time to time depending on a lot of settings.

a 3D LUT with SM creates a lot of problem for me. + 100 ms spikes and stuff like that.

the conclusion was that the driver was doing strange things with "rare" colors. nothing has change since this for me. i worked around it with some settings and setting that take 12 ms without a 3D lut.

[Dlget]

Hi,My RAM is getting full after playing video say for 1hr.
Got 8GB RAM & at starting of player , it's 25%.
But after 1hr it becomes 95%.
Forwarding ,going into fullscreen or out of full screen takes time like forever.
it's like something is loading into RAM but not releasing.

I'm using
madVR 0.90.20
mpcBE 1.4.6
LAV filter 0.68.1
XYSUb filter 3.1.0.746
Sanear AUdio Renderer

[Stereodude]

How does a 3D LUT impact performance? I noticed my render times going up and down sharply while using one.
I have this same issue on my GTX 650 running a QHD (2560x1440) monitor under Windows 10. I'm guessing it has to do with insufficient video RAM on the card and moving things back and forth between the card and system RAM, but I'm not certain. I plan to replace it with a GTX 1070 shortly so I haven't spent a lot of time trying to sort it out.

[JarrettH]

I have this same issue on my GTX 650 running a QHD (2560x1440) monitor under Windows 10. I'm guessing it has to do with insufficient video RAM on the card and moving things back and forth between the card and system RAM, but I'm not certain. I plan to replace it with a GTX 1070 shortly so I haven't spent a lot of time trying to sort it out.

I have a feeling there's more processing involved and when the video content changes (higher bitrate?) that causes a spike in render time. I've seen it go up as much as 15 ms. I hope madshi can go into detail on this.

To alleviate this, I setup a key to toggle debanding. It's usually not a big deal to me if it's off, but it saves performance.

[huhn]

bitrate has nothing to do with this.

the decoding queue would fall first and the rendertime wouldn't spike.

[Patrik G]

Someone has uploaded a bunch of LG HDR demos and they look amazing!
those that works with madvr are the HDR10 videos
the Dolby Vision clips works but madvr doesnt detect them as HDR and so they look washed out.

Enjoy :)
https://www.avforums.com/threads/panasonic-dx902b-owners-thread.2013148/page-237#post-23694482

the rest
https://mega.nz/#F!aBAGBJBb!vGOiLiLo9HT7fBA1qww3-Q

List of the HDR10 videos:
LG_2_DEMO_4K_L_H_01_Daylight.lge
LG_2_DEMO_4K_L_H_02_UHD HDR Tech.lge
LG_2_DEMO_4K_L_H_03_Daylight.lge
LG_2_DEMO_4K_L_H_04_UHD HDR Tech.lge
LG_2_DEMO_4K_L_H_05_Rays of Light.lge
LG_2_DEMO_4K_O_H_3_NASA HDR.lge
LG_2_DEMO_4K_O_H_4_Colors of Journey.lge
LG_2_DEMO_4K_O_H_5_Chess.lge
LG_2_DEMO_4K_O_H_6_Cymatic Jazz.lge
LG_2_DEMO_4K_O_H_7_OLED HDR Tech.lge

rename the videos to "MKV"

http://privat.bahnhof.se/wb192876/LG%20HDR.jpg

[Stereodude]

I have a feeling there's more processing involved and when the video content changes (higher bitrate?) that causes a spike in render time. I've seen it go up as much as 15 ms. I hope madshi can go into detail on this.

To alleviate this, I setup a key to toggle debanding. It's usually not a big deal to me if it's off, but it saves performance.
On my GTX 650 the render time oscillates / bounces up and down significantly when the 3D LUT is enabled and playback is full screen. When it's in a window not being scaled to 1440p it does not. Hence my blaming RAM. On my R9 380 connected to my TV (FHD) the 3D LUT doesn't change the render times in any appreciable fashion.

[ryrynz]

Someone has uploaded a bunch of LG HDR demos and they look amazing!


Based on what I've seen in store with the Sony HDR demos playing back in HDR and non HDR on an LG 70UH635T the difference isn't as great as the image you posted would make it seem, in fact not even close.
HDR is more realistic sure, provides more depth to the image sure but the Rec.709 picture in no way looks washed out at all.
Typical marketing overdoing it, it's pretty common in the industry.

[leeperry]

Pretty OT but yeah, do we even care for HDR at all? 3D kept crapping out and eventually went belly up twice so they figured they'd have to come up with some brand new sales bs but at the end of the day does it even matter to us? My current mVR rig certainly doesn't look washed out hah.

[XMonarchY]

Given the system specs listed below and lack of HDR display, what Nits value should I set for HDR Peal Luminance setting? I would like the image to be as accurate as possible...

[huhn]

it depends on how bright your display can get so there is no answer.

there is no correct way anyway because there is no clear spec on how to compress the dynamic range.

TV are just doing what they want.