Xcode 4.3 Quarz Composer there are no Video Input Devices!

Justus's picture

I use QC for rendering my live Video in Qlab. It works fine on my Macbook Pro. On my new Mac Pro i have installed Xcode 4.3 and Graphic tools for Xcode with QT inside. My System is Lion 10.7.3. I have two Video Devices Blackmagic Intensity and a Usb Card. Both Cards donĀ“t recognized from QC.Is there something I have to Install.

Thank for Help

Justus

cybero's picture
Re: Xcode 4.3 Quarz Composer there are no Video Input Devices!

A] Have you mailed QLab about this on support at figure53 dot com ?

B] Have you mailed the Mac Support site about this ?

c] What do you mean by 'with QT inside'?

D] Have you enquired of BlackMagic's support about this problem you've encountered ?

E] Have you tried downloading and installing BlackMagic's beta driver ?

F] What is the USB card?

gtoledo3's picture
Re: Xcode 4.3 Quarz Composer there are no Video Input Devices!

The Blackmagic won't show unless you do a "get info" on QC (eg., QC's icon, in Finder), check off 32 bit, and open it back up. AFAIK, there is no support in 64 bit Quicktime for recognizing that stuff, so you have to force the 32 bit. That said, I have not tested this in Lion, only Leopard and Snow Leopard.

I've recognized generic usb cards in 64 bit when they're supported on mac, but have had some issues with cards that aren't explicitly supported.

Justus's picture
Re: Xcode 4.3 Quarz Composer there are no Video Input Devices!

Thanks for Help

I change Quarz Composer to 32bit and I can see the possibilities of my Black Magic Intensity. I use as Input signal Pal/Ntsc ( Camcorder Out is DV Signal via Composite )but I cant get a preview of my Live picture . I also try the Beta Driver From BM. If I use a USB-Video-Card too my Quarz Composer is Crashing down.

Thanks Justus

gtoledo3's picture
Re: Xcode 4.3 Quarz Composer there are no Video Input Devices!

Opening up Console.app (in your Utilities folder) might shed some light on what exactly is failing, when.

I have only tested that (blackmagic w/ 32 bit Quicktime) in 10.6.

I have to say - I don't think that 10.7, as a whole, is a suitable operating system for any kind of professional deployment, besides any quirks with QC. The system is a hog, slow, and buggy; it really shows itself in a case like QC, where people can program things that push the edge of performance anyway.

For instance, this issue is truly a Quicktime issue (that of only QT 32 bit having support for this). Through all of the incremental updates to OS X during 10.6, this wasn't fixed, and now, with a whole other OS version, it may be not only unfixed, but broken with the 32 bit variant. This is Quicktime, which isn't exactly an unknown Apple tech. I think that software dev at Apple is basically spinning out of control.

I'd check the video settings input/output settings again though, try some different permutations, maybe one or more will work.

Sorry, doesn't help your scenario much... I guess what I'm saying is, the answer may be in you programming something that works around something that Apple has broken. I'm just trying to give some context for why you're encountering this problem.

cybero's picture
Re: Xcode 4.3 Quarz Composer there are no Video Input Devices!

It does seem pretty ludicrous that having gotten their own hardware to work in PhotoBooth and other Apple applications like iChat, that Apple simply hasn't seen fit to make their own QuickTime framework truly functional within applications that seek to exploit that framework. Not fit for professional deployment does seem quite an apt summation. As for Lion being buggy and slow,that is sadly evident in the way the Finder can take ages to list even short directory listings.

It seems to me it has got to be sorted out, however, I haven't heard any encouraging remarks regarding this from any online leaks of Mountain Lion related postings, which obviously enough, I can't say any more about on this forum. It seems to me that Apple are only pushing Mountain Lion in reaction to the forthcoming release of Windows 8. IMHO a poorly judged move when so much obviously still needs to be fixed in Lion itself that hasn't, so far as I can tell, been addressed to date in Mountain Lion.

All in all a result of Apple's focus shifting over to iPad | iPhone | iTouch devices, from which they now derive the vast majority of their revenue.