at home i have the "postmessage" comands for play pause stop an few others to control winamp, i rate this as the best way to control it, better than sending hotkeys as it will work on any version of winamp weather global hotkeys are turmed on or off.
how can i find out the rest? volume up/down, be good if i could ask it what the volume is set to? or set the volume to a sertain %age?
anyone ever done this sort of thing?
cheers Ralph.
winamp control
Started by
ralphh85
, May 23 2006 11:55 AM
4 replies to this topic
#1
-
Posted 23 May 2006 - 11:55 AM
Dear Ralph,
Yes!......jballi
See his topic: Winamp function/shell
Here is his code: https://ahknet.autoh...v1.0/Winamp.ahk ( SKAN's Dropbox )
Regards,
Anyone ever done this sort of thing?
Yes!......jballi
See his topic: Winamp function/shell
Here is his code: https://ahknet.autoh...v1.0/Winamp.ahk ( SKAN's Dropbox )
Regards,
#2
-
Posted 23 May 2006 - 12:24 PM
There's a large list of postmessage codes for winamp that Rajat posted half way down this page:
http://www.autohotke...topic.php?t=126
Also searching for "winamp postmessage" reveals a lot of threads. It appears not to be possible to retrieve the actual volume level though.
http://www.autohotke...topic.php?t=126
Also searching for "winamp postmessage" reveals a lot of threads. It appears not to be possible to retrieve the actual volume level though.
#3
-
Posted 23 May 2006 - 12:28 PM
Actually, Winamp's SetVolume user message (122) is used to collect the current volume if -666 is sent as the wParm parameter.It appears not to be possible to retrieve the actual volume level though.
SendMessage 0x400,-666,122,,ahk_class Winamp v1.x msgbox The current Winamp volume is %Errorlevel% (From 0 to 255)If using the Winamp function:
CurrentVol:=Winamp("Set Volume",-666) msgbox The current Winamp volume is %CurrentVol% (From 0 to 255)I'm working on on a version of the Winamp function that includes a number of aliases for the more common command combinations (like this one) so that the function will be even more user friendly. I'll get around to publishing it sometime...
I hope this helps.
#4
-
Posted 23 May 2006 - 09:39 PM
Ah, I must have seen an outdated discussion thread, thanks for posting the code.
#5
-
Posted 23 May 2006 - 10:08 PM