This week I’ve launched my first big plugin pack for Final Cut Pro X. Drop Alex4D Animation Transitions onto titles, images, videos and generators to animate them on or off the screen. Instead of a logo or text just appearing, it can slide, spin, scale or skid on. You can also animate clips off screen.



To find out more – including demo videos and a 32 page manual – please visit

From now on I’ll be posting more regularly on my main blog at

I’ll summarise recent notes from there here on my old blog. To see my latest news, notes and links, bookmark my new place.

November 4: Apple’s October 2013 announcements: What’s in them for editors? The mainstream Mac sites aren’t focussed on looking at Apple announcements from a post production point of view.

November 5: iMovie (2013) and Final Cut Pro X 10.1 – what new features that debuted in the new version of iMovie might appear in a future version of Final Cut Pro.

November 6: Final Cut Pro X 10.1 revealed? iMovie (2013) is an unreleased version of Final Cut Pro X with a consumer UI

November 7: New MacBook Pros and MacPro: 4K at high refresh rates via DisplayPort? – will the fast storage, memory and GPUs in Apple’s newest computers be able to support 4K at higher frame rates?

November 7: iMovie and Final Cut Pro X 10.1 part 3: Scripting and plugins – more on what’s hidden within the new version of iMovie.

November 9: Final Cut Server: December resurrection?

November 14: iCloud collaboration for more Apple applications? – Apple added interesting collaboration features to Keynote, Pages and Numbers. Find out more about features that might one day appear in pro applications from Apple.

November 19: DaVinci Resolve 10 is Final Cut Pro X 10.1 compatible

November 20: Import Final Cut Pro X projects into iMovie using hidden workaround

November 25: iMovie and Final Cut Pro X 10.1 part 4 – including a rundown of accessibility features – which are useful for those who cannot use traditional control devices and those who want to use workflow applications to control Final Cut.

November 26: FCPX Grill – the new Final Cut Pro X podcast – a detailed rundown of the first two episodes of Chris Fenwick’s new podcast.

November 27: The case for a new Apple professional application – musing on how Apple might demonstrate the power of the new Mac Pro sends me off in the direction of wish-fulfillment

When the new Mac Pro was previewed at this year’s WWDC, Apple said it would be great at editing 4K.   4K is the next size up from HD – twice the pixels horizontally and vertically: four times the detail. UHD is the consumer brand name for TVs that can show 3840 by 2160 pixel footage.

Apple also mentioned that a new version of Final Cut Pro X is being prepared to make the most of the new machine. However, Final Cut Pro users have been able to create high resolution timelines since the mid-00s.


Although it has been possible to create 4K timelines for many years, smooth editing of 4K footage requires instant playback of more than one stream of video footage at once. For example if you had clip A transitioning to clip B while clip C is overlaid as a picture in picture, your editing software would have to play back clips A, B and C at the same time – changing the transparency of clips A and B while scaling clip C.

Up until now, there have been two strategies of dealing with high quality video on systems that are too slow: wait for the computer the render the video to a single combined clip which can then be played back, or to make lower quality versions that can be edited without rendering.

What could the next Mac Pro / Final Cut Pro X combination bring to 4K editing? The ability to import 4K clips and to work with them instantly – playing more than one at the same time without having to wait for rendering.

Two problems need to be fixed to make this work – fast enough hardware to decode large amounts of video information and a fast enough connection to the storage to get large amounts of data onto the screen.

Read More

To help people work out which Macs work best with Final Cut Pro X, it is useful to refer to a standard speed test.

All but one of the MacBook Pros with Retina configurations do not have dedicated GPUs. New Mac software is depending more and more on GPU power. Editors want to know if the integrated Intel Iris and Iris Pro Graphics GPUs are powerful enough to run professional software well.

Early testing shows that Iris Pro graphics are better than many expected. Take a look at a new post at Bare Feats:

In the past we sneered at the integrated GPUs and their puny performance. Not any more. The Intel Iris and Iris Pro are every bit the match or master of discrete NVIDIA Mobile GPUs — at least when it comes to OpenCL acceleration.

Although it is great news that integrated GPUs are getting better, many are worried that the MacBook Pros should be avoided until Iris Pro has improved a little more.

A speed test proposed by was to time the render of Final Cut Pro X’s built-in ‘Far Far Away’ title on a 23.975 1080p timeline. This test puts enough pressure on main memory and GPU memory to separate older generation Macs from more recent computers.

Over at the the forum, qbe asked me to do the ‘Far Far Away’ test on my new late 2013 MacBook Pro 15″ using only the built-in Iris Pro Graphics and also on only the Discrete GeForce GT 750M GPU which I included in my BTO Mac.

It turns out that the test wasn’t tough enough to show a difference between the two GPUs:

MacBook Pro late-2013 Discrete GeForce GT 750M 2GB 18.8 seconds
MacBook Pro late-2013 Intel Iris Pro Graphics 1GB 19.2 seconds

I’ve come up with a test that shows the differences between these GPUs and other Macs…

The BruceX benchmark

BruceX is a small Final Cut Pro X XML file that you import into Final Cut Pro. It creates a very short timeline at the highest possible standard resolution that Final Cut can handle: 5120 by 2700 (at 23.975 fps). It uses standard Final Cut generators, titles and transitions. As it uses many layers of complex content, it requires lots of GPU RAM.

The benchmark is based on timing how long a Mac configuration takes to export the project to disk.

To use this import the XML file at

…and time the export of a 5K master file from the timeline.

1. Have both QuickTime player and Final Cut Pro X open at the same time.

3. In Final Cut Pro X, go to ‘Final Cut Pro:Preferences…’ – in the Playback tab make sure ‘Background Render’ is off.

3. Use the ‘File:Import:XML…’ command to import ‘BruceX Test – 5K.fcpxml’ to create a very short but complex 5K project.

4. Click the new ‘BruceX Test – 5K ‘ timeline (this makes the Share command selectable)

5. Export the QuickTime movie by choosing “File:Share:Master File…’

6. In the dialogue box that appears, click the ‘Settings’ Tab

7. In the ‘Video Codec’ section choose a flavour of ‘ProRes’ (this instruction used to require H.264 but this selection caused exports to fail in OS X 10.9 – the version of OS X require by Final Cut Pro X 10.1 and the late 2013 Mac Pro)

8. In the ‘Open With’ section, choose ‘QuickTime Player’

9. Click the ‘Next’ button in the bottom-right of the dialogue box

10. In the Save sheet, choose a name and location for the export – export to your fastest drive connected using your fastest connection.

11. Get your stopwatch ready and time from when you click ‘Save’ until you see the movie open up in QuickTime Player (some testers report that the movie plays as black in some setups – this is likely to be the player having problems with 5K H.264, the movie is probably fine and will work in other players such as VLC)

12. If possible do the export at least three times. Your configuration’s BruceX Score is the average export time in seconds. Before timing the next export, restart Final Cut (otherwise the exports speed up each time because X does a little caching renders to save time).

BruceX Final Cut Pro X benchmark

These results include those posted at the Forum and from

The results show that BruceX tests processor power, but also shows that Iris Pro Graphics has some way to go to match a discrete graphics GPU in the new MacBook Pro 15″ with Retina

MacBook Pro late-2013 2.6 Ghz Quad Core i7
16GB 1600 MHz
Discrete GeForce GT 750M 2GB GPU
OS X 10.9.0
88 seconds

MacBook Pro late-2013 2.6 Ghz Quad Core i7
16GB 1600 MHz
Iris Pro Graphics 1GB GPU
OS X 10.9.0
163 seconds

( To choose which GPU to use for the test on my MacBook Pro, I used gfxCardStatus by Cody Krieger – a Shareware app downloaded from )

If you post results in the comments below, I’ll update the graph.

Although many Final Cut Pro X users were disappointed that Apple didn’t announce a new version on October 22, the day’s launches provided some interesting news.

The first of which is that most of the effects, titles, generators and transitions in iMovie 2013 were created using Motion 5, the animation software used to make plugins for Final Cut Pro X.

It is possible to open the titles, effects, generators and transitions built into iMovie using Motion 5.

Also, using an undocumented method unsupported by Apple, you can install Final Cut Pro X plugins into iMovie 2013.

More later today!


Get every new post delivered to your Inbox.

Join 3,656 other followers

%d bloggers like this: