On Mon, 30 Dec 2002 02:36:20 +0100 you wrote:
> Checked out the latest changes from cvs and gave xvidix again a try.
> Still hangs and blanks the screen. But: one time a window appeared. I
> could not reproduce it but guessed, mplayerxp confuses Xfree86 most of
> the time. So I turned off accelleration for the ATI Rage XL and now
> mplayerxp works somehow with xvidix. Somehow because it runs only
> with -xp 0. All other modes gave a
> Exiting... (Not enough buffers for DECODING AHEAD! Try other '-vo'
Try '-v' key. Mplayerxp requires 5 buffers at least for decoding ahead.
Try find out how many buffers mplayerxp can alocate within of video memory
in this case.
> Now, story is not over. What happens with busmastering? If not running
> as root, just using dhahelper, it prints several
> vosub_vidix: Can't lock memory for busmastering
It's ok for non-ROOT!
> As root no message.
> When the movie is finally playing, mplayerxp constantly prints
> vosub_vidix: DMA frame is memcpy() copied
It seems that you have PCI card (not an AGP)!
Currently I'm working on this problem (I've got AIW 3DRage Pro Turbo PCI
for some period of time). BBUSMASTERING doesn't work there too :(
> which drasticly slows down the system. Commenting out the warning gains
> some speed, but mplayerxp is now slower than mplayer when using xvidix.
> And more unstable. OK, OK, I know, it is cvs code and I should be happy
> that mplayerxp finally works on my computer ;o)
Unstability in this case maybe caused only by the fact of direct access to HW.
You should now that mplayerxp has more advanced drivers which perform more
complex working with HW than mplayer.
> For the record: This is a debian/woody system running xfree 4.1.0 coming
> with woody. I only can guess, that mplayerxp does not initialize xvidix
> cleanly for my card like mplayer does.
Please keep in mind that Xvidix is only X11 front-end to VIDIX and nothing more!
there is no difference in initializing between xvidix and fbdev:vidix for example!
> Maybe I will drop in the xvidix code from mplayer to see, what mplayerxp
> a/v-syncing is all about. I remember this being my first intention with
> mplayerxp :o)
Won't work! Mplayer has too old VIDIX interface. They didn't apply my newest
changes and their drivers can't work with more than 3 frames!
(my drivers can use up to 1024 frames in video memory)