Devices > Video Cards, Monitors, Televisions, and Projectors
Request for Wiki Link to madVR Guide
kstuart:
--- Quote from: glynor on December 08, 2013, 02:53:18 pm ---I think we could use a third preset, tuned to work very well with modern integrated GPUs and older GPUs that can't quite handle ROHQ, but which could do much better than ROST settings.
ROST
ROMQ
ROHQ
--- End quote ---
I definitely want to second this request.
( I just ordered an Asus Radeon HD6450 - specifically chosen partially for passive cooling and low profile needed - just to see the level of improvement over the 2009 HD4000 integrated graphics. )
--- Quote ---I prefer to sacrifice some sharpness to avoid ringing/aliasing
--- End quote ---
I think that anyone bothering to use madVR has enough of a "videophile" sensibility that they would make the same choice.
kstuart:
--- Quote from: jmone on December 08, 2013, 12:30:29 am ---Done - I've added the link to the thread on the Red October Wiki Page - http://wiki.jriver.com/index.php/Red_October#More
--- End quote ---
And I just read that page and the following is not accurate:
" Red October HQ -- Same as above, but adding madVR as the renderer. This is more processor intensive, so it only works well on pretty good CPU's -- i5 or above. "
As stated in this thread, the linked madVR guide thread, the following page and many others, madVR primarily uses the GPU (not the CPU):
http://www.missingremote.com/review/intel-hd-4600-madvr-performance
astromo:
--- Quote from: kstuart on January 05, 2014, 04:56:02 pm ---
--- Quote from: glynor on December 08, 2013, 02:53:18 pm ---I think we could use a third preset, tuned to work very well with modern integrated GPUs and older GPUs that can't quite handle ROHQ, but which could do much better than ROST settings.
ROST
ROMQ
ROHQ
--- End quote ---
I definitely want to second this request.
( I just ordered an Asus Radeon HD6450 - specifically chosen partially for passive cooling and low profile needed - just to see the level of improvement over the 2009 HD4000 integrated graphics. )
I think that anyone bothering to use madVR has enough of a "videophile" sensibility that they would make the same choice.
--- End quote ---
Nice work.
Personally, I think any plan to provide simple point-and-shoot options for the non-videophile whether it's a 3 stage or 5 stage plan is worthwhile. That way, a simpleton like me can "have a go" and give the whole thing a "suck" to "see" whether it's a lemon or a lime.
jmone:
--- Quote from: kstuart on January 05, 2014, 05:04:44 pm ---And I just read that page and the following is not accurate:
" Red October HQ -- Same as above, but adding madVR as the renderer. This is more processor intensive, so it only works well on pretty good CPU's -- i5 or above. "
....
--- End quote ---
Updated the wiki to now read:
--- Quote ---Red October HQ -- Same as above, but adding madVR as the renderer. This is more GPU intensive, so it only works well on fast, modern DDR5 based GPU's
--- End quote ---
Let me know of other changes.
Hendrik:
The big problem with madVR is that it can't be properly configured at runtime, most importantly all its settings are saved system wide and will be picked up by any other apps using madVR as well (and their settings by MC)
Say we provide ROHQ presets:
- Low
- Medium
- High
- Ultra
When are the presets loaded? Load them once into madVR settings and let the user configure it from then on if he wants?
In the same step, screw the global madVR settings and just overwrite with our preset?
As you might imagine, it still kinda violates the concept of RO, which is that everything is supposed to work out of the box, and no system-wide DirectShow settings can mess it up, or are modified by it.
Maybe I should ask madshi to give us a runtime config mode like I build for LAV, which ignores global settings, or something like that.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version