On Thu, Dec 02, 2010 at 12:00:51AM +0100, Michael Riepe wrote: > I can only guess here. Perhaps the reasons is that mplayer has read from > the file - which means that a significant portion, starting before or at > the current position, is cached afterwards. And since RAM is way faster > than disk, it doesn't take so long to decode the frames. When you move > farther, dvbcut should slow down again.
Sounds reasonable. I'll test for it. Odd that there is a black interval between each frame though. -- James Cameron http://quozl.linux.org.au/ ------------------------------------------------------------------------------ Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _______________________________________________ DVBCUT-devel mailing list DVBCUT-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dvbcut-devel
