Latest WACUP public preview for x86 & x64 is build #24360 (April 20th 2026) (x86 & x64 changelogs)
Latest restricted WACUP beta release is build #24360 (April 20th 2026) (x86 & x64 changelogs)

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - jon00

Pages: [1]
1
General Discussion / Re: Multiple wacup Instances
« on: May 15, 2020, 02:27:04 PM »
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.

2
General Discussion / Re: Multiple wacup Instances
« on: May 15, 2020, 12:49:15 PM »
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

3
General Discussion / Re: Multiple wacup Instances
« on: May 14, 2020, 02:27:25 PM »
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


4
General Discussion / Re: Multiple wacup Instances
« on: May 14, 2020, 12:54:41 PM »
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?

5
General Discussion / Re: Multiple wacup Instances
« on: May 13, 2020, 05:34:24 PM »
Thanks...that makes complete sense. What is the risk in using multi-instance in Wacup which I already have setup for Winamp installations?

6
General Discussion / Multiple wacup Instances
« on: May 11, 2020, 07:53:16 PM »
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.

7
General Discussion / Re: Queuing with JTFE from media library
« on: May 07, 2020, 11:58:37 AM »
Is the new CL switch permanent (remembered) or need to be done before each WACUP session?

It'll be remembered between sessions once set as long as the config isn't corrupted / removed.
Also build 5500 is now available with the changes.

-dro

Perfect! Works a treat.

8
General Discussion / Re: Queuing with JTFE from media library
« on: May 06, 2020, 06:56:25 PM »
That's fine. I already have it working with the m3u8 file being watched for changes but currently using a timer to poll the command line so that the file updates. With your change, I will just need to remove the timer as the file watcher raised event does the work.

Is the new CL switch permanent (remembered) or need to be done before each WACUP session?

9
General Discussion / Re: Queuing with JTFE from media library
« on: May 06, 2020, 12:01:12 PM »
For the window handling you should be able to use the following with the next build:
Code: [Select]
#define IPC_GETWND 260
/* (requires Winamp 2.9+)
** HWND h=SendMessage(hwnd_winamp,WM_WA_IPC,IPC_GETWND_xxx,IPC_GETWND);
** returns the HWND of the window specified.
** Note: this does not support the WACUP message addition
**       of IPC_GETWND_MAIN since you have to use a valid
**       main window HWND to start with, need I say more?
*/

#define IPC_GETWND_MAIN -1 // use one of these for the param
#define IPC_GETWND_EQ 0    // see api notes on what is valid
#define IPC_GETWND_PE 1    // (IPC_GETWND_MAIN new to WACUP)

//#define IPC_GETWND_MB 2  // deprecated from 5.22+ when the
                           // minibrowser support was killed

#define IPC_GETWND_VIDEO 3
#define IPC_GETWND_ML 4    // added WACUP 1.0.11+ but may not
                           // be applicable based on install!

#define IPC_ISWNDVISIBLE 261 // same param as IPC_GETWND
/* (requires Winamp 2.9+)
** This returns the current visible state of the window.
** Under WACUP using IPC_GETWND_MAIN as the param is
** supported & will return the main window state.
*/

#define IPC_SHOWWND 262 // same param as IPC_GETWND
/* (added WACUP 1.0.11+)
** This will show the specified window if its closed
** and it will return non-zero on success. If the
** window is already visible then nothing is done
** though the return is zero for you state usage.
*/

#define IPC_HIDEWND 263 // same param as IPC_GETWND
/* (added WACUP 1.0.11+)
** This will hide the specified window if its open
** and it will return non-zero on success. If the
** window is already hidden then nothing is done
** though the return is zero for you state usage.
*/

IPC_SHOWWND & IPC_HIDEWND are the main WACUP additions (the other change being some ML & main window specific stuff on the older APIs). That should allow you to hopefully open / close those windows as needed along with using the returned state & IPC_ISWNDVISIBLE if needed beforehand to deal with state persistence as needed.

Will provide the JTFE queue saving details once that's been finished.

-dro

Just to confirm:

All Hwnds and other methods work fine.
'What's playing' settings patch working.

Looking forward to the next beta with the JTFE queue manager modification!

Many thanks again.

10
General Discussion / Re: What's Playing plugin
« on: April 30, 2020, 09:02:49 AM »
Many thanks for your speedy response and fix.

Will the patch be part of wacup or something else?

11
General Discussion / Re: Queuing with JTFE from media library
« on: April 30, 2020, 09:00:36 AM »
For the queue saving option, you can use wacup.exe /TEMP_SAVEPLAYBACKQ whilst WACUP is running (doing it when it's not running will be ignored) & that will save the current queue out to the gen_jumpex.m3u8 file in the settings folder (as normally happens on unloading the plug-in if the restore option is enabled).

If there's nothing in the queue at the time of the command-line action then the gen_jumpex.m3u8 file will be removed if it already exists otherwise the contents of the file will be updated. No queue, no file for simplicity.

There's handling to have the request fail if the process is deemed to have hung & the name of the option is prefixed with "TEMP_" as that's the intention for it in its current incarnation. I would prefer it to be outputting in a different format & to control the location but that's more of a pain to have strings passed around which is why I've re-used the existing handling just to get something working for you.

-dro

To provide queue information in my plugin would require me to poll WACUP with the TEMP_SAVEPLAYBACKQ command every few seconds and then act (if necessary) on the generated file. Whilst feasible, having the queue list just replicated in a m3u file would be much easier to manage as you can the use a filewatcher class to monitor file changes. Any thoughts?

12
General Discussion / Re: What's Playing plugin
« on: April 29, 2020, 10:22:49 PM »
Hi, let me step in here.

The plugin is not providing information about the Title/Artist/Album/Year/Genre and possibly Comment.

To test, save the two files attached somewhere and configure the plugin similar to the attached screenshot.

When the song changes, infoout.txt should contain the actual metrics playing by Wacup. It works fine in Winamp








Pages: [1]