not sure if it's 64 bit - they're not shouting from the rooftops about it being so, so i'm not sure it is.
Why does this need to work on a windows computer? I hope the delay in getting this out isn't due to spending ages working on the windows port.
Allow me to crush this line of speculation:
Final Cut Server is based on Apple's acquisition of a company called Proximity and their Artbox product in the summer of 2006. Artbox ran on linux using a PostgreSQL database and a thin Java client that ran on either Windows or OS X. It handled QuickTime encoding using WINE on linux. Final Cut Server is really just a freshened GUI that with a revamped back-end ported to Leopard which now leverages Qmaster for encoding tasks. It also integrates tightly with Final Cut Pro (which Artbox did not).
So is Final Cut Server 64 bit? The thin client is just Java and QuickTime, so who cares if it is 64 bit? It doesn't need to be. The back end uses the already highly-optimized Qmaster engine for all the heavy lifting.
The Windows client functionality is key because this product is expected to work in a professional environment where Apple does not own all the desktops in the customer companies. This added zero time to development since this feature was already there in Artbox (besides, Sun did all the work anyway when they invented J2SE).
Blame the delay on Leopard being delayed, which is the iPhone's fault. Wait till next year for a new Final Cut Studio.