xine is very slow and mplayer does not run the fs mode
Hi,
What is wrong with xine and mplayer? I have tried both the xine package from the CD and compiling from source but it is still slow. MPlayer plays fine but it does not toggle the full screen mode. I have tried using -fs and -vm for MPlayer, the first has no effect while the second won't display nicely. I am currently running Slackware 10.1 and a 32MB ATI card. Thanks, Basel Mahdi |
sounds like you either just have a wholly pants PC, or you're not using a decent video output mode. on mplayer use "mplayer -vo xv file.avi" for example, to force the use of XVideo extensions. if it doesn't work, then you don't have xv suport, which would be why it's not done automatically for you.
|
I have just tried what you suggested and mplayer gave the same error you mentioned. But why on Slackware? both of the application were working fine on SuSE 9.1-9.3
|
your xorg / XFree86 configuration is the most likely cause. run "xvinfo" and you'll presmuably see "no adaptors present" or similar. if so, you can presumably enable this per video card. I thought is was an option in xorg.conf but i can't see one.
|
Thanks acid_kewpie for your help.
xvinfo gives "no adapters present" as you said. I will take a look at xorg configuration file later and I will let you know what happens. Edit: I forget to mention that mplayer started to behave like this after I compiled kernel-2.6.11.11 but xine behaves the same on 2.4.29 and 2.6.11.11 |
What should I do now to enable the Xvideo support?
running mplayer -vo xv does not display anything as you can see from the code: Code:
bash-3.00$ mplayer -vo xv Naruto_-_134_AonE.avi Code:
bash-3.00$ xvinfo Code:
bash-3.00$ mplayer -vo x11 Naruto_-_134_AonE.avi Code:
bash-3.00$ grep xvi /etc/X11/xorg.conf Code:
# Uncomment this to disable tuning with the xvidtune client. With |
ACK!!! you're using the vesa output??? good christ, that'll kill any half decent card. vesa 2.0 is thae standard that framebuffer use, it's an extemely basic fool proof method to display something graphical on any card less than 10 years old. it's a absolute last reosrt for X, and will never support XV at all. Even a 32mb card should run xv just fine. you need to find the right drivers for your card right away. I've never had anythign to do with ATI cards, but i'd assume that the radeon driver is what you want.
|
As I said earlier , this problem appeared only after I compiled kerner-2.6.11.11. Do you think I missed some modules? What do I need to do in this case?
|
well you're explictly using the vesa driver. installing a new kernel won't change your xorg.conf.... again i don't know about ATI's drivers, but NVidia's own kernel drviers need to be reinstalled after any new kernel is added.
|
Thanks again acid_kewpie for your help.
Do you know the location where the drivers are stored? Maybe I can get the drivers from SuSE 9.3 if I know their location on the file system. |
what graphics card do you use ?
egag |
I am currently running Slackware 10.1 with a 32MB ATI card.
|
i read that in your first post, but i meant the name ?
i think you've gotto choose another driver for X instead of the vesa. --------- Section "Device" Identifier "VESA Framebuffer" Driver "vesa" #VideoRam 4096 # Insert Clocks lines here if appropriate EndSection --------- maybe try to change 'Driver "vesa" ' to ' Driver "ati" ' , and logout of X and restart it. then see if it's any better... egag |
How do I restart X?
|
From SuSE 9.3 xorg.conf
Code:
Section "Device" |
if you have an ati-rage, you can just fill-in that part in tha xorg.conf of Slack.
and make sure that in the section "screen ", the device refers to your device identifier ( "Device[0]"). then logout of X, and restart, or just reboot the pc. egag |
Thanks egag and acid_kewpie for your help.
my xorg.conf currently looks like this: Code:
Section "Device" I will try to update my xorg.conf and replace "Device[0]" and see what happens. Code:
Section "Device" Thanks again, Basel Mahdi |
no need to try the "Device[0]" thing.
it's just an identifier ( name ) that you give to the "device " now it's named "VESA Framebuffer" and your screen section refers to the device with that name. ( well the name is not covering the load ) you could rename it to anything, as long as it's referred to in the screen section. and restarting X ? i myself boot to runlevel3 ( textmode ) and use "startx" to start X so, i just click " logout " in the menu and X is stopped. then just typing "startx" again does it here. if you boot to runlevel 4 ( graph. login ) then i wouldn't know. ( i never do that... ) egag |
Quote:
|
i thought i just wrote that...
-if you login on a command line on a textscreen( all black bg with a lot of white text) --->that's runlevel 3; you use " startx" to go graphic. -if you have a colored screen to login: ---> that's runlevel 4 egag |
well X login is normally 5, not 4. most distro officially don't use 4 at all, although to be neat it's often equivalent to 5.
and to restart X in runlevel 5... just log out. that'll normally kill it, and it is then reloaded by the time you get the login screen back. you could always just zap it on the login screen anyway (Ctrl + Alt + Bksp) |
Quote:
and as Slackware is the oldest distro, i would say : 5 ( in other distros ) is often equivalent to 4. just for the record... :) egag |
Thanks again for both of you.
|
OK, so hippies use 4, real people use 5. point taken.
|
huh... ?
5 is for people on their way to 4... remember: how many roads..()..before they reach runlevel 4 ( quote Bob ) egag |
All times are GMT -5. The time now is 02:10 AM. |