Skip to main content

Hello,

 

I am currently facing a challenge in the interplay of MPD’s (Music Player Daemon) audio output as a http stream in my local network and the sonos interface (currently I use tuneIN to listen to a specific (local!) http address, namely the one I set in my MPD config).

 

I successfully got an mp3 Stream up and running with maximal bitrate of 320kHz, using the following mpd config:


audio_output {
        type        "httpd"
        name        "mp3audio"
        encoder     "lame"     
        port        "8000"
        bitrate     "320"         
        format      "44100:16:2"
}

 

I now wish to replicate this for flac, but simply setting

audio_output {
  type            "httpd"
  name            "Lossless HTTP Stream"
  encoder         "flac"  # or "wav" for uncompressed WAV
  compression     "0"
  port            "8001"  # choose a port
  format          "44100:16:2"  # 44.1 kHz, 16-bit, 2 channels (stereo)
}

seems to not yield the expected result, as no audio is played back at all by the system. Infact the system appears to get caught in a state of constant retrying of loading the stream, with occasional static noise coming out of the speakers for a split second. 

So I don’t really know where the problem here is hidden, maybe someone has had similar experiences or a different approach to streaming from mpd to sonos, although this current solution otherwise fully satisfies my needs. 

Thank you very much!

Hi ​@tom.flgm, welcome to the Sonos Community!

I’m sorry to hear you’re having issues getting FLAC files to play on your system. The settings you have look fine, however I see that your FLAC settings have ‘Lossless HTTP Stream’. We don’t support HTTP or SMBv1 connection types and I see that your FLAC settings have ‘Lossless HTTP Stream’, but it looks like that’s just the name of the output/function/etc.

I’ve never used Music Player Daemon before, so I don’t know what exactly is wrong here. I had a look on their website where they have a help section, so you may have better luck there. Otherwise, my reply will put this thread to the top of the recently active where other users who may know more about this program can reply.

I hope this helps!

Hi Jamie,  

thank you for your reply!

 

I’m sorry to hear you’re having issues getting FLAC files to play on your system. The settings you have look fine, however I see that your FLAC settings have ‘Lossless HTTP Stream’. We don’t support HTTP or SMBv1 connection types and I see that your FLAC settings have ‘Lossless HTTP Stream’, but it looks like that’s just the name of the output/function/etc.

To clarify, yes, I intend to use a http audio stream. This works in the exact configuration I have posted above (using (the old) tuneIN as the receiving part in the Sonos App) , but only for mp3 audio. Altering the exact same settings to a flac encoder, as shown in the second snippet, breaks the whole transmission on the Sonos system’s side. Normal Audio playback via the browser works seamlessly, as expected. Therefore I posted this issue in the Sonos forum directly as it seems to be caused by the system itself, not by MPD. Changing the name (as you correctly stated) from “Lossless HTTP Stream” to something else should not change anything from a technical point of view. Hopefully this clarifies my situation, if not, please let me know!

I’ve never used Music Player Daemon before, so I don’t know what exactly is wrong here. I had a look on their website where they have a help section, so you may have better luck there.

Thank you for your suggestion! However I would also like to keep this thread open hoping for some experiences from other users on this topic. Maybe we can find an answer together!

Hi ​@tom.flgm, 

Thanks for clarifying, I figured that the name field was just that, but I wanted to be sure.

For more on our end, and if you haven’t already, then I would suggest submitting a diagnostics after the FLAC file fails to play and reach out to our support team. They have the necessary tools available to look into your system and see what’s going wrong. If there are any playback errors in the diagnostics, they’ll be able to find them and possibly see what’s causing them.

Don’t worry about the thread being closed, as it’ll stay open as long as it’s active, where after three months of inactivity it will automatically close.

Terms & ConditionsCookie settingsAccessibility statement