The media client I've been using lately is tinyMediaManager. In typical open source fashion, there are dozens of applications available to scan a media library and generate external metadata files and assets, so that the media clients could better parse all the crazy things you throw at it. I did a little bit of research, and discovered that for well over a decade, a sort of unofficial standard had emerged for exactly this problem.
I tried devising my own naming scheme for my files, but not all media clients handled that very gracefully they attempted to parse the names and determine the content type based on file names, or they ignored the names entirely, or even ignored the files.
#Where does tinymediamanager store database files mac osx android
I keep these on an NFS shared drive, and stream to Kodi or ncmpcpp, or whatever media client I happen to be using on any given Linux or Android device. I prefer a digital format, and since I consume a lot of independent content that doesn't have the budget for physical releases anyway, most of my purchases are digital files. I consider myself an early adopter of digital content. How can your computer tell whether that 8 GB file in your ~/Movies folder is the latest superhero movie, or your daughter's soccer game? The trouble with video files is that they are not easily parseable.
0 kommentar(er)
