Music template scheduling

[imilkovic]

Hi everyone,

I’m building a Music Template for scheduling, and I want to use the Year attribute (where each song has its release year stored as a 4-digit number).

For example, I’d like to make sure that the 3rd song in a block comes from between 2010 and 2015.

My questions are:

• Where and how can I set such a range in the Music Template filters?

• Is it possible to use regular expressions (e.g. ^(201[0-5])$) with the Year attribute, or are regex filters only available for custom (string) attributes?

• Or do I need to use Soft Attribute Filters instead, and for a range like 2010-2014 add multiple values (2010, 2011, 2012, 2013, 2014) with equal weight (e.g. 25% each)?

What’s the recommended approach to achieve this in mAirList?

Thanks in advance!

[Tondose]

Hi, there have been several threads about this topic before. First question: Which version of mAirList are you running?

[Stefan_Hillen]

@imilkovic

Is it possible to use regular expressions (e.g. ^(201[0-5])$) with the Year attribute, or are regex filters only available for custom (string) attributes?

Please take a look here, working for Versions starting at 7.0

@Stefan_Hillen

Example filter for the YEAR attribute:

~^19[89] will match only items starting with a year of 198 or 199
~(^19[9]|^20[0]) will match items with 199 or 200
~(^19[679]|^20[0]) will match items with a year of 1960 to 1979, 1990 to 1999 and 2000 to 2009
~200 will match items with a year starting with 200 only

!~197 will except all items beginning with 197
!~^19[89] will except all items beginning with 198 and 199

Example for filter BPM:

~^12[123456] will select all songs with a BPM of 121 to 126 for you

Good to know

! will except items with the following value from the result
~ will match only everything starting with the following value

The soft attribute filters aren’t working like that:

@imilkovic

with equal weight (e.g. 25% each)?

As far as I understand from @torben every filter will trigger a new calculation for the soft attribute but independently from the other soft attributes.

Unfortuately it’s not a percentually calculation. So if you have four soft attributes with a weight of 25 it’s no guarantee that only one of them is used by the scheduler. Or any of them.

As it lacks documentation and v8 may be at the doorstep with very exciting features, I doubt that Torben has time to explain this right now…

[imilkovic]

Thanks guys, works perfectly! Much appreciated! I’ve mostly been using external schedulers before, so I’m still getting the hang of the internal one.

[imilkovic]

Any sneak peeks on v8 features?