Moode Forum

Full Version: Official moOde 7.1.0 support thread
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
Very odd. There shoud be no diff between 3b+ and 3A+

Maybe better to remove the -j4 option and upload a new update zip?
Nah, it's the memory limitation.

I tried again. Same RPi3A+, same SanDisk Ultra 16GB uSD card, same moOde 7.0.1 starting point (with rootfs expanded both last time and this time, of course).

This time I enabled swap using a 1GB /var/swap file. The update process took only 21m.

Code:
pi@710from701:/var/local/www $ cat update-r701.log
20210319 220104 updater: Begin 2021-03-15 update for moOde 7.0.1 2020-12-23
20210319 220104 updater: ** Version check
20210319 220105 updater: ** Step 1-9: Update SQL tables
20210319 220112 updater: ** Step 3-9: Update binaries
20210319 220112 updater: **  Upd 1-5: Install MPD 0.22.6
20210319 220112 updater: **  Upd 2-5: Install miniDLNA 1.3.0
20210319 220112 updater: **  Upd 3-5: Install librespot 0.1.6
20210319 220112 updater: **  Upd 4-5: Install ashuffle 3.11.1
20210319 220112 updater: **  Upd 5-5: Install moodeutl 1.5.2
20210319 220112 updater: ** Step 4-9: Install CamillaDSP and CamillaGUI...
20210319 220112 updater: **  Upd 1-3: Install ALSA cdsp module (commit e941420)
20210319 220112 updater: **  Upd 2-3: Install CamillaDSP 0.5.0-beta4
20210319 220112 updater: **  Upd 3-3: Install CamillaGUI 0.6.0
20210319 220354 updater: ** Step 5-9: Install packages...
20210319 220354 updater: **  Pkg 1-4: SoX utils
20210319 220419 updater: **  Pkg 2-4: FLAC utils
20210319 220428 updater: **  Pkg 3-4: php-yaml
20210319 220438 updater: **  Pkg 4-4: nmap
20210319 220456 updater: ** Step 6-9: Install Allo Boss 2 OLED support...
20210319 220456 updater: **  Pkg 1-2: python-smbus
20210319 220619 updater: **  Pkg 2-2: python-pil
20210319 220652 updater: **  Scr 1-1: Python OLED driver script
20210319 220653 updater: **  Sys 1-1: Systemd unit
20210319 220654 updater: ** Step 7-9: Build upmpdcli and libupnpp-bindings...
20210319 220654 updater: **  Src 1-2: Compile upmpdcli 1.5.8
20210319 221838 updater: **  Src 2-2: Compile libupnpp-bindings-0.20.1
20210319 222153 updater: **  Del 1-1: Delete legacy UPnP sample progs
20210319 222153 updater: ** Step 8-9: Update moOde sources and configs
20210319 222155 updater: ** Step 9-9: Sync changes to disk
20210319 222159 updater: End 2021-03-15 update for moOde 7.0.1 2020-12-23

ETA - I didn't monitor the swap usage closely, but roughly 500MB was in use at several points when I looked.

Regards,
Kent
Maybe -J4 uses more RAM than without?
(03-20-2021, 03:19 AM)Tim Curtis Wrote: [ -> ]Maybe -J4 uses more RAM than without?

Prolly. I didn’t try to monitor core usage. I’ll have to set up an experiment and it’s too late to do it tonight. Mañana.

Regards,
Kent
I have a "no j4" version the update on the distribution server but it will require some tweaks to point to it from your 3A+.

Email or PM me tomorrow and we can test it out.
hooray, the update on the Pi Zero was successful Smile (also took only 18 h to compile the code Wink )
(03-20-2021, 03:28 AM)Tim Curtis Wrote: [ -> ]I have a "no j4" version the update on the distribution server but it will require some tweaks to point to it from your 3A+.

Email or PM me tomorrow and we can test it out.

Sure I can test it but here's what I've already found by running just STEP 7-9 in isolation. [I screwed up the script though, so I didn't capture your nice log output with time stamps.]

moOde 7.1.0 ('cuz I'd already updated), no swap

With 'make -j4' replaced by 'make', the upmpdcli (Src 1-2) portion compiled quickly. There was always at least 200MiB of available memory and cc1plus was often the most active process.

However, the libupnpp-bindings (Src 2-2) portion is still grinding on, 50m into my test.

It's stuck in building libs/upnpp_wrap.o at the moment. We're down to ca 60MiB available memory (the scheduler has had to dip into the buff/cache reserve) and the most active process is the dreaded kswapd0. Basically we're just thrashing. All 4 CPUs are mostly in the wait state with some percentage of idle state and almost no percentage in user state. The desired cc1plus process is getting between 0% and 2% of CPU.

I really think enabling swap for the duration of the update is the better solution. I'll test it later with the RPi Zero-W I just pulled out of its hiding place.

Regards,
Kent
Hang tight. @bitlab generated the build output for upmpdcli and libupnpp bindings and so it might be possible to just copy the files and dirs to their destination instead of compile/make.

I'll try to test later today or tomorrow.
Hello !
I've tried to do the update from 7.0.1 to 7.1 doing "check for update" but the answer returned is always "software is up to date". I run moOde using a Pi-4B 1.2
Any idea ?
Hello,

I just made a fresh install of Moode 7.1.0 which I discover coming from 6.7.1. Thank you for the updates regarding the album/tag views which are better suited for a classical audio collection.

There is still/yet an issue with the thumbnail resolution in preferences/library/ : the "auto" setting still does not seem to work as intended and lower resolution (200px and 300px) are unfortunately no more available.

My screen is a full HD 13,3" (notebook). All the art covers are 500p x 500 px. The "auto" mode generates 100px thumbnails. In  the standard Album view (6 columns) these thumnbnails are scaled up by Firefox in full screen mode to 180 px which leads to blurry thumbail covers. The auto mode behavior has not changed from 6.7.1 (I did not use it) but it is now impossible to force the resolution to 200px thumbnails which is the best (slight downscaling).

200px is reported by Firefox to be the resolution of radio icons which are displayed as 180px.

There is yet no other choice in Album mode but to use of resolution of 400 px which is far too much and makes the UI  not as snappy as before.

Q1 : is it possible to restore the lower resolutions  (including 200px) ?

The system info tab shows two parameters : cover blur (=20px) and cover scale (1.25).

Q2 : What are these settings, are they linked with the "auto" issue and where can they be set ?

Thank you for you help.

Regards.

Philippe
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19