jimbobuk
2nd January 2005, 22:03
I've been exposed to the limitedSharpen script via someone on avsforums who's managed to get it working through ffdshow with avisynth.. I'd recently upgraded my machine to an overclocked mobile athlon 2600, running at around athlon 3300 speed.. and was happy as i could now happily resize to 1920x1080 with lanczos paramter 4/5 .. this new limitedSharpen was getting a lot of people excited so i decided to try it... I am unable to even manage to get it working on its own at realtime speeds.. It seems to be a recurring problem with AMD machines.. even athlon64 machines seem to struggle to do anything good with it..
Does anyone here have any good results with an athlon machine!? I read someone using a 2600mhz celeron... surely my athlon running at 2400mhz benchmarking like a 3300mhz p4 (in some respects) should be able to do something with limitedSharpen style scripts on dvd sources?!
I'm guessing avisynth must be heavily SSE/SSE2 optimised and that intel chips just love it where as amd chips are seriously cripped to being almost twice as slow.. its frustrating but i've no more money to upgrade and for now it runs Half Life 2 well :) and as i said in the beginning it can manage to do some ffdshow stuff at 1920x1080 resizing so i get nice improvements with more sharpening artefacts than i'd perhaps like..
Thanks guys.. just curious really...
How are you guys using avisynth directly to test realtime stuff.. do you have to dvd2avi a rip to be able to add it into an avisynth script? perhaps its the layer between ffdshow and avisynth that is causing some kind of bottleneck?
Cheers
Does anyone here have any good results with an athlon machine!? I read someone using a 2600mhz celeron... surely my athlon running at 2400mhz benchmarking like a 3300mhz p4 (in some respects) should be able to do something with limitedSharpen style scripts on dvd sources?!
I'm guessing avisynth must be heavily SSE/SSE2 optimised and that intel chips just love it where as amd chips are seriously cripped to being almost twice as slow.. its frustrating but i've no more money to upgrade and for now it runs Half Life 2 well :) and as i said in the beginning it can manage to do some ffdshow stuff at 1920x1080 resizing so i get nice improvements with more sharpening artefacts than i'd perhaps like..
Thanks guys.. just curious really...
How are you guys using avisynth directly to test realtime stuff.. do you have to dvd2avi a rip to be able to add it into an avisynth script? perhaps its the layer between ffdshow and avisynth that is causing some kind of bottleneck?
Cheers