Messages

1486

Wishlist / Feature Requests / Re: Checkbox for show WinAMP Format Converter Configuration

« on: March 20, 2019, 01:25:10 PM »

Would it also be helpful to have something on the window (probably as a status area) that once the dialog is closed tries to indicate the current mode being used. As even with the X->Y column, it's not as clear to know if it's a quality level 1 or a level 9 or whatever. Seem reasonable or just a waste of ui space ?

-dro

1487

Wishlist / Feature Requests / Re: Classic Skin Modules Resizing

« on: March 20, 2019, 01:22:53 PM »

That really depends on the skin & with more so modern skins how it's been designed. This is one of the downsides of allowing the UI to be changed as there's going to be lack of functionality for visual eye candy & vice-versa due to how its been designed. I get that from a user view point this is ultimately frustrating & can & has made people move to other players.

That's why for the Quinto skin the artwork window is a fixed size & not allowed to be resized (even though it's something you'd expect to be able to do from other skins) & it can probably be changed as part of a custom build without too much issue if the skin developer wanted to or if someone wanted to have a play around with it.
Specifically for what I think you want, you can try using the modern skin engines per-window scaling (it requires disabling the linked scaling option) & that might help get you something closer to what you want but that has the downside of any outer frames also getting scaled & looking blurry, etc.

-dro

1488

Skins / Re: WACUP-ONLY Skins? - Mods & Fixex

« on: March 20, 2019, 01:14:53 PM »

Altering / updating / maintaining skins have always been a troublesome issue going back to the start of skinning where you'd often be lucky if the skin correctly did just the classic main window. Thankfully classic skins are much easier to say they'll just work & are potentially easier for anyone to fix if needed as they're just image files (it's then just down to artistic ability & interest).

With the Quinto scenario which I assume is the skin implied but applies to other similar skins, it's a balancing act between following the rights of the skin author & trying to appease the needs of users & sometimes there's going to be a disconnect. Though after a point someone is going to get upset by things when keeping things working & actually useful for the active users needs is more important - it just sadly gets much messier when using the modern/winamp3 skins due to them having a scripted / dynamic aspect to them which is harder to deal with if those aren't provided.
For the request, if we know a skin works (aimed more at modern skins than classic skins as they should always work, just will be incomplete) then I don't see a problem either having a thread or a page (a wiki has also been considered for such things but needs to be setup) or even in ones offered from within WACUP directly where it's then detailed that they are compatible &/or what the known issues are. That's different to wanting a change of the colours & would need to be managed to just relate to usability & not desirability.

-dro

1489

Skins / Re: Quinto Black CT

« on: March 20, 2019, 12:50:20 PM »

We all have to learn at some point & compared to some of the points in that other thread, editing xml files isn't that complicated compared to trying to replace what plug-ins, etc are actually doing

-dro

1490

Skins / Re: Quinto Black CT

« on: March 19, 2019, 10:15:04 PM »

Wouldn't say you need to redesign the skin as a custom colour theme could work as an easy(ish) option or like you note making a custom edit for the default values/colour theme for personal usage. The 3rd option which needs some dev work / time would actually involve providing a skin engine override though its trickier to do it for modern skins vs classic skins & would then fall into a grey area of not actually altering the skin being used whilst altering the end display of the skin.

And there's a v2.8 of the skin now available -> https://winaero.com/blog/quinto-black-ct-v2-8-for-winamp-adds-cool-speakers/

-dro

1491

Wishlist / Feature Requests / Re: Checkbox for show WinAMP Format Converter Configuration

« on: March 18, 2019, 01:13:29 PM »

I thought I'd gotten away with not having to replicate that as no one has mentioned it over the past few years

I'll come up with something (probably not for the next build with my current rate of progress) as I'd intentionally tried to do things differently to what came before (hence the window & proper prefs page) but was waiting to see if there was a demand for the prompt mode or not. My initial thought is when the converter window is opened then you'll get the prompt since that's treated as the start of a batch event as iirc the old plug-in would do it on any action which was more confusing.

-dro

1492

Wishlist / Feature Requests / Re: Classic Skin Modules Resizing

« on: March 18, 2019, 12:38:57 PM »

Modern skins were designed with scaling built into the skin engine from the start. Classic skins weren't & only the main & equaliser windows got native double-size support.

WACUP remedies a bit of the classic skin issue in allowing (along with a small update to plug-ins) the generic skinned frames to support double-size mode (e.g. media library & skinned jtf windows). It still leaves the main issue of the main playlist editor window not following the mode (I don't know why it never got done) but that is being worked on as part of the delayed next beta build but will mean out of the box most of the windows should at least follow the double-size mode (would just be the video window that's not done).

Making classic skins scale at more levels (or even custom scaling) needs to be looked into once more of the Winamp core is replaced with the WACUP core. As just getting the main playlist editor to work correctly without breaking everything has been tricky over the last month & a bit - trying to then replace the handling for the main & equaliser windows to allow them to scale to other values would be more work that I won't say no to doing but it's going to be further down the road map.

-dro

1493

Preview Build Discussion / Re: How To Make WACUP Default?

« on: March 05, 2019, 07:36:47 PM »

You're not doing anything wrong but because it's a preview build & is designed to avoid integrating with the OS so builds can be tried out side-by-side then such things are completely expected to happen. Other than manually going in & editing the registry (which is not a solution), there's little else to do for the moment until WACUP has the mechanisms in place to correctly handle such things on its own.

-dro

1494

Resolved Issues / Re: Volume Control Issue

« on: March 05, 2019, 11:46:53 AM »

Preferences -> Global Hotkeys & un-check the multimedia keys option.

I can't win with the default state of that option as others expect it to work & others don't *shrugs*

-dro

1495

Resolved Issues / Re: Why playlists showd shorted by name?

« on: March 04, 2019, 09:59:46 PM »

Ok, so import is working correctly though I suspect you've done it so a managed copy is being used instead of the original playlist selected to be imported if the ordering in the file you're looking at is correct). You can if needed copy that file over to replace the managed copy or remove the current copy & re-import the playlist & then choose at that point either to use the original playlist or to allow it to make a new copy with the original sorting.

Clicking on the column headers was something that many had asked for over years vs what the native plug-in didn't allow to be done. So once you click on them, the playlist order is going to change & it's not possible to go back to an 'unsorted' state as that information just isn't known once the playlist changes have been saved. As a playlist is just a list of entries so unless there was additional metadata to indicate a positional context, that's why I can't make it go back to the non-sorted order.

The only solution would be to add an option that is able to prevent the header from allowing sorting which would then have to be enabled as sorting by default makes more sense imho.

-dro

1496

Wishlist / Feature Requests / Re: Copy/paste items to/from playlist

« on: March 04, 2019, 03:26:41 PM »

Removing actions is no more different than what I'd need to do via anything wacup provided.

I'm in the middle of replacing the playlist editor ui code with my own so I'm putting some thought into these things but for a first attemp I don't want to break existing features.

However non-windows the playlist editor works isn't something I want to do lightly &/or would require an option to change the expected behaviour & then it's what should be default.

Maybe changing to be more windows like is better but I'm a bit torn tbh.

-dro

1497

Resolved Issues / Re: Why playlists showd shorted by name?

« on: March 03, 2019, 05:50:58 PM »

Erm, there shouldn't be any sorting of the playlist view going on until the user clicks on the headers & then it'll be applied. So a straight import shouldn't have done anything & from my initial re-test of an import it's not showing any manipulation of the playlist. Which exact action did you use within the UI (as there's a few ways to import a playlist) & did you have it import as a copy or to use the original playlist file?

-dro

1498

Skins / Re: Big Bento Modern - final release v1.13

« on: March 03, 2019, 05:45:52 PM »

Kinda wish was a modernized winamp skin system that just use html/css much like electron based apps.. would be great and cross platform, would be a huge boost to a newer skinning system for winamp.. the current xml based one is just so messy and the lack of being able to inspect elements and just do css styling is so much more easier.

There's nothing to stop someone making just that but the issue is more in whether you are then going to have people actually using it. Cross-platform isn't all that helpful unless the base player is able to support it or it's taken on by other players as a more standard skinning solution (which imho is probably not going to happen with the current state of play).

The other approach would be to transpile modern skins into something newer but you're then still in a position of effectively writing 2 skin engines - the new one & one that does the transpiling between what we have now & what is needed for the new solution. Maybe that is a better solution for the long term (as it's a viable thing for Milkdrop / AVS presets) but it's still got to have interest from people to start coding it & the additional is does having an effective browser as the ui make sense (my initial thoughts are marred by the demise of songbird which was doing just that).
Will leave victhor to help with the other part of the post as he knows better about what needs to be considered.

-dro

1499

Skins / Re: Quinto Black CT

« on: March 03, 2019, 05:39:50 PM »

Primarily it's down to PeterK unless it's just not knowing about the setting(s) needing to be changed to achieve the desired result (the skin can do so much that it's often hard to find / know what might need to be changed). Though I've only just become aware of the following re: quinto black skin updates - "the future of the skin now depends on Radionomy and what they are going to do with Winamp" so not sure how likely a resolution will be but as you've posted in that other thread then that's the best option you've got.

-dro

1500

Wishlist / Feature Requests / Re: Function to activate full screen when starting video:

« on: February 27, 2019, 09:41:11 PM »

The irony of being asked to add a checkbox for the long hidden option that I'd then done for 5.8.

At the moment I don't plan on adding that option onto the WACUP video preferences page as there's issues with video_auto_fs=1 which can cause issues under modern skins & is why it was for the most part left as a hidden option when it was implemented & supplanted my old auto video full-screen plug-in (which itself had issues but depending on usage could work better than the native option at times).

When the time comes to replacing more of Winamp's core handling with what's done via WACUP's code then I'll come back to this as there needs to be a better way so that video & visualisations can work nicely with it (or something different equivalent to that ini option) without it breaking the user experience.

-dro