(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
@
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
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.
(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.
(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!
Regards,
Kent
(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:
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?
(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)
(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?
(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.