Useful information for HomeTheater PCs

[ShiningDragon]

While searching the last weeks for information to get something similar to TrueTheater HD i found a lot of sites who promised "great" things with ffdshow and avisynth. Last but not least: all of 'em seems to be only empty promises. There is nothing comparable to TrueTheater HD available. -.-

Ok, but this isn't his what i wanted to share with you. I found a website with useful informations for configuring and tweaking a htpc with different 3rd party tools:

http://www.homecinema-hd.com/intro_en.html

It is not errorfree, i guess. But this page is a good start to collect some backgroundinformations for setting up a nice htpc experience in combination with NextPVR. Some of the mentioned software (like ReClock) are already covered by our member imilne. He has some handy-dandy-useful tools for using ReClock (ReClockOrNot, RefreshRate) and additionaly a plugin called "AudioAdjust".

At the moment i am playing around with a bunch of settings and the qualitative experience is far better then my english knowledge.

Perhaps you want to try out some stuff for yourself or just collect useful informations for 3rd party stuff for our wiki.

EDIT 1:
Instead Media Player Classic Home you should use NextPVR
Instead MadVR you should stay at VMR or EVR, because MadVR isn't supported by NextPVR (afaik)
Instead AutoFrequency you should use RefreshRate from imilne (it works great!)
Instead DVDFabKey you should use AnyDVD (i don't like Fengtao; they steal code from other people and say, it's their own work and for this they want money ... a lot of money).
CoreAVC is fast ... nothing more. An awful picturequality (like all cuda based decoders), i wouldn't use it.

EDIT 2:
User of a SandyBridge CPU could tryout the latest ffdshow releases. There's QuickSync Support from an intel developer for MPEG-2, VC-1 and AVC available. But to be honest: i couldn't find out any difference. It could have something to do, that the developer isn't using the full potential of QuickSync and just copy every frame into the slow ram. CPU usage seems to be identical to the libvcodec, perhaps a bit higher.

EDIT 3:
I think the quicksync support within ffdshow is just a blender. I have enabled quicksync support on an i3-550 (clarkdale) which hasn't any quicksupport capable support and it runs (the ffdshow osd confirms it). So i think, that the ffdshow quicksync support is just a fake.