MusicMaster Blog

by Brian Wheeler

Sharing clocks between databases is a very useful feature in MusicMaster Pro, and it becomes even easier to share in MusicMaster CS and MusicMaster Web Client.

There are two ways you can share your clocks in CS and Web Client. The traditional way of exporting the desired clocks and creating a Clocks.mmdex file is still possible. But I’ll also show you a new way to share clocks on these platforms.

In this photo, I demonstrate how to export clocks using an .mmdex file. You simply select the clocks you wish to share from your source station and select Export. At that point, MusicMaster will create an external file called Clocks.mmdex.

Once this file is saved, you simply go to your target station and import the Clocks.mmdex file to introduce these new clocks to your target. Note that items like forced elements pointing to specific song IDs will not carry over and must be reconfigured in your target station.

And this is how this feature looks in our Web Client. Very similar.

This is a fine way to share clocks from station to station in MusicMaster Pro, CS, and the Web Client.

In MusicMaster CS and the Web Client, sharing clocks is even easier AND more complete! In addition to the ability to share clocks as you always have in MusicMaster Pro, there is an additional way to share clocks, INCLUDING forced elements and other items that would traditionally need to be re-configured for your target station. I’ll explain.

Sometimes in the course of sharing clocks, there are elements that are unique to the source. Forced elements, etc. can’t be shared because they aren’t sourced the same from station to station. This is largely because Song IDs are used for forced elements and those numbers are unique to each database in MusicMaster Pro. With CS and the Web Client, your shared clocks will no longer yield unknown elements, as all those resources are shared at the Enterprise level. As a result, you are able to get the entire clock, elements and all.

Here’s how sharing clocks looks in MusicMaster CS. As an example, I’m ingesting clocks from another station within my network, taking a couple of clocks from my Classic Country station and ingesting them into my Hot Country station. I simply select the source station, then select the desired clocks.

The interface is identical in the Web Client. You simply indicate the source from which you’ll take clocks, select the desired clocks, and ingest them into your target station. Again, no more unknown elements, as you’re sharing these clocks internally.

The result is a seamless transition of your clocks from one station to another, elements and all.

As always, if you have any questions about this or any other feature, don’t hesitate to reach out to your MusicMaster MSC for more information!