WebHelp:Multi-user Environments/4.0/es: Difference between revisions
No edit summary |
|||
| Line 8: | Line 8: | ||
[http://www.mediamonkey.com/support/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=49&nav=0,2| FAQ] para más detalles. | [http://www.mediamonkey.com/support/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=49&nav=0,2| FAQ] para más detalles. | ||
== | == Múltiples Clientes / Catálogo de Bases de Datos Independientes == | ||
Para cada cliente simplemente instale MediaMonkey y: | Para cada cliente simplemente instale MediaMonkey y: | ||
# [[{{WebHelp:Links|Adding Existing Files to the Library}}| | # [[{{WebHelp:Links|Adding Existing Files to the Library}}|Agregar Carpetas]] que son compartidas por otros equipos de la red | ||
# [[{{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. | # [[{{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 [[{{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. | 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}} | ||
Revision as of 17:00, 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 soporta actualmente la primera opción, aunque muchos usuarios han tenido éxito usando la segunda opción--vea FAQ para más detalles.
Múltiples Clientes / Catálogo de Bases de Datos Independientes
Para cada cliente simplemente instale MediaMonkey y:
- Agregar Carpetas que son compartidas por otros equipos de la red
- 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
