On April 13th AJA announced new drivers for Kona 2 with hardware upconversion, dual link 10 bit RGB capture and a host of other features. These drivers are recommended and should be installed now. [See Hub News April 13 for details.] At NAB they announced compatibility with Final Cut Pro 5 for both Kona 2 and the Io family.
For Io, Io LA and Io LD the main new feature is reduced latency between computer screen and video monitor over the FireWire connection: down from 7 frames to 4 frames for improved responsiveness. The Io family gets 23.98 frame rate support across the board to support 24P and film project ingest and output. Io will support MultiCam playback of up to 16 sources, video output for Motion 2 and video output from Shake 4.
Io Control Panel
AJA have released a first beta of the Io Control Panel that allows the Io family to act as standalone media converters as long as Final Cut Pro is not running. Inputs and outputs can be selected and saved as presets.
Kona 2 gains much more interesting functions in association with Final Cut Pro 5 (due for release in "May"). As well as MultiCam support for 16 sources, Kona 2 provides HDV codec acceleration to take load off the CPU. Taking load off the CPU for HDV playback lets the CPU perform more real-time effects. Kona 2 and Kona LS have full support for Apple’s new Dynamic RT Extreme, using hardware where it can help (mostly offloading codec decoding) and the host processor otherwise. Both Kona cards support 8 channels of audio input and output and, like Io, video out for Motion 2 and Shake 4.
These improvements for Final Cut Pro 5 appear to be included in the 1.1 Driver update now available (but won’t have any of the new features until Final Cut Pro 5 ships). The updated Io drivers will be available in May, when Final Cut Pro 5 ships.
For those who are wondering about QRes – a feature announced for Kona2 for low resolution captures but never shipped – AJA are supporting standard codecs like DV25, DV50 and DV100 for lower quality captures from uncompressed source, making QRes unnecessary. While the feature is not officially "dead", it’s on a very long term hold.