Plugin activiation at startup
 

I am in a project that will last me the whole summer to complete by myself. I run into a problem. I know how to start Winamp upon startup. But I need to start a winamp plugin upon start up. This is involving the Matrix Orbital. The proper steps I need to take is start LCDC. Then start Winamp. Then start the music plugin for the matrix orbital. Can anyone tell me how to start a plugin outside of winamp after the winamp program has started, all of which needs to occur upon windows startup.

If you are developing a Winamp plug-in please post your question in the Winamp Development forum.

If you downloaded the plug-in please contact the plug-in developer. Third party plug-ins are not supported on Winamp forums.

This isnt a new plugin
 

Once again people do not understand what I am saying. Read every word of the sentence. I was wondering how I could start any given plugin outside of Winamp. I will be starting winamp before I call on a plugin but I need it to start upon Windows start up. Once again this is not a new plugin. This is a general plugin question aimed at Winamp help.

control panel>scheduled tasks>add scheduled task

Once again? You've only made one post... or am I missing something?

No, there's no way to start a plugin outside of Winamp.

What type of plugin is it?
All General Purpose and Input plugins load at Winamp startup.
DSP, Output, and Vis plugins need to be selected in the Prefs.
The hi-lighted one becomes the active one.

The active DSP and Output plugins will automatically load at Winamp startup.

The active vis plugin will only auto load if you start Winamp playing some music (either by linking to a m3u playlist, or including a switch in the command line, or by using a plugin), and making sure "auto-execute vis plugin on playback" is checked in Prefs > Plugins.

It might also help if you told us what Matrix Orbital and LCDC are, without us having to go search for references on google.

Well, DJ posted as I was typing and I was going to say almost the same thing.

Also I do admit that I was confused by your question, mainly from the lack of information. I was not sure if you were developing your own plug-in or using a third party plug-in. So I decided to answer your post going on what info you provided.

If I now understand your post correctly, this does concern a third party Winamp plug-in. However, I did answer your question...Beyond that I couldn't much more info without knowing what kind of plug-in you were talking about.