Compatibility with additional/custom tags on Smart Views

  • 9 Replies
  • 443 Views
*

araxhiel

  • Beta Tester
  • Newbie
  • *
  • 1
    • View Profile
Compatibility with additional/custom tags on Smart Views
« on: April 24, 2018, 04:49:45 AM »
As the title says, it could be a great feature to have more flexibility while creating/configuring a Smart View, based on other tags besides the ones that the application already uses.

To give more context, I'll provide my particular scenario:

Currently, in order to keep my collection organized I rely a lot on the use of Smart Views, where I can filter the albums/artists by music genre, release type (LP, EP, Single, Split), "album type" (Studio, Live Album, Demo, Compilation, etc.), Country/Region (Germany, Norway, U.S.A., etc.), among other "categories".

So far, I've managed to do this using some of the default tags, such as genre, length, filename, and comment, being this one where I set most of the values that I want to use to filter the songs/albums on the Smart Views (ie. Comment = "Germany, Single" or "Spain, Live Album") using the "contains" operator in order to achieve my goal.

But, at least with some of the filters that I use there are already available tags for that information, like "Media type" that can be used instead "comment". Also, there are private frames that can be designated for other type of data that hasn't a proper tag field (like "country", or the ones that iTunes uses, or MP3Tag uses when downloading information from discogs).

So, it could be possible/feasible to add some compatibility with additional tags that aren't available on the default Smart View configuration? (both existing, and user defined)

Thanks in advance.

*

dro

  • Admin / WACUP Developer
  • Administrator
  • Hero Member
  • *****
  • 1228
    • View Profile
    • WACUP (Winamp Community Update Pack)
Re: Compatibility with additional/custom tags on Smart Views
« Reply #1 on: April 25, 2018, 02:06:02 PM »
Some of the things you're mentioning could probably be supported without too much issue when the local library plug-in gets replaced though having it fully dynamic in the data it can get isn't the simplest of tasks (most databases generally need to know what will be stored prior to being used) especially as it also depends upon the input plug-ins to provide that metadata (which they also aren't flexible in their design to provide other fields that aren't already known about).

Will definitely give this some thought to this as I've seen it pop up every now and then over the years and a more flexible library makes sense (despite the tecnhical hurdles).

-dro

*

dro

  • Admin / WACUP Developer
  • Administrator
  • Hero Member
  • *****
  • 1228
    • View Profile
    • WACUP (Winamp Community Update Pack)
Re: Compatibility with additional/custom tags on Smart Views
« Reply #2 on: April 25, 2018, 09:04:56 PM »
Thinking about this a bit more, can you (and anyone else) post the fields you're actually wanting in-addition to what is already supported please.

-dro

*

Juanus

  • Beta Tester
  • Sr. Member
  • ****
  • 268
    • View Profile
Re: Compatibility with additional/custom tags on Smart Views
« Reply #3 on: April 25, 2018, 10:51:50 PM »
Since you are adding Musicbrainz support, let's start with all of the musicbrainz tags
see attached image.

*

dro

  • Admin / WACUP Developer
  • Administrator
  • Hero Member
  • *****
  • 1228
    • View Profile
    • WACUP (Winamp Community Update Pack)
Re: Compatibility with additional/custom tags on Smart Views
« Reply #4 on: April 25, 2018, 11:07:54 PM »
I should have expected an "all of the tagz" reply :) With what's shown, a large number are already present albeit under a different name within the library though the musicbrainz_* values and a few others seem viable to add.

My main reason for asking for anything specific is that tracking all of that data will have a realistic impact on memory usage (especially across a large media library) if it's all to be collected & I know memory is there to be used (since it's not that comparatively cheap to buy currently) but just storing & having to load that data when it's often not going to be used is a bit of a waste.

-dro

*

Juanus

  • Beta Tester
  • Sr. Member
  • ****
  • 268
    • View Profile
Re: Compatibility with additional/custom tags on Smart Views
« Reply #5 on: April 25, 2018, 11:38:47 PM »
at this time, and for this specific request, I would think that the musicbrainz_* values are the least important since you cannot categorize by them and not meant for manual searching. (I wish that there was a way to make those tags read only since they are so specific for a very specific purpose.)
All of the rest of the tags are much more important. I think the OP is looking more for
Language
Media
Release Country
Release Status
Release Type

But I would be happy with ALL THE TAGZ!

[EDIT] Obviously the musicbrainz_* values can't be read-only. Then the program couldn't write to them. I meant to say non user editable.
« Last Edit: April 26, 2018, 12:27:42 AM by Juanus »

*

Benco

  • Beta Tester
  • Newbie
  • *
  • 13
    • View Profile
Re: Compatibility with additional/custom tags on Smart Views
« Reply #6 on: April 26, 2018, 11:55:29 AM »
Hi,

I would be very interested in this feature, it's something that I've been thinking of for a while. Here's another use case: add a "featuring" field. For example, in the Queen's album Hot Space, most tracks have only Queen as Interpret, except for Under Pressure, which features David Bowie. If the Interpret field is Queen feat. David Bowie, it messes with the album grouping, which means the Album Interpret has to be used. Using a Featuring field for storing David Bowie would make more sense.
And does this feature implies that title formatting would also need to be redone? Would make sense.

About the feasibility, could this be a way to go: Let the user specify which fields he needs, which defines the library metadata, and if there's a change in this metadata, have the library rebuild itself. I guess this rebuild would be quite difficult to implement, and very CPU consuming, but maybe it's feasible...

Benco

*

Juanus

  • Beta Tester
  • Sr. Member
  • ****
  • 268
    • View Profile
Re: Compatibility with additional/custom tags on Smart Views
« Reply #7 on: April 26, 2018, 05:47:13 PM »
Benco,

This is already implemented in Winamp/WACUP.
The field you are looking for is Album Artist. Instead of sorting by Artist, you should sort by Album Artist and that will give you the results you are looking for.

In your case
Album Artist = Queen
Artist = Queen feat. David Bowie

This is the standard way to tag and sort. Having a "featured" tag would not comply with the accepted standard.

*

Benco

  • Beta Tester
  • Newbie
  • *
  • 13
    • View Profile
Re: Compatibility with additional/custom tags on Smart Views
« Reply #8 on: April 26, 2018, 06:21:50 PM »
Hi

as I have told in my previous post, I'm aware of this tag (which I miscalled Album Interpet). Using a Featured Artist, though, seems to me a better way to go. If I'm looking for all the songs from Queen, I won't have to use a request like "?artist=Queen or album_artis=Queen". And using "?artist has queen" doesn't work because it would also find Queen Latifah (big fan of Chicago here).

*

dro

  • Admin / WACUP Developer
  • Administrator
  • Hero Member
  • *****
  • 1228
    • View Profile
    • WACUP (Winamp Community Update Pack)
Re: Compatibility with additional/custom tags on Smart Views
« Reply #9 on: April 26, 2018, 07:18:05 PM »
With the 'featuring' suggestion, the only issue I can see (though I might have missed something) is that there's not a common tag field present for storing that information within the file without just having a local library specific field which cannot be easily pushed back to a file.

You might also be able to use a different matching pattern in the query but I appreciate that that won't necessarily work correctly for all cases either. Thanks for the convo & ideas made so far :)

-dro