Taking a slice of the Pi

I am still having issues with my Pi 4b dropping wifi signal on occasion. So either it just doesn't have good range, mine is defective, or some other minor variable is off a bit. It really shouldn't have a problem where it's located as nothing else does.
 
I am still having issues with my Pi 4b dropping wifi signal on occasion. So either it just doesn't have good range, mine is defective, or some other minor variable is off a bit. It really shouldn't have a problem where it's located as nothing else does.
Maybe try giving it a static IP address. While that shouldn't be necessary per se, sometimes it's just something specific to your network that causes the DHCP lease to expire, or reset.

I'd also consider any strong sources of nearby interference, for example mobile phones, home cordless phones, Bluetooth devices, even a microwave oven, that might be causing the drops.

You installed the Moode distro, correct? If so, when you look in the settings, it should tell you what the wireless strength is, and if it looks strong, then there is no good reason why it should drop except interference, or an expiring DHCP lease scenario.

My 2 cents.
 
Maybe try giving it a static IP address. While that shouldn't be necessary per se, sometimes it's just something specific to your network that causes the DHCP lease to expire, or reset.

I'd also consider any strong sources of nearby interference, for example mobile phones, home cordless phones, Bluetooth devices, even a microwave oven, that might be causing the drops.

You installed the Moode distro, correct? If so, when you look in the settings, it should tell you what the wireless strength is, and if it looks strong, then there is no good reason why it should drop except interference, or an expiring DHCP lease scenario.

My 2 cents.
I am using RopieeeXl and when I check in with it on my router it finds the device just fine. It seems that the Roon core just doesn't see or recognize it. But yes, the last time it was running, it had trouble keeping signal and then eventually dropped entirely and it still can't find it.
I took off the case top just to try that but it didn't help.
 
I am beginning to wonder if Ropieee's auto-update is causing problems that can result in a corrupted install.

We've had a few reports now, all with RoPieee, of the unit vanishing from Roon. In those cases, if you looked at the RoPieee web interface, you'd see that it was in the process of updating, but if you don't try to look at it in the web interface and just assume it's time for a power cycle/reboot you can corrupt the install, as the one time you don't want to cut the power is during an update.

Because these units are meant to be run "headless" with no monitor/mouse/keyboard, it's easy to forget that there is that web interface, and just use the unit relative to the Roon interface. But that will not alert you to a RoPieee update in progress, leaving the possibility or likelihood that if the unit vanishes from the Roon interface, you'd just pull the plug for a reboot, which you definitely don't want to do during an update.

I hate things that auto-update, I like to control that process, and the above is one reason why. I would suggest you wipe the card and re-flash RoPieee, that might solve your issue if in fact the install is corrupted due to a faulty update having occurred. If it ever vanishes from the Roon interface, always dial up the RoPieee web interface via the IP address first, before doing anything else, to check for an in progress update.
 
So I went ahead and replaced the sd card, reflashed Ropieexl and so far so good. Figured I would start with the easiest hardware thing to do a do-over on.
 
What are your thoughts on the Pi vs Node2 as far as sound quality?
Thats going to vary substantially depending on which DAC is attached to the Pi. While the Node has it's own at least competent onboard DAC, the Pi's analog output is not really meant to be used for music, originally the S/N ratio was roughly akin to 11-bit resolution through it's analog output, and though that was upgraded via a driver revision in 2017, it is still below 16-bit resolution.

So while a good many people do use the Node's onboard DAC, nobody really uses the Pi's onboard DAC or analog output for anything but computer notification type sounds.
 
At times I notice an improvement, but as Mikey points out there are so many variables in play here. Plus I'm probably not one to get an opinion from as I roll different equipment in and out of my systems frequently. There is no question my new DAC is superior to the one in the Node2, but frankly the Node2 was just fine with a majority of sourcing. I can't source Spotify with it so that is one negative about the direction I went using Roon and RopieeeXL. I still need to delve more into the capabilities of higher resolution sources with the Pi and my Denafrips. I was having too much trouble maintaining connection that I kinda got out of sorts then the holidays got on the way.
 
Thanks guys, Main question revolved around improvement over the stock DAC in the Node2 which was answered.
 
Back
Top