2016-01-04, 13:08
I have had a quick look at filtering artists and albums by the path location of their songs, and it is fairly straight forward addition. But do note that custom nodes/playlist filtering works differently from the default nodes.
For example in the default nodes selecting genre of "funk" you get a list of artists that have songs with a "funk" as a genre. Click on one of those artists and you get a list of only those albums for that artist that have songs with a "funk" as a genre. Click on an album and you get a list of only those songs from that album with a "funk" as a genre. At album and artist level you also get a *all item that skips a level.
In comparison, although a filter type custom node of content "artists" with rule "genre is funk" will show that same list of artists as above, when you click on an artist you will then see all the albums for that artist regardless of genre. Likewise clicking on one of those albums will display all the songs.
The filtering on default nodes passes down the levels, the filtering on custom nodes and playlists does not. So if you make an artist playlist based on rules applied to the songs, although only some of the songs may meet the criteria all of them will be played.
So say you had albums and songs for an artist on two separate drives, and you wanted to see only the music from each of them separately, then an artist level path filter custom node would not help. Having said that I can't see why you would want to split an artist's work in that way.
A much bigger change would be needed to get custom nodes/playlists to pass the filtering down so that only songs that meet the criteria applied to artists or albums are played. Not sure there is sufficient interest in that to make it worthwhile. What do you think?
For example in the default nodes selecting genre of "funk" you get a list of artists that have songs with a "funk" as a genre. Click on one of those artists and you get a list of only those albums for that artist that have songs with a "funk" as a genre. Click on an album and you get a list of only those songs from that album with a "funk" as a genre. At album and artist level you also get a *all item that skips a level.
In comparison, although a filter type custom node of content "artists" with rule "genre is funk" will show that same list of artists as above, when you click on an artist you will then see all the albums for that artist regardless of genre. Likewise clicking on one of those albums will display all the songs.
The filtering on default nodes passes down the levels, the filtering on custom nodes and playlists does not. So if you make an artist playlist based on rules applied to the songs, although only some of the songs may meet the criteria all of them will be played.
So say you had albums and songs for an artist on two separate drives, and you wanted to see only the music from each of them separately, then an artist level path filter custom node would not help. Having said that I can't see why you would want to split an artist's work in that way.
A much bigger change would be needed to get custom nodes/playlists to pass the filtering down so that only songs that meet the criteria applied to artists or albums are played. Not sure there is sufficient interest in that to make it worthwhile. What do you think?
