Messages

1

Wishlist / Feature Requests / Re: Toaster plugin

« on: Today at 02:07:54 PM »

The old toaster plug-in not working from what I remember isn't necessarily a WACUP issue & is mostly due to the age of that plug-in as it wasn't working under Winamp properly for a long time due to how it was trying to use the OS gdiplus implementation from what I remember. I thought there was a patched version of it though I don't see the site for it is up & can't remember where that might've been posted.

I don't know if I'm going to make my own version of it or not at any time soon since there's many other things I still need to do for the core WACUP implementation.


The lyricsplugin should be working under WACUP as I know a lot of people still use it & I've even got some specific handling in place to detect it over my for now local lyrics only plug-in & disable my plug-in so the two don't conflict. It might just require moving the plug-in dll over into the WACUP\Plugins folder as other changes to avoid program installation conflicts means it likely won't auto-detect the install location.

Trying to offer a form of online lyrics look-up is on my todo list, it's just how / where to do that when I don't have the means to pay for a service that is the main problem doing it from when I last looked (trying to use the lyricsplugin online db is afaict not an option).

-dro

2

Preview Build Discussion / Re: Slight wording confusion

« on: Today at 01:58:01 PM »

The installer checks if there's already a running process running & offers to close if which is what the initial prompt was trying to convey. As I didn't think a force close when manually running the installer is the best of ideas - it does however do that if updating from within wacup due to there being other ui aspects to convey it's happening.

The re-showing of that same prompt is because how the installer has been scripted it can't tell at the moment if the attempt to close the found instance is either just being slow to complete or if it's hit a hang on close problem & so will keep re-trying until hopefully that instance does close.

Typically the message would just be seen the once but if it doesn't close then it's not idea & I've now made a note to try to better convey the first attempt didn't work & to either wait a bit more or to attempt to force kill the process at the expense of any potential data loss.

-dro

3

Preview Build Discussion / Re: Physically remove bug: Ignoring selected files

« on: Today at 01:45:45 PM »

No one's reported it so I wasn't aware its broken. Are you doing this in the main playlist or the library playlist views ?

-dro

4

Preview Build Discussion / Re: Can't Play aac or wma Files

« on: Today at 01:43:39 PM »

When saying aac files, are they mp4+aac or raw aac files or aac in some other container? As I know that mp4+aac when they're for example yt rips within the dash format do not currently work (if it's a pure aac frame in an mp4 container then that should be playing).

WMA is noted above though iirc it should on new installs try to use the re-used directshow plug-in unless that couldn't be obtained during install &/or wasn't selected.

-dro

5

General Discussion / Re: Winamp source code to be released

« on: Today at 01:05:28 PM »

I've merged the 2 threads that were made about this. For now this is really all I can say especially now I've had a chance to look at the press release...

Currently it doesn't seem to make any difference for WACUP as there's no developer specific details on what is supposedly going to be provided in ~4 months time nor the licensing terms of that or what the sign-up form stuff is all about (which isn't something I've ever seen related to such a process).

From the press release the Winamp will remain the owner of the software and will decide on the innovations made in the official version part seems to imply it not being super open nor permissive for other solutions. So I don't see how it really helps based on the lack of developer-centric details vs people already being able to make plug-ins &/or compatible clones.

The only things that'd be helpful to save me time would be the modern skin engine plug-in + related aspects & possibly the equaliser to get the correct sound, otherwise I've already got certain remaining aspects being worked on so the last few remaining pre-compiled plug-ins from the 5.666 installer no longer need to be re-used.

I'm just going to keep plodding along in finishing off what is my attempt at a winamp-like re-make & focus on that.

-dro

6

General Discussion / Re: Latest update - Errors and Crashes

« on: May 16, 2024, 07:28:31 PM »

Please look at the known issues section on the preview download page which have suggestions on what to try doing.

-dro

7

General Discussion / Re: Random crashes after recent update (1.99.13.19100)

« on: May 16, 2024, 07:28:11 PM »

Please look at the known issues section on the preview download page which have suggestions on what to try doing.

-dro

8

Preview Build Discussion / Re: Genre Tag Issue

« on: May 12, 2024, 04:46:45 PM »

That's good to know it's improved things. Its still a bit of a pain due to how the combobox/dropdown control works but main thing is it works well enough now.

-dro

9

Preview Build Discussion / Re: native scrobbling fails to scrobble certain songs.

« on: May 12, 2024, 04:45:35 PM »

It was a silly miscalculation on my part when rushing to get the prior build fixed for a different issue with the scrobbling vs pausing playback & I'd missed that I was effectively doing a x1000 on the time to wait when the file was more than 8mins long (due to the scrobbler spec have a 4min max wait time).

Main thing is that it's working ok now with the newer build. As for the update notification, its usually checked for once a week from the prior update check when wacup is next run & as you'd only recently updated to a build it'd have reset that wait to check time which is why it hadn't popped up.

-dro

10

Preview Build Discussion / Re: native scrobbling fails to scrobble certain songs.

« on: May 11, 2024, 09:32:59 AM »

What build are you using? As 1.99.13.19100 should've resolved what you're describing where files over 8 minutes weren't being scrobbled despite what the prefs indicated.

-dro

11

Wishlist / Feature Requests / Re: Bring back waveform seeker able to view waveforms upon clicking (not just play)

« on: May 09, 2024, 10:50:15 AM »

The option to do that has not been removed as it's one I've got enabled & use daily for many years now. If you right-click in the waveform seeker window & there'll be an option to have it show for the selected item. That shouldn't have become un-checked if it was enabled when installing the newer build unless this was a clean install & the prior settings were set to not be maintained.

-dro

12

Preview Build Discussion / Re: Genre Tag Issue

« on: May 08, 2024, 11:42:48 PM »

The problem is mostly due to how the OS combobox / dropdown control wants to do things & so far I can't find anything obvious that'd allow me to override the matching it's automatically trying to do (isn't something I'm actively doing on the basic info tab nor is in_mp3 doing afaict on the id3v2 tab - also probably affects the id3v1 tab).

The setting of the text in that control which has to be done otherwise you have the alternative issue of losing metadata then appears to automatically trigger the control to search within what's been added & try to match to that. This is also going to affect things like the batch edit dialog (though that doesn't seem to do it until interacting with it - something that mp3tag also seems to do) & any instance of the combobox / dropdown control when user input is enabled vs the string not being already known to it.

What I can do to try to workaround the issue on the basic info dialog is to insert the given genre string if it's not found & that keeps it happy. I still need to work out why it's showing it as selected text when that's not what I'm wanting it to do. I'll have to see about hooking the id3v2 tab & trying to do the same.

-dro

13

Preview Build Discussion / Re: 1.99.12.18980 M3U Stream sync connection errors

« on: May 07, 2024, 02:00:17 AM »

I'm only looking at ports 80 / 443 in comparison to whether https or http is specified & if they match as expected.

Everything else will be processed as provided by the caller to the networking service & assumes that whatever is providing the stream urls is doing it correctly otherwise I'd have broken the majority of shoutcast/icecast/equivalent based streaming urls (which for shoutcast defaulted to 8000 if memory serves me right from what I vaguely still remember from when I worked on that).

There'll also be a new prefs option (general -> internet) that allows for the new behaviour to be disabled.

-dro

14

Preview Build Discussion / Re: 1.99.12.18980 M3U Stream sync connection errors

« on: May 07, 2024, 01:36:11 AM »

That'd be why the old preview worked as the 'https://blah:80" was force changed to 'http://blah:80" which would work. Streams on other ports don't necessarily seem to be hitting these base http vs https assumptions (not sure if that's within in_mp3 or the networking service it uses which I've got some control over) & is something I can look into improving.

I've now had a look from a code view point & it appears to be down to in_mp3 doing the url processing before it calls things in the networking service which is then just trying to process the connection against what it's been instructed to use which is what it should be doing but also isn't necessarily ideal when the default http / https port url is trying to be used.

For the next build I've modified the networking service so it'll check what the connection type is vs the port trying to be used. If it's https & port 80 then it'll change it to port 443 & if it's http & port 443 then it'll change it to port 80 which seems reasonable & looks to be something browsers seem to be doing. Doing that allows the provided example playlist to work as-is.

-dro

15

Preview Build Discussion / Re: Bug when switching skins in Preview v1.99.11.18916

« on: May 07, 2024, 12:14:49 AM »

It is & those options won't help as the issue arises before any of that is run. The number & names of the skins found is also what made it more obvious with a default install & no other skins being the reliable way to replicate it against what was shown in the video of the issue.

-dro