×
We are excited to get you started. Here is exactly how we will build this together. It is powerful, it stays local in every city, and it moves fast. Let's go.
"You send Super Hi-Fi a station and your music, and we set it up in the cloud."
A fair guess. What we do is even better.
We design one smart set of programming for each language. Then every city in that language runs off it, live and local.
One design per language. Many cities.
Here is what makes this powerful for Radio Mirchi.
We design it together first. Then we build. And new cities launch fast. Let's go.
The language sits on top. We call its programming the Core. Every city, even the biggest one, sits underneath.
On your sheet, Bengaluru looked like a hub. It is really the biggest spoke. It is perfectly fine to build the Kannada Core from a clock Bengaluru already runs. That makes good sense. But even Bengaluru is still a spoke. Its programming comes from the Kannada Core, not the other way around.
Good news: a Core is just three things. That is the whole recipe for the language.
One clock for each hour of the day. 24 hours. 7 days. That includes the quiet overnight hours too. The clock is the plan for what plays and when.
We name the music categories for this language only. We do not want your whole music library. We pick just the categories this hub needs.
Imaging is the audio between the songs, like sweepers and jingles. At the Core we just name the kinds. A basic sweeper. A voice track. A jingle. A station-name sweeper. Each kind becomes a Smart Folder in the clock.
Because every city under the Core plays the same music and the same clock in every hour, they all share the same shape. Same song counts. Same commercial times. The design is identical everywhere.
This is why it is fast. Design the Core one time, and every city in the language is ready to go. The only thing that changes city to city is the local audio. That is the next page.
Here is the clever part. This is one hour of the Kannada Core, and every city runs this exact hour. The red rows are imaging slots. They are really Smart Folders.
The clock does not hold one city's audio. It holds the name of a Smart Folder. "Short sweep" is a Smart Folder. Every city fills that same folder with its own piece.
Same songs, same order, same commercial times on every city. The only thing that swaps is the local audio inside each Smart Folder.
Watch the "Short sweep" Smart Folder. Bengaluru and Mysuru both play from it, but each plays its own sweeper. The city's Context ID picks which one.
Same folder. Same clock. Same slot.
The stream knows which city it is, so it plays that city's audio.
Each city gets its own stream. We tell that stream its Context ID one time. From then on it always reaches for its own local pieces out of the shared folders.
The Core sets the ad pod shells for each hour. Those are the open ad positions the Core schedules. Every city runs the same clock, so if the Core has five ad pod shells in an hour, every city has five. The times never move.
Each market sends its own local commercials. They land in these ad pod shells and schedule for that hour. Same shell, same time, different ads. Here is the same Shell 1 in both Kannada cities.
There is no separate clock for each city. There is one clock, the Core. Every city on the hub is married to the same number of ad pod shells, at the same times, as every other city. Each market sends its own local spots, and they land in those shells. What goes inside is yours to fill, city by city.
It will feel like we are setting up ten radio stations. We are really setting up ten Cores. Every city is a spoke underneath its language.
Markets shown come from your rollout sheet. We finalize the full list and Context IDs together.
That is the whole idea. One language, one Core, many local city streams.
To build a Core we will need your music categories, your clocks, and your local imaging. The next page lays out exactly what to send, in order.
We are not rebuilding stations one by one. We are building ten Cores. Every city is a fast, local copy of its language. Change one clock at the Core and every city under it changes the same second.
This is the fun part. We design your first Core together, in order: music first, then clocks, then imaging. Here is Kannada. The other nine Cores follow the same three steps.
Tell us the music categories for Kannada, then send us the songs sorted into only those categories. Please do not send one big dump of all your music. We build these categories in the system under Kannada. Send Kannada only.
★ Example starter set · you confirmYou can add, remove or rename any of these. Some categories can also split by speed (fast, medium, slow). This is a starting point to react to, not the final list.
Build the clocks for Kannada for the whole day. One clock for every hour, 24 hours, 7 days. You can have as many clocks as you need, and you can reuse them. You can run an A clock and a B clock that take turns, or change clocks by daypart (the parts of the day, like morning or midday). These same clocks run on every station under Kannada.
★ Example hour · the shape for every hourA few clocks can cover a whole week. The same clock can run in many hours. An A and B clock can rotate inside a daypart.
At the Core, imaging is just a folder name, like "Short Sweeper." We name every folder by the type of piece, not by a city. That is all we do at the Core level. Then we open that Smart Folder. Inside is where the local audio goes. For each city, you give us the local pieces that say that city's name. You can put many in the folder.
★ Name folders by type, not by cityThe Core folder is named "Station Jingle." The Bengaluru jingle and the Mysuru jingle both live inside it. Each city's stream plays its own.
Every station gets its own stream. When we build the Bengaluru stream, it plays a Bengaluru sweeper from this folder. The Mysuru stream plays a Mysuru sweeper. The city's Context ID picks the right one.
The whole list, in order.
Once Kannada is built, the other nine Cores follow the same three steps: music, then clocks, then imaging. Same order every time. We are excited to build this with you. Let's go.