Latest restricted WACUP beta release is build #18916 (April 18th 2024) (x86 & x64 changelogs) | Latest WACUP public preview is build #18916 (April 18th 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.

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 ... 102
1
Skins / Re: Convert / Update old skin?
« on: Today at 12:04:28 AM »
The skin is working correctly for one from 1999 which pre-dates the classic skin additions that Winamp 2.9x introduced in 2003.

If you get a copy of the Skinner's Atlas then the gen.bmp & genex.bmp from it are the files that would need to be added into the old skin along with reading the txt file in the wsz (it's just a zip file so there's nothing special about it) or there's an online copy at https://github.com/WACUP/Winamp-Skinning-Archive/tree/master/Classic%20Skins/Skinners%20Atlas to read through.

There should be enough from the old skin to be able cobble something together to create those 2 files & then you can add them into the existing zip file or leave it as a pre-extracted folder within the Skins folder.

-dro

2
There'll be a fixed build in the day or so. The problem has existed for a couple of years in my code & despite it not having been changed for the new build (haven't gone back & checked other recent beta builds) it seems to be manifesting in a more consistent manner if going to the base skin is involved as part of the chain of switching attempts.

-dro

3
Have now replicated the issue & am looking into what might be going on.

-dro

4
I've had another user report this earlier today despite it not having been mentioned with any of the betas from the prior few month's so I'm not sure why it'd now be messing up other than it's somewhat the nature of trying to re-use the modern skin plug-in gen_ff dll from 5.666 & something yet unknown to me isn't working right.

Compared to the old preview they are for the most part 2 different implementations now & gen_ff was never really meat to be able to work outside of a native winamp implementation as WACUP is now doing.

All I can suggest for now is to try running wacup using wacup.exe /procdump to see if there might be a weird crash happening (something that gen_ff can randomly do) & it could be that's happening & measures to try to avoid a full crash are actually working at the expense of a weird non-skin changing experience.

-dro

5
Skins / Re: Big Bento Modern v1.2
« on: April 18, 2024, 09:02:14 PM »
Could you share fileinfo.m and sc_aerosnap.m for Big Bento Modern v1.2.3, please?
The 4 modified .m files have now been attached as a zip on the first post.

-dro

6
Skins / Re: Big Bento Modern v1.2
« on: April 15, 2024, 11:20:40 AM »
Or maybe I'd not seen the question & as modifying the skin is something anyone can technically do unless what you've still to ask is a gen_ff / core implementation aspect & then who knows what can or cannot be done, rather than asking if it's ok to ask, just ask for it.

-dro

7
Preview Build Discussion / Re: Playback Question
« on: April 09, 2024, 11:54:18 AM »
That action hasn't had any control over the behaviour used nor has WACUP's handling of it changed in a long time so here's what is coded.

If you use the action from the right-click menu or the open action in the main window then it treats it as a play action which'll clear the existing playlist & start playing be it the first item or the first one in the generated shuffle table. That's also why those actions are named / placed where they are.

If you use the add folder option from the playlist editor then that will treat it as an enqueue event & won't change what's playing.

Maybe that menu block could be changed to follow the media library default action (play/enqueue/enqueue & play) with it updating the text for the root of the menu item to then have it contextually be correct.

-dro

8
Using files correctly tagged with albumartist is the preferred option. Alternatively going to preferences -> media library -> local library -> unchecking "Use Album Artist when grouping the Album & Albumart filter results" might in some cases group things in a more expected manner depending on what metadata has been found from the files to start with.

-dro

9
General Discussion / Re: Windows 11 screen doesn't turn off.
« on: April 03, 2024, 10:44:55 AM »
Using either of the DSP plug-ins shouldn't make a difference to the behaviour about staying awake or not as it's the playback state which determines things & not the DSP which is just part of the input -> output chain going on.

-dro

10
Preferences -> Advanced -> Error Reporting -> uncheck "Send crash report via email using default email program (if available)" then that'll avoid it using what's basically a fallback mode as WACUP will also auto-submit the crash report (as long as it can be generated) to the server. The error shown appears to be from the OS itself & there's at least 2 different ways the OS recognises what's the default email client & iirc the api that I use doesn't seem to see it for some which is why it's simpler to un-check the option noted).

re: your crash, if you go to preferences -> plug-ins -> output -> in the drop down change from Not So Direct to Not So Yasapi & that should avoid the issue the Not So Direct plug-in is having with some setups like yours due to how it's trying to manage the output device.

-dro

11
General Discussion / Re: Windows 11 screen doesn't turn off.
« on: April 02, 2024, 10:20:27 AM »
Preferences -> Playback -> Playback tab -> uncheck "Use system keep-alive (default: on)"

That's enabled by default as there's numerous setups where the device / monitor needs to be kept on for the audio to be heard (e.g. due to integrated speakers) but in your instance it's not going to be helpful hence the option.

-dro

12
General Discussion / Re: ReplayGain calculation is broken
« on: March 28, 2024, 03:05:41 PM »
The "missing required decoder" could be related to a known bug with the newer preview build. There's a fix is already in place with the 18654 beta build ("Fixed a recurring failure when trying to send files to be processed for replaygain due to a timing & feature validation conflict when checking writing replaygain metadata is supported" unless it's actually a real case of being a file type not handled. At least the newer preview build is seemingly working better than the one you had been using when it comes to the RG handling.

-dro

13
General Discussion / Re: ReplayGain calculation is broken
« on: March 28, 2024, 02:38:40 PM »
https://getwacup.com/preview/ has the current public preview builds available (all of the builds that have been provided are essentially betas whether they're limited access or done as public previews).

If you're concerned about breaking an existing install then you can easily make portable test installs with the WACUP installer to check if the newer build resolves the issue or not. If it doesn't help then I'll need more information on the files being sent &/or some example files.

-dro

14
General Discussion / Re: ReplayGain calculation is broken
« on: March 28, 2024, 02:16:30 PM »
Not everything supports RG & the plug-in handling things will only accept files where there's an appropriate input plug-in that supports the format converter api which is needed to get the audio data without hacks to fake play things.

Without knowing what you're trying to process & also what WACUP build (as you've mentioned "both of options" which to me sounds like the old 2021 preview build instead of the 2023 one) it's hard to be certain if it's just a build bug or something else that I'm not aware off.

-dro

15
General Discussion / Re: ReplayGain calculation is broken
« on: March 28, 2024, 01:50:25 PM »
When you send files to have RG calculated via the send-to menu then a skinned window will appear to show what's going on.

-dro

Pages: [1] 2 3 ... 102