Tutorials Category

Using folder breaks to create folder hierarchies in Post Haste

Post Haste is a Mac and Windows app to organize your projects from customizable templates. You can setup various parameters to include in the folder name such as project name, client, date, etc.

In the recent rewrite of Post Haste we added a new feature called folder breaks. Folder breaks can be set on a per-parameter basis and tell Post Haste to create a new folder at the start of that parameter. This allows you to create folder hierarchies and is best explained through example.

Folder breaks can be added by ticking the relevant checkbox next to a parameter in the preferences window.

Here are some examples of how folder breaks affect the destination path of the project, using the parameter values shown in the screenshot below.

If all folder breaks are switched off, Post Haste will create a single folder with each parameter separated by an underscore (or whatever separator character you have chosen).

If a folder break is added for the Project parameter, Post Haste will create a new folder and all subsequent parameters will be appended to the project name with an underscore.

If a folder break is added for the Project parameter but the parameter value is left blank, Post Haste is smart enough to apply the folder break to the next valid parameter value.

If a folder break is added for Project and Editor, Date is appended to Project and Editor becomes a new folder.

If a folder break is added to all of the parameters, it looks like the following:

Post Haste allows filename conventions and project organization to be largely invisible to the end-user. Folder breaks make it easier to fit the app into existing naming conventions and are very useful for corporate environments.

Post Haste is a free app for Mac and Windows and is available here.

Posted by Jon Chappell on Thursday April 5 2012 10:19 AM to Video Editing, Software, Tutorials
0 comments Posted Permalink


How to create installers for your plugins and effects

If you are a plugin developer, Plugin Manager in Pro Maintenance Tools can be used to create installers. These provide an easy way for end-users to install plugins quickly and easily with very little setup required from the developer. Installers are completely self-contained so end-users do not need Pro Maintenance Tools installed.

To create an installer:

1. In the main plugin view, select the plugins or groups that you would like to add to the installer. You can have more than one plugin in an installer.

2. Go to Tools > Create Plugin Installer.

3. In the window that appears, specify a name for the plugin or group or plugins, the version number and author.

4. The code signing pane allows you to sign the installer to show that it hasn't been modified by an unscrupulous third party. This is necessary for running the installer on OS X 10.8 or higher.

Signing is optional for users on OS X 10.7 and below but it is recommended if you have access to a valid certificate. Visit Apple's developer site for more details on creating and installing a Developer ID certificate.

Once the certificate is installed, select it from the list in the Code Signing tab.

5. Click Create Installer and you will be prompted for a location.

6. Test the installer by moving the plugins you added to the installer to another location such as the Desktop, running the installer and then checking in Plugin Manager to see if the plugins were installed correctly.

7. Users can choose the Install button to install plugins to their default location or they can click Send to Plugin Manager to import with more options.

Plugin Manager is a comprehensive tool for managing your plugins. It is available as part of Pro Maintenance Tools.

Posted by Jon Chappell on Tuesday April 3 2012 2:34 PM to Software, Tutorials, Developer
0 comments Posted Permalink


What does that error message mean?

Sometimes your NLE will throw up a cryptic error while you are editing, such as "General Error 41" (Final Cut Pro) or "BAD_MAGIC" (Avid). Such errors are often meaningful to the application's developers but not its users.

Luckily Crash Analyzer in Pro Maintenance Tools has a comprehensive error database. Click the Error Lookup button in the toolbar and you will be presented with a searchable list of all supported errors (over 200 at the current time of writing).

Selecting an error presents an explanation of the cause with suggestions on how to overcome it. This can be a real timesaver when a cryptic message pops up on a deadline.

A full list of supported errors is available here and we add new ones in every software update. If you receive an error message that is not supported by Crash Analyzer, you can submit it for inclusion in a future version from the Actions menu.

Crash Analyzer is available as part of Pro Maintenance Tools. We also have an iOS app called EditCodes that uses the same database.

Posted by Jon Chappell on Monday April 2 2012 4:40 PM to Video Editing, Software, Tutorials
0 comments Posted Permalink


Improving tapeless media management with Auto Transfer

Working with tapeless media requires a robust organization and backup policy to ensure your footage remains safe.

One key area of concern is memory cards and readers, as cheaper ones can sometimes behave erratically when they get hot, causing data corruption. Worse still, OS X's Finder will not always show an indication that footage is corrupt when you copy it to your hard drive.

If your camera shoots to QuickTime movies, you should at the very least browse to the copied location and scroll through the directory to spot movie clips without thumbnails, as this may indicate files that are unreadable.

Another potential issue is directory structure. While it may be tempting to copy just the movie clips to your hard drive, some applications and Log and Transfer plugins are expecting the files to exist in a particular place within the directory hierarchy. Not maintaining this structure can lead to files being imported without metadata and timecode or sometimes not importing at all, depending on the application or plugin.

Auto Transfer is a tool for simplifying these problems. It can automatically copy the contents of your memory cards to multiple locations for safety. It also performs checksums on the copied files to ensure they are exactly the same as those on the card.

If a file fails the verification check, Auto Transfer allows you to try copying the file again. The Info pane keeps a record of how many times a failure occurs when copying from a particular card, which is a very useful indicator of a card that's potentially faulty.

Auto Transfer copies the full directory structure from a card, which ensures that it will be able to be read correctly by your NLE and companion apps. It can copy multiple cards simultaneously.

You can also specify additional metadata which can be used to create a custom directory structure, similar to our project management app Post Haste. For example, you could instruct Auto Transfer to create a new folder for each shooting day and put the relevant day's card contents in that folder. Alternatively you could create a directory structure based on the reel, project name and date. It's very customizable and is great for businesses that wish to have a consistent naming convention.

The metadata can also be added to a spreadsheet. There is one spreadsheet per project and each card is added to a new row at the end of the sheet. This allows you to have a printable record of any data you wish to track such as the reel number, scene information, description and more. The columns are customizable.

Various actions are available upon a successful transfer including Growl notifications (see our tutorial for sending Growl notifications to an iOS device), playing a sound effect, ejecting the drive, showing the files in Finder and much more.

Auto Transfer is an essential tool for DITs and anyone who deals with tapeless media. It is available as part of Pro Media Tools and there is a 15-day trial available here.

Posted by Jon Chappell on Thursday March 29 2012 3:04 PM to Software, Cameras, Tutorials
0 comments Posted Permalink


How to restore a trimmed QuickTime movie

QuickTime Player 7 can be very useful for quickly trimming a clip or outputting different sections of a movie to separate files. This can be accomplished by setting the in and out points, going to Edit > Trim to Selection and then exporting the file or doing a Save As.

However, if you accidentally hit Save instead of Save As and then close the movie (this happens more often than you'd think), the movie will be permanently trimmed.

Luckily QT Repair in Pro Maintenance Tools can fix this. The repair assumes that the trimmed data still exists in the file and that the movie is capable of being opened in QuickTime Player and played back, albeit at a shorter length.

1. First of all, check that the trimmed data is still in the file. Open the file in QuickTime Player and press Cmd+I to view the Info window. Compare the Data Size section to the size listed by the Finder - if the size on disk is significantly larger, that means the data is still within the file.



(Note that the size listed in the Info window will never exactly match that of the Finder because it does not include extra data like the QuickTime structure and Finder is using a slightly different method to calculate file sizes as of OS X 10.6.)

2. Launch QT Repair and open the movie clip.

3. In the Quick Start dialog, choose the option to restore trimmed edits.


4. QT Repair will now create a copy so that the original file is safe. This can take a while depending on how big the file is. You can disable this in preferences if you already have a backup of the file elsewhere.

Once the backup is complete, processing should be very quick.


5. When QT Repair says it has finished processing, click OK and it will launch the restored movie in QuickTime Player. The movie should now be its full length. Look at the Data Size field in the Info window and scrub the playhead to check that everything has been restored correctly.

As you can see from the screenshot, QT Repair successfully restored the length of the video and the Data Size field is much closer to the value in the Finder now.

Posted by Jon Chappell on Monday March 5 2012 8:07 AM to Software, QuickTime, Tutorials
0 comments Posted Permalink


How to get render notifications on your iPhone

Editors spend a lot of time rendering and exporting, and it's very useful to know when a render is complete if you are not currently at your computer.

Render Watcher in Pro Media Tools can watch for renders and then perform various tasks when a render is complete. It supports Final Cut Pro 7, Compressor 3 and 4, Avid Media Composer, Adobe Premiere Pro and Adobe Media Encoder.

Render notifications are not supported for Final Cut Pro X because it has background rendering and the alerts would be going off constantly, however you can get export notifications via Compressor or by adding your export folder to the Watch Folder pane. This also works for other apps not natively supported by Render Watcher.

There are three ways to get render notifications from Render Watcher on your iOS device - text message, email and push alert. (Compressor has email support already, however it is impractical for most users because it requires you to run an SMTP server on your computer.)

Push alerts are the most flexible option because you can customize them independently to make sure render notifications don't get lost in your regular email and SMS alerts.

Here's how to setup render and export notifications on your iPhone / iPad:

1. Download and install Pro Media Tools.

2. Launch the Render Watcher application and tick the boxes for all of the render notifications you wish to watch. If desired, add watch folders for applications not natively supported.

3. Go to the Actions tab and select all of the actions you wish to perform when a render is detected. There are lots of options here including playing a sound effect and showing the exported file in the Finder.

4. If you want to send an email or text message, tick the relevant checkbox and enter the destination email address or phone number (selected carriers only).

If you want to only setup push alerts, skip to step 5.

4a. Go to Preferences and enter the details for the account you wish to send email from. Presets have been included for common email providers but you will be able to get the relevant SMTP server information from your email provider's website. In most cases you should leave the Port field blank.

Note: Your email address and password are not sent to our servers and are stored on your computer in encrypted form.

4b. Click Send Test Email and if your settings are correct you should receive an email from Render Watcher in your inbox.

If you don't wish to setup push alerts, skip to Step 13.

5. To setup push alerts, make sure Display Growl notification is ticked in preferences and then download Growl from the Mac App Store for $1.99. If you don't want to pay for it or are running OS X 10.6 or lower, older versions are available here free of charge.

6. Download Boxcar for iOS. We favor Boxcar because it is free (with ads) but this feature should work with any push notification service that supports Growl, such as Prowl.

7. Sign up for a Boxcar account here.

8. In the Boxcar iOS app, sign in and tap the icon in the top left corner that looks like a grid of nine squares. Then tap Add Service.

9. Scroll down the list (it's not alphabetically-ordered) and tap the entry marked Growl. Setup the notification settings as desired and then click Save.

10. Download the Boxcar plugin for Growl. Unzip the .growlView file and double-click it to install. When prompted, select Yes to open the Growl preference pane or alternatively launch System Preferences and open it manually. If you are running the Mac App Store version of Growl on Lion, the preferences dialog is accessed via the menu bar icon.

11. Go the the Display Options tab in the Growl preference pane (called Displays in the Mac App Store version) and set Default Style to Boxcar. This will send all Growl alerts to your iOS device.

Alternatively, if you only want Render Watcher notifications sent to your device, go to the Applications tab, select RenderWatcherHelper, click the Configure button and then set Application's Display Style to Boxcar. RenderWatcherHelper will only appear in the list when it has displayed a Growl alert at least once.

12. In the Display Options tab, select Boxcar in the Display Styles list on the left and select the option to display notifications using Smoke (or whichever theme you prefer).

13. Enter your Boxcar login information below this and click Verify Login. If your login is accepted, click Preview and you should see a Growl alert on your desktop and iOS device.

14. Start a short render and wait for it to finish. If everything is setup correctly, you should see a Render Watcher alert on your computer and then your iOS device. If you don't see this, double-check that you followed the above steps correctly and that the name of the application is ticked in the Applications tab in Render Watcher or that you are exporting to a directory listed in the Watch Folders tab.

Render Watcher is just one of ten useful tools for editors, assistant editors and post production professionals in the Pro Media Tools suite. To find out more, see the features page, watch the overview video or download the free trial.

Posted by Jon Chappell on Monday February 13 2012 2:46 PM to Final Cut Studio, Adobe, Tutorials
0 comments Posted Permalink


How to export chapter markers from Final Cut Pro X

Much has been written about the missing features in Final Cut Pro X when compared with FCP 7. One particular missing feature that has been causing workflow problems for some people is the inability to add chapter markers to an exported QuickTime movie for displaying on an iOS device or Apple TV.

There are several workarounds, such as adding chapter markers in Compressor, but these can be quite tedious as you need to create them manually. Luckily QT Edit in Pro Media Tools can automatically create chapter markers directly from the markers in your Final Cut Pro X timeline.

Here's how to do it:

1. Add markers to your FCPX timeline where you would like the chapters to occur.

2. Share your timeline to Compressor and use one of the Apple Device presets to create an m4v file.

3. Click on the filmstrip icon in FCPX to go back to the Project Browser and then highlight the project name in the list.


4. Go to File > Export XML to create an XML copy of your timeline.

5. Open up the exported movie with QT Edit.

6. Go to File > Import > Chapters.

7. Select "Final Cut Pro X XML (.fcpxml)" in the file type dropdown and browse for the XML file you created earlier. Click Open.

8. The markers will be imported and automatically added as chapters which can be viewed in the Chapters tab. You can edit the chapter positions and modify their names in this tab. Click on a chapter in the list to jump to that point in the movie.

Important: You must have a chapter on frame 1 in order for iOS to detect the chapter list. If your imported markers do not already have a chapter marker on this frame, set the playhead to the start in QT Edit and click the + button in the Chapters tab.

9. Save the movie in QT Edit and sync it to your device.

You can now play the movie on an iPad, iPhone, iPod Touch or Apple TV and the markers will be recognized. QT Edit can also import Final Cut Pro 7 marker lists, Avid locator lists, DVD Studio Pro chapter lists, CSV files, text files and chapters from other QuickTime movies.

Posted by Jon Chappell on Monday February 6 2012 2:26 PM to Final Cut Studio, Tutorials
2 comments Posted Permalink