Some Files Don’t Scan into the MediaMonkey Library

There are several situations in which files may not scan into the MediaMonkey Library.

Verify if Files are Missing from MediaMonkey Library

First though, make sure the files really aren’t in MediaMonkey. They could be in a different Collection than expected. To do this, use the Entire Library > Location node in the Media Tree and navigate to the folder (if in Library) of where the missing files are located on your PC. If the files aren’t there continue below for troubleshooting steps.

Common Configuration Issues

  1. The location containing the files wasn’t configured to be scanned. Make sure that the location is entered correctly in the Add/Rescan Files dialog.
  2. The files were added to your drive after a scan was initiated in MediaMonkey. If you want MediaMonkey to regularly update the library to reflect changes on your drive, set Locations to be scanned on a Schedule of ‘At startup & Continuously’ in the Add/Rescan Files dialog.
  3. MediaMonkey only scans file formats that it supports AND that have been enabled for scanning. If you’re trying to scan a format that isn’t natively supported, there may be a plugin to add support for that format. After installation of the plugin make sure you enable the format in the Add/Rescan Files dialog.
  4. Settings under Tools > Options > Library from the Main Menu include options to ignore short files which will cause short files from being scanned.

Other Issues

  1. MediaMonkey will ignore files in folders used for other features in MediaMonkey. Depending on your version of MediaMonkey this can include the Virtual CD, Previews and UPnP Cache folders.
  2. MediaMonkey will ignore files that are set as or are stored in folders set as hidden in the file system.
  3. MediaMonkey 4 and older will not scan files with a Path exceeding 248 characters. Shorten the Path to have the files scanned by MediaMonkey 4 and older. This limitation doesn’t exist for MediaMonkey 5.
  4. MediaMonkey can fail to scan files when the extension of the file is incorrect. For example some MP2 files are given the incorrect MP3 extension.
  5. Corrupted files can be skipped on scanning. You can attempt to play the file with MediaMonkey from File Explorer to see if playback also fails.
  6. If all files from a drive are ignored on scanning make sure the drive letter isn’t set under IgnoreDriveLetters= in the MediaMonkey.ini.
  7. Some NAS devices (notably Infrant hardware) seem to stall and/or fail to scan some files due to network-related issues. In such cases, setting the device’s TCP MTU to 1492 and disabling jumbo frames on the device may solve the problem.

Related: Why are files missing from the Library?

Applies to: ,

Was this article helpful?