moOde 5 Release Candidate RC0

[blackie333]

In moode 4.4 I have a problem that my Synology NAS disk can't go to sleep when it's folder is defined in moode sources.
Even when moode plays radio station the NAS is somehow under usage...
I have to reboot moode and don't start any playback to allow the disk go sleep...
Can i expect this to be fixed in moode 5.0 ? Thanks

[dw4y_]

Great work !

Still some margin problems in album view, as shown in the screenshots
(I'm a web developper, CSS is 50% of my work, and some details burn my eyes :p )

         

[Tim Curtis]

Margin issues will be fixed in RC1

I'll look into the overlapping text in the sim but I need device model if its IOS otherwise the viewport size and Browser type.

[Geojanitor]

Hey Tim, just downloaded the latest release. I am getting a strange error in the album script beneath the album cover art on the playback page, "sudo: unable to resolve host moode/2", see the attached screen shot. This error is where the "Album Artist" tag usually shows up. I got it on every album I tried. Thanks for all your efforts.

[Tim Curtis]

Thats odd. Normally the encoded-at rate and file format for example "16/44.1 FLAC." would be displayed in that position.

Turn on debug logging in System config and then play the track that produces that strange text.

Then stop playback and run the following command via SSH and post the results.

Code:

moodeutl -l | grep mediainfo

Don't forget to turn off Debug logging or it will really clutter up the log.

-Tim

[dw4y_]

Margin issues will be fixed in RC1

I'll look into the overlapping text in the sim but I need device model if its IOS otherwise the viewport size and Browser type.

I'm testing on Chrome 73 / MacOS Mojave.
Will test on other browsers and IOS devices in a few hours and report it back here.

[jonners]

With my Pi3b+/Katana, MPD Hardware volume, the system boots up with Alsa Volume at 100%, even though the volume wheel has returned to the setting it had when last powered down. Jogging the volume brings it back down to normal.
Fortunately no disasters, since my system doesn't have much excess gain.....

[Tim Curtis]

I also have a Katana and volume is always set correctly during startup.

If you can repro the issue, post the repro steps and moode log when it occurs. There will be telltale log entries that show the volume configuration and initial setting.

[jonners]

Code:

      M O O D E    L O G  

   20190328 110819 worker: - Start
   20190328 110819 worker: Successfully daemonized
   20190328 110819 worker: Integrity check (warning: worker.php)
   20190328 110819 worker: Integrity check (warning: playerlib.php)
   20190328 110819 worker: Integrity check (passed with warnings)
   20190328 110819 worker: ALSA volume (0%)
   20190328 110819 worker: Session loaded
   20190328 110819 worker: Debug logging (off)
   20190328 110819 worker: - Platform
   20190328 110821 worker: Rel  (Moode 5.0-RC0-53 2019-MM-DD)
   20190328 110821 worker: Upd  (None)
   20190328 110821 worker: Rasp (9.6)
   20190328 110821 worker: Kern (4.19.30-v7+)
   20190328 110821 worker: MPD  (0.21.6)
   20190328 110821 worker: Host (moode)
   20190328 110821 worker: Hdwr (Pi-3B+ 1GB v1.3)
   20190328 110821 worker: Arch (armv7l)
   20190328 110821 worker: Gov  (performance)
   20190328 110821 worker: USB boot enabled
   20190328 110825 worker: File system not expanded yet
   20190328 110825 worker: HDMI port off
   20190328 110825 worker: File check ok
   20190328 110825 worker: - Network
   20190328 110826 worker: eth0 exists
   20190328 110826 worker: eth0 (192.168.0.3)
   20190328 110826 worker: wlan0 does not exist
   20190328 110826 worker: - Audio
   20190328 110826 worker: ALSA outputs unmuted
   20190328 110826 worker: ALSA card number (0)
   20190328 110826 worker: Audio output (I2S audio device)
   20190328 110826 worker: Audio device (Allo Katana DAC)
   20190328 110826 worker: ALSA mixer name (Master)
   20190328 110826 worker: MPD volume control (hardware)
   20190328 110826 worker: Hdwr volume controller exists
   20190328 110826 worker: - Services
   20190328 110826 worker: Reset renderer active state
   20190328 110826 worker: MPD conf updated
   20190328 110826 worker: MPD started
   20190328 110827 worker: MPD accepting connections
   20190328 110827 worker: Configure MPD outputs
   20190328 110827 worker: MPD output 1 ALSA default (on)
   20190328 110827 worker: MPD output 2 ALSA crossfeed (off)
   20190328 110827 worker: MPD output 3 ALSA parametric eq (off)
   20190328 110827 worker: MPD output 4 ALSA graphic eq (off)
   20190328 110827 worker: MPD output 5 ALSA polarity inversion (off)
   20190328 110827 worker: MPD output 6 ALSA bluetooth (off)
   20190328 110827 worker: MPD output 7 HTTP stream (off)
   20190328 110827 worker: MPD crossfade (off)
   20190328 110827 worker: - Music sources
   20190328 110827 worker: USB source (DISCL)
   20190328 110827 worker: NAS sources (none configured)
   20190328 110827 worker: - Miscellaneous
   20190328 110827 worker: Volume level (20) restored
   20190328 110827 worker: Maintenance interval (21600)
   20190328 110827 worker: Screen saver activation (Never)
   20190328 110827 worker: Watchdog started
   20190328 110827 worker: Ready

I also have a Katana and volume is always set correctly during startup.

If you can repro the issue, post the repro steps and moode log when it occurs. There will be telltale log entries that show the volume configuration and initial setting.

[Tim Curtis]

I don't see anything suspicious in the log. ALSA volume is zeroed out at the beginning of startup and then the knob volume 20 is restored near the end of startup. This should result in ALSA volume being set appropriately.

Here are some additional debugging commands when the problem occurs. Just remember to not alter the knob setting b4 running the cmds.

Code:

sqlite3 /var/local/www/db/moode-sqlite3.db "select * from cfg_system where param='mpdmixer' or param='audioin' or param='audioout' or param='alsavolume' or param='amixname' or param='mpdmixer_local'"

/var/www/command/util.sh get-alsavol Master