Hey Marianna,

Thanks for keeping us in the loop. It's understandable that with the move to open architecture in MC6 the way the MXO2 mini was accessed had to change significantly to fit in to the new approach, and that has inevitably led to problems.

I'm back on MC5.5 until a solution is figured out. Ultimately that's not a huge issue as I'm really happy with the MC5.5/MXO2 mini as a system, it's just a pity I don't get to take advantage of the additional features of MC6.

If it isn't resolved before the next paid upgrade (MC6.5 I presume), I may be in touch to get a refund on the upgrade I paid for but can't use due to this issue. But in the meantime I'm going to keep hoping there's a combination of a point release and driver update that fixes it so I get to use MC6.

Vilem, I assume that You have a tower case, the video card should be in the PCIe slot 1, which is the top one, read the motherboard manual to see which expansion slot works at which speed in a two or three video cards SLI setup, avoid fitting the Matrox card in one of the slots that slow down in SLI as they surely share bandwidth with the PCIe slot 1, and experiment with the remaining slots.

My new computer is almost ready and I fear the test drive time, my current system works extremely well, as of today I may be participating in the wrong thread, but I could rejoin the sluggisness club anytime soon...

Marianna your "true girly girl who just loves the clothes" is the post of the month, thank You for making me laugh!

Marianna:

Folks..........

The basic architecture of MC 6 is completely different than that of the 5.5 and earlier code base. Most notable is the 64 bit architecture and the Open I/O.    In 5.5 for example, the MXO2 was using the DIO interfaces, similar to what Adrenaline and Mojo SDI used. 

But Open I/O uses the same interfaces as Nitris DX.   

The problem is that during normal scrub, color correction, and trim modes, we send a single frame to tell the I/O device to stop.  Some respond immediately to that stop command and some take a little longer.  We do have a long-term architectural fix but it won’t be coming soon which is why Matrox has been tweaking their driver to provided those with the MX02 better performance.  

Marianna

Marianna, do you have any feel for if this is also a problem with the Intensity Shuttle USB 3.0 and Motu HD Express?

I was wondering if I should sell my matrox just to use Resolve light anyway. So, now knowing that it will be unusable for the time being, I just wanted to ask if there is a list of the current affected video boards. Which one of the BM cards works with MC6 (no sluggish issues) and resolve light?

Has there been any progress on this problem?  I installed the latest drivers but colour correction is still nearly unusable with the Matrox.

Not seeing that here, what do You mean by latest driver? Please provide the version number.

MXO2 mini unified driver 7.1.0.1294 on Media Composer 6.03.2 is pretty rock solid over here. No issues thus far and with color correction.