08-29-2020, 08:17 AM
(08-28-2020, 09:21 AM)RPI4 Rambler Wrote:(08-26-2020, 09:50 AM)vinnn Wrote: Seems less an mpd issue, more the web application snapping under the weight of so much html to generate.You tried using an mpd client instead? Something like mpdroid (Android). Gonna be a more basic interface than the web app to navigate but it has the advantage of being an application with it's own local metadata cache/database. Even if you can get the web app to work your web browser might have problems rendering that much data, especially on a mobile device.
Did I post this already? If so, I apologise. I tend to agree with you, vinn. mpc stats clearly shows that the 'naked' indexing has indeed been done and succeeded. So it might come down that the metatag processing is overwhelmed, either in the indexing stage (too many tags to index) or in the presentation stage. Good suggestion to use a different mpd client. I'll try it out.
One other cause might be the compatibility with the web browser. As I have used Chrome, that would be unlikeliy. I do have a system-wide VPN installed, and that has already caused browser problems, particularly re. DNS. This has still not been solved by the VPN's support dept. Could it be that the VPN blocks the Tags and Album output somehow?
I already mentioned trying out MPD 0.22 but what I meant to say is the latest beta of 0.22 as one can switch to 0.22 within Moode's GUI 6.7.1 now.
Thanks & best regards,
marco
Ok, I tried a diferent MPD client as vinnn suggested, on my old Samsung Android tablet, it's called MPD Control (mpdroid did not work). It offers only two Library views:
Code:
By artists / album
and
Code:
By directories/files
These come from Moode, though, not the app. The app has three operating modes (basically Library Views) in the form of tabs and should be able to display and control music playback:
Code:
Playing | Library | Playlists
And now for the good news, apart from the loading speed, the Library views work but with some restraints (that is covered below)! The app lets you configure at least two servers, and offers not just Library views, it also lets you choose the Outputs as defined in Moode.
By selecting Playlists, one can select Radios and Playlists (Default and Favorites), just as in Moode itself. Selecting Radios yields no output, while Favorites yields none too (which is correct).
All the while Moode itself is doing something: user www-data started php-fpm7.3 (the indexer), so that may explain the empty Radio page in the app. [Edit: it turns out that this MPD client is looking for 'Radios.m3u' as the default, which, in Moode' is called 'Default Playlist.m3u' in /var/lib/mpd/playlists.
Playing a webradio station is indeed displayed and controllable by the app, though without artwork; in Moode the artwork is there, but probably not compatible with this app.
Using the Radio view in the app is still empty but one can select streams (4 in this case); I'm totally in the dark where those streams come from (presumably from Moode) but why and how is beyond me?
Meanwhile back in Moode, the extra metatags field in Appearance has disappeared, limiting the number of views in the Android app.
Cheers,
marco