New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extend Foobar2000 app module with scripts to announce elapsed and total time #6596

Closed
tuukkao opened this Issue Nov 27, 2016 · 2 comments

Comments

Projects
None yet
4 participants
@tuukkao
Contributor

tuukkao commented Nov 27, 2016

I am proposing the following changes to be implemented in the app module for Foobar2000:

  • Add a script for reporting the elapsed time of the currently playing track. I suggest using the shortcut ctrl+shift+e.
  • Add a script for reporting the length of the currently playing track. I suggest using the shortcut ctrl+shift+t.

All of this information can be already accessed via the status bar. However, it can be inefficient to obtain since the lengths are at the very end. Reordering the status bar so that the lengths would be presented first won't work either since it will break the report remaining time script in the app module, which relies on the status bar using its default format. These scripts would present the needed information immediately without having to listen through the entire status bar first. The proposed shortcuts are directly related to the shortcut for reporting the remaining time (ctrl+shift+r) and would therefore be easy to memorise.

I'm willing to start working on this issue immediately.

@leonardder

This comment has been minimized.

Show comment
Hide comment
@leonardder

leonardder Nov 29, 2016

Collaborator
Collaborator

leonardder commented Nov 29, 2016

@feerrenrut

This comment has been minimized.

Show comment
Hide comment
@feerrenrut

feerrenrut Nov 30, 2016

Contributor

Thanks @tuukkao. I'll set this as priority 4 since we are unlikely to work on this internally, however we are happy to accept a pull request for this issue.

Contributor

feerrenrut commented Nov 30, 2016

Thanks @tuukkao. I'll set this as priority 4 since we are unlikely to work on this internally, however we are happy to accept a pull request for this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment