Latest WACUP public preview for x86 & x64 is build #20202 (September 28th 2024) (x86 & x64 changelogs)
Latest restricted WACUP beta release is build #20202 (September 28th 2024) (x86 & x64 changelogs)


NOTE: Beta testers are added in a limited & subjective manner as I can only support so many people as part of the beta test program to keep it useful for my needs.

Unless I think you're going to be helpful, not all requests will be accepted but might still be later on. Remember that beta testing is to help me & the limitations currently works for my needs for this project.

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 - dro

Pages: [1] 2 3 ... 111
1
Can you not restore the removed file then start it normally & turn repeat off? Also is it repeat all or repeat track that you've enabled as well as what skin are you using? If you're not able to restore the file you could try opening the winamp.ini in the wacup settings folder & remove the repeat= line & then try again (though I can't remember if that'll help if a modern style skin is being used).

Not that it should be able to crash in such a scenario but based on the wording of things I've got to assume it's not triggering my crash reporter (if possible running wacup.exe /procdump once before trying to edit the winamp.ini file would be helpful to try to get a crash report so I can try to resolve whatever is going wrong here).

-dro

2
General Discussion / Re: Google instead of Bing for Artowrk search
« on: October 23, 2024, 08:12:41 PM »
Also, I'm still hoping to see the display of the Track/Total track somewhere...
You'll need to edit the skin to do that which will likely require editing & compile maki script files to achieve it - is probably better for you to do it (per this for some of the ways to go about doing it) or find someone willing to do it for you as you'll know where in the ui you're wanting it to appear, etc.

-dro

3
Skins / Re: Any way to make minor changes to an existing skin?
« on: October 23, 2024, 08:08:51 PM »
For the pink section, go to preferences -> plug-ins -> media library -> un-check the plug-ins you don't need & that'll remove those items after a wacup restart. Everything else would involve editing the skin as already mentioned (the red block might be able to be done via xml edits only otherwise you're going to be looking at maki editing to achieve things).

-dro

4
General Discussion / Re: Playlist Window resizing with monitor off/on
« on: October 23, 2024, 12:08:49 PM »
The main window can't change its dimensions whereas the main playlist window can & there's probably something going on that I've yet to replicate where maybe if the monitor is being turned off its causing a possible resolution / dpi change to occur that's then messing with things as a first guess though doing similar things from a quick test doesn't seem to do it so maybe there's something else running doing it.

What version of Windows are you using? Also just to rule out something, what happens if you have wacup set to run at 1x mode instead of double-sized.

-dro

5
General Discussion / Re: Google instead of Bing for Artowrk search
« on: October 23, 2024, 12:04:32 PM »
Options -> Web Content -> select google though I'm tempted to remove that block of options & the initial menu from your screenshot since other parts of the player can effectively do a better job.

-dro

6
General Discussion / Re: Google instead of Bing for Artowrk search
« on: October 23, 2024, 09:36:10 AM »
Where are you using bing within wacup? I've got to assume that's probably a skin specific feature as the artwork look-up I use via sacad irrespective of skin type doesn't use it afaict.

-dro

7
Preview Build Discussion / Re: Song Ratings not displaying in File Info
« on: October 22, 2024, 09:38:16 PM »
It now working seems to point to it likely have been a slightly corrupted local library db which is where the ratings will have been stored in & is why trying out the new test install doesn't have them.

What you could try to do to get them back is to either use the library db import option (media library window -> library button -> import -> import legacy (external) db & point it to the old install settings folder (typically %appdata%\wacup\plugins\ml).

Alternatively in the other install, use ?rating=x in the search filter on the root local library view (where x is from 1 to 5) & then use the 'save as...' action on the view (button on the bottom) & save that out as an m3u8 playlist file before putting that into the main playlist of the new install & then batch selecting & setting the rating value that applies to them via the right-click menu after having selected all of them. A bit convoluted but it's maybe a simpler way to check first that what's about to be set is what's expected compared to the other option above.

-dro

8
Did WACUP's crash reporter get triggered? If it didn't then you'd need to try using the procdump mode (preferences -> advanced -> error reporting -> follow the instructions on that preference page) to try to collect something that is more likely to assist me. As what you've posted doesn't give me anything tangible to work with & from the auto-submitted crash reports since 20202 went up, there seems to have been a spike in notsodirect failures which seem to possibly be triggered by in_mp3 misbehaving but I've so far not managed to replicate it myself.

-dro

9
General Discussion / Re: Problems with WACUP startup
« on: October 17, 2024, 01:05:20 PM »
Can you provide a screenshot of your wacup instance in the broken state please as I'm not sure if it's a skin specific clock or the big clock window (though so far I can't replicate the big clock window not wanting to update in its clock mode).

-dro

10
Wishlist / Feature Requests / Re: Cpro File Info... enhancement
« on: October 13, 2024, 09:15:45 AM »
this is not winamp

11
Where were you loading the playlist from? As that's not something I'm seeing from a quick re-test from external & library playlist actions.

-dro

12
7236 & 20202 are massively different beasts with things that now aren't working because I've not either implemented them or there's bugs in my handling (directly or from trying to leverage some of the pre-compiled plug-ins still from 5.666 which have their own issues).

As 7236 was the last public preview build that fully needed the old winamp core to run whereas anything since has been able to run just on the wacup core with there being no legacy core usage needed for all of the 2024 builds which is probably why it might've been ok before & not now.

It's part of the things that I've got on my list to be looked into in the near term though really I need to get around to finish dropping the re-used in_mp3 & have my own proper consolidated tag handling implemented (hence the build type question as the x64 cannot modify mp3 file metadata).

-dro

13
Are you using the x86 or x64 build? Are you doing this with MP3 files by any chance?

If it's the x64 build then it's completely expected, if it's the x86 build then it wasn't really implemented & was more luck it worked depending on the input plug-in / file type that you're trying to modify with metadata editing as a whole needing to be finished off (more so for the benefit of the x64 build which lacks it at all for some of the formats such as MP3 due to how playback support for that is currently provided).

-dro

14
General Discussion / Re: Exporting my playlists
« on: October 11, 2024, 10:09:04 AM »
Not knowing if you've used the wacup managed or self-managed playlist copies (as that can have an impact due to potential use of relative file paths in the actual playlist files), typically if everything they refer to is in d:\music then on the new OS install the media they refer to needs to be in d:\music again & the settings would need to go back into %appdata%\wacup if taken from there on the prior install (where possible the wacup settings are used with relative locations in mind but there's still a lot of things especially the local library that use fixed paths which is why its simpler to just have everything be in the same place where possible).

-dro

15
Wishlist / Feature Requests / Re: Cpro File Info... enhancement
« on: October 11, 2024, 10:04:54 AM »
Double-clicking the artwork will try to open & select the item shown. It'd require scripting changes to the cpro framework to get it to show the filename & from a look at how the file info panel works, probably more work than is being asked for to make it use the space better when the drawer area isn't in the smallest height it offers. So double-click / right-click -> open folder is the best option to get some of the request.

-dro

Pages: [1] 2 3 ... 111