Le 31 juil. 08 à 15:26, Daniel Stenning a écrit :
I don't know much about movie "vsp" but in the audio world one
generally
tries to work on as big a block of audio "frames" as one can get
away with
as opposed to single frames whereever this is feasible.
Actually, to deinterlace a picture, you have to go to the pixel level.
Depending on how much latency your app can get away with it is
always better
to send as big a number of frames in one go to the processor, so I
would
avoid a "one-by one" scheme unless it is absolutely necessary.
Better to
figure how many frames you can get away with sending to your de-
interlacer
in one go and do that.
Unlike as it is in the audio process, latency is not an issue in my
case since it won't be for realtime playing. It's just the conversion
of one movie file to another one.
You might also want to consider the MBS pre-emptive MT classes if
you need
the power that this gives you, but writing code for pre-emptive
threads is
fraught with dangers so beware :)
Thanks for the tip. I'll try it.
Eric.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
|