소프트웨어 (rewrite) madVR + LAV CUVID + GTS450

0. The Purpose

    To know how much the madVR + LAV CUVID use the system resources in comparison with DXVA.

1. Testbed

    CPU : Intel Core2Quad Q6600 2.4Ghz No-over

    RAM : DDR2 8G

    Video : ASUS nVidia GTS450 GDDR5 1G 192 Shader Units

    M/B : Gigabyte GA-P35 DS4 (rev 2.0)

    Mon : 24" 1920x1200 S-IPS

2. Test Clip

    'Battle Field 3 - Fault Line' Full Game Trailer.

3. Player & Codecs

    DXVA = Potplayer + Arcsoft Video Decoder + EVR (C/P)

    CUDA = Potplayer + LAV CUVID + madVR

4. Let's see the result (DXVA vs CUDA)

5. Conclusions

    - madVR always needs lots of CPU usages for its sophisticated video quality.

    - madVR and LAV CUVID copy the parts of image data to system memories and work there, as a result system memory usages are higher up.

    - As madVR makes multiple passes over the frame and needs to move data back and forth between the shaders and the graphic memories, it makes graphic memory controller work harder.

    - madVR uses GPU too much explosively compared to DXVA, this might cause the bottle-neck. Maybe some clips could stutter or drop so many frames in the specific situation.

    - After all, if you hope to use madVR + LAV CUVID with nVidia graphic cards in your PC, you should be seriously concerned about your system's (overall) abilities.

    - Looking over the enhanced video qualities with the combination of madVR + LAV CUVID, all of us could accept that as a fantastic solution for nVidia HTPC users. But as you see... it's not free.