Multiple wacup Instances

[jon00]

Hi Darren,

What is the best way to run more than one instance of wacup on a single PC? (I see the warning when ticking allow multiple instances). The requirement is to have two copies controlled remotely (by getting their Hwnd) and being able to set the DirectSound output to different sound cards. These settings would need to be remembered for each instance.

[dro]

It depends if it needs to be done as 2 installs of it 1 install & dual configuration folders will be ok.

Making 2 separate installs is sometimes the simplest way but you've then got the fun of how to locate that instance as well as if one instance needs updated plug-ins that the other is also updated.

The other way is to make 1 install & use the /INIDIR option (& for safety the /CONFIG option to avoid possible confusion) for one or both of the instances to be run. With the new (via /NEW) instance handling under WACUP I do /INIDIR="folder" /CONFIG="folder\winamp.ini" with the second instance that WACUP creates (along with the duplication of the settings folder if that's needed).

Also there's the potential for actions for one instance going to the wrong one which the /FIND command-line can help to work around though the best option is to have one of the instances use a different classname so it's easier to distinguish between them. The default as you know is Winamp v1.x but by editing the paths.ini file (directly or via the /PATHSEDIT action against the respective configuration - it can be made to browse to a different folder via the editor) then you can change it something else. Like I use WACUP 0.9x for my development install & my playback install then uses the default.

Am sure there's more questions but that's the obvious things from the top of my head.

-dro

[jon00]

Thanks...that makes complete sense. What is the risk in using multi-instance in Wacup which I already have setup for Winamp installations?

[dro]

The only issue is if you use the same configuration for each instance then if there's settings &/or library / history related changes they can get messed up as there can be a fight as to which one gets to save it's settings last. Otherwise if you've got things running with the duplicated config folders then it's just the aspect of correctly knowing which instance to interact with.

-dro

[jon00]

Thanks.

I have one further issue. The Main Playlist directory is shown as  %APPDATA%\WACUP under diagnostics.

If I add anything to the /M3UDIR= entry it changes to  %SystemDrive%\WACUP\<my new directory>

I assume this is a bug?

[dro]

What's the command line you entered for that?  As without checking right now it might be wacup vs winamp command line conflict as there's a number of aspects like it that I've not taken over.

It's also possible to set that in the paths.ini.

-dro

[jon00]

If you use /M3UDIR ="2" it show the directory as %SystemDrive%\WACUP\2

If you use /M3UDIR = "%AppData%\WACUP\2", it shows the directory as %SystemDrive%\WACUP\%AppData%\WACUP\2

[dro]

Ok, will look into getting that fixed.

-dro

[dro]

It should hopefully work in a more expected manner with the next build now I'm not allowing Winamp's code to be used.

So passing relative (to the existing settings folder) or fully qualified paths are now working from my tests including those using environment variables (%appdata%). If anything passed cannot be made into a valid file / folder path depending on the action used then it'll use the default / expected paths based on the stored configuration.

-dro

[jon00]

Many thanks.

I've run into more issues. It would seem that wacup does not honor the /CLASS=XXXXX on some commands. For example, two classes winamp2 & winamp3 running:

/CLASS="winamp3" /ADD "C:\Playlist\3\Playlistall.m3u"
/CLASS="winamp3" /PLAY
 
The playlist is sent to the winamp2 class but tries to play the correct (winamp3) class?

This works fine on Winamp 5.666 BTW

[dro]

This one seems to be down to me not having replaced everything with the command-line / multi-instance handling.

Setting the class in the paths.ini is probably the more reliable option but I suppose you're just wanting to do it all dynamically as needed.

-dro

[jon00]

This one seems to be down to me not having replaced everything with the command-line / multi-instance handling.

Setting the class in the paths.ini is probably the more reliable option but I suppose you're just wanting to do it all dynamically as needed.

-dro

Indeed....and the fact I already have this working fine with Winamp.

[dro]

The fun of trying to change the wheels & engine as it's being used

I'll need to dig into this but I'm not going to hold off a new release for it.

-dro