Official moOde 8 support thread

[DRONE7]

Try opening alsamixer and bumping the Master volume a couple of times.

The white noise issue is because the Kali reclocker does not support 24 bit format. The fix IIRC was to set SoX resampling to 32-bit

Correct... and change mode from plughw to Direct and check that both Piano dip-switches (RPI compatibility and HAT) are set to OFF.
This is what works for my Piano 2.1 & Kali with 8.

[swizzle]

It appears that support for sec=ntlm was removed in kernel 5.15.

https://bugzilla.kernel.org/show_bug.cgi?id=215375

Dmesg reports
[12896.209510] bad security option: ntlm
[12896.209526] CIFS: VFS: bad security option: ntlm

Regards,
Phil.

[url=https://bugzilla.kernel.org/show_bug.cgi?id=215375][/url]

Well spotted. I gave up on using disk drives plugged into routers because of the manufacturers' refusal/inability to move beyond SMBv1. 

Phil

yes, that's the problem.
I went back to direct disk connection via usb, it is not worth it to implement a NAS just for the audio files to be played on the raspberry: cables, space occupied, greater complexity, configuration, management, energy consumption, times for switching on and off ...
much simpler and more effective a simple disk attached to the router.

I am disappointed that they have brutally removed support for ntlm;
okay that it is not safe, but what security problems can there be for a disk in a private LAN
mounted in read-only mode and without personal data stored
but only with audio files of which I still have an offline copy?

Moode should share your usb connected audio directory as an smb share which you may accomplishes something similar to your old setup. The Pi has to be online of course though.

[Sunfish]

Try opening alsamixer and bumping the Master volume a couple of times.

The white noise issue is because the Kali reclocker does not support 24 bit format. The fix IIRC was to set SoX resampling to 32-bit

Correct... and change mode from plughw to Direct and check that both Piano dip-switches (RPI compatibility and HAT) are set to OFF.
This is what works for my Piano 2.1 & Kali with 8.

@Tim Curtis and @DRONE7
thanks for your help, I managed to get it working finally. The issue is/was the proper way of configuring.
1. 1st boot
2. select the piano 2.1 dac --> reboot
3. select stereo (in my case) --> reboot
4. MPD settings: Sox enabled to Yes and 32 bit selected --> MPD will restart
5. glb-mclk Enabled --> reboot
6. SSH into moOde and indeed juggle the master volume. Now I had sound on the left and the  right channel
7. Volume type select NULL --> MPD will restart
8. all other settings.

The first time this procedure did not work, but in one of the logs I noticed a remark about mixer:HDMI.
For no logical reason I  made a new image of moOde 8.0.0 and edited the /boot/config.txt. In fact I removed the section [Rpi4], as I'm using a Rpi 3b+ that section has no use.
After this adjustment the above procedure worked. Coincidence or not?
I'm a happy camper now
BTW I did not change from 'plughw' to 'direct' because I want to use the graphfic equalizer to pump up the high tones. In that case "direct" will be circumvented. as per the note in moOde: "NOTE: Crossfeed, Parametric EQ and Graphic EQ output using plughw regardless of this setting"

thanks again

[TheOldPresbyope]

Hello , I think I have a bug to report . I have two Raspberry zero w with Moode . Version 7.6.1 was previously running on both of them. Have now written the one with the latest version. The Zero w also starts in AP mode , but can not longer find my router during the scan. However, routers in my neighborhood are found. The SSID of my Router is "TP-LINK_2B91 " .
My location is germany .

I have a Zero W. 
I'll test later this morning to see what the scan reports in AP mode and whether it finds my Router.

No problem on Zero W listing my 2GHz SSID after a scan. 

On a 3B+ the scan lists both my 2GHz SSID and 5GHz SSID.

Problem solved ! It was actually my router. Since here in Germany the wifi networks are jostling in the lower channels, I switched to channel 12 and had it to myself. This setting worked fine in previous versions of Moode as well. I am currently using channel 8 and my router is found by Moode 8.0.0. I assume that it is due to the new operating system substructure (→ Raspberry Pi OS Lite 11.2).

I don't know what's changed in between releases, but here's what I think is happening. 

There is a regulatory-domain code stored in the kernel. Out of the box, a moOde 8 player here says the value is

Code:

pi@m8zero2w:~ $ iw reg get
global
country US: DFS-FCC
    (2400 - 2483 @ 40), (N/A, 30), (N/A)
    (5150 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
    (5250 - 5350 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
    (5470 - 5730 @ 160), (N/A, 23), (0 ms), DFS
    (5730 - 5850 @ 80), (N/A, 30), (N/A)
    (57240 - 71000 @ 2160), (N/A, 40), (N/A)

phy#0
country 99: DFS-UNSET
    (2402 - 2482 @ 40), (6, 20), (N/A)
    (2474 - 2494 @ 20), (6, 20), (N/A)
    (5140 - 5360 @ 160), (6, 20), (N/A)
    (5460 - 5860 @ 160), (6, 20), (N/A)

In s quick test, this value  doesn't seem to be affected by changing the country (code) in moOde's WiFi settings to, say, Germany (DE). This latter is the value which will be used by the wpa_supplicant code which connects to an existing access point.

Continuing with the Germany setting as an example, my finding suggests to me we could have the situation where moOde is able to connect to access points in the channel range permitted in Germany (1-14*) but will scan for APs only in the channel range permitted in the US. 

*As hinted by Lukesan, the RPi doesn't appear to support channel 14.

@Tim Curtis

Assuming I haven't missed something here, it would seem moOde should use the country set in WiFi Configuration to update the internal regulatory domain code. Quoting from the iw man page

Code:

    reg get
        Print out the kernel's current regulatory domain information.

    reg set <ISO/IEC 3166-1 alpha2>
        Notify the kernel about the current regulatory domain.

By the by, supposedly the file /etc/default/crda contains  a setting REGDOMAIN for iw to use as the initial regulatory domain but in both Raspberry Pi OS and my Linux Mint laptop the value of REGDOMAIN is blank. The kernel must be getting it from somewhere.?.?.

Regards,
Kent

[philrandal]

Hello , I think I have a bug to report . I have two Raspberry zero w with Moode . Version 7.6.1 was previously running on both of them. Have now written the one with the latest version. The Zero w also starts in AP mode , but can not longer find my router during the scan. However, routers in my neighborhood are found. The SSID of my Router is "TP-LINK_2B91 " .
My location is germany .

I have a Zero W. 
I'll test later this morning to see what the scan reports in AP mode and whether it finds my Router.

No problem on Zero W listing my 2GHz SSID after a scan. 

On a 3B+ the scan lists both my 2GHz SSID and 5GHz SSID.

Problem solved ! It was actually my router. Since here in Germany the wifi networks are jostling in the lower channels, I switched to channel 12 and had it to myself. This setting worked fine in previous versions of Moode as well. I am currently using channel 8 and my router is found by Moode 8.0.0. I assume that it is due to the new operating system substructure (→ Raspberry Pi OS Lite 11.2).

I don't know what's changed in between releases, but here's what I think is happening. 

There is a regulatory-domain code stored in the kernel. Out of the box, a moOde 8 player here says the value is

Code:

pi@m8zero2w:~ $ iw reg get
global
country US: DFS-FCC
    (2400 - 2483 @ 40), (N/A, 30), (N/A)
    (5150 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
    (5250 - 5350 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
    (5470 - 5730 @ 160), (N/A, 23), (0 ms), DFS
    (5730 - 5850 @ 80), (N/A, 30), (N/A)
    (57240 - 71000 @ 2160), (N/A, 40), (N/A)

phy#0
country 99: DFS-UNSET
    (2402 - 2482 @ 40), (6, 20), (N/A)
    (2474 - 2494 @ 20), (6, 20), (N/A)
    (5140 - 5360 @ 160), (6, 20), (N/A)
    (5460 - 5860 @ 160), (6, 20), (N/A)

In s quick test, this value  doesn't seem to be affected by changing the country (code) in moOde's WiFi settings to, say, Germany (DE). This latter is the value which will be used by the wpa_supplicant code which connects to an existing access point.

Continuing with the Germany setting as an example, my finding suggests to me we could have the situation where moOde is able to connect to access points in the channel range permitted in Germany (1-14*) but will scan for APs only in the channel range permitted in the US. 

*As hinted by Lukesan, the RPi doesn't appear to support channel 14.

@Tim Curtis

Assuming I haven't missed something here, it would seem moOde should use the country set in WiFi Configuration to update the internal regulatory domain code. Quoting from the iw man page

Code:

    reg get
        Print out the kernel's current regulatory domain information.

    reg set <ISO/IEC 3166-1 alpha2>
        Notify the kernel about the current regulatory domain.

By the by, supposedly the file /etc/default/crda contains  a setting REGDOMAIN for iw to use as the initial regulatory domain but in both Raspberry Pi OS and my Linux Mint laptop the value of REGDOMAIN is blank. The kernel must be getting it from somewhere.?.?.

Regards,
Kent

It may be getting it from the router.

Does the solution suggested here work?

https://storck.io/posts/raspberry-pi-cant-find-my-wifi/

Phil

[Tim Curtis]

Right, setting the wifi country code only makes an update to wpa_supplicant.conf "country=" line.

Maybe check to see what raspi_config does?

[UpsiUps]

I hate the Major version upgrades as I have to walk and find all my RPis in the house, plug th eSD card , burn a new one , plug the new one in and restart configuration ... Oh, last point has a significant improvement : backup and restore !

Excellent! and even a possibility to run my own restore script - more excellent !

I all mention that as there seems a small bug, that I have been faced during my upgrade procedure: I unwraped all backup-zips to grab the unique moodecfg.ini and throw them on the /boot partition. That worked very well and the players came up even with the NAS connected per NFS. I then restored using the zip file the rest.
... and then I had a duplication of my NAS Library as Library source. So it seems that restore adds the library regardless if this is already connected.

Workaround ist fast: just deleted the latest entry of the list. But maybe you want to proof, why the duplication is happening.

[TheOldPresbyope]

Right, setting the wifi country code only makes an update to wpa_supplicant.conf "country=" line.

Maybe check to see what raspi_config does?

Just checked raspi-config (https://github.com/RPi-Distro/raspi-conf...spi-config)

After some prelim to get the two-char country code into $COUNTRY, we find starting at line 609 that iw reg set is used

Code:

 if [ $? -eq 0 ];then
   wpa_cli -i "$IFACE" set country "$COUNTRY"
   wpa_cli -i "$IFACE" save_config > /dev/null 2>&1
   if iw reg set "$COUNTRY" 2> /dev/null; then
     ASK_TO_REBOOT=1
   fi

@philrandal

Interesting find. Yet another place to hide configuration info --- the hallmark of Linux! Out of the box, that file doesn't exist either in moOdeOS (e.g., Raspberry Pi OS) or my Linux Mint laptop but obviously one can define it.

On your first point, I don't see how the country code can be retrieved from the router before the access point has been discovered.

Regards,
Kent

[Tim Curtis]

I hate the Major version upgrades as I have to walk and find all my RPis in the house, plug th eSD card , burn a new one , plug the new one in and restart configuration ... Oh, last point has a significant improvement : backup and restore !

Excellent! and even a possibility to run my own restore script - more excellent !

I all mention that as there seems a small bug, that I have been faced during my upgrade procedure: I unwraped all backup-zips to grab the unique moodecfg.ini and throw them on the /boot partition. That worked very well and the players came up even with the NAS connected per NFS. I then restored using the zip file the rest.
... and then I had a duplication of my NAS Library as Library source. So it seems that restore adds the library regardless if this is already connected.

Workaround ist fast: just deleted the latest entry of the list. But maybe you want to proof, why the duplication is happening.

The Restore handles copying moodecfg.ini to /boot. You don't have to do it manually.

[Tim Curtis]

Right, setting the wifi country code only makes an update to wpa_supplicant.conf "country=" line.

Maybe check to see what raspi_config does?

Just checked raspi-config (https://github.com/RPi-Distro/raspi-conf...spi-config)

After some prelim to get the two-char country code into $COUNTRY, we find starting at line 609 that iw reg set is used

Code:

 if [ $? -eq 0 ];then
   wpa_cli -i "$IFACE" set country "$COUNTRY"
   wpa_cli -i "$IFACE" save_config > /dev/null 2>&1
   if iw reg set "$COUNTRY" 2> /dev/null; then
     ASK_TO_REBOOT=1
   fi

@philrandal

Interesting find. Yet another place to hide configuration info --- the hallmark of Linux! Out of the box, that file doesn't exist either in moOdeOS (e.g., Raspberry Pi OS) or my Linux Mint laptop but obviously one can define it.

On your first point, I don't see how the country code can be retrieved from the router before the access point has been discovered.

Regards,
Kent

I'll add that command to the wifi config code block for upcoming 8.0.1