| |||
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
On 26/05/2008, at 11:32 PM, Steve Sisak wrote:
This behaviour confused me too, but the "workaround" (or maybe this is how Apple envisaged it to be used?) is to do something like this (I discovered this in a post on this mailing list): NSDictionary *videoOutputSettings; videoOutputSettings = [NSDictionary dictionaryWithObjectsAndKeys: [NSNumber numberWithInt:ImagePixelWidth], (id)kCVPixelBufferWidthKey, [NSNumber numberWithInt:ImagePixelHeight], (id)kCVPixelBufferHeightKey, [NSNumber numberWithUnsignedInt:kCVPixelFormatType_24RGB], (id)kCVPixelBufferPixelFormatTypeKey, nil]; [mCaptureDecompressedVideoOutput setPixelBufferAttributes:videoOutputSettings]; QTKit then requests frames from the corresponding video input device at the "best match" to the video settings you used for the output. The logic of changing camera settings by changing the output still has me scratching my head, but that's how it's done, at least for now. Nick |
_______________________________________________ Do not post admin requests to the list. They will be ignored. QuickTime-API mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/quicktime-api/email@hidden This email sent to email@hidden
| Home | Archives | FAQ | Terms/Conditions | Contact | RSS | Lists | About |
Visit the Apple Store online or at retail locations.
1-800-MY-APPLE
Contact Apple | Terms of Use | Privacy Policy
Copyright © 2007 Apple Inc. All rights reserved.