For years I've worked with Premiere and After Effects and after purchasing Macbook Pro I decided to move to FCPX and Motion for the incredible integration with Apple hardware.

It is so important to keep up with the industry standards, and I would love to see FCPX and Motion developed more frequently and to be used in more Hollywood productions.

An important note: These days AI and ML technology based tools pop up like mushrooms after rain, and I would love to see Apple encourage and push FCPX and Motion dev teams forward, giving them whatever they need to integrate AI capabilities to make the workflow even faster and more convenient, with limitless possibilities, such as AI based rotoscoping and keying.

The changes proposed would help adoption increase and increase my chances of collaborating with other studios more seamlessly. Please also bring back support of Waves plugins and other pro VSTs for M1, as they are crucial to my workflow for audio finishing.

Final Cut Pro X's Scopes and Multicam support alone are peerless in their elegance and ease-of-use-- The Multicam support far surpasses DaVinci Resolve's Multicam capabilities, while the overall philosophy of FCPX generally empowers an editor to begin working in a fraction of the time it would take to commence an identical project in Avid Media Composer.

Petty format-wars aside (BRAW vs. ProRes RAW), it would be nice to again generate broadcast-compliant Colour Bars & Tone within Final Cut Pro-- Not that Avid Media Composer is yet equipped to do this, either.

Nonetheless (and despite healthy skepticism and downright resistance), myself and colleagues have successfully employed the past several versions of Final Cut Pro X to develop and deliver episodic content for broadcast over the course of half-a-decade. For users of FCPX, the realm of remote collaboration is now a nascent revolution-in-waiting. With recent offerings by Apple's competitors, and the implications of the past two years of global disruption now foremost on everyone's mind, the big question is: Why wait any longer?

Parallel to Steven Sanders' comment on the current limitations of collaboration within FCPX, the way in which 3rd-party plugins are presently distributed and applied to an editor's work tend to effectively 'tie' an FCPX Library to one specific workstation. There has yet to be an equally-elegant method of efficiently managing or encapsulating system-installed plugins within (or alongside) an .FCPXBundle / Library. Such a capability would remarkably accelerate hand-offs between assistants, editors, and colourists, in an otherwise very-capable and broadcast-ready Non-Linear Editing application.

While Apple's plugin economy is certainly a boon to the individual editors who use Final Cut Pro X (and to those who collect the profits of such plugin libraries), this blind-corner in remote extensibility tends to dampen an editing department's ability to efficiently collaborate on common projects throughout the Post-Production process, and severely limits the effective size of such a team-- Therefore capping the scale and complexity of a project they can reasonably expect to embark upon together, when working within Apple's Final Cut Pro X wheelhouse.

Establishing an effective and respectful dialogue between Apple and their user-community, and working toward collective innovation and development may well continue to challenge the Editing Giants (Blackmagic, Avid, Adobe & Apple), to evolve and innovate, together. One would hope that the tools themselves become unobtrusive. Rather than binding us to brands or aesthetics, our tools ought to empower us to focus our faculties on crafting the stories we envision.