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 Sounds In Sync will be exhibiting at the AES show in New York, Oct 17-19. Meet founder and developer Mark Franken for a demo of any of our products and see how they integrate with Pro Tools to perform a variety of tasks including cueing and recording ADR, conforming location WAV files and re-conforming Pro Tools sessions.

Now that Avid have released Pro Tools 2019.5 and qualified it to run with macOS Mojave (10.14.4) * we tested our applications on a system with these installed.

All functions of our applications performed as expected including how they interact with Pro Tools. However macOS Mojave now displays additional security messages when our apps are used in the following way:

If you are running macOS 10.13.4 or above you may have seen the following message when you run an application:

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.

We are pleased to announce that all of our applications are compatible with Apple's latest operating system macOS High Sierra (10.13).

We successfully tested the functions of our applications that interface with Pro Tools on macOS 10.13.2, as this is the version of macOS that Avid have qualified Pro Tools v12.8.3 with. For more information on what versions of macOS are compatible with each version of Pro Tools, see the Pro Tools Operating System Compatibility Chart.

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.