Opened 16 years ago

Closed 12 years ago

#17802 closed defect (fixed)

mplayer 1.0rc2 vo_ontop (stay-on-top) doesn't work

Reported by: shreevatsa.public@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 1.7.0
Keywords: Cc:
Port: MPlayer

Description

mplayer has a keyboard control of:

   T
        Toggle stay-on-top (also see -ontop).

which doesn't work: whenever T is pressed, the OSD always says "Stay on top: disabled", and at the commandline we see "Command vo_ontop: argument 1 isn't an integer."

The explanation for this I found in the replies to a 2007 October thread on their mailing list, at http://lists.mplayerhq.hu/pipermail/mplayer-users/2007-October/069603.html The fix might be to apply this patch to the source (is the current release really older than October 2007?? maybe it's already applied...)

Alternatively, another simpler fix that just works is to do:

touch ~/.mplayer/input.conf

(i.e., create the file if it doesn't exist). But since it's probably not a good idea to modify every user's homedirectories, another fix is to remove the comment after the "T vo_ontop" line in $PREFIX/etc/MPlayer/input.conf (or move the comment to another line).

Note that "T vo_ontop" is not the only command affected by this; e.g. hitting "r" or "t" (which are for moving subtitles) also has the same bug (i.e. there is the message at the commandline, although it doesn't seem to matter), and probably so do whatever other commands in input.conf have a comment following them.

Change History (4)

comment:1 Changed 16 years ago by jmroot (Joshua Root)

Owner: changed from macports-tickets@… to ecronin@…

comment:2 Changed 16 years ago by (none)

Milestone: Port Bugs

Milestone Port Bugs deleted

comment:3 Changed 13 years ago by jmroot (Joshua Root)

Owner: changed from ecronin@… to macports-tickets@…
Port: MPlayer added; mplayer removed

Is this still a problem with 1.0rc4?

comment:4 Changed 12 years ago by jeremyhu (Jeremy Huddleston Sequoia)

Resolution: fixed
Status: newclosed

It sounds like this was fixed upstream, so closing.

Note: See TracTickets for help on using tickets.