Thanks for the response Roman. It has been very helpful. I have an Nvidia card. But yes I get the same results, when I frst create the Gem window I only see a portion of the image . Thanks to your suggestion I closed it and when I re-open it the full image is mapped onto the rectangle and it runs much smoother. Very strange? By the way I get the exact same results with pix_movie as pix_film. I'm getting the same result with alea.mpg as with my video file. For some reason however with my file pix_film doesn't know the length of the file , it keeps running past the final frame. Perhaps mencoder didn't build the header correctly? Thanks again for the help. Jim
On Thu, 2008-02-07 at 01:36 +0100, Roman Haefeli wrote: > hi jim > > i am not sure, but to me it sounds similar to this issue of gem's bug > tracker: > > [1] > http://sourceforge.net/tracker/index.php?func=detail&aid=1771966&group_id=64325&atid=507079 > > not sure again, but this seems to be related as well: > > [2] > http://sourceforge.net/tracker/index.php?func=detail&aid=1849190&group_id=64325&atid=507079 > > on my box, i have the problems described in [1]. not that this would be > a long term solution, but in certain cases it helped to destroy and > recreate the gemwin a second time. > > just out of curiosity: > when you watch a movie with the help of [pix_film] and the > too-slow-problem is triggered, does it show the full frame? on my box, i > encountered, that when i trigger the bug, it's not only very slow, but > it also displays only a portion of the original frame and scales it up > to the rectangle. > > roman > > > > > > > > ___________________________________________________________ > Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de > > _______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
