![]() |
[SOLVED] Large library - performance (5.3 VS 4.4) - Printable Version +- Moode Forum (https://moodeaudio.org/forum) +-- Forum: moOde audio player (https://moodeaudio.org/forum/forumdisplay.php?fid=3) +--- Forum: Support (https://moodeaudio.org/forum/forumdisplay.php?fid=7) +--- Thread: [SOLVED] Large library - performance (5.3 VS 4.4) (/showthread.php?tid=1436) |
RE: Large library - performance (5.3 VS 4.4) - nosferatu_cat - 06-15-2019 (06-07-2019, 04:13 PM)Just tried to apply the patches. The wget failed with a 404 error. I tried it with ssh on a pi and also tried the http portion from a browser on my desktop machine. Tim Curtis Wrote: Here are the lazyload patches :-) RE: Large library - performance (5.3 VS 4.4) - nosferatu_cat - 06-15-2019 (06-15-2019, 07:12 PM)Just to clarify, h ere\s the output of the wget from the pi: Wrote: pi@moode:~ $ wget http://moodeaudio.org/test/lazyload-update.zip RE: Large library - performance (5.3 VS 4.4) - Tim Curtis - 06-15-2019 The patch is rolled into moOde 5.3.1 update. RE: Large library - performance (5.3 VS 4.4) - nosferatu_cat - 06-15-2019 (06-15-2019, 07:43 PM)Ah. I tried today after applying the update yesterday. My performance problem is still there. It takes a long time to load the initial screen when I first connect and response time is very slow, sometimes as much as 30 seconds. I should keep more careful track, but, other than when first connecting, the lag seems random. Sometimes when I tap on the screen (Android tablet) response time is sub second. Other times it lags. Beside the transition from one function to another I often have problems scrolling through lists. This has been the case for me ever since moving to v 5.0 In v4 and previous releases response time was consistently quick. A lesser problem is that the now playing screen does not always update. If I\m reading or doing something else on the tablet when I switch back to Moode, the track shown on the screen is often several tracks behind the one actually playing. I do have a large library although it seems like that shouldn Wrote: The patch is rolled into moOde 5.3.1 update. RE: Large library - performance (5.3 VS 4.4) - Tim Curtis - 06-15-2019 it will be difficult to troubleshoot based solely on a description of the symptoms. Try to provide more information for example: - Errors or other indications in the logs (moode log, mod log, syslog) - Try other clients (PC, Mac, etc) - Try different SDCard RE: Large library - performance (5.3 VS 4.4) - Cyberguy - 06-17-2019 I can confirm that too - sometimes have to reload site to update. The response time have helped a lot from 5.3 to 5.3.1 but we are not seeing 3.x niveau yet ![]() One strange thing - when in Album view and I do a search, then no cover images is shown in result- just blank squares. RPI 3 B+ Moode 5.3.1 iPad Pro 10.50" All but LAN disabled RE: Large library - performance (5.3 VS 4.4) - Tim Curtis - 06-17-2019 I can repro. Until I get time to investigate just tap the Album view button again and it will start the image lazy loader. -Tim RE: Large library - performance (5.3 VS 4.4) - Tim Curtis - 06-17-2019 Confirmed it's a bug. Give this patch a try. You prolly have to refresh Browser multiple times b4 the updated JS gets loaded Code: wget -q http://moodeaudio.org/test/scripts-panels.js.zip -Tim RE: Large library - performance (5.3 VS 4.4) - nosferatu_cat - 06-25-2019 It may be due to the tablet I'm using as a terminal, a Google Nexus 2013 running LineageOS Android 7 equivalent. On a 3 year old ASUS tablet response times are better but not perfect, and on my desktop machine response time is acceptable. The Google Nexus worked fine with Moode 4x. Since the Nexus has had the standard broken USB port for several years I've been looking for an excuse to replace it. Inductive charging is the only thing that's kept it alive. <g> (06-15-2019, 09:06 PM)Tim Curtis Wrote: it will be difficult to troubleshoot based solely on a description of the symptoms. Try to provide more information for example: RE: Large library - performance (5.3 VS 4.4) - nosferatu_cat - 06-30-2019 (06-25-2019, 07:47 PM)Finally got the time to try a different SD card. That solved the problem. nosferatu_cat Wrote: It may be due to the tablet I'm using as a terminal, a Google Nexus 2013 running LineageOS Android 7 equivalent. On a 3 year old ASUS tablet response times are better but not perfect, and on my desktop machine response time is acceptable. The Google Nexus worked fine with Moode 4x. Since the Nexus has had the standard broken USB port for several years I've been looking for an excuse to replace it. Inductive charging is the only thing that's kept it alive. <g> |