With the COVID-19 lockdown temporarily closing ADR studios around the world, sound post supervisors and editors have been creating ingenious ways of recording their ADR.

Apple released its latest major update for macOS called macOS Catalina (10.15) on October 7, 2019. One of the major changes in this update is that it will only allow 64-bit applications to run. We have been working this year to update our apps for 64-bit, and are excited to announce that the following have been released:

Since releasing EdiCue v1 nearly 12 years ago to the day, I’ve received an abundance of user feedback and feature requests for the application. As I live in Australia, I would implement an update while clients slept, where possible, so they could wake up to an email containing a link to download a pre-release version. Other requests required extra patience.

We are pleased to announce that all of our iLok enabled applications can now be licensed using iLok Sharable Licenses. This allows our applications to be authorized from a license server on a local network, eliminating the need to have a physical iLok dongle connected to every computer running one of our applications.

Being able to transfer ADR cue data from one system or application to another can save hours of manual cueing, or copy and pasting of individual data fields. However, the most common way of transferring this data is via a text file, and there are several things about this method that can get you stuck. When dealing with non-English text, or transferring between different operating systems, there’s a good chance your data won’t come across as expected.

Following on from my previous post explaining the background on how text files work, here I will go into examples of how to manage text files and prepare them for import into EdiCue.

While printing ADR cues in EdiCue, text characters can sometimes be displayed incorrectly. If this is happening to you, you probably have a 'text encoding' issue.