Thank you for your donation!


Official moOde 7.0.1 support thread
(01-31-2021, 12:45 AM)TheOldPresbyope Wrote: @Rees86 


Code:
20201223 083541 worker: Pri DNS (::1)


What's up with this? Although the Raspberry Pi OS supports IPv6, moOde doesn't make any explicit use of it (and not all of its functions are guaranteed to work in the face of it).

Something is telling moOde to use an internal IPv6 DNS resolver ('::1' is the localhost loopback address in IPv6).

Regards,
Kent

Hi Kent, that was just the clue I needed to fix the issue!  I turned IPv6 off in my gateway and now the issue is gone.  Doesn't fix the underlying issue but at least I don't need to mess around with the Moode installation to get it working.

(01-31-2021, 01:24 AM)Tim Curtis Wrote: Whenever Corporate networks are involved don't expect to get a free ride to the Public internet from your unapproved Raspberry Pi host, lol

The OP post though suggests that it's not necessarily a locked down Corporate network, hard to tell from the post.

Hi Tim, luckily it's not much of a corporate network.  I'm one of the owners and also the IT / Windows / Network admin so I was able to go into our gateway and turn off IPv6 assignment.  

Thanks the quick responses from both of you!
Rees
Reply
@lamode 

Could I suggest that at this point you start a thread of your own concerning this specific connectivity issue instead of adding to this all-purpose thread which already has 300 posts? It's tiring to try to find your "needle" in this haystack.

Regards,
Kent
Reply
Here is the output:

Code:
20210202 150724 worker: -- Start
20210202 150724 worker: Successfully daemonized
20210202 150725 worker: Integrity check (passed)
20210202 150725 worker: File check (OK)
20210202 150725 worker: Session loaded
20210202 150725 worker: Debug logging (OFF)
20210202 150725 worker: -- Device
20210202 150725 worker: ALSA cards: (0:b1 | 1:Headphones | 2:empty | 3:empty
20210202 150725 worker: Configured: (1:Pi Headphone jack | mixer:(Headphone) | alsavol:0)
20210202 150726 worker: ALSA mixer actual (Headphone)
20210202 150726 worker: ALSA Headphone volume set to (0%)
20210202 150726 worker: -- System
20210202 150728 moode.php: MPD connect failed: cmd=(playlist)
20210202 150728 worker: Host     (moode)
20210202 150728 worker: moOde    (7.0.1 2020-12-23)
20210202 150728 worker: RaspiOS  (10.6)
20210202 150728 worker: Kernel   (5.4.77-v7l+ #1371)
20210202 150728 worker: Platform (Pi-4B 2GB v1.1)
20210202 150728 worker: ARM arch (armv7l, 32-bit kernel)
20210202 150728 worker: MPD ver  (0.22.3_p0x3)
20210202 150728 worker: CPU gov  (ondemand)
20210202 150728 worker: USB boot not available
20210202 150729 worker: File system expanded
20210202 150729 worker: HDMI port off
20210202 150729 worker: -- Network
20210202 150729 worker: eth0 exists
20210202 150729 worker: eth0 address not assigned
20210202 150729 worker: wlan0 exists
20210202 150729 worker: wifi country (IT)
20210202 150729 worker: wlan0 trying SSID (TIM-18451895)
20210202 150729 worker: IP addr (192.168.1.122)
20210202 150729 worker: Netmask (255.255.255.0)
20210202 150729 worker: Gateway (192.168.1.1)
20210202 150729 worker: Pri DNS (192.168.1.1)
20210202 150729 worker: Domain  (homenet.telecomitalia.it)
20210202 150729 worker: -- Audio
20210202 150729 worker: MPD conf updated
20210202 150730 worker: ALSA outputs unmuted
20210202 150730 worker: ALSA card number (1)
20210202 150730 worker: Audio output (Pi Headphone jack)
20210202 150730 worker: Audio formats (U8, S16_LE)
20210202 150730 worker: ALSA mixer name (Headphone)
20210202 150730 worker: MPD volume control (software)
20210202 150730 worker: Hdwr volume controller exists
20210202 150730 worker: Max ALSA volume (100%)
20210202 150730 worker: Reset renderer active flags
20210202 150730 worker: -- MPD
20210202 150730 worker: MPD started
20210202 150731 worker: MPD accepting connections
20210202 150731 worker: Configure MPD outputs
20210202 150731 worker: MPD output 1 ALSA default (on)
20210202 150731 worker: MPD output 2 ALSA crossfeed (off)
20210202 150731 worker: MPD output 3 ALSA parametric eq (off)
20210202 150731 worker: MPD output 4 ALSA graphic eq (off)
20210202 150731 worker: MPD output 5 ALSA polarity inversion (off)
20210202 150731 worker: MPD output 6 ALSA bluetooth (off)
20210202 150731 worker: MPD output 7 HTTP stream (off)
20210202 150731 worker: MPD crossfade (off)
20210202 150731 worker: -- Feature availability
20210202 150731 worker: Source select (available)
20210202 150731 worker: Source select (source: MPD)
20210202 150731 worker: Source select (output: Pi Headphone jack)
20210202 150731 worker: Bluetooth (available)
20210202 150731 worker: Airplay renderer (available)
20210202 150731 worker: Airplay renderer (started)
20210202 150731 worker: Spotify renderer (available)
20210202 150731 worker: Squeezelite renderer (available)
20210202 150731 worker: UPnP renderer (available)
20210202 150731 worker: UPnP renderer (started)
20210202 150731 worker: DLNA server (available)
20210202 150731 worker: UPnP browser (available)
20210202 150731 worker: GPIO button handler (available)
20210202 150731 worker: Stream recorder (n/a)
20210202 150731 worker: -- Music sources
20210202 150731 worker: USB sources (none attached)
20210202 150732 worker: NAS and UPnP sources (mountall initiated)
20210202 150732 worker: -- Miscellaneous
20210202 150732 worker: USB volume knob (Off)
20210202 150732 worker: USB auto-mounter (udisks-glue)
20210202 150732 worker: LED0 (On)
20210202 150732 worker: LED1 (On)
20210202 150732 worker: Saved MPD vol level (0)
20210202 150732 worker: Preamp volume level (0)
20210202 150732 worker: MPD volume level (41) restored
20210202 150732 worker: ALSA Headphone volume (100%)
20210202 150732 worker: Auto-play (Off)
20210202 150732 worker: Maintenance interval (3 hrs)
20210202 150732 worker: Screen saver activation (Never)
20210202 150732 worker: Session permissions (OK)
20210202 150732 worker: Watchdog started
20210202 150732 worker: Ready
Reply
Log is incomplete but the portion that was posted shows nothing abnormal which supports my earlier statement that the issues you are experiencing are external to moOde software.
Enjoy the Music!
http://moodeaudio.org | http://twitter.com/MoodeAudio | http://github.com/moodeaudio
Reply
(02-02-2021, 02:13 PM)Tim Curtis Wrote: Log is incomplete but the portion that was posted shows nothing abnormal which supports my earlier statement that the issues you are experiencing are external to moOde software.

Apologies, I have updated the code above with the full output.

I agree that what you're saying is possible but that would mean that the external issue happened the same day that I updated to 7.0.1 - unlikely.

Only way to know for sure is to go back to 6.7.1 for a while and see how that goes.

Thanks.
Reply
(02-02-2021, 02:03 PM)Rees86 Wrote:
(01-31-2021, 12:45 AM)TheOldPresbyope Wrote: @Rees86 


Code:
20201223 083541 worker: Pri DNS (::1)


What's up with this? Although the Raspberry Pi OS supports IPv6, moOde doesn't make any explicit use of it (and not all of its functions are guaranteed to work in the face of it).

Something is telling moOde to use an internal IPv6 DNS resolver ('::1' is the localhost loopback address in IPv6).

Regards,
Kent

Hi Kent, that was just the clue I needed to fix the issue!  I turned IPv6 off in my gateway and now the issue is gone.  Doesn't fix the underlying issue but at least I don't need to mess around with the Moode installation to get it working.

(01-31-2021, 01:24 AM)Tim Curtis Wrote: Whenever Corporate networks are involved don't expect to get a free ride to the Public internet from your unapproved Raspberry Pi host, lol

The OP post though suggests that it's not necessarily a locked down Corporate network, hard to tell from the post.

Hi Tim, luckily it's not much of a corporate network.  I'm one of the owners and also the IT / Windows / Network admin so I was able to go into our gateway and turn off IPv6 assignment.  

Thanks the quick responses from both of you!
Rees

Glad to hear you found an easy fix but ..."also the IT / Windows / Network admin"...poor you! Big Grin

Regards,
Kent
Reply
(02-02-2021, 12:52 PM)lamode Wrote: A new problem just popped up today. I have been trying out Moode as a player for the past week, and not just a UPnP service. Today I started to play an album but when I return to moode.local I get this screen:

[Image: 1DL8gAz.jpg]

The music is still playing but I can't see or control anything.

I was getting the same thing happening to me - running the latest version of Edge on Windows 10.  Seemed to happen when I left the browser window open for several days.  Try closing browser and re-opening, and if that doesn't work maybe clear browser cache?
Reply
(02-02-2021, 01:33 PM)Mark Dirac Wrote:
(01-03-2021, 05:20 PM)rjorstad Wrote: I recently upgraded to version 7.0.1 and it seems to work fine, however none of the cover art is displayed in the player.  I use BubbleUPnP  via android phone/tablet to stream Qobuz, using Moode as the renderer.  Never had this issue with the previous version of Moode.  Is there a setting that I missed when setting up version 7?

Me too. Some detail:
  • The playlist doesn't advance from track to track.
  • The playlist in moOde only ever contains one track
  • The transport bar in BUPP (mostly) doesn't show progress through the track - stuck at 00:00
  • Album art of now-playing track doesn't appear in moOde
  • Tracks mostly (but not always) do not begin playing immediately, but lag for ~5 seconds
With both moOde 5.3.1 and 6.4.0 none of these issues ever happened - a full playlist appeared in moOde, with album art, and track began playing immediately (<0.5 second)

System - Qobuz to USBridge Sig to RME ADI-2 DAC FS controlled by Bubble UPnP on Android tablet. moOde 7.0.1  No changes in moOde 7.0.1 from default, other than MPD's UPnP is enabled (and DLNA, Spotify etc. is disabled)

If anyone is interested in this bug/disappointment, I am happy to post logs.  moodeutl -l?   cat /var/log/mpd/log?

Try using the OpenHome renderer (menu/configure/audio - scroll to UPnP/DNLA - press edit)
Reply
(02-03-2021, 11:41 AM)the_bertrum Wrote:
(02-02-2021, 01:33 PM)Mark Dirac Wrote:
(01-03-2021, 05:20 PM)rjorstad Wrote: I recently upgraded to version 7.0.1 and it seems to work fine, however none of the cover art is displayed in the player.  I use BubbleUPnP  via android phone/tablet to stream Qobuz, using Moode as the renderer.  Never had this issue with the previous version of Moode.  Is there a setting that I missed when setting up version 7?

Me too. Some detail:
  • The playlist doesn't advance from track to track.
  • The playlist in moOde only ever contains one track
  • The transport bar in BUPP (mostly) doesn't show progress through the track - stuck at 00:00
  • Album art of now-playing track doesn't appear in moOde
  • Tracks mostly (but not always) do not begin playing immediately, but lag for ~5 seconds
With both moOde 5.3.1 and 6.4.0 none of these issues ever happened - a full playlist appeared in moOde, with album art, and track began playing immediately (<0.5 second)

System - Qobuz to USBridge Sig to RME ADI-2 DAC FS controlled by Bubble UPnP on Android tablet. moOde 7.0.1  No changes in moOde 7.0.1 from default, other than MPD's UPnP is enabled (and DLNA, Spotify etc. is disabled)

If anyone is interested in this bug/disappointment, I am happy to post logs.  moodeutl -l?   cat /var/log/mpd/log?

Try using the OpenHome renderer (menu/configure/audio - scroll to UPnP/DNLA - press edit)

Thanks. That worked - but only regarding the issue of the playlist not advancing, not the issue of the OP "Missing cover art".

Why did you suggest that? As a workaround, or because you know of something that has changed in 7.0.1 which might have impacted BubbleUPnP when using UPnP only?
Reply
(02-02-2021, 01:33 PM)Mark Dirac Wrote:
(01-03-2021, 05:20 PM)rjorstad Wrote: I recently upgraded to version 7.0.1 and it seems to work fine, however none of the cover art is displayed in the player.  I use BubbleUPnP  via android phone/tablet to stream Qobuz, using Moode as the renderer.  Never had this issue with the previous version of Moode.  Is there a setting that I missed when setting up version 7?

Me too. Some detail:
  • The playlist doesn't advance from track to track.
  • The playlist in moOde only ever contains one track
  • The transport bar in BUPP (mostly) doesn't show progress through the track - stuck at 00:00
  • Album art of now-playing track doesn't appear in moOde
  • Tracks mostly (but not always) do not begin playing immediately, but lag for ~5 seconds
With both moOde 5.3.1 and 6.4.0 none of these issues ever happened - a full playlist appeared in moOde, with album art, and track began playing immediately (<0.5 second)

System - Qobuz to USBridge Sig to RME ADI-2 DAC FS controlled by Bubble UPnP on Android tablet. moOde 7.0.1  No changes in moOde 7.0.1 from default, other than MPD's UPnP is enabled (and DLNA, Spotify etc. is disabled)

If anyone is interested in this bug/disappointment, I am happy to post logs.  moodeutl -l?   cat /var/log/mpd/log?
Yes, I have experienced this with v7.0.1. Before I read this post, I thought the problem was in my Android tablet side. I remember in moode ver 6.7.1, I would see a couple of songs on the queue waiting for playing and the queue would be updated as time passed. Now, version 7.0.1 only shows the song being playing and it will stop after the end of the current song.
Reply


Forum Jump: