Latest restricted WACUP beta release is build #14278/14282 (January 23rd/24th 2023) (x86 & x64 changelogs) | Latest WACUP public preview is build #7236 (March 11th 2021) (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 ... 94
1
Skins / Re: Big Bento Modern v1.2
« on: January 31, 2023, 05:08:46 PM »
There's now a generic patch in place for the next beta build to deal with the file existence checks that'll do what's needed irrespective of the file existing or not.

-dro

2
Skins / Re: Big Bento Modern v1.2
« on: January 28, 2023, 11:17:12 PM »
It's not just BBM that has this issue & there's old versions of the skins that I know are being used which are still affected. So even with a better implementation for the skin, I've still got to make changes on the core side to deal with this.

Really I need to find a way to provide a proper skin script call to use to check than all of these file existence checks as they don't work 100% but that still involves the skins being updated & means the old ways need to be dealt with.

-dro

3
Skins / Re: Big Bento Modern v1.2
« on: January 28, 2023, 10:31:36 PM »
Ah, I see what's going on. I'll need to edit the patching that's done on the skin version checks to avoid that (really can't remember why that file got picked with this skin for "winamp" vs wacup version detection).

-dro

4
Skins / Re: Big Bento Modern v1.2
« on: January 28, 2023, 02:51:21 PM »
That doesn't make sense as there's nothing that should be needing to touch the OS registry when it comes to a skin specific option. As trying with the option enabled & disabled, toggling the skin provided option has the window going from being integrated to external & back again with it following the expected state. Only thing I can otherwise think of is that there's a conflict from another plug-in present but that should still exist irrespective of that option being set *confused*

-dro

5
Preview Build Discussion / Re: Many bugs
« on: December 29, 2022, 09:18:59 PM »
When I'm back from a needed rest after the new year I'll read through the above & any PM's that have been sent.

-dro

6
General Discussion / Re: Internet Radio + Podcasts not working
« on: December 22, 2022, 11:25:11 PM »
I've just tried the url with the current beta & the preview build & it appears to play ok. Am not sure why it's showing the state it is though it's handled via one of the plug-ins being re-used from 5.666 so that might be part of the issue or there's something on their side that's been set to block access via a player that reports itself to be winamp-like (have known that to happen as some stations will view it as a streamripper).

I'd need an example of the podcast feed trying to be added to see if I can replicate it crashing or not.

-dro

7
General Discussion / Re: Where to find "Search in Playlist" function?
« on: December 19, 2022, 02:17:29 PM »
The in-playlist search field is a skin specific thing & isn't something that the WACUP copy of the Winamp Modern skin implements. The intent is to implement something that works irrespective of the skin but isn't high priority for now when the jump to file dialog exists (which I get isn't as convenient as an inlined search field vs having to have another window open).

With the padding request, there isn't a way to add that & tbh it's probably not something I'd try to implement as imho it's better to have the playlist items use the whole space of the window area that they fill unless there's some specific reason for needing the padding? As I'm not remembering it allowing for anything special like a way to quickly deselect the item(s), etc.

Sorry if that all comes across as somewhat negative.

-dro

8
General Discussion / Re: replaygain ? whats all about?
« on: November 12, 2022, 04:49:06 PM »
You may need to look at the replaygain preferences & adjust the mode that is used as depending on what metadata is present for the file it may end up using the default adjustment i.e. you might be better using the track level instead of album level. There's also a bug with MP3 files where it's not correctly applied because of problems with the re-used plug-in from 5.666 which may also be causing you problems.

-dro

9
Preview Build Discussion / Re: Milkdrop
« on: November 12, 2022, 01:57:24 PM »
Desktop mode is implemented in a different manner with WACUP compared to the 5.666 build of the plug-in & that prevents the old shortcut working. I don't have a suggestion at this time on how to achieve the old behaviour with the WACUP build of milkdrop.

-dro

10
General Discussion / Re: unhiding wacup
« on: November 07, 2022, 12:59:13 PM »
Changing double or triple size mode can vary a bit on how it's going to adjust the position of the windows depending on where they are at the time as well as what type of skin is being used. For classic skins there are also some issues with the handling depending on which monitor if it's a multi-monitor setup it is & the relative position of the monitor that WACUP is running on compared to the primary one. Additionally when the windows are not grouped then things can change around as well. I don't have any intentions on changing the behaviour that's used for now after the mess that went one post-preview build with it.

-dro

11
That has the same effect as Ignorant Output doesn't do anything. I just wasn't sure if you're needing to locally listen to things or not at the same time.

-dro

12
The problem is mostly like that what you're hearing isn't what the streaming dsp is getting as the option to crossfade slightly on track change in the default output plug-in is probably enabled. If you goto preferences -> plug-ins -> output -> directsound -> fading tab to disable it & see if that helps.

As the output plug-in fakes crossfading whereas the dsp is just going to get the immediate data given to it & that can cause these hard-cuts on track change & is something that I'm going to eventually re-work so my streaming source plug-in will instead get things in a manner after all processing & the output plug-in won't be responsible for track cross-fades (i.e. allowing it to work in a manner that's expected irrespective of the plug-ins being used).

-dro

13
Preview Build Discussion / Re: WACUP not adding my flacs to the library
« on: October 09, 2022, 12:21:47 PM »
It's a bug with the current build as I've got this in the changelog for what'll eventually become the next preview build.
Quote
Fixed the api for getting the current list of supported file extensions not always generating a valid response which would then cause things like local library importing or folder drag & drop to miss files
-dro

14
Skins / Re: Issues with Components and desktopalpha="1"
« on: October 01, 2022, 11:01:31 PM »
I guess I'm wrong / misremembering as i didn't think any non-wasabi windows would work unless it's down to those skins doing their standard frame in a way to fake transparency (am not in a position to try out the skins to check for a few more days).

As I read it as related to how Windows does composition of multiple windows within a parent. Modern skins are a pain so whatever 😉

-dro

15
Skins / Re: Issues with Components and desktopalpha="1"
« on: October 01, 2022, 05:37:13 PM »
From what I remember it's due to how the OS works with layering of child windows though I think things changed with that well after gen_ff was initially made that might now allow it to work with modification of some aspects with window creation (not something you can do via maki). Something to possibly look into once I've gotten back into coding.

-dro

Pages: [1] 2 3 ... 94