Posts: 68
Threads: 15
Joined: Apr 2018
Reputation:
0
I just yesterday received my new Allo Boss DAC v1.4. This morning before work, I swapped it in place of my Boss DAC v1.2, into my roughly one year old Raspberry Pi3 running MoOde 3.8.4. I rebooted the RPi3, hit play, got sound. It sounded good, I was happy. But then when I touched the stop button, nothing happened. The Pi is not responding to input, but my playlist keeps on playing.
I'm away from home until this evening, and I didn't have time to do any troubleshooting. I was thinking I should clear all logs, manually re-select the Allo Boss DAC entry in the audio output device list, have MPD do a full re-scan.
- Is the v1.4 Boss DAC supposed to be a drop-in replacement for the v1.2 in MoOde 3.8? Is there anything I need to adjust?
- If adjustments need to be made, any suggestions what those should be?
- Wipe the SDcard and reinstall MoOde 3.8 from scratch?
- Or do I need to move up to MoOde 4 to get the Pi working right with the Boss v1.4?
thanks
--
Posts: 12,033
Threads: 271
Joined: Mar 2018
Reputation:
458
If Allo didi not announce that a new driver was needed for v1.4 Boss then I'm sure its just a new hardware revision and thus no changes needed in any Player software.
I would just re-seat it on the Pi and reboot.
-Tim
Posts: 12,033
Threads: 271
Joined: Mar 2018
Reputation:
458
Very odd.
I use cheap power supplies on my test systems and they are always under-volting but never any problems.
-Tim
Posts: 68
Threads: 15
Joined: Apr 2018
Reputation:
0
06-01-2018, 02:20 AM
(This post was last modified: 06-01-2018, 02:48 AM by rongon.)
Another clue, maybe...
As soon as I hit Play, the MoOde AP disappears from the list of SSH 'devices' in my Android tablet's wireless network settings. I think that means the Allo Boss v1.4 DAC is knocking out the RPi3's built in WiFi adapter. That's why the UI becomes unresponsive; it's not receiving anything from the Android because MoOde is running headless with its WiFi knocked out.
The only more powerful 5V supply I have is another wall wart rated for 3A instead of 2.5A. I don't know if that extra 500mA of capacity should make a difference, but using it didn't change the behavior I'm seeing.
I hope there's nothing wrong with this Boss DAC I just got. I've posted to Allo's support forum over on Computer Audiophile about this.
Now that I have two DC adapters working, perhaps I can try powering the DAC separately from the Pi. I'll read up on how to configure the jumpers on the board, etc. [Edit: Their USB C adapter doesn't fit the 2.1mm barrel plug on my second power supply, so until I get a 2.1mm to USB C adapter that fits my supply, I can't test the separate power supply hypothesis.]
We'll see what happens...
Posts: 68
Threads: 15
Joined: Apr 2018
Reputation:
0
OK, I just finished using the Pi connected through Ethernet with the new Boss DAC 1.2 (rev 1.4 on the pcb). It works fine that way.
So yes, it's confirmed. Playing audio through the new Boss DAC 1.2 knocks out the RPi3's onboard WiFi, and I lose access to the MoOde AP.
Now what do I do?
No response yet from Allo.
Posts: 12,033
Threads: 271
Joined: Mar 2018
Reputation:
458
Get a Pi-3B+ and try using 5GHz WiFi.
Posts: 68
Threads: 15
Joined: Apr 2018
Reputation:
0
Thanks Tim. I was thinking that the newer Pi-3B+ has a different WiFi adapter built in, which might play nicer with the new Boss DAC 1.2 (rev 1.4).
I'm working on getting a 2.1mm F to 2.5mm M adapter so I can power the Boss DAC 1.2 separately from the Pi. It's possible the problem stems from powering both the DAC and the Pi from the same SMPS.
Why 5GHz? I don't see the connection there.
Does MoOde 3.84 work OK on a Pi-3B+? Was that ever tested? Or will it be necessary to install MoOde 4.x?
