Menu

#681 show_info_osd display inconsistent

Next_Release
closed-invalid
nobody
None
5
2017-12-18
2017-08-22
No

Version: 17.8.0 (revision 8621)
Using Qt 4.8.7 (compiled with Qt 4.8.7)
Using MPV 0.14.0

Following implementation of feature request [#637], the following changes in behaviour are seen:

1 show_filename action replaced by show_info_osd, which provides a much busier display by default, when using the mpv engine.

  • show_info_osd display can be configured using smplayer.ini/[advanced]/mpv_osd_media_info setting; eg to emulate show_filename set value to ${filename}.

  • With mplayer engine, show_info_osd emulates show_filename exactly by default: filename is displayed via OSD for a short period ~ 2s. This applies whether the action is invoked by a keyboard command (shift+I by default) or by setting it to run on each opened file through Options/Preferences/Advanced.

  • With the mpv engine, when invoked by a keyboard command, show_info_osd displays the information with no timeout, and has to be cancelled by repeating the command.

  • With the mpv engine, when invoked on opening a file, show_info_osd either displays the information for less than a second and then clears it, or displays it for ~4s, clears it for a moment, then redisplays it with no timeout, and has to be cancelled by repeating the command. These behaviours alternate when moving through a playlist.

Personally I would have preferred the show_filename action with its previous behaviour to be retained along with show_info_osd but perhaps there's probably a technical limitation in the mpv/mplayer interface to blame.

In any case the inconsistent set of behaviours exhibited with the mpv engine is clearly wrong. There should be a timeout in all cases, with a way of overriding it separately for the keyboard invocation case if possible.

Related

Feature Requests: #637

Discussion

  • Dirk Fieldhouse

    Dirk Fieldhouse - 2017-08-22

    Platform: LXLE (Lubuntu remix) 16.04.1 i686 4.4.0-92-generic #115-Ubuntu

     
  • Dirk Fieldhouse

    Dirk Fieldhouse - 2017-08-22

    Please mark this closed:invalid and refer to bug [835]. Why can't the creator of a ticket do that?

     
  • Ricardo Villalba

    • status: open --> closed-invalid
     

Log in to post a comment.