INTERACT FORUM
More => Old Versions => JRiver Media Center 18 for Windows => Topic started by: Sandy B Ridge on January 20, 2013, 05:21:24 pm
-
http://www.anandtech.com/show/6674/getting-the-best-out-of-a-ivy-bridge-htpc-windows-8-madvr-and-more/8
UI a few notches down on XBMC??
A few frame drops with ROHQ and Intel HD4000 iGPU.
SBR
-
For an AnandTech article, I find it a little bit dissapointing mainly because it is lacking detail.
He's not listing the settings for LAV or madvr on which the benchmarks are taken (well, default scaling algorithms; he should have just listed them in a table or something).
I mean its great he's spending more time with MC18 and even recommends it over other solutions like XMBC when it comes down to playback quality but I expect him to get into the gritty details when something does not work as expected. He mentions dropped frames with MC18 but he should have dived into LAV and Madvr settings and compare them to the settings the other combinations run with. As it stands now that statement is meaningless. He should have compared the settings, listed them and compared playback benchmarks between applications with the same settings. Then when you have dropped frames with MC18 and not with the other applications you have something meaningful. Stuff like that is what I've come to expect from AnandTech but this article leaves much to be desired if you ask me.
UI a few notches down on XBMC??
I tend to agree but that could soon change (https://yabb.jriver.com/interact/index.php?topic=76982.0) ;D.
-
I agree, the article lacking quite a bit of accuracy and details, instead focuses on useless details like 5% differences in power consumption depending on which codec you use - that could've been dealt with in maybe two sentences...
In a couple of places its even wrong, either because of outdated facts or just plain wrong assumptions. Usually expect more from AnandTech.
-
I agree, the article lacking quite a bit of accuracy and details, instead focuses on useless details like 5% differences in power consumption depending on which codec you use - that could've been dealt with in maybe two sentences...
In a couple of places its even wrong, either because of outdated facts or just plain wrong assumptions. Usually expect more from AnandTech.
If you have any easy corrections, send them to me (jimh at) and I'll forward them to Ganesh. Thanks.