Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: 1.0 and /command:"Volume up" stopped working (Read 1434 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

1.0 and /command:"Volume up" stopped working

I created an autohotkey script to make better use of my keyboard.  I mapped global hotkeys to the /command:"Volume up" and /command:"Volume Down" and they worked perfectly for a long time.  Then, I upgraded to 1.0 and these commands stopped working.  /playpause /prev and /next still work fine.  Did something change?

1.0 and /command:"Volume up" stopped working

Reply #1 –
The name has been changed: /command:"Up"

Background: When you press shift when opening a main menu, v1.0 displays commands that were previously hidden and only available as command line arguments and keyboard shortcuts. Since the playback menu would have been too long, volume (as well as seeking) commands have been put into submenus, with the "Volume" prefix stripped from their names.
 

1.0 and /command:"Volume up" stopped working

Reply #2 –
Quote from: Frank Bicking on
The name has been changed: /command:"Up"

Background: When you press shift when opening a main menu, v1.0 displays commands that were previously hidden and only available as command line arguments and keyboard shortcuts. Since the playback menu would have been too long, volume (as well as seeking) commands have been put into submenus, with the "Volume" prefix stripped from their names.



Thank you, very much.  Foobar2000 is excellent.