Stupid idea...

[Thomas-O]

This is probably a stupid idea:

Could you adapt the Jellyfin DLNA plugin to create an Odios plugin?

After installing the plugin to a Jellyfin server the user can then easily point and connect their Jellyfin server to an Odios streamer.

The plugin also enabling 3rd party developers to create apps and add-ons to act as Odios remote control points.

[b0bbywan]

Not stupid at all! I'm not familiar with Jellyfin, so what's wrong with the current Jellyfyn DLNA plugin ?

odios already ships upmpdcli, which exposes the streamer as a standard UPnP AV (and OpenHome) MediaRenderer. The Jellyfin DLNA plugin acts as a control point ("Play To"), so it should discover odio on its own and push playback to it. Same with any UPnP control point (BubbleUPnP, BubbleDS...).

[Thomas-O]

Not stupid at all! I'm not familiar with Jellyfin, so what's wrong with the current Jellyfyn DLNA plugin ?

My apologies for what is at best a half-baked idea. Actually, it's closer to raw than half-baked. Anyway,...

The existing DLNA plugin is OK, I suppose. You can use the plugin and BubbleUPNP to connect Jellyfin to Odios. The plugin works OK. And the client works just fine. It's just that compared to the elegant simplicity of something like the Fintunes or M.A.L.P apps, the do-it-all experience of BubbleUPNP is a little makeshift, clumsy and over complicated. Unfortunately, the Fintunes app doesn't support DLNA control, and M.A.L.P is just mpd. Jellyfin doesn't have a universal mpd plugin.

Of course, there's nothing stopping a developer creating a polished DLNA client app which connects the Jellyfin DLNA plugin to DLNA streamers and speakers. A dedicated phone app, kodi add-on or smart tv channel with a library browser designed for Jellyfin libraries, and with settings that enable the user to save the connection details to the server and odios: just open, browse and select play. The only problem is nobody's doing it. Perhaps because they haven't considered the idea; perhaps because commercial streamers & speakers have unpredictable and unreliable DLNA support; perhaps because they don't know about the universal Odios streamer.

Now if there was an Odios (DLNA) plugin for Jellyfin then that might inspire developers to start creating remote control client apps, add-ons and channels. Especially if the Odios plugin has settings where the user can select Odios streamers. Details which are retained by the plugin and the Jellyfin server.

It could simplifying development for those who wish to create front-end remote control clients. And at the same time create greater visibility for the Odios project. Which you might need if you wish to take on the mighty Volumio and the army of commercial streamers.

I think Jellyfin is the ideal streaming source for Odios. For 3 reasons: it's free, it's open-source, and you can easily edit the metadata. The last a great benefit to an idiot like me who is always making a mess of the tagging.

[b0bbywan]

Hey, so I took a better look into this.

Fintunes already plays to odio, on iOS over AirPlay. It breaks on Android, and that's the interesting part: polished Jellyfin clients delegate through the OS-native cast, AirPlay on iOS, Chromecast on Android. odio can receive AirPlay but not Chromecast (no open Cast receiver), so Android dead-ends.

What would work on any OS is an open delegation path the client drives itself: UPnP/DLNA, which odio already exposes via upmpdcli. But no polished Jellyfin client acts as a UPnP control point, only generic ones like BubbleUPnP, and they're clunky.

So the real gap is a polished Jellyfin client that can also push over DLNA, i.e. multiprotocol on the output side, so it reaches an open renderer like odio whatever the phone. Not a server-side plugin.

Sendspin from the open Home Foundation might be another option in a near future, it's still in early development and mostly limited to Music Assistant on the server side for now.

odio is already a ready target via upmpdcli. Happy to help if anyone wants to build it.