madVR - high quality video renderer (GPU assisted)

[Eyldebrandt]

Regardless of settings?

Did you have a different opinion about the old SuperRes algorithm?

Honestly, the differences between the algorithms and the color space on HQ content @ 4K or WQHD are insignificants.
And with low strength, the action is invisible.

I'm confused, because I think SuperRes is better than the 1st version, but settings are gone.

On the very 1st build,I used superRes with high quality instead of mid, and with everything @ 0.0 except strength.
Since, I never succeed to reach the same "quality" i had at the beginning.

I think sxbr is a great algo, definitly, but I'm still using NNEDI3 64 everywhere. So, The only reason why I don't use the first build of SuperRes for all day using is AdaptativeSharpen which is the best sharpener i ever seen.

Well, I know you don't want too much settings in madVR, and it will be a good thing for most users.
But it seems that here, on this particulary thread, there is a lot of dudes who are some kind of seekers.
And those seekers, if I can tell, i don't think you will succeed to pleased them all at 100% with half or less settings.

But again, you're the masterchief, and for what I'm concerned, I'll upgrade for every version, because that contribute to make madVR alive. And that is the most important.

[leeperry]

Not with madVR, no. madVR does currently not support custom shaders which change video resolutions. This is planned for a future version, but it will take some time to get there.
Figures, I was afraid so. I can wait before trying xsbr37 though, no big hurry.

What looks best to you isn't always fixed, though. One day you love a noisy picture and ask for ways to add even more grain.
Oh, do I seriously have to justify myself on this? OK here goes:
-I used to like adding tons of grain using GrainFactory3() over VGA fed to a CRT and HDMI to a Darkchip3 DLP projector because picture was extremely grainy to begin with and adding "smart" noise made the picture less "flat" so to speak.

-Regarding my recent switch from ED1 to ED2 with the same Sammy LCD LED TV, it's actually very simple: I switched from a very thin cheapo 8ft HDMI/DVI cable(BestBuy OEM brand duh) to a 4ft TOTL DVI cable with triple shielding, the thing is stiff as hell and made of solid copper wires.

We've all heard the stories that as long as TMDS gets through, it'll be 1:1 so I'm not sure whether the extreme shielding, signal quality or maybe the AMD drivers playing tricks on me such as several lossy YcbCr/RGB lossy conversions are the culprit(s) but PQ is *way* sharper over DVI. I do know that my neighbors blast me off with WiFi but the bluriness on computer fonts I assumed to be caused by 4:2:2 subsampling is now mostly history and with such a pinpoint sharp picture ED1 instantly became a no-go.

On a noisy set such as CRT or plasma, I would more than likely prefer ED1 again. Choices are good, they come in handy sometimes.

HQ downscaling is actually the scientifically and technically more correct solution. Actually, the non-HQ-downscaling implementation was broken. It did not work as it was originally intended. Still, you liked it better, which is your right. But several other users had a different opinion, *I* had a different opinion, and then add to that the scientific background and the fact that the non-HQ option was actually doing stuff wrong. All this combined led me to the decision to use HQ downscaling.
Oh, so HQ is gone for good now? The thing is that different setups might respond differently, especially the video display built-in dithering. I'll be sure to test the new settings of the latest build(being the mVR whore that I am :rolleyes:) but I would thoroughly enjoy a way to disable HQ again please, otherwise I might be stuck with .14 till mVR allows custom shaders that change video resolutions :(

So HQ looks better or worse depending on the footage and it's now forced, bleh...you even said yourself that you were not sure whether it decreased or improved PQ when you first implemented it. I would happily trade the "don't use linear light for dithering" option for "don't use HQ downscaling for SR" if any possible please, no harm done and I bet no one uses the former anymore(yes, I used to like it with my crappy 8ft HDMI cable on anime content only). GL for dithering is an equally "scientifically and technically less correct solution" AFAICT and looks laughable with any grey ramp, yet it did survive.

This is a custom reencoded Anime sample with ringing artifacts in the source. I've not compared this sample with HQ downscaling on/off. But in any case, do you really want to base your decisions on an Anime reencoding which has EE artifacts in the source already? Of course testing such sources is useful, too, but only as one of many tests.
Well, SR only takes care of upscales AFAIK and pretty much all 720p movies are reencodes in one way or another. I'd even dare saying that 99% of them are 1080p downscales. I do see the very same "hard" edges on whatever content when using NNEDI3 or sxbr though, it's fantastic for tiny videos but they both seriously try too hard for 720p@1080p to my eyes. NEDI is sharper than J3AR and yet doesn't give that nasty computerized look, please don't toss it :o

[Anime Viewer]

* added SuperRes "use alternative color space" option
* replaced SuperRes "HQ downscaling" option with new "algo" multi option[/COLOR]

All SuperRes users, please play with this new build. There are 2 new options: "algo" and "use alternative color space". I've intentionally named them in such a way that you can't know which does which exactly. I would like to hear your feedback about which settings you like.

This time the upscaling factor is less important (higher factor might make differences more obvious, though). Also this time don't try to find optimal passes/sharpness values. Instead it might make sense to dial passes/sharpness up as much as your GPU can handle, so you can better judge the differences between the various new options. Higher passes/strength values will make the differences more obvious.


I've tested a few sources, and notice a difference when switching between the different algorithms. However so far its been difficult to determine which of the looks I prefer. I think testing other sources will be necessary before I come up with a preference. Based on what I can see it almost looks like switching between algo settings was changing between Super-xBR, NEDI, NNEDI3, and something else. I almost missed that there was a algo "0" option, as I expected the options to be numbered from 1 upwards.


Hi guys. today i started watching a movie and noticed that was not smooth, i saw the stats on madvr and was showing a lot of dropped frames. tried another file and playback was smooth, so i thought it was file specifc.
i noticed that when in windowed mode playback is smooth even in 60hz mode, but when i maximize window it have the same problem than in fullscreen exclusive.
there is some pictures for explanation.
i noticed that rendering time increased drastically when in fullscreen or maximized window but only for this file. i fixed the problem by disabling double luma resolution, i was using always and nnedi3 64 neurons, but i always used this option and no problem happened before. also all my used settings i think is in the screenshots, i am using madvr v0.88.8, nvidia gtx660ti, i5 3570k, 8gb ddr3.

another question i have is an older one in fact. when i started tweaking a little more with madvr settings read that nnedi3 improves even more the image quality. i noticed that when using this option the image gets a little glitchy with some random dots appearing, i noticed that this was discussed here. what i did to fix was using the mpc x64 with madvr, i don't know if i did it right but the glitches are gone. but my question is, in current versions there is still this problem? do you guys think that nnedi3 worth the performance hit from 4ms to 16ms rendering time?


You mentioned you have problems when running in Full Screen, but all of your screen shots are in smaller than full screen windows. Take some screen captures while in Full Screen Windowed mode with CTRL+J active, and that may be more helpful in pinpointing your issue.

Your second picture the render times are higher than your movie frame interval times. Whatever settings you were using there were too taxing for your system, and that is why it had a lack of smoothness and dropped frames on that one.

16ms is still a fairly low render reading, so you could run in that setting if you choose. I'm not a fan of NNEDI3 since it leads to the fan kicking up to high. If high GPU load and having the fan running full bore aren't a problem for you then you could use the setting if you feel its giving you any better image quality. I'm not a fan of running in that sate, and feel I can get good image quality with things like Super-BR and SuperRes instead of wasting resources on NNEDI3. Often there are trade offs that come with enabling or disabling certain features, and which fits your eye may be different from what fits some of the other peoples eyes. With one setting you may have to weigh image sharpness vs image smoothness, and in another color vibrancy vs light ringing effect. Ultimately you'll have to decide what looks better to you.

[Nevilne]

quick hard sample for super-xbr chroma ar and bilateral chroma:

start at 150 sharpness, toggle between super-xbr fast ar and slow ar.


madvr.avs

BlankClip()
Subtitle("ONE, TWO, THREE, OUR CHROMA", x=-1, y=150, size=36, spc=4, font="Microsoft Sans Serif", text_color=$aa0000, halo_color=$262626)
converttoyv12.sharpen(0.4)


you can see that fast chroma ar is superior on this image, perhaps it could be a quality/performance option for super-xbr luma/image.

[tFWo]

Any performance improvements with AMD Catalyst 15.7 drivers?

Yes! :) But still slower than 13.12 :(

Render times with same settings (NNEDI64 for Chroma)
13.12. 30.8ms
15.4. 36.3ms
15.7. 32.5ms

[ryrynz]

Yes! :) But still slower than 13.12 :(


But what are the clocks doing?? Can't just look at render times.

[FireFreak111]

Does madVR support Device Rotation, and if not, does madVR have any plans to support it in the future?

[Anima123]

I just tested the new version with NEDI as the image doubler, passes 10, strength 0.30, and use alternative color space checked.

The tests focused on algos, results as follow:

algo 0 show some blocky effects on image and the quality is quite low. The higher the number, more ringing can be observed around the hard-coded subtitles in the image. I would choose algo 1 if there should be only one left.

It seems that algo 1 (algo 0 not counted) is the most ringing resistant one in case more passes are applied. I am happy with the result of 10 passes and 0.30 (maybe someone like less) with algo 1.

Just hope madshi can at least keep both passes and strength, because these two parameters has some kind connection on the effect of the images. It'd be hard to achieve an optimal balance of both, why not rather leave the freedom to the users? For beginners, a reset to default values would be helpful enough.

[Asmodian]

Does madVR support Device Rotation, and if not, does madVR have any plans to support it in the future?

It does! madVR now supports rotated displays.

If you mean noticing a tablet was rotated using the Windows API, it doesn't support it now as far as I know.

[dbcooper]

Yes! :) But still slower than 13.12 :(

Render times with same settings (NNEDI64 for Chroma)
13.12. 30.8ms
15.4. 36.3ms
15.7. 32.5ms

:thanks:

Will test myself soon.

[chros]

Wat, processing the video just runs on the normal shaders.
Processing is not decoding.
Sorry, it was my bad. Thanks for the correction.

No quality advantage, but should be produce more reliable smoothness. If the old mode works fine you, by all means use it. The new path shouldn't really be much slower, though - except maybe if you have a rather slow GPU and if your refresh rate is much higher than the movie frame rate.
Thanks for clarification, and the ongoing development!

[tFWo]

But what are the clocks doing?? Can't just look at render times.

My card (270x) never had problems with downclocking.

GPU usage with 13.12 amdocl.dll on that video is constant 71%. Using 15.7 gpu usage is constant 75%. Clocks don't change with both drivers.

[SithUK]

Madshi: you recommended I try bilinear chroma upscaler to try and resolve my issues with using a 3d lut on an old laptop. I mentioned I watch 1080p content on a 1080p screen. Is there a performance impact from chroma upscaling when watching 1080p at 1080p, ie if there is no upscaling?

What is the best way to read performance using the ctrl+j overlay. Render time? Or is it to use cpuz to monitor gpu and cpu load?

[ryrynz]

My card (270x) never had problems with downclocking.

GPU usage with 13.12 amdocl.dll on that video is constant 71%. Using 15.7 gpu usage is constant 75%. Clocks don't change with both drivers.

It's not a problem, it's a feature :P
Good to know.

[Ver Greeneyes]

Is there a performance impact from chroma upscaling when watching 1080p at 1080p, ie if there is no upscaling?Yes, chroma upscaling is needed on all videos where the chroma resolution is lower than the luma resolution, which is pretty much any video you're likely to encounter. Most content uses 4:2:0, which means the chroma content needs to be scaled to twice its original size to match the luma. On 1080p video, this means scaling from 960x540 to 1920x1080.

[xabregas]

Yes, chroma upscaling is needed on all videos where the chroma resolution is lower than the luma resolution, which is pretty much any video you're likely to encounter. Most content uses 4:2:0, which means the chroma content needs to be scaled to twice its original size to match the luma. On 1080p video, this means scaling from 960x540 to 1920x1080.


Hmm, thats why i found super-xbr on 1080p videos on 1080p screens better than Jinc for example xD

[chros]

Hmm, thats why i found super-xbr on 1080p videos on 1080p screens better than Jinc for example xD
As I said, on my GT650m nvidia mobile card, Jinc+AR is faster than super-xbr+HQAR in v0.88.14 (super-xbr+LQAR was about the same speed) watching 1080p content on 1080p display.

[xabregas]

As I said, on my GT650m nvidia mobile card, Jinc+AR is faster than super-xbr+HQAR in v0.88.14 (super-xbr+LQAR was about the same speed) watching 1080p content on 1080p display.

faster YES, but if PQ is better for me with super-xbr may jinc RIP ;) I only get few more ms in rendering with super-xbr. With NNEDI i get 3x rendering ms if i only use 16 neurons. PQ is better ofc but not as much to justify the extra gpu wattage and burn and its summer here, so super-xbr is a very good implementation, amazing quality, less ringing than the sharpest algo usually have and rendering is not a problem ;)

[pirlouy]

[...About windows 10 compatibility...] Until it's released its almost pointless looking at it. The code changes daily..
Well, it's most of all because madshi has not enough time for this. Ideally, it's the best moment to find Windows bug; developers are ready to fix things. When Release/RC status is reached, they will fix only critical stuff.

[XMonarchY]

Is 88.16 SR with Algo 0 = 88.15 SR with default settings? I can't tell much difference between "alternative colorspace" options, but Algo 1,2,3 are blurry, while Algo 0 = sharp (good) on all sources I tried. The difference is very slight though... I tried disabling SR completely since some said that doing so is like removing dirt from the screen, but all I could notice was increased aliasing when SR was disabled.

[leeperry]

So I just spent quite some time comparing .15 and .16:

-0.00 sharpness is less forgiving, I kinda liked slightly increasing it in order to hide compression artifacts but yeah OK unforgiving is good too and I'm currently sitting 80cm away from a 3500:1 32"....I guess 0.00 would be just fine from a 3 meters distance.

-I still far prefer HQ off in .15, enabling it utterly veils the picture to me. Major bottleneck at work, this is a definite no-go(using NEDI/J3AR/CR AR LL/monostatic ED2@8bit on mostly 720p content, of course the constantly dancing noise of dynamic dithering would more than likely completely hide the HQ veil and make it virtually impossible to spot - especially ED1).

-I'm well aware that my views towards that nasty HQ option would be nitpicking to anyone on this planet but then asking for impressions between HQ algos in .16 is way worse, good luck DBT'ing them for that matter lol. All algos add that same HQ veil to the picture IME and the colorspace option doesn't make any visible difference to me either.

All this said, I'm still extremely impressed by how natural PQ looks with 3 passes and 0.75 strength. I would eventually thoroughly enjoy a debug option to disable HQ in .17 but it actually sounds like NEDI might soon be tossed and SR become a silly checkbox without any knob, so I would also be totally cool with sticking with .15 and calling it a day. PQ is honestly and literally beyond all my expectations and I will happily purchase mVR should it go commercial one day :)

:thanks:

[AngelGraves13]

madshi, can we please get super-xbr for image upscaling as well as chroma upscaling?

Currently, Jinc is the best choice for upscaling unless I use image doubling, which causes a slight delay opening and maximizing videos, and it doubles or quadruples and then scales down using Spline instead of just scaling to the proper size, so it's basically doing twice as much work for no reason.

[Warner306]

madshi, can we please get super-xbr for image upscaling as well as chroma upscaling?

Currently, Jinc is the best choice for upscaling unless I use image doubling, which causes a slight delay opening and maximizing videos, and it doubles or quadruples and then scales down using Spline instead of just scaling to the proper size, so it's basically doing twice as much work for no reason.

Unfortunately, super-xbr is a form of image doubling - it can only double the image resolution. This is why it is limited to chroma upscaling (which is also a form of image doubling) and luma/chroma doubling.

A new linear scaler would be nice, though. Jinc is a little boring after years of use.

[AngelGraves13]

Unfortunately, super-xbr is a form of image doubling - it can only double the image resolution. This is why it is limited to chroma upscaling (which is also a form of image doubling) and luma/chroma doubling.

A new linear scaler would be nice, though. Jinc is a little boring after years of use.

I see. I wonder if there is also a super-xbrz based on the xbrz scaler.

Guess I'll stick to Jinc for now.

[surgical]

Greetings to all:
I use madVR with MPC-HC , LAV and ffdshow ; the latter, because occasionally use some avisynth script.
Anyway, I do it on a Nvidia GTX 570 and still have doubts about the correct color space should I use and need your wise counsel.
Currently, based on what I've learned here, I've my Nvidia in full RGB mode , LAV decoding with RGB levels "untouched as imput" and madVR in TV levels 16-235, as I'm connected via HDMI to a TV Sony KDL 32EX-500 (Bravia Engine 3) that, if I'm not mistaken, does'nt support 0-255 (although I'm not sure if this TV Works internally the signal in limited RGB or YCbCr)
It is correct my config ?
Thank you all in advance

[Asmodian]

That is correct if your TV does not support full RGB.

If you want the desktop correct as well you would need to switch Nvidia to limited RGB and madVR to full. This does reduce the quality of madVR because the GPU does a full to limited conversion which damages the video compared to madVR outputting limited range and the GPU leaving it untouched.

[Hyllian]

I see. I wonder if there is also a super-xbrz based on the xbrz scaler.

Guess I'll stick to Jinc for now.

xbr and xbrz are basically the same algorithm with slightly differencies in corner treatments. The major differencies between them are in the implementation side, as xbrz was a xbr reimplemented in C++ using paralell instructions for use in some emulators that only use CPU to upscale their framebuffers.

See this (http://filthypants.blogspot.com.br/2014/06/true-hq2x-shader-comparison-with-xbr.html?showComment=1430382548352#c8309218819721257465) post to know more about the differencies.

And Super-xBR is almost totally different than xBR. It uses a slightly modified edge detection from xbr and interpolate pixels using known linear interpolators (sinc, cubic, bilinear, etc). The edge detection is just a direction guide. And it doesn't use the corner treatment from xbr, so I can't see how a hypothetical super-xbrz would differ from the existent super-xbr.

The way I figured out how to combine the edge detection with the linear interpolation of pixels without introducing artifacts only works when exactly doubling the resolution. The same way as NEDI works. For now, if I try to scale by a non power-of-two factor, something goes wrong. Maybe it's possible and I just don't know yet. It's something to research in the future.

[Mano]

Anyone see any improvement with AMD Catalyst 15.7 compare to 13.12?

[Schwartz]

I've never seen the appeal of using an upscaler and then slapping on a 'corrective' AR algorithm. Ideally, a scaler shouldn't introduce ringing in the first place. Maybe it's so popular because the red and green bars suggest that it's the best. Remember that these bars aren't an objective assessment. I'd be curious to see each scaler's wave diagram instead. If you want to try something new, there's plenty of other upscalers. I'm a big fan of Spline 3 for upscaling and Mitchell for downscaling. SoftCubic 70-80 is great for dealing with bad encodes and old SD content.

[Hyllian]

Ideally, a scaler shouldn't introduce ringing in the first place.
Some ringing is benefic to the output. If you don't introduce it, the output will be blurred some way. The AR function is to get rid of bad ringing.

[aufkrawall]

The ringing is very obvious with lanczos/spline and afaik, the ringing filter isn't known to really do any harm.
The comparisons with super-xbr and NNEDI3 for chroma led me to the conclusion that Jinc3 AR is doing an extraordinary job.
The only disadvantage is that it can look too soft with extreme synthetic sample upscaling, but this isn't really a realistic case.

[leeperry]

The comparisons with super-xbr and NNEDI3 for chroma led me to the conclusion that Jinc3 AR is doing an extraordinary job.
The only disadvantage is that it can look too soft with extreme synthetic sample upscaling, but this isn't really a realistic case.
Agreed, J3AR hits the spot for chroma IME. But I don't like a very hard-edged chroma as it then tends to interfere with luma too much and look artificial, I kinda suspect that some encoders process it somehow in order to counterbalance the drastic 4:2:0 downsampling so there's really nothing to dig for IMHO(on live-action movies at least, not anime or test patterns eventually).

[Braum]

Madshi do you plan on introducing a frame interpolation function in Madvr ?

[surgical]

That is correct if your TV does not support full RGB.

If you want the desktop correct as well you would need to switch Nvidia to limited RGB and madVR to full. This does reduce the quality of madVR because the GPU does a full to limited conversion which damages the video compared to madVR outputting limited range and the GPU leaving it untouched.

Many thanks Asmodian

[aufkrawall]

Suggestion: Could we have a checkbox for image enhancement to just enable it if no luma upscaling is applied?
This would be useful to prevent sharpening of sharpening artifacts when also using it as an upscaling refinement.
I think it would be neat to help NNEDI3 with AdaptiveSharpen, but I don't want it combined AdaptiveSharpen of image enhancements, which on the other hand is neat to fight chroma blur a bit.

[James Freeman]

Madshi do you plan on introducing a frame interpolation function in Madvr ?

Did you try SVP?
I would love to have a quality interpolation algo in madvR in the future myself.

[aufkrawall]

Some more NNEDI3 vs super-xbr doubling test. Sorry about the image size, I don't know how to crop always exactly the same pixels.
However, I could do this in future if someone explained this to me. :)
720p -> WQHD, Jinc3AR chroma

super-xbr 100 is sharper than NNEDI3 64, but ringing gets more obvious and lines aren't as clean.
NNEDI3 64:
http://abload.de/thumb/nnedi364t9pa0.png (http://abload.de/image.php?img=nnedi364t9pa0.png)

super-xbr 100:
http://abload.de/thumb/super-xbr100x4p8n.png (http://abload.de/image.php?img=super-xbr100x4p8n.png)

With AdaptiveSharpen of 0.2 as an upscaling refinement for NNEDI3, the image still looks natural and clean, but is sharper than super-xbr 100 without sharpen:
http://abload.de/thumb/nnedi364as0.2ur0zpyu.png (http://abload.de/image.php?img=nnedi364as0.2ur0zpyu.png)

Edit: as a reference, the original frame:
http://abload.de/img/frame6ro6g.png

I also notice the worse line reconstruction of super-xbr e.g. with clothes of news speakers.
Even though it's "just" doubling, the advantage of NNEDI3 is already noticeable.

[leeperry]

Oh you nail it, indeed sxbr rings a lot....I was hoping that lowering its strength and increasing the SR sharpness could be helpful but maybe not, I still wish I could try sxbr37(25 is too soft and 50 rings a lot) on untouched DVD material though as temperature is seriously too hot around here these days to run NNEDI3 anyway. For now I slightly increase the SR softness in .15 in order to somewhat tame down the sxbr50 ringing.

[aufkrawall]

Too hot for NNEDI3? :eek: :D
I remember my 780 Ti getting loud with NNEDI3, the MSI Gaming design was too weak for the power consumption to remain silent.
With a MSI Gaming 970, you can set a manual fan curve so that it remains close to totally silent, if you don't mind high VRM temperatures and some coil whine.

[leeperry]

...and HDD temperature going up as well, I can keep my o/c HD7850 fairly silent as long as NNEDI3 isn't on.

[Braum]

Did you try SVP?
I would love to have a quality interpolation algo in madvR in the future myself.

Yeah I also tried AMD Fluid Motion, Interframe (which use svpflow), dmitrirender.

Interframe, dmitrirender and AMD Fluid Motion are great but I would love an integration in madvr.
Something of great quality based on madshi experience and user feedback.

[Mano]

Sub was late so i downloaded raw. Then i notice in the subbed version there are shudders when camera move while there no such thing in the raw file.

I cut it with [ffmpeg -i shudder.mkv -ss 00:04:20.0 -c copy -t 00:00:08.0 cut.mkv] (not sure if this is the correct command to preserve everything).

shudder (https://drive.google.com/file/d/0B6_FDn5cW8h3cTdmX01udHlRY0k/view?usp=sharing)
no shudder (https://drive.google.com/file/d/0B6_FDn5cW8h3RVp0OFNEbDdzQm8/view?usp=sharing)

So is it my side problem or the encoder?

[tFWo]

Sorry about the image size, I don't know how to crop always exactly the same pixels.
However, I could do this in future if someone explained this to me. :)


I use GIMP for this.

Printscreen -> Paste the first image

Change madVR settings

Printscreen again -> Paste as NEW LAYER over the first one

Repeat if necessary.


Check if all layers are selected. Crop.

Now select each layer separately. "Copy visible" each one and paste as NEW IMAGE.

Export each image as PNG.

[aufkrawall]

I just tried a bit around with AdaptiveSharpen vs. FineSharp as upscaling refinements, and I have to say that I now understand why some people describe FineSharp as pure destruction.
It increases ringing in a very unpleasant way, but you need need a lot of strength to make it actually sharpen things noticeably.
With AdaptiveSharpen, you can use much smaller values and it will really sharpen areas which actually need the sharpen. It also doesn't suffer by ringing like FS in LL.
Some textures still get brighter, but probably this is how sharpen just works to some degree?

[JarrettH]

Maybe not everyone's source needs sharpening or there is no detail to bring out :D

[AngelGraves13]

I'm really liking super-xbr at 50 for chroma and image doubling with bilinear upscaling/downscaling. Upscaling DVDs with Jinc AR looks pretty terrible, but Bilinear hides the source artifacts quite well. Sharpness is nice, but not if it makes the videos look worse.

I'm basing this on watching Batman: The Animated Series.

[aufkrawall]

Thanks, tFWo. Will try it out.

Phew, I'm not really good in judging quality of SuperRes for filmed material. I'm lacking samples for which I'd really know at what I'd have to pay attention to.
At least I wouldn't choose algo 2 because of the softness and between 1 and 3, I don't see a real difference with 720p content I've quickly thrown at it. But since 1 tends to make some colors to bright with cartoons, maybe there's no good reason not to use 3?

New SuperRes still improves sharpness with the corresponding parameters, I don't agree that the image would look "dirty" with it.

It's neat to improve the result with any non-NNEDI3 scaler for filmed material. But I honestly rather use NNEDI3 + AS. ;)

[MistahBonzai]

Greetings to all:
.
.
.
I'm connected via HDMI to a TV Sony KDL 32EX-500 (Bravia Engine 3) that, if I'm not mistaken, does'nt support 0-255 (although I'm not sure if this TV Works internally the signal in limited RGB or YCbCr)
It is correct my config ?
Thank you all in advance
I scanned through the users guide (https://docs.sony.com/release/KDL32FA600-EX301-EX400-EX401-EX500-EX501.pdf) and although no mention was made specifically of a 'full range RGB' setting I did note the presence of an analogue 'VESA' RGB compliant connection for a PC which implies full range RGB. Now this may not be the case with HDMI unless so noted. In the end most all displays utilize RGB to the final display processing stage.

I have a run-of-the-mill (KDL40w3000) 8 YO 40" Sony Bravia and it provides selection of either full range or limited RGB under "Video Options">"RGB Dynamic Range" for each of the HDMI inputs. YMMV :)

[JarrettH]

When image doubling, does chroma upscaling happen before chroma doubling?

In that case, would the chain look like...

chroma > super-xbr (chroma upscaling) > super-xbr (chroma doubling)

[QBhd]

Anyone see any improvement with AMD Catalyst 15.7 compare to 13.12?

Nope... just tried 15.7 and madVR can still push my GPU further with 13.12

QB