Never restart the image builder if it fail. In case of failure just reboot your RPI, the builder will resume.
I think it's better to restart from scratch ...
New fresh raspbian image and launch the builder on it.
Sorry about that but if you have launched again the builder on failure, you broke the process :/
Regards
-Eric
I think it's better to restart from scratch ...
New fresh raspbian image and launch the builder on it.
Sorry about that but if you have launched again the builder on failure, you broke the process :/
Regards
-Eric
Last edited:
Rats! I was hoping you'd been able to wrestle your problem to the ground
I remain confused by your nomenclature, though.
Among the various Raspberry Pi releases there is the Raspberry Pi 1 Model B+ (the last of the first generation RPis) and the Raspberry Pi 2 Model B. There is no 2 B+. I have no problem moving SD cards between my RPi3B and my RPi2B. I no longer have an RPi1B+ to test with.
The Pi Zero should do fine. Just don't build moOde directly on the Zero; it's excruciatingly slow [1] compared to building on the Rpi3B. For the Zero I'd either clone your working SD card or build a new one on the RPi3B.
Regards,
Kent
[1] hours, and the optional gmusicapi won't build without hackery to get more memory space for the compiler, or at least that was so the last time I tried.
@sg300b
I'm as curious as the next guy, but knowing how passionately audiophiles wax and wane over various DACs, I'd hope a separate thread would be used. Hint: I've learned to ignore any message which uses the word "soundstage".
Regards,
Kent
@Gallen1119
The equipment list helps, but as @Veazer suggests, you need to tell us just what you did. Did you start with the Raspbian-stretch-lite-2017-11-29 image Were you using the Automated moOde Image Builder [highly recommended!] or following the manual script [I wouldn't]? I routinely build images without issue on an RPi3B using the Image Builder.
Wired ethernet not only seems to help avoid random problems people seem to have but also speeds up the numerous downloads which occur during the build process.
Note that a local monitor and keyboard are *not* required or even recommended during the build. You can follow the action from your MacBook by ssh'ing into your RPi.
Bottom line: if you use the Automated moOde Image Builder exactly as described you should have no difficulty getting a successful build the first time.
Regards,
Kent
PS - It's interesting that you see similar behavior to what @arjen has reported. Maybe if we understand one we'll understand both.
First, thanks for the replies and suggestions. I greatly appreciate this community of helpful audiophiles!!!!
3rd Time is a Charm! Working without a problem this am. Maybe the wired ethernet was the difference in avoiding random errors. Not sure.
Here is what I did each time (only difference was third time had wired internet direct to router rather than WiFi):
- Etcher to burn Raspbian Stretch Lite release 2017-11-29 to uSD on MBP.
- Insert uSD card in RBPi and booted.
- Entered following commands exactly as written:
cd /home/pi
sudo wget -q http://moodeaudio.org/downloads/mos/mosbuild.sh -O /home/pi/mosbuild.sh
sudo chmod +x /home/pi/mosbuild.sh
sudo ./mosbuild.sh
- Waited about an hour until build was completed
You are absolutely correct. I could have done it without monitor/keyboard by ssh, but I had the keyboard/monitor sitting on the desk. I think some noobs may have difficulty ssh'ing into the Pi with detailed instructions. I know it is very basic RBPi, and I have done it several times, but I still have to look it up if it has been a while since I set up a new Pi.
There are just too many variables with everyones' personal hardware. Therefore, I do like the way Tim has posted the instructions...keep it simple.
Now...off to play with all the settings of my new MoOde Audio Player...SO EXCITED!!!!!
I successfully got Moode 4 on my RasPi 3-B with a IQ Audio digiamp + yesterday using the image builder. I'm having trouble with bluetooth connection. I want to connect my Samsung G7 via bluetooth to my RasPi but I keep getting a error from phone unable to connect to bluetooth device. The phone recognizes the speakers (RasPi) by name but will not connect. I made sure that buletooth was the only renderer set to on to be sure none of the other renderers were interfering with bluetooth but the phone will not connect. Any ideas??
Sox Upsample Settings question: does Moode allow for Sox Upsample Settings, similarly to what described in this Archimago post using piCorePlayer?
Archimago's Musings: MUSINGS: More fun with digital filters! Archimago's "Goldilocks" Intermediate Phase suggestion...
Just out of curiosity...
Archimago's Musings: MUSINGS: More fun with digital filters! Archimago's "Goldilocks" Intermediate Phase suggestion...
Just out of curiosity...
I'll leave the answer with respect to Moode to Tim, but SoX is fairly easy (i.e. a bit fiddly) to install and run from the command line. I have run a group of mucsically different files through various upsampling configurations and my results/preferences (listening only) fit with Archmago's. I use 'medium quality' upsampling to 384/24 in Moode to bypass my Allo Boss (V 1.0) dac's hardware upsampling. This is an area where some changes of settings can be distinctly audible.
Skip
@Kent: Of course you are right. There is no Pi2 B+. There is a newer version of the Pi2 (V1.2 I think) but mine is the older one with the 32 bit A7 processor.
Seeing Gallen first had the same problem I did but a third build worked fine I think I will try another build on my Pi2. Just because it should work... But I will keep the Pi3 in my audio system. Just in case I want to ever use the bluetooth option ;-)
Seeing Gallen first had the same problem I did but a third build worked fine I think I will try another build on my Pi2. Just because it should work... But I will keep the Pi3 in my audio system. Just in case I want to ever use the bluetooth option ;-)
Seems like a workable strategy to me
With the RPi3B, keep in mind that some folks have seem mutual interference between the onboard WiFi and Bluetooth subsystems. YMMV.
In my living room I have to tuck my moOde hardware into a cabinet among other electronic devices and lots of cabling. Not a great environment for onboard wireless interfaces so I chose to use an RPi2B there with USB-WiFi and USB-Bluetooth adapters. They're brought out the rear of the cabinet on reasonably short USB-extension cables and separated from each other and from my Netflix USB-stick by about 1/2 meter. Works a charm with everything I've thrown at it.
I'm listening to streaming jazz-radio with it now as I fiddle with other stuff on an RPi3B on my workbench (which for some reason my significant other insists on calling the dining room table!).
Regards,
Kent
Hi All,
I seem to be having soundcard detection issues with my 502dac i2s with rpi3 B. This happens intermittently when the 502dac is connected to it's own power supply. Sometimes the aplay -l shows no soundcard detected, sometimes it does and sometimes it shows a long list of subdevices, but not the soundcard. I tried to ensure that i always power on the 502dac first before the pi, but it can still happen. Then i need to poweroff and on the 502dac and reboot the pi and that usually solves the issue. Anyone using a dac hat with separate power supply encounter similar issue? I'm on moode 4.0 btw.
I seem to be having soundcard detection issues with my 502dac i2s with rpi3 B. This happens intermittently when the 502dac is connected to it's own power supply. Sometimes the aplay -l shows no soundcard detected, sometimes it does and sometimes it shows a long list of subdevices, but not the soundcard. I tried to ensure that i always power on the 502dac first before the pi, but it can still happen. Then i need to poweroff and on the 502dac and reboot the pi and that usually solves the issue. Anyone using a dac hat with separate power supply encounter similar issue? I'm on moode 4.0 btw.
@Kent: I don't use Wifi, most of my house is still wired from the days Wifi was just too slow. So even though I probably will never use BT, if the need ever comes interference will not be a problem.
And I see your spouse is as confused as mine. She keeps referring to my workshop as 'the couch'...
And I see your spouse is as confused as mine. She keeps referring to my workshop as 'the couch'...
Last edited:
This is the last missing feature from my old Foobar-SOX setup which I miss in moode.
Adding setting of the passband and phase response params would be great.
I always think about how these settings could improve the sound even further.
Please, Tim, can we hope for support in some future version ?
Just open an issue on the MPD Git and provide details of what you would like to see in new SoX resampling options.
Issues * MusicPlayerDaemon/MPD * GitHub
The current SoX options that MPD supports are at the link below and are already included in moOde.
Resampler plugins
Actually, there is already an issue tagged "feature" that covers additional SoX features. If you want options other than whats listed in the issue then make a post to the issue.
sox recipes for MPD * Issue #122 * MusicPlayerDaemon/MPD * GitHub
Last edited:
Thank you Tim. The "sox recipes for MPD *Issue #122..." thread is covering exactly the missing options I would like to have.
I have made a comment there so hopefully the MPD guys will make me happy sometimes soon
I have a very bizarre situation. I have been using EQ from time to time without any problems. Last night, I created a new EQ and then apply it. Later, when I try to change to other EQ, the browser will just keep spinning and no response. When I try to refresh the page, it did refresh and I can go to play page or browse page, but I have no way of going back to EQ. Any suggestions how to solve it?
BTW, I am using 4.0 release/
BTW, I am using 4.0 release/
