I have spent a lot of time experimenting with mad-vr and lav trying to find the optimal settings for my GTX 1050Ti which outputs to a 1080p projector. Settings for higher resolution displays will be very different, but as 4k projectors are currently so expensive, for a truly “home cinema” experience 1080p is the limit for most people.
The first thing to do in madvr is to set up profiles for different resolution videos — 1080p videos will require far less work than much lower or higher resolutions, जैसे. 360पी (upscale अच्छी तरह से करने के लिए बहुत काम की जरूरत है) या 4320p (takes a lot of decoding). मेरे पास भी है 2 different low-resolution profiles, one of which gets filtered by file extension so I can use different settings for particularly low quality old divx videos.
आगामी, spend some time reading an up-to-date article about all the settings. Many guides get out of date as the available settings change so make sure the information is up-to-date.
कुछ useful information on which decoding mode to use in LAV is available. I recommend DXVA2 Native (copyback नहीं)
Fundamentally, madvr is processing lots of frames per second. So it can’t spend very long on each frame to maintain smooth playback. Render times over 40ms will almost certainly result in dropped frames. The frame rate of the content will also matter: 60एफपीएस 24fps तुलना में बहुत कठिन काम है. You may want to have different profiles for different frame-rate content.
| फ्रेम रेट | Maximum render time |
|---|---|
| 60एफपीएस | 16एमएस |
| 50fps / 48fps | 20एमएस |
| 30एफपीएस | 33एमएस |
| 25fps / 24fps | 40एमएस |
आकार के संदर्भ में, I group them as there are a lot of different potential sizes. Very little content is in 4:3 अनुपात, so in most cases the content will be either 16:9 या उन्हें लेटरबॉक्स किया जाएगा
SD content is usually 360p, 480पी या 576p. As 360p is so rare I focus on 480p content for SD as settings suitable for 480p60 will cope with 576p as well. I then have categories for 720p, 1080पी, 2160पी और 4320p.
कैसे कभी, I recommend using the width of the content, rather than the height in processing rules. व्यापक प्रारूप आपके सामने आ जाने की संभावना है, जो UltraPanavision70 है 2.76:1. Using this aspect ratio would see 720p content have an actual resolution of 1280×464. Many videos in these wider formats have had the letterboxing cut off, and the problem of defining sizes begins…
There are formats below 360p but you are very unlikely to have any watchable videos in those formats.
| प्रारूप | typical height | typical width |
|---|---|---|
| 360पी | 360 | 640 |
| 480पी | 480 | 640–854 |
| 576पी | 576 | 704–720 |
| 720पी | 534–720 | 960‑1280 |
| 1080पी पूर्ण HD | 800‑1080 | 1440–1920 |
| 4कश्मीर 2160p UHD | 1600–2160 | 2880–4096 |
| 8कश्मीर 4320p SUHD | 3200–4320 | 5760–8192 |
इसलिए, to be comprehensive we need rules for both width and height of the video. Any video with a height greater than 2160 or a width greater than 4096 will have to be regarded as greater than 4k, इसलिए हम 8k के रूप में यह इस तरह मानते हैं, और इसी तरह
| प्रारूप | minimum height+1 | minimum width+1 |
|---|---|---|
| 4320पी | 2160 | 4096 |
| 2160पी | 1080 | 2048 |
| 1080पी | 720 | 1280 |
| 720पी | 576 | 720 |
| एसडी | 0 | 0 |
इसलिए, the following set of rules would do the job to group by both resolution and to split into 4 framerate groups (59–60fps; 47–50fps; 29–30fps; 23–25fps)
You may well wish to use a smaller number of groupings as it is likely you will get a lot of overlap in settings with some of these settings. I find that I only need to split by framerate for the lower resolutions.
अगर (deintFps > 50) तथा ((srcWidth 4096) या (srcHeight 2160)) "4320p60" बाकी अगर (deintFps >= 47) तथा ((srcWidth 4096) या (srcHeight 2160)) "4320p50" बाकी अगर (deintFps >= 29) तथा ((srcWidth 4096) या (srcHeight 2160)) "4320P30" बाकी अगर (deintFps 29) तथा ((srcWidth 4096) या (srcHeight 2160)) "4320p25"
I will continue to tinker and optimise my own settings, and whenever I have found improvements I will update them below.
My settings are as follows
“Hi James I realise it has been a long while, but I just checked this on windows 11 (build 23H2)…”