-
My suggestions for improved Audio Post support …
Here is my personal perspective on what FCPX needs with regards to improved support for audio. I get that it makes sense to send to Pro Tools, Audition, or Logic X. However my guess is these days many editors prefer to handle audio finishing right in the NLE. I could be wrong.
[– A mixing “Environment.” For example – you can designate individual storyline clips or a selected group of clips and “Open in Mixer.” This creates a typical channel strip for each instance with Inserts, Sends, and the ability to route to Buses. The signal routing in this Environment is the absolute signal chain. In other words – the output of the mixer is what you hear when you playback the Storyline.
This concept would add a ton of flexibilty in terms of audio processing, mixing, loudness compliance, metering, and outputting.
[– Better Audio Meters. In fact standard PPM needs to be an option, not the only choice. I think most people still don’t realize that Peak Meters are useless when it comes to measuring perceived loudness. The real purpose of Peak Meters is to prevent overload (aka clipping). You can have two individual clips with the same exact peak ceiling, and clip A could very well be much *louder* perceptually than clip B. Apple should add a dedicated Loudness Meter that measures Program Loudness, Short Term/Momentary Loudness, Loudness Range, and True Peaks. If you are not sending your mixes to Pro Tools or Logic X – well then compliance support is a necessity within FCPX, especially regarding The Calm Act, EBU R128, ATSC A/85, etc.
And even if Apple did not do this, my mixing Environment idea would make it possible to use Loudness Meter plugins on entire mixes, not just on individual clips on a per instance basis. That’s highly inefficient. Sure, you can create a Compound Clip – but that is another story.
[– A File Based Editor. Right now it’s near impossible to perform intricate dialog edits in FCPX. Yup – I realize the Storyline audio clips can be customized visually to simplify editing. However it’s still cumbersome. They need to do away with the cartoonish, rectified waveforms. Best case scenario would be an internal option to “Open In Editor” resulting in a file based editor similar to what is present in Audition, Bias Peak Pro, or Soundtrack Pro. And include basic DSP tasks like Peak Normalization, Average Loudness Normalization, Add Silence, Convert to Stereo/Mono, etc. Lastly, the ability to process files using the bundled plugins as well as any installed third party plugin options. What ever you decide to do to the loaded clip, the resulting edits are reflected in the Storyline instance.
That’s my take …
-paul.