![]() nfo file updates in Mezzmo?Hmmm, it should be that simple. nfo file updates in Mezzmo?Ĭould you tell me what I'm doing wrong, or point me to a Dummies Guide to actioning. nfo file don't appear.Ĭould you tell me what I'm doing wrong, or point me to a Dummies Guide to actioning. I then delete my 'test' folder from Mezzmo and add it again. I have the radio button "Update all attributes. I have Mezzmo set to "Get text metadata and artwork fromXBMC (.nfo/tbn) files". These are generated in the same folder as the movie, which are all mp4's. nfo files that I can get out of tinymediamanager, I could then modify these as required. My best hope seems to be if I can get Mezzmo to process the. The whole of this sector seems to assume that only nerds do this kind of thing - so there don't appear to be any instructions included with any software. It's impossible to differentiate between wrong actions and bugs. None works in a simple, consistent way without bugs. ![]() I've also discovered Ember Media Manager. I've tried tips from another thread, which advises using tinyMediaManager and/or MediaMonkey. It's sad that most of my requirements would be achieved by correctly populating the Artist(s), Genre, and Year fields without keying these into a large number of movies - but I can't achieve it. (I can do it, myself, because I know the folder structures). I want to have it properly organised so that my wife can find her way around my movies. This is done by passing the user ID and group ID to the container via the USER_ID and GROUP_ID environment variables.I was very pleased when I tried Mezzmo - it was the easiest software to drive my media from my PC to my TV.īut now I've got greedy. To avoid any problem, you can specify the user tinyMediaManager should run as. This could prevent the container from properly accessing files and folders on the shared volume and vice versa. For example, the user within the container may not exist on the host or does not match the right user on the host. When using using data volumes (-v flags for /data and media), permissions issues can occur between the host and the container (tinyMediaManager). See below for an example how to use this. ID of the group tinyMediaManager runs as. This image offers some special configuration parameters which can be passed to docker by using environment variables Variable You need read/write access to all mapped volumes! Configuration ![]() If you do not map this out of the container, all your data/settings will be lost on an upgrade of tinyMediaManager /data: where all local data of tinyMediaManager will be stores.You should map the following folders to a volume/folder on the host: E.g.:ĭocker run \ -name =tinymediamanager \ -p 4000:4000 \ -v :/data \ -v :/media/movies \ -v :/media/tvshows \Īfter starting the container, you can access tinyMediaManager via Data volumes Map local volumes/folders/mounts to /media/xxx where all media will be accessed.Map a local volume/folder to /data where all local data from tinyMediaManager is stores (like data, logs, cache and backups).Map any local port to 4000 for web access (via noVNC).Using this image, you will get a fully working instance of tinyMediaManager which is accessible remotely (via web/VNC). This image should work on any x86_64 device. This image includes all needed components (up to date libmediainfo, FFmpeg, …) for the best experience. TinyMediaManager offers an (experimental) official docker image based on Debian Buster (for maximum compatibility).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |