Testing the driver at the moment, worked all day, it's faster and smoother than before, trim works as it should, but the gang issue is still there.

luca.mg:

 but the gang issue is still there.

Luca, did you notice that other post I wrote where I told that the gang issue also was without any external hardware connected .

I just rolled back to MC5.5 and Matrox drivers 5.5, definitely a lot faster than MC6.0.1 and Matrox drivers 6.0.1 beta. Not just my imagination.

Testet MC 6.0.1 with Matrox MXO2Mini Driver Vers.6.0.1.beta, DNxHD Material (115, 175) in a 1080p24 Project.

I'm glad It's there and I would summarize it's "50% better towards MC5 performance" (I know thats a nonsense number but to find a word)

- scrubbing the Timeline is quite better in this DNxHD Project, lets say: it is now really usable for me (although I hope for more)

- trimming (dual roll) is also better (I think) but still a little pain to work with, laggy Picture refresh and this is essential for that tool to beeing useful

So it's kind of halfway there for me. I'm also considering rolling back to MC 5 or 5.5 with MXO 5.5 Drivers because fast trimming - I really need that. By the Way: Disabling the Preview (blue Monitor) does not help in trim mode for me.

Another wish for an ideal world:

I appriciate the Opennes of Avid for 3rdParty Hardware -that's a big thing, thanks for this!

In the ideal world I would not have to double post and double read in 2 different support Forums (Matrox and Avid Community) for getting/giving Solutions. And one points to the other. In such a world only _one_ "Avid Mediacomposer with Matrox(or AJA/Blackmagic/Motu...) Hardware" Forum would exist to bundle all inputs. How about mirroring such a Forum Channel with all its postings on both Avids and the Hardware Manufacturers Sites? One could forward the author from either side (site) to that actual Forum. Of course Forum Moderators from both Communitys/Manufacturers should be active there but... wouldn't that be cool?

The update to Avid didn't solve any issues with slow performance and the MXO2 mini. I have also tried the Black Magic intensity pro and it too is much slower then without monitoring. This problem is on the Avid side, that is my guess, two companies and two different hardware systems, but the same kind of slow performance in the same situations.

I would suggest Avid to try v5.5 oc MC together with the 5.5 Matrox drivers and compare them to MC6.0.1.
64 bit doesn't mean much if this error persists.

I installed the beta drivers. It seems that the beta version of the driver slightly faster response (still below the speed of the MC5). But when working in the project 25iPal (material: 420 DV25, MPEG 50) occurs when using "JKL" keys to freeze the image on the PC monitor. Whenever such as "L" click "J" will be freezing. I have to click first "K" to avoid the image freezes.
William

Hi William, I have no problem with JKL play at various speed; as I reported earlier on this thread moving the Matrox card to a different slot improved performance, any chance You can try doing that?

luca.mg:

Hi William, I have no problem with JKL play at various speed; as I reported earlier on this thread moving the Matrox card to a different slot improved performance, any chance You can try doing that?

Thanks for the tip Luca.

In the coming days I'll run some tests. The second suspect the HDD has been connected by USB2. Usually clipping the disk connected via e-sata. I'll report here.
W.

I wonder why you all are up to make so many compromises. Fact is, the mxo works in MC5.5 like a champ and in MC 6.0.1 not (regardless of a certified system or not)!

Ok there is a beta driver from matrox, but the results are not comparable to MC5.5.

I think it`s up to AVID or to Matrox (i don`t bother who is responsible for that) to bring out soon a patch, which will solve this problem completely. The last patch release in january was more than poor. Since three months the sales promotion of AVID tells that there will be a true benefit working with MC 6.0 and 3rd party hardware. Now it`s time to keep the promise.

Yep I hear you.  I installed Matrox's beta driver and couldn't tell any difference.  Just as I couldn't tell any difference after installing the 6.0.1 update/patch.  These two seem like placebo-software to me, if you believe enough, you seem to notice as slight improvement, but I didn't unfortunately.  But I'm sure there will be a solution eventually.

Sorry to disagree, performance with the beta driver is excellent here, but I'm running an MXO2 (non mini), I can't compare with MC 5.5 as the box wasn't supported, but it runs very well indeed on my underpowered system.

...when selling v6.5 at the latest. Unfortunately i own two versions of 6.0 and can`t use them up to this release.

Vilem:

luca.mg:

Hi William, I have no problem with JKL play at various speed; as I reported earlier on this thread moving the Matrox card to a different slot improved performance, any chance You can try doing that?

Thanks for the tip Luca.

In the coming days I'll run some tests. The second suspect the HDD has been connected by USB2. Usually clipping the disk connected via e-sata. I'll report here.
W.

I did some tests and it seems that the problem of "JKL" nothing to do with MXO2. Freezing is manifested is disconnected and uninstalled MXO2 and projects with the media to e-SATA (I'd think the solution of other problems, noticed the problem JKL). I tried to move into the second graphics card slot, but without result. We can only wait for the patch functional MC6.
W.

luca.mg:

Sorry to disagree, performance with the beta driver is excellent here, but I'm running an MXO2 (non mini), I can't compare with MC 5.5 as the box wasn't supported, but it runs very well indeed on my underpowered system.

Luca,

Did you ever experience what the MXO2 mini ran like under 5.x, or is this your first experience with third party hardware with Avid? I can tell you, the Matrox under 5.x felt as fast and fluid as any Avid hardware, including the Ntris. But it's unusable under 6.x thus far. Shame.

Chris

I wonder if it is not something to do with the way Avid caches data and the way information is used in the buffer. There is only 2G of memory being cached while playing timeline. When I copy files this goes up to 8G.

Once I play the timeline once most the problems not all seem to disappear with the BM Multibridge Eclipse.

I have also posted this in the white screen thread.

Radman.