I'm still trying to narrow down what the problem is
regarding my savage chip-based card, Xvideo and Xine 0.5
(beta from a few days back). Today I stumbled across the
latest version of smpeg, which comes with a basic mpeg 1
player that can handle VCD streams. I haven't used plaympeg
for some time because xine seems faster ;-). But when I
typed "plaympeg --double /dev/cdrom" a near full-screen
window popped out and started playing my VCD as smoothly as
a decent VCD player should.
The interesting thing is that plaympeg appears to be using
which plaympeg | xargs ldd | grep Xv
libXv.so => /usr/X11R6/lib/libXv.so (0x4039e000)
Since plaympeg can (apparently) use my card's Xvideo, I can
only conclude that the problem lies with xine. Using xine
locks up the machine so that only a hard reboot can fix the
On Mon, 30 Jul 2001, csj wrote:
> The interesting thing is that plaympeg appears to be using
> which plaympeg | xargs ldd | grep Xv
> libXv.so => /usr/X11R6/lib/libXv.so (0x4039e000)
> Since plaympeg can (apparently) use my card's Xvideo, I can
> only conclude that the problem lies with xine. Using xine
> locks up the machine so that only a hard reboot can fix the
> Any ideas?
well, this sounds really interesting. Have you compared the code plaympeg
uses to xine's video_out_xv code? Another interesting point would be to
find out where exactly xine hangs your machine and, of course, what's the
difference is in plaympeg's code at that point.
BTW: Do you really have the latest savage drivers installed (mentioned in
the xine howto) ?
time is a funny concept
Get latest updates about Open Source Projects, Conferences and News.