I just plugged it back into the hub via ethernet cable. Hub manager now just shows the Pi device. Connection type - wireless, status not connected. Attemps to connect to it's IP address time out. WTF!
Now unplugged from the hub i can no longer connect to volumio using its own hotspot. I'm starting to think my board is faulty. How do you guys deal with this madness? computer logic is very far removed from human logic.
Contrary to some discouraging posts here, the Pi works just fine as a music player and does not require much computer knowledge, so hang in there. Just to start with the basics, which I haven't necessarily seen completely spelled out here. Also, I have been using Moode, not Volume, so things may be a bit different.
First, a web interface served up by the player is the main way to interact with the Pi. As someone else mentioned, you may need to use the LAN cable to setup the wireless network, assign a name, password, etc., but after that, it's through its WiFi network on your tablet. You can access the Pi in terminal mode, of course, but just to make changes to the software, change some deeply hidden settings, etc. But not to play music. The fact that you're seeing the files and it acts like it's playing music means you've got that far.
In Moode, at least, each different DAC hat type has a specific setting that must be selected in the Configure–>Audio settings. I assume there must be something similar in Volumio. This is one reason why everything else could seem to be working, yet no music is coming out. It's puzzling that you had sounds coming out, then they stopped. Have you tried hooking up to the audio output on the Pi itself? It's obviously not of terrifically high quality, but it might tell you something if you get music there, but not through the DAC hat.
Stick with it. These are very handy, sound really good and are inexpensive enough to have several for different purposes. And you will learn something.
First, a web interface served up by the player is the main way to interact with the Pi. As someone else mentioned, you may need to use the LAN cable to setup the wireless network, assign a name, password, etc., but after that, it's through its WiFi network on your tablet. You can access the Pi in terminal mode, of course, but just to make changes to the software, change some deeply hidden settings, etc. But not to play music. The fact that you're seeing the files and it acts like it's playing music means you've got that far.
In Moode, at least, each different DAC hat type has a specific setting that must be selected in the Configure–>Audio settings. I assume there must be something similar in Volumio. This is one reason why everything else could seem to be working, yet no music is coming out. It's puzzling that you had sounds coming out, then they stopped. Have you tried hooking up to the audio output on the Pi itself? It's obviously not of terrifically high quality, but it might tell you something if you get music there, but not through the DAC hat.
Stick with it. These are very handy, sound really good and are inexpensive enough to have several for different purposes. And you will learn something.
Looks like you have two different connections (wired and wireless), which is why you get two different IPs. Only the top top connection shows as "connected" though. When you set up Volumio in hotspot mode, did you connect it to your wifi? Did you change the tablet's connection back to the wifi network or is it still connecting to the hotspot (it shouldn't)?.
Once you can reach Volumio via your normal network connection (or even in hotspot mode), go into the settings and check that the USB DAC is showing as the output source and that the volume isn't turned down - that should be enough to get you audio.
Once you can reach Volumio via your normal network connection (or even in hotspot mode), go into the settings and check that the USB DAC is showing as the output source and that the volume isn't turned down - that should be enough to get you audio.
Thanks buddy but I think this board is faulty. I did the setup first time around no problem. Logged it into my network, got it to recognise my DAC ok etc but it's just not working wirelessly. The pi case might be blocking it's wireless signal but it shows up ok on my hub manager, it just won't let me connect a tablet or my laptop via the WiFi. Any attempts just time out....and now it's own hotspot has stopped working. Think I'm beat to be honest.
I think it prioritises the network with the best connection and if you look at the screenshots you posted you can see that only the wired connection is active. The wireless connection has been active (because it got an IP) but isn't any longer. Several things you can still do, restart, wait 2 mins to ensure it is booted up, check whether the hotspot network reappears etc. If the case is metal it may also degrade the signal, so the wired connection might be better and more stable. When the board it is running, you should be able to connect to it via volumio.local or the IP address as described above.
I set up volumio in hotspot mode and inputted my wireless network details ok. Its no longer able to connect via the hotspot. With it plugged into the hub I ran through the setup again but everything appears fine. My DAC shows up ok and the volume bar is almost max.
It works with a wired connection but it's no use to me stuck in the back of a closet out by the front door. I can't sit on the hall floor with my headphones on lol. It is useless as a headless device without wifi.
The raspberry pi (weak) wireless should work fine if it’s close enough to a wireless access point and not in a metal enclosure. If it worked once, then it’s probably not faulty, just reset the wireless settings and try again.
Since I need a wireless access point in the room with the raspberry pi I just connected it up with Ethernet.
Since I need a wireless access point in the room with the raspberry pi I just connected it up with Ethernet.
Instead of configuring the raspberry pi as a hot spot just connect it to your wireless? Unsure why you are using it as a hotspot…
The Pi has an alloy finned cooling case and from what you say that's probably what is causing the wireless issues. I need the Pi to be in my living room which is about 20 feet away from the hub through two closed doors. They put the fibre box in with the electricity meter when they built this place, its not handy.
Reading through all this-- I think I'll stick with my iPod. You see, I'm just a computer USER, I don't care about software. Especially after being 65 years-old and not dealing with computers until I was in my early 30s.
In those 65 years, and half of that time being a mechanical engineer, I have tried them all. BASIC, Fortran 76, C, C+, C++, MatLab, virtually every CAD/CAM software ever invented. Did I tell you I hate coding? No offense to anyone, but I hate sitting on my **** writing code. I would rather stick needles in my eyes.
But, I don't like that I have spent thousands of dollars on Apple Music, only to have my music files deleted or moved around whenever Apple updates their software. Not going to spend time on the phone or internet trying resolve where my music went at $1 per song. I have an Apple iPod with old version of software and a 2008 Mac Book Pro with the same old software. Same old moans, same old groans. Never automatically synchronize when attaching the iPod to the laptop. Ever.
One day, that iPod will die. In preparing for that day, I have used Spotify, YouTube and a few others that I can't remember. Ran into the issue where music was flaky, lagging, shitty. Apple said it was internet service and ISP said it was Apple. Don't want to go back to any of them anymore. I read most of these posts on this thread (these words were like speaking Greek to me a few years back), hoping that there was something out there, music streamer, Raspberry Pi- whatever.
No, I don't want to learn anymore software. I just want to listen to music, and pray that the iPod lives a few more years. Before it dies, I hope to transfer all my electronic files to some device that will play the music without me having to be concerned what type file it is and what UNIX command I need to learn, what devices to connect, while all the while remembering that I can take a LP out of its cover and listen to some great music.
In those 65 years, and half of that time being a mechanical engineer, I have tried them all. BASIC, Fortran 76, C, C+, C++, MatLab, virtually every CAD/CAM software ever invented. Did I tell you I hate coding? No offense to anyone, but I hate sitting on my **** writing code. I would rather stick needles in my eyes.
But, I don't like that I have spent thousands of dollars on Apple Music, only to have my music files deleted or moved around whenever Apple updates their software. Not going to spend time on the phone or internet trying resolve where my music went at $1 per song. I have an Apple iPod with old version of software and a 2008 Mac Book Pro with the same old software. Same old moans, same old groans. Never automatically synchronize when attaching the iPod to the laptop. Ever.
One day, that iPod will die. In preparing for that day, I have used Spotify, YouTube and a few others that I can't remember. Ran into the issue where music was flaky, lagging, shitty. Apple said it was internet service and ISP said it was Apple. Don't want to go back to any of them anymore. I read most of these posts on this thread (these words were like speaking Greek to me a few years back), hoping that there was something out there, music streamer, Raspberry Pi- whatever.
No, I don't want to learn anymore software. I just want to listen to music, and pray that the iPod lives a few more years. Before it dies, I hope to transfer all my electronic files to some device that will play the music without me having to be concerned what type file it is and what UNIX command I need to learn, what devices to connect, while all the while remembering that I can take a LP out of its cover and listen to some great music.
I hate iPlayer and that It takes over your files and alters them so you can't do anything with them. Too bad if you haven't made a backup before booting it up because you can't now.
https://store.hiby.com/products/hiby-r3-ii
I have my eye on one of these
In the mean time a cheap android tablet with a usb DAC and the HiBy music player app works very well.
https://store.hiby.com/products/hiby-r3-ii
I have my eye on one of these
In the mean time a cheap android tablet with a usb DAC and the HiBy music player app works very well.
Adress assignment: Not DHCP
In the setup of volumio you have to give volumio a static ip-adress. No dhcp. Forget the hotspot!
In the setup of volumio you have to give volumio a static ip-adress. No dhcp. Forget the hotspot!
Last edited:
There's a reason there's a market for a complete system. Some people just don't like this sort of stuff and would rather just spend a bit of money on something that just works.
I run Moode headless and have had no issues using raspi imager to burn Moode SD cards. I would be wary of just powering the pi off at the PSU, and always use the power off that the player UI provides. SD card corruption on sudden power off is rare, but it can happen...
You should also be able to use the pi from both wired and wireless simultaneously. I do for several applications without trouble. It may be that volumio is only making itself available on one IP. Unplug ethernet cable and reboot the pi.
A metal case might interfere with WiFi but I have them on my pi4b and they're ok so YMMV, but I'd expect WiFi to be ok. Try it without the case.
I run Moode headless and have had no issues using raspi imager to burn Moode SD cards. I would be wary of just powering the pi off at the PSU, and always use the power off that the player UI provides. SD card corruption on sudden power off is rare, but it can happen...
You should also be able to use the pi from both wired and wireless simultaneously. I do for several applications without trouble. It may be that volumio is only making itself available on one IP. Unplug ethernet cable and reboot the pi.
A metal case might interfere with WiFi but I have them on my pi4b and they're ok so YMMV, but I'd expect WiFi to be ok. Try it without the case.
Many of you conflate the use of the Command Line Interface (CLI) console as if you were "programming".... not close by a 100 country miles!
I'm 65, been doing firmware since college days. Love it.
Was doing "internetworking" when we called it DARPAnet. Before we had that Web and while AOL was still doing their ALL caps in their own little world.
Apple?
Let me tell you a joke we have.
If airlines were like Windows, the plane would look awesome, the crews and facilities would be top notch, the plane would take off on time and when it got to 40,000 feet, sometimes it would blow up
If airlines were like Apple, the plane would look awesome, the crews and facilities would be top notch, they'd take off on time... but if you asked how it all worked they'd kick off the flight. Without a parachute.
If airlines were like Unix, the passengers and crew would bring the parts to the plane and they'd build it right by the gate.
Programming, NOT CODING -I hate that word and its implications- is the art of organizing your thoughts into some logic that can be "programmed". Back in the old days, when I started this, it was usually a single thread with subroutines, conditional statements and hardware IO... remember the old Peek and Poke? If you're an engineer it should come easy to you.
Nowadays it's far more complex, with multi threaded/process/core/processors, etc... with parallel and sequential designs, etc...
Yet, through all of this, UNIX and its variants, have stayed very relevant... because it's inherently a simple, very extensible operating system. It even has extensions for real time operation.
The Raspberry is a teaching computer... put together with some incredibly good foresight: features, cost, extensibility, etc.. Learning how to use it will open up an understanding of how computers work and will likely change your attitude towards Programming.
Until then, you're indeed a user... and the High End depends on people like you that will spend 5000 bucks on a "streamer".... And Apple, like Tidal, hashes the music files.
Perhaps what you need is to look at an Android tablet or a PC with a nice AD/DAC. Connect the iPad ( or whatever you use to play the Apple stuff) and then connected into the AD/DAC.... and start recording it at 24/96 with the AD, store the files as lossless WAV... later, if you want to use metadata you can transfer them to some FLAC format.
Maybe I can help. I'm pretty much a dummy. But I have a couple of Raspberry Pi streamers going, and getting them up and running is really not that bad. Some things I've learned are:
1. Don't try to do too much.
2. The Raspberry Pi Imager is way easier than the old freeware imaging utilities. I'm glad that exists. What I do:
3. Your network absolutely needs to have an Ethernet port to connect to the RPi. That's the easiest way to get it started. Connect the Ethernet cable from the RPi's Ethernet port to the Ethernet port on your WiFi router or cable modem. In your PC's web browser Address bar, type in moode.local.
4. Moode will take a while to boot the first time. It will eventually show up in the browser. Once there, you should be able to go into Moode > Configure > Network and set up the Wireless connection. Leave it at DHCP (don't change it to use a STATIC IP address). You will need to enter the name (SSH) of your home network and its password. If you don't know this then you'll need to find it.
5. Once this has been done correctly, Shutdown the RPi, then shut off power to it. Remove the Ethernet cable. Reboot the RPi. You should be able to find Moode from a PC browser window loading the moode.local address. If that doesn't work, go back to step 3 and try again until you get the Network SSH and password figured out.
6. It's easiest to purchase an external USB DAC for sound from the Raspberry Pi. A DAC HAT is going to be much more trouble. I use a Topping D10, and happily. Go into Configure > Audio and set the playback device. That screen is pretty self-explanatory.
6. It takes forever to rip your CDs to files to play in the streamer. It took me years, and I didn't rip my entire CD collection. Just the ones I actually listen to.
7. Another long process is tagging your files so they show up in some kind of order in your Tag View and Album View -- especially if you listen to a lot of classical music. But that's a whole other story...
I hope this helps. I went through a lot of frustration getting confident setting this stuff up, and I still find it fairly difficult if something isn't working or I do something stupid.
1. Don't try to do too much.
2. The Raspberry Pi Imager is way easier than the old freeware imaging utilities. I'm glad that exists. What I do:
- You'll need a micro SD card reader for your PC. I use a cheap USB one, but some laptops have them built in.
- Download the latest version of Moode Audio from moodeaudio.org. It will be a zip file in your Downloads folder.
- Download and install the Raspberry Pi Imager for Windows. It will make the usual icon in your Start menu, etc.
- Run the Raspberry Pi Imager and it should 'see' the Moode image waiting in your Downloads folder. That will burn the Moode image onto the uSD card.
- Once that's done, take the uSD card and insert it into your Raspberry Pi's uSD card slot.
3. Your network absolutely needs to have an Ethernet port to connect to the RPi. That's the easiest way to get it started. Connect the Ethernet cable from the RPi's Ethernet port to the Ethernet port on your WiFi router or cable modem. In your PC's web browser Address bar, type in moode.local.
4. Moode will take a while to boot the first time. It will eventually show up in the browser. Once there, you should be able to go into Moode > Configure > Network and set up the Wireless connection. Leave it at DHCP (don't change it to use a STATIC IP address). You will need to enter the name (SSH) of your home network and its password. If you don't know this then you'll need to find it.
5. Once this has been done correctly, Shutdown the RPi, then shut off power to it. Remove the Ethernet cable. Reboot the RPi. You should be able to find Moode from a PC browser window loading the moode.local address. If that doesn't work, go back to step 3 and try again until you get the Network SSH and password figured out.
6. It's easiest to purchase an external USB DAC for sound from the Raspberry Pi. A DAC HAT is going to be much more trouble. I use a Topping D10, and happily. Go into Configure > Audio and set the playback device. That screen is pretty self-explanatory.
6. It takes forever to rip your CDs to files to play in the streamer. It took me years, and I didn't rip my entire CD collection. Just the ones I actually listen to.
7. Another long process is tagging your files so they show up in some kind of order in your Tag View and Album View -- especially if you listen to a lot of classical music. But that's a whole other story...
I hope this helps. I went through a lot of frustration getting confident setting this stuff up, and I still find it fairly difficult if something isn't working or I do something stupid.
A while back I decided to run Android.... tablets are cheap... and so are micro SD cards. The only issue is getting power over the OTG USB cable.
Recently I got a Chromebook at Costco for 220 bucks (or so) and I plugged in a 1TB uSD card in it. It has TWO... USB-C connectors so I can get power and data OTG running at the same time. It doesn't have a touchscreen... that was an additional 100 bucks and I can be cheap sometimes... but it came with wireless mouse so so it works fine.
All I run in it is Tidal... plus I do have the network file system mounted so I can see the CD rips and some LP recordings... but by and by I downloaded some 500 LPs from tidal and then I got the turntable...
Yes, I got Raspberries... and yes, it's one of the projects... but I got too many projects and I went back to work.. 😛
Oh, for ripping, I do it in a Windows machine. It has an i7, 13th generation, micro form factor. It rips pretty fast. The data is then stored in the network.
Recently I got a Chromebook at Costco for 220 bucks (or so) and I plugged in a 1TB uSD card in it. It has TWO... USB-C connectors so I can get power and data OTG running at the same time. It doesn't have a touchscreen... that was an additional 100 bucks and I can be cheap sometimes... but it came with wireless mouse so so it works fine.
All I run in it is Tidal... plus I do have the network file system mounted so I can see the CD rips and some LP recordings... but by and by I downloaded some 500 LPs from tidal and then I got the turntable...
Yes, I got Raspberries... and yes, it's one of the projects... but I got too many projects and I went back to work.. 😛
Oh, for ripping, I do it in a Windows machine. It has an i7, 13th generation, micro form factor. It rips pretty fast. The data is then stored in the network.
Well I like PiCorePlayer. You don't need an Ethernet connection, as long as you have a monitor and keyboard you can plug into the Rpi. You enter the WiFi information that way, and then set up the PiCorePlayer via your web browser.
But first, I use Balena Etcher to burn the PiCorePlayer image onto an SD card. It takes a few minutes. Then put the card in the RpI, hook up monitor and keyboard, and power up. You'll get s prompt to go into setup, and enter your wifi into.
Make a typo? Burn a new img.
(You could also add a file to the root folder of the SD card with the WiFi info.)
Once the Rpi connects to your home WiFi, go to your web browser and enter the IP address of your RPI. Find that in the DHCP Clients list in your router's setup pages, 192.168.1.1(typ).
You'll need to enable the LMS media server and manually log in to any streaming services you use, I got Tidal and Pandora working.
I also use a DAC hat and a power filter board.
Happy to answer any questions.
But first, I use Balena Etcher to burn the PiCorePlayer image onto an SD card. It takes a few minutes. Then put the card in the RpI, hook up monitor and keyboard, and power up. You'll get s prompt to go into setup, and enter your wifi into.
Make a typo? Burn a new img.
(You could also add a file to the root folder of the SD card with the WiFi info.)
Once the Rpi connects to your home WiFi, go to your web browser and enter the IP address of your RPI. Find that in the DHCP Clients list in your router's setup pages, 192.168.1.1(typ).
You'll need to enable the LMS media server and manually log in to any streaming services you use, I got Tidal and Pandora working.
I also use a DAC hat and a power filter board.
Happy to answer any questions.