为什么图书馆里有重复的书以及如何修复

当 Windows 版 MediaMonkey 扫描文件夹时,它只会添加与现有文件名不匹配的文件,否则它只会使用标签中存在的文件属性的任何更改来更新文件。在某些情况下,Windows 版 MediaMonkey 库中可能会出现重复项:

  • 你的电脑实际上存储了该文件的多个副本
    • 您需要选择要从 PC 中删除哪些重复副本。没有自动方法可以为您从 PC 中删除重复项,因为无法保证保留最佳副本或不删除您想要保留的略有不同的版本。虽然耗时,但这是确保您不会删除您真正想要保留的曲目的最安全的方法。
    • 在媒体树中的收藏夹(如音乐) >要编辑的文件节点中,您可以使用:
      • 重复标题节点将列出所有具有相同标题(MediaMonkey 5+)、相同标题和艺术家(MediaMonkey 4)的文件。
      • 重复内容节点将列出所有具有相同音频内容的文件。要使重复内容正常工作,您必须在工具 > 选项 >下启用分析文件重复项(需要额外时间)选项。然后,当您重新扫描文件时,将为每个文件生成一个哈希值,用于确定重复内容。
      • 重复标题/艺术家(Windows 5+ 版 MediaMonkey)节点将列出具有相同标题和艺术家的所有文件。
    • MediaMonkey for Windows 4 具有以下流行的插件来帮助进行重复管理: Bex 的 Advanced Duplicate Find & FixTrixmoto 的 Duplicate Report 。请参阅其文档以了解如何使用这些插件。
  • 文件被移出/重命名到 Windows 版 MediaMonkey 之外,然后被扫描到库中。Windows 版 MediaMonkey 会将它们视为单独的新文件。
    • 为防止这种情况,请使用 Windows 版 MediaMonkey移动/重命名文件,或在 MediaMonkey 之外移动/重命名文件时使用文件夹监控
    • 无效链接将显示已移动/重命名文件的旧副本。您可以从那里删除它们,但这会从与其关联的播放列表中删除这些文件,并删除它们的播放历史记录。
  • 包含文件的硬盘已被替换或移至新电脑,并在新驱动器/电脑上扫描文件。
    • Windows 版 MediaMonkey 使用 DriveID 来确定文件位于哪个驱动器上。即使使用相同的驱动器号,每个硬盘的 DriveID 也是不同的。
    • 要在 Windows 5+ 版 MediaMonkey 中修复,请右键单击媒体树中的收藏(如音乐) >位置节点中的驱动器,然后选择媒体属性以将其连接到 PC 上的正确驱动器。在 Windows 4+ 版 MediaMonkey 中,您还可以使用定位移动/丢失的文件。MediaMonkey 4 还可以使用数据库插件中的更新文件位置
    • 为防止重复,请确保在修复驱动器 ID 之前没有进行任何扫描(包括文件夹监控)。
    • 如果旧驱动器和新驱动器确实有重复项,您可以从收藏(如音乐) >位置节点的库中删除新驱动器,然后修复旧驱动器。
  • MediaMonkey 4 中使用了数据库插件中的文件更新位置,但在使用插件之前已在新位置扫描了文件
    • 如果您使用此插件,请确保在更新库中文件的位置之前已禁用文件夹监控。否则,Windows 版 MediaMonkey 最终会从工作位置扫描文件,然后插件会修复非工作文件,导致库中每个文件有 2 个条目。
    • 如果发生这种情况,您可以从库中删除新位置的文件(确保文件夹监视已被禁用),然后使用插件修复旧文件。
  • 网络共享/NAS 上的文件位于映射驱动器上,并且在 DriveID 更改后重新扫描了这些文件
    • 众所周知,Windows 有时会更改映射驱动器的 DriveID。我们建议使用网络位置的 UNC 路径而不是映射驱动器来防止这种情况。请参阅上文以获取与新驱动器 ID 相关的文件。
  • 已扫描包含垃圾桶的位置
    • 这种情况可能发生在 NAS 设备上,因为编辑文件后,这些文件最终会被放入回收站。为防止这种情况发生,请确保媒体文件不在包含垃圾桶的位置(垃圾桶通常位于根目录中)。为您的媒体文件创建一个子文件夹,并且只选择它进行扫描,就可以解决这个问题。

Applies to: ,

Translated automatically (see original)

Why are there Duplicates in the Library and how to Fix

When MediaMonkey for Windows scans a folder, it only adds files if they don’t match an existing filename, otherwise it just updates the files with any changes to the file properties that exist in the tags. Under certain scenarios you can end up with duplicates in the MediaMonkey for Windows library:

  • Your PC actually has multiple copies of the file stored
    • You’ll need to select which duplicates copies you want to remove from your PC. There is no automatic method that will remove duplicates from the PC for you as there’s no way to guarantee that the best copy is kept or that slightly different version you meant to keep aren’t removed. Though time-consuming, it is the safest way to ensure that you don’t delete tracks that you actually wanted to keep.
    • In the Collection (like Music) > Files to Edit node in the Media Tree you can use the:
      • Duplicate Titles node which will list all files with the same Title (MediaMonkey 5+), the same Title and Artist (MediaMonkey 4).
      • Duplicate Content node which will list all files with the same audio content. For Duplicate Content to work, you must have the option Analyze files for duplicates (takes extra time) enabled under Tools > Options > Library. Then when you do a rescan of the files a hash will be generated for each one, which is used for the determine duplicate content.
      • Duplicate Titles/Artists (MediaMonkey for Windows 5+) node which will list all files with the same Title and Artist.
    • MediaMonkey for Windows 4 has the following popular Addons to help with duplicate management: Advanced Duplicate Find & Fix by Bex and Duplicate Report by Trixmoto. Consult their documentation on how to use these.
  • Files were moved/renamed outside of MediaMonkey for Windows and then scanned into the library. MediaMonkey for Windows will see them as a separate new files.
    • To prevent this use MediaMonkey for Windows to move/rename the files or use Folder Monitoring while moving/renaming files outside of MediaMonkey.
    • Dead Links will show the old copies of the moved/renamed files. They can be deleted from there, but this removes the files from any Playlists they’re associated with as well as removing their Play History.
  • The hard drive containing the files was replaced or moved to a new PC and the files were scanned on the new drive/PC.
    • MediaMonkey for Windows uses DriveID to determine on what drive files are located. This is different for each hard drive even if the same Drive Letter is used.
    • To fix in MediaMonkey for Windows 5+, right click on the drive in the Collection (like Music) > Location node in the Media Tree and select Media Properties to connect it to the correct drive on your PC. In MediaMonkey for Windows 4+ you can also use Locate Moved/Missing Files. MediaMonkey 4 also can also use the Update Location of Files in Database Addon.
    • To prevent duplicates make sure no scanning (including Folder Monitoring) is done before fixing the driveID.
    • If you do have duplicates from the old drive and new drive you can remove the new drive from the library from the Collection (like Music) > Location node and then fix the old drive.
  • The Update Location of Files in Database Addon was used in MediaMonkey 4, but scanned files in their new location before using the Addon
    • If you use this Addon, make sure you have Folder Monitoring disabled before you update the location of files in the library. Otherwise MediaMonkey for Windows ends up scanning the files from the working location and then the Addon fixes the non-working files resulting in 2 entries for each file in the library.
    • If this happened you can remove the files from the new location (make sure Folder Monitoring is disabled) from the library and then use the Addon to fix the old files.
  • Files on a network share/NAS are located on a Mapped Drive and the files were rescanned after the DriveID changed
    • Windows is known to occasionally change the DriveID for Mapped Drives. We recommend using the UNC Path for the network Location instead of a Mapped Drive to prevent this. See above for getting the files connected to the new driveID.
  • A location that includes the trashcan was scanned
    • This can happen for NAS devices which can end up with files in the recycle bin when they’re edited. To prevent this make sure the media files are not in a location that includes the trashcan (which often is in the root). A sub-folder, and only selecting it for scanning, for your media files will solve this.

Applies to: ,

Hide original

这篇文章有帮助吗?