tinyMediaManager won’t start

  • make sure you copied tinyMediaManager to your applications folder after downloading. For security reasons macOS 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 -version this 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.txt in your tinyMediaManager folder (right click the tinyMediaManager.app -> Show package contents -> navigate to Contents - Resources - Java) with the following content: -Djava.ext.dirs=
  • if tinyMediaManager still won’t start, please have a look at the FAQ for reporting bugs

v4 ships its own Java, so all Java related points from above only apply to v3

macOS Big Sur recently changed the behavior of handling programs and their dialogs when in full screen mode. There is a problem with that behavior in all recent Java versions (see the Java bug report).

There is a workaround for that problem by deactivating this behavior for Java based programs:

  1. Open a terminal
  2. Enter the command defaults write net.java.openjdk.cmd AppleWindowTabbingMode manual
  3. Restart tinyMediaManager

Mounted Drives are not accessible after upgrading to Big Sur

macOS Big Sur did some changed to security policies and now tinyMediaManager isn’t allowed to access several files. To allow tinyMediaManager to access your files do the following steps:

  1. Go to System Preferences -> Security & Privacy -> Privacy and select „Files and Folders“
  2. Add tinyMediaManager to the list of allowed apps