+- 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 7.1.0 support thread (/showthread.php?tid=3615)
RE: Official moOde 7.1.0 support thread - stefsam - 04-02-2021
Hi,
first of all: Thank You for providing such an incredibly flexible, high quality application!
I've migrated my USBridge mSD-card from 7.0.1 to 7.1 today, and what happens is I can't access the "m - Configure" menu any longer: i.e. when selected, nothing happens. Same for "m - Power".
In order to get into Configuration, I've found a workaround: Select "m - BlueZ", then navigate back to the 4 tabs Library-Audio-Network-System.
BUT: neither #configure-modal, nor #power-modal would work any longer.
Needless to say, I've already rebooted twice, both soft- and hard-; and- tried Chrome, Chromium, Firefox and Safari, same behaviour unfortunately.
Would you have any suggestion on how to restore the standard, lost functionality other than...re-flask the mSD card?
Warm Thanks in advance.
RE: Official moOde 7.1.0 support thread - Pbnmjk - 04-02-2021
@CallMeMike @DRONE7
Thank you both for your time...
I'm using USB 3.0 connection, last night I do more research and the problem happen if I left the system without use for a long time.
If I try to play a new song after 10, 15 or 20 minutes (you have the idea), RAID return from sleep and all fine.
My RAID is a Mercury Pro 1U with 4 WD Black 4TB each.
It works fine with Rune, for example, and I never had an issue like this connected to Bryston BDP, it's a MPD based player also.
I find useless a RAID without sleep mode because, if I'm inmmersed in my job, a lot of time the music stop to play and I don't pay attention.
I like moOde really, for this reason I'm spending my time trying to find a solution.
RE: Official moOde 7.1.0 support thread - TheOldPresbyope - 04-02-2021
@Pbnmjk
Since you are using moOde you are thinking of this issue as a moOde problem but it sounds more like a Raspberry Pi/Raspberry Pi OS problem. All moOde (and even here, mostly MPD) is doing is ask the OS to get or put bytes through the RPi firmware/hardware from/to the disk drive(s).
Perhaps you could ask about it on the Raspberry Pi Forum where the appropriate wizards hang out. If there's some sort of defensive coding practice required to deal with drives in a coma, they'd know what it is.
Regards,
Kent
RE: Official moOde 7.1.0 support thread - Pbnmjk - 04-02-2021
(04-02-2021, 07:56 PM)TheOldPresbyope Wrote: @Pbnmjk@TheOldPresbyope
Since you are using moOde you are thinking of this issue as a moOde problem but it sounds more like a Raspberry Pi/Raspberry Pi OS problem. All moOde (and even here, mostly MPD) is doing is ask the OS to get or put bytes through the RPi firmware/hardware from/to the disk drive(s).
Perhaps you could ask about it on the Raspberry Pi Forum where the appropriate wizards hang out. If there's some sort of defensive coding practice required to deal with drives in a coma, they'd know what it is.
Regards,
Kent
Thank you Kent... I'll try your suggestion
RE: Official moOde 7.1.0 support thread - Pbnmjk - 04-04-2021
@TheOldPresbyope
Well, I did a lot of research and I tried a lot of things, but one issue remains and I don't know how to solve it.
When I reconnect the USB RAID, mo0de don't associate the database with RAID and a new scan is made each time I connect the RAID like I never had it connected before.
For example today I turned ON my RPI4 8GB with RAID connected, it didn't recognize it and I disconnected and reconnected the RAID, but after this, mo0de didn't asume database from the last time it was connected, it start a new scan like this were a new HD.
The same happen if I boot without RAID connected and I connect the RAID after, mo0de start a new scan like this were a new HD.
If mo0de scan the RAID and I remove it and connect it again, no matter the time I take to do it, mo0de recognize USB and start a new scan from zero.
Always forget the database asociate to the RAID.
Some suggestion?
Thank you in advance.
Raspberry Pi 3, moodeaudio 7 and Bluetooth hci0: Frame reassembly failed (-84) - eKroko - 04-04-2021
Hello,
I'm using moodeaudio Version 6.7.1 2020-07-22 with great delight.
(Setup: Raspberry Pi 3 + Hifiberry Amp2, bluetooth renderer)
It works flawlessly with playing local files, using the radio stations and using the bluetooth renderer to stream audio from my mobile device to moodeaudio.
Then I upgraded to Version 7 however when using the bluetooth renderer I received only garbled output and found this (tons of messages) in the syslog:
Bluetooth: hci0: Frame reassembly failed (-84) (lots off them)
Apr 4 10:14:18 moodeog bluealsa[956]: /usr/bin/bluealsa: W: Missing RTP packet: 53 != 48
Apr 4 10:14:18 moodeog bluealsa[956]: /usr/bin/bluealsa: E: SBC decoding error: No such file or directory
...
Apr 4 10:14:19 moodeog kernel: [ 229.197485] Bluetooth: hci0: SCO packet for unknown connection handle 14694
Apr 4 10:14:19 moodeog kernel: [ 229.330068] Bluetooth: hci0: Frame reassembly failed (-84)
Apr 4 10:14:19 moodeog bluealsa[956]: /usr/bin/bluealsa: W: Missing RTP packet: 145 != 144
Apr 4 10:14:19 moodeog bluealsa[956]: /usr/bin/bluealsa: E: SBC decoding error: No such file or directory
I switched back to Version 6.7.1 and everything was fine, I switched forward and had the problem again.
Now I tried version 7.1 again, however the problem remains.
Sound via hifiberry, mp3 playing, radio stations - all fine.
But when I connect via bluetooth, the output is not continuous, every few seconds there is a stop and then a start of the stream resulting in garbled output.
According to a lot of internet articles, this might be correlated to a high load, however
- the same scenario works perfectly/flawless with version 6.7.1
- I could not identify a high load on my Pi while playing bluetooth audio (streaming from mobile to moodeaudio and output via hifiberrry amp2)
One potential difference I see is the bluez - update with version 7
Am I the only one who has these kind of problems?
Any ideas to solve this issue?
RE: Official moOde 7.1.0 support thread - Tim Curtis - 04-04-2021
Quick test with my iPhone and no issues whatsoever with Bluetooth.
RE: Official moOde 7.1.0 support thread - TheOldPresbyope - 04-04-2021
(04-04-2021, 07:12 AM)Pbnmjk Wrote: @TheOldPresbyope
Well, I did a lot of research and I tried a lot of things, but one issue remains and I don't know how to solve it.
When I reconnect the USB RAID, mo0de don't associate the database with RAID and a new scan is made each time I connect the RAID like I never had it connected before.
For example today I turned ON my RPI4 8GB with RAID connected, it didn't recognize it and I disconnected and reconnected the RAID, but after this, mo0de didn't asume database from the last time it was connected, it start a new scan like this were a new HD.
The same happen if I boot without RAID connected and I connect the RAID after, mo0de start a new scan like this were a new HD.
If mo0de scan the RAID and I remove it and connect it again, no matter the time I take to do it, mo0de recognize USB and start a new scan from zero.
Always forget the database asociate to the RAID.
Some suggestion?
Thank you in advance.
What does "it didn't recognize it" mean?
Similarly, what does "moOde start a new scan" mean?
I just wrote a few albums' worth of tracks to a USB Thumbdrive. I plugged it into a moOde 7.1.0 player on an RPi3B+. Here's the activity reported to /var/log/syslog when the drive is detected, analyzed, and mounted by the OS:
Code:
...
Apr 4 11:37:06 710LD kernel: [ 123.885619] usb 1-1.2: new high-speed USB device number 7 using dwc_otg
Apr 4 11:37:07 710LD kernel: [ 124.064683] usb 1-1.2: New USB device found, idVendor=05dc, idProduct=c75c, bcdDevice= 1.06
Apr 4 11:37:07 710LD kernel: [ 124.064695] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Apr 4 11:37:07 710LD kernel: [ 124.064701] usb 1-1.2: Product: USB Flash Drive
Apr 4 11:37:07 710LD kernel: [ 124.064707] usb 1-1.2: Manufacturer: Lexar
Apr 4 11:37:07 710LD kernel: [ 124.064713] usb 1-1.2: SerialNumber: 64BF5CE8D1AF4FF9
Apr 4 11:37:07 710LD kernel: [ 124.065239] usb-storage 1-1.2:1.0: USB Mass Storage device detected
Apr 4 11:37:07 710LD kernel: [ 124.065602] scsi host1: usb-storage 1-1.2:1.0
Apr 4 11:37:07 710LD mtp-probe: checking bus 1, device 7: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2"
Apr 4 11:37:07 710LD mtp-probe: bus: 1, device: 7 was not an MTP device
Apr 4 11:37:07 710LD mtp-probe: checking bus 1, device 7: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2"
Apr 4 11:37:07 710LD mtp-probe: bus: 1, device: 7 was not an MTP device
Apr 4 11:37:08 710LD kernel: [ 125.214743] scsi 1:0:0:0: Direct-Access Lexar USB Flash Drive 8.07 PQ: 0 ANSI: 4
Apr 4 11:37:08 710LD kernel: [ 125.215484] sd 1:0:0:0: Attached scsi generic sg1 type 0
Apr 4 11:37:08 710LD kernel: [ 125.223102] sd 1:0:0:0: [sdb] 31266816 512-byte logical blocks: (16.0 GB/14.9 GiB)
Apr 4 11:37:08 710LD kernel: [ 125.244715] sd 1:0:0:0: [sdb] Write Protect is off
Apr 4 11:37:08 710LD kernel: [ 125.244736] sd 1:0:0:0: [sdb] Mode Sense: 23 00 00 00
Apr 4 11:37:08 710LD kernel: [ 125.245764] sd 1:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Apr 4 11:37:08 710LD kernel: [ 125.389388] sdb: sdb1
Apr 4 11:37:08 710LD kernel: [ 125.392783] sd 1:0:0:0: [sdb] Attached SCSI removable disk
Apr 4 11:37:08 710LD kernel: [ 125.705770] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Apr 4 11:37:08 710LD systemd[1]: Stopping Samba SMB Daemon...
Apr 4 11:37:08 710LD systemd[1]: smbd.service: Main process exited, code=killed, status=15/TERM
Apr 4 11:37:08 710LD systemd[1]: smbd.service: Succeeded.
Apr 4 11:37:08 710LD systemd[1]: Stopped Samba SMB Daemon.
Apr 4 11:37:08 710LD systemd[1]: Starting Samba SMB Daemon...
Apr 4 11:37:09 710LD winbindd[508]: [2021/04/04 11:37:09.030431, 0] ../source3/winbindd/wb_lookupsids.c:659(wb_lookupsids_recv)
Apr 4 11:37:09 710LD winbindd[508]: res_names->count = 3, expected 4
Apr 4 11:37:09 710LD smbd[1799]: [2021/04/04 11:37:09.055131, 0] ../lib/util/become_daemon.c:138(daemon_ready)
Apr 4 11:37:09 710LD smbd[1799]: daemon_ready: STATUS=daemon 'smbd' finished starting up and ready to serve connections
Apr 4 11:37:09 710LD systemd[1]: Started Samba SMB Daemon.
Apr 4 11:37:09 710LD nmbd[479]: [2021/04/04 11:37:09.079812, 0] ../source3/nmbd/nmbd.c:58(terminate)
Apr 4 11:37:09 710LD systemd[1]: Stopping Samba NMB Daemon...
Apr 4 11:37:09 710LD nmbd[479]: Got SIGTERM: going down...
Apr 4 11:37:09 710LD systemd[1]: nmbd.service: Succeeded.
Apr 4 11:37:09 710LD systemd[1]: Stopped Samba NMB Daemon.
Apr 4 11:37:09 710LD systemd[1]: Starting Samba NMB Daemon...
Apr 4 11:37:09 710LD nmbd[1806]: [2021/04/04 11:37:09.236300, 0] ../lib/util/become_daemon.c:138(daemon_ready)
Apr 4 11:37:09 710LD nmbd[1806]: daemon_ready: STATUS=daemon 'nmbd' finished starting up and ready to serve connections
Apr 4 11:37:09 710LD systemd[1]: Started Samba NMB Daemon.
...Next I told moOde to "m>Update library". When this task was done, the albums show up in the Library Folder view under USB and similarly in the Tag and Album views. They play as expected.
I unplugged the thumbdrive and power-cycled the moOde player. With moOde running again, the albums still show up in the various Library views which means the MPD database is intact. Now, of course, they don't play because the drive isn't present. Trying to play a track results in a popup declaring an MPD error.
Finally, I plugged in the thumbdrive again. Now the tracks/albums all play. At no time did my fingers leave my hands (old magician's joke). The database is unchanged and the links it contains point properly into the remounted drive.
If your USB RAID drive is behaving differently then we need a lot more diagnostic data and even then we might not understand or "fix" what's going on. (There's interactions with the kernel, with drivers, with UDEV, etc.)
Regards,
Kent
RE: Official moOde 7.1.0 support thread - Pbnmjk - 04-04-2021
[attachment=2232]
What does "it didn't recognize it" mean?
Similarly, what does "moOde start a new scan" mean?
@TheOldPresbyope
To the first question:
I can see folders with albums and songs from the last regeneration in the Library, but if I try to play a track It didn't play anything if I select play or clear/play, etc option. I can add a track, but if I try to play from player it do nothing.
To the second question:
It is, mo0de made a new regeneration from zero like it never exist before, I can see in the Library how the folders are added from zero.
Today, I did the following:
Turned On RPI4
Check the Library and all RAID music was there.
Connected RAID.
Now I can see all the music in Library, but no track is recognized if I try to play.
I was looking at configure "Library" without do a simple thing and returned to Library and the following message appear, but I can search folders and tracks of RAID in the Library (I added an attachment with an image capure:
MPD error
Failed to open "ALSA Default (alsa);
Failed to open ALSA device "hw:2,0": No such file or directory
RE: Official moOde 7.1.0 support thread - DRONE7 - 04-04-2021
Quote:Today, I did the following:
Turned On RPI4
Check the Library and all RAID music was there.
Connected RAID.
Now I can see all the music in Library, but no track is recognized if I try to play.
I was looking at configure "Library" without do a simple thing and returned to Library and the following message appear, but I can search folders and tracks of RAID in the Library (I added an attachment with an image capure:
MPD error
Failed to open "ALSA Default (alsa);
Failed to open ALSA device "hw:2,0": No such file or directory
You're starting MoOde before you start your NAS/RAID ? would explain the error message. If you are then go to the library tab and select 'Remount Sources' and Yes then check that the green tick appears.
Best if you power on your NAS/RAID before powering on your Pi.
If this does not appear to be the problem/solution then what kernel are you using ? 32 or 64 bit ? as the experimental 64 bit kernel is known to give library misbehaviour so revert to the 32 bit kernel.