Why are some files Greyed Out / Fail to Play?

When browsing the Library or trying to play files MediaMonkey will display files in grey if they’re in the database, but not playable either because:

  1. The files are inaccessible.
  2. They’re in an unsupported format

If tracks don’t appear grey but aren’t playing or are playing incorrectly, it’s likely an output-related problem (related to the equalizer, DSPs, volume leveling, or the Output plug-in), an issue discussed at: “No Sound is playing / Sound is corrupted“.

Files are Inaccessible

Inaccessible files will also appear in the ‘Dead Links’ nodes (e.g. (like Entire Library > Files to Edit > Dead Links node) where they can be fixed. Files can become inaccessible if:

  1. Files have been moved using a tool other than MediaMonkey and Folder Monitoring isn’t configured to automatically update the library to reflect such changes.
    • If you have MediaMonkey Gold, select all the greyed out tracks and use File > Locate moved/missing tracks. This will find matching tracks based on file size AND timestamp, or track metadata.
    • If you don’t have MediaMonkey Gold, delete the old entries, and scan the location to which the tracks have been moved.
    • Configure Folder Monitoring to prevent this from recurring.
  2. The drive containing media files has been changed and the new drive has a driveID that differs from the old drive. To correct this, first back up your database and then try one of the following:
    • In MediaMonkey 5+ you can use right click on the drive (Collection Name (e.g. Music) > Location > Drive Letter (e.g. D:)) select ‘Media Properties’ from the Context Menu to point the drive to the correct location.
    • If you have MediaMonkey Gold, select all the greyed out tracks and use File > Locate moved/missing tracks. This will find matching tracks based on file size AND timestamp, or track metadata.
    • In MediaMonkey 4 use the third party Update Location of Files in Database Addon.
  3. Files are stored on a removable drive that is not connected or on a network location that is inaccessible. Resolve by connecting the drive or the network location.
  4. Files are stored to a networked drive/mapped drive to which MediaMonkey doesn’t have permissions. e.g. if the drive is mapped with one set of credentials, but MediaMonkey is running under a different set of credentials. Resolve by giving MediaMonkey permission to access the location.
  5. A network path is mapped to a drive letter (e.g. J:). In some cases Windows changes the driveID which is what MediaMonkey uses to find the drive (instead of drive letter). The solution is to access your files using the UNC Path instead of a mapped drive:
    \\ip _address\path (always works)
    \\computer_name\path (often works)
    In MediaMonkey 5+ you can use right click on the drive in the Collection’s > Location node and use Media Properties from the Context Menu to point the drive to the correct drive.
  6. Files are located on drive A or B and MediaMonkey isn’t able to access them. To fix this remove the drive letter from IgnoreDriveLetters=AB in MediaMonkey.ini (this only affects those who’ve installed any version of MediaMonkey prior to MediaMonkey 4.1).

Files are in an Unsupported Format

MediaMonkey supports most common audio formats, but audio formats may not be supported if:

  1. No audio formats can be played because the version of Windows used is Windows Windows N version, which doesn’t include multimedia components. This can be corrected by installing the missing codecs.
  2. It can occur because of audio plugin incompatibilities, DRM (digital rights management) or because required codecs are missing. See:
    WMA Tracks fail to Play
    MP3 Tracks Fail to Play
    M4A Playback
    CDs fail to play

Applies to: ,

Was this article helpful?