[Szumlins]

And you are getting a hot output on SDI 1? Do you have a down convert playing out or something like Video+Key selected? In the Kona control panel set your primary and secondary format to whatever your monitor is capable of with your footage. Just set control to color bars and see if you are having the same problem.

—
—
-Mike

[Szumlins]

You may have problems on output if you don’t have your lanes set up properly on the PCIe bus (based on your other question). Make sure the Kona card has at least a 4x slot before trying to view any output.

—
—
-Mike

[Szumlins]

If you read the release notes in the latest Kona drivers, it explains that Kona cards will run just fine in a 4x slot. Select option 2, put your Kona and storage in slots 3 an 4.

—
—
-Mike

[Szumlins]

I hear if you rub his belly you get three wishes.

—
—
-Mike

[Szumlins]

The easy setups for the Kona cards correctly use 10-bit.

—
—
-Mike

[Szumlins]

[Mack Truck] “So what would be the IO HD setup for a MacBook Pro (firewire 400 drive ?). Thanks.”

You would get an Express34 firewire card or eSATA card to support your storage on a Macbook Pro

—
—
-Mike

[Szumlins]

[Lance Bachelder] “You can also run your Avid’s and Pro Tool rigs off MetaSan for add’l storage.”

Last I had checked, MetaSan no longer supported ProTools. Even though ProTools saw the volume and was capable of accessing it, the latency involved in every read/write going back through the MDC was causing unreliable and unusable results. This is one of the big reasons why file locking SANs traditionally do not work in ProTools environments.

Someone correct me if I’m wrong here about MetaSAN/PT support.

—
—
-Mike

[Szumlins]

[David Jahns] “FibreJet or Terrablock? We want a file level SAN, not a volume level.”

I’d have to say the Terrablock is a rock solid machine. Is there a particular reason you’ve decided that file level is that way you want to go? Especially with FCP I see file locking somewhat of a null issue. All of the NLE’s in use are non destructive anyway, media can be on any volume.

The real power of the Terrablock comes from the fact that it isn’t tied to OS or any sort of software abstraction layer. If your app can work with a local hard drive, it can work with a Terrablock. In addition to this, upgrades like Panther or whatever big cat comes next aren’t going to require a full metadata controller overhaul. The client OS doesn’t now the hard drive isn’t local and requires no special software to mount a volume.

Couple that with the unmatched stream count coming out of the Terrablock and it is win-win.

—
—
-Mike

[Szumlins]

AJA hasn’t released easy setups yet for the Io and FCS2, but they will be available shortly. Apple provides the actual driver for the Io, so if you are lucky enough to have an Io and a copy of FCS2, you’ll have to hand generate easy setups or just wait for a bit.

—
—
-Mike

[Szumlins]

Just to clarify from a technical level, the ioHD speaks ProRes422 along the firewire 800 cable. Essentially when footage is sent out to the ioHD, it translates that footage to ProRes422 for playout by the device.

Since FCS2 just shipped and the ioHD hasn’t even begun to yet, it remains to be seen what the hardware limits will be, but in theory you could still edit and work with uncompressed HD footage, just not capture it.

At the end of the day, these are all unknowns until it is a shipping product and has been QAed on some different machines. My suggestion would be to not speculate how high/low it can go until it is shipping. In the mean time, focus on what it can do that other cards can’t. It fits right in the middle of the product line perfectly. All the i/o and then some of an LH, all the conversions of a Kona3. Depends on what YOU need to do with it. Any way you look at it, AJA has a solution.

—
—
-Mike