Posts: 873
Joined: Jul 2008
Reputation:
8
I use it sometimes and sort the view by playcount. It gives me an overview of my most played songs.
However this could be done with a smart playlist. So removing it gets my vote.
Posts: 103
Joined: Feb 2012
Reputation:
1
+1 for removing song node.
Posts: 31,445
Joined: Jan 2011
I have a small-ish music library (just shy of 7,000), but I almost always list it by song and not by artist or album. I don't normally collect whole albums since there's only one or two songs that I actually want to listen to on a regular basis. I'd rather scroll through everything I have based on track name.
Then again, I'm an old man now (33 is old?) and I don't understand the young people's music anymore. Maybe I'm just out of it?
Posts: 3,077
Joined: Jun 2009
I do use it often to find a song that I barely know the name, but in Estuary with good integration of the globalsearch addon I suppose I'll use it a lot less.
@
ned you are quite young
But the main question is why removing something that could be useful to some ? There's large library of movies, it's hard to browse a long movie list, yet I sometimes do browse it do find something to watch.
Or maybe remove the node and add a default playlist.
Posts: 4,545
Joined: Jun 2015
Reputation:
269
2016-03-16, 14:13
(This post was last modified: 2016-03-16, 14:14 by DaveBlake.)
Yes, the songs node is an unfiltered list of all the songs in the library. If the library is large there can be a painfully long delay before that list is displayed, I assume that is the main reason why some people want to remove this facility.
But despite the slowness, I am strongly against the removeal of this node. At very least if you do decide to remove it as a default node, then I hope that the core facility remains so that users can create a folder type custom node (using musicdb//songs) that does the same thing.
It seems crazy to me that we even consider removing the ability to list all the songs. It may not be something used often or by everyone, but that is not reason to remove it.
There is the presumption that all users categorise their music by genre, or have albums. Some users, I believe, don't tag or scrape genre, or organise their music by albums. If your library is a collection of songs then seeing a list of all of them may be just what you want. If your library is small, and not everyone owns lots of music, a list of songs is also usable way to browse. What chance that these users are watching this forum to know to reply?
Users can also create smart playlists with lots of songs that are very slow to display, so removing the songs node does not solve the underlying speed issue. It is all too easy to remove a function, much harder to improve the design.
Posts: 3,077
Joined: Jun 2009
(2016-03-16, 14:19)zag Wrote: but the speed thing has come up a few times on the forum by users.
I may miss something obvious, but isn't the fact that user complains about the speed of something, the proof that users do use and need this thing ?
Posts: 3,901
Joined: Sep 2013
Reputation:
358
I don't use the song node as such, but I can imagine that there are a lot of people who do.
Besides, one of the reasons I enjoy Kodi is the flexibility it gives me to display my media the way I want to. Removing the song node would remove some of that flexibility. Besides, displaying all the songs isn't slow, its starting playback of one of them that is.
Learning Linux the hard way !!
Posts: 10,533
Joined: Oct 2011
Reputation:
640
jjd-uk
Team-Kodi Member
Posts: 10,533
I've seen many reports of users using the Songs node to initiate random playback of their entire library which is why I vote for it to not be removed.
