WebHelp:Multi-user Environments/4.0/es: Difference between revisions
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
{{WebHelpHeader|Ambientes Multi-usuario}} | {{WebHelpHeader|Ambientes Multi-usuario}} | ||
MediaMonkey puede ser configurado para: | MediaMonkey puede ser configurado para uso en ambientes de red multi-usuario. Hay dos posibles enfoques para realizar esto: | ||
# Varios clientes usando una base de datos de un Catálogo independiente | |||
# Varios clientes compartiendo una base de datos de un Catálogo en común | |||
# | |||
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. | 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. |
Revision as of 16:19, 17 May 2012
MediaMonkey puede ser configurado para uso en ambientes de red multi-usuario. Hay dos posibles enfoques para realizar esto:
- Varios clientes usando una base de datos de un Catálogo independiente
- Varios clientes compartiendo una base de datos de un Catálogo en común
MediaMonkey presently supports the first option, although numerous users have had success with the second option--see the FAQ for details.
Multiple Clients / Independent Library Databases
For each client, simply install MediaMonkey and:
- Add Folders that are shared by other networked machines
- 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 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.
English • Deutsch • español • français |
Additional Help: Knowledge Base | Forum | MediaMonkey Support | MediaMonkey for Android Help | MediaMonkey 5 Help | MediaMonkey 4 Help