-
FCP 7 XML, CS5.5, Lion, Matrox MXO2 – Premiere still just stops working
I’ve been importing XMLs from FCP. Nothing complex. Cuts, dissolves, jpegs of ProRes 720p footage. With CS5 I could rarely get it to import, and usually it crashed upon trying to play. At least now in CS5.5 It will work for maybe 5-10 minutes until suddenly there’s no output from the matrox. No output on the computer screen either. I can open clips but they’re just black with no sound. Scrubbing does nothing. Quitting doesn’t completely work either. I end up having to force quit and relaunch.
I’ve even downloaded the new matrox 2.3.2 Lion drivers for CS5.5 and FCP 7 running on lion. But nothing.
Anything I can try? It’s on an older Mac Pro 2007 with 7 gig of RAM.
-
5 Replies
-
The issue you’re describing with CS5.5 and the Matrox player is not a PremierePro issue directly, it’s an MXO2 Player issue.
We have an MXO2 in our main suite here and whether it’s CS5.5 on Lion or CS5 on Snow Leopard the behaviour is the same. Eventually the player will lockup and display the behaviour you describe; no playback, no output (even to computer monitor) and sometimes a restart of the app won’t fix it.
Matrox says to trash your Premiere Pro preferences (and maybe even uninstall and re-install the driver) and you might want to try that a few times – but considering how this issue constantly crops up, that kind of ridiculous maintenance (which they suggested equally frequently with FCP to be fair) is indicative of their own driver issues.
In my own case I have to, when working with premiere pro, start a sequence that’s not using the MXO2 player, edit away, and then copy the sequence into an MXO2 player sequence to hope for playout or monitoring. When NOT using an MXO2 sequence, the freezes, stalls, and diplay issues go away and Premiere Pro works very well. The sequence, once copied or imported to an MXO2 sequence is a gamble for playback.
I’ve been incredibly displeased with Matrox over my two years with the MXO2 because of constant issues like this. It’s too bad, because the MXO2 series had (and with the as-yet-unreleased Thunderbolt adapters still has) a lot of promise – however, it has yet to really live up to that promise in a reliable, consistent way.
Good luck!
—
There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger -
Your experience is the same as mine. But my guess is that Adobe and Matrox are partners in some sort to make this happen. They need to get together and make it work or quit promoting it. I’d like to add Premiere to the arsenal as a contender for being my editor of choice. I like the integration with AE for sure, and I already have CS5. I’d rather not dish out $995 for Avid, but Avid is solid on the MX02 mini.
I too had to copy the sequence into a matrox player sequence to get it to work. But yes, it only works for a short time and then the connection is lost. The same occasionally occurs in FCP, but it’s usually related to waking from sleep. Otherwise the box is solid on FCP. It has it’s troubles with AE too.
-
Hi Bret,
Looks like we’re in exactly the same boat.
Here’s to hoping we get a fix!
—
There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger -
It’s been like this about a year for me. I don’t think anyone really cares to tell ya the truth.
-
The Premiere Pro CS5.5 (5.5.2) update fixes some problems with instability with third-party I/O hardware, including Matrox hardware. See this page for details:
https://adobe.ly/premiere_pro_552
———————————————————————————————————
Todd Kopriva, Adobe Systems Incorporated
Technical Support for professional video software
After Effects Help & Support
Premiere Pro Help & Support
———————————————————————————————————
Reply to this Discussion! Login or Sign Up