Latest restricted WACUP beta release is build #14638 (February 23rd 2023) (x86 & x64 changelogs) | Latest WACUP public preview is build #7236 (March 11th 2021) (x86 only)

NOTE: Beta testers are added in a limited & subjective manner as I can only support so many people as part of the beta test program to keep it useful for my needs.

Unless I think you're going to be helpful, not all requests will be accepted but might still be later on. Remember that beta testing is to help me & the limitations currently works for my needs for this project.

Author Topic: Adding To Managing Smart Views  (Read 997 times)


  • Beta Tester
  • Newbie
  • *
  • Posts: 3
    • View Profile
Adding To Managing Smart Views
« on: July 27, 2022, 01:48:15 PM »
In the Managing Smart Views.
The world of Audio and Video has dynamically changed over the past 35 years, and the number of file types has increased.
From .sid (commodore) .wav (MS) .bit (early MP3 stage) and away we ago.

Since noted: This is still a work in progress

When creating a new view, can more "FILTERED" sorting fields be added.
Such as "Comment" and "File Type" (.mid, .mp3, .mp4, etc) for those who have large libraries, to sort in one spot.
This can be done "Sudo" using the manual filter via filename, but not very well.

The other is:
Please do not show (.mid, or z, y, z )file types in this view



  • Admin / WACUP Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 3992
    • View Profile
    • WACUP (Winamp Community Update Project)
Re: Adding To Managing Smart Views
« Reply #1 on: July 27, 2022, 06:59:56 PM »
A filter based on extension seems reasonable, just not sure what the performance impact would be as that value is generated as needed from the filename. Adding comment as a filter I'd have to be convinced about as that can be filled with a lot of data for some setups which would just tank performance nor would it make grouping of things likely all that useful.

Something else that had come to mind but needs some thought on how to do it without messing with some expected compatibility is to expand the 'type' so it could be something like audio,video,video game,whatever else makes sense based on some additional input & consensus (or not if it doesn't make sense to do).

Though there's also just using the appropriate view query syntax to limit what is found overall but that could probably be made easier to configure somehow. As I know there's been cases of wanting to have different sub-library scenarios (a bit like the old dynamic library plug-in) but it's how to convey & configure that which I'm open to suggestions on what could be done to achieve it.