You are not logged in.
Pages: 1
I'm getting a various array of issues with Mplayer2 that I'm not sure what the root problem is (if there is one). Here's the ones I've noticed so far, all done without placing anything in config files:
The progression bar/seekbar and volume display are rendered in those weird square glyphs, so all I'm seeing is a line of white-outlined rectangles.
I have to apply 'joystick=no' in my ~/.mplayer/config in order to use any Mplayer2 keybindings, as everything is read as if as I'm using a Joystick.
I can't do any precise seeking, e.g., <10 seconds.
I'm getting no audio output when using my HDMI (although all other applications work). Audio output does work on my laptop's internal sound.
What's strange is that when I run Mplayer2 with SMplayer, everything works perfectly fine. If I uninstall Mplayer2 and install Mplayer, everything also works perfectly fine. One of the primary reasons I want to switch over to Mplayer2 is for the precise seeking, and yet compounded with all the other issues I'm facing, I still can't get that to work (and yet it works when using SMplayer under Mplayer2.. what??).
What's also strange is that I'm quite sure that I've downloaded Mplayer2 in the past and have had no problems (although I can't confirm this completely). But when switching between Mplayer2 and Mplayer recently, I've suddenly no longer had accessibility to Mplayer2 without copious amounts of bugs. This leads me to think it's some config file stuck between the two or something.
Has anyone else had a similar issue and/or know a possible root problem to this? FWIW, I searched/google to no avail. Am running everything fully updated. Am also using the infinality font patch, though I'm not sure if it's related to these issues.
Last edited by nil (2013-05-19 08:22:29)
Offline
The progression bar/seekbar and volume display are rendered in those weird square glyphs, so all I'm seeing is a line of white-outlined rectangles.
https://bbs.archlinux.org/viewtopic.php?pid=1268847
I can't do any precise seeking, e.g., <10 seconds.
What's your input.conf config?
Part of my ~/.mplayer/input.conf:
RIGHT seek +10
LEFT seek -3
DOWN seek -60
UP seek +60
PGUP seek 600
PGDWN seek -600Worked well with mplayer2, but I've switched to mpv - you can give it a go https://aur.archlinux.org/packages/mpv-player-git/
Some files seemingly don't allow seeking / precise seeking. You can try
--forceidx
Force index rebuilding. Useful for files with broken index (A/V desync,
etc). This will enable seeking in files where seeking was not possible.but it's just a guess ;P
Offline
Thanks for the link. I'll try it out and see what works. On your question, I'm running stock Mplayer2 with no configs edited. If I do add something like
LEFT seek -5
RIGHT seek +5into ~/.mplayer/input.conf, then it still seeks only to 10 seconds (and also, note that I have to put 'joystick=no' into ~/.mplayer/config, or otherwise no keybinding will ever be read). However, if I change SMplayer settings to seek +/-5 seconds, it does work, so I'm a little confused how SMplayer has everything work off the bat, and yet I assumed it was just a GUI front-end..
Last edited by nil (2013-05-19 09:21:16)
Offline
I'm not sure why, but you need hr-seek=always to seek under 10 seconds.
Offline
Pages: 1