CommandPost is a “free and open source macOS application that makes your post production and editing life faster and more fun. It adds hundreds of features to Apple’s Final Cut Pro to make it even better and more enjoyable to edit with, including extensive control surface support.” (CommandPost.io website)
(Click to see larger image.)
I’ve used it for years and find it indispensable, especially for three features: multiple clipboards, exporting the Timeline Index as a CSV file and enabling the FCP timeline to automatically scroll.
In fact, the reason I got it in the first place years ago was for the timeline scrolling.
However, that scrolling feature is now a problem – because Apple added timeline scrolling to FCP in their latest release.
Here’s what you need to know.
(Click to see larger image.)
The scrolling timeline is turned off by default in FCP (bottom red arrow). To turn it on, check Scroll timeline continuously during playback in Preferences > Playback.
Fortunately, the scrolling timeline is also off in CommandPost (red arrows above). To turn it on, select Enable Scrolling Timeline. To turn it off, deselect it. This screen shot shows it disabled.
However if BOTH these options are enabled, FCP becomes unstable.
The fix is easy, turn one of them off. Personally, I enable the scrolling timeline in FCP, turn it off in CommandPost, then use CommandPost for everything else.
One Response to Caution: A Scrolling Timeline Conflict in Apple Final Cut Pro
Thanks, Larry. I use Command Post with my Loupedeck console when I edit in FCPX. Now I will know to disable timeline scrolling in FCPX so I don’t have glitchy behavior. Good tip!