Is there an issue with IOS Safari & MoOde?

[suzywong]

The streamers:

Allo USBSig/Digi1Sig (ethernet):  Moode 8.0.2
RPi 3B+ (ethernet and wifi): Moode  7.6.1
RPi Zero W (ethernet) : Moode 7.6.1

The control points:

PC: Windoze 10 - Google Chrome
iPad Pro (4-5 years old): iOS 15.4.1 - Safari

All the streamers exhibit pretty much the same behaviour.

Using the PC, Moode loads and displays the Tag screen in a very healthy 3-5 seconds (the Zero being the slowest).

Using Safari on the iPad it takes Moode 50+ seconds to load the Tag screen. That's right, FIFTY! There are other issues that have been discussed before (slowness when scrolling).

For trial purposes I loaded Google Chrome onto the iPad. Tag screen load times are 3-5 seconds for all the streamers. There are also no issues when scrolling. I think I can conclude that the issues are not related to my "ancient hardware"   , as Chrome for iPad works just fine.

So does anybody have any idea as to what is going on here with Safari? Or, indeed, what settings in Safari have I might have messed up?

[TheOldPresbyope]

@suzywong

5th Gen iPad 9.7 (2017) here, updated from the original iOS 10.2.1 to iOS 15.4.1. 

This device seems to be performing well in a 5GHz WiFi environment with either Safari or Chrome controlling a moOde 8.0.2 player which in turn is connected (also via WiFi) to a ca 550 album NAS. There's certainly nothing like a 50 second load time after I clear browser cache/browsing data. How big is your library? 

I tired of benchmarking different Web browsers several years ago, especially on iOS devices where Apple requires all browsers to use the same WebKit engine (or at least it did the last time I looked). Some variation in performance is to be expected, of course, but not a 10-to-1 difference in load times.

Not sure where to suggest you look for an explanation.

Regards,
Kent

[swinokur]

Hey there,
I reported an issue with moode's behavior on iOS based devices earlier. (It takes a long time for the album images to appear).

One thing I did find is that the web debugging tool "MIHTool" (http://mihtool.com/) did /not/ have the same rendering slowdown issue as all other browsers on the same iPad.

So if you're seeing weird behavior on an ios device - try using MIHtool to load moode's webpage and see if you get different performance...

[kit1cat]

I have a iPad Mini 5 using the latest ISO and have problems using Safari, long time to load pages etc. No problems using Edge, Firefox or Opera on the mini 5.

[Tim Curtis]

Try clearing the Safari Browser cache.

[Tim Curtis]

Another thing to check is whether Safari Browser supports native lazy loading of images. If it does not then an alternative but slightly slower javascript routine is used to lazy load images. Last I checked Safari still does not support native lazy load.

Open the Browser javascript console. It's a selection on the View, Developer tools menu or similar.

Type in the command below. If it returns "true" then the Browser supports native lazy load.

Code:

('loading' in HTMLImageElement.prototype)

[TheOldPresbyope]

Candidly, I'm in no way expert in Apple software. Unlike various Android devices I've owned, my iPad is used as an appliance.

Nevertheless, picking up my iPad and drilling down through Settings>Safari>Advanced>Experimental  Features, I find that "Lazy image loading" is enabled. (ETA - there's a gazillion other experimental settings, some enabled, some not, for which I have no gazetteer.)

Maybe that has a bearing on my observed performance vs others?

Regards,
Kent

[Tim Curtis]

Good find :-)

The setting is present in Safari v15.1 on my iMac OSX Montery v12.0.1 but not available in Safari thats included in IOS 12.5.5 on my old iPad mini 2.

[TheOldPresbyope]

OTOH,

 I just disabled the "Lazy image loading" setting and cleared browser history; restarted Safari and again navigated to the same moOde player. I don't notice a significant difference, if any, in the time it takes to load and display the library. 

we need someone who experiences the issue to do some tests.

Regards,
Kent

[swinokur]

for reference here's the thread where I described everything I was seeing as well as the troubleshooting steps that I took.

https://moodeaudio.org/forum/showthread.php?tid=4701