Myriad Playout v6 - some exciting news about it's release

Liam Burke • May 12, 2023

Myriad v6 Public Beta testing has been going well... REALLY well!

I just wanted to post a quick update on where we are with getting Myriad v6 Playout up to "Full Release" status.


First off: a quick explanation on what we mean by "Full" vs "Beta" Releases and the process we use to get new releases of our software tested and released.


Full Release vs Beta Release - what does that mean?


When we are working on a new release of Myriad, our primary aims during testing are to make sure that the any new features work as designed, and more importantly, that when it leaves BR Towers that it's not going to cause real live radio stations any headaches. In the forefront of our minds is that  Myriad is used every day by thousands of users in radio stations all around the world, and the last thing we want to do is give them even MORE to deal with - or even worse, to take a radio station Off-Air due to something we missed.


To do this, we work hard during development to make sure that new features do what they should, don't have any critical bugs, and just as importantly, don't break anything else.


All new software goes through a series of stages as part of each release cycle:


  • Alpha builds:  This stage usually means that any new features are functionally complete, but will likely have some bugs in, some of which might even cause the program to shutdown unexpectedly. These are almost always only ever used internally at BR Towers and it's incredibly rare that these are let out of the building!
  • Private Beta Releases: By this stage, the software is usually complete, and has passed the initial rounds of internal testing showing that it is reliable and works well, with no critical issues found. These versions are used internally at BR Towers as well as at selected real world radio stations who we work closely with as part of their daily broadcasting.
  • Public Beta Releases: We are now happy that the software works well and does what it should, and that it hasn't caused any operational issues during testing. At this point we are confident that it's ready for everyone to use, and we expect that it should be able to move to Full release shortly. However, it's still considered a test release, so is not supported buy our normal Support team, and should only be used On-Air at your own risk on the understanding that there may be bugs we've not found!
  • Full Release: Once we are happy that the new release is in use at a significant number of stations and has been running long enough that we are confident that is has the high quality we would expect, we upgrade the Beta to "Full Release" status - at this point it's fully supported by our Support Team so customers can then feel confident enough to start rolling it out on their own stations - of course, subject to any testing they want to do themselves first! At this point we will also start deploying this new release ourselves to all new customers.


If you want a more detailed explanation about Beta releases, there is a full explanation here https://www.broadcastradio.com/beta-versions-explained


Developing new features:


As part of daily life in the Broadcast Radio software Dev team, whenever we're working on a new update, we regularly produce "Alpha" test builds that we run on multiple internal test radio stations - each one of these stations is testing a different common configuration. For example, one station might be using the built in media engine, whilst another otherwise identical station is using the Remote Media Engine Host instead. Another test computer might be running multiple radio stations all from a single PC, whilst yet another is simulating radio stations that use Split Advert Breaks and ID's to produce different branded content.


These test stations are much more than simple log playback - they are designed to simulate as many common scenarios that our end users carry out every day as possible - so we even use automated testing to simulate users deleting and importing media items, importing news and weather content, even making sure that we can correctly import syndicated shows from 3rd party providers, and validating that their "Now Playing" information is correctly ingested and then sent back out at playout time.


Once we have finished work on a new feature and are happy that it has passed the automated testing, a full internal private "Beta" build is  then passed to members of our Support team who do "as-live" testing of features, as well as making sure that any customer reported issues have been resolved. The will also putt it through their own typical test scenarios based on their own real-world experience working with customers directly.


We also send that private Beta build out to a carefully selected pool of broadcasters who then test that new version on their actual live radio stations - usually on a test system first, and when they are happy, they will then run it live On-Air - you'll sometimes hear us refer to these stations as our "Private Beta Test" stations. These stations are essential to our testing process as it will put the softwar through its paces in the fast paced environment of a live broadcast studio - a true trial by fire if you will! Hopefully it's a testament to our development skills that these stations are always very happy to test these versions, as they know it's incredibly rare that it will cause them any actual On-Air issues!


We then expand our own internal testing pool to include other parts of the Broadcast Radio team to make sure that documentation can be worked on or updated, any training videos created, as well as making sure that the commercial team is happy that they are ready to talk about new features and improvements with customers, as well as making sure they are comfortable with how to demonstrate the new version at the many trade shows and Expo's that we attend each year.


Once all the above has completed and we are happy that Myriad is ready,  we then do a full build of Myriad ready for a "Public Beta Release".


Our quality target for these Public Beta releases is that this release should ultimately be good enough to be upgraded to "Full Release" status once it's passed public testing.


This means that it should be able to be used by normal non-technical presenters, on a real world radio station with zero "Off-Air" bugs, and as few minor issues as possible - we aren't perfect, and any coder who says they are is lying! - but we do our very best to make sure that these releases are as good as is humanly possibly.


Part of the reason for these Public Beta Releases is that although we have tested as many common environments as possible, it's impossible to simulate the hundreds of possible different scenarios that Myriad might be used in, and of course hundreds of thousands of different actions that different users will carry out at stations in real-world use every day. For example, one station might have a particular set of hardware that performs differently than others, or one user may use a feature differently from how we intended it, and comes across a bug.


So this Public Beta testing is an incredibly important phase in the release cycle - without knowing that other broadcasters have already upgraded and tested out each new release, what confidence would you have that your station is not going to be adversely affected by a change?


We also feel a strong sense of responsibility with these Public Beta versions - the last thing we would want to do is to to release something that is going to make a presenter or a station sound unprofessional. Further, if we were to get a reputation that our Beta Releases are unreliable then broadcasters would stop downloading and testing them because they wouldn't have the confidence to use it. This means we would lose that incredibly valuable real-world testing that makes sure that every release of Myriad that goes to "Full Release" is as rock solid as possible.


Sometimes during this Public Beta Release phase, an issue will be found that we feel is critical enough that we need to issue a fix before we are happy to sign off on that version going to Full Release.


An example of this recently was with the first ever Beta Release of Myriad Playout v6 (v6.1.1),  when a user in France found that in certain circumstances Myriad would not run correctly - in this case, because in France a decimal point is represented by a comma "," instead of a "." character. Obviously this is not a good thing(tm) so we got that fixed and issued the v6.1.2 release along with some other tweaks improvements and bug fixes that came up with that first release.


This testing and release cycle will then usually repeat until we are confident that the most recent Beta is ready, at which point it is then upgraded to Full Release status.   


So, that's the process explained, where are we with Myriad Playout v6?


First off, the really great news is that Myriad Playout v6.1 has turned out to be REMARKABLY reliable.


Between you and me, we fully expected that there would be something that we would have to re-work with the very first release, maybe even meaning that we would have to do another big release to get things sorted - after all, v6 is a huge update from v5, and there are thousands of UI changes, and tens of thousands of code line changes that we've been working on for the past 9 months or more, so even with fingers and toes crossed, we did think that we might need more updates before it was ready for "Full" release.


The amazing news is that we were wildly wrong - Myriad v6 has proven to be incredibly reliable - so much so, that almost 1 in 10 Myriad v5 stations have already updated to the latest beta release (v6.1.2) and are using it live on-air, and almost every station that has downloaded the beta to try it out has ended up being so happy with it that they have rolled it out on-air.   Yes, we are feeling more than a little bit chuffed about that!


BUT! (And there is always a BUT!) - Our own testing and feedback from the beta testing programme has shown a very small number of issues (less than 10) that we want to get fixes out for before it goes Full Release - rather than do a Full Release now, then have to wait for the next big release to get those fixes out. 


For example, the method used to "Group" items in the Media Library search results has stopped working. It's hard to imagine how this could possibly take a radio station off-air, but I'm pretty sure it might well drive a presenter up the wall if they have come to rely on using that as part of producing their show! So we fixed it, along with the other niggles.


So - whats next?


The plan is now pretty simple - within the next week or so we will be shipping a v6.1.3 Public Beta release that fixes those last few bits, but ALSO adds in a couple of new features as well - for example you can now configure Remote Edit Server to process each recorded voice link using a 3rd party audio processor such as StereoTool to help iron out those differences that come from different rooms, microphones and techniques. This feature was in Myriad v5 RES, but it wasn't quite ready in time for the original Beta release of v6, but it is now, so we've been able to include it in v6.1.3.


Typically we let a Beta release run for about 4 weeks to make sure enough broadcasters have put it through it's paces before we declare it ready to upgrade to a Full Release, however, as the changes in v6.1.3 are relatively minor we are hoping that we will be able to cut down this period slightly to get it up to Full Release status more rapidly than usual.


We actually took a big step towards this goal today internally at BR Towers, as we completed the upgrade of ALL of our internal "long term" test stations to Myriad v6 - this is a huge step towards us being ready to certify that we are happy that Myriad v6 will be our flagship product - but also a slightly sad day, as some of those stations have been running Myriad v5 for nearly 7 years through various versions - But that's the price of progress!


(Note to v5 users: Don't  worry, we still have several other test stations running the latest v5.32.2 release as well, just in case!)


Summary


So in summary - within the next week or so we will release  Myriad Playout v6.1.3, and once that is released, we'll then follow it up shortly afterwards with a Myriad AutoTrack SE v4.6.1 beta release with the aim that these will both go Full Release shortly after.


As you can imagine, we're incredibly excited about this, and we genuinely can't wait to get Myriad v6 to Full Release as we know so many stations are waiting to upgrade as soon as they can- we know they are as excited about it as we are, because we get asked about it multiple times a day - and we genuinely love that keenness!


Once both Myriad Playout and AutoTrack have gone to Full Release, we will then be working on the first release of Myriad Anywhere v6 Self-Hosted for stations that host their own Myriad Anywhere sites. 


Of course, Myriad Anywhere Cloud itself is always kept up to date by our team here, and it all Myriad Anywhere Cloud stations receive updates automatically every week or two, and it also has it's own Beta versions that are updated more often than that - for more information on how to opt-in to these Beta Releases of Myriad Anywhere Cloud v6, see this post on on facebook


Hopefully this helps explain where we are, and just how soon Myriad Playout v6 will be ready for the big time!

By Liam Burke 19 Apr, 2022
This smart microphone may be ideal for Myriad Anywhere users.
By Liam Burke 28 Jun, 2021
Image Source: Pexels
By Liam Burke 26 Feb, 2021
We are often asked for recommendations for smaller, low cost mixers for stations that are launching on a tight budget or looking to add additional studio capacity as cost effectively as possible. Type 'stereo mixer' into Google and literally hundreds of options will come up but the vast majority of them are not really suitable for use with Myriad because they do not have enough stereo inputs, are designed for sound mixing or do not offer the basic facilities needed to present a radio show. But there are a few that could be considered as a possible alternative to a full broadcast mixer. The Behringer DX2000USB may be the ideal mixer for smaller stations, as long as they are willing to live the compromises it brings when used in a broadcast radio environment.
By Liam Burke 04 Dec, 2020
This post was originally posted on Arran's blog https://thisisarran.me/index.php/2020/12/04/the-technical-side-of-a-radio-station/ and is reproduced here by his kind permission. If you have a post you'd like share, please contact us and let us know!
Home Studio Mixer Review For Myriad Anywhere
By Liam Burke 28 Jul, 2020
With the World still struggling to adapt to the 'new normal' of working from home and minimising social contact, more and more stations are using Myriad Anywhere to enable presenters to record Remote Voice Tracks or even prevent live shows from their own home studios. Generally, all you need is a good microphone and a pair of headphones (we recommend a headset if possible) but we are hearing from a number of customers who are looking to create a home studio setup to allow them to get more creative and emulate their studio experience. So we thought we would take a quick look at a couple of home mixer options that work well with both Myriad Anywhere and fully installed Myriad Playout.
By Liam Burke 29 Jun, 2020
Sometimes you want to repeat complete Log hours in your schedule. Under normal circumstances, Myriad Schedule (or AutoTrack) will generate a new Log Hour for every hour of the week. But once you have edited and Voice Tracked an hour, it is sometimes good to be able to re-use that Log Hour elsewhere in your schedule or maybe even on another Station (if you are running more than one. This can be done using the Log.CopyHour Command.
Myriad RVT & Anywhere Cloud
By Liam Burke 22 Apr, 2020
We ran the numbers and stations are using Myriad Remote Voice Tracking, a lot! Let's take a closer look.
By Liam Burke 02 Apr, 2020
There is one question we have been asked again and again in the past few weeks, how can we present a live show from a home? With many stations now finding access to their studio restricted and increasing restrictions on non-essential travel, most stations are now having to consider how they can continue to provide vital services. We are doing everything we can to assist stations through these difficult times with regular software updates that include features to assist with remote working as well as help articles and documents to help people get the most from their systems. To recap, the remote working options for Myriad 5 Playout users are: Remote Voice Tracking (RVT) - Desktop application that allows you to edit the Log and add Voice Tracks. Myriad Anywhere RVT (Cloud or Self Hosted) - Similar feature set to RVT but with a web based interface to allow greater access across a wider range of devices. Myriad Playout Remote - Desktop application that offers partial remote control over your studio Myriad 5 Playout system. 3rd Party Remote Control Solutions (Teamviewer, VNC etc) - Services that offer full remote control of your Myriad 5 Playout System to allow advanced features such as scheduling, but not usually useful for audio based features such as RVT. Myriad Anywhere is explained in detail on the Myriad Anywhere section of our website and full documentation on both Myriad Anywhere and RVT can be found in the documentation section of our support site. Voice Tracking provides a great way to add 'live' sounding elements to your automated output and for many stations, will be the main tool used to 'keep the lights on'. But what about if you want to present a live show from a remote location? What tools will you need and how will you go about setting it up?
By Liam Burke 18 Mar, 2020
Myriad Playout v4 and v5 have both always had very strong remote features and this document will outline those features, potential use cases, and security precautions. The features and security precautions can be different between the 2 product versions, so any differences will be noted in each section. Products covered: Myriad Playout Remote v5 Myriad Anywhere (Cloud) v5 Myriad Anywhere (Self Hosted) v5 Myriad Remote Voice Tracking v5 and v4 Myriad Monitor v4 Other 3rd party Remote Control Products
By Liam Burke 17 Mar, 2020
At Broadcast Radio, we work very hard to make sure that our products and services stay running whenever the office is closed, and a couple of years ago we started a rolling project to make sure that we could carry on even if we couldn't make it into the office. TL;DR: We are ready for Covid-19 and for our people to work from home. To save you reading the rest of this article (unless you want to!), every single person who works for Broadcast Radio has been trained on how to access all the normal office documents, the phone systems, email, Instant Messaging, Technical Support Resources and CRM systems so that they can carry on as normal, if and when they need to work remotely. Wherever needed we've provided PC's, laptops, screens, comms headsets and other devices to any of our people that need them, and in the event that the office has to be physically closed, we will just carry on with a "virtual" office with business as usual on all the usual phone numbers and email addresses. Our main priority has been to make sure our people are safe and well first, and only after that, to make sure we can provide the tools they need to help our customers do the same. As the vast majority of our customers are radio stations, it's essential they can stay operating for as long possible, and part of that is making sure we are there to back them up, so making sure our people can answer the phones and email as normally as possible remains our goal for as long as this outbreak lasts. A bit more background The Broadcast Radio office is based on an office park that sits on the banks of the Humber Estuary - which is one of the largest waterways in the UK - and on a good day gives an amazing view out of the office window - the picture above of the Humber Bridge was taken just now from the offfice car park to prove the point! With the great scenery comes a risk though - water not staying where it should. The office itself sits very high up so is in no risk of flooding, but 5 years ago the river overflowed after very several days of very heavy rain, and one of the roads nearby was impassible for a day, meaning that about 20% of our people couldn't easily make it to the office. Because we had already planned for this eventuality, the actual impact was minimal - our people just switched to working remotely, and business carried on as usual. Although it has a tongue-in-cheek in name, we started our planning under the name "Project Zombocalypse" many years ago when we wanted to make sure that as many aspects of running the company could be carried out remotely should the need ever arise. This light-hearted look at scenarios starts with the premise that we can't leave our homes due to that most infamous of all movie genres, the Zombie outbreak, so we need to carry on on the assumption that getting to the office is out of the question. We started by breaking down the task into 2 parts - People and Infrastructure - and like everything we do here, people are first. A) People first! To start with, we needed to work out who could do their work from home - and with the exception of our actual studio build engineers, the vast majority of our team could indeed work remotely. Sales, Admin, Technical Support and the R&D teams can all carry out 95% of their jobs without needing to be in the building for quite a long period. Ok, great, but HOW will they actually do that? This really is where you have to think quite carefully, so we broke that down into sub-sections, and then worked out answers for each one: PC's: An obvious one really, people need to be able to access the resources in the office remotely in the same way that they use them when they are in the building - users don't like "friction", so wherever possible, resources, documents, software etc. should all be accessible in familiar ways. The answer is actually remarkably simple for normal office use - "Remote Desktop" is built into Windows and is ideal for the job. To access their desktop PC's we made sure that each user knows how to VPN in to the office network from their home PC's, and what their desktop PC is called, that way they can just pick up where they left off. Interestingly, several users don't have a home PC at all, having switched to tablets and phones for home web browsing etc, so we made sure we have a stock of company laptops ready to go and these are issued out to anyone who needs them. Phones: Most of our people talk to customers every single day on the phone, so we needed to make sure you can still dial the office numbers and get through to the right people. Over the years we've worked our way through various different solutions to this, but a couple of years ago we switched to using a 3CX phone system and everyone now has the 3CX app on their mobile phones that can be set to mirror their desktop phone with 2 taps. So if they do need to work remotely, they just open the app, "activate" the account and straight away calls will flow to them over their broadband connection. This means it's totally free for them to use - no fear of accidentally running up big personal phone bills when calling customers as the call is routed to the office and then onward from there to our normal phone lines. In fact, we love 3CX so much that we are now a certified and accredited re-seller of 3CX products to the industry. Inter-person/office communication: Phones are great, but actually a huge amount of our inter-person communication is text based - either emails or Instant Messaging ("IM") - so we needed to make sure that we keep that all running as well. In fact, when users are physically separated it becomes essential to keep good communication flowing . For both email and IM we turned to Microsoft - for years we had been running Microsoft Exchange and Skype for Business on servers at the office, but 4 years ago we switched to Office 365 and then IM to Microsoft Teams, so both of those are now hosted and run for us by Microsoft for little to no cost. MS Outlook and MS Teams are available as desktop applications, mobile apps (for both iOS and Android) and also via web browsers, so again, we made sure that everyone knows how to access email and IM from their mobiles as well as using the regular tools they are used to on their office PC's. Internet Connectivity: all of the above only works if we can guarantee internet access to the office so users can VPN in (for PC's) and access the phone system. To make sure we stay connected, we have 3 dedicated fibre circuits into the building, each of which can handle all of the data needed to keep us running. We also have a fallback wireless circuit from a different telco which can be enabled should the need ever arise. Once you've identified the areas above, next you have to make sure that people can actually use those - do people have a good enough broadband connection at home? Do they have a PC? Do they have a suitable workspace that they will be comfortable to work in for the duration of a working day - for example, one of our people has a home pc, but it's plugged into their TV for use as a gaming system and home theatre system. If they ever have to work from home for an extended period, their kids will likely want to use that TV for Netflix, so we made sure that we sent home a dedicated monitor for them to use on their home-office desk instead. Small things, but easy to miss when you are "blue sky thinking" about how to handle these scenarios. B) Infrastructure This itself breaks down into quite a few different areas, so i'll only touch lightly on each: Office files and servers : The core of any business, your data is your second most important asset, so you should protect them wherever possible. We run a minimum of 2 live copies of all data here in the office, as well as 2 separate backup solutions, and 2 different off site backup technologies. That's everything from spreadsheets and word documents, to product test data and source code. In fact our source code actually lives in 2 separate places on TOP of those above, that's how critical it is! Customer support servers: We have a number of servers that exist to make sure that our customers keep going - for example Product License Activation servers and Technical Support. These run on 2 separate systems so should one fail the other can take over. We can also manually generate licenses and handle support via email alone should the need arise. Hosting services: We also provide streaming for hundreds of different radio stations all over the world, as well an increasing number of "Radio In the Cloud" customers where we host the infrastructure for stations for them. These streaming and hosting servers are located in commercial data centres around the UK so enjoy all the benefits of huge backup generators and redundant architecture. A number of the Radio in the Cloud services are also hosted at the Broadcast Radio Offices, so these also get additional facilities to make sure they stay up and running. Interestingly, when you come to look at supporting remote working, it's actually only item 1 above (office files) that you have make sure are available for that part of the business, and as we've already made sure people can remote in and access their content, this is already covered! In the last few years we've also started a big change to moving more and more of our office files into cloud provided services like Microsoft Sharepoint and Dropbox as this reduces the requirement for office infrastructure even more. We're also hosting more and more of our proprietary data in private Microsoft Azure spaces as well. So in summary, we have now activated our plans ready for whatever comes next: Everyone here has checked and confirmed they can make and receive calls via the normal numbers from wherever they need to. Everyone here has checked and confirmed they can access their office PCs remotely. This includes making sure the PC is left switched on, or remotely "wakeable", should the need arise Everyone knows how to access email and instant messaging via web browsers etc. Everyone has the right equipment already at their homes to allow remote working. We have checked that all our physical IT infrastructure is working and that backup services are ready. We have turned off the coffee machine. For now, thats all that's needed. Of course, the situation is rapidly evolving, and over the coming days there will be all manner of surprises and twists to come, and of course we will face our own challenges as it's likely that some of our people will need to rest and recuperate, but we are happy that we have planned for the most likely outcomes, and have the flexibility to adapt should we need to.
Show More
Share by: