Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Cannot register as donator
It takes some time until the donation gets registered with our system (up to 15 minutes). If you are not able to register for the donator version with the email address you used, please contact us via the contact form.
Does tinyMediaManager modify files from my library
tinyMediaManager will not alter files from your media library unless you force it to by using:
- scrape meta data (NFO files and artwork files will be created/overwritten)
- rename (the media files including all necessary files like artwork and NFOs will be renamed according to your settings)
- delete (the media files (including all meta data files) of the selected movie(s)/TV show(s)/episode(s) will be deleted from the file system
Import watched state into Kodi
By default Kodi does not import the watched state from the NFO into its internal database. You can force Kodi to import the state by following the steps in the Kodi wiki.
Java Heap Space errors
If you got a larger library, the preserved memory (512MB default) for the tinyMediaManager process can be reached. You are able to increase the memory by setting user parameters:
- open (or create if it does not exist) the file extra.txt in the tinyMediaManager folder
- add the a new line containing
-Xmx1024m(where 1024 is the amount of megabytes you want to preserve for tmm; you can change it as you want. BE AWARE: this amount of memory has to be free when tinyMediaManager starts)
- relaunch tinyMediaManager
Re-import NFO changes in Kodi
Once a movie or TV show has been imported into Kodi, Kodi does not react on (external) changes to the NFO file. You can force Kodi to refresh the data by following the steps on the Kodi wiki.
How to handle bonus content
Bonus content like cut scenes or some extra clips may cause some import problems when not having the right name scheme (tinyMediaManager detects them as additional movies).
The best way to put bonus content to your movie is to create a subfolder called
extras inside the movie folder and put all bonus content inside this folder.
Another way would be to add the string
-extras at the end of every bonus content file like
Aladdin Cut Scenes-extras.avi.
This way tinyMediaManager knows that these files are extra files for your movie and assigns them to the corresponding movie rather than creating a new movie.
How big is tinyMediaManager
Some download sites published that tinyMediaManager is only about 500kB big. This is true - for the netinstaller.
But if you run the netinstaller, tinyMediaManager will patch itself up to the latest version and its size (depending on the operating system you use) is about 20 - 25MB.
tinyMediaManager stores all data (internal database, logs, cache, ..) inside its own folder. Depending on the size of your media library this could be over 100MB.
Where should I install tinyMediaManager
If you have chosen the installer, tinyMediaManager got installed to C:\Users<username>\AppData\Roaming\tinyMediaManager. If you have chosen the portable version, simply extract it to your preferred location (e.g. the users directory, or any other hard drive/network share).
After downloading the disk image, mount it and move tinyMediaManager to your Applications directory
We'd suggest you to extract tinyMediaManager to your home directory. tinyMediaManager stores all data inside its own directory, this is why the users directory would fit best.
Errors and bugs
Scraping does sometimes not work
Sometimes we receive garbled/unparseable responses from the meta data providers (or some devices along the connection to the servers like gateways). Since we are using some sort of HTTP caching, these unparseable responses are cached for a while with a result, that a further scraping will also result in an error.
If you encounter that problem you can try to clear the cache via the menu
- Tools -> Cache -> Clear url cache
tinyMediaManager won't start
We've built tinyMediaManager as fail safe as possible. But there are always combinations of Java/OS/configurations possible which could prevent it from starting. Have a look at the OS specific sections if there are any hints for getting tinyMediaManager to start.
If the hints did not help, please collect the following logs which are produced by two steps of starting tinyMediaManager:
- The updater, which fetches the latest version of tinyMediaManager directly from the web (launcher.log)
- Launching of tinyMediaManager itself (logs/tmm.log)
In the case tinyMediaManager won't bring up his own UI, please send us the logs
via our contact form
Blank window on startup
The Installation Page has more info and a possible fix.
UI glitches with a remote desktop connection
If you use tinyMediaManager with a remote desktop connection software like RDP or VNC, Java can produce some weird glitches due a lack of 3D rendering with remote desktop connections.
In this case, try to create (or edit if it already exists) a file called extra.txt in the tinyMediaManager install directory and add the following line
and restart tinyMediaManager
tinyMediaManager is unreadable with a high DPI monitor
Java for windows does handle high DPI display different to other systems and you may need to do a minor change: increase the font size in the general settings and restart tinyMediaManager and you should be able to read everything smoothly again
tinyMediaManager can't connect to the internet viy NTLM proxy
NTLM authentification does not work within tinyMediaManager. You can use something like CNTLM to connect to the internet.
The user interface of tinyMediaManager is corrupted
Try to create (or edit if it already exists) a file called extra.txt in the tinyMediaManager install directory and add the following line
and restart tinyMediaManager
tinyMediaManager won't start with Java Portable
Java Portable provides Java in a different way than the installed one. You may need to create a batch file (.bat) inside the tinyMediaManager folder with the following content (including the dot at the end!):
cd %~dp0 <path to PortableApps>\CommonFiles\Java\bin\javaw.exe -Djava.net.preferIPv4Stack=true -Dsilent=noupdate -Dfile.encoding=UTF-8 -Dappbase=http://www.tinymediamanager.org/ -jar getdown.jar .
<path to PortableApps> with the installation path of your PortableApps.
tinyMediaManager won't start
- make sure you copied tinyMediaManager to your applications folder after downloading. For security reasons OSX executes apps from the downloads folder in a read only sandbox but tinyMediaManager needs write access (to store settings, database, logs, ...)
- make sure Java is installed (open the terminal/command line via Spotlight -> terminal) and type
java -versionthis should print the installed Java version of your system (1.6, 1.7 or 1.8). If the program is not found, please install the latest Java version
- if Java is installed, but tinyMediaManager won't start, there could be a Java library in your /Library/Java/Extensions which interfere with tinyMediaManager. In this case try to create a file called
extra.txtin your tinyMediaManager folder (right click the tinyMediaManager.app -> Show package contents -> navigate to Contents - Resources - Java) with the following content:
- if tinyMediaManager still won't start, please have a look at the FAQ for reporting bugs
Using SWT on OSX crashes tinyMediaManager
There are several different versions of Java (1.6 from Apple and 1.7/1.8 from Oracle) out for OSX combined with several different versions of OSX itself (10.5 - 10.10). On some combinations of these two components will not work with the AWT-SWT bridge. The short answer is: if putting the swt.jar inside the lib folder does not work in your tinyMediaManager installation, there is nothing we can do to make it work
tinyMediaManager won't start
Some Linux distributions only provide a headless version of Java per default (this is the core part of Java without any UI libraries). Make sure you also have the UI part of Java installed.
libmediainfo does not load
libmediainfo is a native library which has to be compiled for every distribution/release/arch. We ship a pre packaged version of libmediainfo along with tinyMediaManager which should be suitable for most Linux users. If that version does not work for you, please try to install libmediainfo from your distribution (that is being loaded as fallback when the shipped one does not load)
Problems importing movies with special characters in their name
If you have problems to import movies with a special character in their name, check if the locale en_US.UTF-8 has been generated on your system. If not, have a look at the documentation of your linux distribution how to generate them. On Arch Linux/Manjaro the steps would be:
- login as root
- uncomment the line
en_US.UTF-8 UTF-8in the file
- logout and login again
Ugly font rendering in Linux
Due to a bug in the JVM, fonts are drawn rather ugly in Linux desktop environments. We did as much improvements (with rendering parameters) as possible. If using a newer JVM (v1.8) is not possible for you, there is the option to install a "patched JVM". There are packages for Ubuntu or Arch Linux. You may find similar packages for other Linux distributions as well.
Native file chooser is not available
To use the native file chooser (GTK) you need at least Java 8 with JavaFX. Either use the Oracle runtime or OpenJDK with the OpenJFX enhancement (available for most distributions).