Latest restricted WACUP beta release is build #19100 (May 10th 2024) (x86 & x64 changelogs) | Latest WACUP public preview is build #19100 (May 10th 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 ... 104
1
That'd have been predixis musicip or something like that which I never liked since it was an embedded version of it's program instead of leveraging the existing libraries that winamp of that time was already providing. I know some liked it but imho it wasn't ever nice to use.

A form of dynamic playlists will be looked into at some point but it's not a top priority vs other things I've already got in the queue to finish & it should already be able to be achieved mostly by playing around with smartviews & the query language to try to get associated results since that's what I was planning on the dynamic playlists to be based around.

-dro

2
General Discussion / Re: album art overview
« on: May 28, 2024, 12:50:02 PM »
I've still to implement the details mode in my local library plug-in.

-dro

3
Preview Build Discussion / Re: Can't Play aac or wma Files
« on: May 26, 2024, 11:43:16 AM »
If in_dshow isn't present then most likely the install wasn't able to get in_mp3 which is the one which handles raw .aac files (the first file iirc is the winamp 5.1 example file or a close equivalent of it).

-dro

4
Not today as the full screen thing I was greeted with this morning on my win10 dev machine after it had rebooted to apply recent OS updates. Probably in the next few weeks once I've figured out the big stability issue affecting the current preview build.

-dro

5
Have had another report about this (had forgotten it had been reported on here already) so it seems like Win11's menus might be messing up custom drawing or just ignoring having the font applied which is then causing all of the menu width calculations to break (i.e. the bit that I rely on the OS to not mess up). Something else to check out once I start actively doing Win11 compatibility testing.

-dro

6
The drive location doesn't seem to be directly the reason & is something I'd messed up during some code consolidation causing what's passed to the OS api used to not behave as expected if the length of the filepath string for any items after the first item attempted to be removed is shorter than it.

For what I could replicate once I'd realised that (being on another drive just seemed to be a more obvious way to help replicate the issue), it should be resolved for when the next build is made available. The library playlists are working ok so it's just limited to the main playlist & at least doing it a file at a time or batch sending to a library playlist & removing from within there is a clunky but viable workaround for it.

-dro

7
It's being blocked by filename as there were a number of cases of it crashing & users not updating to newer builds of it that fixed it iirc or there was conflict between the 2 plug-ins (mine & theirs) being enabled at the same time. So to avoid me being spammed / getting complaints when the issue was not on my side, it was added to the block list.

As I'm offering the feature natively (was part of WACUP before I was ever aware of the other plug-in) & it does everything afaict that plug-in was doing plus more (i.e. it has albumart support along with none of the faff in having to setup your own app id, etc), not allowing the other plug-in by filename in this instance doesn't seem like a bad thing to be doing.

-dro

8
Preview Build Discussion / Re: Slight wording confusion
« on: May 24, 2024, 01:28:41 AM »
Have now made changes for the next build that should hopefully not end up being seen but if it is, it'll change the message shown during the different steps that are now in place to get the running instance(s) to close including different wording for the initially shown message.

-dro

9
I've tried out the main playlist & library playlist actions with the current 19100 build & it's removing things in the manner I'd expect (i.e. the playlist item is removed & the actual files appear in the recycle bin per the default settings to do that for physically removed files). Really could do with clarification on where in the ui you're trying to do the remove action.

-dro

10
Wishlist / Feature Requests / Re: German language
« on: May 23, 2024, 07:42:04 PM »
Intent yes, whether it'll happen is down to others if I ever get around to implementing localisation support. As WACUP is still only a preview build & I won't be doing anything towards language packs until the preview state gets dropped.

-dro

11
Thanks for letting me know it's helped improve stability for you.

-dro

12
Skins / Re: Waveform Seeker Plug-in colors
« on: May 20, 2024, 06:16:29 PM »
The waveform seeker stuff has been around for years whereas the big clock handling is from around 2 months back (or a few builds back as my sense of time is massively off at the moment).

-dro

13
Skins / Re: Waveform Seeker Plug-in colors
« on: May 20, 2024, 11:12:17 AM »
Waveform Seeker

For all skin types using a waveseek.txt file in the root of the skin:
Quote
[colours]
background=
cue_point=
status_text=
wave_normal=
wave_playing=
wave_failed=

For modern skins only:
Quote
plugin.waveseeker.background
plugin.waveseeker.cue_point
plugin.waveseeker.status_text
plugin.waveseeker.wave_normal
plugin.waveseeker.wave_playing
plugin.waveseeker.wave_failed




Big Clock

For all skin types using a bigclock.txt file in the root of the skin:
Quote
[colours]
background=
timertext=
timertextshadow=
visosc=
vissa=

For modern skins only:
Quote
plugin.bigclock.background
plugin.bigclock.timertext
plugin.bigclock.timertextshadow
plugin.bigclock.visosc
plugin.bigclock.vissa



Under a classic skin & to a lesser extent with modern skins (which tend to be more thoughtful of the generic colours provided), it's basing it on what might be provided from the skin vs default colours & attempting to generate something if needed that has enough visual difference between fore & background colours along with any plug-in specific alpha that's being used.

-dro

14
Ah that page, have quickly put up something now that'll point to the specific known issue pages (forgot I'd removed that some time back as what it was showing wasn't relevant).

The main crash issue that's going on is intermittent & can either not appear or might appear randomly or can happen after every play for some. By following the 2 suggestions, it should make things stable & then just leaves it down to some of the other possible problems happening.

-dro

15
https://getwacup.com/preview/preview_1_99_13_19100_known_issues.html is what's set for the Known Issues link on https://getwacup.com/preview/ for the current 19100 build (the older release pages also linked from the summary preview page have things for those builds).

Could do with knowing what link you're trying to access if it's not working so I can check & resolve it.

-dro

Pages: [1] 2 3 ... 104