howdy voxinaters
according to the wiki
QuoteOne important note about payloadXML files is that they can't be the only part of a command. You should have some other phrase before them that the engine can use to identify which command to execute (in the example above, "Play song" is said first).
what if i want to use a payload xml or some other xml WITHOUT using a phrase before the payload phrase.
for example I want to use the phrases like shown below to trigger the values as shown below.
Previous track button 40044
Next track button 40048
Play button 40045
Pause/Unpause button 40046
Stop button 40047
Fadeout and stop 40147
Stop after current track 40157
Fast-forward 5 seconds 40148
Fast-rewind 5 seconds 40144
Start of playlist 40154
Go to end of playlist 40158
Open file dialog 40029
Open URL dialog 40155
Open file info box 40188
Set time display mode to elapsed 40037
Set time display mode to remaining 40038
Toggle preferences screen 40012
Open visualization options 40190
Open visualization plug-in options 40191
Execute current visualization plug-in 40192
Toggle about box 40041
Toggle title Autoscrolling 40189
Toggle always on top 40019
Toggle Windowshade 40064
Toggle Playlist Windowshade 40266
http://forums.winamp.com/showthread.php?threadid=180297
I don't want to say "Jarvis" then VC comes out of standby then say "winamp open visualization options", what I would like to say is "open visualization plugin options", i also don't want to write a VC command for each winamp command, that's what I've been doing, and things are looking untidy, most of my groups are like this, in some scenarios I prefer payloads without speaking any phrases before.
can it be done in VC ? or should I try conjuring up something in python ? ::hmm
Depends on your desires. I'm seeing only 7 commands needed in the above, and it could be a bit less if you were to be slightly more consistent with your command choices. Is 7 commands too many?
Note that the phrase doesn't have to be at the beginning of the command. It can be after the payload. Below, the parts in quotations could be your phrases. The rest can be in your payloadxml file, if that's how you prefer to do it.
command 1
Previous track "button" > 40044
Next track "button" > 40048
Play "button" > 40045
Pause/Unpause "button" > 40046
Stop "button" > 40047
command 2
"Fast" forward "five seconds" > 40148
"Fast" rewind "five seconds" > 40144
commmand 3
Start of "playlist" 40154
Go to end of "playlist" 40158
command 4
"Open" file dialog > 40029
"Open" URL dialog > 40155
"Open" file info box > 40188
"Open" visualization options > 40190
"Open" visualization plug-in options > 40191
command 5
"Set time display mode to" elapsed > 40037
"Set time display mode to" remaining > 40038
command 6
"Toggle" preferences screen > 40012
"Toggle" about box > 40041
"Toggle" title Autoscrolling > 40189
"Toggle" always on top > 40019
"Toggle" Windowshade > 40064
"Toggle" Playlist Windowshade > 40266
command 7
"Execute" current visualization plug-in > 40192
[you could have other "execute" options as well here]
Quote from: nime5ter on June 17, 2014, 06:37:45 PM
Depends on your desires. I'm seeing only 7 commands needed in the above, and it could be a bit less if you were to be slightly more consistent with your command choices. Is 7 commands too many?
Note that the phrase doesn't have to be at the beginning of the command. It can be after the payload. Below, the parts in quotations could be your phrases. The rest can be in your payloadxml file, if that's how you prefer to do it.
It's not what i had in mind, Thanks.
Quote from: xtermin8r on June 17, 2014, 06:01:59 PM
according to the wiki...
what if i want to use a payload xml or some other xml WITHOUT using a phrase in the payload phrase.
Then you are out of luck. I would suggest in most cases you could use the word "press" followed by the payload, and edit your payload phrases down to makes them less verbose.
Otherwise you will need to either create one command for each, or break them up into a few categories of commands with payloads as Nime5ter suggests.