Thanks for the explanation, but after reading this several times, I still don’t see how this would work in my case.
My station does not use a single generic hourly structure.
I have different clocks for different hours — different music categories, different jingle sets, different rules, sometimes different program logic. In total, there are around 77 different clock variations.
With that in mind, I don’t understand how a single repeating “create” event (or a template-based approach) is supposed to handle this.
If every hour has a different clock and different rules, how can one repeating event — or even a repeat every 60 minutes setup — reliably generate the correct playlist for each specific hour without manually mapping and maintaining all those dependencies?
From my perspective, this still looks like replacing a clear and explicit workflow (each event clearly represents what happens in that hour) with a more abstract one, where the actual behavior depends on naming conventions, variables, and implicit assumptions. That makes it much harder to verify and control in real daily radio operation.
Could you please explain concretely, step by step, how a station with many different hourly clocks (not a uniform hourly structure) is supposed to implement this using the proposed approach?
At the moment, I understand the theory, but I don’t see a practical, safe way to apply it to a real-world radio setup like mine.
