NextPVR recording setting with JellyFin addon

[ceejayemm]

Martin

Moved to a new thread as requested.

I am experimenting with JellyFin as a replacement for Kodi as a front end. I have a Docker based JellyFin 10.10.3 server and use the Amazon Firestick JellyFin plugin as the front end client.  I have installed the NextPVR JellyFin plugin (v11) and can access my existing NextPVR v7 server for both live tv and recordings without any problems.  Moving on to testing setting up recordings I find this set up works for basic recordings but doesn't allow access to the more 'advanced' NextPVR recording options, for example recordings setup via JellyFin  have the following default settings:

Pre-Padding: set to zero
Post-Padding: set to zero
Directory: set to default
Keep: set to 1

In (native) NextPVR I would normally have:

Pre-Padding: set to 1
Post-Padding: set to 5
Directory: set to default but I have a number of additional directories (eg Films, Sports, TV, Events etc) that I can select if needed
Keep: set to All

Is there any chance any of these settings could be made selectable in the JellyFin NextPVR plugin ?  I am almost at the point of making a permanent move to this setup so if these changes were possible that could well be the deciding factor.

If this is not the right forum to ask such questions please let me know which is. I did check the JellyFin forums as well but couldn't find a suitable place there to ask about this.

Regards.

Chris

[mvallevand]

I don't have Jellyfin installed but when you record does their GUI give you options when you recording to set the padding and the keep values? If those are passed they code looks like it uses them. I don't know if keep=ALL is valid for NextPVR though, if that is what they pass. I'd have to check.

You'd have to have Jellfyin developers if their API allows a method of selecting the recording directory. The GUI is not something the add on can control. I could only pass directories if that was available.

Note the Jellyfin API is not going to be as stable as Kodi's, the developers don't care about it, there hasn't been any attempt to improve it since the original import from MediaBrowser and it was inferior at the time to what MB was using. Basically all I do is put bandaids on that old MB code after a version is released.

Martin