stands for Emotion File Finish, and is a cost effective software application that auto analyses, detects and normalises audio loudness violations in file-based media. eFF complies with the latest standards, based on ITU-R BS.1770-3 and BS.1771, ATSC A-85, OP59, TRB-32 and EBU R128.
Eff supports AIFF, WAV, MOV, and MXF files (OP1a and OP Atom), with either 16 bit and 24 bit uncompressed audio tracks, the Harris LXF format, and it supports MPG files with compressed MP2 audio tracks. eFF can read and write all types of media files that contain Dolby E encoded channels, plus extract PCM wavs from Dolby material, or create a Dolby E encoded wav from PCM material. Uniquely, eFF also supports the Panasonic P2 format, via an option.
Eff Comply can also process ‘multifiles’. WIth multifiles, there are a number of mono files in WAV, AIFF or op-atom MXF format, with each mono file providing a portion of a stereo or 5.1 signal. Eff opens all the relevant files, and combines them so as to calculate Loudness values from the correctly weighted components. Eff then works out what adjustment to apply to each individual file so that the combined fileset meet the targets, before creating a new set of compliant files.
Eff reads in an existing file, and compares the audio levels in the file with preconfigured profiles that are stored in the software, and adjusts the audio levels in the file either up or down, to meet whatever level targets you have configured. eFF can test to multiple loudness targets in a single pass, as well as check and report on True Peak values, and LRA.
It is a frequent requirement within Post to create multiple versions of the same material, to supply to different markets. If the loudness or PPM requirements for the different deliverables are not identical, it has been an inconvenient and slow process to adjust the audio, and a manual process is prone to operator error. Using eFF, this becomes simple. Additionally, by configuring a number of profiles in Eff matching your standard delivery specifications, there is much less scope for errors.
Select one of the following for more information:-
- Top Clippings
- Stereo, 5.1 or multi-channel?
- Bars & Tone
- ATSC A85 Loudness Compliance
- Graphical Display
- Manual or Watchfolder?
- Versions and Options
- Operating System and Hardware Support
- Dedicated P2 Support
- Codecs supported
- Customer Case Studies
- Track replacements and News [re: Telestream]
- Dolby E Doodle Doo
- Nobby-san, Hot Springs and the Aston
- Engine crosses the chasm
- (New at IBC) Top questions: audio and file based workflows
- New at IBC 2016
- News about audio and file-based workflows
- If you tried our file-based audio software, here's some new info for you
- Improve Operational Efficiency_ Use your edit suite just for creative work
- True Peak
- 3 Biggest Topics at NAB (and short video)
- Perfect Pitch for Audio Frame Rate Conversion
- EBU R128s1 Loudness Compliance (Eff and Engine trial download)
- Loudness: What is Gating?
- From the summer of love to the summer of hope...
- What Should (or Shouldn't) a Loudness Tool Do?
- Automating iTunes authoring, mastering, and the new compliance requirements
- Why are Loudness and PPM important?
- Loudness Compliance: The 10-Point Checklist
- What should I look for in file-based audio correction?
- 4K, versioning, and file-based operational efficiency (new podcast interview)
- MX1: loudness compliance with a wide range of Dolby E audio configurations
- QuickTime MOV files with two MOOV atoms at Premiere Digital Services
- NAB 2018... customer tales from the year past
- What the playout engineer said...
- The Heat Is On
- Doing business at IBC (or, what really happens in Amsterdam...)