2018-04-08, 00:01
In trying to work around speed issues related to .m3u playlists, I thought I'd create an album smart playlist based on user ratings. The playlist contains 170 albums representing about 2,700 tracks. Browsing the playlist is very quick. But when I try to play the playlist in partymode using the context menu, nothing plays. The dialog pops up saying it is filling glasses, but nothing happens after that. After waiting 5+ minutes, I tried to just play the playlist from the context menu. When using the play option, Kodi locks up without any notification. After waiting 5 minutes or so, the playlist eventually starts playing.
Linked below is a debug log of me launching Kodi, attempting to play the playlist in partymode, and then just playing it via the context menu. This time it seemed like it only took 1-2 minutes before the playlist started playing. What's weird is the default partymode playlist only takes about 5 or 6 seconds to load, and it contains over 36,000 tracks. Can't figure out why other playlists take so much longer.
Is there anything I can do to improve performance, or is this just the way it is? Should partymode work for album playlists? FYI, my music is on a directly attached USB drive, not network storage.
Thanks!
pastebin.xyz/p?q=d01FQms
FYI, this is a large debug log and Chrome seems to choke on it...Microsoft Edge doesn't seem to have a problem with it though.
Linked below is a debug log of me launching Kodi, attempting to play the playlist in partymode, and then just playing it via the context menu. This time it seemed like it only took 1-2 minutes before the playlist started playing. What's weird is the default partymode playlist only takes about 5 or 6 seconds to load, and it contains over 36,000 tracks. Can't figure out why other playlists take so much longer.
Is there anything I can do to improve performance, or is this just the way it is? Should partymode work for album playlists? FYI, my music is on a directly attached USB drive, not network storage.
Thanks!
pastebin.xyz/p?q=d01FQms
FYI, this is a large debug log and Chrome seems to choke on it...Microsoft Edge doesn't seem to have a problem with it though.