Beatlenyc
Forum Replies Created
-
Hey Randy,
Just saw the post on Matrox’s site and apparently they fixed the bug with ATI cards last October, so you should be ok. Let me know what you think about your MXO. I was thinking I might wait a bit and see if BMD or AJA come out with a card that works with laptops.
Laura
-
I don’t know why the link doesn’t work. But you can just go to DV.com and search for MXO ATI. The first hit is the article, which is really really interesting. I have a call into the Matrox folks now to see what they say about a possible fix. But if it’s not yet resolved, then it seems that the color translation to your LCD or CRT or anything else will definitely be off. And since this is at least 1/2 the purpose of the box, then…well, it may not be worth it. (fyi, as I was typing this, the Matrox customer care guy called me and said they would respond to my posting about this on their Pre-Sales forum.)
I also have an email into the Black Magic folks to see if they’re coming out with any MBP capable cards any time soon. I plan to email AJA as well (the Kona card makers) but haven’t quite gotten that far. This HDV monitoring issue has already eaten up 2 1/2 days this week – so I really need to get back to work! Ugggh!!
Last, but not least, I’m thinking about other possible monitoring solutions. I have an M25U deck and wondering if using firewire into that and then component into the Dell would get be something better than pure DVI out to the dell. IF any one has any expertise with this, I’d be grateful to hear their advice on this.
Laura
-
The only problem with MXO, which I’m just starting to learn about, is that it doesn’t work with ATI video cards (which are currently what the MacBook Pro ships with). I am trying to work out a solution to this myself. (For details on why MXO is incompatible with MBP, see https://www.dv.com/features/features_item.php?articleId=193104902). The long and the short of it is that MXO isn’t able to get the YUV signal directly from that ATI card. According to the article, the Matrox folks are aware of this and are working on a solution….
If I find anything else out I will let you know.