Closed GoogleCodeExporter closed 8 years ago
enable verbose debugging in gnome-mplayer and run firefox from a terminal
without any
other firefoxes open and do the test again and post the log that is generated.
Original comment by kdeko...@gmail.com
on 8 Jan 2010 at 9:52
How do I do this please? Is gnome-mplayer the same as mplayer? Where is the
config
file for it?
Original comment by systempa...@gmail.com
on 8 Jan 2010 at 9:58
I'm guessing from that comment that you may not gnome-mplayer installed.
gnome-mplayer is a wrapper for mplayer that works with gecko-mediaplayer to
play the
media files.
Run gnome-mplayer and choose Edit->Preferences [Interface] and then choose
Verbose
Debug Enabled (last option on the tab).
Then make sure gnome-mplayer will play a file. If it does not, run
gnome-mplayer from
the terminal and see if any errors are emitted.
Original comment by kdeko...@gmail.com
on 8 Jan 2010 at 10:02
Ok, running gnome-mplayer directly with the -v option is giving output:
GNOME MPlayer v0.9.8
vo = (null) ao = (null)
Running with GIO support
Master Playback is 1
Master Range is -1225354464 to -1225359372
Master Current Volume -1074910984, multiplier = -0.020375
Scaled Volume is -3065270.539822
Using volume of -3065271.00
opening /home/simon/arquake.avi
is block 0
is character 0
is reg 1
is dir 0
playlist 0
embedded in window id 0x0
opening playlist
playlist detection = 0
adding file:///home/simon/arquake.avi to playlist (cancel = 0)
getting file metadata for /home/simon/arquake.avi
Using match: type='signal',interface='com.gnome.mplayer'
Using match: type='signal',interface='org.gnome.SettingsDaemon'
Using match: type='signal',interface='org.gnome.SettingsDaemon.MediaKeys'
Proxy connections and Command connected
playing - file:///home/simon/arquake.avi
is playlist 0
current size = 0 x 0
Changing window size to 720 x 540 visible = 1
mplayer -quiet -slave -identify -volume -3065271 -framedrop -vf-pre
yadif,softskip,scale -noconsolecontrols -noidle -stop-xscreensaver -osdlevel 0
-nomouseinput -nocache -wid 0x480004c -ss 0 -ass -noembeddedfonts
-ass-font-scale
1.00 -channels 2 -vf-add screenshot -af-add
export=/tmp/mplayer-af_exportiusjii:512
/home/simon/arquake.avi
Spawn succeeded for filename /home/simon/arquake.avi
current size = 720 x 540
MPlayer SVN-r29776-4.4.1 (C) 2000-2009 MPlayer Team
ERROR: The volume option must be >= -1.000000: -3065271
Thread completing
shutting down threadquery for /home/simon/arquake.avi since threaddata->done is
TRUE
Why are we passing crazy volume options around?
Original comment by systempa...@gmail.com
on 8 Jan 2010 at 10:06
Ok now I'm really confused. It seems that enabling debug mode caused it to start
working in Firefox. But playing files locally with gnome-mplayer is still
passing
crazy volume options. I redownloaded the file using firefox (which is now
playing it
fine embedded), just in case, but that doesn't play locally either.
HUH?
Original comment by systempa...@gmail.com
on 8 Jan 2010 at 10:13
Wow... something is messed up with your libasound or your sound driver. Never
seen
negative values like that. Might try enabling software volume Edit->Preferences
[Mplayer] - Mplayer Software Volume Control Enabled. Are you on 64bit perhaps?
Original comment by kdeko...@gmail.com
on 8 Jan 2010 at 10:17
Ok, I have attached my ~/.config/gnome-mplayer/gnome-mplayer.conf file.
Quite literally, with verbose=0 it doesn't work in firefox, with verbose=1 it
does.
I still can't get it to work when called directly though.
Original comment by systempa...@gmail.com
on 8 Jan 2010 at 10:17
Attachments:
I'm on 32bit.
Original comment by systempa...@gmail.com
on 8 Jan 2010 at 10:18
Ok, softvol=true has fixed it. I want software volume anyway, but I do not
understand
why the hardware volume is so messed up.
Original comment by systempa...@gmail.com
on 8 Jan 2010 at 10:20
The hardware volumes are read using libasound, so gnome-mplayer is using
whatever it
gets from it. This is the first time I've seen one messed up like that. I think
you
might have a driver issue.
Original comment by kdeko...@gmail.com
on 8 Jan 2010 at 10:24
Closing due to driver error
Original comment by kdeko...@gmail.com
on 8 Jan 2010 at 10:25
Thanks for the help.
Original comment by systempa...@gmail.com
on 8 Jan 2010 at 10:51
Original issue reported on code.google.com by
systempa...@gmail.com
on 8 Jan 2010 at 9:49