tinyMediaManager

tinyMediaManager v4.2 is a big release with several noteworthy changes.

tinyMediaManager v4.2 introduces a new feature called “post processing”. With this feature you are able to trigger external tools/commands on your media files from within tinyMediaManager. This will allow you to execute scripts/features which are not ... [More] available in tinyMediaManager but doable with external tools. The access to movie related data which is passed to the external tools can be done with JMTE. [Less]

TheTVDB announced that the sunset of their (free) API v3 will be on October 1, 2021. With the sunset of TheTVDB API v3, the current implementation in tinyMediaManager will no longer be able to pull data from TheTVDB.

tinyMediaManager v4 introduces a new way to show you what kind of metadata is missing. In the past this check was kinda hard coded inside tinyMediaManager and the corresponding column (called NFO) was more or less just an indicator if there is a NFO ... [More] file available or not - which is a rather useless information about the quality of the data for your library. [Less]

tinyMediaManager v4.2 introduces a new way to show you what kind of metadata is missing. In the past this check was kinda hard coded inside tinyMediaManager and the corresponding column (called NFO) was more or less just an indicator if there is a ... [More] NFO file available or not - which is a rather useless information about the quality of the data for your library. [Less]

In addition to the absolute path based skip folders, tinyMediaManager v4.2 adds the ability to add skip folders for movies which are based on regular expressions. With regular expressions you have a better utility to exclude folders from the update ... [More] data source scan as with the path based approach. To use a regular expression in your skip folder, you just need to press the button below the one for adding a full path in the skip folder section: And then add the regular expression you like to use for your skip folder: To keep the handling of the regular expressions easy, only the actual folder name will be checked against the regular expression (and not the full path). [Less]

The site Softpedia.com has made a review about tinyMediaManager:

The site freeappsforme.com has made a review about tinyMediaManager:

tinyMediaManager offers an (experimental) official docker image based on Debian Buster (for maximum compatibility). This image includes all needed components (up to date libmediainfo, FFmpeg, …) for the best experience. This image should work on any ... [More] x86_64 device. Using this image, you will get a fully working instance of tinyMediaManager which is accessible remotely (via web/VNC). Instructions Map any local port to 4000 for web access (via noVNC) Map a local volume/folder to /data where all local data from tinyMediaManager is stores (like data, logs, cache and backups) Map local volumes/folders/mounts to /media/xxx where all media will be accessed. E.g.: /mnt/movies -> /media/movies /mnt/tvshows -> /media/tvshows Sample run command: docker run \ --name=tinymediamanager \ -p 4000:4000 \ -v :/data \ -v :/media/movies \ -v :/media/tvshows \ tinymediamanager/tinymediamanager:latest After starting the container, you can access tinyMediaManager via http://your-host-ip:4000. Data volumes You should map the following folders to a volume/folder on the host: /data: where all local data of tinyMediaManager will be stores. If you do not map this out of the container, all your data/settings will be lost on an upgrade of tinyMediaManager /media: contains all your data sources You need read/write access to all mapped volumes! Configuration This image offers some special configuration parameters which can be passed to docker by using environment variables Variable         Description     Default   USER_ID ID of the user tinyMediaManager runs as. See below for an example how to use this. 1000 GROUP_ID ID of the group tinyMediaManager runs as. See below for an example how to use this. 1000 PASSWORD Password for remote access   Permissions When using using data volumes (-v flags for /data and media), permissions issues can occur between the host and the container (tinyMediaManager). For example, the user within the container may not exist on the host or does not match the right user on the host. This could prevent the container from properly accessing files and folders on the shared volume and vice versa. To avoid any problem, you can specify the user tinyMediaManager should run as. This is done by passing the user ID and group ID to the container via the USER_ID and GROUP_ID environment variables. To find the right IDs to use, issue the following command on the host, with the user owning the data volume on the host: id Which gives an output like this one: uid=1000(myuser) gid=1000(myuser) groups=1000(myuser),4(adm),24(cdrom),27(sudo),46(plugdev),113(lpadmin) The value of uid (user ID) and gid (group ID) are the ones that you should be given the container. Clipboard Because of security restrictions in the browser, your client clipboard cannot be synchronized to the clipboard of tinyMediaManager. To copy data from/to the remote connection of tinyMediaManager, you need to invoke the clipboard feature from noVNC. Just open the control panel of noVNC from the left side of the window and use the clipboard feature from there to copy the data. [Less]

tinyMediaManager v4.2 introduces a feature where you can enable a “not not overwrite existing data” option when scraping. This becomes handy if you have manually entered data or added custom artwork for your movies/TV shows. You can enable this ... [More] protection in the search dialogs or scrape dialogs: When this option is activated, tinyMediaManager does not overwrite existing data/images/trailers. [Less]