A bedroom DJ friend of mine is about to purchase a Home licence and has asked me to set-up a mAirList layout/config for him. We’ve gone for a local mAirListDB file as he wants a fairly quick search facility. For a number of years, he’s used Raduga so has all of his files with the ~ overlap value as part of the filename and is un-willing (at this time) to deviate from this.
I cannot seem to get mAirList to recognise the ~ value on the files. I have disabled AutoCue and have the ~ set to the FadeOut option but when dragging files into the Playlist (either from a Folder or Database Search), there is no FadeOut point and in Automation the song plays to the end.
I’ve tried the latest v3.0 and v3.1 snapshots. Is there a set of config options I need to use as I’ve never used these in mAirList before or has the ~ feature “broken” ?! I appreciate the DB or MMD is a better way but for now he wants to stick with the ~ format.
I’m sure Torben will correct me if I’m wrong (and I haven’t used ~ myself), but I’m sure the option is Import ~ in file name as Fade Out, which implies that you need to have AutoCue set on for it to work, right?
I would try that first, anyway. Let us know if it works!
Oh. The ~ options should be on the Miscellaneous > File Import tab,
and the Auto Cue options should have their own tab under Modules.
Does your chum definitely have a recent snapshot of V3.0 of mAirList installed (not, say V2.x)?
Has he deleted the mAirListDB entries between attempts to import the ~ files correctly?
(If not, the import process won’t happen. )
If both the above are ‘yes,’ could you please paste one or two examples of file names where the import doesn’t work? I’m not 100% sure, but I think any ‘extraneous’ characters (like spaces) after/before the ~ character might stuff up the import process.
I will double check this here and let you know if it works correctly, and if so, the Config settings and file names I used. Fair enuffski?
I’ve been doing the config here - so I’ve got v2, v3.0 and v3.1 to play with. I cannot get either v3.0 or v3.1 (latest builds) to work with the ~ markers but a v2 config works fine and if I edit the filename with a new ~ value then mAirList “sees” it when loading it from the Browser.
Well… according to my observations, it does work, but only if you disable Auto Cue. Because there is (was) a bug which made Auto Cue overwrite any Fade Out marker determined by the tilde.
I’m uploading Build 680, let me know if it works for you.
Thanks for the quick fix - that’s working fine now I would have expected AutoCue to override the ~ setting but odd that I couldn’t get it to work even with it (AutoCue) disabled.
Overriding the ~ with Auto Cue doesn’t make any sense - Auto Cue should only be the fallback if there is no other cue information (database, MMD, tag, tilde) at all.
Glad to her that it’s working now. I will also port the bugfix to v3.1 for the next release.
Which specific AutoCue options need to be disabled? All four checkboxes, or ‘only’ the one you want to use with ~ (like CueIn or FadeOut)?
Also, will your fix mean that (from now on) the ~ options will always take precedence over all AutoCue options, regardless of whether any AutoCue options are ‘on?’
From now on, any marker determined by an existing tilde will be ignored by Auto Cue.
As Fade Out is the only marker shared by the tilde mechanism and Auto Cue, this rule can be rephrases as:
If “Import ~ in filename as Fade Out” is on, and there is a valid tilde in the file name, no Auto Cue will be performed for Fade Out, regardless of whether it is switched on or off in the config. (Auto Cue for Cue In and Cue Out may still be performed depending on your settings.)
)
I would have expected AutoCue to override the ~ setting but odd that I couldn’t get it to work even with it (AutoCue) disabled.
Yes, I’d expect any explicit marker to take priority over an “auto” one!