We are currently in the process of changing our bank. If you pay by bank transfer then please use the new account details for future payments – we will email you with further information and it will also be included on your next invoice. If you have any questions then please feel free to contact us.

One of our service providers is experiencing a network outage, this is affecting AutoDJ services hosted on the uk3-adj server. Thank you for your patience, the network engineers are working on the problem and we expect service to be back up shortly.

Due to a customer request, it is now possible for a scheduled event to interrupt the currently playing track.

Previously, when a schedule activated, the current track would finish before the scheduled playlist started. This makes sense with individual tracks but for customers uploading full mixes, it resulted in scheduled events playing later than expected (i.e after the current mix ends).

The option to interrupt the current track is now available when you create a new schedule. You will also need to restart your AutoDJ if using this feature.

For those customers already on the new AutoDJ system, we have made some improvements and bug fixes. You can restart your AutoDJ to update it.

  • Fixed: Issue with song titles when streaming live, where song titles would keep overriding the live show title.
  • Improved: Player in the dashboard now uses a TLS stream for compatibility with Chrome, even if the destination server doesn’t support TLS.

We will be migrating customers over to the new AutoDJ system in the coming weeks and retiring the old version.

Due to a recent Google Chrome update, plain HTTP content (such as many audio streams) will not be played for some Chrome users if hosted on a TLS enabled web page. Previously, the user would have seen a ‘mixed content’ warning and the stream will have played normally.

The player that we provide with your MixStream server automatically detects whether a TLS stream is required (this has been the case for some time now as it avoided the mixed content warnings), but if you are using any other player (such as your own HTML5 player or a third party player) on your TLS enabled website then you will need to change your stream URL to the secure version.

To obtain your TLS stream URL, please log into the dahsboard and click the ‘Servers’ option in the menu, navigate to your server and scroll down to ‘Listener Connections’. You will need to use the ‘Stream URL (TLS)’ or ‘TLS Proxy’.

If you use Shoutcast then the TLS stream is provided via a web proxy.
Icecast servers support TLS natively – this makes it more reliable than using a proxy.

What is TLS?
TLS was formerly known as SSL and is the name of the encryption that’s used for securing web pages. You can tell if a web page is TLS enabled by looking at the URL – if it starts with https:// and not http:// then it is TLS enabled.

Do I need to make changes if my website isn’t TLS enabled?
No, if your web page starts with http:// then you don’t need to use the TLS enabled stream URL.

We are currently unable to take payments automatically via PayPal Billing Agreements. This is due to a recent update to our billing system, we use a third party module for PayPal Billing Agreements and are currently waiting for the module provider to release an update to fix the problem.

We expect this to be resolved in the next 1-2 weeks, however for this month, please complete your payment manually by going to the invoice and making your payment from there. You can still pay manually through PayPal and automatic payments will resume as soon as possible.

Thank you for your patience.