Differences

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

--- tutorials:musicmaster:start [2017/08/21 10:50] – [mAirListDB synchronization via the Nexus API] tw
+++ tutorials:musicmaster:start [2019/07/09 16:18] (current) – external edit 127.0.0.1
@@ Line 5: / Line 5: @@
 mAirList offers three different ways of integration with MusicMaster.
-===== mAirListDB synchronization via files =====
+| ^ mAirListDB required ^ Nexus API required ^ Primary Database ^
+^ 1. Sync via files | yes | yes | mAirList |
+^ 2. Sync via Nexus | yes | - | mAirList |
+^ 3. Direct Nexus connection | - | yes | MusicMaster |
+===== Option 1: mAirListDB synchronization via files =====
-In this traditional setup, mAirList and MusicMaster communicate through text file exports - [[reference:mairlistdb_library_csv_import_export|CSV]] (for mAirListDB library export to MusicMaster) and [[reference:text_playlist_import_format_specification|TPI]] (for log export from MusicMaster to mAirListDB).
+In this traditional setup, mAirList and MusicMaster communicate through text file exports - [[reference:mairlistdb_library_csv_import_export|CSV]] (for mAirListDB library export to MusicMaster) and [[reference:text_playlist_import_format_specification|TPI]] (for log export from MusicMaster to mAirListDB). Songs are added to mAirListDB first, then exported to MusicMaster.
-[[:filesync|See full tutorial for synchronization via files.]]
+[[mairlistdb-sync-files|See full tutorial for synchronization via files.]]
-===== mAirListDB synchronization via the Nexus API =====
+===== Option 2: mAirListDB synchronization via the Nexus API =====
 This is pretty much like like file synchronization, but uses the MusicMaster Nexus API to synchronize library and playlists.
-[[:mairlistdb-sync-nexus|See full tutorial for synchronization via Nexus.]]
+[[tutorials:musicmaster:mairlistdb-sync-nexus|See full tutorial for synchronization via Nexus.]]
-===== Direct Nexus database connection =====
+===== Option 3: Direct Nexus database connection =====
+This is a very different approach to those above, as it does not involve any mAirListDB database. Instead, the mAirList playout process attaches itself directly to the Nexus server, using MusicMaster as the library and scheduling backend. This approach works best for 24/7 automated music channels, as it gets rid of the constant synchronization -- all library maintenance and scheduling is done in MusicMaster.
+[[nexus-database-connection|See full tutorial for Nexus database connection.]]