Profiles tab missing on Jellyfin 10.9.2

[EthanArmbrust]

The tab to configure DLNA profiles is missing on the 10.9.2 Jellyfin web client.

10.8.13

10.9.2

[ethanzxlee]

workaround - if you have created custom profile in the older versions , they would be stored in your config directory config/dlna/user, so you can copy all the xml files to the new directory under plugins plugins/configurations/dlna/user and it should work like it used to be after restarting the server

[samson-fu]

Will the UI get back in the future? It is a very important setting.

[disgustipated]

I started crafting this up this morning locally to add a profiles tab similar to how it used to be. The Playback reporting plugin has a tabbed structure which I like and I was able to get the profiles tab to show like that plugin does on the dlna plugin page in my local environment. Lots more would need to be built out for this. Editing the xml files in the profiles folder in the plugin folder is a decent workaround.

i built a branch on my local repo with the profiles tab working in the plugin settings page. need to fill out the rest of the ui and controls for editing with how it used to look. mapped the below out from the old version. some of this could probably be cleaned up a bit and organized differently as the old ui wasnt very clear what you were editing.

profiles
    custom profiles
        lists custom profiles - were stored in user folder
    system profiles were stored in a system profiles folder
        lists out system profiles - clicking goes to editing the profile as a custom one

    editingprofile - dlnaprofile.html
        tabs - 
            info
                Name
                User Library
                supported media types
                maximum streaming quality
                music transcoding bitrate
                submenus
                    identification
                    display
                    image settings
                    server settings
                    subtitle profiles
                    xml settings
            direct playback - profiles that define container, video codec, audio codec
                NEW button
                video
                audio
                photo
            transcoding - settings holding transcoding options
                NEW button
                video 
                audio
                photo
            containers - Container profiles indicate the limitations of a device when playing specific formats. If a limitation applies then the media will be transcoded, even if the format is configured for direct playback.
            codecs - lists codecs for audio and video
                Video
                Video AUdio
            responses - Response profiles provide a way to customize information sent to the device when playing certain kinds of media.

[teranex]

workaround - if you have created custom profile in the older versions , they would be stored in your config directory config/dlna/user, so you can copy all the xml files to the new directory under plugins plugins/configurations/dlna/user and it should work like it used to be after restarting the server

I can't seem to get this working. I use jellyfin on ubuntu 22.04. My configuration seems to be in /var/lib/jellyfin/plugins/configurations/. So I copied my xml file from the previous location to /var/lib/jellyfin/plugins/configurations/dlna and restarted jellyfin, but it still complains it's going to use the default DLNA configuration when I start playing on my AV.

Just to make sure I'm looking in the correct directory, I changed the Client Discovery Interval from 60 to 55 and saw indeed the change in that directory:

root@jellyfin:/var/lib/jellyfin/plugins/configurations# ll
drwxr-xr-x  3 jellyfin jellyfin 4096 May 14 17:16 dlna/
-rw-r--r--  1 jellyfin jellyfin  494 Jun 13 20:11 Jellyfin.Plugin.Dlna.xml

looking in Jellyfin.Plugin.Dlna.xml I then indeed see value 55 instead of 60.

[disgustipated]

workaround - if you have created custom profile in the older versions , they would be stored in your config directory config/dlna/user, so you can copy all the xml files to the new directory under plugins plugins/configurations/dlna/user and it should work like it used to be after restarting the server

I can't seem to get this working. I use jellyfin on ubuntu 22.04. My configuration seems to be in /var/lib/jellyfin/plugins/configurations/. So I copied my xml file from the previous location to /var/lib/jellyfin/plugins/configurations/dlna and restarted jellyfin, but it still complains it's going to use the default DLNA configuration when I start playing on my AV.

Just to make sure I'm looking in the correct directory, I changed the Client Discovery Interval from 60 to 55 and saw indeed the change in that directory:

root@jellyfin:/var/lib/jellyfin/plugins/configurations# ll
drwxr-xr-x  3 jellyfin jellyfin 4096 May 14 17:16 dlna/
-rw-r--r--  1 jellyfin jellyfin  494 Jun 13 20:11 Jellyfin.Plugin.Dlna.xml

looking in Jellyfin.Plugin.Dlna.xml I then indeed see value 55 instead of 60.

What version are you on? I'm using latest with the plugin but I'm in docker, you should have something similar though. My profiles are stored inside /config/plugins/DLNA_2.0.0.0/profiles/

[KintsugiUwU]

What if I just installed jellyfin and this plugin. I seem to not have the Samsung Smart TV profile. I can't play anything as the TV (2012 E-Series). says unsupported media format

If I browse trough DLNA via the TV some files work, when using jellyfin client to stream to the tv with DLNA it shows the error

[disgustipated]

What if I just installed jellyfin and this plugin. I seem to not have the Samsung Smart TV profile. I can't play anything as the TV (2012 E-Series). says unsupported media format

If I browse trough DLNA via the TV some files work, when using jellyfin client to stream to the tv with DLNA it shows the error

you can still manually edit the profiles. check the logs and see what the tv is showing for information passed in the dlna scan. note that playback might still be limited by the capabilities for the tv even if you force it in the profile.
to manually edit them look in your logs to see what the information the tv broadcasts make a matched the profile. you'll see something like this

jellyfin  | [17:24:47] [INF] [15] Jellyfin.Plugin.Dlna.DlnaManager: No matching device profile found. The default will need to be used.
jellyfin  | {"FriendlyName": "", "ModelNumber": "Digital Media Client", "SerialNumber": null, "ModelName": "", "ModelDescription": null, "ModelUrl": "", "Manufacturer": "", "ManufacturerUrl": "", "Headers": [], "$type": "DeviceIdentification"}
jellyfin  | [17:24:47] [INF] [15] Jellyfin.Plugin.Dlna.Main.DlnaHost: DLNA Session created for DeviceFriendlyName

hopefully your tv should be seen there with valid values populated and something in friendly name.
next find your profiles on your server and make a copy of one similar for your model and then edit this to try and make it match your tv. for instance mine was showing the friendly name LG and some numbers in the friendlyname so the LG* here made them match

  <Identification>
    <FriendlyName>LG*</FriendlyName>
    <Headers>
      <HttpHeaderInfo name="User-Agent" value="LG" match="Substring" />
    </Headers>
  </Identification>

[KintsugiUwU]

When I look at the logs I only see this:

[2024-08-08 09:03:16.729 +02:00] [INF] [15] Jellyfin.Plugin.Dlna.Main.DlnaHost: DLNA Session created for "[TV]UE46ES7000" - "UE46ES7000"

With no mention to profiles or anything. It seems like it's not using any profile

Edit: if I try to enable loggin the jellyfin instance won't spin back up: https://jellyfin.org/docs/general/networking/dlna/
Adding "Emby.Dlna": "Debug",
"Emby.Dlna.Eventing": "Debug"
Causes the server to crash and not both unless removed

[disgustipated]

When I look at the logs I only see this:

[2024-08-08 09:03:16.729 +02:00] [INF] [15] Jellyfin.Plugin.Dlna.Main.DlnaHost: DLNA Session created for "[TV]UE46ES7000" - "UE46ES7000"

With no mention to profiles or anything. It seems like it's not using any profile

That means its using one of the profiles. This thread is for recreating the profiles editor back in to the add-on so if youre having an issue you'll want to create a separate one.

[Nullcaller]

Any updates on this, @disgustipated? I kinda want to try and have a go at it, both because I want to utilize the functionality and for a little bit of fun. I don't want to be a nuisance, though, so if you're cooking up something cool, I'll wait.

[disgustipated]

I have a branch in my fork that has the UI tab showing. There's a bunch of things that still need done though. This morning I started looking at some of where the profiles are stored and understand better where user profiles are and how the system profiles are used. In short, kinda getting there and I was thinking of starting to tackle that now that dlna is working well again. This is going to be a big task though, and I thought I saw some more work from the jf server project with how profiles are used there too so I wanted to look into what their plans were there.

[Nullcaller]

May I try and help, i.e. fork your branch and try to bring some of the profile settings back? I found a PR in jellyfin-web that removed DLNA plugin settings, and it seemed to me like some of the code would probably be transferrable. API endpoints seem to still be there (though I haven't checked that thoroughly), so bringing back at least some of the old UI back appears to be an achievable goal. Then, I believe, it can be modified from there to be more betterer.

[disgustipated]

You're free to do whatever ya want 😁
When I looked at pulling in the old stuff I decided against it because it was an old way of reading the xml and i never liked how the ui elements looked to begin with, it always seemed all jumbled so that's why i wanted to write it from scratch.

[Nullcaller]

Yeah, I agree the profiles UI needs some love... Just making a sanity check here, is my understanding correct that, most of the times, when you use device profiles, you leave most settings at default, and tweak only the few that you need?