Too late to edit the above, but it appears that AirAudio requires a rooted device whereas Bubble does not.
Hello, I'm new and just purchased a Pi. I have a basic newbie question if someone wouldn't mind helping. I have Moode installed and I can bring it up. I can play something but have no audio on earphones. Question 1 - can the Pi play out through mini-plug earpods? Question 2 - if it can output to earphones, then I need some help in how to configure it because I'm getting nothing. Any tips appreciated.
Thanks, Steve
Thanks, Steve
Hello, Pavlograd.
The jack out is not for earphones.
It's is for amplificator or for example a amplfied speakers
The jack out is not for earphones.
It's is for amplificator or for example a amplfied speakers
The RPi built-in analogue audio output is not recommended for critical listening. It is there for marketing purposes, I suppose ...
Does the Sox resample options also apply when playing via airplay or is that something that needs to be manually adjusted?
Has anyone managed to get BBC Radio 4xtra working as a stream in Moode? All hints, tips and urls gratefully received
Hi,
The SoX resample rates on the MPD config screen only apply to MPD.
Airplay receiver always outputs 16/44.1 PCM and thus must use resampling if the input stream is not already at this rate. It can be configured to use either basic or SoX resampling. Moode configuration uses SoX to ensure highest SQ.
-Tim
Re: BBC Radio 4 Extra
Just add new station
http://bbcmedia.ic.llnwd.net/stream/bbcmedia_radio4extra_mf_p
Mine took a while to update but works fine.
Happy Days
Just add new station
http://bbcmedia.ic.llnwd.net/stream/bbcmedia_radio4extra_mf_p
Mine took a while to update but works fine.
Happy Days
Hi,
I have a Rpi3 that is connected to the WiFi using its onboard wlan, and it has 70% signal strength. I also have an USB-Dac connected to the Pi. I found that playing music from my server using samba, it has a weird problem. depending on how i change the buffer-size playing an mp3 @320kb (no matter how long the song is) the last 4-5 seconds it freezes for a second and i get this in my logs : usb 1-1.5: 1:1: cannot get freq at ep 0x1.
I have tried all usb-ports and changed the buffer to 0.5mb,1mb, 2mb 4mb 8mb 16mb and 32mb on the smaller buffers (up to 4mb) this 1 second delay happens in the last 4-5 seconds of the song. the higher buffer makes the songs freeze after half or a quarter of the song.
When turning the buffer off. It doesn't freeze at all when playing mp3.
now the weird thing, when i am playing a flac file 24bit-192khz with no buffering, it doesn't work, freezes all the time. maybe this is no surprise, when enabling the buffer 4mb and up, the flac plays without any problems what so ever.
The flacfile is almost 200mb and gives no error, but the mp3 11mb causes freezing with buffering enabled.
so for testing:
When i put the mp3 file on the SDcard it plays without a problem no matter the buffer-size.
when playing with Rsize and Wsize it gave similar results to the changing of the buffer-size.
when using nfs instead, 8mb buffer, mp3 doesn't have a real problem. the logs shows : usb 1-1.5: 1:1: cannot get freq at ep 0x1 before the song starts but there are no problems when listening to the song it happens before it starts. The flac works perfect too (for flac it doesn't matter if it still uses smb or if uses nfs)
So basically i don't have an urgent matter, as it works on nfs, Just want to share my findings, but if you have a solution i overlooked i am happy to test.
I have a Rpi3 that is connected to the WiFi using its onboard wlan, and it has 70% signal strength. I also have an USB-Dac connected to the Pi. I found that playing music from my server using samba, it has a weird problem. depending on how i change the buffer-size playing an mp3 @320kb (no matter how long the song is) the last 4-5 seconds it freezes for a second and i get this in my logs : usb 1-1.5: 1:1: cannot get freq at ep 0x1.
I have tried all usb-ports and changed the buffer to 0.5mb,1mb, 2mb 4mb 8mb 16mb and 32mb on the smaller buffers (up to 4mb) this 1 second delay happens in the last 4-5 seconds of the song. the higher buffer makes the songs freeze after half or a quarter of the song.
When turning the buffer off. It doesn't freeze at all when playing mp3.
now the weird thing, when i am playing a flac file 24bit-192khz with no buffering, it doesn't work, freezes all the time. maybe this is no surprise, when enabling the buffer 4mb and up, the flac plays without any problems what so ever.
The flacfile is almost 200mb and gives no error, but the mp3 11mb causes freezing with buffering enabled.
so for testing:
When i put the mp3 file on the SDcard it plays without a problem no matter the buffer-size.
when playing with Rsize and Wsize it gave similar results to the changing of the buffer-size.
when using nfs instead, 8mb buffer, mp3 doesn't have a real problem. the logs shows : usb 1-1.5: 1:1: cannot get freq at ep 0x1 before the song starts but there are no problems when listening to the song it happens before it starts. The flac works perfect too (for flac it doesn't matter if it still uses smb or if uses nfs)
So basically i don't have an urgent matter, as it works on nfs, Just want to share my findings, but if you have a solution i overlooked i am happy to test.
Is the error message from ALSA clock?
What USB device do you have?
Reding up on the message, it looks like it resides with the USB device and a problem with timing - IIRC the onboard wifi comes off the same bus as the USB. Can you connect using Ethernet and see if the problem still occurs?
Does it happen with all MP3 files or only 320kb ones? Can you convert a working flac to a 44.1khz MP3 and see if the problem still occurs?
Have you disabled onboard Bluetooth?
Do you have any other USB devices connected?
Reading on this error, it is related to ALSA underrun, and it seems to be a hardware problem
Given that you can play the same file fine locally, that puts a whole bunch of unknowns into the mix - network, wifi, server, USB, dac, config - simplify that down by taking the network out of the equation and your problem goes away. However, your flac works, which raises more questions.
An overview of your network would help - router, wifi channel, wifi config at the router, connection to your server, what kind of server and share.
Also, more info on failing MP3 - bitrate, frquency, etc. Are there any mp3s that work? Can you encode a really basic, low bitrate one and test that?
What USB device do you have?
Reding up on the message, it looks like it resides with the USB device and a problem with timing - IIRC the onboard wifi comes off the same bus as the USB. Can you connect using Ethernet and see if the problem still occurs?
Does it happen with all MP3 files or only 320kb ones? Can you convert a working flac to a 44.1khz MP3 and see if the problem still occurs?
Have you disabled onboard Bluetooth?
Do you have any other USB devices connected?
Reading on this error, it is related to ALSA underrun, and it seems to be a hardware problem
Given that you can play the same file fine locally, that puts a whole bunch of unknowns into the mix - network, wifi, server, USB, dac, config - simplify that down by taking the network out of the equation and your problem goes away. However, your flac works, which raises more questions.
An overview of your network would help - router, wifi channel, wifi config at the router, connection to your server, what kind of server and share.
Also, more info on failing MP3 - bitrate, frquency, etc. Are there any mp3s that work? Can you encode a really basic, low bitrate one and test that?
The Pi3 3.5mm jack can certainly output to headphones, but by default audio is set to output to hdmi.
Enter the following via ssh:
Code:
snd_bcm2835
sudo amixer cset numid=3 1
sudo amixer cset numid=2 1That will permanently set ALSA audio to output to the 3.5mm jack.
snd_bcm2835 loads the driver
sudo amixer set numid=3 1 sets it to 'analogue' mode
sudo amixer set numid=3 0 sets it to 'auto' mode (buggered if I know what auto does... give it a try, you can't hurt it)
sudo amixer set numid=3 2 sets it to 'hdmi' mode
The line 'sudo amixer cset numid=2 1' sets the 'write' parameter, making the change permanent, until you change it again - for testing, you should get headphone audio after 'sudo amixer set numid=3 1'
Last edited:
Further... in my experience 'wifi' ain't 'wifi' - it can be 54kbps 802.11b through to 6.75Gbps 802.11ad. 😱
In nearly every situation I have encountered where people have problems playing streamed audio, it's because the router is a basic (known as POS in the trade 😉 ) model that just can't hack the bandwidth you are trying to push through it. If you are using the router the ISP gave you, I suspect it is underpowered... very few ISP supplied routers are any damned good, in my experience.
Take my home setup in Borneo, where I only live a part of the year - I had an Apple Airport Time capsule which supports MIMO and 802.11ac, giving 2.4GHz and 5GHz with a bandwidth of 40MHz and a throughput of around 100mbps, which is fine for the half-dozen laptops, iPhones and iPads we have around the place, but when I brought all my amps and a handful of RPis for my latest r&d effort, it was lagging and streaming video to the appletv while playing audio to a couple of Moode players saw it give up. So enter a new triple-antenna, 450MBPs 802.11n router and it handles everything I can throw at it, despite the new router being 802.11n vs 802.11ac, in theory a 'lesser' spec. Simply because with three separate transceivers, the router isn't having to turn around all the time and can receive and transmit simultaneously.
So, 70% 'signal' means bugger all, really, except that you can see your router pretty well without much interference. The Pi is only really happy at 20MHz on 2.4GHz, so having your router set to 40MHz, if you have that option, can actually make things worse as the router is continually stepping down, then stepping back, as it talks to different devices.
Also, what channels you are on and how congested your local airwaves are can have a significant effect on throughput. If you are in an apartment, for example, you can actually improve things by reducing your routers power, as it won't 'see' many of the competing signals and thus won't be having to back off the band all the time to allow other routers their shot at a limited band. Doing a wifi survey is imperative, if you live in an urban location. In this house I can see mine and the neighbours - we are on different channels, though, so no bother. In NZ I can see mine - the nearest house is about 400M away, so again, no bother. Because I'm partial to 'outside broadcasting', I have a bunch of repeaters and my neighbour can see my network, but again we are on different channels, so no problems with them bands.
For me, I don't have an FCC to worry about, so I configure my routers to use 'asian' frequencies, which have a wider range of channels and higher output than the US, but you often find that the default configs assume USA and thus you are emasculating your potential, somewhat. (Not sure where in the world you are, Carmen Sandiego).
Ensure your router and your computers, etc. actually match your geography - on the Pi, using sudo cat /etc/wpa_supplicant/wpa_supplicant.conf will tell you which country code you are using and you can change it to suit.
Which doesn't mean I am advocating changing it to a country you aren't in, as that can incur the wrath of the authorities, but for me that's not an issue - both my homes are in the full-fat, wide spectrum part of the world 😉
If all things are equal, your server is configured fine, your Pi is configured fine and you can 'see' everything you need to, it may be that your router just doesn't cut the mustard any more. With high-powered routers now at a ridiculously low price, you can save yourself a lot of bother by upgrading. At worst, it won't hurt to get newer tech in place.
Last edited:
Is there a bug/problem with .dsf id3tag v2.3 recognition?
With foobar/mp3tag/tag&rename there are no problems.
I have done 'update mpd db' from sources and 'update this folder' with no luck.
With foobar/mp3tag/tag&rename there are no problems.
I have done 'update mpd db' from sources and 'update this folder' with no luck.
Hi,
I use moodeaudio with rpi 3 B.
Some questions.
I have a allo piano 2.1 i2s dac using the PCM5142. I can't find that or any other dacs w/PCM5142 in the dac-list. For now, I use the iq-audio-pi-dac (PCM5122) but the sound is not as good as it should be. What can I do?
2nd, I plan to use pi/moode with dynacords xeo4 active speakers. What are the appropriate settings for these?. They should talk UAC2 via USB.
Rüdiger
I use moodeaudio with rpi 3 B.
Some questions.
I have a allo piano 2.1 i2s dac using the PCM5142. I can't find that or any other dacs w/PCM5142 in the dac-list. For now, I use the iq-audio-pi-dac (PCM5122) but the sound is not as good as it should be. What can I do?
2nd, I plan to use pi/moode with dynacords xeo4 active speakers. What are the appropriate settings for these?. They should talk UAC2 via USB.
Rüdiger
Maybe the upcoming Moode 3.0 will have the settings for Piano 2.1? They have appeared on the latest release of Volumio.
and next q: I have a 32GB minsdcard. I expanded the root fs to fill the whole card. This worked ok. So now, where do I copy my music files (flacs) so moode finds it?
Rüdiger
Rüdiger
Hi Rüdiger,
Moode supports the following storage devices:
- NAS via SMB/CIFS or NFS file sharing protocols
- USB storage device
- SD Card that Moode is installed on
The following samba shares are available:
NAS, RADIO, SDCARD and USB
If you want to copy music files to Moode SD card then connect directly to the SDCARD samba share. For example:
From Mac. cifs://moode/SDCARD
From Win. z: -> \\moode\SDCARD
-Tim