+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: Media stubs (/t-media-stubs)
Media stubs - Philmo67 - 2024-01-15
Hello,
I'm listing the physical discs that I haven't yet ripped in Jellyfin, so that we can use the Jellyfin clients (KODI most often) to browse our collection, choose a movie, and, if necessary, look for the physical disc and insert it in the optical drive.
The naming conventions I use are TITLE.DVD.disc , TITLE.BLURAY.disc and TITLE.BLURAY.3D.MVC.disc.
The metadata is retrieved and transmitted without any problem from the film's "TITLE".
I can't manage to materialize the fact that the film is on a physical medium, and possibly in 3D, either in Jellyfin or KODI. You can tell in KODI because it doesn't display media flags for physical discs.
Do you use this handy "media stubs" feature?
How do you manage to make physical disks and ripped media cohabit?
RE: Media stubs - tmsrxzar - 2024-01-15
jellyfin being a "media SERVER" not a "media PLAYER" i think you will find that features that involve physically changing discs are lacking
mostly people serve existing files
RE: Media stubs - Philmo67 - 2024-01-15
It seems to be a useful reminiscence of Emby: https://emby.media/support/articles/Media-Stubs.html
Having everything listed in Jellyfin also simplifies things with request systems like Jellyseerr (even if, here again, the detection of films on physical media is not automatic).
Indeed, with physical media, at playback time, it's the client's role, not the server's, to manage any missing media. KODI, for example, asks you to insert the disc and can even open its disc tray. On the other hand, a handheld device throws an error popup, that could be avoided if there was a way to see that the film is not streamable.
It seems to me that the nfo files generated by Jellyfin when indexing *.disc files should be able to contain streamdetails (even dummy ones), but that's why I'm asking you for advice :-)
RE: Media stubs - tmsrxzar - 2024-01-15
just trying to set a reasonable expectation
i would never use such a thing because my jellyfin has no drive and lives in a server closet
primary use is remote playback to my phones and tablets while away from home so it would serve no point to have my tablet ask me to insert a disc when i am on a train
RE: Media stubs - Philmo67 - 2024-01-18
Am I the only one to use Jellyfin in this context?
In short, I'm looking for a way to make media flags work on *.disc files from Jellyfin in KODI. As for other metadata, it's all working perfectly.
I'm a bit stuck:
KODI alone handles media flags correctly by parsing the file name.
It's not possible (at least not to my knowledge) to have a video library other than what is inserted directly into the KODI database by the Jellyfin plugin. Media flags would therefore have to be supplied by Jellyfin.
One idea worth exploring: when browsing the Jellyfin library, it's possible to filter content by video type (BD, DVD, 4K, SD, 3D).
How can I shape my *.disc and/or *.nfo files so that this concept can be exploited?
RE: Media stubs - tmsrxzar - 2024-01-18
if anything is going to work ...
if jellyfin identifies .disc as a "media" file it will need to serve it while bypassing ffmpeg (and everything else it does); this may work using jellyfin for kodi in native playback instead of addon (native is usually a terrible idea for regular media though)
it *could be possible by putting the url into a .strm file, jellyfin will identify .strm files but also tries to scan them so you will get errors in the log
that url would have to be a network location that kodi can access; nfs:// or smb://
and if kodi will still recognize .disc as physical media when being served in such a manner; i have no idea on the requirements kodi has for this
RE: Media stubs - Philmo67 - 2024-01-18
According to https://github.com/jellyfin/jellyfin/blob/a884b1f7869436fb373d71106330ab1db79cee11/Emby.Naming/Common/NamingOptions.cs#L95 , Jellyfin considers *.disc files as stub files not video files, and the ffmpeg bypassing logic is OK (with a clear error message if you try to stream it, saying you are trying to stream a placeholder file).
On the other hand, Stubtypes and 3DFormat (from the same C# file) don't seem to work, at least with the naming scheme I'm using because https://github.com/jellyfin/jellyfin/blob/a884b1f7869436fb373d71106330ab1db79cee11/Emby.Naming/Video/VideoResolver.cs#L96 seems to contain all the logic to manage the information I'm interested in in this thread, to populate some *.nfo file maybe.
They seem to get lost afterwards and appear nowhere in Jellyfin.
I use native mode and despite using appropriate naming conventions, the way the Jellyfin addon populates KODI database seems to bypass KODI's mediaflag detection.
I can use (and I am using) path based smart playlists though to try to facilitate navigation in KODI as much as possible.
RE: Media stubs - tmsrxzar - 2024-01-18
try the .strm workaround above
i was experimenting about a year ago with media integration between jellyfin and kodi, i was able to trick jellyfin into indexing media which was served by Hulu and accessed by the Hulu addon for kodi which i used a strm file containing a plugin:// path
the jellyfin addon for kodi had to be modified to allow kodi to control the resume pointers instead of the server for this content but it did actually work to populate "my library" with titles from Hulu