The goal for software developers is to create applications that are simple to use while containing the flexibility and functionality required for its user base. This is especially true when the application interfaces with another application. In this case, the primary application needs to be able to communicate with the secondary effectively, so that data is exchanged correctly, without the need for the user to make selections while importing or exporting data. This has been the driving force behind the updates made in EdiCue v4.
Streamlining Integration with Pro Tools
One of the bottlenecks that EdiCue has had since its inception has been importing ADR cue data from Pro Tools. This process has relied on the user manually exporting a text file from Pro Tools and making the correct selections during the export and subsequent import into EdiCue.
To streamline this process, I set aside a major portion of 2021 to write the code that can read and write Pro Tools session (.ptx) files. The result of this investment is EdiCue can now not only import ADR cue data directly from a PTX file, but also export cue data in a PTX file.
On the import side, EdiCue now offers the option to import cue data from audio clips, clip groups or both. When all cue data is stored in clip groups, selecting the option to load data from 'Clip Groups Only' allows EdiCue to ignore all audio clips in the session, speeding up load time.
On the export side, I am pleased to report that EdiCue now exports cue data in empty clip groups – the most requested feature our users have made. Now EdiCue no longer needs to create audio clips that references a mute WAV file. On top of this, during export you can now define the color of each clip being exported by the clip name. By default, all clips containing the '[TBW]' tag are exported red.
Adding Support for Nuendo
In tandem with this Pro Tools development, I also worked with Steinberg to add support for Nuendo. Looking to provide the best user experience possible, we were able to formulate a protocol that allows the two applications to seamlessly transfer ADR cue data in the background without the need to save or load data from files. I’m grateful to Steinberg for providing this feature-rich interface to allow EdiCue to interact with Nuendo in this way.
EdiCue now has a new Project Interface window. Like the Session Interface window for Pro Tools, the Project Interface window can import character lines from a PDF shooting script and be used to set the attributes of each cue before sending this information to Nuendo.
Rather than store the cue data in audio clips, the data in Nuendo is stored in cycle markers which extends the existing ADR features of Nuendo. Once the cues have been created with EdiCue, they are ready to record directly with the Nuendo Marker window.
In addition, all cues can be imported directly into the EdiCue main window to export EdiCue ADR cue sheet PDFs or any other file type it can export.
For studios that record their ADR with Nuendo, they now have a way to load the ADR cue data from EdiCue PDFs, if the production sends them this type of PDF to record an actor. To do this simply load the EdiCue PDF into EdiCue and select the menu item: File > Send Data to Nuendo Project. This will create an 'ADR Cues' marker track with the cue data stored in cycle markers ready for record.
Demonstration of what's new in EdiCue v4
Full list of what's new in EdiCue v4
- Capability to read and write Pro Tools PTX files
- During PTX import you can now select to load data from clip groups, audio clips or both
- Added new 'Get Session' toolbar button to load the session that is currently open in Pro Tools
- Export stores cue data in clip groups with option to set the color of the clip
- New template sessions are saved as PTX files
- Integration with Nuendo 12
- New Project Interface window added to create new cues in Nuendo
- ADR Cues are stored in cycle markers in a single ADR cues marker track
- 'ProdInfo' and 'SceneNos' marker tracks can be created to store this data
- Cue data can be transferred instantly between Nuendo and EdiCue
- Compatibility will ARM (M1) macs by providing a universal binary app
- A new 'Compare ADR Cue Lists' window to check ADR cue revisions made between EdiCue exports
- New Session Interface window setting: On Get Clip > Bring Pro Tools to front
- While loading Pro Tools data
- Mute clips are now always loaded, and the mute state is stored
- Mute clips are only exported in PTX files as mute clip groups, so they can be retained while regenerating the cue session
- Provided new option to ignore clips on inactive tracks
- Mute clips are now always loaded, and the mute state is stored
- Option to load the character names from a PDF shooting script while creating a template session file
- Bug fixes
- Custom Cue Numbers with an alpha suffix are now shown correctly in the full cue number
- Check while appending the cue data in Pro Tools clip names that there is a space character between words
- Fix in the 'Cue Number Settings' tab to show the correct cue counter length when a non-default setting is restored
- Bug fix in the Session Interface window to restore the reason and priority shortcut keys. Broke in v3.4.2
- Ability to load Excel files with a 'Cell Format String' = "00\:00\:00\:00"
- Fixes in multiple locations to load and append EdiCue PDFs correctly that use feet+frames
- Fix so exports to a TBW list that uses footages now shows the correct value
To try EdiCue v4 for yourself, download the installer from the Download page. Once installed, run it and click ‘Try’ to activate a three day trial license.
NOTE: EdiCue v4 requires macOS 10.12+, Windows 8+ (64-bit), Pro Tools 12.6+, Nuendo 12+, while EdiCue v4 licenses require a 2nd or 3rd generation USB iLok or sharable iLok license.
For existing EdiCue full license holders an upgrade from v2 or v3 can be purchased from our web store. To transition to the new version, EdiCue v4 licenses can activate EdiCue v3.4.0+. Rental and EDU bundle license holders do not need to upgrade as these licenses automatically run both versions.