winamp.m3u is missing despite checkbox being ticked

[HtCwCjUeff]

I'm trying to get the "Now playing" feature running with AdiIRC, which works fine with the original Winamp-release, but the winamp.m3u file is missing despite having ticked the checkbox in the advanced settings.

Is there something I am missing here?

[dro]

Are you looking in the correct folder e.g. %appdata%\wacup (assuming a default WACUP install) ? You can go to preferences -> advanced -> diagnostics & the settings locations tab to get the correct path for your install. If the winamp.m3u definitely isn't in the folder then you might need to first force a playlist change such as by changing the order of a playlist item & then see if it gets saved on closing.

Otherwise it's possible that the program might be assuming a certain folder location or it's doing a different way of determining if it's a Winamp compatible client or not (I've not heard of AdiIRC until now so I don't have any knowledge of what it might or might not be doing).

-dro

[HtCwCjUeff]

I now cleanly removed everything (with the exception of having used a registry cleaner) and reinstalled WACUP.

There is a special option to create a legacy file for making plugins work in other programs (AdiIRC in my case) under Options > Preference > Advanced > Options Page 2 > Playlist Compatibility which I had checked before and which is checked now.

I installed WACUP under C:\Program Files (x86)\winamp\ and set both paths in AdiIRC accordingly:


The good news is: It's not saying * /np: Your Media Player is not running, but the bad news is, it's only printing "* @HtCwCjUeff is bouncing to ''" without naming the artist or title of the song.

Any ideas?

[dro]

Maybe try having it run the winamp.exe named WACUP loader instead of the wacup.exe. Alternatively it might be trying to hook into the running process & that's where things get messy at the moment as the wacup.exe/winamp.exe aren't the actually running process (they don't even stay running with the current beta builds) & it's the winamp.original instance that's what is actually running.

I suspect it's probably needing to access the actual running instance but WACUP's loader spawns a child process & AdiIRC probably isn't interacting with that. Without knowing what AdiIRC is actually doing (I've not yet looked if there's source code / documentation details) I don't have much else to suggest & wouldn't be surprised if this isn't something that'll get resolved until I've dropped the need to run the original Winamp core process & not have the loader setup as-is.

-dro

[HtCwCjUeff]

Maybe try having it run the winamp.exe named WACUP loader instead of the wacup.exe.

Just tried that one out with the same end result: Still not working.

[dro]

Then most likely until the loader process (winamp.exe / wacup.exe) is the actual running instance it's not going to work nor is it reasonable to expect changes to be made to AdiIRC when WACUP is still in a preview state & once the original Winamp process is dropped then more things should work as expected when it comes to external tooling interactions.

I've also just had a quick look but couldn't find anything obvious detailing what AdiIRC is doing so above is my best guess at why it's failing for now.

-dro

[HtCwCjUeff]

Everything is working fine on my side now; I simply disabled the plugin and re-enabled it by switching over to Winamp again and then it worked!

Wasn't a problem of AdiIRC or WACUP after all, so can be closed.