Differences

This shows you the differences between two versions of the page.

--- tutorials:musicmaster:nexus-database-connection [2018/10/11 14:18] – [Advanced Settings] tw
+++ tutorials:musicmaster:nexus-database-connection [2020/11/23 16:46] (current) – [Editing Music] tw
@@ Line 18: / Line 18: @@
 Please check with MusicMaster support if you are unsure whether your MusicMaster installation provides the above requirements.
+===== Nexus API Configuration =====
 Before you can configure the database connection, you must set up the Nexus API in the mAirList configuration. In particular, the following fields must be mapped correctly between MusicMaster and mAirList:
@@ Line 92: / Line 94: @@
   - Manually, by creating the song in MM and entering all details by hand. Make sure that the exact file name is entered into the corresponding field.
   - Automatically using the //Nexus Importer// tool found in the mAirList Start Menu group. This tool will fetch a list of all files contained in the MusicMaster library, then scan the audio folder for new files, and add the files to the MusicMaster library. Any existing file tags (ID3 etc.) will be parsed and translated to the respective MusicMaster fields.
+Beginning with mAirList 6.3.8, the Nexus Importer can also be integrated into the MusicMaster GUI by the means of a [[https://musicmaster.com/?p=1379|User Button]] by adding the following to MusicMaster.ini:
+<code>
+[UserButton1]
+Tooltip=Look for New Files in mAirList
+Image=C:\mAirList\Icons\nexusimporter.ico
+App=C:\Program Files (x86)\mAirList 6.3\mAirList.exe
+CommandScript="-mode nexusimporter -songid " & mm.GetField(1)
+</code>
+If you are working with more than one MusicMaster database, you must additionally pass the name of the database on the command line:
+<code>
+CommandScript="-mode nexusimporter -database """ & mm.DatasetLogo & """ -songid " & mm.GetField(1)
+</code>
+In that case, all databases must be registered in the Nexus API configuration of mAirList. In order to identify the database, mAirList will first compare the value to the Nexus ID, then to the alias set in the Nexus API configuration.
+===== Editing Music =====
+Generally, all library maintenance should be performed from inside MusicMaster.
+There are a few things however that cannot be edited easily from MusicMaster. In particular the cue markers, as MusicMaster does not have any built-in editing tool.
+If you need to edit any fields that are not easily accessible from MusicMaster, you have the option to use mAirList's //File Tagger// tool, found in the mAirList Start Menu Group. The File Tagger is basically a browser (as found in the main playout window) and an item properties dialog (the same that you get when you double-click an item in the playout).
+In the browser part, click //Add// and add a new //Database// pane. This will give you access to all MusicMaster categories and the songs inside them. Double-click a song to edit its properties. When you are finished, **don't forget to click //Export -> Export to Database//** in order to store your changes permanently inside the MusicMaster library.
+Starting with mAirList 6.3.8, another way to edit items has been established: The //Nexus Editor//, integrated into MusicMaster via a User Button:
+<code>
+[UserButton2]
+Tooltip=Edit song in mAirList
+Image=C:\mAirList\Icons\nexuseditor.ico
+App=C:\Program Files (x86)\mAirList 6.3\mAirList-tmp.exe
+CommandScript="-mode nexuseditor -songid " & mm.GetField(1)
+</code>
+When working with more than one database, you must pass the database name on the commandline, and it must match the Nexus database ID or alias set in the config (see comments above):
+<code>
+CommandScript="-mode nexuseditor -database """ & mm.DatasetLogo & """ -songid " & mm.GetField(1)
+</code>
 ===== Regionalization =====