Recent Posts

91

Preview Build Discussion / [Issue] Local Library completely blank

« Last post by SuperVGBoy on April 14, 2025, 01:43:50 AM »

After clicking on an audio file within WACUP that I assume was corrupted, The local library is completely blank. The music files are still there as well as the folders redirecting to them, as they are selectable and playable in my saved playlists, but the songs won't show up in the Local Library tab, even if I rescan the folders.
Investigating led to me finding this error in settings.

I tried restarting the app and restarting the computer, but neither fixed the issue. I thought it was because I wasn't on the latest build, but updating didn't fix it either.
WACUP Version:
1.99.27.21136

92

Skins / Re: Quinto Black CT

« Last post by ariszlo on April 12, 2025, 08:57:51 PM »

Hi Aminifu,

I only have the email address from Quinto's skin.xml that you also have.

93

Preview Build Discussion / Re: WACUP is almost perfect, 2 minor issues

« Last post by nxho on April 12, 2025, 11:12:23 AM »

Does this mean it's not getting added in the future since I'm the only soul who is still using it or are you guys busy with much more important stuff and It will eventually come?

The aim of the preview build was to not screw around with existing settings especially when it was starting out as a plug-in pack for 5.666. As such I don't have any code in the builds that can register what file types WACUP can handle but there are things in place to allow for manually associating it if that's wanted (e.g. the open with option the OS provides & then the options on preferences -> general can be changed to adjust what the default behaviour in response to command-line actions is using). At some point I'll get around to completing the feature along with having to look into implementing a shell extension to resolve other problems with trying to process many files which the basic command-line behaviour doesn't cope well with in recent Windows versions.

I only play mp3 files, no idea if it happens with other formats.I'm using the latest build (1.99.27.21136 (x86))

Are you also looking at the metadata &/or making changes to the metadata of those MP3 files?

Very interesting. And thanks for the insight! To answer your question: No metadata changes on my behalf, just simple playback.
Also I have further feedback which may be of use to you:

Today I noticed a different hooking behaviour: I listened to File 1 in folder 1. Then I doubleclicked and listened to File 2 from Folder 2. After the track ended and playback stopped, I deleted Folder 1 and was suprised that it couldn't be deleted. File 2 from Folder 2 was still in the playlist and WACUP was open, and to my surprise windows allowed me to delete Folder 2, but in order to delete Folder 1 I had to close WACUP. To summarize, it's as if the second to last file got hooked. Weird erratic behaviour. File 1 was 58 minutes and File 2 was 7 or so minutes, and I waited the whole 7 minutes and once it stopped I attempted to delete File 1 with WACUP still open.

94

Preview Build Discussion / Re: WACUP is almost perfect, 2 minor issues

« Last post by dro on April 12, 2025, 09:51:13 AM »

Does this mean it's not getting added in the future since I'm the only soul who is still using it or are you guys busy with much more important stuff and It will eventually come?

The aim of the preview build was to not screw around with existing settings especially when it was starting out as a plug-in pack for 5.666. As such I don't have any code in the builds that can register what file types WACUP can handle but there are things in place to allow for manually associating it if that's wanted (e.g. the open with option the OS provides & then the options on preferences -> general can be changed to adjust what the default behaviour in response to command-line actions is using). At some point I'll get around to completing the feature along with having to look into implementing a shell extension to resolve other problems with trying to process many files which the basic command-line behaviour doesn't cope well with in recent Windows versions.

I only play mp3 files, no idea if it happens with other formats.I'm using the latest build (1.99.27.21136 (x86))

Are you also looking at the metadata &/or making changes to the metadata of those MP3 files?

95

Preview Build Discussion / Re: WACUP is almost perfect, 2 minor issues

« Last post by nxho on April 12, 2025, 06:30:31 AM »

As a sort of work-around for the Enqueue option, you can Right-Click on a file in WACUP's Media Library and choose the Enqueue option there to add it to the current playlist.



I know not the same as doing it from Explorer but thought I'd mention it.

ahh you got me excited for a moment:) I have a unique habit of downloading a lot of mp3's and deleting about 95% of them. I never used the media library for this kind of work. But thanks for mentioning it, good to know it's there in some form:)

96

Preview Build Discussion / Re: WACUP is almost perfect, 2 minor issues

« Last post by MarkRH on April 11, 2025, 11:33:08 PM »

As a sort of work-around for the Enqueue option, you can Right-Click on a file in WACUP's Media Library and choose the Enqueue option there to add it to the current playlist.



I know not the same as doing it from Explorer but thought I'd mention it.

97

Preview Build Discussion / Re: WACUP is almost perfect, 2 minor issues

« Last post by nxho on April 11, 2025, 07:04:12 PM »

1) This is noted as not being a thing in the build related information shown during install of the preview build.

Sorry I didn't read that one. Does this mean it's not getting added in the future since I'm the only soul who is still using it or are you guys busy with much more important stuff and It will eventually come?

2) That shouldn't be happening & I'd need to know what file type(s) it's happening with as I'd resolved all instances of files being held onto that I could replicate (there's still a window of a few seconds after a file is accessed due to me caching access to them to make repeated metadata queries not have to take as long again during that time) otherwise the access to the file especially if playback has stopped shouldn't leave anything in a held open state (unless it's maybe a bug with the re-used in_mp3 again). Would also need to know what build of WACUP you're having this issue with.

I only play mp3 files, no idea if it happens with other formats.I'm using the latest build (1.99.27.21136 (x86))
Thanks for your response! Let me know if you need more information

98

Preview Build Discussion / Re: WACUP is almost perfect, 2 minor issues

« Last post by dro on April 11, 2025, 06:50:02 PM »

1) This is noted as not being a thing in the build related information shown during install of the preview build.

2) That shouldn't be happening & I'd need to know what file type(s) it's happening with as I'd resolved all instances of files being held onto that I could replicate (there's still a window of a few seconds after a file is accessed due to me caching access to them to make repeated metadata queries not have to take as long again during that time) otherwise the access to the file especially if playback has stopped shouldn't leave anything in a held open state (unless it's maybe a bug with the re-used in_mp3 again). Would also need to know what build of WACUP you're having this issue with.

99

Preview Build Discussion / WACUP is almost perfect, 2 minor issues

« Last post by nxho on April 11, 2025, 06:32:38 PM »

Recently switched from decades of Winamp abuse,I have 2 issues for which the solution may be hidden somewhere in the settings but I'm unable to locate them:

1: Winamp used to add "enqueue" to the Windows context menu after install. With it I used to add mp3 files directly to the playlist. Any way to bring it back? I really miss it. Used to be somewhere in the top part in the context menu for mp3's

2: Can't delete the folder (in Windows Explorer) where the last played track is located, even when playback is stopped. Need to exit Wacup to delete the folder. Why is it using hooking a folder with no playback? Any solution?

I'm on Win 11 22H2

100

Skins / Re: Quinto Black CT

« Last post by Aminifu on April 11, 2025, 02:26:09 AM »

Do I also have to remove the studio.xnf file?

I don't know but as far as I can judge probably not.

Hi ariszlo,

As dro stated, it has been a long standing requirement to remove the studio.xnf file and let it be re-built when updating Quinto Black CT. It would be nice if that was no longer needed.

Do you have a way of directly contacting Peter? I tried via the last email address I have for him. No reply as far.