I noticed that you added Jellyfin library integration recently. Have you guys considered adding support for JRiver Media Center metadata and/or libraries so that content that is brought into Infuse will take advantage of metadata that has already been looked up? I’ve been finding that if I add SMB shares to my JRiver media files, Infuse does well in some cases, but stumbles on TV shows, movies, etc. that are maybe less common (one in particular is the Planet Earth series where Infuse just doesn’t seem to know what to do with it). But since I’ve already taken the time to sort out all the metadata in JRiver, it would be nice to be able to use that in Infuse and since JRiver doesn’t have an AppleTV app, this would go a long way towards integrating JRiver with the AppleTV.
There are at least 2 ways to go about this from your end.
The first, which is most likely easier, is to read and parse JRiver’s metadata files that are stored with the media files with an xml extension. Here’s an example of an mkv file and the corresponding sidecar filename:
Bruce Springsteen’s Letter To You.2020.mkv
Bruce Springsteen’s Letter To You.2020_mkv_JRSidecar.xml
The contents of the sidecar file are pretty straightforward XML, and I’ve attached an example. If you guys agree to proceed with implementing this, I’ll be happy to provide more examples, including an example file for a TV show (the most distinct difference would be that Media Sub Type would be “TV Show” instead of “Movie”). I can also let you know which tags are standard and which are “custom” user fields that I added for my own needs.
This approach would require some form of directory monitoring for new and deleted media files to keep the Infuse media list up to date.
The second option, which would be move complicated and would probably require you guys to get a JRiver license so you could test it is to use their REST web interface which allows you to retrieve the user’s JRiver library, which would include all the metadata for everything the user has in their JRiver system, along with a lot of additional information for things like how the user has their views configured, much of which probably wouldn’t be useful within the Infuse app.