Official moOde 6.6.0 support thread

[Blixa]

Could be. Are you using a stock moOde 6.6.0 image?

Yes Tim.
I used a fresh image and it's ok now.. Ii was strange that same issue in 2 different SD, maybe a problem in NAS, i don't know..
Quick question: in future could be available an option to save added radio url and covers. in order to upload easily in new versions or fresh image?
Thanks for support

[Tim Curtis]

Import/Export stations is part of 6.6.0. Click the gear icon in Radio view

[Tim Curtis]

Just noticed that I was no longer scrobbling, so I looked and from what I could see mpdas had exited. I could not find anything in any of the logs. Starting it back up (in detached mode) works fine for now.

Had a scrobbling hickup today as well. Switched back to the 32-bit kernel to check if it'd happen again — all good so far.

I’ve been on the 32-bit kernel for days now. Just checking again and I can now see it exited again three hours ago.

That component is pretty old and doesn't look like its actively maintained anymore.
https://github.com/hrkfdn/mpdas

[Blixa]

Import/Export stations is part of 6.6.0. Click the gear icon in Radio view

Nice! thanks..

[Martin951]

no luck on the D802C Pro with latest Moode so far - none of Pi3/4 with 6.6.0 works

Pi4

moOde release        = 6.6.0 2020-07-09
RaspiOS            = 10.4
Linux kernel        = 5.4.49-v7l+ #1323
Platform        = Pi-4B 2GB v1.1
Architecture        = armv7l (32-bit)
System uptime        = up 8 minutes
Timezone        = Europe/Amsterdam
Current time        = 2020-07-18 14:31:21

Clean 6.6.0 image installed

pi@keukenTest:~ $ cat /proc/asound/cards
 0 [Headphones     ]: bcm2835_headphonbcm2835 Headphones - bcm2835 Headphones
                      bcm2835 Headphones
 1 [DACX6          ]: USB-Audio - DAC-X6
                      DAC-X6 DAC-X6 at usb-0000:01:00.0-1.2, full speed
--> Works


pi@keukenTest:~ $ cat /proc/asound/cards
 0 [Headphones     ]: bcm2835_headphonbcm2835 Headphones - bcm2835 Headphones
                      bcm2835 Headphones
 1 [FXD802C        ]: USB-Audio - FX-D802C
                      FXAUDIO FX-D802C at usb-0000:01:00.0-1.2, high speed
--> Doesnt work



Pi3

moOde release        = 6.6.0 2020-07-09
RaspiOS            = 10.3
Linux kernel        = 5.4.49-v7+ #1323
Platform        = Pi-3B+ 1GB v1.3
Architecture        = armv7l (32-bit)
System uptime        = up 1 day, 22 hours, 29 minutes
Timezone        = Europe/Amsterdam
Current time        = 2020-07-18 14:42:15

Upgraded from 6.5.2

pi@moode:~ $ cat /proc/asound/cards
 0 [Headphones     ]: bcm2835_headphonbcm2835 Headphones - bcm2835 Headphones
                      bcm2835 Headphones
 1 [DACX6          ]: USB-Audio - DAC-X6
                      DAC-X6 DAC-X6 at usb-3f980000.usb-1.1.3, full speed
--> Works


pi@moode:~ $ cat /proc/asound/cards
 0 [Headphones     ]: bcm2835_headphonbcm2835 Headphones - bcm2835 Headphones
                      bcm2835 Headphones
 1 [FXD802C        ]: USB-Audio - FX-D802C
                      FXAUDIO FX-D802C at usb-3f980000.usb-1.1.2, high speed

--> Doesnt work

[Martin951]

hi, I just upgraded my 2 RPi's to 6.6.0 but unfortunately the RPi4 is only giving sort of random beep noise through the USB DAC and nothing simple like restart or changing USB ports helps. RPi4 worked fine on 6.5.2 (which was my first install of Moode)

So far my experience with Moode was just fantastic so I (and my wife) hope that we soon have Moode in the kitchen again!


RPi4 --> FX-Audio D802C Pro USB input: strange beep random noise (USB sound card option is there and selected)

RPi3 --> FX-Audio DAC-X6 USB input working fine

Hi, Martin.

So have you tried simply swapping the two DACs between the RPi3B and the RPi4B to see if this issue is DAC specific or RPi model specific?

...
/var/log/messages
Jul 16 18:44:49 keuken kernel: [ 1247.242476] usb 1-1.1: new high-speed USB device number 6 using xhci_hcd
Jul 16 18:44:49 keuken kernel: [ 1247.421305] usb 1-1.1: config 1 has an invalid interface number: 255 but max is 2
Jul 16 18:44:49 keuken kernel: [ 1247.421322] usb 1-1.1: config 1 has no interface number 2
Jul 16 18:44:49 keuken kernel: [ 1247.422344] usb 1-1.1: New USB device found, idVendor=0d8c, idProduct=0158, bcdDevice= 0.08
Jul 16 18:44:49 keuken kernel: [ 1247.422363] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jul 16 18:44:49 keuken kernel: [ 1247.422385] usb 1-1.1: Product: FX-D802C
Jul 16 18:44:49 keuken kernel: [ 1247.422400] usb 1-1.1: Manufacturer: FXAUDIO
Jul 16 18:44:49 keuken mtp-probe: checking bus 1, device 6: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1"
Jul 16 18:44:49 keuken mtp-probe: bus: 1, device: 6 was not an MTP device
Jul 16 18:44:49 keuken kernel: [ 1247.465121] input: FXAUDIO FX-D802C Consumer Control as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1/1-1.1:1.255/0003:0D8C:0158.0004/input/input6
Jul 16 18:44:49 keuken kernel: [ 1247.533198] input: FXAUDIO FX-D802C as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1/1-1.1:1.255/0003:0D8C:0158.0004/input/input7
Jul 16 18:44:49 keuken kernel: [ 1247.533691] hid-generic 0003:0D8C:0158.0004: input,hiddev96,hidraw0: USB HID v1.11 Device [FXAUDIO FX-D802C] on usb-0000:01:00.0-1.1/input255
Jul 16 18:45:20 keuken mtp-probe: checking bus 1, device 6: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1"
Jul 16 18:45:20 keuken mtp-probe: bus: 1, device: 6 was not an MTP device

Some of this is expected, notably the "was not an MTP device" shows up for any USB device which isn't, like a generic USB Disk Enclosure I have plugged in, and not suspicious.

The "config 1" business, however, isn't something I've seen with my USB DACs. That's why I'm curious to know if it shows up on the RPi3B.

Regards,
Kent

so I replied just yet apparently with a new post, anyway.. on the D802C Pro, Pi3/4 with 6.6.0 both dont work

/var/log/messages output on Pi3:

Jul 18 14:46:45 moode kernel: [    3.106712] usb 1-1: New USB device found, idVendor=0424, idProduct=2514, bcdDevice= b.b3
Jul 18 14:46:45 moode kernel: [    3.111542] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 18 14:46:45 moode kernel: [    3.114874] hub 1-1:1.0: USB hub found
Jul 18 14:46:45 moode kernel: [    3.117770] hub 1-1:1.0: 4 ports detected
Jul 18 14:46:45 moode kernel: [    3.436460] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
Jul 18 14:46:45 moode kernel: [    3.566731] usb 1-1.1: New USB device found, idVendor=0424, idProduct=2514, bcdDevice= b.b3
Jul 18 14:46:45 moode kernel: [    3.572388] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 18 14:46:45 moode kernel: [    3.576050] hub 1-1.1:1.0: USB hub found
Jul 18 14:46:45 moode kernel: [    3.579092] hub 1-1.1:1.0: 3 ports detected
Jul 18 14:46:45 moode kernel: [    3.896464] usb 1-1.1.2: new high-speed USB device number 4 using dwc_otg
Jul 18 14:46:45 moode kernel: [    4.075292] usb 1-1.1.2: config 1 has an invalid interface number: 255 but max is 2
Jul 18 14:46:45 moode kernel: [    4.078234] usb 1-1.1.2: config 1 has no interface number 2
Jul 18 14:46:45 moode kernel: [    4.082022] usb 1-1.1.2: New USB device found, idVendor=0d8c, idProduct=0158, bcdDevice= 0.08
Jul 18 14:46:45 moode kernel: [    4.087873] usb 1-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jul 18 14:46:45 moode kernel: [    4.090874] usb 1-1.1.2: Product: FX-D802C
Jul 18 14:46:45 moode kernel: [    4.093758] usb 1-1.1.2: Manufacturer: FXAUDIO
Jul 18 14:46:45 moode kernel: [    4.101931] input: FXAUDIO FX-D802C Consumer Control as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.255/0003:0D8C:0158.0001/input/input0
Jul 18 14:46:45 moode rsyslogd: imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) from systemd.  [v8.1901.0]
Jul 18 14:46:45 moode kernel: [    4.176708] input: FXAUDIO FX-D802C as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.255/0003:0D8C:0158.0001/input/input1
Jul 18 14:46:45 moode kernel: [    4.183323] hid-generic 0003:0D8C:0158.0001: input,hiddev96,hidraw0: USB HID v1.11 Device [FXAUDIO FX-D802C] on usb-3f980000.usb-1.1.2/input255
Jul 18 14:46:45 moode kernel: [    4.368668] NET: Registered protocol family 10
Jul 18 14:46:45 moode kernel: [    4.373054] Segment Routing with IPv6
Jul 18 14:46:45 moode kernel: [    4.496450] usb 1-1.1.1: new high-speed USB device number 5 using dwc_otg
Jul 18 14:46:45 moode rsyslogd:  [origin software="rsyslogd" swVersion="8.1901.0" x-pid="329" x-info="https://www.rsyslog.com"] start
Jul 18 14:46:45 moode kernel: [    4.627244] usb 1-1.1.1: New USB device found, idVendor=0424, idProduct=7800, bcdDevice= 3.00
Jul 18 14:46:45 moode kernel: [    4.634172] usb 1-1.1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 18 14:46:45 moode kernel: [    4.909209] lan78xx 1-1.1.1:1.0 (unnamed net_device) (uninitialized): No External EEPROM. Setting MAC Speed
Jul 18 14:46:45 moode kernel: [    4.916872] libphy: lan78xx-mdiobus: probed
Jul 18 14:46:45 moode kernel: [    5.033198] lan78xx 1-1.1.1:1.0 (unnamed net_device) (uninitialized): int urb period 64
Jul 18 14:46:45 moode kernel: [    5.418561] random: systemd: uninitialized urandom read (16 bytes read)
Jul 18 14:46:45 moode kernel: [    5.667637] random: systemd: uninitialized urandom read (16 bytes read)
Jul 18 14:46:45 moode kernel: [    5.682027] random: systemd: uninitialized urandom read (16 bytes read)

[Tim Curtis]

USB audio devices are handled by a single universal USB audio driver and a "quirks" file that contains special settings for various USB audio chipsets. The driver and quirks file are compiled into the Linux kernel.

is there a product link that states the device is compatible with Linux?

[hestehandler]

Just noticed that I was no longer scrobbling, so I looked and from what I could see mpdas had exited. I could not find anything in any of the logs. Starting it back up (in detached mode) works fine for now.

Had a scrobbling hickup today as well. Switched back to the 32-bit kernel to check if it'd happen again — all good so far.

I’ve been on the 32-bit kernel for days now. Just checking again and I can now see it exited again three hours ago.

That component is pretty old and doesn't look like its actively maintained anymore.
https://github.com/hrkfdn/mpdas

Then I suggest replacing it with https://github.com/MusicPlayerDaemon/mpdscribble I’ve run it on my previous MPD setup as a service without problems, and it is under the MPD-project umbrella.

BTW: I ran MPDAS with som logging waiting for it to fail, and it only took ~15 min. for that to happen. Here is the snippet:

Code:

(15:25:05) [INFO] Updated "Now Playing" status successfully.
(15:27:06) [INFO] Scrobbling: Japan - The Experience of Swimming
(15:27:06) [INFO] Scrobbled successfully.
(15:29:09) [INFO] New song: Japan - The Width of a Room
(15:29:11) [ERROR] Last.fm returned an error while updating the currently playing track:
<?xml version="1.0" encoding="UTF-8"?>
<lfm status="failed">
 <error code="4">Authentication Failed - You do not have permissions to access the service</error>
</lfm>

(15:29:11) [ERROR] Code: 4
(15:29:11) [ERROR] Authentication failed. Please check your login data.
(15:29:11) [INFO] Closing mpdas.

So yeah, don’t spend time on MPDAS and let’s get MPDSCRIBBLE integrated instead.

[Tim Curtis]

That could work. I don't have time to do the integration but if another dev wants to volunteer their time to develop, test and create a PR I'll be happy to work with them :-)

[hestehandler]

That could work. I don't have time to do the integration but if another dev wants to volunteer their time to develop, test and create a PR I'll be happy to work with them :-)

I’m sorry, but you should probably hold the horses. I’ve just installed mpdscribble, and this gives the same result. I can see that both MPDAS and MPDSCRIBBLE are using the deprecated 1.2.X protocol, and when Last.FM will (already have?) turn that service off is not documented. The current API is version 2.0 (already some years old). It needs user authentication on installation of clients and uses XLM – so a complete re-write of the scrobbler service is needed for this to work.

So either Last.FM had a server hosting the legacy 1.2 system fail (very likely), or they have shut it down without informing the outside world (also very likely).

Alas.