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 ... 30
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.


Wishlist / Feature Requests / Re: Classic Skin Modules Resizing
« on: Yesterday at 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.


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.


Preview Build Discussion / 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*


Preview Build Discussion / 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.


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.


Preview Build Discussion / 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?


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.


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.


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.


I'll just quote myself from my past life from
you don't have to do resource hacking (and haven't needed to do it for 2 years!). you just need to put a 1x1 black bmp file named videologo.bmp into the %appdata%\Winamp folder and that will hide it

The only thing I'd amend to that is "%appdata%\Winamp" should be changed to the Winamp / WACUP settings folder as applicable otherwise you can change the logo as wanted & with WACUP you should also be able to use a videologo.png instead of a bmp file if that's preferred.


Wishlist / Feature Requests / Re: Old recommended video overlay options
« on: February 27, 2019, 09:28:15 PM »
My understanding is that the option you've highlighted from the older Winamp release was removed due to the OS removing the support since it related to DirectDraw I believe & since Vista, there's been a move to deprecate / remove features on the OS side related to it. As such the video support that 5.666 provides (which is unchanged under WACUP) uses some of the newer output solutions which negates the point of trying to add back in such options when they just don't have any relevance.

Also I need to just state this now, although Winamp & WACUP by being based on top of Winamp can do video playback, it's not an area that really interests me & I think moving WACUP towards more of an audio player is better suited on how the majority that prefer to use Winamp or something like it want as video support was never great in Winamp nor never very much liked. I know that there are some who are happy with it & I'm not going out of my way to intentionally remove it but audio & associated file management are better areas & points of interest to me when working on things vs video playback which is just a myriad of pain most of the time.


Wishlist / Feature Requests / Re: An NDI plugin for WACUP will be possible
« on: February 27, 2019, 09:22:12 PM »
I've never come across NDI but it seems like if the SDK is permissive that anyone could potentially make a plug-in to work with it to capture the video window (or vis window for that matter) & send it to another solution. It's not something that is jumping out at me as a native feature I'd like to support due to not being able to easily acquire their SDK without providing personal information but there's nothing to stop someone else from doing it if they'd so desire.


The actions of that sub-menu only work when processing the playback override queue & not just playing things normally within the main playlist.

Unless the bottom option is enabled, they are one time action when that temporary queue completes playback (as long as also other aspects of Winamp aren't conflicting). Without knowing what the old plug-in that you're also trying to use is (which is more likely the reason for issues with the menu options not working as they also rely upon being able to self-close Winamp without it crashing), there's not much I can otherwise suggest as the feature worked as expected when I last tested it.


Wishlist / Feature Requests / Re: Window Sizing
« on: February 27, 2019, 10:33:58 AM »
Smooth resizing is the option for classic skins but you then lose the option to easily dock the windows during sizing when it's enabled (something I want so it'll eventually get implemented).

Not sure about allowing any side resizing as I know most modern skins allow for it but the classic skin engine isn't really built to do that as it assumes bottom-right for all sizing interactions.

It could be changed but it might need to be something done as an opt-in than on by default (as my initial thought to the idea).


Pages: [1] 2 3 ... 30