Maintain, optimize and troubleshoot your NLE
Professional cloud workflow platform
Simplified media management

7 reasons to upgrade from Snow Leopard

Today Adobe announced it's dropping support for Mac OS X 10.6 Snow Leopard. While Adobe says it only affects a small number of customers, there is still a sizable number of users running the older OS, with some surveys suggesting as much as 19% usage.

Here are 7 reasons why you should upgrade from Snow Leopard to a newer version of OS X.

It's less secure

Apple is no longer fixing OS X bugs and some browser manufacturers no longer offer 10.6 support, leaving your system vulnerable.

Many new applications won't work with it

Not just Adobe, many other apps no longer support 10.6, including all Apple and Avid applications and many hardware products and cameras. Some upcoming new products from us will require newer OS versions to take advantage of more recent technologies.

It's slower

With every new OS release there is normally a speed boost from more efficient code execution, as well as new performance-enhancing technologies like AV Foundation, timer coalescing and compressed memory.

You're missing out on new features / technologies

Useful new technologies for pro users since 10.6 include AV Foundation, compressed memory, tabbed Finder windows, file tags, Airdrop, Notification Center and Airplay Mirroring. This is in addition to the aforementioned performance-enhancing technologies.

Developers are making sacrifices for older OSes

While we don't shy away from embracing features from newer OSes if they have a clear benefit to users, maintaining two codebases for a small subset of users is complex and takes time away from feature development.

Upgrades are cheap

10.9 is free and 10.8 is $20 on the Apple Store.

You can make it look and behave exactly like Snow Leopard

Lion introduced several controversial features like reverse scrolling and an inability to Save As. Luckily some of those decisions were reversed in later versions and others are completely customizable. We have a guide to making newer versions behave more like Snow Leopard here.

Posted by Jon Chappell on Mar 6 2014 to Analysis, Apple, Software
Permalink

Apple limits availability of non-Retina MacBook Pros

Today Apple aimed to reaffirm their commitment to professional users with more details on the new Mac Pro. While some have correctly pointed out that the starting price for the new version is higher than the old model, this seems entirely reasonable to me given the significant leap in specifications. I was also relieved that it is reasonably upgradeable, minus the graphics card, although Mac users have never had a wide variety of cards to choose from anyway.

However, at the same time Apple took away some professional options. The Retina MacBook Pro was updated with more screen size options and improved specifications, however it has almost entirely replaced the older non-Retina model.

There are very specific reasons why some pros would choose a non-Retina model: matte display, greater availability of ports and upgradeable interior. The only option Apple is offering is a 13" version, which seems strange because I would have assumed that the type of user who chooses the non-Retina model would aim for the largest screen size possible. This would suggest that Apple is not aiming this laptop at spec-sensitive professionals at all, but instead users who are looking for a cheap option. However, it's only slightly cheaper than the 13" Retina so I'm really not sure what their target market is (if you can figure it out, let me know in the comments).

My 2011 MacBook Pro recently got destroyed so I was in the market for a new one. I considered a Retina laptop but in the end I opted for a 15" non-Retina MacBook Pro that was barely faster than my 2011 model. I could grudgingly cope with the glossy display and reduced ports but the lack of upgradeability was the deal-breaker for me. While it is good that Apple has reduced the prices of the Retina model, you'd be a fool not to max it out at the time of purchase. As I've said before on this blog, Apple is charging a premium price for a throwaway computer and they really need to factor that into the initial selling price.

Posted by Jon Chappell on Oct 22 2013 to Apple, Analysis, Hardware
Permalink

My thoughts on the new Mac Pro

Apple just gave us a sneak peek at the new redesigned Mac Pro.

Pros
* It's not dead!
* It finally has Thunderbolt and a significant spec bump
* Dual GPUs
* The Thunderbolt ports are not all running on the same bus
* It's significantly smaller and lighter

Cons
* No space for internal PCI cards - all expansion is through Thunderbolt
* The hard drive is not user-replaceable
* It will definitely not fit in a rack
* AMD cards will not run CUDA-optimized apps like Resolve well

Unknowns
* Price
* Is the RAM replaceable or soldered to the motherboard?

The cons are not cons for everyone and it seemed like my Twitter feed was split down the middle. It looks like Apple has focused on FCPX as the target application but not really paid much heed to other pro apps people might want to use. I think this is a sign that people at the very high end of the industry may want to look elsewhere for their pro computers, whether that is a Hackintosh or a Windows box.

A big problem with lack of internal upgradeability is downtime. If the hard drive dies in a regular Mac Pro, it is not difficult to replace it, and you can be up and running again in minutes if you were smart enough to clone the drive beforehand. The problem with the new Mac Pro is that every issue is potentially a visit to the Apple Store, which could take a day or more for them to fix (not to mention the added cost if you're out of warranty). So it is probably best for facilities to have multiple spare Mac Pros that they can swap out easily.

Which brings me onto my next point - how much is it? Apple didn't say. But assuming everything is soldered to the motherboard and the case can't be opened, the Mac Pro will essentially be a disposable computer that you should not expect to last for as long as your current Mac Pro. A disposable computer should be sold for a disposable price, so I expect the success of the new Mac Pro to entirely hinge on the pricing, especially as comparably-specced Windows computers can be purchased for less.

What that means is that right now we don't really know if the new Mac Pro is worthwhile until we get more details, but it's clear that Apple has put its cards on the table and very much hedged against making a computer that will meet everyone's needs in our diverse industry.

Update: Apple has posted more details on their site and it looks like both hard drive and memory are upgradeable. This is great and makes me feel much better about the machine but I still think it will depend on pricing.

Update 2: Blackmagic says work is underway to support the Mac Pro in Resolve and Adobe says the upcoming Premiere Pro CC should support it out of the box.

Posted by Jon Chappell on Jun 10 2013 to Analysis, Apple, Hardware
Permalink

5 things Apple should change in OS X 10.9

OS X is a mature operating system so it's probably largely meeting most people's needs already, however here's a list of five things we'd like to see in OS X 10.9.

1. AV Foundation improvements

The QuickTime API is horrible and I'd love to ditch it completely, but AV Foundation has some catching up to do before that can happen.

It needs support for third-party codecs like DNxHD, support for reference movies and the ability to update a file in-place (like QT Edit does) without having to re-encode the entire movie just to make a small modification.

2. Native support for containers other than QuickTime

It'd be great if OS X could natively deal with MXFs, AVIs, MKVs, etc as if they were QuickTime movies.

3. Encrypted folders

Ability to encrypt and password protect a single folder on your hard disk, instead of the entire drive or the entire home folder.

4. Finder improvements

It looks like Apple may already be bringing tabs to Finder (great) but we'd also like to see an editable location bar like Windows has, bring back Cmd-clicking on the title bar to open another folder in a new window, and a solution to the scroll bar temporarily obscuring the last item in a list.

5. Second screen support

An API for low-latency visual output to an iOS device would be great for status windows, scopes, etc.

Things Apple definitely shouldn't change:

1. Don't kill QuickTime yet.

2. Don't make it so we can't run 32-bit apps anymore.

3. Don't force all apps to be sandboxed.

4. Allow untrusted apps to run if the user desires.

Posted by Jon Chappell on Jun 5 2013 to Analysis, Apple, Software
Permalink

How to import projects and events into Final Cut Pro X

Need to restore a backup or import a project from another system into FCPX? It's not as simple as it seems at first glance. You would think that you could just double-click the project file but that produces the following error:

Final Cut Pro X is expecting projects to be contained in a folder inside your Final Cut Projects directory (or Final Cut Events if you are importing an event). The default locations of these folders are in ~/Movies.

To successfully import these files, you must create a new directory inside your Final Cut Projects or Final Cut Events folder and then copy the project to this new directory. FCPX will determine the project name from the name of the directory but the project file does not need to have the same name.

It's also worth noting that there is a difference between double-clicking an XML file and importing it via File > Import > XML.

Double-clicking seems to import the file without modifying it, so you will get errors if a project already exists with this ID or the event is not in the exact location as specified in the XML file. However, if you import it via File > Import > XML, it is more intelligent and will assign a new ID if necessary and find the new location of the event if it has changed.

Posted by Jon Chappell on Sep 27 2012 to Apple, Final Cut Studio, Tutorials
Permalink

Making Lion and Mountain Lion more like Snow Leopard

Until recently, most of our users were still using Snow Leopard. Then suddenly a massive switch occurred and a majority upgraded to Lion. This may have been because applications like Adobe Premiere and Avid Media Composer now require Lion or it may have been because the MobileMe shutdown forced people onto iCloud.

Whatever the reason, here are some tips for making 10.7 or 10.8 more welcoming for a 10.6 user.

Reverse scrolling

In Lion, Apple inverted the scroll direction so that up scrolls down and down scrolls up. Some people prefer this but you can switch it off by going to the Trackpad preference pane and deselecting Scroll direction: natural in the Scroll and Zoom tab.

Works on: 10.7+

Show Finder status bar

By default, the Finder's status bar at the bottom is hidden. To switch it back on, go to View > Show Status Bar.

Works on: 10.7+

Show scroll bars

By default, scroll bars appear briefly in Lion and then disappear. This can be annoying because they briefly obscure the bottom file in a Finder window when in List mode. To make scroll bars always appear, go to the General preference pane and change Show scroll bars to Always.

Works on: 10.7+

Hide All My Files

In Lion every Finder window opens into a section called All My Files, which shows every file in your user directory in one place. I much preferred the old way of showing the Home folder, so you can hide All My Files by going to Finder preferences and then deselecting All My Files in the Sidebar tab.

You can also set it to default to the home folder by going to the General tab and choosing your home folder in the "New Finder windows show" popup.

You may also like to show your hard drives and DVDs on the Desktop, which can be set from the General tab.

Works on: 10.7+

Stop restoring windows

Lion restores your previous windows when you restart an application. Apple provides an option in the General preference pane that allows you to deselect Restore windows when quitting and re-opening apps. In Mountain Lion the option is called Close windows when quitting an application and should be ticked.

However, in practice, these options have never worked reliably for me and applications will often try to restore old windows regardless. I therefore close windows manually before quitting an application and this fixes the problem.

Works on: 10.7+

Restore classic Expose grouping

Mountain Lion provides a new option in the Mission Control preference pane called Group windows by application. Deselecting this restores the 10.5 and 10.6 behavior of showing every window on the screen, regardless of which application it belonged to.

Works on: 10.8+

Dictation

Dictation is activated by pressing the Fn (function) key twice. Everything you say is sent to Apple's servers so businesses may wish to steer clear of this feature. To switch it off, go to the Dictation & Speech preference pane and set the radio button to Off.

Works on: 10.8+

Notification Center

Mountain Lion includes a new iOS-style Notification Center. To switch it off for 24 hours, Option-click the icon in the far right of the menu bar.

Here is a tip for removing the icon completely but you should do it at your own risk.

Works on: 10.8+

Turn off autosave

Mountain Lion provides a new option in the General preference pane called Ask to keep changes when closing documents. This essentially turns off the autosave feature added in Lion.

Works on: 10.8+

Posted by Jon Chappell on Aug 6 2012 to Tutorials, Apple, Software
Permalink

Thoughts on Final Cut Pro X 10.0.3

Today Apple released Final Cut Pro X 10.0.3 which offers several new features such as multicam and broadcast monitoring (beta) that were previously missing.

Looking through the details, it's hard to find anything that would appeal to consumers and it is clear that this is an attempt by Apple to appease at least some of the pros. My first reaction (and the reaction of a lot of people on Twitter) was that this was the version Apple should have released back in June.

Here are some of the features I found interesting:

  • Multicam - 64 angles are supported and lots of options for syncing, including PluralEyes-style analysis of the audio waveforms. In comparison, Adobe Premiere Pro supports 4 angles and Final Cut Pro 7 supports 128.
  • Media Relink - You can now reconnect to files, which is useful if you need to swap out VFX shots or FCPX for some reason loses the link. This really should have been a 1.0 feature.
  • XML 1.1 - As mentioned earlier on this blog, the previous version of FCPXML didn't support audio levels so you'd lose your levels if you transferred the project elsewhere. This is now supported in FCPXML 1.1, although it's worth noting that Apple's developer documentation still says XML is not a perfect copy and does not contain everything that a project file does.
  • Broadcast monitoring - Apple's description is vague about which devices are supported but today AJA released new drivers that support FCPX output from SDI. There is no word yet from Black Magic Design or Matrox but I would assume new drivers are coming soon. It's worth noting that broadcast monitoring is only supported on Lion.

That doesn't make it a perfect tool for the professional broadcast / film industries of course. I really can't see EDL support ever being added, nor support for broadcast tape capture. But over time I think this will matter less and less. Case in point: I'm working on a feature right now and was very surprised when the post house asked me to deliver the Final Cut Pro 7 project for grading / mixing instead of EDLs and OMF.

I think Apple is very much gambling on the future here and I am definitely considering looking into it for short form work.

Update: Larry Jordan offers more info on the differences between FCP7 and FCPX's multicam implementation. Thanks Larry!

FCP 7 would LINK up to 128 cameras in a multicam clip, however you could only view 16 of them. FCP X links and allows you to view up to 64 clips at once, by switching between up to four banks of 16 cameras each. Also, edits can be made in real-time or by positioning the playhead.
Posted by Jon Chappell on Jan 31 2012 to Apple, Final Cut Studio, Analysis
Permalink

Critical problems with QuickTime 7.7 and QuickTime 7.6.6 build 1787

There are widespread reports of problems with the latest version of QuickTime (QuickTime 7.7 on Leopard and QuickTime 7.6.6 build 1787 on Snow Leopard and Lion). This update is installed as part of Security Update 2011-006 for Snow Leopard and OS X 10.7.2 for Lion.

(The security update is the most likely culprit but it may alternatively have been caused by the iTunes 10.5 update that was released at the same time.)

The problems include:

Unable to play certain movies


Several people have been getting the message "An invalid public movie atom was found in the movie" when playing back in QuickTime Player. Final Cut Pro will either crash or display a white screen.

This seems to especially affect HDV files created by Focus Enhancements storage products. Focus has acknowledged the issue here (PDF).

The recommended solution is to downgrade QuickTime or restore an earlier version of your system from a backup or clone.

Update 2011-11-09:
Matt Geller of Meta Media Creative came up with another way of solving the problem. Replace the following files with the versions from a computer without Security Update 2011-006 installed (or alternatively extract them using Pacifist):

/System/Library/QuickTime/ApplePixletVideo.component
/System/Library/QuickTime/AppleVAH264HW.component
/System/Library/QuickTime/QuickTime3GPP.component
/System/Library/QuickTime/QuickTimeComponents.component
/System/Library/QuickTime/QuickTimeFireWireDV.component
/System/Library/QuickTime/QuickTimeH264.component
/System/Library/QuickTime/QuickTimeIIDCDigitizer.component
/System/Library/QuickTime/QuickTimeImporters.component
/System/Library/QuickTime/QuickTimeMPEG.component
/System/Library/QuickTime/QuickTimeMPEG4.component
/System/Library/QuickTime/QuickTimeStreaming.component
/System/Library/QuickTime/QuickTimeVR.component

Reboot your computer and the problem should be solved. Remember to make a backup of the files you replace, just in case.

Related forum threads:
Apple Discussions: Invalid public movie atom was found in movie
Apple Discussions: Help!!! Upgrading to iTunes 10.5 has destroyed all video in Final Cut Pro
Apple Discussions: Problems after QuickTime 7.7 update
DV Info: Public atom?
LAFCPUG: Invalid public movie atom was found in movie

QuickTime-based applications crashing at startup


Some people have had problems with Compressor, Cinema Tools, Final Cut Pro and QuickTime Player crashing at startup.

The crash log says:

Dyld Error Message:
Symbol not found: _ValidateAudioChannelLayout
Referenced from: /Library/QuickTime/QuickTimeComponents.component/Contents/MacOS/QuickTimeComponents
Expected in: /System/Library/Frameworks/QuickTime.framework/Versions/A/QuickTime

To fix this, copy /System/Library/QuickTime/QuickTimeComponents.component to ~/Library/QuickTime, overwriting the existing file in that location. Backup the file before you do this.

If you are using Lion, your user Library directory will be hidden by default. Use System Toolkit to make it visible.

Related forum threads:
Apple Discussions: Compressor 4 crashes at startup
Apple Discussions: QuickTime crash on Lion
Apple Discussions: Quicktime 7.6.6 (Pro) quits on launch when in Lion

Because of these issues, I would recommend steering clear of the latest security and iTunes updates on your editing machine, especially if you're using Focus Enhancements products. Anyone with this issue should notify Apple so they understand how widespread the problem is.

Posted by Jon Chappell on Nov 7 2011 to Apple, QuickTime, Software
Permalink

A quick note on the Final Cut Pro X XML format

Apple released a Final Cut Pro X update today which added several much-needed features, one of which was XML import and export. I've seen a lot of confusion on Twitter so I'm going to clarify some terminology.

XML is a format for ordering data within a file. XMEML is a subset that Final Cut Pro 7 and below uses for creating a plain-text version of a Final Cut Pro project or sequence that other applications can read. The data is ordered in much the same way as it is within the project file, with the browser contents at the top, followed by the sequences, tracks and the media within.

FCPXML is the new subset for Final Cut Pro X. It is organized in the way FCPX organizes its data internally, which is completely different from the Final Cut Pro 7 way. You have resources at the top (all files and generators within the project) followed by a single sequence with the storylines and clips inside. There are no tracks and each clip is organized into a parent-child relationship rather than chronological order. Timing information such as in and out points are expressed in time units rather than frame units.

So the two formats are completely different and there is no way to directly import FCP 7 XMEML into Final Cut Pro X or vice versa. Apple seems to be leaving this up to third-parties. DaVinci Resolve supports FCPXML and XMEML so it may be possible to convert one to the other (I haven't tested this). Some features will not translate back and forth because they don't exist in the other application.

Currently XML in and out exists only as a menu command. There is no way for applications to automatically communicate with FCPX at this time. Update: Apple just confirmed you can programatically send an XML file to FCPX but there is no way of receiving XML data yet. It is also not possible to update an existing project - importing or sending an XML file will create new projects and events.

Also note that for some reason, you can't export project-based XML when the project is loaded. You have to go back to the Project Library, select the project name and then export the XML.

As you may know, lack of XML in and out prevented us from granting feature parity with Final Cut Pro 7 users in Pro Media Tools and our other products. We're going to begin integrating support in stages, so expect updates very soon.

Update: It would appear that the XML export function in its current implementation doesn't preserve important information, which is a problem when roundtripping. We still aim to support it in our applications and hopefully these issues will be addressed by Apple very soon.

Posted by Jon Chappell on Sep 20 2011 to Apple, DR News, Final Cut Studio
Permalink

5 great Lion features for editors

Mac OS X 10.7 Lion was released earlier today. I've heard a couple of people say they're not enthusiastic about it and, with features like Autosave and Launchpad, it's mainly geared at consumers. I completely disagree and here's my list of five features that are great for editors and video professionals (in no particular order).

AirDrop

Even in the 21st century, many people I know still use good old Sneakernet to distribute files between computers. People still use such a low-tech method of transferring files because the machines don't need to be networked to each other, there's no setup process and you're not opening yourself up to potential security issues (assuming the files and the drive are virus-free, of course).

AirDrop allows you to send files to people physically located nearby who are not necessarily on the same Wi-Fi network. When you want to send a file to someone, both of you click the AirDrop icon in the Finder sidebar and you then drag the file onto the person's name. If they accept the file, it is encrypted and sent directly to their Downloads folder.

You only appear to other users on the network if you have the AirDrop folder open. This provides greater privacy and security than having regular file sharing running constantly.

Lion Server and Xsan

Every Mac now has the potential to be a server for just $50, giving you a great deal of control over your system and the users that access it.

Lion now includes Xsan, a network file system popular with video editors. This used to cost $999 so it's a huge saving for large installations.

AV Foundation

Love it or loathe it, you can't deny that Final Cut Pro X is built on a great technical foundation. AV Foundation ships with Lion and allows developers to utilize the same technology in their applications. It's something we plan to explore to improve future versions of Pro Media Tools.

It's also worth noting that the QuickTime 7 API is still there so existing QuickTime applications will continue to work. Final Cut Pro 7 runs just fine in Lion.

Merging folders

This feature has been part of Windows for decades and I'm surprised it's taken this long to make it to the Mac. If you drag a folder onto another folder with the same name, it now gives you the option to merge the two together. This is a huge timesaver.

Versions

We're big fans of incremental backups, which is why we created FCP Versioner. It's great to see something similar included in the OS for applications that support it.

Other nice features include the ability to encrypt an entire drive without a perceptible performance drop (according to Apple's marketing), OpenGL 3.2, Resume and Time Machine local snapshots, for recovering files when you're on the road without your Time Capsule or backup drive.

Lion seems faster too - I've seen noticeable performance improvements in all of our applications when run under Lion.

Of course, there are downsides too. Firstly, it's only available from the Mac App Store. If you are running OS X 10.5 Leopard, you will need to first upgrade to 10.6 Snow Leopard in order to access the store and download Lion. Apple will be selling Lion USB keys for $69 in August for users on Leopard or without broadband internet access.

Secondly, Rosetta is dead. This means that applications built for PowerPC computers will not work on Lion, including the Final Cut Studio 2 installer.

Thirdly, for some reason Apple decided to invert scrolling in Lion, meaning that dragging two fingers down scrolls up and vice versa. This would work well on a touchscreen but feels unnatural with a scroll mouse or trackpad. Fortunately it can be disabled in System Preferences but I don't know why Apple decided to make this the default.

Fourthly, features that some professionals have been demanding for a while, such as OpenGL 4.1, 10-bit monitor support and Blu-ray playback via third party drives still haven't materialized.

Overall, I think Lion is a step forward for professionals that provides much-needed additions to OS X. Driver and application support will likely take a while to catch up, despite the beta period, so as a rule I wouldn't recommend using it for professional use until the .3 or .4 update ships, even though I've actually found it to be quite stable in my testing.

Posted by Jon Chappell on Jul 20 2011 to Apple, Software, Analysis
Permalink