It needed a bit of extra time on the oven, but Xsan 2.2 is now available for download. You can find it in several flavors:

• Release notes
• Full Install Disk (all OS versions, it seems)
• Updater for 10.5
• Updater for 10.6
• Admin Tools for 10.5
• Admin Tools for 10.6
• Uninstaller

Or you can just use Software Update. (I can't remember a release of the full installer like this before. It is certainly a nice touch.)

Make sure you update your metadata controllers before updating clients. To be safe, make a backup of your MDC's /Library/Filesystems/Xsan/Config folder. And don't go enabling extended attributes until everyone is running Xsan 2.2.

[Update: Please note the interesting experiences in the comments below.]

Although I can't find the download anywhere, Apple has posted several KB articles on Xsan 2.2. I guess they want us to be good and ready for the release.

• Xsan 2.2: Enabling extended attributes
• Xsan 2.2: How to set Spotlight search levels
• Xsan 2.2: Avoid using native extended attributes with StorNext clients
• Xsan 2.2: "fsmpm not running" message in Xsan Admin
• Xsan: Install Xsan 2.2 Update for 10.6 after installing Mac OS X v10.6
• About the security content of Xsan 2.2

They also updated a few older articles...

• Xsan: Compatibility of Xsan metadata controllers (MDCs) and clients
• Xsan 2: Optimizing file system journal size
• Xsan 2: "The item will be deleted immediately" or "-1407" alert when moving items to the Trash

All Xsanityers in Amsterdam are invited for drinks at our crash-pad:

Friday, September 11, at 20:00
Eerste Laurierdwarsstraat 23

Thanks to Tekserve and Offhollywood Digital for sponsoring.

(Although I can't make it, I'll be sure to wear my wooden shoes. — Aaron)

Apple has posted a knowledge base article about an incompatibility between Xsan 2.1.1 and OS X 10.6:

Do not upgrade computers running Xsan 2.1.1 to Mac OS X v10.6 or Mac OS X Server v10.6 Snow Leopard.

You must install the Xsan 2.2 Update for compatibility with Snow Leopard; this update will be available soon.

Apple quietly announced Xsan 2.2 yesterday. Although not yet shipping, we do have some information to bring you.

First, the bad news. Xsan 2.2 is Intel-only. It will not run on PowerPC hardware. This implies that your metadata controllers need to be Intel.

Also, support for 1.x clients has been dropped when connecting to a metadata controller running 2.2. Time to shell out the upgrade money! To be clear, clients can be either PPC (running 2.1.1) or Intel (running 2.1.1 or — better — 2.2).

Now the good news: Xsan 2.2 supports Mac OS X 10.5.7 10.5.8 and 10.6 (Snow Leopard). Snow Leopard will begin shipping on Friday, August 28. There are fixes for extended file system attributes, Spotlight searching, and failover. And it will be a free upgrade from Xsan 2.

Now a friendly reminder: Keep your upgrades under control. No Xsan client should have a greater version of the OS or Xsan than the MDCs. You may want to restrict the ability for your clients to perform software updates until you have updated your MDCs.

Expect Xsan 2.2 to be released shortly. Keep looking here for the latest info.

Details on WriteXML and ReadXML changes in FCSvr 1.5, after the jump...

I have attempted to point out various feature enhancements and I give my opinion on what I think is useful. Once I get my hands on the FCSvr 1.5 DVD, I'll post a more detail and screen by screen comparison of FCSvr 1.1.1 vs 1.5.

Note: Most of the information for this article was provided by what's Apple has publicly announced on apple.com/finalcutserver/.

Active Directory support

Final Cut Server 1.5 now supports the authentication and authorization of users against Microsoft’s Active Directory (AD). This feature is huge; it didn’t exist in Final Cut Server 1.1.1, and was a huge hurdle for Final Cut Server being adopted in many enterprises and as well education organizations that had large AD deployments. Now AD users can now log in using their same username and passwords that they used for logging into their Macs (if bounded to AD) and/or their Microsoft Exchange email accounts.

Offline editing with ProRes 422 (Proxy)


Final Cut Server 1.5 now supports a new flavor of Edit Proxies ProRes 422 (Proxy). This new ProRes codec fixes many issues that existed with the flavor of the Apple Pro Res Edit Proxies codec that shipped with FCSvr 1.1.1.

Selectable proxy format creation

Final Cut Server 1.5 now supports the ability to catalogue your media using distinct Clip Proxy transcode settings. Previously in Final Cut Server 1.1.1 a user was only allowed to use 1 specify type of Clip Proxy for all assets in Final Cut Server. This didn’t allow very much flexibility when you needed to catalogue for example SD 4:3 footage and 16:9 HD footage, because depending on the Clip Proxy transcode setting you selected your footage would be either squished or stretched.

Image Sequences


Final Cut Server 1.5 now has more robust and useful integration of image sequences. You can now view image sequences as entire asset. Before in Final Cut Server 1.1.1 or earlier, Final Cut Server would only create an asset bundle assets of image sequences. Now when cataloguing an image sequence, FCSvr allows to you create an “image sequence asset”. 

Cataloguing the asset using the “Create an image sequence option” will both preserve the image sequence as a bundle, but now also create a video clip proxy, and a ProRess 422 (Proxy) if enabled, that will allow you to use this image sequence directly in Final Cut Pro (FCP) for editing.

Production

Final Cut Server 1.5 now supports production hierarchies, which essentially allow you to store productions within productions. This will also offer administrators the ability via a new set of Permission Sets to have more granular control over which productions or sub productions a user or group has access to.

Smart Searches


Final Cut Server 1.5 now allows users to save Smart Searches Globally. In Final Cut Server 1.1.1 Smart Searches could only be saved and be reused by the user creating the smart search, which was an administrative pain. Now users have ability to save their smart searches saved and made available for use to all Final Cut Server users.

Improved search performance

Although I haven't experienced Final Cut Server 1.5, my assumption is that Apple has configured further optimization of the Postgres implementation of Final Cut Server as well.

Support for metadata in audio files

Final Cut Server 1.5 now parses and displays metadata from AIFF, WAV, CAF, M4A, SDII, and AAC files. Previously in Final Cut Server 1.1.1 this embedded metadata was not searchable and/or viewable in the Final Cut Server DB. I personally had to write a script that parsed this information out of the file and sync it with Final Cut Server. For Final Cut Server 1.1.1 users, I will post the script and implementation instruction shortly.