Cineform Codec+Output card compatability

[Mikael Couderc]

Hi all,
I've been looking at all the posts I could find on the matter, here and on other forums, but couldn't find enough info on specific questions with regards to Cineform and output cards.
Thing is, I guess I (and probably a few others, judging by the amount of posts by confused users) would greatly appreciate a recap.
Sorry if this has been covered anywhere before...

I need a card that will let me output the video signal to an external monitor (Hdmi) for final grading.
There seem to be a few that claim to do just that, and the most popular solutions (and the ones I'm currently looking into) seem to be MXO2 mini, Aja Xena LHi, and Blackmagic intensity and decklink flavors.
So far so good. What I'm having trouble grasping though, is how do they integrate into my workflow in terms of Codecs supported.
From what I understand, some of these cards only work with specific projects and specific codecs inside of PPro CS4, while others are codec independant.
So, how does the Cineform codec integrate into all that? What card is Cineform the most compatable with?
Thanx for clarifying that for me...


Edit: I'm referring to a quote from David some time ago:

http://www.dvinfo.net/conf/cineform-...-cineform.html

'We support

AJA HS
AJA LH
AJA LHe
AJA 2Ke

adding right now

AJA LHi
AJA ioExpress

To use either Matrox or Blackmagic devices you need to use their editing modes, and we have not profiled the performance as it will not be using the Prospect accelerator. We have confirmed under CS4 than both MXO2 and Intensity to playback CineForm AVIs in either edit modes.'

and this one:

http://www.dvinfo.net/conf/cineform-...intensity.html

[David Newman]

The CineForm codec works with all of them in the native edting modes AJA, BM, Matrox MXO2.) AJA and Blackmagic cards work natively under First Light. AJA cards works natively with Prospect HD's edit mode in CS3. CS4 support coming, likely AJA + BM around the same time as so much had to changed to support CS4, the limiation that made use AJA only is going away.

[Mikael Couderc]

Thanx for answering.
Could you just elaborate on a few points please?:

Originally Posted by David Newman

The CineForm codec works with all of them in the native edting modes AJA, BM, Matrox MXO2.)

What do you mean by 'native'?
Does that mean I will only get an output IF I use Cineform in a brand specific preset? (ie: I will only get an output on a Matrox card if I use Cineform in a Matrox preset?)
Is this even true for the Xena cards?

Originally Posted by David Newman

AJA and Blackmagic cards work natively under First Light

So MXO2 doesn't work at all? Or is it limited in some way?

Also, to finish with, what would the Xena cards bring that the others wouldn't?

Thanx for your answers.

[David Newman]

AJA, Matrox and Blackmagic all have their own editing modes (presets), for CS3 and CS4 and CineForm AVI/MOVs work fine in those modes -- that is all I meant by "native". Only AJA Xena is supported in CineForm editing modes under CS3 -- there is an advantage to this, mainly more speed. Matrox doesn't has an SDK MXO2, so no third party can integrate that product.

[Mikael Couderc]

Ok, I get it now!
So in a nutshell, all of these cards will give me an output with Cineform encoded material providing I use their respective presets (in CS3 and CS4), BUT only Xena under CS3 will allow me to use a Cineform prospect hd preset. CS4 support for prospect hd presets is coming for AJA and BM, but not for Matrox (any chance this will happen some day?)
Correct me if I'm wrong...
Thanx again!

[David Newman]

There is chance the MXO2 will be supported, that depends on Matrox first, as today it can't be done.

[Tom Santopolo]

Any word from Matrox on this? I purchased the MXO2 mini like a dummy and now its useless to me - I sold my intensity.

[Tom Santopolo]

And I posted the question on the Matrox forum weeks ago and they don't respond.

[David Newman]

Tom,

No word to report, it is new market for Matrox as they have not typically built I/O cards that would be suitable for third party implementation. We do hope they see value in supporting third parties using MXO2.