Archive for September, 2006

Best of New York…We need your help!!

Monday, September 18th, 2006

Wiredrive and Getty Images are co-sponsoring the Boards Summit Closing Night Party on Thursday, October 25th at the Knitting Factory.

We are in the process of designing the party invitations, and need your help!

Our invitations are going to feature as many local NYC favorites as we can fit, and you, dear reader, are going to help us create them. We want to know the best art museums, the greenest parks, the tastiest bakeries, the unparalleled shopping, the hippest restaurants, the blurriest bars, the coolest music venues, or just a good place to grab a game of chess.

Yes, we would like YOUR help to create a “Best of NY” list for people in the commercial industry.

Please list your picks in the comment section below, and tell us why they’re your favorite… and tell your friends to do the same!

Your valuable feedback will be integrated into our invitation designs! We hope to see you at the party, so don’t forget to register for the Boards Summit at www.boardssummit.com.

Mac OS X Compatibility with Autodesk Cleaner 6.0

Monday, September 11th, 2006

A few clients were having issues when trying to compress video files with Cleaner 6.0 using the latest version of Quicktime. Here is what
Autodesk says about the compatibility issue:

Published date: 2006-03-14
ID: TD5935147

Applies to:
cleanerâ„¢ 6.0.1 for Macintosh
cleanerâ„¢ 6 for Macintosh

Please note that the recommended operating systems for Autodesk Cleaner 6.0 are: Mac OS 10.1, 10.2, 10.3, with QuickTime v5 - 6.5

New features introduced since Mac OS 10.3 (Panther), including H.264, will not be supported by Cleaner 6.0. However, support for these features, as well as certification for Mac OS 10.4 and QuickTime 7, is now available in Cleaner 6.5.

See it here:

Some people found a way around this by uninstalling the latest Quicktime and reverting back to an earlier version, but we cannot recommend this. You may want to consider upgrading to Cleaner 6.5, which has fixed this problem, or using a different encoding method entirely.