It's black, and it's about 0.5cm proud of the USB connector.
The original "nano" version.

That should work, the link describes it as compatible with Raspberry Pi / Pi2. Old skool!

Mine is not the nano version, and I see now it is actually an entirely different model # too, EW-7722UTn.
At 300mbps it has double the bandwidth of that generic one I have, and they describe that extender cable as having a hardwire in it, which is why it doesn't droop at all under the weight of the adapter:

Edimax.jpg

I found my Amazon purchase, August 2016, and they still list/sell that exact package.
 
I finally got around to trying the latest Moode 7.2.1 as a UPnP endpoint for Audirvana Studio (1.2.0). Took about 10 seconds for the dreaded white noise to hit. So it's back to Moode 6.7.1 that was released last July. I notice that the following version of Moode contained a new version of the Upmpdcli - it went from 1.4.x to 1.5.x so it's possible the changes in that client are what broke the functionality.

I still have a suspicion that Audirvana isn't keeping up with this sort of compatibility.
 
The original "nano" version.

That should work, the link describes it as compatible with Raspberry Pi / Pi2. Old skool!

Mine is not the nano version, and I see now it is actually an entirely different model # too, EW-7722UTn.
At 300mbps it has double the bandwidth of that generic one I have, and they describe that extender cable as having a hardwire in it, which is why it doesn't droop at all under the weight of the adapter:

View attachment 36866

I found my Amazon purchase, August 2016, and they still list/sell that exact package.
I've decided I'm going to keep a few different USB WiFi modules (including the generic you mentioned earlier) as that's hella cheaper than getting an electrician in to do a low-voltage drop from my patch panel. Redundant Array of Inexpensive USB WiFi Adapters [RAIUWA] :D
 
Last edited:
I've decided I'm going to keep a few different USB WiFi modules (including the generic you mentioned earlier) as that's hella cheaper than getting an electrician in to do a low-voltage drop from my patch panel. Redundant Array of Inexpensive USB WiFi Adapters [RAIUWA] :D
You mean Redundant Array of Inexpensive USB WiFi Adapters [RAIUWA]™.
 
I still have a suspicion that Audirvana isn't keeping up with this sort of compatibility.
I do too, though my own use with Qobuz on Audirvana seems fine, but certainly the local JRiver server and Moode have no issues at all.
Is this when streaming TIDAL, or from an Audirvana local UPnP server, or both/either?
 
I do too, though my own use with Qobuz on Audirvana seems fine, but certainly the local JRiver server and Moode have no issues at all.
Is this when streaming TIDAL, or from an Audirvana local UPnP server, or both/either?
Both, although this instance was Tidal. Sometimes it wouldn't happen for a while, and trick me into thinking it was fixed on those earlier attempts.
 
Just a post to say I've recently purchased the Pi2AES HAT for the RPi, and am very impressed with the sound of the music coming out, esp. the I2S output into my PS Audio DS Jr. I'm using MoOde, but have also added the Roonbridge as an option to the MoOde renderers. I've been comparing the Pi2AES output to the Sonore Ultrarendu, and can honestly say I can't tell much difference (though my 72 yo ears may be suspect). Over on the SuperBestAudioFriends (SBAF) forum there is a Pi2AES for Dummies thread that is quite informative, and the consensus is that this is a great product. Check it out if you have any interest in the product.
 
Moode Audio Player 7.3.0 is now available as a downloadable disk image, or as an in-place update to existing Moode 7.2.1 instances. The in-place update takes about 2 minutes to complete depending on your network and system speed, after which a restart is required.

This release is based on RaspiOS Buster Lite 10.6 (2020-12-02) and Linux kernel 5.4.77 build #1371.

Code:
########################################################
//
// 2021-06-25 TC moOde 7.3.0
//
########################################################

New features

- NEW: ALSA output modes including Default (plughw) and Direct (hw)
- NEW: Volume normalization and format options for librespot

Updates

- UPD: Bump to MPD 0.22.8
- UPD: Bump to librespot 0.2.0
- UPD: Bump to CamillaDSP 0.5.2, GUI 0.4.1, Backend 0.7.1, Plot 0.5.3
- UPD: Simplify ALSA framework
- UPD: Add verbose debug option to CamillaDSP
- UPD: Run updMpdConf() after in-place update
- UPD: Improve method for updating currentsong.txt
- UPD: Option to turn off Now-playing (EQ bars) icon
- UPD: Option to turn off CoverView Playbar
- UPD: Enable rpi-cirrus-wm5102.dtbo to show in DT overlay list
- UPD: Route Bluetooth through ALSA framework
- UPD: Load i2c-dev at boot time via /etc/modules
- UPD: Set theme-color meta element in header to Theme color
- UPD: Add Output chain and Loopback state to Audio info
- UPD: Improve how MPD Config changes are processed
- UPD: Drop Max USB current (not applicable anymore)
- UPD: BlueZ Config when change to Local, disconnect device

Bug fixes

- FIX: Missing "Roonbridge Active" in currentsong.txt
- FIX: Currentsong.txt truncated at startup
- FIX: Airplay, Spotify renderers crash when ALSA Loopback On
- FIX: DSP confs break when audioout set to Bluetooth
- FIX: Station Home page field not in Audio info
- FIX: Wlan0 power save not disabled during startup for Pi-Zero W
- FIX: Instability in libcurl3 shipped with RaspiOS Buster
- FIX: Permissions on shairport-sync debug log
- FIX: Missing -u option in shairport-sync logging
- FIX: CamillaDSP and 64-bit kernel showing for 32-bit only Pi's
- FIX: WiFi/BT options missing from System config for Zero W
- FIX: Display wakes when USB DAC disconnected if Wake on play ON
- FIX: CamillaDSP Config back link handling

As always, if you are enjoying the use of Moode Audio Player, please consider making a donation on Moodeaudio.org to help ensure the moOde project continues to develop great audio software for the Raspberry Pi audio community.
 
Moode Audio Player 7.3.0 is now available as a downloadable disk image, or as an in-place update to existing Moode 7.2.1 instances. The in-place update takes about 2 minutes to complete depending on your network and system speed, after which a restart is required.

This release is based on RaspiOS Buster Lite 10.6 (2020-12-02) and Linux kernel 5.4.77 build #1371.

Code:
########################################################
//
// 2021-06-25 TC moOde 7.3.0
//
########################################################

New features

- NEW: ALSA output modes including Default (plughw) and Direct (hw)
- NEW: Volume normalization and format options for librespot

Updates

- UPD: Bump to MPD 0.22.8
- UPD: Bump to librespot 0.2.0
- UPD: Bump to CamillaDSP 0.5.2, GUI 0.4.1, Backend 0.7.1, Plot 0.5.3
- UPD: Simplify ALSA framework
- UPD: Add verbose debug option to CamillaDSP
- UPD: Run updMpdConf() after in-place update
- UPD: Improve method for updating currentsong.txt
- UPD: Option to turn off Now-playing (EQ bars) icon
- UPD: Option to turn off CoverView Playbar
- UPD: Enable rpi-cirrus-wm5102.dtbo to show in DT overlay list
- UPD: Route Bluetooth through ALSA framework
- UPD: Load i2c-dev at boot time via /etc/modules
- UPD: Set theme-color meta element in header to Theme color
- UPD: Add Output chain and Loopback state to Audio info
- UPD: Improve how MPD Config changes are processed
- UPD: Drop Max USB current (not applicable anymore)
- UPD: BlueZ Config when change to Local, disconnect device

Bug fixes

- FIX: Missing "Roonbridge Active" in currentsong.txt
- FIX: Currentsong.txt truncated at startup
- FIX: Airplay, Spotify renderers crash when ALSA Loopback On
- FIX: DSP confs break when audioout set to Bluetooth
- FIX: Station Home page field not in Audio info
- FIX: Wlan0 power save not disabled during startup for Pi-Zero W
- FIX: Instability in libcurl3 shipped with RaspiOS Buster
- FIX: Permissions on shairport-sync debug log
- FIX: Missing -u option in shairport-sync logging
- FIX: CamillaDSP and 64-bit kernel showing for 32-bit only Pi's
- FIX: WiFi/BT options missing from System config for Zero W
- FIX: Display wakes when USB DAC disconnected if Wake on play ON
- FIX: CamillaDSP Config back link handling

As always, if you are enjoying the use of Moode Audio Player, please take a moment to consider making a donation on Moodeaudio.org to help ensure the moOde project continues to develop great audio software for the Raspberry Pi audio community.
All my Moode renderers are now updated. :)
 
Moode Audio Player 7.4.0 is now available as a downloadable disk image, or as an in-place update to existing Moode 7.3.0 instances. The in-place update takes about 2 minutes to complete depending on your network and system speed, after which a restart is required.

This release includes important new features, updates and bug fixes including Multiroom Audio, CamillaDSP Quick Select, and Backup/Restore Manager. Please visit the Moode Forum for more information.
Code:
################################################################################
#
# 2021-09-24 TC moOde 7.4.0
#
################################################################################

New features
- NEW: Multiroom audio
- NEW: CamillaDSP Quick Select
- NEW: Backup/restore manager
Updates
- UPD: Bump to MPD 0.22.11
- UPD: Bump to CamillaDSP 0.6.3
- UPD: Bump to upmpdcli 1.5.11
- UPD: Add "okto research dac8 Stereo" to device table
- UPD: Improve memory reporting in System info
- UPD: Add option for Null mixer to MPD Config
- UPD: Add Show tracks option to One touch album
- UPD: Add Album header context menu in tracks list
- UPD: Separate One touch options for Album and Radio
Radio stations
- NEW: Organ Experience
- NEW: SmoothLounge Global
- UPD: 4ZZZ FM 102.1 - Alternative
- UPD: SmoothJazz Global
- UPD: OrganLive.com
- UPD: Positively Baroque
- UPD: Maschinengeist Radio (OFFLINE)
Bug fixes
- FIX: Typo in MPD Config message regarding disconnected device
- FIX: Fallback to encoded_at rate from MPD db if mediainfo reports blank rate
- FIX: CoverView Playbar show/hide not working when launched from Library
- FIX: Typo in cdsp 32b float format (FLOATLE should be FLOAT32LE)
- FIX: BlueZ audioout being set to Bluetooth on Disconnect
- FIX: Web socket get_mute() not working in pycamilladsp.py
- FIX: Various auto-config bugs
- FIX: Console error from Menu, Refresh
- FIX: Margin issue on Clock Radio text and controls
- FIX: Testing for old MPD mixer_type "disabled" in several modules
- FIX: Parsing issue with mixer names containing embedded parenthesis
- FIX: Selective_resample_mode param present in mpd.conf when SoX is off

As always, if you are enjoying the use of Moode Audio Player, please consider making a donation on Moodeaudio.org to help ensure the moOde project continues to develop great audio software for the Raspberry Pi audio community.

moOde.png
 
moOde 7.4.1 is available for download, or as an in-place update to existing 7.4.0 instances. This release offers various bug fixes including a remedy to the BlueZ configuration crashing when connecting to a Bluetooth speaker. Please visit the Moode forum for more information.
 
moOde 7.5.0 is available for download, or as an in-place update to existing 7.4.1 instances. This release is said to include important new features, updates, and various bug fixes. The in-place update should take about 1 minute, depending on both network and system speeds.
In-place update progress can be monitored via SSH, command moodeutl -t.
  • It's a good idea to use the backup function on your Moode system before applying updates.
  • After rebooting, use Menu -> Update Library to incorporate the Internet Radio station revisions, additions, and deletions.
This release is based on RaspiOS Buster Lite 10.6 (2020-12-02) and Linux kernel 5.4.77 build #1371, please refer to the official Release Notes below for more information:

Code:
################################################################################
#
# 2021-11-09 TC moOde 7.5.0
#
################################################################################

New features

- NEW: Toggle CoverView on/off from System Config

Updates

- UPD: Bump to MPD 0.23.3
- UPD: Bump to librespot 0.3.1
- UPD: Bump to Meson 0.59.2
- UPD: Add MPD Config option to play silence before stopping DSD/DoP
- UPD: Add "Disabled" option to Multiroom Receiver config
- UPD: Add ALSA output mode to Multiroom Receiver config
- UPD: Add query timeout to Multiroom Sender config
- UPD: Add IP addr timeout to System config
- UPD: Add Pi Zero 2 W in revision code parsing
- UPD: Improve Spotify Config
- UPD: Improve help text on System Config
- UPD: Improve validation for Receiver volume config
- UPD: Trim strings when creating/updating radio station

Radio stations

- NEW: PRM - Prog Rock & Metal
- UPD: Bayern 2
- UPD: BR-Klassik
- UPD: Jazz FM
- UPD: JB Radio 2
- UPD: Linn Classical
- UPD: Linn Jazz
- UPD: Linn Radio
- UPD: Soma FM - Metal Detector
- UPD: Zen FM

Bug fixes

- FIX: Item "Add favorites" visible on context menu
- FIX: Advanced options toggle broken on Multiroom Config

As always, if you are enjoying the use of Moode Audio Player, please consider making a donation on Moodeaudio.org to help ensure the moOde project continues to develop great audio software for the Raspberry Pi audio community.

moOde.png
 
Wait, moode does multiroom? with spotify or quboz?
New function, only just included with the previous release if memory serves.

I haven't played with it as yet, but I think it will do any source. You have to configure one Moode instance as the host, and then others as clients to that host if I'm not mistaken, and all instances need to be the current (7.4 or newer I believe) release.

The configuration steps did not look difficult when I perused it, so if your units are updated please try and give that a whirl and report back, and if they aren't current Moode instances, then time to update!

Qobuz intentionally broke their direct support for these FOSS distros a long time ago, so with Qobuz you are still needing to stream it using a 3rd party app such as BubbleUPnP, or mconnect Player HD anyway. I do that using Moode's UPnP Renderer, I see no reason why multiroom would not work there, but I'm not sure if the Spotify Renderer would work the same way.

Would it even need to work with the Spotify Renderer? So long as you can get Spotify Connect to work with the Moode Spotify Renderer, then don't you already have the ability to do multiroom via the Spotify Connect aspect anyway?
 
Wait, moode does multiroom? with spotify or quboz?
Here is the Moode multiroom setup guide, not crazy but also not trivial in terms of setup requirements. To answer your original question it looks like Spotify yes, and Qobuz no, though even with Spotify there is the caution of it being a work in progress with a few glitches.

For me personally, the current limitation of everything being resampled to 16-bit/48kHz makes this feature more a curiosity than anything else, not really quite ready for prime time just yet.

I tried tonight with internet radio and experienced glitches, though that was with a Pi Zero 2W as receiver and I see in the notes that was stated to be untested and possibly not working, which it really isn't, so over the weekend I'll take that out of the equation and use a more powerful Pi model as the receiver instead:

Code:
###############################################################################
#
#  Setup Guide for moOde Multiroom Audio
#
#  These instructions are designed for an initial configuration of a moOde
#  Multiroom Audio system. Additional configuration help is provided within the
#  player via Menu, Quick help and the (i) information buttons.
#
#  Version: 1.0 2021-09-24
#
#  (C) Tim Curtis 2021 http://moodeaudio.org
#
################################################################################

PREFACE

This initial release of moOde Multiroom audio is designed for listening in a
casual or background setting. There is no support in this release for audiophile
features including uncompressed PCM format, rates greater than 48 kHz, DSP or
clock correction between Sender and Receiver. These features may however appear
in future versions of the feature.

OVERVIEW

A moOde multiroom audio system consists of a Sender and Receivers. The Sender
should be a dedicated moOde player configured to output to the integrated HDMI
port or optionally the Headphone jack but not connected to any speakers or
headphones. It functions solely as a Music Server that Sends its audio output to
one or more Receivers. NOTE: There can only be one Sender on the network.

BLOCK DIAGRAM

        +---------+
        | Router  |----------------------------+
        +---------+                            |
             |                                 |
             | Ethernet                        |
             |                                 |
         +-------+                             |
         |       | Pi-4 or 3B+                 | Ethernet and/or WiFi 5GHz
         | Sendr | Music Sources               |
         |       | Spotify, Airplay            |
         +-------+                             |
                                               |
                                               |
                                               |
                         +---------------------+---------------------+
                         |                     |                     |
                         |                     |                     |
                         | Pi-4, 3B+, 3A+      |                     |
                     +-------+             +-------+             +-------+
                     |       |             |       |             |       |
                     | Rcvr1 |             | Rcvr2 |             | Rcvr3 |
                     |       |             |       |             |       |
                     +-------+             +-------+             +-------+
                         |                     |                     |
                         |                     | Speakers            |
                       +---+                 +---+                 +---+
                       | . |                 | . |                 | . |
                       | O |                 | O |                 | O |
                       +---+                 +---+                 +---+

RECEIVER CONFIGURATION

Receivers should be configured first. The Receiver player daemon is separate
from MPD and the Audio Renderers and thus the Receiver configuration should be
dedicated although it's not absolutely required. A Receiver can have Airplay and
Spotify renderers running in the background but there is no coordination between
them and the Receiver player. Initiating a Spotify or Airplay connection while
the Receiver player is ON will result in audio output conflicts and errors.

A) Audio Configuration (Menu, Configure, Audio)

1. Configure the audio device
   - Set I2S audio device appropriately
   - Set ALSA Loopback to "OFF"
2. EDIT MPD settings
   - Set MPD Audio output appropriately
   - Set SoX Resampling Enabled to "No"
3. Set the following DSP's to "Off"
   - Crossfeed
   - Polarity inversion
   - Graphic EQ
   - Parametric EQ
   - CamillaDSP
4. Set all Audio Renderers to "Off"
5. Set DLNA server to "Off"

B) Multiroom Configuration (Menu, Configure, Multiroom)
   Optionally Multiroom CONFIGURE while still on Audio Config screen.

1. Set the Receiver daemon to ON
2. Optionally set Master volume opt-in to YES. This allows Receiver volume to be
   controlled by the volume knob in Playback or Playbar view of the Sender.

SENDER CONFIGURATION

The Sender should be a dedicated computer configured to output to the integrated
HDMI port or optionally the Headphone jack but not connected to any speakers or
headphones. It functions solely as a Music Server that sends its audio output to
one or more multiroom Receivers.

A) Audio Configuration (Menu, Configure, Audio)

1. Set ALSA Output mode to "Default (plughw)"
2. Set ALSA Loopback to "ON"
3. EDIT MPD settings
   - Set MPD Audio output to "HDMI 1"
   - Set Mixer type to "Hardware"
   - Set SoX Resampling Enabled to "No"
4. Set the following DSP's to "Off"
   - Crossfeed
   - Polarity inversion
   - Graphic EQ
   - Parametric EQ
   - CamillaDSP
5. Set the following Audio Renderers to "Off"
   - Bluetooth
   - Squeezelite
   - RoonBridge
6. Optionally turn on Airplay and/or Spotify renderers
7. Set DLNA server to "Off"

B) Sender Configuration (Menu, Configure, Multiroom)

1. DISCOVER Receivers. This is necessary to generate the list of Receiver hosts
   and their IP addresses. This must be done initially and whenever hosts are
   added or removed from the configuration.
2. Set Sender daemon to "ON"
3. Optionally set Initial volume for the Receivers. This action simply sets
   each Receiver's volume to an initial level for convenience.
4. In Playback view the Sender icon will appear at the top middle. Click this
   icon to open the Receivers panel which lists each Receiver, its On/Off state,
   volume and mute state. Receiver volume can be adjusted via the slider
   followed by clicking on the volume button. Mute state can be toggled by
   clicking on the mute button.

NETWORKING AND AUDIO FORMAT

A) Networking

The performance of the system depends on having low latency, high throughput
networking and hosts. If any hosts are connected via WiFi then interference
in the WiFi band can result in degraded performance and audio dropouts.

1. Discovery of Receivers relies on Multicast DNS (mDNS)
2. Addressing for the audio distribution protocol relies on IP Multicast using
   a default address of 239.0.0.1 and port 1350

B) Audio format

1. Audio is converted to 16 bit 48 kHz PCM format and encoded using the Opus
   CODEC. Resampling if needed is handled by ALSA using the Speex converter.
2. Encoded Opus frames are transmitted over the network using RTP over UDP

SPOTIFY AND AIRPLAY

Playing Spotify or Airplay through the Sender sets the Receiver hardware
volume to 100% (0dB). Overall volume is controlled by the Spotify or Airplay
client. Receiver volume is restored after the client disconnects.

USAGE NOTES

1. Spotify and Airplay support is a work-in-progress (WIP) in this initial
   release. Airplay generally works well with few audio glitches but Spotify
   can be glitchy.
2. The 2.4 GHz WiFi band which is crowded and prone to interference should be
   avoided.
3. ARM6 single-core Pi's including Pi-1B and Pi-Zero have not been tested as
   either Sender or Receiver and so YMMV.
4. The SQL table cfg_multiroom contains the configuration parameters for the
   feature. Parameters not exposed in the Multiroom Config screen can be edited
   in this table for development and testing purposes.

################################################################################
#  Post questions regarding this guide to http://moodeaudio.org/forum
################################################################################
 
Well, I've run into somewhat of a frustrating issue - with the last update to 7.5.0, I've noticed that my HiFiBerry DAC+ Pro I2S boards are no longer working as expected - I keep getting ALSA errors. I thought at first that perhaps I'd damaged the board on one player due to power outages we'd been having but when I updated the second player (which had been working swimmingly), it too started getting the following error:

Alsa Error.JPG

I'd prefer not to pave the SD card and reimage if possible, but this is certainly problematic. I'm wondering if this is a bad build with a regression or a broken update scenario?

And, of course, I can't troubleshoot via the forums because my account was somehow blown away and new account registrations are currently disabled. :(
 
Well, I've run into somewhat of a frustrating issue - with the last update to 7.5.0, I've noticed that my HiFiBerry DAC+ Pro I2S boards are no longer working as expected - I keep getting ALSA errors. I thought at first that perhaps I'd damaged the board on one player due to power outages we'd been having but when I updated the second player (which had been working swimmingly), it too started getting the following error:

View attachment 41898

I'd prefer not to pave the SD card and reimage if possible, but this is certainly problematic. I'm wondering if this is a bad build with a regression or a broken update scenario?

And, of course, I can't troubleshoot via the forums because my account was somehow blown away and new account registrations are currently disabled. :(
Try revisiting: m ➞ Configure ➞ Audio ➞ I²S Audio Device (SET)

The HiFiBerry DAC+ Pro is still on the named device list, so it should not require the DT overlay. I have had the USB output revert to the Pi onboard headphone jack after certain in-place updates, so I guess it's possible the I²S Audio Device setting could also get wiped on some updates?

I have a DAC+ Pro so can try to replicate, mine is currently running an older version of Moode but I can easily re-image it with 7.5.0 to test, though mine is running on a 3B+ board, so there's that variable in addition to a clean install vs. in-place update.

I don't know why they aren't accepting new registrations on the Moode site, but I do know why yours might have been nuked. It had to do with a hasty decision to kill low (under 5?) post accounts, because the vast majority of spam they were getting were from that kind of account. They have since rescinded the policy after realizing that did nuke a bunch of legit end users who just hadn't posted much of anything, and they apologized for being a bit too hair triggered on that.
 
No issues with a clean 7.5.0 install on my end, the DAC+ Pro is on the I²S Audio Device list and after selection and (SET), plays music.

I thought of another variable however, I use DLNA/UPnP, and you use LMS/Squeezelite. I still think by the looks of your error message that the system has just forgotten what the output device is, and if you remind it, all will be well again.
 
Try revisiting: m ➞ Configure ➞ Audio ➞ I²S Audio Device (SET)

The HiFiBerry DAC+ Pro is still on the named device list, so it should not require the DT overlay. I have had the USB output revert to the Pi onboard headphone jack after certain in-place updates, so I guess it's possible the I²S Audio Device setting could also get wiped on some updates?

I have a DAC+ Pro so can try to replicate, mine is currently running an older version of Moode but I can easily re-image it with 7.5.0 to test, though mine is running on a 3B+ board, so there's that variable in addition to a clean install vs. in-place update.

I don't know why they aren't accepting new registrations on the Moode site, but I do know why yours might have been nuked. It had to do with a hasty decision to kill low (under 5?) post accounts, because the vast majority of spam they were getting were from that kind of account. They have since rescinded the policy after realizing that did nuke a bunch of legit end users who just hadn't posted much of anything, and they apologized for being a bit too hair triggered on that.
Both of these Moode endpoints are Pi 3B+ based, so it would be the same configuration. Once is using the DAC+ Pro XLR, and one is using a DAC+ Pro. I've already tried the I²S configuration multiple times (both named devices as well as DT overlay) with no luck. Next step is full rebuild - hopefully that works as intended.
 
OK. I reinstalled from scratch and that seems to have fixed the problem. Not a great user experience, however.
 
Back
Top