Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Matrox MXO and MXO2 test

Kaku,

How does MXO2 LE max help in a FCP environment. I have just purchased and set up tonight, i have dropped some H Proxies onto the timeline and they don't play smooth at all, very choppy.I thought the MXO was supposed to help with this? I have 4tb raid system, and to be hinest my proxies play no differently with the MXO on. What are the benefits of this system for RED users?

many thanks
 
MXO2 does not assist in playing proxy files any smoother or better. It is merely an I/O device. It allows you to capture or output video using the device as a conduit. It is possible that it will slow down video operation of video clips if you are not using the proper system (fast hard drives, fast processor, RAM, etc..) There is a MAX version of the MXO2 that does accelerate H.264 encoding.. Maybe this is what you are thinking of. I'm interested in buying an MXO2, but I only need it for outputting video via HDMI (10-Bit)..
 
Jason,

With my experience of using Multibridge Pro and other cards for the long time with the proxies, comparing to that working with 1k size proxy on MXO2 with RED 1k output (currently only for 23.976 and 25) does make the proxies play back smoother scale up to HD because of its hardware scaling ability.

Working with proxies larger than 1K on FCP, from my experience, not really practical because of the performance. Playing back with 1K proxies, MXO2 plays back without stopping and less flickers comparing to playing back with Multibridge Pro.

I specifically asked Wayne Andrews to use hardware scaling feature work for R3D footage and that is what he provided to us. 29.97 support is coming very soon after NAB.

If you have more questions and going to NAB, ask Wayne at Matrox booth about it.
 
i think something is going wrong here. I treid to render out to H264 1080 a small section -5mins- of footage from a 2K timeline, it was going to take 1hr 20mins.? using the mxo2 le.
 
Robert,

The part that Mac has to process R3D (which we call R3D debayering I suppose) is handled by the CPU unless you have the RED Rocket™. So MXO2 LE Max COULD BE helping to process to transcode from QT (after it was debayered) to H264, but the debayering is taking the most time.
 
I will try to see if Max will help transcoding directly from RED software, even with RED ROCKET.
 
I have red rocket, but i can't really see the benefits of having the MXO2 LE. I thiught it was going to be more useful than it is. Transcodes out don't seem to be any faster than normal in fact they seem slower.
 
I have RED Rocket™, but i can't really see the benefits of having the MXO2 LE. I thiught it was going to be more useful than it is. Transcodes out don't seem to be any faster than normal in fact they seem slower.


The only benefits at the moment (as i've seen) are when transcoding using MAX to H264....Rocket card has not benefit as far as i can tell NOR do i know how it could be utilized to benefit using MXO2 LE with MAX.....at least i cannot think of how it could be utilized.
 
I have RED Rocket™, but i can't really see the benefits of having the MXO2 LE. I thiught it was going to be more useful than it is. Transcodes out don't seem to be any faster than normal in fact they seem slower.

If that is the case the H.264 export of REDLINE is not using the MAX technology. I will report this to Matrox and ask them to work on it.
 
Yes. At the end I'm using the MXO with FCP outputting to digital cinema desktop preview or raw. In this way I can feed two apple cinema display and one SDI JVC broadcast monitor. I know it's not ideal but it works for now.
Hie lucas maybe you or Kaku have a clue.
Having some trouble with the SDI out of the MXO2LE who feed a JVC TM-H1750C HI RES.
Either in color and FCP the JVC CRT monitor show me really dark footages compare to the LCD calibrated 2.2 of the macBookPro (the shift difference is huge)
Same shift difference if I calibrate a screen with hdmi control.
Wich make me thinking maybe matrox behave like I was working on gamma 1.8 and dark the footages on purpose.
if I push the JVC brigntness at +16 it seems similar to the macbook pro LCD.
By the way running snow leopard Fcp 7.0.2. with Nvidia card and last matrox firmware 1.9.1
Any clue?:mad2:
Cheers to all
 
I'm using MXO2LE on my private Mac Pro with TVLogic LVM173W (HDSDI) and Sony Bravia (HDMI) and they display normally.

To check what the host application is outputting through the video I/O, I look at the scope in Apple Color and check with the histogram on the LVM-173W or Blackmagic Ultrascope and they are identical.

The video hardware does not set gamma unless if there's a feature, basically they just directly output whatever the host application is outputting.

I do have a 9 inch HD CRT from JVC and notice some formats display awkwardly (not only with Matrox I/Os but with Blackmagic Multibridge Pro and MOTU V4HD, so maybe JVC's input is not that robust to various formats?

You can try first, to put your color profile on your MBP to the default. The default is gamma 2.2 and 6500K on Snow Leopard so basically won't be that much off. Then compare the pictures on the MBP and your JVC CRT.

MXO2LE is pretty much straight forward, so first go back to the basic and build your references from there. I will be here to help you more.
 
Thank you Kaku for your time,
I did set the lcd back to default, and the shift difference between crt (too much black) and lcd is still there.
I calibrated the jvc using the calibration color bar (with it's BW and blue fonction) brightness are now at +23 but footages look pristine in CRT now! :emote_headwall:
Any clue?
Regards
 
When any video I/O is connected to monitor via digital connection, settings should be very close to the default, so there's something wrong there.

Can you please let Matrox support know about this?

One more clarification, what is the source of the colorbar are you using? Is it the one in the video generator tab? Or, still file from somewhere else. If in case of still file, then IT IS probably imported as gamma 1.8 instead of 2.2, so you have to go to its property to set it to 2.2. Maybe that is throwing you off.
 
MXO2 version 2 for MacOS is available on the Matrox Website.

Now MXO2 series (non-mini) can output 23.976p (finally!) and sync to 23.976 external clock.
 
Back
Top