Log in

View Full Version : Hmm, MS Vista = 24pct slower encodes ?


halsboss
24th February 2007, 14:53
Sorry, "server too busy" and firefix froze on last post.

http://forum.videohelp.com/viewtopic.php?p=1663338#1663338
http://www.tomshardware.com/2007/01/29/xp-vs-vista/

...lack of support for the OpenGL graphics library under Windows Vista. This is something we expected, and
we clearly advise against replacing Windows XP with Windows Vista if you need to run professional graphics applications.

We are disappointed that CPU-intensive applications such as video transcoding with XviD (DVD to XviD MPEG4) or the MainConcept H.264 Encoder performed 18% to nearly 24% slower in our standard benchmark scenarios. Both benchmarks finished much quicker under Windows XP. There aren't newer versions available, and we don't see immediate solutions to this issue...

Does this mean AVIsynth runs slower ?

Alain2
24th February 2007, 16:35
Well to me it's a bit obvious that an OS like vista requiring higher specs computers than XP because it is eating a lot more cpu and memory just for its own running environment is therefore not helping the other processes that would need resources on top, like avisynth and others..

Manao
24th February 2007, 16:47
Two threads will help you :

http://forum.doom9.org/showthread.php?p=953621#post953621
http://forum.doom9.org/showthread.php?p=947278#post947278

The conclusions - for now :
- Vista doesn't reduce the available raw processing power, as soon as you disable aero. That means avisynth filters will be as fast.
- Something is noticably slower in the encoding chains used by Toms Hardware. It has to do with DirectShow, but whether it is DirectShow itself or one of the filter is still unknown ( somehow, zambelli doesn't find time to run the necessary tests, I myself don't have Vista, and nobody else seems to care... )

So, basically, only DirectShowSource should be slower.

Terranigma
24th February 2007, 17:18
Manao, curious.. is mt_masktools 26 a later version than 2.0a30?

Manao
24th February 2007, 17:24
Nop, it's a version for avisynth 2.6 - filters for 2.5 aren't compatible with avisynth 2.6. Feature-wise, it should be the same version as 2.0a30.

tsp
24th February 2007, 17:45
Manao: shouldn't that be filters for 2.6 aren't compatible with avisynth 2.5 as I thought the whole point about 2.6 was it should be backward compatible with 2.5 filters while adding new colorspace?

Manao
24th February 2007, 17:52
The interface file changed, so I thought it wasn't binary compatible. I actually didn't test myself, so you may be correct.