02-04-2021, 08:44 PM
hi, apologies if this has been discussed. I did not see any specifically related threads.
I'm seeing a huge performance difference between a windows client and an android client. I think I need to provide specifics on my setup for this to be useful. I'm running moode 7.01 on a pi4, 4 GB. All my music is on an NFS server (also pi4, 4 GB). The connection between the server and the moode player is wired cat6 ethernet (a couple of 100 mbit fast ethernet switches make the connection). The music repository on the server is pretty large, over 20,000 albums, nearly all flac. For clients I have used multiple android devices - phones and tablets, multiple windows laptops, and I have tried nearly every browser out there. On android, I seem to have done best with opera lite. On windows, I've mostly used firefox. Regardless of whether the windows laptop clients are wired or wireless, I get decent performance - response to clicks is good enough (one caveat is the tag view, which is pretty unuseable with a large music repository. Even on wndows, it takes about 8 seconds to get a response to selecting, say, an artist in the tag view. I'd love to have the tag view functionality, but that doesn't seem possible without a significant architecture change, whether in moode or more likely in the mpd indexing)
On the android client, with a largish playlist (say 2000 songs), turning shuffle on or off can take several seconds. Ditto for going from play to pause, or changing from playback to library views. Back in the day, I did unix admin. there was a rule of thumb for user interfaces: we tried to keep response around 50 ms, so several seconds is pretty problematic. All my android devices are running fairly recent versions of android. The tablet does a fair bit better than a phone, but still exhibits this behavior. I have cover display turned off on the playlist view to help performance a bit, but it doesn't solve this problem. First connection from the client to an idle moode using an android device can take multiple 10s of seconds. This does not happen if I use my windows laptop. If I accidentally select the tag view on android, I can pretty much go get lunch.
I have used many digital playback systems in the last 25 years, including some I built myself (but I'm not a software developer). Moode is terrific, best I have used. Somewhere around moode 6 the performance for large repositories became much better, and is greatly appreciated. performance in 7 seems more sluggish than 6, but the android problem is there in all versions. I realize there may not be a fix without significant rearchitecture in moode or mpd, but wanted to put this on the table for awareness and any discussion.
I love moode, but perhaps can sully this post with one minor suggested improvement: "set favorites" currently requires you to type your selection. often I want to set the favorites to an existing playlist and may not remember its exact name. having the option to select from a list of current playlists would be very nice IMO.
I'm seeing a huge performance difference between a windows client and an android client. I think I need to provide specifics on my setup for this to be useful. I'm running moode 7.01 on a pi4, 4 GB. All my music is on an NFS server (also pi4, 4 GB). The connection between the server and the moode player is wired cat6 ethernet (a couple of 100 mbit fast ethernet switches make the connection). The music repository on the server is pretty large, over 20,000 albums, nearly all flac. For clients I have used multiple android devices - phones and tablets, multiple windows laptops, and I have tried nearly every browser out there. On android, I seem to have done best with opera lite. On windows, I've mostly used firefox. Regardless of whether the windows laptop clients are wired or wireless, I get decent performance - response to clicks is good enough (one caveat is the tag view, which is pretty unuseable with a large music repository. Even on wndows, it takes about 8 seconds to get a response to selecting, say, an artist in the tag view. I'd love to have the tag view functionality, but that doesn't seem possible without a significant architecture change, whether in moode or more likely in the mpd indexing)
On the android client, with a largish playlist (say 2000 songs), turning shuffle on or off can take several seconds. Ditto for going from play to pause, or changing from playback to library views. Back in the day, I did unix admin. there was a rule of thumb for user interfaces: we tried to keep response around 50 ms, so several seconds is pretty problematic. All my android devices are running fairly recent versions of android. The tablet does a fair bit better than a phone, but still exhibits this behavior. I have cover display turned off on the playlist view to help performance a bit, but it doesn't solve this problem. First connection from the client to an idle moode using an android device can take multiple 10s of seconds. This does not happen if I use my windows laptop. If I accidentally select the tag view on android, I can pretty much go get lunch.
I have used many digital playback systems in the last 25 years, including some I built myself (but I'm not a software developer). Moode is terrific, best I have used. Somewhere around moode 6 the performance for large repositories became much better, and is greatly appreciated. performance in 7 seems more sluggish than 6, but the android problem is there in all versions. I realize there may not be a fix without significant rearchitecture in moode or mpd, but wanted to put this on the table for awareness and any discussion.
I love moode, but perhaps can sully this post with one minor suggested improvement: "set favorites" currently requires you to type your selection. often I want to set the favorites to an existing playlist and may not remember its exact name. having the option to select from a list of current playlists would be very nice IMO.
