10-31-2021, 07:05 PM
I've been having performance problems with the Moode web interface for two or three years and posted about it before at tiresome length. I think I've solved the problem. The question is whether or not it's a work around or a solution. In my bedroom installation I've used my Android tablet or phone as the terminal. Response time is generally in the 10 to 60 second range for a screen tap. Recently I tried my wife's old (4 years) laptop, Intel I5 processor, 8Gb RAM. It works great. My current phone has an octacore Snapdragon 662 processor and 6 Gb of RAM. My tablet has a MediaTek Helio P221 octacore processor and 4 Gb of RAM. Neither are particularly high end but work fine for other web browsing.
Wifi signal strength in the bedroom is around -50dBf for 5GHz and better for 2.4. I'm happy to be able to use Moode again although the laptop requires sitting up. <g> I'm guessing that either the graphics processor or the CPU in the Android devices isn't big enough unless it's an Android thing. I do get slower response time using an HDMI or DSI local display with the Pi but not as slow as the Android devices.
Does anyone else have a similar experience?
BTW, I've been having fun with CamillaDSP. I built a simple loudness contour that works and am receiving a measurement mic today.
Wifi signal strength in the bedroom is around -50dBf for 5GHz and better for 2.4. I'm happy to be able to use Moode again although the laptop requires sitting up. <g> I'm guessing that either the graphics processor or the CPU in the Android devices isn't big enough unless it's an Android thing. I do get slower response time using an HDMI or DSI local display with the Pi but not as slow as the Android devices.
Does anyone else have a similar experience?
BTW, I've been having fun with CamillaDSP. I built a simple loudness contour that works and am receiving a measurement mic today.
