in case someone is wondering about support of the Matrox Mini in MC 7 ... so far the combo runs trouble-free on my machine.

OS X 10.8.4 & Matrox 3.3 (3.3.0.0067)

I'm reporting the same, on just super-basic, "does it work?" testing on the MXO2 with MAX.  No issues to report.

Matrox says they're working on official support, hoping for this summer.

tho_wi:

in case someone is wondering about support of the Matrox Mini in MC 7 ... so far the combo runs trouble-free on my machine.

OS X 10.8.4 & Matrox 3.3 (3.3.0.0067)

Very interesting. Is that 'works' in the sense that the MX02 box works with MC 5.5? I've never used the MC 6 upgrade I bought or bought the MC 6.5 version I trialed because neither 'worked' to the extent I could actually edit with the MX02 box attached without unacceptable lag when trimming, hopeless performance when using colour correction and all too frequent crashes. 

Personally I like 5.5 - stable and responsive are very good attributes for editing software - but there is a lot to like in MC 7 as advertised. Experience of the two intervening versions makes me wary of even investing my time in the clean install needed to trial it as well as a degree of reluctance to part with the money when I've had no use at all from the last upgrade I paid for. 

The problem of passing MC 7 bins back to projects based on earlier versions is a further disinsentive. My home system is most regularly a mirror of the studio based Avid in use on whatever project I'm editing. It's not good for me if I can't add the work done back home to the main version of the project. Am I alone in wondering why there is apparently no 'save as Version X.X compatible bin' option in MC 7? One of the great glories of Avid and it's principle distinguishing features is the ease and reliability of moving projects / bins / media between systems. 

Apologies, this post has rather strayed off topic.

No system in my sig but it's a 2x6 core MacPro, a Proavio raid attached to an Atto R380 card an MX02 Mini with up to date Matrox drivers installed. You can probably guess it's running MC 5.5 (well 5.5.3.7, I'm not a total luddite)

noodleinsoup:

Very interesting. Is that 'works' in the sense that the MX02 box works with MC 5.5? I've never used the MC 6 upgrade I bought or bought the MC 6.5 version I trialed because neither 'worked' to the extent I could actually edit with the MX02 box attached without unacceptable lag when trimming, hopeless performance when using colour correction and all too frequent crashes.

That said I do not output Audio through HDMI (I use the cinch output) and I also don't use the internal calibration tool provided by Matrox (which is really extremely rudimentary with it's old school 8bit apporach and therfore really rediculous ... to say the least). I also have to admit I am only referring to video output... not to video-recording through the Matrox Mini.

hmmm... that's very interesting... how do you output you audio then? no sync issues?

When you say "cinch output" what are you referring to?  Are you outputting audio from a seperate output device?  Can this be done in MC 7?  If so...would love to know how.  I have a Apogee Duet 2 that I would love to use for just audio output but I hear Avid doesn't support that due to the possibly of sync issues.

Noodleinsoup summed up my concerns exactly. I have had the same problems with Matrox and every version of MC 6 and am quite reluctant to move to 7 until I'm sure it's worth it . . .

Eduardo Serrano:

hmmm... that's very interesting... how do you output you audio then? no sync issues?

cycledfilms:

When you say "cinch output" what are you referring to?  Are you outputting audio from a seperate output device?

well, I simply use the cinch output of the Matrox Mini. It's in sync (at least as good in sync as output through HDMI...).

I don't know whether or not this improves trimming performance ... however this is how I connect the Matrox Mini's outputs...