Try using "!Winamp Gen!AVS"
BTW, great name
Been using from this forum for about 12 months now and never needed to ask a question that the search function couldn't answer, until now. I guess thats a credit to all who do participate in the forum, thank you muchly.
Anyhoo I am putting together a skin (will post it up soon) and noticed that the AVS visualisations in Winamp are killing my car pc. I have adjusted the winamp settings and it has improved things but I would really like to be able to automatically close the visualisations when navigating away from my Visualisation screen to other CPU demanding tasks.
I tried the following on my menu button but it didn't achieve what I wanted.
I think that is the correct window name. Is there a particular way to obtain the window name or is it just what is displayed at the top of the frame? Sorry for my ignorance there, programming isn't one of my strong points
So, any ideas?
Thanks in advance,
No luck there, I am using winamp version 5.13 if that makes any difference.
I see you also have a creative forum name. Shame I sold the old RA28 celica, the new car doesn't quite fit the old forum name.
This is because AVS gets loaded "into" RR... you can either keep track of your Visu state using variables and re-execute the VISU command when exiting the screen (if your variable states it's ON), or you can change the setting to visuname=!Winamp Ge!AVS in RR.INI for instance (notice the "missing" N). This should keep AVS from being embedded into RR but it will also preven RR from removing it's border and from doing any advanced commands on it (fullavs, nextavs etc).
Thanks for the help fellas, but I skinned this cat a little differently.
I set the visualisation to come on automatically after 2 seconds
in vis skin I put : IDL,002
in Exectbl.ini I put : "IDLE","VISU"
and on all the buttons that exit from this vis skin, I added this VISU||EXIT|| ie
It works almost exactly how I want it. The only problem is that if I move the mouse at all the timer kicks in and will turn the vis on/off. It should be fine for the touch screen as it will be one touch to open the vis skin and start the vis and then one touch to close the vis and navigate away from it.
I have buttons for "EXEC;PREVAVS||=", and "EXEC;NEXTAVS||=", on the vis window and the timer issue means that after I select these buttons, the vis stops after 2 seconds but another movement gets them started again. A nuisance but not too hard to live with. I guess this is a function of the VISU command being a toggle for on and off and thats a constraint from winamp.
Guino - Thanks for the probably very good direction, but once you mentioned variables, my brain had a blue screen moment. I am more of a spanner type of guy. Programming scares me....... A lot.
Thanks again for your help fellas, if you have any peals of wisdom for vis switching off after mouse movements issue, I'm all ears.
Oh and Anthony, sorry about the confusion but I think you can appreciate the car reference.... I've never met an Anthony I didn't like. Great name.
OK scrap that last method, a little more searching found this and it works perfectly. Why didn't I find this or even think of this before.
Launch the vis skin with
and use the same exit commands from before
No idle timer so no problems. Exerything works perfectly and its all so logical I'm gonna have to slap myself and say dunderclump.
I'm gonna have to go and hide now