Skip to main content
Nereocystis
Trending Lyricist I
April 26, 2022

Still no DLNA support in Sonos (using jellyfin)

  • April 26, 2022
  • 17 replies
  • 6334 views

I have a jellyfin server running on my Linux box, which is serving as my DLNA server, for music,etc.

I cannot find a way to get Sonos to see jellyfin.

I have tried going into music library setup and adding
\\moray.lan:8096\web\index.html

Nothing. I don’t see it in the jellyfin log, or in the firewall (ufw) log

 

This server is available via browser, android jellyfin app, my Denon receiver, Roku, etc

Only Sonos fails.

Years ago, I added the music files via a Samba server, using the ugly SMB protocol. It works sending info to Sonos. But I prefer to switch to DLNA.

 

I spent 90 minutes on the phone with Sonos support, but didn’t get very far. They agreed to put in a request for DLNA support. They were not happy that I was using Linux, though they claim support for NAS. They suggested that I install Plex, which is available for Linux. It is a possible solution, but I want support for 19 year old DLNA protocol.

I can use the android jellyfin app to broadcast music to Sonos, though it shows up as PCM 44.1 KHz input on my receiver

If the receiver plays directly from jellyfin, the input is flac, which is the way it should be.

This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.

17 replies

Show previous replies
pwt
pwt
Virtuoso
May 3, 2022

Setting Line Out Level to Fixed does sound better. I don’t quite understand why. If the problem with variable Line-Out Level is just volume, I could increase the volume on the receiver, and the sound would be fine.

When Variable Volume is used, the Connect has to modify the PCM bitstream to emulate ‘quieter’ source content: that’s why it sounds different (although any difference ought to be very slight). The use of EQ and Loudness settings will also alter the bitstream.

If you want to eliminate any bitstream modification, you have to use Fixed Volume.

Those are the choices.

One thing you might consider is using the Connect’s analog output (i.e., use the Connect’s internal DAC) with variable volume, and seeing how that sounds.

4 x P:5 | Sub | 4 x P:1 | 3 x Connect | 2 x Boost | Connect:Amp | 2 x One | Amp | Move | Port | Era 300
    NereocystisAuthor
    Trending Lyricist I
    May 3, 2022

    Thanks for your explanation @pwt 

    Now that you mention it, I can see that Connect would have to modify the PCM bitstream.

    To my ears, the difference between fixed and variable is quite noticeable, and results in noticeable drop in quality.

    I’m not quite sure what makes the best solution, but I finally understand the problem better.

    pwt
    pwt
    Virtuoso
    May 4, 2022

    To my ears, the difference between fixed and variable is quite noticeable, and results in noticeable drop in quality.

    Any differences ought to be very hard to discern, assuming EQ and Loudness settings aren’t applied in the variable volume case.

    Ears are very sensitive to differences in volume -- even very slight differences that one might not consciously notice -- with louder sources preferred. Perhaps it’s possible you’re not experiencing exactly the same volume level when comparing the two settings.

    4 x P:5 | Sub | 4 x P:1 | 3 x Connect | 2 x Boost | Connect:Amp | 2 x One | Amp | Move | Port | Era 300
    NereocystisAuthor
    Trending Lyricist I
    May 4, 2022

    Good catch. Loudness was turned on.

    Oddly, when I first clicked on EQ, Loudness was off, then 2 seconds later, I watched Loudness move to on. Perhaps just a delay in the app.

    I don’t remember ever setting Loudness, and don’t think that I would do it on purpose, unless I tested it once, and forgot to turn it off.

    One more thing to try.

    And, in fact, I notice that loudness is on for all of the Sonos devices. Wonder if this is a default.

    When cmparing earlier, I did adjust the volume. I suspect that the difference is not volume.

    wottynatty
    Enthusiast I
    July 9, 2022

    Yes, thanks, I added show upnp servers.

    I see other complaints about UPnP servers not showing up in Sonos. Here’s one example below. Sonos support does not seem to be familiar with UPnP servers. I spend more than an hour discussing servers with them, and they only wanted me to use a proprietary server, plex

    Problems with UPnP server

    It appears they want you do use Plex because it requires an ongoing fee to Plex, with whom they presumably have a relationship.

      jgatie
      jgatie
      July 9, 2022

      It appears they want you do use Plex because it requires an ongoing fee to Plex, with whom they presumably have a relationship.

       

      If by "relationship" you mean a financial deal, you are mistaken.  Sonos has no financial deals with 3rd party services.  The partnerships with music services are not financial, and any service who wishes can use the Sonos API to add themselves to the Sonos app for free.

        Airgetlam
        Airgetlam
        July 10, 2022

        This is borne out by the financial reports that Sonos releases yearly, as a public company. No financial relationship whatsoever. 

        Bruce
          Terms & ConditionsAccessibility statement