madVR - high quality video renderer (GPU assisted)

[MSL_DK]

Unfortunately I don't have access to the yCMS sources so I can't say what's wrong exactly or fix the problem myself. However, I would guess that inconsistencies in your measurements might be the problem.

I do not think so. I just got my Spyder4 swapped to a i1pro and I'm pretty sure that it makes correct measurements.

[MSL_DK]

It would be nice if someone wrote up a mini guide on how to calibrate madVR via yCMS with hfcr from scratch for people like me who are relatively new to hardware calibration and somewhat clueless.

:goodpost:

[pururin]

So now for Intel users DXVA2 scaling for both Chroma/Luma is the best choice?

Also can HD 4000 handle Bicubic75 Chroma+Lanczos3 AR Luma? I'm planning on getting one (I3 3225).

Personally, I prefer less taxing combinations that give reasonably good result (Catmull-rom Chroma+ Bicubic75 Luma in the old discussion?) to save power consumption.

[clsid]

@madshi
Would it be possible to make the default scaling settings dynamic? Then you might be able to provide a better out-of-the-box experience, certainly on weaker hardware.

I was thinking of something like this:
1) Show the graphics card name and DeviceID somewhere in madVR settings.
2) Create a topic where people can post test results for the various scaling algorithms in madVR.
Provide links to some representative sample files, so everybody can test with the same ones.
Something like:
http://xhmikosr.1f0.de/samples/2160p/ParkJoy/ParkJoy_720p50.x264.CRF23.mkv
Testers should post details like:
- graphics card name and deviceid
- windows version
- CPU
- screen resolution
- max GPU usage for the sample file(s) for the various scaling methods
3) Based on the results you can decide which sane defaults should be used for each card. I am sure some of the regulars in this topic are willing to help out to generate such conclusions for you, saving you the trouble/time.
A rule of thumb could be at most 80% GPU usage for processing 30i/60p, or maybe a bit more conservative.
And of course the heaviest algorithms should not blindly be used on powerful hardware. You could decide to choose a specific one as the max for default settings, so that there is a good balance between performance and quality.
4) Add a simple lookup table to madVR that uses the DeviceID as index and contains the default scaling settings for each card. A relatively small table should probably already suffice for listing the most popular cards.
(perhaps an external .xml file might be an alternative for an embedded table, as it would allow additions without touching madVR)
5) Use conservative defaults for unknown cards. Or perhaps use some heuristics based on GPU details such as memory/core frequency/shadermodel version/#of shader units. I dunno what kind of info you can (easily) acquire.

[ryrynz]

Already been suggested a number of times, looks to be one of those possibly 1.0 polishing features.


Once again falling into final stage fine-tuning but having MadVR perform a benchmark and auto selecting a preset would be quite cool.

[6233638]

i'm using mobility HD5650. can u suggest what setting for chroma, image up & downscale? thanks~

my setting
chorma 3 jinc AR
luma up 3 jinc AR
down Catmull-Rom AR + linearIf you can run those settings without dropping frames, I would say those are already ideal.


I'm trying to figure out a "scale" for the settings in madVR, to see what the best options are from low-end to high-end, balancing performance and image quality.

how about an audio renderer which works hand in hand with madvr to get rig of the frame drop repeat problem by resampling the audio
...
so madvr runs 100% smooth without reclock and out of the box.That's exactly what Reclock is for though?

[dansrfe]

madshi,

Is it possible to have an option to override PGS subtitle positioning? I know if you choose to do this it will be at the bottom of your list and that's ok. Just wanted to see if you deemed it worthy to enter the list in the first place. Thanks!

[madshi]

At least it looks much closer if compared to the one produced by version 0.85.1 on ION chipset. :)
I've found a little bug. Colors with DXVA scaling turned on might now be too bright by a factor of "257/256". This will be fixed in the next build. Then colors should truely be 100% identical.

and how about an audio renderer which works hand in hand with madvr
I do not have any plans to write an audio renderer.

You could add a very small wizard that simply asks what the user's GPU is and then set recommended scalars based on that. Might be easier to auto-detect though.
It's not necessary to ask the user which GPU he has, I can find out via Direct3D.

0.85.1 seems to suffer from the same problem. Also had the problem where the playback does not start with LAV Video come back. MPC-HC's decoder still seems to work fine, but I have great trouble making it 100% reproducable. I have a feeling both problems are connected. It's like a frame is requested from the dxva2 decoder and it either takes very long for it to come or it doesn't come at all.
That sounds quite weird. If you can manage to create a log which *only* has the situation in it where playback does not start at all, I'd be interested in that. If you have a monster log where playback sometimes starts and sometimes not, I'd rather pass on that because it would be hard to interpret.

Just for my information: All these issues only apply to DXVA decoding. No problems with DXVA deinterlacing and/or DXVA scaling, is that correct?

Maybe I will also create a seeking sample to better test seeking in the future, unless something like this already exists.
That might be useful.

weird, with my gt430, if i activate the madvr deinterlacing on either setting, it becomes a slideshow. However the cuvid deinterlace to 60p works perfectly. :-/
That is very weird, I've no explanation for that. Do you have an SSE4.1 capable CPU? Are you sure that cuvid deinterlacing is done with highest possible quality? You could double check by using the cheese slices test video. Most important of all: When you get that slideshow, which of the queues are empty and which are full? You can see that in the madVR debug OSD (Ctrl+J).

the chroma upsampling being done by intel/dxva2 is also a result of dxva scaling on intel?
If you activate DXVA scaling with v0.85.2, chroma upscaling is automatically also done by DXVA on all GPUs.

I do not think so. I just got my Spyder4 swapped to a i1pro and I'm pretty sure that it makes correct measurements.
I'm not saying that the measurements are incorrect. The problem might be that if you do too many measurements which are too near to each other, the measurements might not be on a straight line/curve. That could produce problems for yCMS. You could try to reduce the number of measurements. That will result in yCMS having to interpolate/guess more, but it might fix those artifacts. But I don't really know, I'm not really an expert with this.

So now for Intel users DXVA2 scaling for both Chroma/Luma is the best choice?

Also can HD 4000 handle Bicubic75 Chroma+Lanczos3 AR Luma? I'm planning on getting one (I3 3225).

Personally, I prefer less taxing combinations that give reasonably good result (Catmull-rom Chroma+ Bicubic75 Luma in the old discussion?) to save power consumption.
If "reasonably good result" and "save power consumption" are your primary concerns that using DXVA2 scaling for Intel GPUs sounds like a good solution. However, there's currently the one problem with this that Intel only outputs to 8bit RGB. So you might get some banding. But I'm in contact with Intel to get this fixed. Not sure if I can get them to fix this, but I'm trying...

@madshi
Would it be possible to make the default scaling settings dynamic? Then you might be able to provide a better out-of-the-box experience, certainly on weaker hardware.

I was thinking of something like this:
1) Show the graphics card name and DeviceID somewhere in madVR settings.
2) Create a topic where people can post test results for the various scaling algorithms in madVR.
Provide links to some representative sample files, so everybody can test with the same ones.
Something like:
http://xhmikosr.1f0.de/samples/2160p/ParkJoy/ParkJoy_720p50.x264.CRF23.mkv
Testers should post details like:
- graphics card name and deviceid
- windows version
- CPU
- screen resolution
- max GPU usage for the sample file(s) for the various scaling methods
3) Based on the results you can decide which sane defaults should be used for each card. I am sure some of the regulars in this topic are willing to help out to generate such conclusions for you, saving you the trouble/time.
A rule of thumb could be at most 80% GPU usage for processing 30i/60p, or maybe a bit more conservative.
And of course the heaviest algorithms should not blindly be used on powerful hardware. You could decide to choose a specific one as the max for default settings, so that there is a good balance between performance and quality.
4) Add a simple lookup table to madVR that uses the DeviceID as index and contains the default scaling settings for each card. A relatively small table should probably already suffice for listing the most popular cards.
(perhaps an external .xml file might be an alternative for an embedded table, as it would allow additions without touching madVR)
5) Use conservative defaults for unknown cards. Or perhaps use some heuristics based on GPU details such as memory/core frequency/shadermodel version/#of shader units. I dunno what kind of info you can (easily) acquire.
It's a good idea, but it's a rather complex thing. E.g. on Intel GPUs using DXVA scaling and deinterlacing is running in dedicated hardwired circuits, while with AMD and NVidia, DXVA stuff mostly runs on GPU shaders. So with Intel using DXVA scaling and deinterlacing shouldn't slow madVR rendering performance down much. The situation is different with AMD and NVidia. Then performance can differ a lot depending on whether you downscale or upscale, and with which scaling factor.

But the main problem is that the current scaling algorithms may not be final yet. E.g. current algorithms all run in HLSL pixel shaders. Maybe I can use CUDA/OpenCL to squeeze more performance out of the GPU, then everything could change again. So I think it's too early right now to start creating such a GPU <-> settings database.

In the long run I do plan to either make such a database, or to alternatively add a built-in benchmark which measures GPU speed and then auto-configures madVR accordingly. But this is all future talk. I still need to add several missing features first...

Is it possible to have an option to override PGS subtitle positioning? I know if you choose to do this it will be at the bottom of your list and that's ok. Just wanted to see if you deemed it worthy to enter the list in the first place. Thanks!
I think the subtitle renderer would be the better place to have such options. Soon (hopefully) the next xy-vsfilter version might replace the MPC-HC internal subtitle renderer as the best option for madVR subtitle rendering. Let's see then which options xy-vsfilter will offer and whether that'll be enough for everybody. If not, you could try convincing the xy-vsfilter dev to add more options.

[DragonQ]

It's not necessary to ask the user which GPU he has, I can find out via Direct3D.
Yeah but what I mean is, wouldn't you have to keep a big database of every card in existence this way? With a simple menu (old IGP, new IGP/old GPU, new GPU) you can be more generic.

[aufkrawall]

If you activate DXVA scaling with v0.85.2, chroma upscaling is automatically also done by DXVA on all GPUs.

Even if no luma scaling happens?

Edit: I guess not. :D
But now that DXVA logic of madVR has changed, why not making it possible to select DXVA scaling also for luma? :)

[sneaker_ger]

That sounds quite weird. If you can manage to create a log which *only* has the situation in it where playback does not start at all, I'd be interested in that. If you have a monster log where playback sometimes starts and sometimes not, I'd rather pass on that because it would be hard to interpret.

I'm still trying to create a proper log. I have the feeling that the debug version behaves somehow different - read: better - than the normal version. Is that possible?

I tried to create a similar situation by playing a 1080p60 file, which the HD5850 is too slow to handle:
http://www.mediafire.com/?ffwpozffc2gkhyp
The symptons are the same.

I'll keep trying to create a proper sample but it really proves to be difficult.

Just for my information: All these issues only apply to DXVA decoding. No problems with DXVA deinterlacing and/or DXVA scaling, is that correct?

Just testing DXVA2 decoding here. No deinterlacing or DXVA2 scaling going on.

[sneaker_ger]

Back to Cat 12.9, first video: transparent window, no start.
Switch to [debug]: works fine. :mad:

[ajp_anton]

Even if no luma scaling happens?

Edit: I guess not. :D
But now that DXVA logic of madVR has changed, why not making it possible to select DXVA scaling also for luma? :)Why not? DXVA scaling now outputs RGB, which it can do whether there's luma scaling or not.
And "also for luma"? It's currently *only* for luma (which automatically does it for chroma as well).

edit: I just realized, my overlayed start menu has been fixed. If it's in your list of unresolved low-prio bugs, you can forget about it.

[Hwasin]

If you activate DXVA scaling with v0.85.2, chroma upscaling is automatically also done by DXVA on all GPUs.
This does not seem to be true in any fullscreen mode for me. Using Intel HD3000 in a optimus system with 540m

The test I did was to set chroma with Jinc + AR. In windowed mode, rendering time is 9ms. In fullscreen mode, it's 60ms.

[khanmein]

If you can run those settings without dropping frames, I would say those are already ideal.


I'm trying to figure out a "scale" for the settings in madVR, to see what the best options are from low-end to high-end, balancing performance and image quality.

dropping/delay frames impossible 0. once i start play BD-RMVB (DXVA-CB, NV12 4:2:0)
@drop frame 4
@delay frame 1
once i alt+tab full screen or adjust the seek bar drop/delay frame will increase slightly & stay at there as long i didn't pause or click forward/backward.

i noticed when start playing MKV+FLAC, the mpc will delay & hang for less than 15 sec with black screen. after that it play smoothly.

[ajp_anton]

This does not seem to be true in any fullscreen mode for me. Using Intel HD3000 in a optimus system with 540m

The test I did was to set chroma with Jinc + AR. In windowed mode, rendering time is 9ms. In fullscreen mode, it's 60ms.And what about if chroma upscampling is set to bilinear or nearest neighbor?

[Hwasin]

And what about if chroma upscampling is set to bilinear or nearest neighbor?
I don't know how to tell the difference. But upon further testing. This only happens with 1920*1080 material. My screen is 1920*1080.

It doesn't use DXVA2 scaling when luma scaling is nor used.

[Mangix]

Maybe I can use CUDA/OpenCL to squeeze more performance out of the GPU, then everything could change again.I thought that CUDA as well as OpenCL didn't expose any graphics related functionality like textures and whatnot but did allow GPGPU stuff like password cracking.

[Heuer]

I seem to be having problems with 85.2 - it is causing sound breakup on the centre channel. Reloaded 85.1 and everything was back to normal. Tried this iteration three times with the same result so I am back to running the earlier release. Any suggestions?

Setup - i3, GTX650Ti, W7, MPC-HC, LAV + MadVR + Re-clock. Break up gets worse as video (720p was the tester) progresses.

[madshi]

Even if no luma scaling happens?
This does not seem to be true in any fullscreen mode for me. Using Intel HD3000 in a optimus system with 540m

The test I did was to set chroma with Jinc + AR. In windowed mode, rendering time is 9ms. In fullscreen mode, it's 60ms.
DXVA scaling is only active if the video needs to be scaled. If DXVA scaling is active, chroma upsampling is being done by DXVA, too. If the video doesn't need to be scaled, chroma is still upsampled by the madVR algorithms.

But now that DXVA logic of madVR has changed, why not making it possible to select DXVA scaling also for luma? :)
Well, I guess it would be possible. But I somehow doubt the usefulness of using DXVA chroma upsampling with non-DXVA luma upscaling. So I wonder whether I should invest the development time to make this combination work.

Back to Cat 12.9, first video: transparent window, no start.
Switch to [debug]: works fine. :mad:
That's bad. I'll try to reproduce this on my development PC. You're using win7, right?

dropping/delay frames impossible 0. once i start play BD-RMVB (DXVA-CB, NV12 4:2:0)
@drop frame 4
@delay frame 1
once i alt+tab full screen or adjust the seek bar drop/delay frame will increase slightly & stay at there as long i didn't pause or click forward/backward.
Try activating the "delay playback start until queues are full" in the madVR settings. That might get rid of the frame drops when starting the video.

i noticed when start playing MKV+FLAC, the mpc will delay & hang for less than 15 sec with black screen. after that it play smoothly.
Which MKV splitter and which FLAC decoder are you using? Try madFlac as an alternative, if you haven't already...

I thought that CUDA as well as OpenCL didn't expose any graphics related functionality like textures and whatnot but did allow GPGPU stuff like password cracking.
Both CUDA and OpenCL (1.2) have interop functionality to Direct3D9 which in theory allows accessing D3D textures. However, it only half works at the current time and is very slow with current AMD drivers. But there's hope that this might be improved in the future.

I seem to be having problems with 85.2 - it is causing sound breakup on the centre channel. Reloaded 85.1 and everything was back to normal. Tried this iteration three times with the same result so I am back to running the earlier release. Any suggestions?

Setup - i3, GTX650Ti, W7, MPC-HC, LAV + MadVR + Re-clock. Break up gets worse as video (720p was the tester) progresses.
Are you using anything DXVA related? Does it help if you disable those? Does madVR drop any frames while you get audio breakup? In theory madVR does not have anything to do with audio at all. This might be a result of how DXVA/Direct3D demands resources from the CPU, maybe not leaving enough resources to the audio driver? Does your CPU run near 100% when this problem occurs? You could also check DPC latency, there are test tools available for that.

[dansrfe]

While DXVA2 is selected as the decoder in LAV Video and a file is playing, if MPC-HC's window is dragged to another screen then the video size resizes to what MPC-HC originally started with. This doesn't happen when software decoding is selected though.

[Toku]

Just noticed that It's pretty difficult to see progress in the FSE seekbar when you're a bit back from the monitor unless the screen is pretty dark. Is it possible to get the progress color darkened or something? Obviously isn't anything major, and I seem to remember you said that you wouldn't rethink the presentation until v 1.0, but just thought I'd mention it.

[THX-UltraII]

Since that madVR is very mature already I think it might be usefull that a WIKI / manual will be created for madVR. I do not have the knowledge for this unfortunately.

[pandy]

I have small idea - perhaps not very smart - is there any chance to add display support for YCbCr data without conversion to RGB on RGB output - this can provide capability to change RGB analog output to YPbPr output - very simple adapter (perhaps some buffer only, perhaps only some caps + sync combiner) should be enough to connect any graphic card to YPbPr input of TV (one one typical video modes need to be set anyway) - in normal conditions people need to buy/build ( VGA RGB to YPbPr converter (http://forums.benheck.com/viewtopic.php?f=20&t=36782) ) special converter from RGB to YPbPr. With such settings - i.e. RGB used as YPbPr output only sync combiner will be required.

[petri234]

Does this occur with all 23.976p movies for you, or just with some? Does it e.g. depend on the codec? Have you updated to the latest LAV version? I've not heard about such instability by anyone else yet, so I wonder why it only seems to affect you. Maybe it's just with some specific video files?



I checked, and it did indeed occur with every movie that is 1080/23.976p. Updating to the latest LAV filters did the trick though, so it must have been on their end. Thanks!

[hannes69]

Can you guys please test the following:

(1) Use software decoding and e.g. Bilinear scaling.
(2) Use native DXVA2 decoding and e.g. Bilinear scaling.
(3) Use software decoding and DXVA2 scaling.
(4) Use native DXVA2 decoding and DXVA2 scaling.
I use AMD HD4550 with Windows7/64bit.
Colors in (2), (3), (4) are the same but different from (1). Especially green is much too oversaturated. (1) stays the same by using copy-back-decoding instead of software.
DXVA-Deinterlacing works as intended, no change in colors.
Interesting: using native decoding instead of copy-back lowers cpu load as expected but as well gpu load! Furthermore dxva2 upscaling has about the same gpu load as Mitchell-Netravali.


The quote refers to 0.85.1

Redone the test with 0.85.2:
Now (1), (3) and (4) are the same, (2) is different (in the same way with oversaturated green like in 0.85.1). So using native decoding without dxva scaling is still broken (at least for my setup).
With 0.85.2 GPU load with native DXVA decoding is about 0 - 30% HIGHER than copyback decoding (depending on scaling algorithm!)

[truexfan81]

That is very weird, I've no explanation for that. Do you have an SSE4.1 capable CPU? Are you sure that cuvid deinterlacing is done with highest possible quality? You could double check by using the cheese slices test video. Most important of all: When you get that slideshow, which of the queues are empty and which are full? You can see that in the madVR debug OSD (Ctrl+J).

Madshi
this is my cpu (http://www.cpu-world.com/CPUs/K10/AMD-Athlon%20II%20X2%20245%20-%20ADX245OCK23GQ%20%28ADX245OCGQBOX%29.html)
and now that i have complained about it, it appears to be acting like when you take a car to the mechanic, it just won't make that same sound :D or in this case, a slide-show. i will report back later if it starts doing it again.

:thanks:

[nevcairiel]

AMD CPUs only support SSE 4.1 in Bulldozer and above, so no, your CPU does not qualify.

[leeperry]

Both CUDA and OpenCL (1.2) have interop functionality to Direct3D9 which in theory allows accessing D3D textures. However, it only half works at the current time and is very slow with current AMD drivers. But there's hope that this might be improved in the future.
Does that imply that Jinc might be less demanding on nvidia boards someday in the future?

[phoenixxl]

When Madvr crashed earlier today , I noticed this:

http://i.imgur.com/aA090.png

However , the correct value should be this :

http://i.imgur.com/y8zVD.png


Please consider revisiting the code that determines said value.

Friendly regards,

Phoenixxl.

[aufkrawall]

Well, I guess it would be possible. But I somehow doubt the usefulness of using DXVA chroma upsampling with non-DXVA luma upscaling. So I wonder whether I should invest the development time to make this combination work.

What if you watch a movie in native resolution? Then it will use the selected chroma scaling method (by default bilinear), right?.

If true, that's why I think an option to select DXVA chroma scaling for such situations would be a good idea since it looks better than bilinear and doesn't require (m)any ressources.

[sneaker_ger]

That's bad. I'll try to reproduce this on my development PC. You're using win7, right?

Yes, Win 7 x64.

The question is, why am I the only user to report this? I can't be the only ATI user on Win 7. So chances are you won't be able to reproduce it, I guess.

[ajp_anton]

DXVA scaling is only active if the video needs to be scaled. If DXVA scaling is active, chroma upsampling is being done by DXVA, too. If the video doesn't need to be scaled, chroma is still upsampled by the madVR algorithms.Why? Isn't chroma upscaled all the way up to full resolution (and converted to RGB) by DXVA? If the uses chooses DXVA, why change it when the luma scaling factor happens to be 1?

[6233638]

Madshi, I've just seen a new bug introduced in 0.85.2

If you are downscaling with DXVA2 and switch to anything else, it results in a green image. I have to switch to a non-DXVA2 scaling algorithm a second time to restore the correct colours.


What if you watch a movie in native resolution? Then it will use the selected chroma scaling method (by default bilinear), right?.

If true, that's why I think an option to select DXVA chroma scaling for such situations would be a good idea since it looks better than bilinear and doesn't require (m)any ressources.If you have an Nvidia card, DXVA2 scaling is just bilinear with a sharpening filter applied, and it comes at a significant performance hit compared to using just about anything else. Selecting "bilinear" in madVR runs about 10x faster, and looks better. (no ringing or other artefacts introduced)

To get a basic idea of what kind of scaling DXVA2 is using on your system, right click and save this image (http://www.abload.de/img/scaling7eklk.gif)

If you open it in MadVR and switch between DXVA2 and Bilinear scaling on an Nvidia card, there is no difference between the two, and a clear difference when using anything else, for example.


As a side note, there are some interesting things that happen when using the anti-ringing filter and/or linear light scaling with this test, and I wonder if something like this could possibly be used to help fine-tune the algorithms further. (it was also interesting to use a multi-coloured one (http://www.abload.de/img/test0yqvu.gif) to see how they were blended together) Then again, it's a completely artificial thing that may have no bearing on real-world content at all, so maybe it's pointless.

Still, it's an easy way to get an idea of what scaling algorithm DXVA2 is using, through comparisons.

[DragonQ]

Hmm it appears my new laptop comes with an nVidia NVS 5200M, as well as the Intel HD 4000 IGP. There's very little information about this GPU out there so I guess I'll have to investigate which one is best for MadVR!

[wanezhiling]

NVS 5200M is based on GT435M(GF108), a weak GPU.

[DragonQ]

Yeah but the Intel HD 4000 isn't exactly a beast either.

[DragonQ]

Madshi, how do I submit a freeze report? I'm getting freezes using the NVS 5200M in my laptop with MadVR (no issues using the Intel HD 4000 with MadVR, or either card with EVR).

[DarkSpace]

To get a basic idea of what kind of scaling DXVA2 is using on your system, right click and save this image (http://www.abload.de/img/scaling7eklk.gif)
As a side note, there are some interesting things that happen when using the anti-ringing filter and/or linear light scaling with this test, and I wonder if something like this could possibly be used to help fine-tune the algorithms further. (it was also interesting to use a multi-coloured one (http://www.abload.de/img/test0yqvu.gif) to see how they were blended together) Then again, it's a completely artificial thing that may have no bearing on real-world content at all, so maybe it's pointless.
Those images also show these "gremlins" that madshi noticed in the Jinc AR algorithms, though they're more pronounced when scaling in Linear Light and using 8 taps. Also, am I the only one who thinks that Linear Light upscaling with Jinc (AR or not) looks worse* on these images?

* I don't really know, but I was expecting at least some kind of darker grey, Linear Light scaling makes it look as if there's hardly and black in the image, at least for the black-and-white checkerboard pattern. I may be wrong, though.

Edit: Looks like I'm getting Bilinear upscaling on AMD Radeon HD 6970M when scaling with DXVA. However, I didn't pay too close attention to things like additional sharpening algorithms.

[vivan]

DragonQ, try to untick "use a separate device for presentation" in madVR settings. This happens (image freezes after some time, not madVR itself) on all Optimus systems, when using dGPU.

[DragonQ]

OK thanks, I'll try that tomrrow.

[6233638]

Those images also show these "gremlins" that madshi noticed in the Jinc AR algorithmsYes, but it's probably not useful material for that.

Also, am I the only one who thinks that Linear Light upscaling with Jinc (AR or not) looks worse* on these images?Linear light is not a good option for upscaling really.

Looks like I'm getting Bilinear upscaling on AMD Radeon HD 6970M when scaling with DXVA. However, I didn't pay too close attention to things like additional sharpening algorithms.It's really only a useful test to quickly see if the card is using bilinear or not, as that's very distinctive compared to the other scaling algorithms.

For sharpening, it's a lot more obvious with other test patterns. I don't think you would really notice it there.

[khanmein]

@madshi i'm using oldsch madFlac v1.10 + LAV splitter v0.54.1

bro, r u goin to release new update for madFlac?

should i tick delay playback start after seeking, too? thanks alot~

[pandy]

@madshi

http://forum.doom9.org/showthread.php?p=1604267#post1604267

Thank You in Advance madshi

[egur]

I'd like to ask for a feature:
Make MadVR power aware - have a combo box for selecting scaler used when laptop is on batteries.
Values can be either :
* DXVA scaler
* Bilinear (D3D)
* Same as connected to AC power.

Or just duplicate the existing propery pages for selecting the scaler(s) in power savings mode.

As for defaults, I'd rather have DXVA used for power savings mode, but maybe other people have different ideas.

[lastending]

I'm new here and can't read this topic from the beginning.
Someone can tell me how to disable scaling algorithms (chroma upscaling, image up/downscaling) please? I like to see orignal colors/sharpen of source
or can you show me some option you usually use for better? (I have source 1080p and 17" monitor + 32" TV)

[MokrySedeS]

I may be wrong but I think that you can't aviod chroma scaling.
As for image scaling - it's controlled by a player. For example in mpc-hc check this option: Menu View --> Video Frame --> Normal Size

[Heuer]

Madshi

Regarding my sound break-up issue with 85.2.

I tried running it on a different machine (i5, W7, MPC-HC+LAV+madVR+Reclock) and this time there was sound but no picture. (It always amazed me that this setup would run happily run on a machine without a discrete GPU, but it did for most material without crashing). I then tried downloading the 85.2 zip file from your 'previous versions' page rather than the header on page 1 of this thread. It worked perfectly so not sure if there is a problem with one of your zip files or links?

[lastending]

I may be wrong but I think that you can't aviod chroma scaling.
As for image scaling - it's controlled by a player. For example in mpc-hc check this option: Menu View --> Video Frame --> Normal Size

Thank you :)
i only have sb cpu and i see someone tell about to set image scaling for DXVA2, i tried and only think i see is bolder colors (it's pretty for me) and little alias

[cca]

Since my main PC died (lightning ...) I am trying to use my humble Atom netbook for media purposes, it does have HDMI. madVR is unusable in it I'm afraid. DXVA scaling results in out of order frames for a couple of seconds and eventually a BSOD. Bilinear is the only option, but it still drops frames. Only EVR Custom in MPC-HC works correctly, set in Bilinear mode too. The GPU is an Intel GMA 3600. I suspect it has rather crappy drivers too. No newer version either on either the manufacturer's site or Intel's.