July 2010 - Pro-apps-dev - lists.apple.com

Re: 3rd party download pages
by Charles Meyer 13 Jul '10

13 Jul '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

Re: 3rd party download pages
by Andreas Kiel 13 Jul '10

13 Jul '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

Re: 3rd party download pages
by Andreas Kiel 13 Jul '10

13 Jul '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

Re: FxPlug dealloc Crashing in Motion
by Darrin Cardani 12 Jul '10

12 Jul '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Bob, Darrin On Jul 12, 2010, at 3:28 PM, Bob Currier wrote: I've got an FxPlug that's working fine in FCP, but when used in Motion it crashes whenever dealloc is called. The relevant crash log is below. -- Bob Process: Motion [82906] Path: /Applications/Motion.app/Contents/MacOS/Motion Identifier: com.apple.motion Version: 4.0.2 (726) Build Info: Motion-7260000~10 Code Type: X86 (Native) Parent Process: launchd [227] Date/Time: 2010-07-12 15:25:09.786 -0700 OS Version: Mac OS X 10.6.3 (10D573) Report Version: 6 Exception Type: EXC_BAD_ACCESS (SIGBUS) Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000020 Crashed Thread: 0 Dispatch queue: com.apple.main-thread Application Specific Information: objc_msgSend() selector name: release _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/dcardani%40apple.com -- Darrin Cardani dcardani(a)apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… It's crashing during tearing down of the object which handles parameter communication between your plugin and the app. My guess is that you're deallocating some piece of parameter data, and then we're trying to do the same. I'm not sure why that would work in FCP and crash in Motion, but you could just be getting lucky, if that's what the problem is. (On the other hand, it's possible that we're deleting something we shouldn't because you've already deleted it. But I'd think we'd have run into this before if that were the case.) Are you running with Zombies enabled? If not, you should try that, and see if the console says anything about a zombied object being double- deleted or anything like that. Actually, if the console already says anything, let me know that, too. If we can't figure it out that way, and you're willing to send me the plugin, I could see what I can find from this end. I've no-op'd the dealloc routine, and even removed it entirely, yet the crash still occurs. Although the crash is in Motion, and seems to be occurring after my plugin has been unloaded, no doubt it's something I'm doing wrong. Any ideas of how to proceed to locate this? I do have a number of custom UI params. Interval Since Last Report: 4098 sec Crashes Since Last Report: 1 Per-App Interval Since Last Report: 39 sec Per-App Crashes Since Last Report: 1 Anonymous UUID: 2E1CCFC8-421A-4B37-8270-7D6D9A3F92CB Thread 0 Crashed: Dispatch queue: com.apple.main-thread 0 libobjc.A.dylib 0x9861eed7 objc_msgSend + 23 1 com.apple.ozone.framework 0x009886de -[OZProPlugParmHandler dealloc] + 782 2 com.apple.ozone.framework 0x0097669c OZProPlugEffect::~OZProPlugEffect() + 924 3 com.apple.ozone.framework 0x008a9738 OZPasteEntry::~OZPasteEntry() + 152 4 com.apple.ozone.framework 0x008aa128 OZPasteList::~OZPasteList() + 88 5 libSystem.B.dylib 0x97b2d3bf __cxa_finalize + 208 6 libSystem.B.dylib 0x97b2d2d4 exit + 33 7 com.apple.AppKit 0x950bfcc2 -[NSApplication terminate:] + 1056 8 com.apple.prokit 0x001be0a3 -[NSProApplication terminate:] + 116 9 com.apple.motion 0x0000746c 0x1000 + 25708 10 com.apple.AppKit 0x94ec55c6 -[NSApplication sendAction:to:from:] + 112 11 com.apple.prokit 0x001be3b8 -[NSProApplication sendAction:to:from:] + 127 12 com.apple.AppKit 0x94ec5479 -[NSMenuItem _corePerformAction] + 435 13 com.apple.AppKit 0x94ec516b -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 174 14 com.apple.AppKit 0x94ec505a -[NSMenu performActionForItemAtIndex:] + 65 15 com.apple.AppKit 0x94ec500d -[NSMenu _internalPerformActionForItemAtIndex:] + 50 16 com.apple.AppKit 0x94ec4f73 -[NSMenuItem _internalPerformActionThroughMenuIfPossible] + 97 17 com.apple.AppKit 0x94ec4eb7 -[NSCarbonMenuImpl _carbonCommandProcessEvent:handlerCallRef:] + 336 18 com.apple.AppKit 0x94eb95f9 NSSLMMenuEventHandler + 404 19 com.apple.HIToolbox 0x94a500a9 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1567 20 com.apple.HIToolbox 0x94a4f370 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 411 21 com.apple.HIToolbox 0x94a71b55 SendEventToEventTarget + 52 22 com.apple.HIToolbox 0x94a9e147 SendHICommandEvent(unsigned long, HICommand const*, unsigned long, unsigned long, unsigned char, void const*, OpaqueEventTargetRef*, OpaqueEventTargetRef*, OpaqueEventRef**) + 448 23 com.apple.HIToolbox 0x94ac2e40 SendMenuCommandWithContextAndModifiers + 66 24 com.apple.HIToolbox 0x94ac2df5 SendMenuItemSelectedEvent + 121 25 com.apple.HIToolbox 0x94ac2cfa FinishMenuSelection(SelectionData*, MenuResult*, MenuResult*) + 152 26 com.apple.HIToolbox 0x94a92436 MenuSelectCore(MenuData*, Point, double, unsigned long, OpaqueMenuRef**, unsigned short*) + 454 27 com.apple.HIToolbox 0x94a91ba4 _HandleMenuSelection2 + 465 28 com.apple.HIToolbox 0x94a919c2 _HandleMenuSelection + 53 29 com.apple.AppKit 0x94eb2b3a _NSHandleCarbonMenuEvent + 285 30 com.apple.AppKit 0x94e876e6 _DPSNextEvent + 2304 31 com.apple.AppKit 0x94e86976 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 156 32 com.apple.AppKit 0x94e48bef -[NSApplication run] + 821 33 com.apple.prokit 0x001beab1 NSProApplicationMain + 326 34 com.apple.motion 0x000055de 0x1000 + 17886 35 com.apple.motion 0x00002746 0x1000 + 5958 This email sent to dcardani(a)apple.com This email sent to site_archiver(a)lists.apple.com

1 0

Re: FxPlug dealloc Crashing in Motion
by Paul Schneider 12 Jul '10

12 Jul '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Hi Bob, It sounds like an object is being under-retained, and dealloc'd before everything is done with it. If you run with NSZombieEnabled, you should see some console messages describing which object is being freed prematurely: http://developer.apple.com/mac/library/technotes/tn2004/tn2124.html#SECFOUN… - Paul On Jul 12, 2010, at 5:28 PM, Bob Currier wrote: > I've got an FxPlug that's working fine in FCP, but when used in Motion > it crashes whenever dealloc is called. > > I've no-op'd the dealloc routine, and even removed it entirely, yet the > crash still occurs. > > Although the crash is in Motion, and seems to be occurring after my > plugin has been unloaded, no doubt it's something I'm doing wrong. Any > ideas of how to proceed to locate this? I do have a number of custom UI > params. > > The relevant crash log is below. > > -- Bob > > Process: Motion [82906] > Path: /Applications/Motion.app/Contents/MacOS/Motion > Identifier: com.apple.motion > Version: 4.0.2 (726) > Build Info: Motion-7260000~10 > Code Type: X86 (Native) > Parent Process: launchd [227] > > Date/Time: 2010-07-12 15:25:09.786 -0700 > OS Version: Mac OS X 10.6.3 (10D573) > Report Version: 6 > > Interval Since Last Report: 4098 sec > Crashes Since Last Report: 1 > Per-App Interval Since Last Report: 39 sec > Per-App Crashes Since Last Report: 1 > Anonymous UUID: 2E1CCFC8-421A-4B37-8270-7D6D9A3F92CB > > Exception Type: EXC_BAD_ACCESS (SIGBUS) > Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000020 > Crashed Thread: 0 Dispatch queue: com.apple.main-thread > > Application Specific Information: > objc_msgSend() selector name: release > > > Thread 0 Crashed: Dispatch queue: com.apple.main-thread > 0 libobjc.A.dylib 0x9861eed7 objc_msgSend + 23 > 1 com.apple.ozone.framework 0x009886de -[OZProPlugParmHandler > dealloc] + 782 > 2 com.apple.ozone.framework 0x0097669c > OZProPlugEffect::~OZProPlugEffect() + 924 > 3 com.apple.ozone.framework 0x008a9738 > OZPasteEntry::~OZPasteEntry() + 152 > 4 com.apple.ozone.framework 0x008aa128 OZPasteList::~OZPasteList() + 88 > 5 libSystem.B.dylib 0x97b2d3bf __cxa_finalize + 208 > 6 libSystem.B.dylib 0x97b2d2d4 exit + 33 > 7 com.apple.AppKit 0x950bfcc2 -[NSApplication > terminate:] + 1056 > 8 com.apple.prokit 0x001be0a3 -[NSProApplication > terminate:] + 116 > 9 com.apple.motion 0x0000746c 0x1000 + 25708 > 10 com.apple.AppKit 0x94ec55c6 -[NSApplication > sendAction:to:from:] + 112 > 11 com.apple.prokit 0x001be3b8 -[NSProApplication > sendAction:to:from:] + 127 > 12 com.apple.AppKit 0x94ec5479 -[NSMenuItem > _corePerformAction] + 435 > 13 com.apple.AppKit 0x94ec516b -[NSCarbonMenuImpl > performActionWithHighlightingForItemAtIndex:] + 174 > 14 com.apple.AppKit 0x94ec505a -[NSMenu > performActionForItemAtIndex:] + 65 > 15 com.apple.AppKit 0x94ec500d -[NSMenu > _internalPerformActionForItemAtIndex:] + 50 > 16 com.apple.AppKit 0x94ec4f73 -[NSMenuItem > _internalPerformActionThroughMenuIfPossible] + 97 > 17 com.apple.AppKit 0x94ec4eb7 -[NSCarbonMenuImpl > _carbonCommandProcessEvent:handlerCallRef:] + 336 > 18 com.apple.AppKit 0x94eb95f9 NSSLMMenuEventHandler + 404 > 19 com.apple.HIToolbox 0x94a500a9 > DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, > HandlerCallRec*) + 1567 > 20 com.apple.HIToolbox 0x94a4f370 > SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, > HandlerCallRec*) + 411 > 21 com.apple.HIToolbox 0x94a71b55 SendEventToEventTarget + 52 > 22 com.apple.HIToolbox 0x94a9e147 > SendHICommandEvent(unsigned long, HICommand const*, unsigned long, > unsigned long, unsigned char, void const*, OpaqueEventTargetRef*, > OpaqueEventTargetRef*, OpaqueEventRef**) + 448 > 23 com.apple.HIToolbox 0x94ac2e40 > SendMenuCommandWithContextAndModifiers + 66 > 24 com.apple.HIToolbox 0x94ac2df5 SendMenuItemSelectedEvent + 121 > 25 com.apple.HIToolbox 0x94ac2cfa > FinishMenuSelection(SelectionData*, MenuResult*, MenuResult*) + 152 > 26 com.apple.HIToolbox 0x94a92436 MenuSelectCore(MenuData*, > Point, double, unsigned long, OpaqueMenuRef**, unsigned short*) + 454 > 27 com.apple.HIToolbox 0x94a91ba4 _HandleMenuSelection2 + 465 > 28 com.apple.HIToolbox 0x94a919c2 _HandleMenuSelection + 53 > 29 com.apple.AppKit 0x94eb2b3a _NSHandleCarbonMenuEvent + 285 > 30 com.apple.AppKit 0x94e876e6 _DPSNextEvent + 2304 > 31 com.apple.AppKit 0x94e86976 -[NSApplication > nextEventMatchingMask:untilDate:inMode:dequeue:] + 156 > 32 com.apple.AppKit 0x94e48bef -[NSApplication run] + 821 > 33 com.apple.prokit 0x001beab1 NSProApplicationMain + 326 > 34 com.apple.motion 0x000055de 0x1000 + 17886 > 35 com.apple.motion 0x00002746 0x1000 + 5958 > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/pro-apps-dev/pschneider%40apple.com > > This email sent to pschneider(a)apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

Re: 3rd party download pages
by Jon Chappell 12 Jul '10

12 Jul '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:cc:content-type; bh=Zjne7wSs9uVVzcShqMSHZBPrCXBVMZSZI/sgiDEIKjQ=; b=sxwOTUrT3mf61VVylIuNF7hvrZPoxZAVpIxxlBojYbUe1xQVblsT3DGEzIqyB1CH5L aeSn4dQIc+z6ByV75kn653h5R5cXf+9dowpciaca2QgkDWFzG8V9zTBsHoTgR6jaGjI7 aFbfuu6RLP9JHrOiCk79g3zXAhT5ufDHCB1JI= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=rkeli8KfthZdTcWDlQBwvTKRKyRvEtm25qdgA1y+GWoQRLxWirIVnEirJ5FTpUrOrY u+CTRdF6nAT3G2rSgkMfscd/30fE/xTjnNfVRBnfAItn9SM6KUlRBtpHK7uMLggvYeOn XO8xbJHFwqFEDCtrn82xCKG0WxM34uklITBrk= _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

Re: 3rd party download pages
by Charles Meyer 12 Jul '10

12 Jul '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

FxPlug dealloc Crashing in Motion
by Bob Currier 12 Jul '10

12 Jul '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com I've got an FxPlug that's working fine in FCP, but when used in Motion it crashes whenever dealloc is called. I've no-op'd the dealloc routine, and even removed it entirely, yet the crash still occurs. Although the crash is in Motion, and seems to be occurring after my plugin has been unloaded, no doubt it's something I'm doing wrong. Any ideas of how to proceed to locate this? I do have a number of custom UI params. The relevant crash log is below. -- Bob Process: Motion [82906] Path: /Applications/Motion.app/Contents/MacOS/Motion Identifier: com.apple.motion Version: 4.0.2 (726) Build Info: Motion-7260000~10 Code Type: X86 (Native) Parent Process: launchd [227] Date/Time: 2010-07-12 15:25:09.786 -0700 OS Version: Mac OS X 10.6.3 (10D573) Report Version: 6 Interval Since Last Report: 4098 sec Crashes Since Last Report: 1 Per-App Interval Since Last Report: 39 sec Per-App Crashes Since Last Report: 1 Anonymous UUID: 2E1CCFC8-421A-4B37-8270-7D6D9A3F92CB Exception Type: EXC_BAD_ACCESS (SIGBUS) Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000020 Crashed Thread: 0 Dispatch queue: com.apple.main-thread Application Specific Information: objc_msgSend() selector name: release Thread 0 Crashed: Dispatch queue: com.apple.main-thread 0 libobjc.A.dylib 0x9861eed7 objc_msgSend + 23 1 com.apple.ozone.framework 0x009886de -[OZProPlugParmHandler dealloc] + 782 2 com.apple.ozone.framework 0x0097669c OZProPlugEffect::~OZProPlugEffect() + 924 3 com.apple.ozone.framework 0x008a9738 OZPasteEntry::~OZPasteEntry() + 152 4 com.apple.ozone.framework 0x008aa128 OZPasteList::~OZPasteList() + 88 5 libSystem.B.dylib 0x97b2d3bf __cxa_finalize + 208 6 libSystem.B.dylib 0x97b2d2d4 exit + 33 7 com.apple.AppKit 0x950bfcc2 -[NSApplication terminate:] + 1056 8 com.apple.prokit 0x001be0a3 -[NSProApplication terminate:] + 116 9 com.apple.motion 0x0000746c 0x1000 + 25708 10 com.apple.AppKit 0x94ec55c6 -[NSApplication sendAction:to:from:] + 112 11 com.apple.prokit 0x001be3b8 -[NSProApplication sendAction:to:from:] + 127 12 com.apple.AppKit 0x94ec5479 -[NSMenuItem _corePerformAction] + 435 13 com.apple.AppKit 0x94ec516b -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 174 14 com.apple.AppKit 0x94ec505a -[NSMenu performActionForItemAtIndex:] + 65 15 com.apple.AppKit 0x94ec500d -[NSMenu _internalPerformActionForItemAtIndex:] + 50 16 com.apple.AppKit 0x94ec4f73 -[NSMenuItem _internalPerformActionThroughMenuIfPossible] + 97 17 com.apple.AppKit 0x94ec4eb7 -[NSCarbonMenuImpl _carbonCommandProcessEvent:handlerCallRef:] + 336 18 com.apple.AppKit 0x94eb95f9 NSSLMMenuEventHandler + 404 19 com.apple.HIToolbox 0x94a500a9 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1567 20 com.apple.HIToolbox 0x94a4f370 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 411 21 com.apple.HIToolbox 0x94a71b55 SendEventToEventTarget + 52 22 com.apple.HIToolbox 0x94a9e147 SendHICommandEvent(unsigned long, HICommand const*, unsigned long, unsigned long, unsigned char, void const*, OpaqueEventTargetRef*, OpaqueEventTargetRef*, OpaqueEventRef**) + 448 23 com.apple.HIToolbox 0x94ac2e40 SendMenuCommandWithContextAndModifiers + 66 24 com.apple.HIToolbox 0x94ac2df5 SendMenuItemSelectedEvent + 121 25 com.apple.HIToolbox 0x94ac2cfa FinishMenuSelection(SelectionData*, MenuResult*, MenuResult*) + 152 26 com.apple.HIToolbox 0x94a92436 MenuSelectCore(MenuData*, Point, double, unsigned long, OpaqueMenuRef**, unsigned short*) + 454 27 com.apple.HIToolbox 0x94a91ba4 _HandleMenuSelection2 + 465 28 com.apple.HIToolbox 0x94a919c2 _HandleMenuSelection + 53 29 com.apple.AppKit 0x94eb2b3a _NSHandleCarbonMenuEvent + 285 30 com.apple.AppKit 0x94e876e6 _DPSNextEvent + 2304 31 com.apple.AppKit 0x94e86976 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 156 32 com.apple.AppKit 0x94e48bef -[NSApplication run] + 821 33 com.apple.prokit 0x001beab1 NSProApplicationMain + 326 34 com.apple.motion 0x000055de 0x1000 + 17886 35 com.apple.motion 0x00002746 0x1000 + 5958 _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

Re: kFxImageColorInfo_RGB_GAMMA_DEFAULT_MACINTOSH_DISPLAY Still Used?
by Bob Currier 12 Jul '10

12 Jul '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Thanks guys. I assumed it would be 1.8, but wanted to be sure. -- Bob On Mon, Jul 12, 2010 1:51 PM, Paul Schneider <pschneider(a)apple.com> wrote: > >I believe that FCP will still send you >kFxImageColorInfo_RGB_GAMMA_DEFAULT_MACINTOSH_DISPLAY images if you set >your sequence to render in RGB. This is very uncommon. In this case, the >images will be gamma 1.8, even on 10.6. > >We used MACINTOSH_DISPLAY as a synonym for gamma 1.8, and this name >unfortunately became confusing when the default gamma for macintosh >displays changed. > > >On Jul 12, 2010, at 3:31 PM, Darrin Cardani wrote: > >> >> On Jul 11, 2010, at 3:38 PM, Bob Currier wrote: >> >>> Does anything still generate kFxImage >>> ColorInfo_RGB_GAMMA_DEFAULT_MACINTOSH_DISPLAY as a color property? >>> >>> If so, which app and how can I force it to do so? >> >> Motion no longer does. Paul, do you know what FCP does? >> >>> And does the gamma value change from 1.8 (which the comments in >>> FxImage.h indicate) to 2.2 when moving to 10.6? >> >> >> I couldn't remember myself, so I searched my old emails from this list >and found this: >> >> On Sep 17, 2009, at 12:07 PM, Darrin Cardani wrote: >> >>> On Sep 17, 2009, at 6:32 AM, Gabriele de Simone wrote: >>> >>>> I filed a very small bug against the SDK documentation, I only >wanted a clarification for what the k >FxImageColorInfo_RGB_GAMMA_DEFAULT_MACINTOSH_DISPLAY constant really >means now that the default gamma on Snow Leopard is 2.2. >>>> >>>> Unfortunately whoever read this bug didn't seem to understand my >question, and closed it: >>>> >>>> 6480950 >>>> >>>> Could you please reopen the bug, or otherwise let me know the answer >to my question? >>> >>> >>> Gabe, >>> Sorry for the confusion. The kFxI >mageColorInfo_RGB_GAMMA_DEFAULT_MACINTOSH_DISPLAY constant will still >mean 1.8, and kFxImageColorInfo_RGB_GAMMA_VIDEO will still mean 2.2. >> >> Looking through the source confirms that. >> >> Darrin >> -- >> Darrin Cardani >> dcardani(a)apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

Re: kFxImageColorInfo_RGB_GAMMA_DEFAULT_MACINTOSH_DISPLAY Still Used?
by Paul Schneider 12 Jul '10

12 Jul '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com I believe that FCP will still send you kFxImageColorInfo_RGB_GAMMA_DEFAULT_MACINTOSH_DISPLAY images if you set your sequence to render in RGB. This is very uncommon. In this case, the images will be gamma 1.8, even on 10.6. We used MACINTOSH_DISPLAY as a synonym for gamma 1.8, and this name unfortunately became confusing when the default gamma for macintosh displays changed. On Jul 12, 2010, at 3:31 PM, Darrin Cardani wrote: > > On Jul 11, 2010, at 3:38 PM, Bob Currier wrote: > >> Does anything still generate kFxImage >> ColorInfo_RGB_GAMMA_DEFAULT_MACINTOSH_DISPLAY as a color property? >> >> If so, which app and how can I force it to do so? > > Motion no longer does. Paul, do you know what FCP does? > >> And does the gamma value change from 1.8 (which the comments in >> FxImage.h indicate) to 2.2 when moving to 10.6? > > > I couldn't remember myself, so I searched my old emails from this list and found this: > > On Sep 17, 2009, at 12:07 PM, Darrin Cardani wrote: > >> On Sep 17, 2009, at 6:32 AM, Gabriele de Simone wrote: >> >>> I filed a very small bug against the SDK documentation, I only wanted a clarification for what the kFxImageColorInfo_RGB_GAMMA_DEFAULT_MACINTOSH_DISPLAY constant really means now that the default gamma on Snow Leopard is 2.2. >>> >>> Unfortunately whoever read this bug didn't seem to understand my question, and closed it: >>> >>> 6480950 >>> >>> Could you please reopen the bug, or otherwise let me know the answer to my question? >> >> >> Gabe, >> Sorry for the confusion. The kFxImageColorInfo_RGB_GAMMA_DEFAULT_MACINTOSH_DISPLAY constant will still mean 1.8, and kFxImageColorInfo_RGB_GAMMA_VIDEO will still mean 2.2. > > Looking through the source confirms that. > > Darrin > -- > Darrin Cardani > dcardani(a)apple.com > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/pro-apps-dev/pschneider%40apple.com > > This email sent to pschneider(a)apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0