Latest restricted WACUP beta release is build #17040 (September 30th 2023) (x86 & x64 changelogs) | Latest WACUP public preview is build #17040 (September 30th 2023) (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

Pages: 1 2 [3] 4 5 ... 10
21
Hi binco81,

I, for one, do use the 'advance to next on stop' option so disabling it is not a viable fix for your issue, imo. Hopefully dro will be able to fix your issue in the next release without having to disable any of the current WACUP functions.

Yes, I understand people use it. The part I said about "disabling it since I don't use it" would be like me disabling a specific plugin that possibly controls this part.

I wasn't suggesting to remove this function from WACUP, I was just curious if disabling some specific plugin on my end would make a temporary fix for this problem here, without affecting anyone else.
22
Hi binco81,

I, for one, do use the 'advance to next on stop' option so disabling it is not a viable fix for your issue, imo. Hopefully dro will be able to fix your issue in the next release without having to disable any of the current WACUP functions.

23
It's a processing conflict with the 'advance to next on stop' option which is handled via Alt+Click & due to how the stop hotkey is sent the handler isn't seeing that it's from within a hotkey action & so toggles that option instead of doing the stop that's wanted. Will look to get it fixed for the next build.

-dro

Thank you for looking into it.

In the meantime, is there a workaround to "fix" this? Like disabling the function using the ALT+CLICK since I don't use it?
24
It's a processing conflict with the 'advance to next on stop' option which is handled via Alt+Click & due to how the stop hotkey is sent the handler isn't seeing that it's from within a hotkey action & so toggles that option instead of doing the stop that's wanted. Will look to get it fixed for the next build.

-dro
25
Possible bug

I started using WACUP recently but I noticed a weird behavior while trying to set some Global Hotkeys that I always used with Winamp 5.666 and other previous Winamp ersions without any problems.

When I try to use the combination of ALT+anything (a few hotkeys I tried: ALT+1, ALT+S, ALT+numpad 3) for the "Playback: Stop" function, WACUP doesn't show any error and allows this combination, but when the music is playing, it just won't stop the music when using those hotkeys. If I use literally the same combinations (ALT+1, ALT+S, ALT+numpad 3) for "Playback: Play" or "Playback: Pause", it works normally.

I tried replacing ALT with CTRL and use the same combinations for the second key (CTRL+1, CTRL+S, CTRL+numpad 3) for "Playback: Stop" and it works normally. Even CTRL+ALT+anything works. It just won't work with ALT+any combination for some weird reason.

I even used Hotkey Screener to see if another program was using those hotkeys, but it said wacup.exe was the "owner" of the hotkeys using ALT+something, so it appears to WACUP is not saving or blocking the use of ALT+anything for the "Playback: Stop".
26
Skins / New modern skin : Asrec.
« Last post by parisienne17 on November 09, 2023, 02:18:12 AM »
Big thanks to the unvaluable help and kindness of Ariszlô who provided me skinning knowledge and tweaked scripts which allowed me to complete my first winamp skin. This is a 7 modes one, somehow minimalistic but I tried to keep it ergonomic and graphic with 2 modes housing visualisation.

Don't be surprised by missing pop-up entries when switching modes : due to a fickle vis holder, Ariszlô made it to prevent switching from one visualisation mode to another. Just go to a non one THEN switch back to your favorite treat.

This is a V1 with minor cosmetic tweaks to come but feel free to use it and comment on your whishes to better it.
Another one is to come soon on a port of the good old Sonique Cell skin by Sonitec (screenshot below).


Asrec.
https://drive.google.com/file/d/1QlKwLIAcvSbgx2797SyNOiywTZEAtlfI/view?usp=sharing



   
Cellamp.

27
That shouldn't be needed now with the handling that's in place to try to maintain the shuffle table between sessions (as long as what's in the main playlist doesn't massively change between instances). It even tries to avoid including items already played if what's in the playlist has changed to only account for what's left to be played (which can be monitored via the diagnostic prefs pages).

Winamp had those issues in not being able to maintain things & yes shuffle off & manually triggering the randomise is the other way to see what's going on _but_ for WACUP which hasn't relied on Winamp's handling for shuffle / randomise in many years now, both shuffle & random actions go through the same code, it's just whether the main playlist queue list or the shuffle list is the one that gets updated.

-dro
28
Hi

I had the 2nd problem years ago when I was using total random programmation and I found a way to do it so you never have twice the same song.

Once you loaded your songs and folders in the playlist window click down the playlist window on Misc > Sort > Randomize list

The keyboard shortcut is Ctrl+Shift+R

You can do this twice or more if you think the order is not your taste and then you play the whole playlist from the first song without enabling the shuffle mode

It's another way to shuffle

Hope it helps
29
Preview Build Discussion / Re: OGG files not playing in Public Preview v17040
« Last post by Phuntso on November 01, 2023, 08:28:09 AM »
I kid you not I just found out the damn cause...

I downloaded random OGG sample files to test to see if there's something about my OGG files that specifically the latest WACUP PB is picky about...

Get any OGG file, set the file attribute to 'Read-only' and then try playing it - WACUP cannot read the OGG file anymore, it cannot even display its metadata properly, if at all. In 'Read-only' for WACUP the 'file is corrupted' and its playback is skipped.

My MP3s, FLACs and MIDis are unaffected by 'Read-only' bug.


That leaves the window glitching issue which is also new in latest PB.

To test this, you need some application running that shows on the desktop, like Stickies (by Zhorn Software, freeware btw) or a windowed full screen app.
Minimize WACUP to tray. Then click on its tray icon to make it come up. You'll notice that in case of a running windowed full screen app WACUP's window doesn't show and in case of Stickies it hides behind the sticky note on the desktop, as if following 'bottom-most' order instruction. Even if to toggle WACUP to be 'Always On Top' it will have hard time following that instruction.
The previous PB didn't have issues showing its window, I also never had to enable 'Always On Top'.

The latest PB also has difficulties rendering the Drone skin by R. Peter Clark and 883DESIGN (year 2006 skin) - e.g.: playlist border disappears after going over an element which shows a 'tooltip'. The Drone skin tooltips now also have extra black bits which aren't supposed to exist.


Alright now, happy solving! Will be waiting for next PB. :)
30
General Discussion / Re: Can I sync an Ipod classic to my Wacup Library?
« Last post by dro on October 31, 2023, 10:34:07 PM »
Did you also try using ml_ipod instead of the ml_pmp / pmp_ipod option ?

-dro
Pages: 1 2 [3] 4 5 ... 10