Correct answer: 1
And even with the new checkboxes I’m planning to introduce, MMDs will still have precedence over Auto Cue, and no Auto Cue will be performed if an MMD file exists. Likewise, no ID3 (or OGG/FLAC) tags will be read when an MMD file is present.
Imagine you deleted a Fade Out point found by Auto Cue on purpose before you saved the MMD file - would you want Auto Cue to detect it again when you load the item into the playlist or database?
There is a hierarchy of the various methods, but it’s hardcoded. Here’s what happens when you drag a file into the playlist (assuming none of the methods is disabled in the config):
-
Query all connected mAirListDB databases whether the files is listed in it. If so, use the record from the database and break.
-
Look for an MMD file. If it exists, read it and break here.
-
Look for a mAirList TXXX ID3 tag. If it exists, read it and break here.
-
Set Title := Filename
-
Determine duration (by opening the file with BASS)
-
Read any native file tags (ID3, Ogg, FLAC, WAV INFO, …).
-
Set ItemType := Default item type specified in config.
-
If there’s a tilde ~ in the filename, use tilde as Fade Out value.
-
Perform Auto Cue (omit Fade Out if there was a tilde).
Import into database is similar, however…
-
Step 1 (database lookup) is not performed - but I consider reenabling it, so the data can be pulled from other databases you may have configured.
-
Step 9 (auto cue) is skipped if you ticked the respective checkbox in the Sync dialog.