Torben,
Any plans to use BASS_ChannelGetLevel with regards to automatic overlap of tracks ? For example: Sample the last 10s of a song, if the levels falls below a certain level - Move on to the next playlist item. Perhaps a rule that EndType items marked “e” or “f” are ignored, as they would have been user-set.
If this is something that IS being worked on, it’ll be well received 
Spent some time reading the BASS forum, huh?
Looks like this is a reliable way to detect the end of a song, of course only when searching backwards from the end of the song. I wouldn’t want to do that “live” during the automation, though. Any automatic change to the cue markers should be double-checked by the presenter.
How about an “AUTO” button in the PFL dialog? Click it, click TEST to listen and confirm, and you’re done.
Torben
Yeah, I had a look again last night. I’ve used it (BASS) to try out some audio stuff, but never actually got very far - I need to sit down and really go through it’s code and see how it all works.
But some form of audio sampling would be nice - I was thinking more along the lines of those people who haven’t yet been able to set FadeOut markers, and on a large library - Could take a while before 24/7 automation can be relied upon.
What I plan to do now is:
Torben
With the examples from the BASS forum, it wasn’t as difficult as I expected.
As of mAirList 2.1.8, you can …
pi.GetCueIn.SetValue(pi.AutoSearchPosition(ptCueIn));
pi.GetCueOut.SetValue(pi.AutoSearchPosition(ptCueOut));
pi.GetFadeOut.SetValue(pi.AutoSearchPosition(ptFadeOut));
I hope you’ll like it 
Torben
Torben, I do hope I will be able to disable everything that has been discussed in this thread? I disagree 100% with every part of it (or if you prefer: Oh my God NO!!!).
I don’t use EndType at all, so I don’t want any ‘rules’ based on it.
None of my tracks have any unwanted silence at the start, but several of them do fade in (e.g. Sparks: This Town Ain’t Big Enough). I don’t want mAirListTag to ‘suggest’ a non-zero Cue In point based on level. The only time I ever want a non-zero Cue In point is to skip the intro of a live track; or very occasionally to skip ‘oddities’ at the start of a track (e.g. the ‘run and giggle’ at the start of Spice Girls: Wannabe).
Similarly, I don’t want any Cue Out points set for any items EVER: in my experience, setting a Cue Out point screws up the way the fade out algorithm works. If a Cue Out point is set, my desired always-three-seconds fade becomes a fade whose length is (Cue Out - Fade Out)—which could be anything from 1 to 15+ seconds (!).
I don’t want the PFL dialog cluttered up with AUTO buttons which I will never ever use. That dialog is crowded enough as it is! So can you please make it possible for those buttons not to be displayed at all? I don’t want someone less experienced to be tempted to use them!
Thanks in advance.
BFN
CAD
Cad - There are tickboxes in the Misc section of the config to enable/disable the auto-cue detection. Before the auto-detection, “EndType” was an easy way of seeing what songs I had been and in/outro’d. Now, I haven’t got to worry about nasty fades and little gaps if I were to automate using songs I had set a FadeOut point on.
Way beyond the scope of mAirList (at present), the EndType can be used to determine how the playout system should deal with songs in relation to a news backtiming marker (or some time critical event).
I’m more concerned that Cad’s got the Spice Girls on his playlist
Cad,
you should really try v2.1, and you’ll find that mAirList is still - and more than ever! - the most configurable radio automation software on the planet
Torben
Charlie: The Spice Girls tracks was merely an example (one I added to our library recently). We’re not on air quite yet, so ‘muggins’ has been starting to add reliable MP3s to form a library, and tagging them up.
We are also about a million miles from exotica like time critical events, plus I don’t want to start any debates among our presenters about whether a given track is an ‘end’ or a ‘fade.’ But out of interest: how do you deal with false endings (e.g. Temperance Seven: Pasadena), given you use F to mean Fade? (evil >grin<)
Torben: We will be on air quite soon, so:
I have to concentrate 100% on the stable release of mAirList only. Once we are on air (in a few weeks from now), I might have time to look at mAirList 2.1, but not now: sorry! I do promise to look at it sometime though, but don’t be upset if I end up preferring V2.0 to V2.1. V2.1 seems to have a lot of worrying features that I will need to turn off, plus it doesn’t allow ‘chaining’ of the Cartwall players (same as Triggers, but at EOF instead of at the start): so I’m not looking forward to trying V2.1.
Most of my spare time at the moment is devoted to ripping and tagging (see mAirListTag bug reports ), to replace our previous music library.
BFN
CAD
I understand that you are very busy with Leith FM, and it’s certainly a good idea to rely on the stable release. This is what the dual-release thing is all about.
My point is, if you had downloaded the latest 2.1.x version, you would have noticed that all of these features are optional and configurable, and that there are no extra buttons in the PFL dialog. That is to say - you wouldn’t have needed to write that “oh my god no” comment, saving you a lot of agitation
By the way, are there any mAirListTag bugs I have ignored so far? If so, please let me know.
Torben
(preparing to chase Charlie’s Invalid Pointer Operation bug now)
By the way, are there any mAirListTag bugs I have ignored so far? If so, please let me know.
Forget about it, I saw your post now 
Torben
Torben, my sincere apologies if I was a little ‘over the top.’
I understand what you’re saying about 2.1 but unfortunately I really am racing against time, so much so that I honestly can’t afford the time to look at 2.1 just now.
It will genuinely be a couple of months before I am done with making jingles, an initial ‘test broadcast’ loop of ideally one hour duration using bought-out music only, station jingle package, etc. … plus ripping and tagging.
BFN
CAD