From: Miguel F. <mi...@ce...> - 2003-09-04 14:23:30
|
On Wed, 2003-09-03 at 23:35, xin...@li... wrote: > > Thanks. Now another question: what kind of CPU do I need to do this > > properly? > > > > Mine is an Athlon 1800, slightly underclocked (regular multiplier, > > slightly lower bus speed. It's running at 1400 or so.) My video > > card is a Matrox G400 and I'm using Xv. If I enable post-processing > > and choose "Greedy2Frame" (which gives me the best results) it seems > > like my machine can just barely keep up--for instance, going into the > > menu at that point causes the machine to stop displaying new frames > > for a fraction of a second. > > This is the reason, why this algorithm is called "greedy". ;) well, just for the records... the computer where it was ported/developed/tested (mine :) is an athlon xp 2000 with matrox G450. i can enable pulldown detection (it eats more cpu when it doesn't detect the pulldown - if it does the framerate is decreased), greedy2frame and even chroma filtering at the same time without using all my cpu. btw: i plan to add some small hacks to tvtime so it can use less cpu as a tradeof for quality. if anybody cares, the older deinterlace code (in XV driver) used some of the same algorithms of tvtime. those work on images at YUY2 format. however, unlike the new tvtime plugin, it did not convert the frames from YV12 (libmpeg2 output) to YUY2. so the result was less accurate but "cheaper". regards, Miguel |