top of page
Search
Writer's pictureThe Baron

SON OF THE DIARY OF THE MAD TECH-MAN (Vol 3, beginning April 2021)



WHO WOULD BE A TECH-MAN!?!


So, after a period of relative stability across our broadcast platform, we noticed an increased number of outages in our DeePlay 24/7 autoplay, and our web player needed to switch to the emergency player more and more. Following discussions with our platform partner, shoutca.st (now Unmuted), we worked out that the problems were actually coming from the third link in our broadcast chain, Centova.


Let me explain.


Our music doesn't just get sent from our studio direct to your listening device. First it has to be encoded via our Mixxx player and sent to Unmuted's servers via our local ISPs. They encode it still further and pass it on, via their local ISPs, in the format that Centova, one of the world's largest internet radio streaming services, require. They then pass it along, via their ISPs, to your listening device. Your device then unencodes via your chosen player app or software. That's a long chain with many links. Throw in our website host WIX, Amazon networks for Alexa, and our operating systems, and you can see it has many chances to break.


Unmuted came to us with a proposal. How about we let them do the Centova role, with new software and the complete removal of 2 to 3 pieces of that chain? All at no extra cost.


It was a no brainer on paper. But it did mean that everything would need to be changed. All our website coding. All our web & app players. Alexa. Radio Directories. Internet Radios. Our individual broadcast players. It would be a massive under-taking.


Now, if only we knew some mad tech-man, willing to take on the job!


Step forward Tech-Man. not just any tech-man, but Mad Tech-Man.


So we planned very carefully. We gave plenty of warnings and step by step updates of what would happen, why it would happen, when it would happen and what would need to be done next.


To everyone's surprise (including the Mad Tech-Man), the switch-over went without a hitch.


We were off air for around 30 seconds. The web players and applets were updated (and changed) in less than a minute. (Of course, that isn't what really happened, Tech-Man spent 2 days doing parallel changes before hand).


Alexa was back within 3 hours.


Radio directories updated within 24 to 36 hours.


Internet radio settings within 12 to 72 hours.


And lo, Mad Tech-Man surveyed all he had done and created, and his heart filled with gladness and joy.


Except since then the rest of the world has decided to attack the other parts of the chain. Microcrap have done update after update (to fix the stuff they broke in the previous update mostly, with each fix updating causing more issues!) affecting some of our DJ's sensitive setups. Internet providers decided to do backbone switchovers and upgrades with little or no warning.


And Centova decided to switch priority broadcasting uptime to their big commercial partners, squeezing out smaller players with outages all over the place.


But wait, that last one didn't affect RRO! We were no longer with them!


Now, if only everyone else would leave us alone to just do our shows and have fun playing the music we all love.


Yes folks, even a Mad Tech-Man can dream deluded dreams....

27 views6 comments

6 Comments


The Baron
The Baron
Sep 27, 2021

DEEPLAY UPDATE 27/09/21


Thankfully, calmer heads at Mixxx have prevailed, and asked for the log files I suggested they review 3 weeks ago!! In less than 8 hours they had spotted the bug, and within 24 hours had released a special beta that they hope will fix the two bugs stopping us having our proper autoplay. That beta is now installed and will go live after the DBRS finishes tonight.


So, everyone, keep everything crossed!

Like

The Baron
The Baron
Sep 20, 2021

DeePlay Update on 20th September 2021


Sadly, we are still stuck on our emergency autoplay. It turns out that the team responsible for Mixxx development on Ubuntu would rather waste time shooting the messenger than actually fixing the TWO MISSION CRITICAL BUGS FOR ANY APPLICATION CLAIMING TO BE A RADIO STREAMING APP.


The two problems affect the autoplay feature, which skips, on average, around 5 in every 13 songs in an autoplay list (making it difficult to time placements such as Playback Friday shows as an example, or even to count down to the start of a live show!), and which causes a memory leak on a large playlist that basically crashes Mixxx after anything from 24 to 72 hours.


Like

The Baron
The Baron
Aug 03, 2021

Sadly, the crash issue has NOT been resolved. Stand by for update.

Like
robbfogg
robbfogg
Aug 03, 2021
Replying to

😥🤯

Like

The Baron
The Baron
Jul 12, 2021

MAD TECH-MAN UPDATE 12th July 2021


Just a quick update, the extra memory and a basic clean of the OS and Player code has failed to fix the crash-issue :(


So for the next 2 or 3 weeks, the backup auto-DJ app will be running with a vastly slimmed down playlist, until I can properly strip down the server and rebuild it from scratch.


Oh joy.

Like

The Baron
The Baron
Jul 09, 2021

MAD TECH-MAN: THE SEQUEL! 9th of July 2021



Oh man.


So, after long lauding the merits of Ubuntu, Streamerr (new name for Unmuted/Shoutcast) AND Mixx, something very strange happened that begun what we now call "The Week of Hell." Yes, things were so bad, we gave it a name.


There I was Wednesday afternoon, getting the studio ready for "The Baron's Rock Show", when up pops the Ubuntu v20 software updater button. Now, my rule is NEVER DO AN UPDATE ON SHOW DAY, but I had become complacent with Ubuntu, after all, it had always been a smooth switch and it was only a small update. So I did the update.


Complete and utter disaster.


The sound drivers were completely…


Like
bottom of page