Popular - Feature Requests - Support

Make a suggestion:

Hot
Popular
Recent
Completed / Closed
Post a new idea

Vote for an existing idea
Post a new idea

Title:

Product:

Description:

Please explain the feature you would like and why this would be useful to you.
For example: As a radio DJ I would like to have a wall of one-touch radio buttons so I can play jingles without having to load them into the log.

Post idea

< 42 43 44 45 46 47 48 49 50 >

vote

Vote

Clock simulation / preview mode.

You can build a clock but you can't run it forward and see what a simulated week of scheduling would produce before committing. A "simulate 7 days" preview showing era balance, artist spread and rest time compliance would catch problems before they g ...

vote

Vote

Daypart Separation is track-only, not category-level.

You can prevent the same track repeating in the same daypart — but there's no equivalent policy for preventing the same category position from repeating.

vote

Vote

Scheduling strategy is set per clock item, not per category globally.

To my knowledge: If you have A1 in 10 different clocks, you have to set Most Rested on each one individually. A global default strategy per track group would save significant setup time and prevent inconsistency.

vote

Vote

seasonal or special programming easily.

Scheduling a Christmas clock for December 24–26 only, or a summer weekend rotation from June–August, requires manual intervention every year. A date-range scheduling layer above the weekly grid would make this manageable.

vote

Vote

bulk category management tool

To my knowledge: Moving tracks between categories (track groups) is done one at a time or via the Move Tracks window which is two-group-at-a-time. With a large-track library across 9 categories you need the ability to filter by multiple criteria and ...

vote

Vote

Loudness Analysis has no per-category reporting

You can run the analysis but you can't see which categories or eras have the most inconsistent levels, or which specific tracks are outliers. A loudness report sorted by deviation would let you prioritise which tracks to review manually.

vote

Vote

Valid From / Expires exist on tracks but there's no workflow around them

If a track expires it simply stops scheduling silently. There's no notification, no dashboard of "tracks expiring this week", no prompt to graduate or delete. For A1 management — where you want tracks to graduate to A2 after 9–12 months — you're flyi ...

vote

Vote

Related Artists requires manual entry with no lookup.

o link Robbie Williams to Take That, or George Michael to Wham!, you type both artist names in manually. There's no search-as-you-type, no suggestion based on existing library data, and no way to see all related artist relationships at a glance. At s ...

vote

Vote

No duplicate detection in the database.

It's possible to import the same track twice (different file paths, slightly different artist capitalisation) and the scheduler will treat them as different tracks. A duplicate detector based on title + artist + duration matching would prevent most o ...

vote

Vote

The Logged Tracks export is reactive, not analytical.

You can export a CSV of what played, but there's no built-in rotation analytics — no "plays per category this week", no era balance report, no "least played tracks in each category". These are the core questions a music director asks daily and they c ...

< 42 43 44 45 46 47 48 49 50 >

Feature Requests

Make a suggestion:

Log In

Contact