Peke at 23:47, 8 May 2011

2011-05-08T23:47:47Z

← Older revision		Revision as of 23:47, 8 May 2011
Line 11:		Line 11:
	For each client, simply install MediaMonkey and:		For each client, simply install MediaMonkey and:

	# [[Adding Existing Files to the Library\|Add Folders]] that are shared by other networked machines		# [[{{WebHelp:Links\|Adding Existing Files to the Library}}\|Add Folders]] that are shared by other networked machines
	# [[Adding Existing Files to the Library\|Set the File Monitor]] to monitor the shared folders for changes so that any changes made by other users to Tracks and their associated Tags will be detected, and the database updated appropriately.		# [[{{WebHelp:Links\|Adding Existing Files to the Library}}\|Set the File Monitor]] to monitor the shared folders for changes so that any changes made by other users to Tracks and their associated Tags will be detected, and the database updated appropriately.

	The key issue to remember is that changes are detected based on the actual files and their tags, which means that edits to Track Properties by other users are detected only if they are saved to the Track's Tags. Thus in this scenario it is advisable not to take advantage of [[About Track Properties\|fields that are not saved to Tags]], unless you don't mind the fact that the data will be lost. For some data (e.g. volume leveling coefficients) this is a non-issue, however, for other fields it may be of concern.		The key issue to remember is that changes are detected based on the actual files and their tags, which means that edits to Track Properties by other users are detected only if they are saved to the Track's Tags. Thus in this scenario it is advisable not to take advantage of [[{{WebHelp:Links\|About Track Properties}}\|fields that are not saved to Tags]], unless you don't mind the fact that the data will be lost. For some data (e.g. volume leveling coefficients) this is a non-issue, however, for other fields it may be of concern.
	{{WebHelpFooter}}		{{WebHelpFooter}}

Peke: Created page with " {{WebHelpHeader|Multi-user Environments}} MediaMonkey can be configured for use in multi-user networked environments. There are two possible approaches to this: # Multiple Cli..."

2011-05-05T22:27:06Z

Created page with " {{WebHelpHeader|Multi-user Environments}} MediaMonkey can be configured for use in multi-user networked environments. There are two possible approaches to this: # Multiple Cli..."

New page

{{WebHelpHeader|Multi-user Environments}}
MediaMonkey can be configured for use in multi-user networked environments. There are two possible approaches to this:

# Multiple Clients each using an independent Library database
# Multiple clients sharing a common Library database

MediaMonkey presently supports the first option, although numerous users have had success with the second option--see the [http://www.mediamonkey.com/support/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=49&nav=0,2| FAQ] for details.

== Multiple Clients / Independent Library Databases ==

For each client, simply install MediaMonkey and:

# [[Adding Existing Files to the Library|Add Folders]] that are shared by other networked machines
# [[Adding Existing Files to the Library|Set the File Monitor]] to monitor the shared folders for changes so that any changes made by other users to Tracks and their associated Tags will be detected, and the database updated appropriately.

The key issue to remember is that changes are detected based on the actual files and their tags, which means that edits to Track Properties by other users are detected only if they are saved to the Track's Tags. Thus in this scenario it is advisable not to take advantage of [[About Track Properties|fields that are not saved to Tags]], unless you don't mind the fact that the data will be lost. For some data (e.g. volume leveling coefficients) this is a non-issue, however, for other fields it may be of concern.
{{WebHelpFooter}}

WebHelp:Multi-user Environments/4.0 - Revision history

Peke at 23:47, 8 May 2011

Peke: Created page with " {{WebHelpHeader|Multi-user Environments}} MediaMonkey can be configured for use in multi-user networked environments. There are two possible approaches to this: # Multiple Cli..."