QTCaptureDevice gives different inputDevices

Scripting Forums AppleScriptObjC and Xcode
#1

Hi,

I’m trying to get a simple device recorder up and running. I have a working version in Objective-C and wanted to translate it into AppleScriptObjC in order to better learn AppleScriptObjC.

I noticed that when I call:

	
NSArray *inputDevices = [QTCaptureDevice inputDevices];
NSLog(@"inputDevices=%@",inputDevices);

I get


inputDevices=(
    iMic USB audio system,
    Built-in Input,
    V2U13724
)

However when trying this in with AppleScriptObjC


set videoDeviceList to current application's QTCaptureDevice's inputDevices()
log (videoDeviceList)

I get


(
    "Built-in Input",
    "iMic USB audio system"
)

The weird thing is if I add the Objective-C code as the parent class I also get different inputDevices…
Am I missing something or is this an issue where I will have to stick with Objective-C?

//MSFcripter

#2

I’m not sure why you’re seeing that difference – I get the same thing whether I do it with your Objective-C code or the ASOC code. I get this:

Ric

#3

Played with it again today… no success

Could it be something concerning non-default devices. The device I’m not seeing in ASOC is a VGA2USB grabber - even though I see it in ObjC. Doesn’t sound reasonable, but well…

Will have to check this on another mac and report back…

//MSFcripter

#4

ok… so far what I have figured out, this seems to be an issue with 32-bit and 64-bit and the epiphan grabber i guess.

If I set the active architecture for building in XCode to i386 (Debug | i386) I see

2011-05-02 13:06:42.466 Lecturecast-Unit[53568:a0f] mifeurst: inputDevices available:(
    "iMic USB audio system",
    "Built-in Input",
    V2U13724
)

If I set it back to x86_64 (Debug | x86_64) I see

2011-05-02 13:06:27.685 Lecturecast-Unit[53503:a0f] mifeurst: inputDevices available:(
    "Built-in Input",
    "iMic USB audio system"
)

I checked with epiphan.org for their latest driver http://www.epiphan.com/products/frame-grabbers/vga2usb/download/

Their latest driver is stated as

Is this a dead end? QTKit issue, vendor issue… Obviously I’m going to stick with 32-bit, however providing 64-bit would be great.

//MSFcripter