+- Moode Forum (https://moodeaudio.org/forum)
+-- Forum: moOde audio player (https://moodeaudio.org/forum/forumdisplay.php?fid=3)
+--- Forum: Support (https://moodeaudio.org/forum/forumdisplay.php?fid=7)
+--- Thread: Official moOde 8 support thread (/showthread.php?tid=4777)
RE: Official moOde 8 support thread - TheOldPresbyope - 03-21-2022
(03-21-2022, 01:47 AM)hui13 Wrote: Anyone tried Bluetooth functionality. Running 8.01 on RPI3B+ and getting following screen after scan. Same behaviour from terminal. Not the same behaviour that I had with 7.6.1 which worked as expected.
I can confirm.
@Tim Curtis
The information returned by bluetoothctl scan on seem to have changed between buster and bullseye. Sigh.
Regards,
Kent
RE: Overlay issue? - Marrahm - 03-21-2022
8.0.01..
RE: Official moOde 8 support thread - the_bertrum - 03-21-2022
(03-21-2022, 12:31 PM)TheOldPresbyope Wrote:(03-21-2022, 01:47 AM)hui13 Wrote: Anyone tried Bluetooth functionality. Running 8.01 on RPI3B+ and getting following screen after scan. Same behaviour from terminal. Not the same behaviour that I had with 7.6.1 which worked as expected.
I can confirm.
@Tim Curtis
The information returned by bluetoothctl scan on seem to have changed between buster and bullseye. Sigh.
Regards,
Kent
I find that the device name appears in the list correctly if the device in question has a previous pairing that was initiated from the other device. Also, repeating the scan over and over will sometimes show device name on my system (where the other devices happens to be other moOde bluetooth radios).
RE: Official moOde 8 support thread - Tim Curtis - 03-21-2022
(03-21-2022, 12:31 PM)TheOldPresbyope Wrote:(03-21-2022, 01:47 AM)hui13 Wrote: Anyone tried Bluetooth functionality. Running 8.01 on RPI3B+ and getting following screen after scan. Same behaviour from terminal. Not the same behaviour that I had with 7.6.1 which worked as expected.
I can confirm.
@Tim Curtis
The information returned by bluetoothctl scan on seem to have changed between buster and bullseye. Sigh.
Regards,
Kent
I get this which seems pretty normal. IIRC sometimes the scan has to be run multiple times before names start appearing in the list.
[attachment=2737]
I also ran bluetoothctl in SSH feeding it the commands from moOde bt.sh script and got similar results.
Code:
pi@moode:~ $ sudo bluetoothctl
Agent registered
[CHG] Controller B8:27:EB:46:EC:18 Pairable: yes
[bluetooth]# scan on
Discovery started
[CHG] Controller B8:27:EB:46:EC:18 Discovering: yes
[NEW] Device 21:4C:AF:7E:C5:D0 21-4C-AF-7E-C5-D0
[NEW] Device 53:C1:EA:94:62:29 Google Display
[NEW] Device 11:E0:BA:4E:5D:00 11-E0-BA-4E-5D-00
[CHG] Device D8:1C:79:A8:55:24 RSSI: -54
[CHG] Device D8:1C:79:A8:55:24 TxPower: 12
[NEW] Device 28:FF:3C:8B:E8:59 28-FF-3C-8B-E8-59
[NEW] Device 48:69:18:19:BE:8A 48-69-18-19-BE-8A
[NEW] Device F0:B3:EC:0A:F7:B1 F0-B3-EC-0A-F7-B1
[NEW] Device 76:E0:F1:5B:83:27 76-E0-F1-5B-83-27
[NEW] Device 17:2E:6F:0B:2C:74 17-2E-6F-0B-2C-74
[NEW] Device 77:CF:83:AE:F6:3C 77-CF-83-AE-F6-3C
[NEW] Device C8:69:CD:15:1F:EE C8-69-CD-15-1F-EE
[NEW] Device 67:AA:6B:06:2F:3C Jabra Evolve2 85
[NEW] Device A4:77:58:09:EE:C8 Anker SoundCore
[CHG] Device 11:E0:BA:4E:5D:00 RSSI: -82
[NEW] Device 79:C9:8B:D1:01:7A 79-C9-8B-D1-01-7A
[NEW] Device 47:A9:E5:F1:2C:96 47-A9-E5-F1-2C-96
[NEW] Device 63:27:B8:5E:BC:DD 63-27-B8-5E-BC-DD
[bluetooth]# scan off
Discovery stopped
[CHG] Device 63:27:B8:5E:BC:DD TxPower is nil
[CHG] Device 63:27:B8:5E:BC:DD RSSI is nil
[CHG] Device 47:A9:E5:F1:2C:96 TxPower is nil
[CHG] Device 47:A9:E5:F1:2C:96 RSSI is nil
[CHG] Device 79:C9:8B:D1:01:7A TxPower is nil
[CHG] Device 79:C9:8B:D1:01:7A RSSI is nil
[CHG] Device A4:77:58:09:EE:C8 TxPower is nil
[CHG] Device A4:77:58:09:EE:C8 RSSI is nil
[CHG] Device 67:AA:6B:06:2F:3C RSSI is nil
[CHG] Device C8:69:CD:15:1F:EE TxPower is nil
[CHG] Device C8:69:CD:15:1F:EE RSSI is nil
[CHG] Device 77:CF:83:AE:F6:3C TxPower is nil
[CHG] Device 77:CF:83:AE:F6:3C RSSI is nil
[CHG] Device 17:2E:6F:0B:2C:74 RSSI is nil
[CHG] Device 76:E0:F1:5B:83:27 RSSI is nil
[CHG] Device F0:B3:EC:0A:F7:B1 TxPower is nil
[CHG] Device F0:B3:EC:0A:F7:B1 RSSI is nil
[CHG] Device 48:69:18:19:BE:8A TxPower is nil
[CHG] Device 48:69:18:19:BE:8A RSSI is nil
[CHG] Device 28:FF:3C:8B:E8:59 TxPower is nil
[CHG] Device 28:FF:3C:8B:E8:59 RSSI is nil
[CHG] Device D8:1C:79:A8:55:24 TxPower is nil
[CHG] Device D8:1C:79:A8:55:24 RSSI is nil
[CHG] Device 11:E0:BA:4E:5D:00 RSSI is nil
[CHG] Device 53:C1:EA:94:62:29 RSSI is nil
[CHG] Device 21:4C:AF:7E:C5:D0 RSSI is nil
[CHG] Controller B8:27:EB:46:EC:18 Discovering: no
[bluetooth]# quit
pi@moode:~ $ sudo bluetoothctl
Agent registered
[CHG] Controller B8:27:EB:46:EC:18 Pairable: yes
[bluetooth]# devices
Device 63:27:B8:5E:BC:DD 63-27-B8-5E-BC-DD
Device 47:A9:E5:F1:2C:96 47-A9-E5-F1-2C-96
Device 79:C9:8B:D1:01:7A 79-C9-8B-D1-01-7A
Device A4:77:58:09:EE:C8 Anker SoundCore
Device 67:AA:6B:06:2F:3C Jabra Evolve2 85
Device C8:69:CD:15:1F:EE C8-69-CD-15-1F-EE
Device 77:CF:83:AE:F6:3C 77-CF-83-AE-F6-3C
Device 17:2E:6F:0B:2C:74 17-2E-6F-0B-2C-74
Device 76:E0:F1:5B:83:27 76-E0-F1-5B-83-27
Device F0:B3:EC:0A:F7:B1 F0-B3-EC-0A-F7-B1
Device 48:69:18:19:BE:8A 48-69-18-19-BE-8A
Device 28:FF:3C:8B:E8:59 28-FF-3C-8B-E8-59
Device 11:E0:BA:4E:5D:00 11-E0-BA-4E-5D-00
Device 53:C1:EA:94:62:29 Google Display
Device 21:4C:AF:7E:C5:D0 21-4C-AF-7E-C5-D0
Device D8:1C:79:A8:55:24 Tim’s iPhone
[bluetooth]# quit
pi@moode:~ $I did notice in the bt.sh script the SCAN() function which uses expect is looking for the wrong responses from the "scan on" and "scan off" commands. It won't affect the scan results but I'll fix it for upcoming 8.0.2 bug fix release.
Code:
pi@moode:~ $ sudo /var/www/command/bt.sh -s
** Scanning for devices (20 secs)
**
** Trusted devices
** A4:77:58:09:EE:C8 Anker SoundCore
** 47:A9:E5:F1:2C:96 47-A9-E5-F1-2C-96
** C8:69:CD:15:1F:EE C8-69-CD-15-1F-EE
** 19:E4:84:03:62:C6 19-E4-84-03-62-C6
** F0:B3:EC:0A:F7:B1 F0-B3-EC-0A-F7-B1
** 11:E0:BA:4E:5D:00 11-E0-BA-4E-5D-00
** 46:21:85:41:25:7F Echo Dot-4WH
** 53:C1:EA:94:62:29 53-C1-EA-94-62-29
** 76:94:DF:8F:BD:CD 76-94-DF-8F-BD-CD
** 28:FF:3C:8B:E8:59 28-FF-3C-8B-E8-59
** 2E:AE:40:0C:24:FF 2E-AE-40-0C-24-FF
** 60:F0:E0:A6:A4:F3 Jabra Evolve2 85
** D8:1C:79:A8:55:24 Tim’s iPhone
**
** Scan complete
pi@moode:~ $ RE: Overlay issue? - Marrahm - 03-21-2022
(03-21-2022, 05:33 AM)JanneP Wrote:Confirmed, Thanks Janne! Nice work.(03-20-2022, 10:45 PM)Tim Curtis Wrote:(03-20-2022, 10:19 PM)Marrahm Wrote: Pi with the HifiBerry HD DAC. Everything worked perfectly under M7 using Tim’s overlay fix. But using same overlay and config in v8 gives me an ALSA error:
Failed to open "ALSA Default" (alsa); Failed to open ALSA device "_audioout": No such file or directory
Which log should I be looking into for clues?
I don’t know if this is relevant or not, but I swear v7 did not call the HD DAC an I2S dac, but v8 seems to automatically select that when I select the proper overlay.
Thanks,
Mike
Version 8.0.0 or 8.0.1 ?
Works here with the version 8.0.1, but need one change in config.txt
Disable the onboard EEPROM by adding
force_eeprom_read=0
to your boot/config.txt file.
See the last comments:
https://github.com/raspberrypi/linux/issues/4898
FYI, put this line at the end of the config file in the [all] segment. Didn’t work originally when i put in another section.
Mike
RE: Overlay issue? - Tim Curtis - 03-21-2022
(03-21-2022, 05:33 AM)JanneP Wrote:(03-20-2022, 10:45 PM)Tim Curtis Wrote:(03-20-2022, 10:19 PM)Marrahm Wrote: Pi with the HifiBerry HD DAC. Everything worked perfectly under M7 using Tim’s overlay fix. But using same overlay and config in v8 gives me an ALSA error:
Failed to open "ALSA Default" (alsa); Failed to open ALSA device "_audioout": No such file or directory
Which log should I be looking into for clues?
I don’t know if this is relevant or not, but I swear v7 did not call the HD DAC an I2S dac, but v8 seems to automatically select that when I select the proper overlay.
Thanks,
Mike
Version 8.0.0 or 8.0.1 ?
Works here with the version 8.0.1, but need one change in config.txt
Disable the onboard EEPROM by adding
force_eeprom_read=0
to your boot/config.txt file.
See the last comments:
https://github.com/raspberrypi/linux/issues/4898
The commit to kernel 5.15.25 makes no mention of needing this command in confix.txt.
https://github.com/raspberrypi/linux/pull/4904
Is there a post in the Hifiberry Forum that can be referenced?
Also @Marrahm, you posted about the "DAC HD" (not the 2) giving an ALSA error. Is this a separate issue or were you actually referring to the "DAC 2 HD"?
-Tim
RE: Official moOde 8 support thread - Tim Curtis - 03-21-2022
(03-21-2022, 11:13 AM)s_mury Wrote: Hi all,
I am having problems generating my library. It takes quite some minutes for the busy indicator to stop but there is still no music in the library. The thumbnail generation process seems to be working because I can see what it is doing using the View Status button. That also means it is not the NAS, which I also confirmed by going to the mount point on the pi.
If I use the update library command, I can see empty album folders appearing in the folder view but with no files in them.
Looking in the MPD log, I see file not found messages but the file is there in the mount folder. I can post logs this evening.
This may have been occurring before I updated to moode 8.0.1. It was my reason for updating but I didn't check it so extensively before the update.
The test sound file works.
Could you please advise how to troubleshoot this and which logs I should post?
Best wishes
Sean
Errors in the MPD log such as "File not found" can result from insufficient permissions on the file and all the containing directories.
MPD needs read permission to the files and read+execute permissions to all the parent directories.
https://mpd.readthedocs.io/en/latest/user.html?highlight=permission#i-can-t-see-my-music-in-the-mpd-database
RE: Official moOde 8 support thread - Tim Curtis - 03-21-2022
(03-21-2022, 02:06 PM)the_bertrum Wrote:(03-21-2022, 12:31 PM)TheOldPresbyope Wrote:(03-21-2022, 01:47 AM)hui13 Wrote: Anyone tried Bluetooth functionality. Running 8.01 on RPI3B+ and getting following screen after scan. Same behaviour from terminal. Not the same behaviour that I had with 7.6.1 which worked as expected.
I can confirm.
@Tim Curtis
The information returned by bluetoothctl scan on seem to have changed between buster and bullseye. Sigh.
Regards,
Kent
I find that the device name appears in the list correctly if the device in question has a previous pairing that was initiated from the other device. Also, repeating the scan over and over will sometimes show device name on my system (where the other devices happens to be other moOde bluetooth radios).
Yes, repeating the scan usually helps to get names to appear.
Are you saying the names of the moOde BT speakers don't appear in the list?
It could be a regression or some new config file that needs to be present. The file thats supposed to provide the name is below.
Code:
pi@moode:~ $ cat /etc/machine-info
PRETTY_HOSTNAME=Moode BluetoothRE: Overlay issue? - JanneP - 03-21-2022
(03-21-2022, 02:41 PM)Tim Curtis Wrote:(03-21-2022, 05:33 AM)JanneP Wrote:(03-20-2022, 10:45 PM)Tim Curtis Wrote:(03-20-2022, 10:19 PM)Marrahm Wrote: Pi with the HifiBerry HD DAC. Everything worked perfectly under M7 using Tim’s overlay fix. But using same overlay and config in v8 gives me an ALSA error:
Failed to open "ALSA Default" (alsa); Failed to open ALSA device "_audioout": No such file or directory
Which log should I be looking into for clues?
I don’t know if this is relevant or not, but I swear v7 did not call the HD DAC an I2S dac, but v8 seems to automatically select that when I select the proper overlay.
Thanks,
Mike
Version 8.0.0 or 8.0.1 ?
Works here with the version 8.0.1, but need one change in config.txt
Disable the onboard EEPROM by adding
force_eeprom_read=0
to your boot/config.txt file.
See the last comments:
https://github.com/raspberrypi/linux/issues/4898
The commit to kernel 5.15.25 makes no mention of needing this command in confix.txt.
https://github.com/raspberrypi/linux/pull/4904
Is there a post in the Hifiberry Forum that can be referenced?
Also @Marrahm, you posted about the "DAC HD" (not the 2) giving an ALSA error. Is this a separate issue or were you actually referring to the "DAC 2 HD"?
-Tim
To my knowledge there is no post in the Hifiberry forum for that.
If you check the issue comments, config.txt modification is there.
https://github.com/raspberrypi/linux/issues/4898
RE: Official moOde 8 support thread - the_bertrum - 03-21-2022
(03-21-2022, 02:55 PM)Tim Curtis Wrote: Are you saying the names of the moOde BT speakers don't appear in the list?
They appear, then disappear, then reappear at different tiomes on subsequent scans. This could have been happening for a while, I only ever connect from the remote device rather than scanning and connecting from the Blue-Z interface.