91
Preview Build Discussion / Re: WACUP Preview Build 1.9.20.17040 Annoyance
« Last post by MourningStar on January 30, 2024, 06:59:35 PM »... I like the blinking ...+1
Latest restricted WACUP beta release is build #18980 (April 24th 2024) (x86 & x64 changelogs) | Latest WACUP public preview is build #18980 (April 24th 2024) (x86 only)
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.
Recent Posts
92
Preview Build Discussion / Re: WACUP - First experiences, bugs, wish list
« Last post by Altus on January 30, 2024, 06:49:27 PM »1) When you say "metadata from the local library" do you mean the "Media library"? I have deactivated it completely and this could explain why it works differently for you, if the changes you made in the next build have nothing to do with it. With Winamp I can load the playlists however I want, they are always loaded correctly.
>> Update <<
Okay, I started all over again with a fresh WACUP full installation. And lo and behold, the playlists are also loading correctly. So I deactivated plug-in after plug-in to see which one was to blame, but it worked all the time. But then I realized the difference: Shuffle! Shuffle is practically always on for me, if I turn it off then I can load all playlists just like in Winamp.
Something seems to work differently with the shuffle in WACUP than in Winamp. Firstly, the loading of the playlist and secondly, WACUP (if you start WACUP with a *.m3u8 file and shuffle is on) always plays song #1, which I assume should not be the case.
2) I've been using Winamp "since forever" but I have no idea what's going on under the hood. And I've only known WACUP for a short time and therefore know much less about WACUP than about Winamp. I am only reporting as a beginner WACUP user what I have noticed. The way it is for me at the moment, setting a search limit is useless for me. Even if the idea is quite clever, I lose the ability to scroll quickly.
I already said in post #1 that it would probably be difficult to change the plug-in so that both are possible. The cursor would have to start on the current song and then distribute the limit up and down. Then even a limit of 100 would certainly be enough. But it's not so tragic. The songs are only on a SATA SSD but the search is still quite fast. But Slower than in Winamp, by the way.
But WACUP isn't finished yet, so I'll just wait for the final release!
3) About performance and timers: Here too, of course I had no idea that there were so many dependencies. My Winamp always runs in "Windowshade Mode" and all animations are always completely deactivated via the skin option, so I only see the effects of the timer in Winamp on the scrolling song ticker and the spectrum analyzer.
Regarding CPU utilization: This varies depending on the CPU, of course. I only have the values of a 24 thread CPU at hand. However, Winamp is also used on an old 4-core with 8 threads, where the difference is much more noticeable. Winamp and WACUP are compared with the original Modern Skin when playing the same song. The animations are deactivated on both and both run in Windowshade mode.
For a better understanding: 100% / 24 threads = 4.16% would be one thread.
@60fps/16.6ms:
Winamp: 0,19% (min) 0,25% (max) WITHOUT Scrolling Song Title.
WACUP: 0,24% (min) 0,29% (max) WITHOUT Scrolling Song Title.
Winamp: 0,21% (min) 0,31% (max) WITH Scrolling Song Title.
WACUP: 0,25% (min) 0,32% (max) WITH Scrolling Song Title.
@30fps/33.3ms:
Winamp: 0,17% (min) 0,22% (max) WITHOUT Scrolling Song Title.
WACUP: 0,22% (min) 0,29% (max) WITHOUT Scrolling Song Title. << Almost the same @60fps ??
Winamp: 0,17% (min) 0,24% (max) WITH Scrolling Song Title.
WACUP: 0,25% (min) 0,32% (max) WITH Scrolling Song Title.
Hidden (ALT+W):
Winamp: 0,09% (min) 0,12% (max)
WACUP: 0,18% (min) 0,24% (max)
@15fps/66.6ms (my winamp default):
Winamp: 0,09% (min) 0,12% (max) WITHOUT Scrolling Song.
Winamp: 0,14% (min) 0,20% (max) WITH Scrolling Song.
Interesting that if you hide the main window and only show the tray icon (ALT+W), WACUP uses twice as much CPU as Winamp. The values seem ridiculous, of course, but this is due to the number of threads. Nevertheless, the utilization is significantly higher than with Winamp. But if the switch to 30fps in WACUP doesn't really help, then a switch to 15fps probably won't either. Apparently WACUP simply works differently than Winamp.
Oh, one more thing: When I unpacked the fresh installation and clicked on the "Disable Local Library plug-in..." the following dialog appeared:
I think there are a few typos in there
>> Update <<
Okay, I started all over again with a fresh WACUP full installation. And lo and behold, the playlists are also loading correctly. So I deactivated plug-in after plug-in to see which one was to blame, but it worked all the time. But then I realized the difference: Shuffle! Shuffle is practically always on for me, if I turn it off then I can load all playlists just like in Winamp.
Something seems to work differently with the shuffle in WACUP than in Winamp. Firstly, the loading of the playlist and secondly, WACUP (if you start WACUP with a *.m3u8 file and shuffle is on) always plays song #1, which I assume should not be the case.
2) I've been using Winamp "since forever" but I have no idea what's going on under the hood. And I've only known WACUP for a short time and therefore know much less about WACUP than about Winamp. I am only reporting as a beginner WACUP user what I have noticed. The way it is for me at the moment, setting a search limit is useless for me. Even if the idea is quite clever, I lose the ability to scroll quickly.
I already said in post #1 that it would probably be difficult to change the plug-in so that both are possible. The cursor would have to start on the current song and then distribute the limit up and down. Then even a limit of 100 would certainly be enough. But it's not so tragic. The songs are only on a SATA SSD but the search is still quite fast. But Slower than in Winamp, by the way.
But WACUP isn't finished yet, so I'll just wait for the final release!
3) About performance and timers: Here too, of course I had no idea that there were so many dependencies. My Winamp always runs in "Windowshade Mode" and all animations are always completely deactivated via the skin option, so I only see the effects of the timer in Winamp on the scrolling song ticker and the spectrum analyzer.
Regarding CPU utilization: This varies depending on the CPU, of course. I only have the values of a 24 thread CPU at hand. However, Winamp is also used on an old 4-core with 8 threads, where the difference is much more noticeable. Winamp and WACUP are compared with the original Modern Skin when playing the same song. The animations are deactivated on both and both run in Windowshade mode.
For a better understanding: 100% / 24 threads = 4.16% would be one thread.
@60fps/16.6ms:
Winamp: 0,19% (min) 0,25% (max) WITHOUT Scrolling Song Title.
WACUP: 0,24% (min) 0,29% (max) WITHOUT Scrolling Song Title.
Winamp: 0,21% (min) 0,31% (max) WITH Scrolling Song Title.
WACUP: 0,25% (min) 0,32% (max) WITH Scrolling Song Title.
@30fps/33.3ms:
Winamp: 0,17% (min) 0,22% (max) WITHOUT Scrolling Song Title.
WACUP: 0,22% (min) 0,29% (max) WITHOUT Scrolling Song Title. << Almost the same @60fps ??
Winamp: 0,17% (min) 0,24% (max) WITH Scrolling Song Title.
WACUP: 0,25% (min) 0,32% (max) WITH Scrolling Song Title.
Hidden (ALT+W):
Winamp: 0,09% (min) 0,12% (max)
WACUP: 0,18% (min) 0,24% (max)
@15fps/66.6ms (my winamp default):
Winamp: 0,09% (min) 0,12% (max) WITHOUT Scrolling Song.
Winamp: 0,14% (min) 0,20% (max) WITH Scrolling Song.
Interesting that if you hide the main window and only show the tray icon (ALT+W), WACUP uses twice as much CPU as Winamp. The values seem ridiculous, of course, but this is due to the number of threads. Nevertheless, the utilization is significantly higher than with Winamp. But if the switch to 30fps in WACUP doesn't really help, then a switch to 15fps probably won't either. Apparently WACUP simply works differently than Winamp.
Oh, one more thing: When I unpacked the fresh installation and clicked on the "Disable Local Library plug-in..." the following dialog appeared:
I think there are a few typos in there
93
Preview Build Discussion / Re: WACUP Preview Build 1.9.20.17040 Annoyance
« Last post by Aminifu on January 30, 2024, 05:12:42 PM »This reminds me that there is no way to please everyone.
As an older user, I like the blinking when I pause playback. Sometimes I get called away for whatever reason and sometimes I pause playback and sometimes I don't. When I return, the blinking reminds me that I paused playback and the lack of sound doesn't mean the app has stopped working.
As an older user, I like the blinking when I pause playback. Sometimes I get called away for whatever reason and sometimes I pause playback and sometimes I don't. When I return, the blinking reminds me that I paused playback and the lack of sound doesn't mean the app has stopped working.
94
Preview Build Discussion / Re: WACUP Preview Build 1.9.20.17040 Annoyance
« Last post by dro on January 30, 2024, 02:57:27 PM »Hmm, it should have been doing it with any older WACUP builds as that's what the winamp skins tend to do unless a skin has been specifically coded not to that behaviour (which is only possible if it's a winamp3 / modern style & in the current builds isn't possible to disable for classic / 2.x style skins).
If it's a classic / 2.x style skin then there's an option which is already present for the next preview build, for the other skin types then there's no simple toggle option to do it.
-dro
If it's a classic / 2.x style skin then there's an option which is already present for the next preview build, for the other skin types then there's no simple toggle option to do it.
-dro
95
Preview Build Discussion / WACUP Preview Build 1.9.20.17040 Annoyance
« Last post by LMHess on January 30, 2024, 02:29:44 PM »I have installed the current Public Preview Build 1.9.20.17040 and everything seems to be working just fine except when I pause playback the time indicator blinks.
Older versions of WACUP didn't do this and it is **EXTREMELY** annoying. Any way to turn this "feature" off? I couldn't find a setting for it.
Older versions of WACUP didn't do this and it is **EXTREMELY** annoying. Any way to turn this "feature" off? I couldn't find a setting for it.
96
Skins / Re: Defix - Yukon
« Last post by Denis on January 30, 2024, 08:33:45 AM »
I don't have a 4K monitor yet (still using 1920 x 1080), so I down-scaled it to 50%. So far, it is performing as well as the other modern skins I'm using. I'll provide some specifics after I play with it for awhile.
I also don’t have a 4K monitor yet, but if I get one, I’ll already have a skin for it) Moreover, the scaling works better than expected, I recently launched a skin for 1366x768 with a scaling of 40%, it works quite stable.
97
Skins / Re: Defix - Yukon
« Last post by Aminifu on January 30, 2024, 04:14:16 AM »Hi Denis,
I really like what you have so far. The color theme is easy on my old eyes.
I pray your life changes do not turn out as bad as you fear and you get the chance to finish this skin.
I don't have a 4K monitor yet (still using 1920 x 1080), so I down-scaled it to 50%. So far, it is performing as well as the other modern skins I'm using. I'll provide some specifics after I play with it for awhile.
@dro
Thank you for pointing out the download link. Don't understand how I missed it, when it was right in front of me.
I really like what you have so far. The color theme is easy on my old eyes.
I pray your life changes do not turn out as bad as you fear and you get the chance to finish this skin.
I don't have a 4K monitor yet (still using 1920 x 1080), so I down-scaled it to 50%. So far, it is performing as well as the other modern skins I'm using. I'll provide some specifics after I play with it for awhile.
@dro
Thank you for pointing out the download link. Don't understand how I missed it, when it was right in front of me.
98
Skins / Re: Defix - Yukon
« Last post by dro on January 30, 2024, 01:17:37 AM »It's the first of the attachments in the initial post.
-dro
-dro
99
Skins / Re: Defix - Yukon
« Last post by Aminifu on January 30, 2024, 12:27:55 AM »But one way or another, if you use it or just test it, then I would like to know with what scaling and what resolution, whether everything works correctly and stably, perhaps you will have ideas and wishes.
...
I would like to test it, but I don't see a way to download it.
100
Skins / Re: Defix - Yukon
« Last post by Denis on January 29, 2024, 07:16:23 PM »Completed Volume (I took the idea from one of the Ariszlo skins) and Coverflow scripts.
Since I took the Big Bento skin as a basis, I don’t see any point in posting the rest of the skippts, they either haven’t changed yet or require improvement.
Since I took the Big Bento skin as a basis, I don’t see any point in posting the rest of the skippts, they either haven’t changed yet or require improvement.