Avid AMA Best Practices

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.

• The first thing to determine is if AMA is a viable workflow for your project. It's useful for short projects with a fast turnaround but Avid can get bogged down with longer and more complex sequences, especially where multicam is involved. AMA can be very useful at importing additional metadata so a common workflow is to mount the AMA volume or link to the AMA files and then transcode.

• It is recommended that you copy the camera media to another drive before importing. When doing so, make sure to keep the same folder structure and filenames as the original card or Avid may be unable to locate the media files or associated metadata. Auto Transfer is a useful tool for achieving this.

• Some AMA plugins may use the same file types, which can cause a conflict if Media Composer doesn't know which plugin to use for a particular file. For example, the ARRI Alexa MXF plugin can conflict with the Avid MXF plugin. When linking to AMA files it is therefore important to specify the exact plugin in the Enable dropdown of the Link to AMA File(s) dialog.
  

• Remember to unmount AMA volumes in Media Composer before unmounting them in the operating system.

• AMA uses the Source field to identify the files. Beware of third-party applications that use the Tape Name field instead as they will not be able to relink in Media Composer 5.5 and below. A common workaround is to export an EDL of your sequence and then reimport it and relink. If you are using MC 6, be sure to select Allow relinking between tape and file based media in the Relink dialog.
  

• If you change the tape name or other metadata after transcoding / consolidating, you may be unable to reconnect to the AMA linked clips. Either don't modify the tape name or modify it before transcoding / consolidating.

• Using AMA will limit your options when exporting. If you want to export an AAF you will need to transcode to DNxHD. To do this, right-click on your sequence and select Transcode / Consolidate, select the desired DNxHD flavor and tick Create New Sequence. You will now be able to AAF export the new sequence.
  

Posted by Jon Chappell on Tuesday August 28 2012 4:17 PM to Video Editing, Avid, Tutorials
0 comments Posted Permalink

How to fix hasplmd crashes

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

Developer features I will miss from Final Cut Pro 7

I'm currently working on a feature film that will be my last Final Cut Pro 7 project. I'd just finished implementing a custom solution to automatically log and sort clips as they are brought in, when it suddenly occurred to me that a lot of what I was doing would not be possible in the future with a competing NLE (at least not on the Mac; Sony Vegas has great scripting capabilities).

Here is a summary of things we can do with FCP 7 that is impossible or less smooth with its replacements:

(Note: we don't develop effects plugins so this post does not delve into plugin-related differences between the apps. But it's a post I'd be glad to link to if someone else writes it.)

Controlling the NLE

Developers can use Apple Events to perform such tasks as programmatically saving and loading projects, highlighting items in a bin and searching. None of the competing apps are able to do this.

We can also communicate with Final Cut Pro over MIDI, which we put to good use in Cut Notes, but Premiere and FCPX unfortunately lack this feature.

XML Interchange

It is important to be able to easily get data in and out of the editing application. There is mixed support for this among competing apps. Avid has XML output via FilmScribe but this is not as fully-featured as FCP XML and I have found the FilmScribe app to be unreliable. FCPX XML exports do not include all of the information within the project or event. Premiere gets full marks for including FCP 7 XML interchange support.

Avid does get some bonus points for being able to import and export marker lists though, which none of the others can (it's even better than FCP 7 which was limited to export only). Some people would say this feature is unnecessary if you have XML input, however it's very useful for applications that don't need or cannot access the underlying project, such as our own Cut Notes app.

Manipulation of project data

Probably the most useful feature is the ability to change data within the project. You can add new clips, batch modify metadata and sort clips into bins. It's very powerful and you can specify various options when importing a clip or bin such as only adding clips that do not currently exist or making copies of existing clips.

More importantly, it can be done on the fly without needing to close the project or modify any files on disk. Quick Bins, FCP Versioner and several of our other apps make use of this feature.

Avid doesn't support this at all and Final Cut Pro X and Adobe Premiere only support this via manual XML import / export.

Premiere wins extra marks for basing its project file format on XML but it then loses most of them by not documenting the project file format nor encouraging development of it.

These are all great features that we're putting to good use in our apps and it's a shame to lose them. We've developed workarounds for most of them but these often require additional manual work by the user, which we're keen to avoid.

Apple created third-party developer ecosystems with FCP 7 and FCPX that simply don't exist with other NLEs (and FCPX's developer features still need some more work, as noted above). We're putting this post out to encourage NLE manufacturers to increase their focus on third party developer-friendly features. Fostering third-party development helps end users, developers and the manufacturers themselves. Everyone wins.

Posted by Jon Chappell on Monday March 26 2012 11:57 AM to Analysis, Avid, Adobe
5 comments Posted Permalink