On Windows Vista, SoundSet and SoundGet do not work to control the volume of the device. I am really waiting for this and more in the next releases as promised and so do many others people. I have just downloaded AutoHotkey and it is really a fantastic work for me for the first time of use. Finally, I found the best hotkey software for my PC. Thanks a lot for your software.
AutoHotkey for Vista ( About controlling the volume )
Started by
AutoHotkey_Fan
, Jun 27 2007 03:34 AM
13 replies to this topic
#1
-
Posted 27 June 2007 - 03:34 AM
Out of curiosity, does it work to control the volume if autohotkey.exe is set to run in compatibility mode for WinXP SP2 ?
#2
-
Posted 27 June 2007 - 05:50 AM
Great question. If it does work, I'll add it to the documentation.
#3
-
Posted 27 June 2007 - 10:56 AM
I recently installed Vista and have installed AHK too.
I ran Rajat's Volume OSD for the test, with the mixer panel open.
If I run the script, it inserts a new application of which I can only control it's slider. If I compile, it is the same, but if I change the exe to XPSP2 compatability, it adjusts the speaker and all applications, just as if you grabbed the control with the mouse.
I'm glad you suggested this, as I had a couple other applications I was having trouble doing the same with. Girder, and Max10, for use with my mouse remote from X10.
I ran Rajat's Volume OSD for the test, with the mixer panel open.
If I run the script, it inserts a new application of which I can only control it's slider. If I compile, it is the same, but if I change the exe to XPSP2 compatability, it adjusts the speaker and all applications, just as if you grabbed the control with the mouse.
I'm glad you suggested this, as I had a couple other applications I was having trouble doing the same with. Girder, and Max10, for use with my mouse remote from X10.
#4
-
Posted 02 July 2007 - 09:04 PM
Jeff Main
Ran an additional test tonight for corrupt...
Set the ahk exe properties to run as XPSP2 compat, and now I can run the script as I could the compiled script's EXE.
Set the ahk exe properties to run as XPSP2 compat, and now I can run the script as I could the compiled script's EXE.
#5
-
Posted 03 July 2007 - 01:50 AM
Jeff Main
Wow, I have tried all, but I can't solve the problem at all. Maybe, we should wait for the help documents ( even a change ) from the site admin, Lord Chris. I think this will not be a small change because there is a big difference between Windows XP and Windows Vista ( I am just talking about the volume controller here ). It will take a little long for that change, but I am going to wait for that. Thanks a lot for your kindness to bring AutoHotkey to all of us. Thank you ...
#6
-
Posted 04 July 2007 - 06:47 AM
Yes! The sound engine in Vista was completely re-wrote from the ground up.
As I understand it, the engineers behind it didn't follow the guidelines put in front of them, and were let go and replaced by new engineers that could think differently.
Previously, the sound engine was manipulated at the kernal level, now it is manipulated at the user level. Each app's volume can be adjusted independently of all others, whereas previously, you had the master and a single wave control for all apps, unless they programmed a seperate volume control within their own app. The Vista mixer is a new way of thinking for sure, and will take some getting used to.
As I understand it, the engineers behind it didn't follow the guidelines put in front of them, and were let go and replaced by new engineers that could think differently.
Previously, the sound engine was manipulated at the kernal level, now it is manipulated at the user level. Each app's volume can be adjusted independently of all others, whereas previously, you had the master and a single wave control for all apps, unless they programmed a seperate volume control within their own app. The Vista mixer is a new way of thinking for sure, and will take some getting used to.
#7
-
Posted 04 July 2007 - 09:50 PM
Jeff Main
Thanks for the info. I've revised the SoundSet page to read:
Revisions/improvements are welcome.On Windows Vista, SoundSet and SoundGet affect only the script itself (this may be resolved in a future version). There are at least two ways to work around this:
1) In the properties dialog for the file "AutoHotkey.exe" (or a compiled script), change the compatibility setting to "Windows XP".
2) Have the script send volume-control keystrokes to change the master volume for the entire system. For example:Send {Volume_Up} ; Raise the master volume by 1 interval (typically 5%). Send {Volume_Down 3} ; Lower the master volume by 3 intervals. Send {Volume_Mute} ; Mute/unmute the master volume.
#8
-
Posted 06 July 2007 - 01:18 PM
Did any workarounds surface? It seems that with Windows 7, even the "Win XP compatibility" trick doesn't work anymore.
#9
-
Posted 08 November 2009 - 03:46 PM
Oh? I'm able to control the volume just fine with SoundSet on Windows 7 with XP compatibility set for AutoHotkey.exe. However, Vista Audio Control Functions generally work better and with less side-effects.
#10
-
Posted 13 November 2009 - 03:03 PM
I solved it with a dirty workaround:
; set Master Sound to 8 (from 50 which is max on my Lenovo T510) Send {Volume_Down 50} ; go down to 0 (no matter what volume was before) Send {Volume_Up 8} ; increase to 8
;set Master Sound to 40 (from 50 which is max on my Lenovo T510) Send {Volume_Up 50} ; increase to 50 (no matter what volume was before) Send {Volume_Down 10} ; go down to 40
#11
-
Posted 28 April 2011 - 06:14 PM
Can soundget(or set) work properly for windows vista+ in the next version?
#12
-
Posted 01 July 2011 - 07:45 AM
You can use the VA.ahk library which can be found on the forums for anything newer than XP.
#13
-
Posted 01 July 2011 - 05:13 PM
I like your little quick and dirty trick, although I suspect it is better to take the sound down to zero (0) before raising the volume.
If you max the volume and then shrink it, if the person is playing a file, it could be hazardous to someone's ear.
If you max the volume and then shrink it, if the person is playing a file, it could be hazardous to someone's ear.
#14
-
Posted 01 September 2011 - 04:45 AM