Some of you may have experienced the beachball of death when FCPX tries to load a project and eventually resorted to force-quitting the app.

In most cases, the app hasn't hung at all but is just taking a really long time to open the project. If you leave it long enough (8-12 hours) it should eventually open. We recommend running our Project Repair tool to optimize the project file before doing this, as the optimization process lowers the file size and can shave off some loading time.
The reason it is taking so long is that the project has become too complex. A common cause of this is over-use of compound clips, especially compound clips inside multiclips. I have seen this lead to multi-gigabyte project files, even though the timeline was only a few minutes long.
Once the project opens successfully, begin the process of removing the compound clips. FCPX will hang for a short while whenever you try to do anything, but as you reduce the number of compound clips it will become more and more responsive.
Posted by Jon Chappell on Monday January 21 2013 12:17 PM to Video Editing, Final Cut Studio, Tutorials
0 comments
Posted Permalink
Sometimes you need to swap out an audio track if there's a problem or you need to provide multiple languages or different soundtracks.
Instead of compressing the video again, QT Edit makes it really easy to do this in just a few steps.
1. Open up the movie file in QT Edit.

2. Select the existing audio track and press the - button to delete it.
3. Click the + button and select Audio. Browse for the new audio, which can be an AIFF, WAV or another movie file.

Important: QT Edit inserts the track at the current playhead position so make sure the playhead is at the beginning. If you make a mistake, manually set the start point of the new track to 00:00:00:00.
4. Double-check sync in the preview window and then hit Save.
5. You will be asked if you want to flatten the movie. This makes the movie self-contained. In most cases you will want to flatten, but if you want to create a reference movie select Don't Flatten.

QT Edit is just one of many useful utilities in the Pro Media Tools suite. To find out more, check out the feature list, watch the overview video, read the user manual or download the 15-day trial.
Posted by Jon Chappell on Tuesday December 4 2012 2:11 PM to Utilities, QuickTime, Tutorials
0 comments
Posted Permalink
This past weekend I used Adobe Encore for the first time to create a Blu-ray for an important screening. I'd previously tested the workflow and everything had worked well, but this was my first time using it on a project.
I initially had some issues encoding the Premiere Pro sequence to H.264 because Adobe Media Encoder told me it would take 42 hours, and after leaving it for a few hours it seemed to be making good on that promise. I eventually narrowed the problem down to a corrupt Dynamic Link cache which I trashed with CS Repair and got the more respectable prediction of 10 hours (it was a 90 minute feature with 10-bit RGB source files).

I checked the original source files and they were fine. I checked the AC3 and it was fine. I restarted Encore and the problem was still there. I cleared the media cache from within the preferences menu; no change. I thought it might just be the preview but the problem existed on a test disc that I burned.
I eventually traced it to project corruption. There is a file in your project directory called ProjectMedia.acx. This is what the end of the file looked like:

The file should end with the closing XML tag </EncoreProject> (and there should only be one) but extra data has been added at the end. To fix this, close Encore, open up the file in TextEdit and delete everything beyond the first </EncoreProject> tag.
Then trash your media cache. For some reason the button in preferences doesn't remove everything so I'd recommend removing all files from the media cache directories at ~/Library/Application Support/Adobe/Common or by using Housekeeper.
I relaunched Encore, everything worked properly and I was able to create the disc and breathe a sigh of relief. I would definitely recommend keeping an eye on ProjectMedia.acx though because I just checked it again and more corruption has crept in.
Posted by Jon Chappell on Thursday October 25 2012 12:40 PM to DVD, Adobe, Tutorials
1 comment
Posted Permalink
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 Thursday September 27 2012 11:32 AM to Apple, Final Cut Studio, Tutorials
1 comment
Posted Permalink
Avid Media Composer traditionally required all media files to be converted to its DNxHD Op-Atom MXF format but recent versions have allowed you to skip this process and import tapeless media instantly. This feature is called Avid Media Access (AMA). Media Composer ships with very few AMA plugins so to support additional camera formats you may need to download and install extra AMA plugins.
Using AMA is not without its pitfalls so here are some ways of reducing problems.



Posted by Jon Chappell on Tuesday August 28 2012 4:17 PM to Video Editing, Avid, Tutorials
0 comments
Posted Permalink
Dynamic Link is a key selling point of the Adobe suite that many people rely on for their workflows. Here's what to do if it doesn't work as expected. This article is mainly aimed to dynamic linking between After Effects and Premiere but many of the suggestions will apply to the other applications in the suite.



Posted by Jon Chappell on Monday August 20 2012 10:54 AM to Video Editing, Adobe, Tutorials
2 comments
Posted Permalink
Preference Manager is a useful tool for trashing preferences for a range of video editing applications including Avid, Premiere and all versions of Final Cut Pro. This wipes the user settings for your editing application and can fix a wide range of problems.
However, having to set everything up again can be a chore. With a little bit of preparation in advance, you can ensure you never have to trash them again.
1. Start with a stable foundation. We recommend trashing preferences in Preference Manager and then setting them up again from scratch in your NLE, but you can skip this step if you are confident that your settings are stable.

2. Backup the settings. You can choose to backup additional items such as keyboard layouts if you desire.

3. Optionally, lock your preference files to prevent them from becoming corrupt. Some apps don't work correctly with locked preference files, so for these apps the lock option will be greyed out.

4. When a problem occurs, instead of trashing preferences, restore the backup. This will restore the settings you backed up previously to enable you to get back to work quickly.

Additional tips:
Preference Manager is a free and useful tool for editors and post production professionals. See the user manual for more workflow tips.
Posted by Jon Chappell on Monday August 13 2012 1:41 PM to Video Editing, Utilities, Tutorials
0 comments
Posted Permalink
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.
Works on: 10.7+
Works on: 10.7+

Works on: 10.7+
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+

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+

Works on: 10.8+
Works on: 10.8+
Here is a tip for removing the icon completely but you should do it at your own risk.
Works on: 10.8+
Works on: 10.8+
Posted by Jon Chappell on Monday August 6 2012 1:47 PM to Apple, Software, Tutorials
4 comments
Posted Permalink
If you run Avid Media Composer 6 on Lion you may have experienced an issue where a process called hasplmd crashes literally every 10 seconds. This fills up your Console logs very quickly and causes the crash reporter to be constantly running and writing to the hard drive.
Here's a an example of my Console log (abridged):
7/15/12 8:18:10.906 PM ReportCrash: Saved crash report for hasplmd[70958] version ??? (???) to /Library/Logs/DiagnosticReports/hasplmd_2012-07-15-201810_localhost.crash
7/15/12 8:18:21.040 PM ReportCrash: Saved crash report for hasplmd[70968] version ??? (???) to /Library/Logs/DiagnosticReports/hasplmd_2012-07-15-201821_localhost.crash
7/15/12 8:18:31.208 PM ReportCrash: Saved crash report for hasplmd[70969] version ??? (???) to /Library/Logs/DiagnosticReports/hasplmd_2012-07-15-201831_localhost.crash
7/15/12 8:18:41.378 PM ReportCrash: Saved crash report for hasplmd[70974] version ??? (???) to /Library/Logs/DiagnosticReports/hasplmd_2012-07-15-201841_localhost.crash
7/15/12 8:18:51.620 PM ReportCrash: Saved crash report for hasplmd[70986] version ??? (???) to /Library/Logs/DiagnosticReports/hasplmd_2012-07-15-201851_localhost.crash
hasplmd is used for dongle verification, although it took me a while to notice because I use Avid with a dongle and it worked just fine in spite of the crashes.
To fix this, download the newer 6.23 version of the drivers here (I chose the GUI version).
Alternatively, to disable hasplmd completely, type the following command in the Terminal:
sudo launchctl unload -w /Library/LaunchDaemons/com.aladdin.hasplmd.plist
You'll need to type your password after doing this.
Posted by Jon Chappell on Monday July 16 2012 11:05 AM to Software, Avid, Tutorials
0 comments
Posted Permalink
I had this question asked to me the other day so I thought I'd write a quick article on it. You may have noticed that Compressor does not create H.264 files with timecode tracks when using the Apple Devices presets.
The reason for this is that MP4 and M4V files do not support timecode. However, the MP4 specification is based on the QuickTime file format so it's easy to create a QuickTime movie (.mov) instead of an MP4 and the file will still be recognized by iOS devices and the Apple TV.

To do this, simply add an Apple Devices preset to a file and then change the file extension to mov in the Encoder tab of the Settings window. Compressor will then create an iOS and Apple TV-compatible H.264 with a timecode track.
Posted by Jon Chappell on Monday July 9 2012 12:43 PM to Final Cut Studio, QuickTime, Tutorials
0 comments
Posted Permalink
| Older posts |