Official moOde 6.6.0 support thread

[gtgibo]

Hi I noticed a small bug in 6.6.0, when I am at the computer with windows 10 operating system in the network section the Raspberry with the name Moode is no longer displayed. Before when it mounted 6.5.2 everything was ok.

[Tim Curtis]

I don't think this a bug in moOde since it shows up in my Mac's network discovery. These network discovery protocols are not 100% reliable especially when hosts come in and out of the network. Sometimes you have to reboot the client (Windows, Mac, Linux) and let it rediscover things on the network.

[swizzle]

It's another way to push you to get a new phone I suppose.
Are you not able to get round the issue by using a different browser or do they use the same javascript engine?  Sorry I don't use Apple devices so am just curious.

You are almost certainly correct

I've tried using different browsers from the Apple Appstore: 

Most (for example Google Chrome, Firefox, Opera & DuckDuckGo) are incompatible with iOS 9.3.5, and won't even install.

Others (like MS Edge (old version) & Dolphin) will install, but have the same issues as Safari, in that MoOde will start up, the library loads, but the Library (Radio, Album, Tag etc) & Playlist (also Appearance) screens are "all grey".

Probably time to pension off the iPad 2, unless Swizzle can fix it easily - for sure, it's not worth compromising the new build of MoOde, just for the sake for the older iPads.

I agree, although it may be possible to detect and use the older Javascript/CSS that worked on older devices.  For me at least, I use Kazoo as the controller and this runs fine on iOS 9.3.5 (for the moment at least).

It wouldn’t make any sense to use the old javascript but years of supporting janky IE means there’s usually a way to work around browser issues. I’ll have to look at the console log again when I have more free time to see if that’s the case here, but I suspect older iOS devices are going to start showing their age wrt performance anyway.

And an iPad 2 doesn’t even have a Retina display, why do you hate your eyes?

[TheOldPresbyope]

I'm not writing the UI code so I'll keep quiet after this, but the phrase "technical debt" comes to mind when I think about work-arounds for moldering systems.

Regards,
Kent

[suzywong]

iPad 2 performance is not really a issue if it is only being used as a "single usage" controller for moode. similarly for the retina display. so my iPad 2 sits permanently in a "goose-neck" stand in my office with Safari open at the Allo streamer Library page.

[gtgibo]

I don't think this a bug in moOde since it shows up in my Mac's network discovery. These network discovery protocols are not  100% reliable especially when hosts come in and out of the network. Sometimes you have to reboot the client (Windows, Mac, Linux) and let it rediscover things on the network.

Thanks for your answer and work, but pure rebooting several times from both the computer and the raspberry the problem persists.

[Tim Curtis]

Try rebooting your Router

[TheOldPresbyope]

Hi I noticed a small bug in 6.6.0, when I am at the computer with windows 10 operating system in the network section the Raspberry with the name Moode is no longer displayed. Before when it mounted 6.5.2 everything was ok.

I think this is Win10 being its idiosyncratic self.

My partner runs Win10 Home on her laptop. I have a number of RPis running moOdeOS, as well as a laptop and a tower server running Linux Mint. (there's always a few other LInux-based boxes of one kind or another around but let's stay focused.) On the laptop I'm also running Win10 Pro as a virtual machine.

The moOde players and the Linux hosts can all "see" each other (in their equivalent of what used to be Window's Network Neighborhood) as well as her Win10 laptop and my Win10 virtual machine.

Neither Win10 system shows any moOde player or Linux host in its Network screen. However, both can find all these hosts when using the net command.

I keep my copy of Win10Pro because I have a couple of favorite applications which run better in it than in the wine compatibility layer in LInux (although wine gets better with each release) and because I always want to be able to test Windows-based music-related apps which get suggested.

I do not use Win10Pro for daily work. I find it increasingly annoying and no longer care to invest the time to make the rest of my world compatible with it.

Just my two cents worth.

Regards,
Kent

[suzywong]

The moOde players and the Linux hosts can all "see" each other (in their equivalent of what used to be Window's Network Neighborhood) as well as her Win10 laptop and my Win10 virtual machine.

Neither Win10 system shows any moOde player or Linux host in its Network screen. However, both can find all these hosts when using the net command.

Curious, I can my RPis in Windows Explorer's left hand panel in the "Network section" (Win10 pro). They show the NAS, Playlists, Radio & SDCard folders, but not the actual software folders, which is not surprising.

[swizzle]

Really impressive. Very smooth. The only thing is that my old iPad 2 with iOS 9.3.5 doesn't show radio library again. Many elements are missing. Cleaning cache and reboot didn't help.

Did it work with 6.5? iOS 9 is sufficiently old enough that the version of Safari it uses is missing some key web features and unfortunately there’s no way to just update the browser.

I do feel like a moode browser is a really good use case for an old tablet though so you might try loading 6.6 with the browser’s console window showing and if there are any errors post the output (in a code box, it’s the little icon on the top right with <>) and we might be able to work around whatever javascript isn’t supported.

I have to connect my iPhone to a Windows PC, so I use Chrome for remote debug. I hope this will help you.

Code:

moode.local/:34 Viewport argument key "viewport-fit" not recognized and ignored.
VMundefined:33 SyntaxError: Unexpected keyword 'const'
(anonymous) @ playerlib-nomin.js:33
VMundefined:3 Viewport argument key "viewport-fit" not recognized and ignored.
attr @ VM44 jquery-1.8.2.min.js:3
access @ VM44 jquery-1.8.2.min.js:3
attr @ VM44 jquery-1.8.2.min.js:3
(anonymous) @ VM22 scripts-panels.min.js:25
k @ VM44 jquery-1.8.2.min.js:3
fireWith @ VM44 jquery-1.8.2.min.js:3
ready @ VM44 jquery-1.8.2.min.js:3
D @ VM44 jquery-1.8.2.min.js:3
VMundefined:26 ReferenceError: Can't find variable: getParamOrValue
setFontSize @ VM1 playerlib.min.js:26
(anonymous) @ VM22 scripts-panels.min.js:25
k @ VM44 jquery-1.8.2.min.js:3
fireWith @ VM44 jquery-1.8.2.min.js:3
y @ VM44 jquery-1.8.2.min.js:3
d @ VM44 jquery-1.8.2.min.js:3
moode.local/:34 Viewport argument key "viewport-fit" not recognized and ignored.
VMundefined:33 SyntaxError: Unexpected keyword 'const'
(anonymous) @ playerlib-nomin.js:33
VMundefined:3 Viewport argument key "viewport-fit" not recognized and ignored.
attr @ VM44 jquery-1.8.2.min.js:3
access @ VM44 jquery-1.8.2.min.js:3
attr @ VM44 jquery-1.8.2.min.js:3
(anonymous) @ VM22 scripts-panels.min.js:25
k @ VM44 jquery-1.8.2.min.js:3
fireWith @ VM44 jquery-1.8.2.min.js:3
ready @ VM44 jquery-1.8.2.min.js:3
D @ VM44 jquery-1.8.2.min.js:3
VMundefined:26 ReferenceError: Can't find variable: getParamOrValue
setFontSize @ VM1 playerlib.min.js:26
(anonymous) @ VM22 scripts-panels.min.js:25
k @ VM44 jquery-1.8.2.min.js:3
fireWith @ VM44 jquery-1.8.2.min.js:3
y @ VM44 jquery-1.8.2.min.js:3
d @ VM44 jquery-1.8.2.min.js:3

Ugh, minimized javascript is worthless for debugging.

Anyway so const seems to be at issue here. Early iOS is missing a bunch of javascript that would later make up ES6. It basically lets you set up an immutable variable (it’s kind of a convenience feature for large, team-based development as it’ll throw an error if you try to redefine one so you know there’s a something not good happening), but there’s really nothing stopping us from using regular variables and just not messing with them.

https://www.javascripttutorial.net/es6/j...ipt-const/

In playerlib.js there are a number of variables defined with const at the beginning of the file, you can change it to use let instead and that seems to work (albeit on my iOS 14 device), though I can’t say there won’t be issues elsewhere related to that change or other ES6 conventions that old iOS doesn’t support that have crept into the code in other areas and still prevent it from working. 

The comment about older devices... there are usually a lot of features added to newer moode versions that are nice to have but there’s no such thing as a free lunch and those features often come with added processing demands. As an example the new badges for bitrate, etc. The more complex the list structure and css is the more your device has to work to display it. I did some work to streamline the lists a few versions ago but recent progress has stamped that out lol. Tl;dr: you will definitely be happier running moode on newer hardware.