I'm using Emby with two movie libraries - one regular and one Remux. I also have two radarr instances.
Remux quality is only available to certain users on Emby - and I was hoping to restrict jellyseer users in the same way. I tried to do this by adding the remux radarr as a '4k' server.
This kind of works - requesting in '4k' goes to the correct radarr instance. The problem is, jellyseer is (I'm assuming here) using the metadata of files in emby to determine whether or not the 4k version exists.
This means that it's impossible to request the remux of a movie that exists in the regular library, but is of 4k quality.
Desired Behavior
It'd be nice if:
The '4k' label wasn't hard-coded (In my case, I'd use 'Remux')
We could configure jellyseer to only consider particular libraries in Emby (and Plex/Jellyfin?) to determine which versions are available. Ie, a '4k' version only exists if it's in '4k Movies' library in Emby, rather than using meta data
Additional Context
If this is something people would like, I would be happy to look into implementing this myself.
Code of Conduct
[X] I agree to follow Jellyseerr's Code of Conduct
Description
I'm using Emby with two movie libraries - one regular and one Remux. I also have two radarr instances.
Remux quality is only available to certain users on Emby - and I was hoping to restrict jellyseer users in the same way. I tried to do this by adding the remux radarr as a '4k' server.
This kind of works - requesting in '4k' goes to the correct radarr instance. The problem is, jellyseer is (I'm assuming here) using the metadata of files in emby to determine whether or not the 4k version exists.
This means that it's impossible to request the remux of a movie that exists in the regular library, but is of 4k quality.
Desired Behavior
It'd be nice if:
Additional Context
If this is something people would like, I would be happy to look into implementing this myself.
Code of Conduct