On Thu, 2004-01-22 at 10:52, Frank 'Sigi' Luithle wrote:
> a) transcode's routines for resizing and deinterlacing eat up a lot more CPU
> than AviSynth's. Especially at Pass 1 this is apparent -- I'd like to
> know why (wrong setup?)
Not necessarily related to resizing/deinterlacing, but try and tweak the
-u parameter. In some cases, bumping up (at least) the first numeric
argument increased the processing speed quite a bit for me. Don't
remember details, though.
> d) Probably it's worthwhile to port AviSynth's resizing/deinterlacing over
> into transcode. The AviSynth website states that VirtualDub's routines are
> even better optimized (they explicitely talk about resizing there even).
> Unfortunately I'm not able to do that I'm afraid...
Make sure you're comparing similar algorithms. A faster resizer usually
has poorer quality, or the other way round.
E.g. see y4mscaler which performs very high quality rescaling, but it's
not quite so fast.
http://www.mir.com/DMG/Software/y4mscaler.html
Probably the same is true for deinterlacing.
--
Florin Andrei
http://florin.myip.org/
____________________________________________________
http://lists.exit1.org/mailman/listinfo/dvdrip-users
How To Ask Questions The Smart Way:
http://catb.org/~esr/faqs/smart-questions.html
|
DOCUMENTATION
TABLE OF CONTENTS