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.
Apple is no longer fixing OS X bugs and some browser manufacturers no longer offer 10.6 support, leaving your system vulnerable.
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.
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.
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.
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.
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.
Final Cut Pro 10.1 includes some major changes to the inner workings of the app, including the addition of libraries for managing projects and events.
The locations of your libraries are stored in the preference files, so after trashing preferences with Preference Manager you may not see any projects or events after relaunching FCPX. This will also occur after using other tools that rely on Preference Manager such as QuickFix.
To get them back, go to File > Open Library > Other > Locate in FCPX and browse for the library files on disk.
Our recommended workflow for all applications is not to trash preferences, but to instead preemptively backup the preferences when they are stable and then restore the backup when things go wrong.
Here's another installment of bugs in your NLE you should know about.
Contiguous clips in an EDL will be imported without cuts (Avid has this behavior too but FCP 7 doesn't)
Media files corrupted by "Write XMP ID to Files on Import" feature (I always switch this off - it's damaged too many files to risk it)
It's common nowadays for videos to be processed through one or more applications prior to editorial. Unfortunately that can result in camera metadata being stripped from the processed files. This can cause lots of problems later on if you need to relink back to the original files for grading.
QT Edit solves this by letting you import metadata from another QuickTime movie. Here's how to do it:
1. Open up the destination movie.
2. Go to File > Import > Metadata. Browse for the camera original source file.
3. Select the metadata items you'd like to import or just import all metadata from the source file.
4. Save the destination file.
Being able to choose the metadata that is imported allows you to copy metadata fields between files even if the source file isn't the camera original version. Metadata can be added, removed or edited after import.
Pro Media Tools helps studios, production companies and freelancers alike forge new workflows every day. To find out more view the feature list, read the user manual, watch the overview video or download the free trial.
Does your editing application crash when you scrub to a particular point in the timeline? Does it crash or fail at the same point each time you export or render? It's likely that you have a corrupt clip or render file in your timeline.
Corrupt render files are easy to resolve. Most NLEs offer a way to clear out render files, so it's best to try this first to see if it fixes the problem.
If that fails, you'll need to figure out the exact clip that is corrupt. The manual method is to divide and conquer - split the timeline in half, then half again, and so on until you narrow down the offending clip. This can be very time consuming so an easier way is to use Corrupt Clip Finder to scan the project and test each file it finds.
It will scan the project files from most NLEs (FCP 7, FCPX, Adobe Premiere and other apps) but you can scan an entire media directory for applications not supported. In fact, for large projects it can be quicker to scan the media directory than the project file.
Not every file it flags up will be corrupt, as it will also flag up files that could potentially cause problems, such as CMYK image files or video larger than 4K in FCP 7. You can see the reason it flagged up a file by hovering over the filename in the list.
Once the files are identified, you can choose to quarantine them by moving them to another folder, delete them or attempt a repair. You can also color code them in Finder, which can be useful for highlighting files that appear to work fine but may potentially cause an issue for future reference.
Here's another installment of critical, useful or bizarre bugs in your NLE that you should know about.
Multicam edits switch angles when relaunching a project in Premiere CC (probably best to do multicam edits in CS6 for now)
Update 7-1-13: Adobe has posted a candid response to the multicam bugs.
After a bit of a hiatus, Bugs of the Week is back again.
Like any major software update, Premiere Pro CC has several new and exciting bugs.
Audio waveform sync doesn't work with one camera angle and multiple audio files. Here's a workaround.
Premiere CC no longer creates a new sequence with a new project (this is probably a good thing but it's causing some confusion)
Media Composer 6.0.4 released. Among the usual bug fixes, it also includes a new XML export option for markers.
Apple finally fixed a bug we reported a year ago that prevented certain apps from opening QuickTime movies that did not have a chapter marker on the first frame. We've been working around it but it is now fixed in OS X 10.8.4 so we recommend updating.
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.
Another installment of our weekly list of serious, useful and unusual bugs in your NLE.
Here's another installment of our weekly list of critical, useful and bizarre bugs in your editing system.