Articles tagged with: Final Cut Pro X

Three kinds of ‘Delete Clip’ in the Final Cut Pro X timeline

Wednesday, 18 February 2015

Because Final Cut Pro X doesn't have tracks, Apple have made three kinds of delete for clips in the timeline.


This clip has two connected clips: a video cutaway and an audio clip.

If when removing the selected clip I want the connected clips to be removed, I'd press the Delete key:


If I want to delete the selected clip but keep the connected clips and not change the duration of the edit, pressing Shift-Delete replaces the selected clip with a gap clip:


If I want to keep the connected clips and close up the timeline when deleting the selected clip, I would press Option-Command-Delete (some people call these two modifier keys 'alt-cmd'):


Video in text Final Cut Pro X tutorial

Monday, 08 December 2014

As well as their weekly free Final Cut Pro X and Apple Motion tuition under the MacBreak video series for Pixelcorps, Ripple Training also make free short videos that show how to achieve special effects.

This Video in Text Effect tutorial shows how to make a video clip appear within text while showing other content behind the text.

Selected Final Cut work

Sunday, 07 December 2014

An important web site that Final Cut Pro X fans should know about is - a site dedicated to high budget productions edited using Final Cut. Those who think Final Cut Pro X isn’t for professionals should investigate what it is already being used for.


One of the videos showcased is the music video for 'We Exist' by Arcade Fire which was edited by Thomas Grove Carter - which is nominated in the Best Music Video category at the 2014 Grammys.


Many hours of free Final Cut Pro X videos from Ripple Training

Friday, 05 December 2014

[Updated in June 2017] Since before Final Cut Pro X was launched, Ripple Training have been known to provide the best Final Cut video tutorials. As well as great value training products, they also continue to give away hours of training on YouTube.

Here is my YouTube playlist of almost 200 videos that can be used as a free training course for those starting out with Final Cut. They have been released almost once a week every week since version 10.0.0 was launched.



The user interface of Final Cut changed a great deal with version 10.3, so the playlist starts with Ripple’s lessons on getting started with Final Cut using the new UI and ways of working.

The playlist is then chronological. You'll see the old user interface and old way of organising footage and timelines.

As well as these longer tutorials, Ripple also make tip videos in their weekly 'Final Cut Pro X in under 5 minutes' series. As the information in each video doesn't depend on the previous one, their 'under 5 minutes' YouTube playlist is in reverse chronological order.

These many hours of training are free, but they weren't designed as a carefully constructed programme. If you do watch them you'll have to work harder to put everything together. If you find these videos useful, I strongly suggest that you check out Ripple Training's paid video tutorials. You'll learn all the same information, but the process will be quicker and the knowledge easier to retain.

For the paid training, start with Final Cut Pro X Core Training, then go on to Media Management in Final Cut Pro X. After that, move on to Sound Editing and Color Correction. Then choose tutorials based on your specific needs: Multicam Editing and Warp Speed Editing.

Alternatively, if you already know the Final Cut Pro X basics, use these free videos to learn more about areas of the application you are less certain of.

Ripple also have many free hours of Motion 5 training videos, alongside great paid training courses.

Diagnose Final Cut Pro X plugin problems

Thursday, 04 December 2014

A common problem when moving Final Cut projects from Mac is that of missing plugins. Even if the plugin is on both Macs, it works on one, but the project can't seem to find it on the other.

A useful tool to aid in Final Cut Pro X detective work is Spherico's X-FX Handler application (Direct download). If you find it useful, This email address is being protected from spambots. You need JavaScript enabled to view it. to find out how to donate some money to show your appreciation.

Export the problem Final Cut Pro X 10.1.X project as an XML file and open it with X-FX Handler. It will show a list of all the effects, transitions, titles and generators in the project:


The listing shows where the project expects the find each plugin. The majority of problems occur when a plugin seems to be in the same place on the second machine, but isn't. This happens when two folders seem to have the same name. You might have two folders in the Finder named "Transitions" - if you use the Get Info command in the Finder you might find one is named "Transitions" and the other is "Transitions.localized"

For more information on how X-FX Handler works, use the Help menu to read the detailed manual. It shows how although a plugin seems to be installed on both Macs, there are different places where the plugin might be - which means a project moving from one Mac to another might not recognise that the plugin is installed on the new machine:



Final Cut Pro X 10.1.4

Tuesday, 02 December 2014

The 10.1.4 update appeared on December 2nd 2014. It was a maintenance release, not a feature update. As well as the usual bug fixes, Apple added very useful import and export features in the form of MXF handling through the separate Pro Video Formats 2.0 installer.

Both should be available in the Updates pane of the App Store application. You can download MXF support directly from Apple as well.


Ripple Training's MXF introduction and how it works in Final Cut Pro X:

Need MXF export but don't want to update Final Cut Pro X?

If you are in the middle of a project it is inadvisable to update Final Cut Pro X, but you can still produce MXF files if you have Compressor or Motion. Apple's Final Cut Pro X, Compressor & Motion MXF FAQ mentions that you can  use Apple's new Pro Video Formats 2.0 MXF export with versions of Final Cut Pro X, Motion and Compressor.

MXF Options


For AVC-Intra you can choose between 720p, 1080i and 1080p, 50Mbit/s and 100Mbit/s. You can also choose between 2 and 16 even numbers of audio channels at either 16 or 24 bits. You can also start timecode at the native value or force it to start at 10 hours or 1 hour.

As well as MXF working in Apple's ProApps, you can also use QuickTime Player 7 to open and play MXF files:


MXF is a wrapper format for different codecs, so you'll find that in some cases although you can export a flavour of MXF, you won't be able to import it back into Final Cut or play it using QuickTime Player 7:


AVC intra HD formats and IMX SD format show as greyed out in the import window. Uncompressed either doesn't export properly or play back properly.

Final Cut Pro X is now UK DPP-compliant

Since October 1 UK broadcasters have required that programmes be submitted as files - not on HD tape. The format they chose MXF OP1a with specific metadata which is known as the AS-11 standard. Alex Snelling (who wrote the standard work on Final Cut Pro X 10.1 Library workflows) has written a new document on how to prepare programmes for broadcast using Final Cut Pro X.



Download it from the 10dot1 website. The same page also includes specialised Compressor presets that aid AS-11 export.

This is good news for Final Cut Pro X users outside the UK because the AS-11 delivery standard was created in conjunction with the US-based Advanced Media Workflow Association. This means there is a good chance this standard will be adopted elsewhere in the world.


Don't forget that although recent updates haven't caused too many problems, it is best not to update Final Cut while in the middle of a project.

CoreMelt reported that all their plugins work with 10.1.4.

Philip Johnston reports that MXF AVC Long GOP files from Panasonic cameras now work with Final Cut Pro X, but XAVC-L footage from Sony's PXW-X70 didn't work.

Not updated

It is rare that Apple Motion isn't updated at the same time as Final Cut Pro X. This implies that Final Cut's effects and compositing didn't changed between 10.1.3 and 10.1.4.

It is odd also that the ProApps team didn't update the UI to match OS X Yosemite - unlike Pages, Keynote and Numbers.

A little bit more 'Pro'

With this maintenance release Apple added a feature that is useful for broadcasters, but not any other features for the wider constituency of Final Cut editors. In July 2014 I compared 10.X with Final Cut Classic using graphs showing which markets each update supported. The last major update was 10.1.2:

10.1.2 update compared with previous versions

Here's where 10.1.4 fits into this progression:



As I said in July, it looks like the next major version of Final Cut will shore up the middle markets: those using Final Cut Pro X for important and/or paid work and people working in smaller production companies. As well as features that demonstrate OS X Yosemite continuity and extension capabilities alongside Apple's replacement for iPhone and Aperture.

Alex4D on podcasts

Friday, 21 November 2014

A roundup of my appearances on post-production podcasts:

April 2012

Digital Production Buzz

I talked to Larry Jordan about how I came to create plugins for Final Cut Pro and how things changed when Final Cut Pro X came along. Thanks to Michael Horton of the LA Creative Pro User Group for getting me on the air!

iTunes · Website (my interview only)

January 2013

Moviola Digital Filmmakers Podcast: Creating Final Cut Pro X Effects Using Apple Motion 5

After presenting one of four webinars for Moviola, I answered a few questions on making Final Cut plugins.


June 2013

Going POSTal

While attending the London SuperMeet featuring Tom Rolf, I said a few words during Ben Barden's coverage of the event.


August 2013

Go Creative Show 004: Pure Logic

On the release of Logic Pro X, I talked to host Ben Consoli about what the update means for Final Cut Pro X users.

iTunes · Website

October 2013

Go Creative Show 014: Hi Larry

I covered the announcement of the radically different Mac Pro.

iTunes · Website

November 2013

FCPX Grill 004: Reading the FCPX Tea Leaves

I talked to host Chris Fenwick about the (then) future version of Final Cut Pro X hidden inside a new version of iMovie.

iTunes · Website

December 2013

FCPX Grill 008: FCPX 10.1 Mini Intro

Chris and I discuss our initial impressions of Final Cut's biggest update.

iTunes · Website

February 2014

FCPX Grill 022: Homegrown Plugins

We discuss unreported features of Final Cut Pro X 10.1 and go into detail on plugin development.

iTunes · Website

July 2014

FCPX Grill 061: How Pro is Pro?

As Apple hardly communicate with traditional post production market, I talk to Chris about how Apple concentrates on different aspects of Final Cut for each release - in order to guess what Apple might update next.

iTunes · Website

November 2014

FCPX Grill 095: Let's Talk Motion

Chris Fenwick, a long-time Adobe After Effects designer, interviewed me about Motion, Apple's motion graphics production application.

iTunes · Website

FCPX Grill 100: An Incredible Year

I was part of a round-table of past and future guests celebrating 100 episodes of the Grill.

iTunes · Website


New ClipExporter 2: Final Cut Pro X export to After Effects and Nuke

Monday, 10 November 2014


New on the Mac App store: ClipExporter 2 for Final Cut Pro X. It takes Final Cut Pro X timelines and makes them editable in Adobe After Effects and Nuke. Although Final Cut has the best NLE real-time compositor, there are times when more complex problems need to be solved. Many high-end TV and feature films use After Effects and Nuke to create more advanced effects and compositions.

ClipExporter2 also exports media managed clips from Final Cut - useful for other post production tools that need the footage used on the timeline only. A useful tool for getting media managed RED footage onto an After Effects timeline.

ClipExporter 2 has been rewritten to take advantage of all the features of Final Cut's XML format - recreating timelines in After Effects and Nuke. You can even choose which clips to export by only converting clips with specific roles.

As part of the export process ClipExporter 2 also produces a clip log listing all the clips being converted (in a timeline or the clips with specific roles which will be exported). The list includes timecode information and Final Cut metadata and can be exported as a CSV file, which is useful for workflow administration.

ClipExporter works in four modes.

Export to Adobe After Effects

Timeline elements including blend modes, position, scale, anchor point, rotation, distortion, notes and markers are recreated as AE projects. ClipExporter 2 also translates keyframes of most of these parameters.

It even converts retimed clips, metadata and notes.

Here's a timeline in Final Cut:


Including a note to the compositor on one of the clips:


Just the After Effects logo is selected - this is After Effects export mode - without media management.


On export a clip report is shown which can be exported as a text file:


ClipExporter generates .jsx files. In After Effects .jsx files are script files that are run using the File:Scripts:Run Script command.

The timeline in After Effects including a marker and the metadata note appearing as a layer comment:



Not Dynamic Link, but quick to update in Final Cut

As ClipExporter doesn't use Adobe Dynamic Link, you need to render your After Effects project as a QuickTime movie and import it as a clip in Final Cut Pro X (keeping it external to the library). However you can make changes ripple through to Final Cut easily. Once you have updated the After Effects project, re-export the QuickTime movie with the same name in a sub-folder of the location where you first exported. In the Finder then replace the first export with the second version. It will be updated automatically in Final Cut Pro - even if it is editing the timeline where the clip is used.

Media management

ClipExporter's Video Exporter exports only the video used in a timeline (with optional handles) as new clips - not re-encoding, creating new smaller ProRes, H.264, AVCHD and RED files. ClipExporter even adds Final Cut Pro X-specific metadata to the new smaller clips (on all formats apart from RED clips). Define which metadata is included by choosing the relevant metdata view when exporting the XML final from Final Cut. 

ClipExporter includes naming templates which name the new smaller clips to match the import specifications of other high end post-production tools.

Export media managed timeline to After Effects - including RED footage

After Effects 'linked mode' does the media management of the Video Exporter - creating copies of only the media used in a Final Cut Pro X timeline and makes a After Effects project that uses the new clips as a source.

In this mode not as many parameters of the Final Cut timeline can be recreated in After Effects due to limitations in the Final Cut XML format, but you can add notes to the clip metadata which will appear as layer comments in AE.

Export media managed timeline to Nuke

The used footage only (with optional handles) is copied into new clips using the source codec and each clip is converted into a Nuke file. All the clip metadata is included in a Backdrop node. If you need to export a After Effects project with the same timeline, that is also an option. Here are is the result of exporting the previous Final Cut Pro X timeline to After Effects and Nuke in the Finder:


For more information, including a 30-day demo version visit ClipExporter. Download it from the Mac App Store at an introductory price until November 23.

Retina Tax: Some Mac display modes slow down Final Cut Pro X exports

Sunday, 09 November 2014

When Macs first got retina displays with the MacBookPro with Retina display, I wasn't interested. I was used to my 17" MacBook Pro with the 1920x1200 screen option. What was the point of getting a 15" screen that would make 1440x900 look better. 1440x900 points is too small for comfortable editing in Final Cut or any modern UI. I also didn't want the GPU wasting resources supporting a retina display better used for faster rendering and exporting.

My 1920x1200 17" MacBook Pro was fine for HD editing. In Final Cut Pro 7 it was possible to have 2 up display of footage at 50% and 100% playout of HD when going full screen. When I added my 27" iMac, I could view 1920x1080 footage on its 2560x1440 at 100% with either the event viewer or inspector open. In practice when editing HD, I don't often need to see the whole frame at 100%.

Last year, when my 17" MacBook Pro was four years old, I couldn't resist the new 15" MacBook Pro with retina display. The downside of the GPU wasting time on retina calculations was outweighed by faster CPU and very fast 1TB SSD (800MB/s). Knowing that the display could also set to 1920 by 1200 made it good enough for editing in Final Cut Pro X.

Ever since the iPhone 4 introduced retina displays, people have been waiting for desktop retina displays from Apple. When the 27" iMac with retina was first rumoured, I wondered what the point would be for editors. Why have a better rendered UI when what we work with is moving video. Even at desktop viewing distances, it is hard to tell the difference between HD and 4K when video is being updated at 24 or more frames per second.

The cost of retina when exporting from Final Cut Pro X

Again I thought that the GPU would be wasting power on the UI instead of working on video. I visited an Apple Store and used my BruceX benchmark to compare movie export times with and without GPU supporting all the pixels on the retina display. BruceX is a small xml file that doesn't use any external media to test the GPU (and the CPU a little) to export a very complex 2 second 5K ProRes 422 QuickTime movie.

I ran the benchmark on a iMac (Retina 5K, 27-inch, Late 2014), 3.5 Ghz Intel Core i5, 8GB, 1TB Fusion drive, R9 M290X 2GB GPU. The average of four tests was 50.1 seconds. I then used SwitchResX to change the display from 2560x1440 HiDPI (Retina Best) to 2560x1440 (non retina). The export time of the 2 second 5K reduced to an average of 43.3 seconds. That's around 14% faster in non-retina mode. 

So my tip for those who have the iMac with Retina 5K display is to switch resolution to a non-retina mode when exporting more complex timelines when you are under a tight deadline.

For more BruceX results visit this thread where people have reported values for many Mac configurations - including Hacktoshes and using many different graphics cards. 

Retina tax also applies to MacBook Pros with Retina

I've also tested my MacBook Pro with Retina (15" late-2013, 2.6 Ghz Core i7, 16GB RAM, 1TB SSD, GeForce GT 750M 2GB GPU).

It turns out that retina More Space display mode is slower than others:

Retina More Space (3840x2400 scaled down to 2880x1800 native pixels): 87 seconds

(Best) Retina (2880x1800 native resolution): 80.6 seconds

1400x900 (doubled in scale to 2880x1800): 80.4 seconds

1920x1200 (scaled up to 2880x1800): 79.2 seconds

So, on Retina Macbook Pros with displays set to More Space, if you want to save a little rendering time in Final Cut Pro X, change the resolution to Best (Retina) before exporting.

Compared with other Macs


More to the iMac 5K than 27" retina

Only when trying out the iMac at the Apple Store did I remember that the display could be set to 'More Space' instead of 'Best (Retina).' That is an advantage over my current 27" iMac. Here's a 4K clip displaying at 50% on a 2560x1440 screen - showing the same amount of UI that a 4K clip displayed at 100% on a retina 5120x2880 display:


The 'More Space' setting simulates a 3200x1800 point display on an imaginary 6400x3600 display that's even larger than the native pixels. This is similar to the Retina MacBook Pro 15" GPU showing a 1920x1200 point display by drawing to an imaginary 3840x2400 screen and scaling the image down to the native 2880x1800 pixels.

Working with HD/4K on a 6K+ display allows for more Final Cut UI while editing:

5K more

In this case, I set the event filmstrip size to the maximum. Here is a closeup of those clips at native resolution:

5K more detail

A selection from the full 5120x2880 screenshot.

What would 6K non-retina be like?

A silly thing to do with SwitchResX (and other similar tools such as QuickRes - the tool I have on my Retina MacBook Pro), is to set the display to be 6400x3600 non-retina.


The 4K image appears the same, but the UI is half the size:


The linked image is a 50% version of the source image (the full 6400x3600 image).

The good news is that although the iMac is labelled as 5K, Final Cut Pro X UI works very well on its simulated 6K display.

Apple's 'Magnetic Timeline' Final Cut Pro X patent

Wednesday, 29 October 2014

This week Apple was awarded a patent related to the Final Cut Pro X timeline. It is available as text and 95 page PDF. It was applied for on June 6, 2011. Most of the abstract covers only part of the patent:

A media-editing application of some embodiments allows a user of the application to group media clips displayed in the timeline into a single clip representation. A composite display area of the media-editing application often displays numerous clips at various instances in time and at various levels in the compositing hierarchy. To reduce the number of media clips in the timeline, the media-editing application of some embodiments allows the user to select several media clips and combine them into a one media clip representation. In this manner, the media-editing application reduces the congestion in the timeline. These single clip representations are referred to as "compound clips." Compound clips can be viewed as containers that can include several media clips of the same type in some embodiments, or that can include several media clips of several different types in other embodiments.

Although the abstract mainly covers compound clips, most of the ways a non-track-based magnetic timeline works is described in the patent itself. A little 'smuggling' by the patent lawyers?

Here's a list of contents to show what editing software features Apple now has a patent for. Instead of reading the text, use this list of figures with some interesting quotes from the relevant sections. Remember that the phrase "in some embodiments" doesn't mean that Apple planned to add that feature to Final Cut Pro, these clauses are included to make the patent cover a wider range of possible editing software features.

Fig 1: Main UI


Connected clips in secondary storylines are referred to as "anchored clips in anchored or secondary lanes."

Instead of, or in conjunction with, having several levels of media clips that anchor off the central compositing lane, some embodiments allow media clips to be placed in these anchor lanes and to be anchored off of other anchored media clips placed in these anchor lanes.

Skimming within clips with the option to see skimmed clips in the viewer:

In some embodiments, the playback (or skimming) is not shown in the timeline clips, but rather in the preview display area

Fig 2: Selecting ranges in clips before reducing audio volume of range

Fig 3-4: Expand Audio/Video clips and Detach Audio

Fig 5: Change appearance of clips in the timeline

Some embodiments may also allow the user to directly manipulate the media clips (e.g., by expanding or contracting the audio or video portions using a cursor) to change the appearance.

Fig 6: Zooming timeline horizontally

Fig 7-9: The playhead and the skimmer

Fig 10-11 Clip skimming

Fig 12 Insert edit

Fig 13 Adding a selected event clip to the end of the timeline

Fig 14 Connecting a clip

Fig 15-18 Replace edits

Gap clips to maintain duration:

When the second media clip is shorter in duration than the first media clip, some embodiments replace the first clip by placing the second clip at the point that the first clip starts. This will cause a gap to close or to be filled with a position clip after the second clip.

Fig 19-20 Gap clips

Known here as Position clips

Fig 21 Trimming connected clips

Including the fact that if connected clips are audio only, they can be trimmed down to the sample level instead of being limited to whole frames.

Fig 22 Slipping clips

Fig 23 Connection point

Including an option to use the point dragged from in the event clip as the connection point when dragging to the timeline i.e. if the mousedown is 1/3rd of the way along the clip or selection when you start dragging, then the connection point is set to 1/3rd along the clip.

Fig 24 Changing the connection point

Fig 25 Creating a secondary storyline

Some embodiments allow the user to create a container first in an anchor lane and add media clips into the container from the timeline or the clip browser.

Fig 26 Extend edits

Fig 27-31 Editing and moving the playhead using timecode entry

Fig 32 Editing with video only, audio only or both audio and video

Fig 33-35 Two Up view

The media-editing application in some embodiments displays two frames in the viewer  for other types of editing as well. Some of different types of editing include a ripple edit, a slide edit, a slip edit, etc.

Fig 36 Making compound clips

Fig 37 Navigating Timeline History

Fig 38 Bookmarking a timeline history view

Fig 39 Timeline history state diagram

Fig 40 Retiming a compound clip

Fig 41-46 Importing clips into a database

Including transcoding and proxy generation

Fig 47-50 How timelines are represented in the database

Fig 51 Application architecture


It might be possible to associate some of the internal frameworks in Final Cut Pro X and iMovie with elements of this diagram. For example, the Rendering Engine could be implemented by 'Ozone.framework' - the 'headless' copy of Apple Motion 5.X in Final Cut and iMovie. You might be able to guess what 'TLKit.framework' does.

There's an interesting hint about how the application defined in the patent might not only be a traditional application running on a computer: 

In some embodiments, the media editing application is a stand-alone application or is integrated into another application, while in other embodiments the application might be implemented within an operating system. Furthermore, in some embodiments, the application is provided as part of a server-based solution. In some such embodiments, the application is provided via a thin client. That is, the application runs on a server while a user interacts with the application via a separate machine remote from the server. In other such embodiments, the application is provided via a thick client. That is, the application is distributed from the server to the client machine and runs on the client machine.

Fig 52 Computing device

All software patents need to include a description of a computing device for the software to run on.

Review: MoviePro 3K video camera app for iPhone 6 Plus

Monday, 27 October 2014

MoviePro has been available on the iTunes App Store for a long time, but it has been updated to take advantage of the faster processors and better camera processing in the iPhone 6 and iPhone 6 Plus.

The headline news is that MoviePro can record at 3K at up to 30 frames per second on the iPhone 5S, iPhone 6 and iPhone 6 Plus. 3K is 3072x1728 pixels per frame. 

This 4K video on YouTube shows how much bigger 3K is than HD and shows the quality of the recording. The quality isn't limited by the camera, but by YouTube:

When viewing this full-screen, make sure YouTube is playing the 4K version by choosing '2160p 4K' from the cog pop-up menu.

There is also the problem of not having a big enough screen to show the video on. Here is the same video with the centre HD area cut out. It shows the quality, and also shows how much you can zoom 3K video in an HD frame without losing any quality.

If you want to download the source 4,587,894,223 byte 3840x2160 ProResLT file, it will be available for a month here (or until HighTail turns off the unlimited downloads/bandwidth setting for the file).

Here is a partial list of resolutions MoviePro can record in: 320x240, 1024x768, 1600x900, 2560x1920 (4:3), 2560x1440, 1920x872 (2.20:1), 1920x698 (2.75:1)

As well as high spatial resolution, MoviePro can also record in a large range of framerates: 2, 3, 4, 5, 6.. in single frame increments to 23, 24, 25, 30, 48, 50, 60, 96, 100, 120, 192, 200 and 240 frames per second. 1080p can be recorded at up to 60 fps. 240fps at 1280x720.

Pro features

As this app has been around for a while, there have been many improvements over the months to support professional use:

High data rates

For 3072x1728 25fps footage, the H.264 file has a data rate of 120-130 megabits per second. That's up to 681K per frame. If you encoded a QuickTime movie using Photo Jpeg with a quality set to 'Low' (25), its data rate would be around 640K per frame. If you record at 30 frames per second, the data rate isn't higher, so you get lower quality frames.

If you record 3072x1728 at 2 frames per second, the data rate goes down to around 25 Mbps. That results in very high quality frames.

The data rates fall quickly for lower resolution videos: 3000x1688 movies are recorded at around 115 Mbps, 2560x1440 at 85 Mbps, 1920x1080 at 45 Mbps.

The data rate cannot be set directly - 'Video Quality' is defined as a percentage of the quality the iPhone would normally record:

mp3.5 presets


As well as having a on-screen sound meter, there is also an on-screen control for input record level. Using a splitter cable you can monitor with headphones while a separate microphone records the scene. You can also use a bluetooth connect microphone.

You can also control how audio is recorded: choosing between none, low, medium, normal (?) and uncompressed:

mp3.5 audio

It seems the data rate for Low, Medium and Normal have the same result: 64 Kbps 44.1 kHz AAC. Uncompressed is 710 Kbps 44.1 kHz uncompressed. There are no sample size or frequency controls.


You can group settings into five presets which you can swap between with a tap. Pressing the 'Star' control near the record button brings up the presets:

mp3.5 presetsoverlay

As you can see, some of the preset descriptions are shown in type that is too large to fully show in the overlay.

Other settings not built into presets include:

  • Orientation
  • Which built-in microphone to use (Bottom / Front Top / Back)
  • Zoom - choosing either a slider for direct zooming, or a +/- buttons and a zoom speed control
  • Whether the Volume + button can trigger recording or not (useful for external microphones and headsets)
  • Guides - One kind of guide: Dividing the screen into thirds
  • Recording time - As well as the usual unlimited recording, set recording time for values between 5 seconds and 2 hours
  • Spy Mode - The option to blank the screen when recording
  • On-screen Audio Metering
  • Video Stabilization

A nice touch for left-handed operators is that the UI reconfigures if you hold your device up the other way.

Right-handed UI:

mp3.5 UIRight

Left-handed UI:

mp3.5 UILeft

By default, MoviePro will auto focus, auto expose and auto white balance while recording. By tapping on the screen you can set the point that the software uses for focus and exposure. Dragging from the point you've tapped allows you to have separate focus and exposure points:

mp3.5 focus-exposure-point

You can also turn on the device flash and use it as a light, use a timer delay before recording and also pause recording while filming with creating a separate QuickTime file

Instead of sending footage to the camera roll, you can keep them in the app library, which has a browser that provides useful information - and gives access to a video editor:

mp3.5 library 

3K in Final Cut Pro X

When you create a new project in Final Cut and set it to set the resolution based on the first clip added to the timeline, you get the following message:


If you switch the Format pop-up to 'Custom' Final Cut will set the project to the correct dimensions:


Bear in mind

There are a few areas where MoviePro could do with some improvement.

The first is frame rate control: Even though you might choose a specific frame rate, the frame rate recorded often isn't exactly correct: If set to record at 25 frames per second, the resulting movie is usually 25.035 fps, but sometimes 25.034 fps or 25.025 fps. The metadata in the file means that editing software like Final Cut Pro X reads the frame rate as 25 fps, but QuickTime Player 7 and Mpeg Streamclip determine that the frame rates I've listed. Here are the frame rates of other movies I've recorded: 24.024 fps (not 24), 23.029 fps (not 23), 20.025 (not 20), 120.2 fps, 200.557 fps, 239.634 fps (but sometimes exactly 240 fps).

There is a note from the developer stating that if you can do without higher resolutions and data rates, the recorded frames per second are more likely to match the setting, but that setting didn't improve the accuracy for me.

This is probably a side effect of the software framework MoviePro uses - the iPhone prioritises quality over consistency. MoviePro needs a mode that records at exactly the frame rates required. This is needed if you want your iPhone or iPad to synchronize with other devices recording at the same time - be they cameras recording other angles of moments that might only happen once. If the high frame rate section is only going to be recorded using MoviePro is less of a problem - editing software will treat the 239.634 fps footage as if it is 240 fps and when you play it at the frame rate of your project, you'll get the slow motion you want.

Frame rate accuracy is also important when performers are working to music playback for sync slow motion for music videos. 

Talking of frame rates, professional movie makers need more specific frame rates: 23.976, 29.97 and their x2 and x3 multiples. To get better results, they also need shutter speed control. Footage shot at 25 fps is usually made from stills shot with a 1/50th second shutter speed (known as a shutter angle of 180° as it results in a shutter speed of twice the frame rate). That means footage shot at 2 fps should have a shutter speed of 1/4 of of a second.

As the data rate of 3072x1728 footage can be as high as 130 Mbps, it would be be great to have that same data rate available to lower resolutions (perhaps at higher frame rates). Recording as a Photo Jpeg medium (instead of H.264) 2560x1440 QuickTime movie would result in high quality footage with enough extra resolution for reframing and stabilzation.

Being extra picky, it would be good for the UI graphics to be scaled for the iPhone 6 Plus display, as some of the graphics is a little blocky if you take a closer look.


The fact that I'm asking for precise frame rate control, shutter angle control and audio encoding settings shows how professional this application already is. This application is great value. Buy it now and it will help your iPhone become a secret weapon on your next professional shoot.

MoviePro costs £2.99 and is available from the iTunes Store.

Creating Apple Store iOS App Previews using Final Cut Pro X

Thursday, 23 October 2014

For those iOS developers who want to provide more information to potential purchasers in the iOS app store, Apple suggest using video-based 'app previews.'

Apple have provided resources for developers who want to create app previews using iMovie 10.0.6 and Final Cut Pro X 10.1.3. 

New in OS X Yosemite is the ability to record what happens on an iOS 8 device attached to your Mac. Here's an excerpt from Apple's instructions:

Capture Screen Recordings with QuickTime Player

  1. Connect your iOS device to your Mac using a Lightning cable.
  2. Open QuickTime Player.
  3. Choose File > New Movie Recording.
  4. In the window that appears, select your iOS device as the Camera and Microphone
 input source.


Once you use the Record button, perform the actions on your iOS device that demonstrate the features of the app, you save the recording on your Mac.

Final Cut Pro X app preview settings

There's a PDF of instructions for those new to Final Cut Pro on how to create new projects and which custom size to use for each app preview: 

  • iPhone 5s, iPhone 5c,
 iPod touch 5th generation: 640 x 1136 for portrait, 1136 x 640 for landscape
  • iPhone 6: 750 x 1334 for portrait, 1334 x 750 for landscape
  • iPad Air, iPad 4th generation, iPad mini with Retina display: 900 x 1200 for portrait, 1200 x 900 for landscape
  • iPhone 6 Plus 1080 x 1920 for portrait, 1920 x 1080 for landscape

App previews must be set to a frame rate of 30p.

11 free titles

As well as the short PDF guide Apple also provide a set of free title plugins (12.2MB ZIP) to provide useful information in overlays on top of screen recordings:


The ZIP includes installation instructions.

A new market?

For writer/editors, creating iOS app previews might become a marketable skill: "Sales for this app were low, but after using the services of AppPreview4D, everything changed!"

iMovie for OS X Yosemite: Final Cut Pro X for Yosemite clues

Thursday, 16 October 2014

As iMovie for OS X Mavericks is a full version of Final Cut Pro X with a consumer UI, the new version of iMovie for OS X Yosemite is relevant to those waiting for the next version of Final Cut.

iMovie for for OS X Yosemite (version 10.0.6) has a new user interface.

The old UI:


The new 10.0.6 UI:


The old adjust controls:


The new adjust controls:



10.0.6 new features

  • Updated look for OS X Yosemite
  • New file export options including Custom H.264, ProRes and Audio Only
  • Share any video frame as an image
  • Email HD video with Mail Drop when signed into iCloud
  • Select a portion of a clip in the timeline by dragging across the bottom of a clip
  • Adjustments bar is always open for easy access to audio and video tools

For developers using iMovie to create app previews on the App Store:

  • Support for iPhone and iPad screen recording videos captured with QuickTime Player
  • 11 animated titles designed to showcase apps in action
  • Share option to easily export for the App Store

Version 10.0.6 will on run on any version of OS X before OS X Yosemite.

A short Apple developer document explaining how to use iMovie to create app previews. Ripple Training also have a video which shows the process, including iMovie's 'App Preview' mode.

As iMovie 10.0.6 requires OS X Yosemite, iMovie 10.0.5 is available for those who haven't upgraded. This means both online help systems are still available:

iMovie 10.0.5 help.

iMovie 10.0.6 help.


Although there are some new features to iMovie, the majority of the changes between 10.0.5 and 10.0.6 refresh the UI for OS X Yosemite. Not all the UI has been updated however. The Import Media dialogue box hasn't been updated (apart from its title bar):


An unmentioned 10.0.6 improvement was first seen in Final Cut Pro X: the option to hide clips you've already imported.

New "App Preview" project type

Here are the icons for the 11 new animated titles designed to work for App previews:


Three have a yellow on-screen control for repositioning the title:


These new titles are implemented as Motion 5.1.1 templates. The current version of Apple Motion is 5.1.2. The other Motion titles were created using an older version of Motion.

Export options

The new version of iMovie adds the ability to export the current project or clip as a ProRes (422) mov, H.264 .mp4 or audio only file (with a choice of AAC, MP3, AIFF or WAV formats).

As you drag on the custom H.264 quality slider, whose range is between 2 and 16 Mbps for 720p footage… 


the estimated file size is updated:


A feature that would be useful in Final Cut Pro X. You can also choose to export at lower resolutions using the pop-up: Options are 1920 x 1080, 1280 x 720, 960 x 540 and 854 x 480. The custom data rate range changes based on the resolution of the export.

If you are working in an App Preview project, a new App Preview share destination appears - H.264 mp4 with AAC Audio.

If you have imported 4K footage, you can export it (or a selected range of it) at full resolution in ProRes .mov or H.264 .mp4:


Remote control apps are dead, long live remote control

The iOS 8 - OS X Yosemite combination means that Apple will discontinue specialised remote control iOS applications. To replace them full iOS equivalent applications will be able to control their OS X counterparts.

Here's how this works with Keynote. Keynote on iOS can control Keynote presentations running on nearby OS X Yosemite Macs.

You first pair your iOS device with the Mac using a preference: 


Once linked you tap the 'iOS play' icon:


The presentation doesn't have to be in slideshow mode on the Mac:


Once the iOS device finds the Keynote app running on the Mac:


As each slide comes up in the presentation on the Mac, it appears on the iOS device. As well as going to previous and next slides, the iOS device can use a range of colours to mark up slides on the Mac screen. Sketching done on the iOS device:


…appears on the Mac:


This is the kind of two-way communication that would be very useful for iMovie and Final Cut Pro X users. Up until now, most remote control iOS apps have controlled Mac applications by simulating keypresses. Now useful information could be passed from the application running on the Mac to the iOS app. For example, the Mac could be displaying a project so that it fills the screen while the iOS app shows an inspector for the current clip.

Final Cut Pro X inside iMovie 10.0.6

It looks like the Final Cut parts of iMovie were created in August. There are no obvious hints about future X features hidden in iMovie. As before, a large proportion of iMovie's almost 3GB bulk are made of frameworks used in Final Cut Pro X. 

What does this mean? That the features for iMovie 10.0.6 were frozen by August; the weeks since then were used to fix bugs in iMovie for OS X Yosemite compatibility (and perhaps bugs in Yosemite for iMovie compatibility).

Skinning iMovie 10.0.7 (i.e. Final Cut Pro X 10.2)?

Classic Apple user interface design avoids Modes - states where only some tools, menu commands and user interface elements are available and when the effects of some tools change. It is interesting that with iMovie 10.0.6 Apple have added a third mode. As well as video editing and trailer making, the App Preview project type acts as a mode - changing which titles are available and making sure the resulting movie is the correct size.

It would be interesting if Apple added more project types. Two examples 'Media Logging' project and 'Producer Feedback' project. In fact, if Apple could add types of project, they could make the application skinning/project type mechanism available to third parties. Useful if you wanted to create a 'BBC News' project type, or a 'Real Estate' project type. As iMovie is the Final Cut Pro X underpinnings with a consumer friendly skin, perhaps these custom versions of iMovie could include a few features from Final Cut. Useful for large enterprise deployments of 'iMovie Pro X.'

New patent shows a little early Apple thinking on Final Cut Pro X

Monday, 13 October 2014

Last week Apple was awarded a patent concerning how to highlight discontiguous groups of clips on a timeline.

Even though it is a new patent, it shows Apple’s thinking back when it was applied for. This patent took years to be awarded, so any feature hints found in the application document have been superseded by what Apple chose to implement in the intervening years.

Patenting concepts that apply to editing software requires a description of a sample editing user interface. Here is an example from the patent:


The imaginary sample editing application shows a combination of Final Cut Pro 7, iMovie and Final Cut Pro X. Layers from Final Cut Pro 7, iMovie's way of having content in more than one place at a time (clips would appear in 'All Files,' 'Video' and in an interview folder). The viewer/inspector/timeline layout are from Final Cut Pro X.

The parts of this illustration that interest me are the labels above the viewer and the inspector. The viewer has three control areas: 'Display Types,' 'Viewer Tools' and 'Overlays.' The inspector seems to have two tabs at the top - 'Inspector' and 'Transcript' with clip 'Specific Controls' at the bottom of the inspector.

This patent was applied for in May 2009. Interesting that Apple considered including a clip transcript panel in a clip inspector. I also hope that Apple will expand the way overlays work in the Final Cut Pro X viewer.

The patent.



BBC adoption makes Apple's Final Cut Pro X seem more 'Pro'

Thursday, 04 September 2014

Peter Wiggins of has broken a big story:

After a successful trial period BBC news cameramen/editors will be upgrading to Final Cut Pro X from FCP 7 for their news gathering field operations. A full roll-out throughout all the English regions is expected next year.


Further trials are ensuing within other divisions of the BBC and, aside from it's widespread use on The Culture Show, FCP X is about to be deployed for several other productions within the BBC including several popular daytime shows.

Interesting that two very different uses are mentioned in this story: news gathering field operations and popular daytime shows.

The first use shows that Final Cut Pro X is good for individuals with very little support while on location, but with standards-based exporting that integrated well with higher-end systems back at base. A popular news editing system at the BBC at the moment is based on Quantel iQ.

The second use shows that Final Cut works well with the kind of productions made by small production teams and medium-sized production companies. 

Following on from ITVs adoption of Adobe Creative Cloud for larger teams and dramas, this isn't a good sign for Avid and editors who only know how to use Avid Everywhere tools. It may be that the software at the core of Media Composer can't be tuned for recent Mac and PC hardware as well as Premiere and Final Cut Pro have been.

The French Final Cut Pro X website has reported that French broadcaster TF1 has also adopted Final Cut Pro X for its news department (Google's English translation).

In other news this week, Hamburg Pro Media have stopped selling their Mac OS X MXF tools. MXF is the wrapper for movie footage captured by many modern cameras and also the delivery container for submitting programmes to UK TV companies from October 1st. Hamburg Pro Media used to provide a suite of tools for UK TV production companies to be compliant with the new delivery rules (the old product page archived on the Internet Wayback Machine). Hamburg Pro Media's AS-11 Suite Workflow Guide.

Next week is IBC 2014, the main European trade fair for the TV production industry. There's a good chance these stories will influence some of the conversations next week in Amsterdam.

Read the story and stay tuned to find out more!


2010 Apple patent: Final Cut Pro X concepts

Saturday, 30 August 2014

A patent filed by Apple in 2010 shows a possible future direction for iMovie that includes ideas that have appeared in Final Cut Pro X. More evidence of the large amount of research and development Apple put into editing user interfaces.

I've written before about Apple's patent concerning wider story structure as well as timeline structure. This week saw Apple being awarded a patent that seems to have arisen out of making editing easier for a wider range of people. A step on the way to general video literacy.

US Patent 8,819,557 is for "Media-editing application with a free-form space for organizing or compositing media clips." It follows on from the way older editing applications gave space in icon-based bins for editors to play with clip order. In Final Cut Pro 7, Adobe Premiere and Media Composer bins can show clips as icons that can be arranged in any way prior to being added to a timeline. 

This Apple patent turns icon-view bins into spaces where editors can combine clips together into timelines, as well as perform many other operations - including assigning keywords, defining selected ranges, skimming, trimming sequences and trimming edits and more.




The patent includes a storyboard that shows an element of dyamic trimming. Here is an excerpt from the text:

During playback, a playhead moves along the media clips in the sequence. Before the playhead reaches the end of the media clip, the user can invoke a command that will cause the media clip to continue playing content from its source file after the current out-point is reached. When the playhead reaches a location in the media clip source at which the user wants to set a new out-point for the media clip, the user can invoke a command that will cause the frame at that location to be set as the new out-point for the media clip.

As well as the full text of the patent, you can view the whole 119 page patent - including many UI storyboards in this 13MB PDF. The easiset way of reading the patent is to have the text in one window with the PDF in an another.



look at this site methodology of case study