您的 MediaMonkey 库可以通过多种方式共享。您可以使用 DLNA (UPnP) 共享媒体文件和播放列表，以便在本地网络上进行流式传输，将您的媒体和播放列表同步到便携式设备或共享实际数据库文件。
在本地网络上流媒体文件
通过主菜单中的“工具”>“选项”>“媒体共享”，您可以设置 MediaMonkey，以便网络上任何支持 DLNA 的客户端都可以使用您的媒体文件。有关 Windows 版 MediaMonkey 的 DLNA 共享的更多信息，请参阅在线帮助：帮助：流式传输到其他设备 (UPnP / DLNA) 。客户端无法通过 DLNA 修改媒体文件。
共享您的媒体文件
您可以选择直接在本地网络上共享媒体文件。在这种情况下，您可以让每台电脑上的 MediaMonkey 直接扫描媒体文件并直接播放，每个用户管理自己的媒体库。此方法不允许播放历史记录和播放列表共享。每个用户都可以更新元数据（除非您将文件设为只读），这会影响所有其他用户。
同步
通过同步，您可以将媒体文件和播放列表复制到便携式设备或云服务 (MediaMonkey 5)，这样设备就可以拥有本地副本，而无需依赖本地网络连接来访问 MediaMonkey。对于安装了 MediaMonkey for Android 的 Android 设备和 Apple 设备，这包括将某些元数据同步回 MediaMonkey 库的功能。
共享 MediaMonkey 数据库
默认情况下，MediaMonkey 的MediaMonkey.ini文件配置为单个用户访问本地存储的数据库。但是，可以更改这些设置，以便多个用户可以共享存储在公共位置的数据库。
要设置这样的共享环境：
- 在安装了 MediaMonkey 的机器上，将包含音乐的网络位置粘贴到“扫描文件夹”对话框中，以扫描该位置。最好扫描 UNC 路径，而不是映射驱动器。例如
\ip _address\path（几乎总是有效）
\computer_name\path（通常有效）
J：（映射的网络驱动器有时无法被识别） - 关闭 MediaMonkey（这样它就不会覆盖任何更改）
- 备份MediaMonkey.ini文件。
- 如果要将同一台 PC 上的数据库共享给不同的 Windows 用户，请将MediaMonkey.ini文件移至 Program Files/MediaMonkey 目录。这将使所有用户拥有相同的 MediaMonkey 设置，但是，您必须确保所有用户都有权读取/写入此目录。
- 将 MediaMonkey 数据库保存到共享文件夹，例如
C:\MM 共享库\mm.db 或 \ip _address\path\mm.db (\computer_name\path\mm.db) - 对于访问数据库的每台机器，编辑MediaMonkey.ini文件，以便它使用数据库的自定义位置。
- 启动 MediaMonkey 以确保您的 MediaMonkey 数据库文件具有正确设置权限，以便所有用户都可以读取/写入数据库。
NOTES
Your MediaMonkey library can be shared in various ways. You can use DLNA (UPnP) to share your media files and Playlists for streaming on the local network, Sync your media and Playlists to portable devices or share the actual database file.
Stream Media Files on the Local Network
Via Tools > Options > Media Sharing from the Main Menu you can setup MediaMonkey to make available your media files to any DLNA capable client on your network. For more on DLNA sharing from MediaMonkey for Windows see the Online Help: Help: Streaming to other Devices (UPnP / DLNA). Clients can’t modify media files over DLNA.
Sharing your Media Files
You can choose to just share your media files on the local network directly. In this scenario you’d have MediaMonkey on each PC scan the media files directly and play them directly and each user manages their own library. This method won’t allow for play history and playlist sharing. Each user could update metadata (unless you make files read-only) and this affects all other users.
Synchronization
With synchronization you can copy media files and playlists to portable devices or cloud services (MediaMonkey 5) which allows the device to have a local copy and not rely on a local network connection to MediaMonkey. For Android devices with MediaMonkey for Android and Apple devices this includes the ability to sync back certain metadata to your MediaMonkey library.
Sharing the MediaMonkey Database
By default, MediaMonkey’s MediaMonkey.ini file is configured for single user access to a locally stored database. However, it is possible to change these settings so that multiple users can share a database stored to a common location.
To set up such a shared environment:
- On a machine that has MediaMonkey installed, scan a network location that will contain your music by pasting it into the Scan Folders dialog. It is preferable to scan a UNC path rather than a mapped drive. e.g.
\ip _address\path (almost always works)
\computer_name\path (often works)
J: (mapped network drive sometimes fail to be recognized) - Close MediaMonkey (so that it doesn’t overwrite any of the changes)
- Back up the MediaMonkey.ini file.
- If sharing the database on the same PC to different Windows Users, move the MediaMonkey.ini file to the Program Files/MediaMonkey directory. This will cause all users to have the same MediaMonkey settings, however, you must make sure that all users have permission to read/write to this directory.
- Save the MediaMonkey database to a shared folder e.g.
C:\MM Shared library\mm.db or \ip _address\path\mm.db (\computer_name\path\mm.db) - For each machine that is accessing the database, edit the MediaMonkey.ini file so that it uses the customized location of the database.
- Start MediaMonkey to ensure that your MediaMonkey database file has correctly set permissions so that all users can read/write to the database.
NOTES
- MediaMonkey uses SQLite as the back end database, and it isn’t designed as a multi-user/networked database, so although this approach works, it is unsupported. Test this approach in your local environment carefully before deploying. More about SQLite in a networked/multi-user environment:
http://www.sqlite.org/whentouse.html
http://www.sqlite.org/lockingv3.html - MediaMonkey accesses the database often which can result in a slower experience when accessing the database over a networked connection. To improve performance, MediaMonkey can be configured to perform certain database operations in memory instead of over the network. This improves performance, but reduces reliability of the SQLite database primarily if the connection to the DB is lost while a database operation is in progress (e.g. if an external HD containing the DB is removed or in case of a WiFi/Wired connection loss). To configure this, make the following change in each instance of MediaMonkey.ini (the default value is 0):
[SYSTEM]
SQLitePageToMemory=1;
- MediaMonkey Server is in development which would also allow for a shared database between different installation of MediaMonkey 5: /forum/viewforum.php?f=31
- If the files are greyed out on one of the machines when viewing or playing them, see: Why is Music Greyed Out / Fails to Play?
Applies to: MMW4, MMW5+
Hide original
