View Full Version : madVR - high quality video renderer (GPU assisted)
Qaq
8th January 2016, 08:23
If I use Full-Range I get crushed black, everything just become like what's called black crush, shadows just doesn't shown as shadows anymore.
Go to TV's color settings and see if you can change Black level. On some TVs its Low by default and needs to be changed to High for full range.
In sum, for RGB 0-255 you need PC mode for HDMI input and High black level in color.
x7007
8th January 2016, 10:04
Go to TV's color settings and see if you can change Black level. On some TVs its Low by default and needs to be changed to High for full range.
In sum, for RGB 0-255 you need PC mode for HDMI input and High black level in color.
I don't have any option to change the black level. what philips tv brand do you know can do that ? that's what interesting me , cause I checked reviews over many philips tv models and never seen this option.
huhn
8th January 2016, 11:02
I don't have any option to change the black level. what philips tv brand do you know can do that ? that's what interesting me , cause I checked reviews over many philips tv models and never seen this option.
yes usually only PC mode is full range.
and yeah there are issues with contrast/ brightness which can clip a lot of black levels.
x7007
8th January 2016, 11:31
yes usually only PC mode is full range.
and yeah there are issues with contrast/ brightness which can clip a lot of black levels.
I have Game mode and Computer mode, but game mode is like 0-255 you use Limited . and Computer mode is like it turned the brightness up and using Full range makes it look like Game mode. but if you go 3D mode then it revert back to Game mode automatically and you are left with crushed black again.
Qaq
8th January 2016, 15:29
I don't have any option to change the black level. what philips tv brand do you know can do that ?
Sorry, I don't have any experience with philips. I have 2 LG TVs and both have options to change black level either in PC and non-PC modes.
6233638
9th January 2016, 09:20
Can we move the levels discussion to its own topic?
It's not specific to madVR at all and has filled several pages of this topic.
James Freeman
9th January 2016, 19:35
I love madVR.
jkauff
9th January 2016, 22:04
I love madVR.
Well said.
It's so cool to have my SD movies from the 30s and 40s all look like Blu-ray restorations. Thanks madshi.
Della
9th January 2016, 23:31
Well said.
It's so cool to have my SD movies from the 30s and 40s all look like Blu-ray restorations. Thanks madshi.
If you're getting Blu-Ray like SD upscaling, I definitely need a better GPU or better settings!
GTX-960 upscale to 2160 sure ain't a blu-Ray experience for me.
:confused:
Warner306
10th January 2016, 01:05
If you're getting Blu-Ray like SD upscaling, I definitely need a better GPU or better settings!
GTX-960 upscale to 2160 sure ain't a blu-Ray experience for me.
:confused:
He is probably experiencing this with SD -> 1080P upscaling. I don't think it looks like a Blu-ray, but the chain of Image Doubling + SuperRes(3) + crispen edges(1.0) looks pretty impressive to me.
The dilemma madVR has created for this user is that I enjoy Kodi as a media frontend but only the defunct DSPlayer is compatible with madVR. In a year or less, I will be forced to choose between madVR and Kodi. It's madVR, of course.
Thunderbolt8
10th January 2016, 01:46
Ive heard that you can make kodi start mpc-hc & madvr when you select a file to watch.
foozoor
10th January 2016, 01:46
The dilemma madVR has created for this user is that I enjoy Kodi as a media frontend but only the defunct DSPlayer is compatible with madVR. In a year or less, I will be forced to choose between madVR and Kodi. It's madVR, of course.
No need to choose anymore with the new Emby Theater. :)
This is a home theater application like Kodi. The first beta should be released tomorrow.
As you can see it works with madVR!
http://emby.media/community/uploads/inline/2/561bc276520b9_1.png
http://i.imgur.com/KdLq93J.jpg
Warner306
10th January 2016, 03:00
I requested an improvement to sharpen edges and was told to produce some screenshots to illustrate my specific issues.
After taking some screenshots, I think my concerns about sharpen edges producing excessive ringing are overstated, and the limitation of this sharpener has more to do with the thickness of edges it creates and the resulting silhouette. It is an aggressive sharpener and produces an aggressive result.
Source: The Walk (2015)
720p - 10 GB
1080p - 10 GB
madVR profile settings:
720p
Chroma: super-xbr100 + AR
Image: Jinc3 + AR
Image doubling: Off
Upscaling refinement: thin edges (0.1), SuperRes (1)
Artifact removal - Debanding: Medium/High
Image enhancements: Off
Dithering: Ordered
1080p
Chroma: super-xbr100 + AR
Image: Jinc3 + AR
Image doubling: Off
Upscaling refinement: Off
Artifact removal - Debanding: Medium/High
Image enhancements: sharpen edges (0.5)
Dithering: Error Diffusion 2
The intent was to show a disparity in the appearance of the image from an upscaled image (720p) enhanced with SuperRes to a source not resized (1080p) but enhanced with sharpen edges.
At a distance the two profiles look fairly equivalent in terms of detail:
(720p) SuperRes (1.0):
http://i1357.photobucket.com/albums/q760/Warner306/2-720P_zpsa43jne3u.png
Full Size (http://i1357.photobucket.com/albums/q760/Warner306/2-720P_zpsa43jne3u.png)
(1080p) sharpen edges (0.5):
http://i1357.photobucket.com/albums/q760/Warner306/2-1080P_zpshtdadspx.png
Full Size (http://i1357.photobucket.com/albums/q760/Warner306/2-1080P_zpshtdadspx.png)
But, up close, it becomes apparent why sharpen edges appears so abrasive in motion.
Zoomed-in, the image is clearly of a lower resolution in the 720p shot. The impact of upscaling has softened detail. And, while SuperRes has improved things, it is still soft compared to the 1080p profile.
(720p) SuperRes (1.0):
http://i1357.photobucket.com/albums/q760/Warner306/4-720P_zpsr14oex4m.png
Full Size (http://i1357.photobucket.com/albums/q760/Warner306/4-720P_zpsr14oex4m.png)
At 1080p, beyond the detail advantage, sharpen edges does produce its own ringing comparable to the 720p shot. But the ringing is more pronounced and the lines around the actor's shirt are noticeably thicker. The increase in resolution has made sharpening less natural and more clinical.
(1080p) sharpen edges (0.5):
http://i1357.photobucket.com/albums/q760/Warner306/4-1080P_zpstaxwmang.png
Full Size (http://i1357.photobucket.com/albums/q760/Warner306/4-1080P_zpstaxwmang.png)
The same can be said for the next series of shots.
Image detail is reasonably equivalent at a distance.
(720p) SuperRes (1.0):
http://i1357.photobucket.com/albums/q760/Warner306/1-720P_zpszt984qhx.png
Full Size (http://i1357.photobucket.com/albums/q760/Warner306/1-720P_zpszt984qhx.png)
(1080p) sharpen edges (0.5):
http://i1357.photobucket.com/albums/q760/Warner306/1-1080P_zpsuwpa55ux.png
Full Size (http://i1357.photobucket.com/albums/q760/Warner306/1-1080P_zpsuwpa55ux.png)
Zoomed-in, the soft nature of the 720p image is again apparent. This softness better hides the impact sharpening than the 1080p image. The 1080p image also suffers from rigid edges that are the hallmark of my criticism with sharpen edges.
Added ringing is seen in both images. Although, I wouldn't consider it excessive.
(720p) SuperRes (1.0):
http://i1357.photobucket.com/albums/q760/Warner306/5-720P_zpsxjlqaszj.png
Full Size (http://i1357.photobucket.com/albums/q760/Warner306/5-720P_zpsxjlqaszj.png)
(1080p) sharpen edges (0.5):
http://i1357.photobucket.com/albums/q760/Warner306/5-1080P_zpsgyhrqzqv.png
Full Size (http://i1357.photobucket.com/albums/q760/Warner306/5-1080P_zpsgyhrqzqv.png)
And the last series.
(720p) SuperRes (1.0):
http://i1357.photobucket.com/albums/q760/Warner306/3-720P_zpsxa4rferb.png
Full Size (http://i1357.photobucket.com/albums/q760/Warner306/3-720P_zpsxa4rferb.png)
(1080p) sharpen edges (0.5):
http://i1357.photobucket.com/albums/q760/Warner306/3-1080P_zpshoqrdmrn.png
Full Size (http://i1357.photobucket.com/albums/q760/Warner306/3-1080P_zpshoqrdmrn.png)
(720p) SuperRes (1.0):
http://i1357.photobucket.com/albums/q760/Warner306/6-720P_zpsofgddv36.png
Full Size (http://i1357.photobucket.com/albums/q760/Warner306/6-720P_zpsofgddv36.png)
(1080p) sharpen edges (0.5):
http://i1357.photobucket.com/albums/q760/Warner306/6-1080P_zpsat4tzptv.png
Full Size (http://i1357.photobucket.com/albums/q760/Warner306/6-1080P_zpsat4tzptv.png)
Conclusion: This comparison has pointed out the obvious: Sharpening is best combined with image upscaling to remain natural and avoid oversharpening. I do think the ringing of sharpen edges could be improved, but it is not a whole lot more distracting than the ringing caused by image upscaling. My contention with sharpen edges comes with its very nature to enhance object edges; sometimes, excessively.
This finding has not dissuaded me from using image sharpening with high-quality 1080p content. However, it has shown the harsh, clinical nature of sharpen edges and AdaptiveSharpen may not be for everyone. I, for one, now use crispen edges for 1080p -> 1080p sharpening.
cripsen edges rings just like sharpen edges, but does a better job of not bringing attention to itself. I think the choice comes down to a preference in the style of sharpening, more than anything.
And it should be noted, sharpen edges, while clinical is superior to AdaptiveSharpen, which displays sharpen edges' faults even more.
(1080p) crispen edges (0.6):
http://i1357.photobucket.com/albums/q760/Warner306/crispen%20edges_zps3jnmupjo.png
Full Size (http://i1357.photobucket.com/albums/q760/Warner306/crispen%20edges_zps3jnmupjo.png)
(1080p) sharpen edges (0.5):
http://i1357.photobucket.com/albums/q760/Warner306/sharpen%20edges_zpsmg26t76a.png
Full Size (http://i1357.photobucket.com/albums/q760/Warner306/sharpen%20edges_zpsmg26t76a.png)
Problem solved? I guess for now...
Warner306
10th January 2016, 03:03
No need to choose anymore with the new Emby Theater. :)
This is a home theater application like Kodi. The first beta should be released tomorrow.
As you can see it works with madVR!
http://emby.media/community/uploads/inline/2/561bc276520b9_1.png
http://i.imgur.com/KdLq93J.jpg
Yes, I'm aware of this project and will check it out.
I still prefer the depth and feature-set of Kodi. Kodi has superior add-on support (add-ons that are compatible with DSPlayer and madVR), better metadata and more customization. That said, if you are watching content and not browsing your library, any player with built-in support for madVR is "good-enough."
Warner306
10th January 2016, 03:07
Ive heard that you can make kodi start mpc-hc & madvr when you select a file to watch.
Yes, I've written a set-up guide on how to do this (in my signature). But it is nowhere near as good as having madVR built-in to the player. Start and resume points work properly, the GUI is consistent and the library is easier to manage in terms what is and isn't watched. Also, there is an actual GUI; MPC doesn't really offer anything in terms of a home theater GUI.
Della
10th January 2016, 03:50
He is probably experiencing this with SD -> 1080P upscaling. I don't think it looks like a Blu-ray, but the chain of Image Doubling + SuperRes(3) + crispen edges(1.0) looks pretty impressive to me.
The dilemma madVR has created for this user is that I enjoy Kodi as a media frontend but only the defunct DSPlayer is compatible with madVR. In a year or less, I will be forced to choose between madVR and Kodi. It's madVR, of course.
Thanks, I'll check my configuration.
BTW, I've read your guide before, (though I use MBC with MPC-BE vice Kodi) well done.
RainyDog
10th January 2016, 09:11
The dilemma madVR has created for this user is that I enjoy Kodi as a media frontend but only the defunct DSPlayer is compatible with madVR. In a year or less, I will be forced to choose between madVR and Kodi. It's madVR, of course.
Why won't you still be able to launch MPC/madVR as an external player with Kodi in a year? That's all I've ever done, even when DSPlayer had madVR built in.
RainyDog
10th January 2016, 09:23
I requested an improvement to sharpen edges and was told to produce some screenshots to illustrate my specific issues.
After taking some screenshots, I think my concerns about sharpen edges producing excessive ringing are overstated, and the limitation of this sharpener has more to do with the thickness of edges it creates and the resulting silhouette. It is an aggressive sharpener and produces an aggressive result.
Thanks for the interesting comparisons Warner. But you missed a couple of important inclusions in my opinion.
Matching grabs of the untouched source. And sharpen edges in combination with thin edges, especially since you mention yoursef that the main issue with the former is thicker lines which the latter is there to mitigate.
RainyDog
10th January 2016, 09:36
On a related note, I always fall back on the sharpness and resolution pattern on the AVS calibration patterns (http://www.avsforum.com/forum/139-display-calibration/948496-avs-hd-709-blu-ray-mp4-calibration.html) to look at the effects of sharpeners.
Sharpen edges is the first sharpener I've across that actually seems to darken the image slightly. It's instantly noticeable in the dotted boxes in the bottom left and top right when applied. I've never seen another sharpener affect this pattern in way it does actually, it's very manipulative but in a way I've never really seen. Everything's heavily affected from lines to dots to the shapes of edges on text.
In comparison to others, crispen edges adds obvious aliaising and makes text looks jaggy plus brightens the overall image slightly although it's fairly subtle at the default value of 1.0.
Adapative sharpen is the most subtle of the three in terms of altering the image composition. But it also brightens more than the others and also somehow just looks flatter and harsher with actual viewing content.
madshi
10th January 2016, 19:48
EDIT2: !!! Enabling "Activate SuperRes Filter" is what is yielding the sepia image. !!!
Oh, good to know, will have a look at that later.
So let's sum up:
madVR doesn't take into account doubled frame rate when YADIF deinterlacing is enabled.
That's not my fault. I'm switching refresh rates based on the framerate information the decoder provides to me. If that isn't correct, then that's the decoder's fault, not mine.
YADIF deinterlacing seems to be better than madVR's.
It's not as simple as that. YADIF is a video mode deinterlacer. Forced film mode in madVR is a pure IVTC algorithm, which only works properly with fully telecined sources. DXVA deinterlacing is supposed to auto detect whether the source is video or telecined film and adjust accordingly.
For telecined sources, usually madVR's forced film mode is the best deinterlacer out of those 3. For video content, usually DXVA looks better than YADIF, but sometimes DXVA stumble and makes mistakes. YADIF doesn't try to figure out which content is film and which is video, so it cannot stumble.
(Furthermore, DXVA deinterlacing seems broken in Crimson drivers atm, as huhn already mentioned.)
With the latest version (v0.89.19), the matrix of YCgCo video is recognized as BT.709 and results in wrong color.
That seems to be a bug in the decoder. Which one were you using? LAV Video Decoder?
It seems the fix is using NVCP Pre renderer 3
I'm not sure what exactly NVCP prerender is, but if it is what I think it is, it should definitely be set to "application controlled" or however that option is named.
Furthermore: Don't use CUVID, use DXVA Copyback instead. And disable GSync, when using madVR.
2.2.3.3.5.2 Dolby Vision
The Dolby Vision video stream is composed of a BDMV HDR video stream and a Dolby Vision enhancement layer video stream. The enhancement layer is an HEVC video stream with embedded Dolby Vision metadata. The Dolby Vision is characterized by the followings:
color primaries: BT.2020 with non-constant luminance
EOTF(Electro-Optical Transfer Function): SMPTE 2084
Bit depth: 12bit (combination of BDMV HDR video stream and Dolby Vision enhancement layer)
Enhancement layer video stream: 1920x1080 resolution, same frame rate with the BDMV HDR video stream, 100Mbps or lower together with the BDMV HDR video stream
http://www.blu-raydisc.com/assets/Downloadablefile/BD-ROM_Part3_V3.0_WhitePaper_150724.pdf
Regarding Dolby Vision, here is a very good info:
http://hdguru.com/dolby-vision-tries-to-set-bar-for-hdr/
http://www.dolby.com/us/en/technologies/dolby-vision/dolby-vision-white-paper.pdf
Will it be technically possible to achieve accurate playback of the UHD BD mastered in Dolby Vision using MPC-HC/LAVfilters/madvr?
Interesting, but these are all whitepapers, which means it's mostly marketing fluff with very little detailed technical information. E.g. the BD-ROM WhitePaper just has one very little paragraph about Dolby Vision, just describing the very basics. We'd need a lot more information to try to implement full Dolby Vision support.
madshi, 2 feature requests:
The possibility to choose constant OSD background color. When the video sample has too bright background (like the sky) it's really hard to read OSD from a distance (on the projector).
The delay before madVR switches the display to the appropriate mode. When I try to drop the player's window to the second monitor it often gets dropped back on the primary one because of immediate mode switch.
Both are features that nobody else has requested before. Which makes me think that they're probably not overly important atm. I need to prioritize development, get the most important stuff done first.
Conclusion: This comparison has pointed out the obvious: Sharpening is best combined with image upscaling to remain natural and avoid oversharpening. I do think the ringing of sharpen edges could be improved, but it is not a whole lot more distracting than the ringing caused by image upscaling. My contention with sharpen edges comes with its very nature to enhance object edges; sometimes, excessively.
This finding has not dissuaded me from using image sharpening with high-quality 1080p content. However, it has shown the harsh, clinical nature of sharpen edges and AdaptiveSharpen may not be for everyone. I, for one, now use crispen edges for 1080p -> 1080p sharpening.
cripsen edges rings just like sharpen edges, but does a better job of not bringing attention to itself. I think the choice comes down to a preference in the style of sharpening, more than anything.
And it should be noted, sharpen edges, while clinical is superior to AdaptiveSharpen, which displays sharpen edges' faults even more.
Problem solved? I guess for now...
Thanks for the interesting images. I do miss the original size BMPs/PNGs, because only that way would I be able to reproduce your sharpening results here, and maybe try different settings or try to improve the algorithms with the help of your images.
On a related note, I always fall back on the sharpness and resolution pattern on the AVS calibration patterns (http://www.avsforum.com/forum/139-display-calibration/948496-avs-hd-709-blu-ray-mp4-calibration.html) to look at the effects of sharpeners.
Sharpen edges is the first sharpener I've across that actually seems to darken the image slightly. It's instantly noticeable in the dotted boxes in the bottom left and top right when applied. I've never seen another sharpener affect this pattern in way it does actually, it's very manipulative but in a way I've never really seen. Everything's heavily affected from lines to dots to the shapes of edges on text.
In comparison to others, crispen edges adds obvious aliaising and makes text looks jaggy plus brightens the overall image slightly although it's fairly subtle at the default value of 1.0.
Adapative sharpen is the most subtle of the three in terms of altering the image composition. But it also brightens more than the others and also somehow just looks flatter and harsher with actual viewing content.
So short summary: You sound like you hate all of those algos? :p
FWIW, I've noticed myself that "sharpen edges" might be slightly too dark. It will be ever so slightly brighter in the next build. However, I'm not sure if anything will change for artificial test patterns. Due to the way "sharpen edges" works internally, it might not look too great on such test patterns.
I do like artificial test patterns to get an idea of what an algorithm does exactly. But final judgement of an algo's quality should be made with real life content. After all, if you sit down at an evening to use madVR for your entertainment, you're going to watch movies and not look at test patterns. That said, a good test can be movies with hard coded subtitles. They make a good compromise between artificial test patterns and filmed content. They're usually very sharp, but still often have a bit of anti-aliasing in them, which makes them more suitable to sharpening tests than 1 pixel on/off patterns.
aufkrawall
10th January 2016, 20:10
Pleeease also updated Adaptive Sharpen with next build?
Could you also take a look again at strength/brightness differences with AS in madVR/media player shader?
If not, of course I can test it again. :)
madshi
10th January 2016, 20:14
madVR v0.90.0 released
http://madshi.net/madVR.zip
* added support for 3D decoders (IMediaSample3D)
* added support for 3D frame packed playback via HDMI 1.4+ (requires win8.1+)
* added support for native 10bit 4:2:0 DXVA decoding (+ scaling)
* added "Reconstruction" chroma upsampling algorithm (replaces NEDI option)
* updated SuperRes algorithm for chroma upscaling
* replaced luma upscaling "linear light" with "sigmoidal light" option
* sharpen edges is now ever so slightly brighter than before
* updated AdaptiveSharpen to version 2016-01-07
* fixed: D3D11 presentation crashed NVidia driver if 3D vision was enabled
* if DCI-P3 3dlut isn't selected, BT.2020 3dlut is used instead (if available)
* if BT.2020 3dlut isn't selected, DCI-P3 3dlut is used instead (if available)
http://madshi.net/icon_redBalloon.gifhttp://madshi.net/icon_greenBalloon.gifhttp://madshi.net/icon_blueBalloon.gif
Finally we have 3D playback support for 3D Blu-Rays!!
In addition to madVR v0.90.0 you will also need to use this latest LAV special build:
https://files.1f0.de/lavf/nightly/LAVFilters-0.67.0-54.exe
Please say thank you to nevcairiel for being willing to implement 3D splitting and decoding, even though his personal interest in 3D playback is not very high. FWIW, this LAV build is a test build, not a release build, and it has a few limitations:
1) It currently only supports 3D MKV files created by MakeMKV. Support for 3D m2ts files will be coming soon, though.
2) Decoding is done by using the Intel Media SDK. So an external Intel DLL is needed, which the installer downloads automatically.
3) It's a very first build, so a few bugs may still exist.
One note to NVidia users: If you have 3D Vision enabled, then the NVidia driver will try to convert 2D movies to 3D when using D3D11 for presentation. This actually works, but how good the conversion is I don't really know. Just be aware that you should disable 3D Vision for 2D movies if you want to watch them in 2D.
The new "Reconstruction" chroma upsampling algorithm is somewhat related to "Bilateral" in that it tries to use the luma channel as a guide to improve the chroma channel quality. However, "Reconstruction" should be a bit more reliable than "Bilateral", showing fewer artifacts and not completely falling apart with some clips. On the other hand, if Bilateral works, it's almost unbeatable in its quality.
"Reconstruction" is based on feisty2's "Chroma Reconstructor", especially the "sharp" and "placebo" options. The default "soft" option is heavily modified by me and optimized for better performance and persistance against artifacts. The "sharp" and "placebo" options often produce very good quality, but sometimes they produce artifacts similar to Bilateral, sometimes not as bad as Bilateral, sometimes even worse. So my recommendation is to use the "soft" variant.
DragonQ
10th January 2016, 20:33
If I set Chroma to "Reconstruction", the stats say it's using "Jinc". :/
madshi
10th January 2016, 20:51
If I set Chroma to "Reconstruction", the stats say it's using "Jinc". :/
That's just a cosmetical error. Will be fixed next weekend. It's really using "Reconstruction".
aufkrawall
10th January 2016, 21:09
Amazing changelog!
With my sh*tty cartoon samples full of ringing and other artifacts, the new chroma reconstruction looks very good with the soft setting.
To which other algorithm might the performance hit be compareable?
huhn
10th January 2016, 21:19
there is a new auto scaling OSD feature right?
i don't see it in the changelog.
nevcairiel
10th January 2016, 21:20
there is a new auto scaling OSD feature right?
i don't see it in the changelog.
That was in the previous version already.
aufkrawall
10th January 2016, 21:23
With what bitdepth does the DXVA2 10 bit scaling work?
madshi
10th January 2016, 21:33
Amazing changelog!
With my sh*tty cartoon samples full of ringing and other artifacts, the new chroma reconstruction looks very good with the soft setting.
To which other algorithm might the performance hit be compareable?
Good to hear you like it! I actually used your favorite cartoon sample as one of the test samples for fine tuning the algorithm.
In terms of performance, I would expect it to be slower than Jinc and super-xbr, but faster than NNEDI3-16.
there is a new auto scaling OSD feature right?
i don't see it in the changelog.
That was in the previous version already.
^ True, I guess I should update the changelog for previous version.
With what bitdepth does the DXVA2 10 bit scaling work?
Well, IIRC for NVidia I'm using P010 input and 16bit RGB output. Which exact bitdepth the DXVA scaler internally uses I don't know. NVidia hasn't had great DXVA scaling, though, from what I remember, so it's probably not a good choice atm, and I suppose that AMD and Intel will only start supporting 10bit scaling once they also support 10bit DXVA HEVC decoding.
aufkrawall
10th January 2016, 21:48
Good to hear you like it! I actually used your favorite cartoon sample as one of the test samples for fine tuning the algorithm.
Nice to hear it might have been helpful. :)
In terms of performance, I would expect it to be slower than Jinc and super-xbr, but faster than NNEDI3-16.
I've used NNEDI3 32 for some occasions, so I replace it with Reconstruction now (and will report back if I see anything worth mentioning).
The changes to sharpen edges to avoid darkening look good with the FineSharp test image. With the old sharpen edges I also noticed the darkening with game screenshots. Will test this again with the new algorithm.
But first an Adaptive Sharpen comparison madVR vs. MPC HC shader.
Btw: Thanks for updating it.
Manni
10th January 2016, 21:59
Amazing news for 3D support, thanks a lot to both you and Nevcairiel, can't wait to test this.
One question though, will we have a separate 3D LUT for 3D? Also at the moment does MadVR apply no LUT when playing 3D content?
nevcairiel
10th January 2016, 22:06
One question though, will we have a separate 3D LUT for 3D?
Profiles can help you.
Hopefully madshi implemented a boolean property for 3D in profiles. ;)
aufkrawall
10th January 2016, 22:13
Adaptive Sharpen strength of 1.0 via bacondither's shaders in MPC HC is mostly equal to a strength of 0.7 in madVR:
1.0 MPC HC:
http://abload.de/thumb/as1.0mpchcwds1h.png (http://abload.de/image.php?img=as1.0mpchcwds1h.png)
1.0 madVR:
http://abload.de/thumb/as1.0madvr0zssu.png (http://abload.de/image.php?img=as1.0madvr0zssu.png)
0.7 madVR:
http://abload.de/thumb/as0.7madvr70s02.png (http://abload.de/image.php?img=as0.7madvr70s02.png)
Is letting the shader run in TV levels expected to have such a huge effect?
Manni
10th January 2016, 23:05
Profiles can help you.
Hopefully madshi implemented a boolean property for 3D in profiles. ;)
Thanks, I'll have a look.
Still, it would be nice to have a 3D LUT slot for 3D.
Also, forgot to ask, is it LAV installer which downloads the intel dll, and where does it install it?
@Madshi, thanks also for the P3/Rec2020 change in the 3D LUT table, just noticed this.
Ver Greeneyes
10th January 2016, 23:12
In terms of performance, I would expect it to be slower than Jinc and super-xbr, but faster than NNEDI3-16.What about in terms of quality? Can it beat NNEDI3, or is it roughly the same at best? Thanks for the new release!
Thunderbolt8
10th January 2016, 23:37
The new "Reconstruction" chroma upsampling algorithm is somewhat related to "Bilateral" in that it tries to use the luma channel as a guide to improve the chroma channel quality. However, "Reconstruction" should be a bit more reliable than "Bilateral", showing fewer artifacts and not completely falling apart with some clips. On the other hand, if Bilateral works, it's almost unbeatable in its quality.this is about chroma upscaling, right? so you are saying that bilateral is basically the best chroma upscaling algorithm? then something doesnt work out with the bars to indicate quality, because there is clearly more sharpness and less artifacts indicated by using super-xbr
Manni
10th January 2016, 23:40
Tried the new MadVR with the latest LAV, the movie displays in 2D.
It might be because of the Intel dll, I have to install LAV on another client because I use KCP on my HTPC, then copy the content of the LAV Filters folder on the HTPC in the KCP/LAV, but it doesn't look like the Intel DLL is there.
Also unless the help file hasn't been updated, there doesn't seem to be a way to test 3D for profiles yet.
madshi
11th January 2016, 00:15
One question though, will we have a separate 3D LUT for 3D? Also at the moment does MadVR apply no LUT when playing 3D content?
Separate from 2D? And/or separate for left and right eye?
Profiles can help you.
Hopefully madshi implemented a boolean property for 3D in profiles. ;)
The "3D" profile variables is right on top of my to do list, but not implemented right now... :o
Adaptive Sharpen strength of 1.0 via bacondither's shaders in MPC HC is mostly equal to a strength of 0.7 in madVR.
Is letting the shader run in TV levels expected to have such a huge effect?
That seems like a bigger difference than expected. But then, does it matter? The key question is whether image quality is the same when using comparable strength settings?
What about in terms of quality? Can it beat NNEDI3, or is it roughly the same at best? Thanks for the new release!
It depends a whole lot on the sample you're testing with. In some samples Bilateral wins, in some Reconstruction "sharp" wins, in some NNEDI3 wins, in some Reconstruction "soft" wins. Both Bilateral and Reconstruction take the luma channel into account, while NNEDI3 does not. So if the luma channel is helpful for chroma upscaling, Bilateral and Reconstruction may beat NNEDI3, sometimes significantly. But the luma channel might be flat, or even detrimental. In the latter case Bilateral and Reconstruction "sharp" can produce bad artifacts, while Reconstruction "soft" usually at least manages to not make things worse compared to e.g. Jinc or super-xbr upsampling.
Of course it should be said that differences in chroma upscaling quality are often near to invisible. You need to pick specific scenes to really see a difference. E.g. red stuff on black background makes for a great test.
If you want to look at the luma and chroma planes separately, you can toggle between them by pressing Ctrl+Alt+Shift+F12 multiple times.
this is about chroma upscaling, right? so you are saying that bilateral is basically the best chroma upscaling algorithm? then something doesnt work out with the bars to indicate quality, because there is clearly more sharpness and less artifacts indicated by using super-xbr
As explained above, it all depends on the video sample/scene. Sometimes Bilateral and "sharp" Reconstruction can beat the living hell out of every other algorithm, and sometimes they produce nasty artifacts. I hope "soft" Reconstruction to be a good compromise.
Tried the new MadVR with the latest LAV, the movie displays in 2D.
It might be because of the Intel dll, I have to install LAV on another client because I use KCP on my HTPC, then copy the content of the LAV Filters folder on the HTPC in the KCP/LAV, but it doesn't look like the Intel DLL is there.
Requirements for 3D playback:
1) Make sure the DLL is there.
2) Make sure you have 3D enabled in the madVR settings.
3) Make sure your OS has 3D enabled in the control panel. Alternatively you can let madVR auto enable the OS 3D setting (see settings dialog) for you, when playing 3D movies.
4) You need to use Windows 8.1 or newer.
5) The current LAV test build does *not* support 3D m2ts files yet. Only 3D MKV.
If 3) or 4) are missing then you should automatically get side-by-side rendered by madVR.
rodrigo081089
11th January 2016, 00:28
A few days ago i started to have a ghosting problem with my tv while iīm using madvr.
If i watch the same movie using plex i donīt have ghosting.
Any ideas why is this happening?
Thanks
Manni
11th January 2016, 00:33
Separate from 2D? And/or separate for left and right eye?
The "3D" profile variables is right on top of my to do list, but not implemented right now... :o
Requirements for 3D playback:
1) Make sure the DLL is there.
2) Make sure you have 3D enabled in the madVR settings.
3) Make sure your OS has 3D enabled in the control panel. Alternatively you can let madVR auto enable the OS 3D setting (see settings dialog) for you, when playing 3D movies.
4) You need to use Windows 8.1 or newer.
5) The current LAV test build does *not* support 3D m2ts files yet. Only 3D MKV.
If 3) or 4) are missing then you should automatically get side-by-side rendered by madVR.
Thanks, I meant separate LUT for 3D content, so we'd have rec-709 2D and rec-709 3D (I don't think it's likely we'll have any non rec-709 3D anytime soon).
Alternatively, an option not to apply the rec-709 LUT for 3D might be enough if that's easier. It's just that the rec-709 LUT for 2D and 3D can't be the same.
Re the above, all the conditions are checked, except
1) As posted above, I don't know the name of the DLL or in which folder it's supposed to be installed. I have to install LAV on another client and then copy the LAV folders to the HTPC in the KCP folder, so if it's not there (and it doesn't seem to be), it's not present.
Otherwise,
2) 3D is enabled in MadVR settings. If I try to use the options to force the OS 3D enabling, although it shouldn't be necessary, I get a crash (I sent the bug report, please let me know if you need anything else).
3) 3D is enabled in the OS
4) I use Win 8.1 Pro x64 with MCE, but MadVR + LAV are installed in 32bits as KCP Black isn't yet available in 64bits.
5) Made a test mkv using makemkv, the created file reports stereo AVC 4.1, so all is good there.
If you give me more info about the Intel dll, I will check this.
huhn
11th January 2016, 01:16
A few days ago i started to have a ghosting problem with my tv while iīm using madvr.
If i watch the same movie using plex i donīt have ghosting.
Any ideas why is this happening?
Thanks
can you make a screen from the OSD (control+j)?
rodrigo081089
11th January 2016, 01:24
can you make a screen from the OSD (control+j)?
Problem solved, it was the hdmi 1 the problem, if i use the hdmi 2 o 3 works ok.
Thanks
Schwartz
11th January 2016, 02:37
I've had this weird thing happen where in the middle of a movie, it suddenly froze up for several seconds while the seek bar indicator kept moving. Then it stuttered a little bit as though I was watching something trying to stream and not getting enough bandwidth. Then the movie caught up to the audio in a time lapse. Look at the queue.
Edit: Happened again in an old MPEG4. I don't think this is decoder or video related.
h264 movie, madVR 0.90 x64, MPC-HC x64, internal LAV 0.66
http://i.imgur.com/lhzVW06.png
ryrynz
11th January 2016, 02:53
That's not my fault. I'm switching refresh rates based on the framerate information the decoder provides to me. If that isn't correct, then that's the decoder's fault, not mine.
Nev has this issue fixed in his nightly builds.
JohnLai
11th January 2016, 03:12
@mashi,
I can't select DXVA option for "Image Upscaling" section with v0.90.0
Warner306
11th January 2016, 03:28
Why won't you still be able to launch MPC/madVR as an external player with Kodi in a year? That's all I've ever done, even when DSPlayer had madVR built in.
My biggest objection to using MPC with Kodi is an inability to set specific audio delays for 24 Hz playback. My set-up requires this.
Otherwise, MPC is fine, but it isn't really meant for 10ft home theater use.
huhn
11th January 2016, 03:29
lol wtf?
http://privat.bahnhof.se/wb192876/Host.split.3.m2ts_snapshot_02.39_%5B2016.01.11_01.29.16%5D.jpg
latest madvr with win 10
DO NOT DOWNLOAD IT!
the creator must be fucking drunk.
wtf are you doing ?
arnt you supposed to make the renderer better?
why go back to the 80s for graphics and 16 color system?
i think i have seen this video game before?
tetris from early 80s right ;)?
this looks like a decoding issue not a rendering issue.
what type of file is that, what decoder is used and what is send to madVR.
you can find most of these information in the madVR OSD (control+j) and media info.
Warner306
11th January 2016, 03:31
lol wtf?
latest madvr with win 10
DO NOT DOWNLOAD IT!
the creator must be fucking drunk.
wtf are you doing ?
arnt you supposed to make the renderer better?
why go back to the 80s for graphics and 16 color system?
i think i have seen this video game before?
tetris from early 80s right ;)?
There are hundreds of releases of madVR, and the most recent version is for testing purposes. My system is fine. I don't think madshi would appreciate being called drunk.
What are your settings?
Warner306
11th January 2016, 03:37
Thanks for the interesting comparisons Warner. But you missed a couple of important inclusions in my opinion.
Matching grabs of the untouched source. And sharpen edges in combination with thin edges, especially since you mention yoursef that the main issue with the former is thicker lines which the latter is there to mitigate.
I've tried many times to combine sharpen edges with varying levels of thin edges and can't get it to look right. So I gave up. I think sharpen edges looks best when used alone.
None of the sharpeners are perfect; I just think SuperRes is better than the others in many ways.
MS-DOS
11th January 2016, 05:33
madshi,
0.9 reintroduced an old'ish bug with playback freezing on D3D11 ( 1 (https://www.doom9.org/showthread.php?p=1721013#post1721013) 2 (https://www.doom9.org/showthread.php?p=1721676#post1721676)).
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.