AVCHD Lite – What is it (and why can’t I edit it in iMovie or Final Cut)? (updated)

After a few years of being available there are now many hard-disk based video cameras that use the AVCHD format for video, support for the format in video editing software is well supported now on both Mac OS X and Windows by apps like Final Cut Pro / Express, iMovie, Adobe Premiere, VoltaicHD and more. This all leads to a much simpler experience for users of AVCHD cameras than it was a couple of years ago.

AVCHD Lite – Throwing a spanner in the works?

Image of Panasonic Lumix camera that uses the AVCHD Lite format

More recent digital stills camera have started coming with the ability to shoot HD video, for many of the small compact cameras there became a need for high-quality efficient video format that could be used in small compact cameras with less capable hardware. The solution to this was a variant of the AVCHD format called AVCHD Lite.

The main differences between AVCHD Lite and the regular AVCHD: a maximum resolution of 1280 x 720p in AVCHD Lite compared to 1920 x 1080p in regular AVCHD and a less-intensive compression method – both of which make the format more suitable for less powerful camera hardware.

Why can’t I edit AVCHD Lite in iMovie or Final Cut?

AVCHD Lite throws a spanner in the works because many of the existing AVCHD editing packages are incapable of supporting it without an update to the software. At the time of writing none of Apple’s video editing applications such as iMovie, Final Cut Pro or Express support the AVCHD Lite format. Adobe’s Premiere and Premiere Elements applications also do not appear to support AVCHD Lite at this time.

The only solution for AVCHD Lite on Mac OS X at the moment is the one that saved many an early adopter like myself a couple of years or so ago when AVCHD cameras first came out – VoltaicHD by Shedworx. This is a $35 app that will convert your AVCHD Lite footage to the Apple Intermediate Codec format that can then be used in any of Apple’s video editing applications.

Some Handy Links / References…

Here’s a few links to some handy information about AVCHD Lite:

Update:

As of 04/06/09 iMovie now supports editing of AVCHD Lite files with the iMovie 8.0.3 update!

FlamingoHD 1.0 released

I wrote a review of FlamingoHD a couple of months ago of their new media management application for Mac OS X called FlamingoHD (made by Shedworx, the makers of VoltaicHD).

At the time of the review FlamingoHD was available for sale as a beta version (for those early adopters!), however, Shedworx have reached their first milestone and have now released version 1.0 of FlamingoHD to the world!

The main new feature in the final version 1.0 release is a new filmstrip view that lets you see keyframes from the video clips in your library. This is really handy and lets you see what scenes are within your various clips:

For a more detailed overview read my previous post: FlamingoHD – Helping you manage your AVCHD media or checkout the FlamingoHD page on the Shedworx website.

How to restore a MySQL database from your Time Machine backup

I’m writing this as much to remind myself as for anyone else really :) I generally run databases running on my MacBook which I use for sites in active development, I then transfer these databases over to a staging server which are then use by other people in the team and sometimes clients to input site content. Last week I imported content from the staging server and overwrote my local database thinking that the staging server was the most up to date, but as it turned out I was incorrect!

Fortunately I’m running Mac OS X’s Time Machine backup on my MacBook so I didn’t see a problem as I could just restore it from that. However, in reality it wasn’t quite as straight forward to do, so here’s what I had to do in the end to restore this database from my Time Machine backup.

Step 1: Find your local databases

Navigate to the location of your MySQL databases. For my MySQL install this is found at /usr/local/mysql but depending on how you’ve installed MySQL it might be elsewhere.

As you’ll probably see that’s not a location you can just regularly view in the Finder on Mac so you’ll need to use the ‘Go to Folder…’ option within the ‘Go’ menu in the Finder.

Once you’ve got to that location you’ll see the MySQL data folder which shows up with a red no-access symbol on it so you can’t actually navigate straight into it via the finder. Seeing as we can’t access the folder to restore a specific database we’ll just restore the whole folder from the Time Machine backup instead.

Image of MySQL's Data folder in the Finder

Step 2: Shutdown your MySQL server

It’s important that you shut down your MySQL server process before you continue. How you do this depends on how you’ve got MySQL installed. If you installed MySQL from the official installer for OS X downloaded from the MySQL website then you may have the a System Preference which you can use to stop it.

If you’ve installed MySQL another way such as self-compiled or via Mac Ports or you just want to use the Terminal then you can stop it from the Terminal instead. The following command can be used:

sudo mysqladmin shutdown

If you don’t have MySQL configured in your path in Terminal you may need to use the full path to the mysqladmin command:

sudo /usr/local/mysql/bin/mysqladmin shutdown

The path to those files may vary depending on how you’ve installed MySQL so if it doesn’t work then you’ll need to check the correct location. Note that I’ve also used ‘sudo’ in that command in case you need root privileges to stop the MySQL process. Check the MySQL documentation for your version of MySQL for further help.

Step 3: Rename your MySQL data folder via the Terminal

Image of file listing in OS X's Terminal applicationThe next step is to rename your MySQL data folder temporarily to avoid any clashes when restoring the data folder from the Time Machine backup. First you need to get into your MySQL directory:

cd /usr/local/mysql

You can then list all the files to check you’re in the right place:

ls -al

You should now see all the files including the ‘data’ directory where the databases are located. We can now use the following command to rename the data directory:

sudo mv data data-bak

Once that’s done you should see your directory happily renamed in both the Terminal and the Finder window.

Step 4: Enter Time Machine to restore your MySQL data directory

The next step is to enter Time Machine mode and restore the data directory from the backup. I’m sure you probably know how to enter Time Machine mode but make sure you enter whilst focused on the MySQL Finder window.

Image of restored files in Finder windowGo back in time a sufficient amount so that you’ll definitely be getting the version of the data that you want, highlight the data folder and click Restore. Because we renamed the data directory Time Machine will simply restore the data directory without any prompts. You should now see both the restored data directory and the renamed data-bak directory.

Step 5: Copy the database from the restored data directory

You can now copy the database from the restored data directory, this is done via the following Terminal command:

sudo cp -R data-bak/my_database_name data/my_database_name

The database is actually a directory containing other files so you need to use the ‘-R’ flag to recursively copy all of these across with the directory itself.

Step 6: Delete the restored data directory and rename the data-bak directory

Now that the database is restored and copied you can safely delete the restored data directory as it’s no longer needed at this point. Note: Be very careful using the ‘rm’ command! Bad things can happen if used incorrectly!

sudo rm -R data

You can then rename the data-bak directory back to it’s original name ‘data’, note that the ‘mv’ command doesn’t require the ‘-R’ flag:

sudo mv data-bak data

Step 7: Check file permissions / ownership

You may need to check the file permissions and ownership of the database that you have just restored to make sure that it will be accessible by MySQL when it is running. These may vary depending on your MySQL install method but they should be something like this:

drwx—— 60 _mysql wheel 2040 8 May 12:14 my_database_name

Basically the directory is owned by the user ‘_mysql’ and in the group ‘wheel’. If you need to change the owner then use the following command:

sudo chown -R _mysql data/my_database_name

Step 8: Start up MySQL

Once this has all been done, you can then start MySQL again using either the System Preference if you have it or via the Terminal command:

sudo mysqld_safe &

or with the full path:

sudo /usr/local/mysql/bin/mysqld_safe &

Step 9: There is no Step 9!

Hopefully you should now be able to access your newly restored database. As I said at the beginning, this is the method I used to restore a database myself recently, there may be other ways to do it but hopefully these steps might be of use to anyone else in the same situation.

Clipstart – Simple video file management and uploading for Mac OS X

Clipstart is a newly released application that is designed to complement Photo applications such as iPhoto or Picasa. It offers a streamlined interface that lets you import video footage from video cameras, tag them and then upload them to either Vimeo or Flickr.

Image of Clipstart application iconThat’s Clipstart’s features summed up in one paragraph but the application does what it does really well. There’s been a growing need for applications like these to manage the ever increasing amount of consumer video that many people have on their computers these days. iMovie is great for editing video and iPhoto can import video into it’s library but neither of them are up to the task of file managing the quantity of video files that users of digital video devices (e.g. Flip, Kodak Z series and mobile phones such as the Nokia N series etc) tend to produce.

Clipstart lets you manage all these files simply and easily and lets you upload either whole clips or only specific sections of clips directly to both Vimeo and Flickr. There’s currently no YouTube support though, I’m not sure if this is because Apple’s iPhoto already supports YouTube directly but I could see YouTube being another location that users would like to publish too so perhaps this will come in future versions. Update: I remembered that the upcoming Snow Leopard Mac OSX 10.6 also features an updated version of Quicktime Player which can upload straight to YouTube, perhaps this is one reason why Clipstart doesn’t include it?

You can find out more about it over at the Clipstart website where there is a screencast that takes you through the workflow and features as well as a demo version that you can use to try it out for yourself. It costs $29 for a single user licence.

Working with HD video on Mac OSX? FlamingoHD is another good option to check out…

If you’re working with HD video then you’ll want to check out FlamingoHD which is a similar application to Clipstart but is more specifically focused on HD workflow and in particular providing support for the AVCHD format of HD video used on many hard disk based cameras. FlamingoHD does also support all other video formats supported by Quicktime so video from Flip and Kodak Z series cameras can be imported as well as digital stills.