tutorials:musicmaster:mairlistdb-sync-files
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
tutorials:musicmaster:mairlistdb-sync-files [2017/08/21 12:26] – [MusicMaster and mAirListDB Synchronization via Files] tw | tutorials:musicmaster:mairlistdb-sync-files [2019/07/09 16:18] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 24: | Line 24: | ||
===== Library Synchronization ===== | ===== Library Synchronization ===== | ||
+ | This section is about library synchronization, | ||
+ | |||
+ | ==== Export from mAirListDB ==== | ||
+ | |||
+ | The first step is to export the mAirListDB library, or part of it, as a CSV file. | ||
+ | |||
+ | To create the file, use one of the commands in the mAirListDB app main menu under //Database -> Export//. You can export the entire library, only the current view (folder, item type filter, etc.), or the current selection. | ||
+ | |||
+ | We use the [[reference: | ||
+ | |||
+ | MusicMaster requires that you use **a fixed name for the CSV file**. In our example, we use '' | ||
+ | |||
+ | ==== Import into MusicMaster ==== | ||
+ | |||
+ | Before MusicMaster can import the CSV file you created, you must set up the library synchronization definition to MusicMaster. This must only be done once. | ||
+ | |||
+ | The definition is in the file '' | ||
+ | |||
+ | In particular, you must specify the folder and name of the CSV file that you created with mAirList: | ||
+ | |||
+ | [Import] | ||
+ | SourceType=AsciiD | ||
+ | SourcePath=C: | ||
+ | SourceSpec=LibraryExport.csv | ||
+ | |||
+ | The most important thing is to adjust the mapping of the MusicMaster fields (with their numeric IDs) to the column names in the CSV file: | ||
+ | |||
+ | [LibImportMapAdd] | ||
+ | Map1=101, | ||
+ | Map2=161, | ||
+ | Map3=272, | ||
+ | Map4=103, | ||
+ | Map5=105, | ||
+ | Map6=102, | ||
+ | Map7=104, | ||
+ | etc. | ||
+ | | ||
+ | Note that there are two sections that must be edtied: '' | ||
+ | |||
+ | Once the .def file is correctly set up, you can open MusicMaster, | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | Now all songs from your CSV file should be added to or updated in the MusicMaster database. | ||
===== Schedule Export (and Import) ===== | ===== Schedule Export (and Import) ===== | ||
+ | This section is about scheduling export, that is, exporting the music log created in MusicMaster and loading it into the mAirListDB playlist view. | ||
+ | |||
+ | We assume that you have used the Automatic Scheduler in MusicMaster to create some music schedules. We use one export file per day, so you should have scheduled at least one entire day that we are now going to export. | ||
+ | |||
+ | The file format being used is mAirList' | ||
+ | |||
+ | ==== MusicMaster setup ==== | ||
+ | |||
+ | Before you can export the schedule from MusicMaster, | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | Again, we recommend that you let the MusicMaster support assist you in this step. We will provide a template file that will help you to create the definitions quickly. | ||
+ | |||
+ | The crucial part is the 4th column for the three " | ||
+ | |||
+ | Also make sure that, in the Design Properties, the //Output filename pattern// must be set to '' | ||
+ | |||
+ | ==== Perform the export ==== | ||
+ | |||
+ | Once the design is ready, save it, then go to //Dataset -> Schedule -> Export -> Export to Automation//, | ||
+ | |||
+ | 00: | ||
+ | 00: | ||
+ | 00: | ||
+ | 00: | ||
+ | 00: | ||
+ | ... | ||
+ | | ||
+ | The first column is the start time, the second the timing (" | ||
+ | |||
+ | Hint: If the ID column is missing or empty, you have selected an incorrect field for the 4th column in the Export Designer; also check that the ID field has been propagated correctly with the mAirListDB Internal IDs during CSV import. | ||
+ | |||
+ | ==== mAirListDB setup ==== | ||
+ | |||
+ | Now that we have created the TPI files, we can set up the import in mAirListDB, using appropriate hour and music templates. **Because even when we use MusicMaster as an external music scheduling software, we will still use the mAirListDB Mini Scheduler in order to import the TPI files into the mAirListDB playlist!** We will just advise the Mini Scheduler to pick up the TPI files rather than using the internal music scheduling function. (In fact, you can even combine the internal scheduler and TPI import, e.g. use the hour template to schedule fixed elements like news breaks and advertising, | ||
+ | |||
+ | So the first thing to do is to set up one or more Hour Templates in mAirListDB, as described in the [[tutorials: | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | Note: Use //Music block// instead of //Fill with music// in order to import the entire log MusicMaster generated for that hour, including any possible overplanning. | ||
+ | |||
+ | Next, we create a new Music Template. In the definition of Block 1 (we only work with Block 1 all the time), set the source to //External scheduler//: | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | Then click // | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | The important bits are: | ||
+ | |||
+ | * File format: TPI | ||
+ | * File style: One file per day | ||
+ | * Split hour by: automatic | ||
+ | * Split block by: automatic | ||
+ | * Source folder: '' | ||
+ | * Filename format: '' | ||
+ | |||
+ | The import tasks can be left untouched as we will not deal with unknown files. | ||
+ | |||
+ | Save the template, and assign it to all 24x7 hours in the Template Assignments grid. | ||
+ | ==== Peform the import ==== | ||
+ | |||
+ | Once the Hour Template and Music Template have been set up, run the Mini Scheduler (click the // | ||
===== Reconciliation ===== | ===== Reconciliation ===== | ||
tutorials/musicmaster/mairlistdb-sync-files.1503318390.txt.gz · Last modified: 2019/07/09 16:19 (external edit)