Latest WACUP beta release is build #9630 (December 22nd 2021) | Latest WACUP public preview is build #7236 (March 11th 2021)


NOTE: New beta testers are not currently being added as I need to re-work the beta test program

If you've not already requested to be a beta tester & would like to then please send a PM to 'dro' to be added to the beta test group.

Note: requests to be a beta tester are processed in batches when new beta builds are released so please by patient of this process.

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 - Aminifu

Pages: [1] 2 3 ... 14
1
Skins / Re: Defix Hi-End (skin) v2.0.5 (Last updated: November 24th 2021)
« on: December 25, 2021, 07:55:08 AM »
Hi Denis,

I've returned to version 163_Beta because I like the way album art is used in the 2 info boxes in the playlist in this version better than in version 2.0.5. I just noticed an issue with the info box that contains the song title, artist, album, etc. This info is not updated when the next song starts if the album art or artist associated with the song is the same as was associated with the previous song. I can get the info to update correctly if I close and re-open the playlist window. I'm wondering if this is due to the way this version of the skin is coded or if it is due to something in WACUP's coding. I'm currently using beta build #9630.



2
Skins / Re: New BentoX Skin for WinAmp/WACUP
« on: December 23, 2021, 03:47:38 AM »
Thank you Eris. I keep forgetting to state which version of WACUP (beta and/or preview) I'm referring to.

3
Skins / Re: New BentoX Skin for WinAmp/WACUP
« on: December 23, 2021, 02:15:11 AM »
Hi,

The second preference option in reply #3 above is for Winamp. In WACUP, this option is in Preferences/General/Appearance.

4
General Discussion / Merry Christmas and Happy New Year
« on: December 18, 2021, 12:02:05 AM »
Happy Holidays to dro and family and all WACUP users!

5
General Discussion / The Winamp INI File for Dummies
« on: December 16, 2021, 08:25:50 PM »
Hi dro,

I know you don't like that the "winamp.ini" file is used to store configuration settings that would best be saved elsewhere. I also know you and DJ Egg created the subject topic post for Winamp users and it was last updated in 2004.

I'm wondering if you have a WACUP related version on your ToDo List.

6
Skins / Re: New BentoX Skin for WinAmp/WACUP
« on: December 07, 2021, 11:07:02 PM »
Thank you. I like it.  :)

7
Wishlist / Feature Requests / Re: Managing Smart Views
« on: November 28, 2021, 08:54:52 PM »
... But another thing made me curious, what are these sub-views you're talking about? I've never heard of that. Maybe that's what I need for organizing my views and it's already there. How can I create a sub-view?

I agree with your comments about controlling the number of folder nodes.

Sorry, the use of "sub-views" is a bad and inaccurate word choice. I made my smart views some time ago with Winamp. When I first started using WACUP (in 2017), I copied my media library configuration files from Winamp to WACUP. I now see that the smart view editor in WACUP has a few changes.

Anyway what I see in my smart views is just the result of the filter strings I'm using (using advanced mode suggestions). I don't see a way to switch to advanced mode in the current WACUP editor. This may be due to the change of library plug-in from ml_local.dll to ml_ll.dll. The gen_ll.dll plug-in is also no longer used, which may also have something to do with this. Since my old smart views still work, the underlying code must still be present. I just don't see a way to create these views in the way I did before.


8
Skins / Re: Defix Hi-End (skin) v2.0.5 (Last updated: November 24th 2021)
« on: November 26, 2021, 10:04:39 PM »
Thank you Denis for the quick turn-around. An early Xmas present?  :)

I can see the speaker animation in all 3 modes with the base and entire frequency ranges. The effect is subtle in the standard mode and more pronounced in the other 2.

I was surprised by the feature added to replace the equalizer from the earlier versions. I'm not a skinner, so I will need to learn how to use it. I use a DSP plug-in instead of the equalizer, so I won't miss it.

9
Skins / Re: Defix Hi-End (skin) v2.0 (Last updated: November 22nd 2021)
« on: November 24, 2021, 08:25:04 AM »
Hi Denis,

Interesting changes in version 2.0. I can't get the animated speakers to work. Is there an option somewhere that needs to be enabled?

I think they work. They have little diffuser travel and only respond to low frequencies. But yes, I'll probably make a second mode, which will be more visual.

Yes !!! Thanks, Denis.  :D

I used the equalizer to maximize the frequencies output of my files and still don't see any movement in the main speaker drivers. So I hope you do find time to make a second mode.

I have seen multiple driver speakers in other skins where all the drivers are animated. I added the animated speakers (shown in reply #32 above) from Steven Mould's excellent "JVC Tape v0.6" skin to your skin. He graciously gives his consent that his skin may be used as a reference point. Only the large bass drivers are animated in these speakers, but the speakers look like the real thing and do provide a very cool effect, imo.

I remember using component stereo systems many, many years ago and like using skins that remind me of those old analog music systems.

10
Wishlist / Feature Requests / Re: Managing Smart Views
« on: November 24, 2021, 12:13:55 AM »
Whatever is done, I prefer that the main navigation tree not be filled with a load of nodes. I currently limit the number of main custom smart views I create just for that reason. If I reach my limit, I plan to delete the least used view before creating another.

I create overall main views that contain sub-views (in order to group related views). For example, I have a Genre view that contains sub-views for each genre the files in my collection use. I also have a Decades view that contains sub-views for each decade the files in my collection were released in.

I've also learned to use search strings to provide seldom needed views instead of creating smart views to have seldom used views always available. I assume this is what most users do.

11
I'm able to change the sort order of the playlist view by clicking on the column headings. Drag and drop would probably conflict with this current way of sorting.

12
Wishlist / Feature Requests / Re: Media Library Views Settings
« on: November 23, 2021, 10:48:10 PM »
Thank you dro, for your comments. As usual, things that appear rather simple on the surface aren't when looked at more closely. I didn't think about the other things saved in these files, beyond column setups. I seldom change things (including sort order) once I setup a view, but I can understand that others may, and probably do, use views differently.

Beyond that, now that I'm using a mix of 32KB and 64KB apps, I need to keep in mind the limits of 32KB apps.

The modern skins I'm using appear to be using the same font, but maybe not the same sizes, in their library views. So that could be what is causing column widths to change when I randomly pick a skin that is using a different font size. In any case, this is something controlled by the skins developers and is not easily changed by the user.

Whatever you come up with to improve default library views in general is appreciated. Even if nothing changes, you just taking time to think about these things is even more appreciated.

Now that I'm including these view configuration files with my other configuration files backups (which I should have been doing all along), it is easier to replace a changed file than readjusting a changed view. My only excuse is that it has taken me awhile to learn which configuration files control what is important to me and where they are. This is the price of using an app that gives the user so much control over it's user interface (and other features). It is this high degree of customization that kept me using Winamp (and now WACUP) over the years.

I've never been the kind of user who stays with the out-of-the-box experience, when given the ability to change things.  ;)

13
Skins / Re: Defix Hi-End (skin) v2.0 (Last updated: November 22nd 2021)
« on: November 22, 2021, 08:06:00 AM »
Hi Denis,

Interesting changes in version 2.0. I can't get the animated speakers to work. Is there an option somewhere that needs to be enabled?

14
Wishlist / Feature Requests / Re: Media Library Views Settings
« on: November 05, 2021, 04:58:04 AM »
..

These files would be the default for any new skin, as they are now. Then once the library window in a skin is used (with or without changing it's setup) a new set of these files (or what is in them) would be saved for each skin.
...

That part of reply #2 should have said;

These files would be the default library views for any skin the first time a skin's library window is used (as they are now for all skins every time a skin is used). Then once the library window in a skin is used (with or without changing it's views configurations) a new set of these files (or what is in them) would be saved for that skin. Once an individual library views configuration is saved for a skin, it would be used for that skin going forward. The active skin's library views configuration would be updated (if the user changes it) when the session ends or the skin is switched to another during the session.

In other words, I'm asking that what is now being done globally for the library views for all skins, be done individually for each skin.

15
Wishlist / Feature Requests / Re: Media Library Views Settings
« on: November 04, 2021, 06:43:14 AM »
I'm talking about the view configuration files that are currently saved in the users data 'WACUP/Plugins/ml/views' folder. I should mention that the current behavior pre-dates WACUP. Would WACUP object to making these files read-only after they are setup as desired? When making a desired change, a pop-up could be used to alert the file's read-only state. Similar to what happens when attempting to save metadata edits in a read-only audio file.

These files would be the default for any new skin, as they are now. Then once the library window in a skin is used (with or without changing it's setup) a new set of these files (or what is in them) would be saved for each skin.

My favorite modern skin has a control that lets the media library window be switched to a fullscreen mode. I then adjusted the column widths (when allowed) within the default and custom views I use to let all or most of the metadata strings for each column to be seen. The column widths within some of the views I setup for this skin are sometimes made narrower when switching to another skin that doesn't support a fullscreen mode for the library window (this is mostly a modern and cPro skins issue). It won't be so bad if the column widths stayed at what I set them to. Then I could simply use horizontal and vertical scroll bars to view everything within smaller library windows. When the column widths are narrowed, their metadata strings are truncated to much and I have to readjust the affected columns. I've not been able to determine what triggers these column width changes. It doesn't happen all the time and some views are not affected.

It would be nice to not have to switch to my favorite skin just to use the library without having to sometimes readjust things.

I get your point about the studio.xnf file. I was mainly thinking of keeping the number of files that would otherwise be needed small. It does frustrate me when I have to nuke the studio.xnf file just to fix corrupt configurations for 1 skin or update the configurations when a new version for a skin is released. New skin versions will often add stuff, but never remove stuff that is no longer needed. I do realize that new skin versions are not able to clean up what is no longer needed, so the occasional nuke is not always a bad thing, but I never like doing it.


Pages: [1] 2 3 ... 14