Mountain Lion vs Lion video input issues when running QC in 64bit mode?

cwilms's picture

After some unexpected downtime due to some MacBook Pro hardware issues I am back into trying to resolve a video input problem. I'm really hoping someone can provide some insight into what I'm experiencing.

In the Summer of 2012 I had OSX 10.7.3 running QC 4.5. I was able to use both the Native video input patch and the FV Video input patch in 64bit mode with positive results with the Matrox MXO2mini. The inputs are also available when running QC in 32bit mode.

I have since upgraded to 10.8.3 running QC 4.6. I am unable to get either the Native input patch or FV Video input patch to see a video input source using either Matrox MXO2mini or the AJA ioexpress in 64bit mode. If I run QC in 32bit mode the inputs are visible and work however some of my 64bit plugins aren't available then.

I get the same results in QuicktimeX when selecting an video input source.

Any idea why 64bit mode in Mountain Lion loses this capability when in Lion it was working just fine??? I know the VideoTools 3.2 plugin bring BlackMagic support to the table now. Does Blackmagic do video input different that Matrox and AJA? If not is there a way to bring AJA ioExpress support to the VideoTools plugin?

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

smokris's picture
Re: Mountain Lion vs Lion video input issues when running QC ...

I can't speak to the issue with the built-in video capture patch, aside from confirming that QC's built in video capture has long been flaky in 64bit mode.

I know the VideoTools 3.2 plugin bring BlackMagic support to the table now. Does Blackmagic do video input different that Matrox and AJA? If not is there a way to bring AJA ioExpress support to the VideoTools plugin?

VideoTools interacts with Blackmagic devices directly using the Blackmagic SDK (bypassing QuickTime and AVFoundation), and VideoTools 2.3's Blackmagic Capture patch only supports Blackmagic devices. Since we're focusing our development resources on Vuo, we don't have the capacity to add major new functionality (like supporting Matrox or AJA devices using their respective SDKs) to Kineme products at this point.