getmusicbee.com

General => MusicBee Wishlist => Topic started by: alec.tron on July 25, 2020, 08:11:53 AM

Title: Tag Hierarchy Explorer Panel - Wishlist/Ideas
Post by: alec.tron on July 25, 2020, 08:11:53 AM
Hello hai,
now that we have a new Tag Hierarchy Explorer Panel in MB, might be good to detach it from the large thread where this started:
https://getmusicbee.com/forum/index.php?topic=8987.msg178058

And collect bits that relate to this new panel in its' own thread.

The few bits I would love to see at some point in the future still:
- configuration options
    - option to only show branches and/or groups that have files inside them, or associated children (with content/files)
    - option to show how many files sit in each branch/group [i.e. maybe just a number in  brackets like - in hierachy panel mock up view:
Code
Genres (123456)
    Blues (987)
        Delta Blues (654)
     maybe even trigger'able on the branch level so I on can decide on a per branch facet if/where this is important info...]


Also, @psychoadept and others active in the MB Wiki - would there be a space that would lend itself to storing and maintaining various mappings/txt files for others to use ?
I pasted a fair few in the above thread already, but forum is a tad limited for that, and would be nice if there was an agreed upon resource to store, collaborate on, and version these Tag Hierarchy Explorer Panel txt files.

Churs.
c.
Title: Re: Tag Hierarchy Explorer Panel - Wishlist/Ideas
Post by: alec.tron on July 25, 2020, 09:50:33 AM
Here's a set of 4 basic files (slight overkill to use github, but was readily available, and give me versioning easily if need be, plus collaboration options, if others have github accounts...):

Overview (if you are familiar with github)
https://github.com/alectron/MusicBee_TagHierarchies


Or, links to the currently existing 4 Variants, as raw txt contents (that you could paste into the panel directly), below:

--------------------------------------------------

Genres:
Discogs_Genres_Styles.txt
https://raw.githubusercontent.com/alectron/MusicBee_TagHierarchies/master/Genres/Discogs_Genres_Styles.txt

MusicBee_2Layer.txt
https://raw.githubusercontent.com/alectron/MusicBee_TagHierarchies/master/Genres/MusicBee_2Layer.txt

MusicBee_3Layer.txt
https://raw.githubusercontent.com/alectron/MusicBee_TagHierarchies/master/Genres/MusicBee_3Layer.txt

--------------------------------------------------

Instruments:
Instruments_Monash.txt
https://raw.githubusercontent.com/alectron/MusicBee_TagHierarchies/master/Instruments/Instruments_Monash.txt

--------------------------------------------------

c.


ps. also a tip - if you want to dive into this and merge/edit/re-construct these for your library/tags - as the MB Panel is all based on proper White-Space & Line-Indent formatting, I'd recommend to get a good text editor that is suited for this (i.e. my recommendations would be: NotePad++, Sublime, etc)
Title: Re: Tag Hierarchy Explorer Panel - Wishlist/Ideas
Post by: The Incredible Boom Boom on July 27, 2020, 05:20:47 PM
Tagging genres would be a cinch if the hierarchy could tag recursively.

Code
Pop::Genre Category
    Pop::Genre
        Japanese Pop::Genre
            歌謡曲::SubGenre
            City Pop::SubGenre

Asia
    East Asia
        Japanese::Genre Category
            Japanese Pop::Genre
                歌謡曲::SubGenre
                City Pop::SubGenre

If you tagged <SubGenre> as "City Pop," MB would fill in <Genre> with Pop; Japanese Pop.
Title: Re: Tag Hierarchy Explorer Panel - Wishlist/Ideas
Post by: alec.tron on July 27, 2020, 08:35:30 PM
Tagging genres would be a cinch if the hierarchy could tag recursively.

If you tagged <SubGenre> as "City Pop," MB would fill in <Genre> with Pop; Japanese Pop.
Yes and no (imo).
This could probably be fairly easily done by script, if the Tag Hierarchy context were retrievable via api. But give it a bit of time, and it might come - this feature after all is only a few days old.

Also - some food for thought - what would you need redundant/recursive tag writing for ?
The one thing I had use for it would be to later consume the recursive context injected back into the file in auto playlists...
But, what IF Auto Playlists themselves could have rules written against the TagHierarchy context/relations ? Then you'd only need the the 'City Pop' tag, to get all the other tags & their handling for free...

So IF Auto Playlists were the need, then with the above, there'd no need to re-inject the tagHierarchy context back into tag metadata fields anymore...
Just a thought, and, might be you had something else in mind ?

Churs.
c.
Title: Re: Tag Hierarchy Explorer Panel - Wishlist/Ideas
Post by: The Incredible Boom Boom on December 14, 2020, 02:25:45 AM
REQUEST Could we have the ability to multi-select nodes from the THE, ala the Column Browser?

Also - some food for thought - what would you need redundant/recursive tag writing for ?
The one thing I had use for it would be to later consume the recursive context injected back into the file in auto playlists...
But, what IF Auto Playlists themselves could have rules written against the TagHierarchy context/relations ? Then you'd only need the the 'City Pop' tag, to get all the other tags & their handling for free...

So IF Auto Playlists were the need, then with the above, there'd no need to re-inject the tagHierarchy context back into tag metadata fields anymore...
Just a thought, and, might be you had something else in mind ?

Just realized I forgot to respond to this. Oops. It was mostly for laziest purposes and having MB populate <Genre> with parent genres. However, tagging files and using the THE in such a manner is sort of primitive, so it's moot now.
Title: Re: Tag Hierarchy Explorer Panel - Wishlist/Ideas
Post by: The Incredible Boom Boom on December 15, 2020, 04:16:34 AM
I dunno whether I'm supposed to put THE requests here or the other thread.  :-X

I have a few.

REQUEST Could we have the ability to multi-select nodes from the THE, ala the Column Browser?

List all available tags from a given node
Right now, I have...
Code
Contemporary Hit::Style
...
...
...
International
    Africa
    Asia
        日本::Keywords
            Contemporary Hit::Style
            ...
    Europe
        Sweden::Keywords
            Contemporary Hit::Style
In the Tag Relationship Editor, there's a list of tags with no relational connection to the music library, so there must also be a list of tags with a relational connection. It would be dope to have access to that list, something like...
Code
Contemporary Hit::Style
...
...
...
International
    Africa
    Asia
        日本::Keywords
            ALL::Style
    Europe
        Sweden::Keywords
            ALL::Style
...will fill the child node with tags that have been assigned elsewhere, avoiding clutter and redundancy in the .txt file.

Match Any Text in Tag...
...the same way <Tag> contains "example text" works in the Custom Search window.

For example, I have <Keywords>=Gender:male/female in multiple albums and normally* I can't match "male/female" in the THE, because "Gender:" gets in the way. I say "normally," because when I remove "Gender:" from one album, the rest of the albums actually become available in the THE too.

<Tag Hierarchy> Tag, ala <Genre Category>
Since the hierarchy is already being stored somewhere, is there an easy way you can make it accessible as a tag? 🤔