Messages

1486

Wishlist / Feature Requests / Re: Save ML Window Configurations on a per Skin basis

« on: November 16, 2017, 02:28:30 PM »

The filename is a bit of a misnomer as it's really 'plug-in profile' but with other files already using 'plugin' it ended up as 'profile'. The file is just for controlling which plug-ins can be loaded. I think what you're proposing can already be done but it involves specifying a completely different settings folder which isn't ideal as you can't easily keep things in sync. So the best that can be done comes down to things like proportional sizing of the views vs the container window but that comes with issues as well.

-dro

1487

Wishlist / Feature Requests / Re: EBU R128 loudness normalisation

« on: November 15, 2017, 09:08:37 PM »

This is all new to me and perhaps this has already been discussed in length somewhere, but how do you feel about this EBU R128 method and is it perhaps possible to implement it into WACUP's 'Calculate Replay Gain'?

I've briefly mentioned it in some of the beta discussion threads but not as a topic on it's own. Using the newer format is something that is on my list of things I want to do as the existing plug-in that handles it needs to be replaced to allow for it (as well as to resolve some issues with normal RG calculations).

As it seems like the newer format is preferred by other players, I've no problem into eventually getting around to supporting it

-dro

1488

General Discussion / Re: Why I'm still not become a tester of WACUP?

« on: November 14, 2017, 04:07:56 PM »

All of the valid beta tester requests have been actioned with either access granted or rejected with details to re-submit the correct way (as I'd found a pool of requests from a forum mode I wasn't aware off 🙄). Anyone requesting to become a beta tester and using the 'add to group' option (I've still to find out where that appears as a user) will get a rejection and a message to send a PM to me instead - doing it via a PM (even if it can be slow at times) is the correct way to be considered.

-dro

1489

Wishlist / Feature Requests / Re: Art Navigator

« on: November 13, 2017, 09:30:50 PM »

Relying on the library isn't always a safe assumption either as a lot of people don't like it & won't have it installed (something else I'm trying to do with WACUP is remove the need for the library to be able to still achieve certain functionality like skinning & the send-to menu).

The main down-side with the multi-content view is that it's a very skin specific implementation (i.e. Bento was coded specifically to provide that mode). I get that a lot of people don't bother changing the skin (based on how many I came across over the years despite an option during setup that didn't realise the skin could be changed).

When I'm in a position, then I will hopefully be able to come up with a solution that meets your needs & the other thoughts that it's spawned in my head

-dro

1490

Wishlist / Feature Requests / Re: Art Navigator

« on: November 13, 2017, 08:07:08 PM »

Ok, we might have gotten our wires a bit crossed on what's actually being wanted (though it still requires underlying changes made to allow for plug-ins / skins to have the potential to access any of the artwork types that can exist in a tag other than just the 'cover' type). I was referring to viewing & editing but more within the confines of an editing scenario rather than (as I think might now be the case) in showing all of the artwork types at the same time in a view.

Whatever might be done, I hold to it needing to work in any skin type & not just modern skins (which was how it was done officially for a long time to the detriment of classic skin users imho when changes could be made to achieve feature parity). Will have a think about this as it'd probably be more suited in some form for a post v1.0 release.

-dro

1491

Wishlist / Feature Requests / Re: Art Navigator

« on: November 12, 2017, 10:45:11 PM »

If you've sent a PM then it'll start being actioned tomorrow 13th (monday) now that a new build is available I'm working on the backlog of requests.

At the moment 'cover' is all that's done as that's just what the Winamp native behaviour is setup to work with. To support other artwork types (front, back, etc) needs the Winamp UI for handling artwork to be changed & for the relevant plug-ins to be updated (or a shim put in front of them to support it until a replacement plug-in is made e.g. with in_mp3). So doing all of that (which would be more like mp3tag from my experience) is probably going to go a long way towards what you're wanting.

Having a view mode to see what's there (other than via the tagging interface), that's potentially a bit trickier due to only a 'cover' assumption (e.g. modern skins might be hard to get working). Though for classic skins or via a custom plug-in / UI element then I don't see why something couldn't be done (e.g. left/right in the album art plug-ins window could move through the available artwork types). There'd probably also need to be some preference option to determine the read order of the artwork so if needed something else could be the default instead of 'cover' if found (or just how to proceed if a type is missing).

-dro

1492

Wishlist / Feature Requests / Re: Add an Option to exclude folders from Watch Folders

« on: November 10, 2017, 11:55:28 PM »

I thought that it was already possible to do that but from the config options provided it seems not (other than manually setting the folders one at a time & disabling the scanning within the sub-folders checkbox). So afaik, the only real way to see this happen would involve a replacement library plug-in which has the support to do what's wanted (tbh the watch folders mode needs re-working so it's not reliant upon scanning things but instead responding to OS provided file change notifications).

-dro

1493

General Discussion / Re: Why I'm still not become a tester of WACUP?

« on: November 10, 2017, 10:36:42 PM »

As I've finally put out a new beta build (https://getwacup.com/blog/index.php/2017/11/10/wacup-beta-build-1988/), I will be working through the pending beta tester requests I've received over the last few months and should have the backlog cleared by the end of the 13th (Monday).

My apologies for those who've included any additional messages in their beta tester requests & not had a response as the requests get filtered to a pending folder when received. Alas this release cycle hasn't been the smoothest & took longer than I'd expected it to be but I hope this newer build moves things on in a good way from where it was with the prior build.

-dro

1494

Skins / Re: Big Bento Modern Beta

« on: November 08, 2017, 02:39:13 PM »

Good idea, now let's hope I can figure out how to display en ellipse dinamically..

slip the string & then append the ellipse. nice & simple

-dro

1495

Skins / Re: Big Bento Modern Beta

« on: November 08, 2017, 01:26:54 AM »

Maybe for the longer title strings, rather than a hard clip, use an ellipse (...) as that'll make it less harsh if clipping does have to happen (I'd hope that most people get what a ... implies).

-dro

1496

Skins / Re: Big Bento Modern Beta

« on: November 03, 2017, 01:14:05 PM »

*Maybe it works if placing the file inside a Language Pack / Folder on a WACUP install? I haven't test it, let me know if you do.

Language pack support is somewhat intentionally broken in WACUP and this will be re-enabled at a later time. This was done to avoid issues with existing language packs & the replacement plug-ins which try to leverage some of the existing resources & can crash in some cases.

-dro

1497

General Discussion / Re: New Winamp Logo?

« on: October 23, 2017, 04:26:17 PM »

Whatever it means, I'm still working on WACUP as I highly doubt they'll ever provide updated versions worthy of the Winamp name. Will re-post what I'd posted about seeing the new logo from elsewhere...


Dunno why they'd bother doing that other than to fool people (the comments from people so far is saddening) & tick some corporate branding boxes. Whatever way, it's an awful looking logo (some odd bastardisation of the spinner logo whilst making it like a T and an S).

The 'cast' is the RN platform & 'sell' is targetspot (those have both also been updated) but 'cast' would have been better suited for shoutcast but that seems to just being abused now (they've damaged the brand with their piss-poor streaming service).

However I'm starting to wonder based on the wording if they'll instead just re-brand their RN app for listening to their streams with the winamp name. That'd be a quick way to keep the brand name used without any real investment (as it's been admitted there is no winamp dev team).

-dro

1498

Skins / Re: Big Bento Modern Beta

« on: October 23, 2017, 04:10:17 PM »

Is the Browser tab still useful? All it does is tell you that "You've asked for client.winamp.com."

Was it ever useful is probably the better question imho. I'd personally rather not see it in there at all (in any of the modern skins) & things just load in the default browser (using a crippled IE/webbrowser experience isn't enjoyable) if there's a need. As the modern skins can more easily show the sort of extra info that doing things via the browser is trying to do without the massive overhead & jarring interfacing.

-dro

1499

Skins / Re: Windows 2k like Winamp Skin

« on: October 23, 2017, 03:29:00 PM »

I think we might have gotten the wires crossed on this as the thinking behind that (which is not certain to happen) was more to make it simpler for users rather than skinners and those that want a scalable classic skin without needing someone else to do things for them or don't have the technical skills.

As it could be done as a simple single button / menu action (so not much clutter) but as I've got things going on which make more of the classic skin scalable (at least more parts work with double-size) maybe leveraging the modern skin engine to deal with classic skins isn't the right. So I'm not sure about the whole "skinners tools" plug-in aspect as it wasn't what I'd been thinking about (was purely just a way to resolve non-scaling classic skins).

-dro

1500

Skins / Re: Big Bento Modern Beta

« on: October 23, 2017, 12:44:40 PM »

Plus it's a relief it's not a WACUP specific issue unlike we had with the Invicta skin.

Which version of Invicta? Version 1.0, Version 1.1 or Version 1.31?

That issue wasn't down to a specific skin version but how the replacement png image loading worked in WACUP vs native (it related to gamma correction handling which is more of an issue for older png files).

-dro