View Full Version : LAV Filters - DirectShow Media Splitter and Decoders
Pat357
23rd April 2012, 17:25
hello.
Is it possible to play an FLV with speex audio in it, in MPC? Or it has nothing to do with you?
I mean, I can play it, but get no audio.
Thanks!
You could ask Nev to look at it and check if it possible to add the "speex" format to his ffmpeg using the "libspeex" external lib.
Many FFmpeg builds have this libspeex library already added and the sources for this are public available.
(see http://ffmpeg.zeranoe.com/builds/# for example)
FDisk80
23rd April 2012, 20:55
All Nightly builds after Version: 0.50.1 – 2012/03/29 have constant stutters in video when used together with SVP (60fps interpolation).
See graph.
http://i.imgur.com/eOpwW.jpg
Going back to official version 0.50.1 from 2012/03/29 solves the stuttering problem.
http://i.imgur.com/MT5ek.jpg
egur
23rd April 2012, 22:13
LAV filters and QuickSync decoder are used for benchmarking IvyBridge at Anandtech (http://www.anandtech.com/show/5773/intels-ivy-bridge-an-htpc-perspective)
SamuriHL
23rd April 2012, 22:22
Damnit! I still can't buy one yet. This is just a tease!!!! :p I want to finish my machine. sigh.
nevcairiel
23rd April 2012, 22:22
I got one. :p
NikosD
23rd April 2012, 22:25
LAV filters and QuickSync decoder are used for benchmarking IvyBridge at Anandtech (http://www.anandtech.com/show/5773/intels-ivy-bridge-an-htpc-perspective)
The article says also no 4K support on HDMI Ivy Bridge motherboards and probably no 4K decoding support too.
WHY ?
All the previous time Intel was saying multiple simultaneous 4K x 4K streams support.
WHAT HAPPENED ?
Is it a drivers temporary limitation or an Ivy Bridge weakness ?
My main concern is the decoding support of 4K, not the motherboards limitation.
SamuriHL
23rd April 2012, 22:28
I got one. :p
You SUCK! :p I have to wait til Sunday apparently. Damn Intel!!!!!!!
nevcairiel
23rd April 2012, 22:39
My main concern is the decoding support of 4K, not the motherboards limitation.
4K decoding works just fine on IVB.
Although it is rather pointless if you cannot output it. :p
andyvt
23rd April 2012, 22:43
The article says also no 4K support on HDMI Ivy Bridge motherboards and probably no 4K decoding support too.
WHY ?
All the previous time Intel was saying multiple simultaneous 4K x 4K streams support.
WHAT HAPPENED ?
Is it a drivers temporary limitation or an Ivy Bridge weakness ?
My main concern is the decoding support of 4K, not the motherboards limitation.
IVB supports HWA 4K decoding (although oddly the QS decoder doesn't - not sure why) via DXVA2.
http://lh4.ggpht.com/-CAdcKPPbfJI/T5VQJr9MIKI/AAAAAAAAGWE/W8KiKYledc4/s500/lav4kdxva2decode.JPG
Just had to comment out some code in LAV, FWIW the ArcSoft TMT filter works too (http://www.missingremote.com/review/intel-core-i7-3770k-ivy-bridge-cpu-and-dz77ga-70k-motherboard).
andyvt
23rd April 2012, 22:44
4K decoding works just fine on IVB.
Although it is rather pointless if you cannot output it. :p
Yep, it's going to be a while before there are consumer 4K displays.
nevcairiel
23rd April 2012, 22:48
Just had to comment out some code in LAV, FWIW the ArcSoft TMT filter works too (http://www.missingremote.com/review/intel-core-i7-3770k-ivy-bridge-cpu-and-dz77ga-70k-motherboard).
I should try to make auto-detection work, but its not like there is alot of content available.
andyvt
23rd April 2012, 22:50
I should try to make auto-detection work, but its not like there is alot of content available.
It's an academic problem right now. Only really useful for reviewers :)
NikosD
23rd April 2012, 22:56
Yep, it's going to be a while before there are consumer 4K displays.
Nevcariel wasn't talking about 4K displays.
He was talking about motherboard limitation of HDMI on Ivy Bridge motherboards.
Nevcariel or someone else, can you post DXVA benchmarks of 4K clips ?
Also what is the QuickSync utilization of 4K clips during normal playback ?
You can use Intels Performance monitor to see that.
What are the benchmark figures of QuickSync 2.0 (Ivy Bridge), using my H.264 video collection ?
Thanks!
andyvt
23rd April 2012, 23:01
Nevcariel wasn't talking about 4K displays.
He was talking about motherboard limitation of HDMI on Ivy Bridge motherboards.
How useful is that feature when it's not possible to buy an HDMI displays capable of that resolution? Until that changes, this is an academic annoyance (which is why I addressed what I did).
jakmal
23rd April 2012, 23:10
It's an academic problem right now. Only really useful for reviewers :)
And people in the industry :) I have seen some people try to play 4K in VLC on a 4 x Eyefinity setup!
jakmal
23rd April 2012, 23:12
How useful is that feature when it's not possible to buy an HDMI displays capable of that resolution? Until that changes, this is an academic annoyance (which is why I addressed what I did).
Andrew, There is at least one 4K projector available for consumer purchase, the Sony VPL-VW1000ES. I am quite confident that with the Sharp announcement, they will become as common next year as the 2560 x 1600 monitors are right now.
nevcairiel
23rd April 2012, 23:13
More importantly, Intel needs to finally address the bug that doesn't reliably let you configure Full Range RGB over HDMI. They have a switch for it, but it doesn't do anything, and it resets on reboots or resolution changes ... very annoying. :p
jakmal
23rd April 2012, 23:19
More importantly, Intel needs to finally address the bug that doesn't reliably let you configure Full Range RGB over HDMI. They have a switch for it, but it doesn't do anything, and it resets on reboots or resolution changes ... very annoying. :p
Btw, where exactly in the control panel is this setting?
nevcairiel
23rd April 2012, 23:20
Btw, where exactly in the control panel is this setting?
Display -> Monitor / TV Settings. "Quantization Range"
It only shows up when you actually have a HDMI connection (or DVI->HDMI Adapter), it always gives you full range on pure DVI connections to a PC monitor.
You can trick it into using full-range RGB by creating some custom resolutions, but for some reason its being stupid about it for me, and doesn't accept a bunch of resolutions.
If i don't find a solution, i'll put my old GPU back in there, wrong black levels are a deal breaker. NVIDIA should hurry with their 600 series mid-end/low-end cards, i would get one. ;)
jakmal
23rd April 2012, 23:25
Display -> Monitor / TV Settings. "Quantization Range"
It only shows up when you actually have a HDMI connection (or DVI->HDMI Adapter), it always gives you full range on pure DVI connections to a PC monitor.
You can trick it into using full-range RGB by creating some custom resolutions, but for some reason its being stupid about it for me, and doesn't accept a bunch of resolutions.
If i don't find a solution, i'll put my old GPU back in there, wrong black levels are a deal breaker. NVIDIA should hurry with their 600 series mid-end/low-end cards, i would get one. ;)
Couple of related questions:
1. Are you able to drive 1080p50 through HDMI using the IVB system ?
2. Is chroma upsampling working well with the latest NV drivers on the Fermi cards ?
andyvt
23rd April 2012, 23:27
Andrew, There is at least one 4K projector available for consumer purchase, the Sony VPL-VW1000ES. I am quite confident that with the Sharp announcement, they will become as common next year as the 2560 x 1600 monitors are right now.
You know that's $25K?
IVB (and SNB IIRC) support 2560 x 1600 over DisplayPort, which most high res monitors also provide. You might even be able to use a DP->HDMI adapter in the scenario where it doesn't.
nevcairiel
23rd April 2012, 23:29
1. Are you able to drive 1080p50 through HDMI using the IVB system ?
Short of the wrong black levels, yes all the resolutions seem to be working.
2. Is chroma upsampling working well with the latest NV drivers on the Fermi cards ?
As good as the default algorithms can be expected to work, so i guess thats a yes. I think you're confusing AMD with NVIDIA here, i don't think i ever saw chroma issues on a NVIDIA card.
andyvt
23rd April 2012, 23:30
More importantly, Intel needs to finally address the bug that doesn't reliably let you configure Full Range RGB over HDMI. They have a switch for it, but it doesn't do anything, and it resets on reboots or resolution changes ... very annoying. :p
This issue has been raised and an RCR created. They haven't provided a timeline for changing the behavior (the current implementation is by design), but it is in the system.
jakmal
23rd April 2012, 23:31
You know that's $25K?
Yes, I have 'access' to one :) Most of the industry is developing 4K capable gear with that unit as the HDMI sink.. Outside of the home, I see there is a lot of demand for reliable 4K decode and display. A couple of weeks back, I set up a configuration with an AMD A8-3850 doing software decode (avcodec) of a 4K clip and outputting it over a 7750's HDMI port to that projector.
CruNcher
24th April 2012, 00:00
IVB supports HWA 4K decoding (although oddly the QS decoder doesn't - not sure why) via DXVA2.
http://lh4.ggpht.com/-CAdcKPPbfJI/T5VQJr9MIKI/AAAAAAAAGWE/W8KiKYledc4/s500/lav4kdxva2decode.JPG
Just had to comment out some code in LAV, FWIW the ArcSoft TMT filter works too (http://www.missingremote.com/review/intel-core-i7-3770k-ivy-bridge-cpu-and-dz77ga-70k-motherboard).
nice tests andyvt
liked especialy this one :)
http://www.missingremote.com/sites/default/files/ivbhandbraketime.jpg
http://www.missingremote.com/sites/default/files/ivbhandbrakepower.jpg
finally someone who compares this ;)
It was quiete anyoying all the time seeing reviewers show time or fps and then you had only the compare with some artificial power outputs from prime or Game runs totally useless :P
andyvt
24th April 2012, 00:09
nice tests andyvt
...
It was quiete anyoying all the time seeing reviewers show time or fps and then you had only the compare with some artificial power outputs from prime or Game runs totally useless :P
Thanks :)
andyvt
24th April 2012, 00:11
Yes, I have 'access' to one :) Most of the industry is developing 4K capable gear with that unit as the HDMI sink.. Outside of the home, I see there is a lot of demand for reliable 4K decode and display. A couple of weeks back, I set up a configuration with an AMD A8-3850 doing software decode (avcodec) of a 4K clip and outputting it over a 7750's HDMI port to that projector.
I don't mean to say that it isn't an important feature, just that it's so niche that it's mostly academic. When I can buy a 75-80" 4K PDP for $5K, then it will be a major, blocking, earth stopping problem :D
CruNcher
24th April 2012, 00:16
As we can see the Core i7-3770K is the clear winner in the time taken to convert the thirty minute 480i
Is this the same Video you used later on with MediaConverter also ?
if yes excellent (not like other reviewers who change the files from one Software to the next jeez) ;)
andyvt
24th April 2012, 00:22
Is this the same Video you used later on with MediaConverter also ?
Yep. Same file.
DragonQ
24th April 2012, 00:25
Display -> Monitor / TV Settings. "Quantization Range"
It only shows up when you actually have a HDMI connection (or DVI->HDMI Adapter), it always gives you full range on pure DVI connections to a PC monitor.
That setting works on my Core i5-430M. Always defaults to TV levels when I plug it into my mum's TV but I need to change it to PC levels to avoid black crush. It does introduce video noise though, which sucks.
CruNcher
24th April 2012, 00:32
@andyvt
How did you executed the HQV Color Up-sampling test i guess you compared the Cards on their native EVR results did you used a Player for that ?
Also the Noise test is this based on Luma and Chroma in the Intel Control Panel ?
I wish you would have compared AMDs 2nd Generation Video Research of the 7000 series here too :)
if i supply you with a test sequence could you test this on the Intel Deinterlacer on Ivy Bridge, though i guess the test system is not in your possession anymore ?
Seeing the old Generation scoring so good just let my jaw drop and i would say ATI is back though without a real competitive next Generation complete compare between Nvidia, Intel and AMD it's hard to say GT 430 is hardly comparable with the 680 and the improvements there on the Video part (though comparing Intels partly fixed function Hardware Deinterlacing with Nvidias and AMDs Shader based is not really fair so the highest Class of Cards needs to be compared to get a General idea of where everyone stands :)
andyvt i guess you know that but there are too much frame variations in the Deinterlace and Upsampling Screenshots frame accuracy is key here else this is pretty useless to compare (though even better would be full Video Compares no still frames anymore), but anyway overall on the right track :)
Midzuki
24th April 2012, 00:48
......
When I can buy a 75-80" 4K PDP for $5K, then it will be a major, blocking, earth stopping problem :D
I'd recommend a 120'' device at least :D
andyvt
24th April 2012, 01:00
I'd recommend a 120'' device at least :D
That would be nice, but the logistics behind a display/projector that large are unworkable in my current location :(
andyvt
24th April 2012, 01:12
@andyvt
How did you executed the HQV Color Up-sampling test i guess you compared the Cards on their native EVR results did you used a Player for that (screenshots) ?
Also the Noise test is this based on Luma and Chroma in the Intel Control Panel ?
I use PowerDVD for HQV-HD testing, with the settings at default levels. IMO it's not that useful because GPU vendors design for the test. For e.g. AMD has historically performed well in it, but in practice their default VPP settings are a hot mess of overdone NR, skin tone correction and other tweaks.
I whish you would have compared AMDs 2nd Generation Video Research of the 7000 series with this :)
If AMD sends me one I am more than happy to run it through the same set of tests :)
Btw this flickering of the Adaptive Contrast is a general issue ;)
"First, it should be made clear that the issue observed in the video above is not unique to Intel HD Graphics"
- pretty sure I said something similar in the video :)
This issue is a major source of frustration for WMC users, and no one wants to take ownership (IMO it's MS's issue to fix). The idea behind including it in this review (and future ones) is 1) to provide an easy documented solution to end users who encounter it and 2) raise awareness around the problem so hopefully someone does something, even if they don't really own it.
if i supply you with a test sequence could you test this on the Intel Deinterlacer on Ivy Bridge
Sure.
CruNcher
24th April 2012, 01:55
Look here http://forum.doom9.org/showpost.php?p=1554676&postcount=619
the source is on top results bellow it but i guess not much will have changed here :)
andyvt
24th April 2012, 02:42
Look here http://forum.doom9.org/showpost.php?p=1554676&postcount=619
the source is on top results bellow it but i guess not much will have changed here :)
This (http://babgvant.com/images/snapshot_2500000064.png) is MS Decoder + EVR in GraphStudioNext @native size. LMK if you wanted something different.
nevcairiel
24th April 2012, 06:50
This issue has been raised and an RCR created. They haven't provided a timeline for changing the behavior (the current implementation is by design), but it is in the system.
If its by design, its a bad design.
Why offer an option that doesn't work? Even more so, one that resets on its own all the time? :p
Anyway, its sad such a trivial issue will force me to install a GPU in this box. Well, to be honest the iGPU wasn't fast enough for madVR to be 100% reliable anyway, 720p60 content wasn't handled fast enough.
Sadly the AnandTech HTPC review didn't use 720p content, because with madVR 1080p actually has less load then 720p (1080p does not need Luma scaling)
wanezhiling
24th April 2012, 06:54
Well, to be honest the iGPU wasn't fast enough for madVR to be 100% reliable anyway, 720p60 content wasn't handled fast enough.
:(sigh..
jakmal
24th April 2012, 07:04
Anyway, its sad such a trivial issue will force me to install a GPU in this box. Well, to be honest the iGPU wasn't fast enough for madVR to be 100% reliable anyway, 720p60 content wasn't handled fast enough.
Sadly the AnandTech HTPC review didn't use 720p content, because with madVR 1080p actually has less load then 720p (1080p does not need Luma scaling)
Oho :| I thought I had taken care of luma scaling by putting in two SD streams.. So, what is the GPU loading like with 720p60 ? Any difference between software decoding and QS / DXVA fall-back ? I assume you are using the 2133 MHz DRAM...
nevcairiel
24th April 2012, 07:06
Oho :| I thought I had taken care of luma scaling by putting in two SD streams.. So, what is the GPU loading like with 720p60 ? Any difference between software decoding and QS / DXVA fall-back ? I assume you are using the 2133 MHz DRAM...
Well, 720p is more pixels to process then SD content, so it'll take more power. madVR reports rendering time of 19-20ms. At 1080p its 13-14ms for comparison.
I didn't check actual GPU loads (yet), but i did see it drop quite some frames.
This is with M-N for Chroma and Lanczos3 for Luma (my preferred settings)
I also only have a rather old driver (2598 or something, came with the board), but i couldn't find a better one on the Intel page, so stuff may improve.
Qaq
24th April 2012, 07:40
Funny thing is that with my 5450 (yeah, already ordered 7750) I only got issues with 1080p and only with present queue. I mean with prev. madVR versions and only sometimes. So I wonder what is the difference for present queue between 1080 and 720 scaled to 1080 (which plays fine)? This question is related to comments above and not to madVR itself :)
jakmal
24th April 2012, 08:05
Well, 720p is more pixels to process then SD content, so it'll take more power. madVR reports rendering time of 19-20ms. At 1080p its 13-14ms for comparison.
I didn't check actual GPU loads (yet), but i did see it drop quite some frames.
So, no difference between fullscreen windowed and fullscreen exclusive? For Andrew, FSE worked well, but in my system it was FSW..
This is with M-N for Chroma and Lanczos3 for Luma (my preferred settings)
Which of the algorithms / configurations load the GPU the most? In addition to making sure that none of the 'tradeoff quality for performance' options are checked, perhaps we should just benchmark with those algorithms.
I also only have a rather old driver (2598 or something, came with the board), but i couldn't find a better one on the Intel page, so stuff may improve.
I think both Andrew and me reviewed it with v2696, and Asus provided v2712 just after I finished the benchmarking...
nevcairiel
24th April 2012, 08:09
Which of the algorithms / configurations load the GPU the most? In addition to making sure that none of the 'tradeoff quality for performance' options are checked, perhaps we should just benchmark with those algorithms.
The "most" is Lanczos 8-tap, but its unrealistic because it has awful image quality. Just go with the 4-tap variants of either Lanczos or Spline.
I think both Andrew and me reviewed it with v2696, and Asus provided v2712 just after I finished the benchmarking...
With provided i assume you mean to you directly? Sadly their download page doesn't have anything above the 2598, and Intels 2712 download is still passworded.
egur
24th April 2012, 08:56
Is the RGB-HDMI black level issue only in IvyBridge?
My HTPC has a SandyBridge connected the same way and the black levels are perfect. I have Panasonic plasma (50" V20) with excellent black levels - makes it very easy to spot wrong settings.
I personally don't use MadVR, I use EVR.
EVR results were missing from the Anadtech review. EVR-CP provides worse results at worse performance. I don't see a reason to use it in SandyBridge or newer platforms.
8 tap Lanczos exhibits too much ringing (in upscaling). For MadVR, probably better (quality wise) to use 6 taps or even Bi-cubic.
In order to achieve Lanczos4 (8 taps) sharpness without (or little :) ) ringing, one needs a context adaptive algorithm like EVR provides. I hope MadVR will add this.
BTW, latest drivers on Intel's site is v2656.
jakmal
24th April 2012, 09:22
Well, 720p is more pixels to process then SD content, so it'll take more power. madVR reports rendering time of 19-20ms. At 1080p its 13-14ms for comparison.
I didn't check actual GPU loads (yet), but i did see it drop quite some frames.
I tested with a 720p60 camcorder clip, and the GPU utilization is between 80 and 90%, but frames are still getting dropped :( Running DDR3-1600 at 9-9-9-24 for this experiment. Software config is LAV Filters with QS Decoder, and madVR settings as quoted in the review. Driver version is v2712.
I personally don't use MadVR, I use EVR.
EVR results were missing from the Anadtech review. EVR-CP provides worse results at worse performance. I don't see a reason to use it in SandyBridge or newer platforms.
Interesting! I used EVR-CP because it is the default out of the box for MPC-HC, and it has always served me in good stead so far :) By the way, what exactly are the differences between EVR and EVR-CP ?
In order to achieve Lanczos4 (8 taps) sharpness without (or little :) ) ringing, one needs a context adaptive algorithm like EVR provides. I hope MadVR will add this.
The one provided by EVR is dependent on the drivers, I assume? Do you have any insights on whether context adaptive algorithms are being used by other GPU vendors also?
BTW, latest drivers on Intel's site is v2656.
v2712 is available here (http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=21135&ProdId=3442&lang=eng&OSVersion=Windows%207%20%2864-bit%29*&DownloadType=Drivers)
egur
24th April 2012, 09:41
I tested with a 720p60 camcorder clip, and the GPU utilization is between 80 and 90%, but frames are still getting dropped :( Running DDR3-1600 at 9-9-9-24 for this experiment. Software config is LAV Filters with QS Decoder, and madVR settings as quoted in the review. Driver version is v2712.
I'm afraid Lanczos4 is too much for IvyBridge - a mainstream and north dGPU is needed.
Interesting! I used EVR-CP because it is the default out of the box for MPC-HC, and it has always served me in good stead so far :) By the way, what exactly are the differences between EVR and EVR-CP ?
EVR uses what the driver recommends as the best algorithm. This is HW and driver specific. Different GPU can give completely different results.
EVR-CP is an open source project that implements EVR's interfaces.
Using EVR (in SNB/IVB) you'll get:
* Context adaptive scaling
* Deinterlacing and all video post processing algorithms found in the iGPU control panel.
If the display is connected to a dGPU, EVR will use that GPU's video processing algorithms including a scaler.
The one provided by EVR is dependent on the drivers, I assume? Do you have any insights on whether context adaptive algorithms are being used by other GPU vendors also?
As far as I've seen, other vendors do not have such technology. I believe they use text book algorithms like Lanczos or bi-cubic.
Context adaptive scaling was done by another company (not Nvidia/AMD) but I'm not aware of video related products.
v2712 is available here (http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=21135&ProdId=3442&lang=eng&OSVersion=Windows%207%20%2864-bit%29*&DownloadType=Drivers)
This file is password protected. I'll forward the complaints about this issue.
OEMS/ISVs can get the latest drivers and tools from Intel's Validation Internet Portal.
wanezhiling
24th April 2012, 09:43
By the way, what exactly are the differences between EVR and EVR-CP ?
http://forum.doom9.org/showpost.php?p=1570573&postcount=10488
jmone
24th April 2012, 09:46
Great review jakmal...finally one focused on HTPC use with LAV/mad. Anyway after reading it, I'm now doubtful if a CPU upgrade on my Shuttle HTPC from a i7-2600K's 3000 iGPU (needs a BIOS upgrade) for a i7-3770 4000 iGPU is going to give that much of a bump. At present I have to use non-tap scalers (eg Mitchell-Netravali) to prevent dropping frames (render queue issues) on 1080/50i/p or 60i material, and that works perfectly. While I'm not interested in OC the mem on a HTPC to get a "just works" soln (esp a Shuttle), I did read you were using the 4 Tap Lanczos scaler, how was it with 3 Taps on 1080/60i marterial - does it still drop frames?
jakmal
24th April 2012, 10:19
At present I have to use non-tap scalers (eg Mitchell-Netravali) to prevent dropping frames (render queue issues) on 1080/50i/p or 60i material, and that works perfectly. While I'm not interested in OC the mem on a HTPC to get a "just works" soln (esp a Shuttle), I did read you were using the 4 Tap Lanczos scaler, how was it with 3 Taps on 1080/60i marterial - does it still drop frames?
Default for chroma upsampling is SoftCubic. Luma algorithms are Lanczos (4-tap).
I went back to DDR3-1333 and the performance is quite bad even for the M-N algo. If you are going to use madVR, I don't suggest using DDR3-1333.
Also, 720p60 drops frames even with DDR3-1600, and Hendrik reports that it is the case even with DDR3-2133.
So, yes, lots of caveats apply to the LAV / madVR section of the review I posted.
nevcairiel
24th April 2012, 10:19
Is the RGB-HDMI black level issue only in IvyBridge?
No, it affects SNB as well, and i assume all others as well.
The config screen is just lying to you. It offers an option to switch between limited and full range, but when i do, it doesn't change the video at all, and next time i change resolution or reboot its reset to the old value. My TV is calibrated for full-range RGB, and i would like to keep it that way.
It doesn't crush blacks or anything, that part is under control, but it just doesn't send full range RGB like i want it to.
Its a simple driver problem.
I personally don't use MadVR, I use EVR.
EVR results were missing from the Anadtech review. EVR-CP provides worse results at worse performance. I don't see a reason to use it in SandyBridge or newer platforms.
EVR doesn't offer proper subtitle support, and its vsync accuracy is a mess.
This is why EVR-CP or madVR are much better, even if you lose the (limited) hardware scaler. I'm happy with my madVR configuration, imho it looks better then EVR. Not to mention that i can calibrate to fit my display 100% with madVR. :)
PS:
EVR-CP (and to some degree madVR) offer the same deinterlacing and other processing. Not that i would want any post-processing except deinterlacing.
Also, 720p60 drops frames even with DDR3-1600, and Hendrik reports that it is the case even with DDR3-2133.
Memory can only do so much. The sweet spot seems to be around 1600 or 1833, my 2133 is probably overkill, but its not like it was extra expensive.
Considering IVB is even native 1600 now, getting 1333 seems just dumb. :)
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.