April 2012 - Pro-apps-dev - lists.apple.com

Re: up-side-down image in Motion update
by Darrin Cardani 25 Apr '12

25 Apr '12

On Apr 25, 2012, at 9:43 AM, Paul Miller wrote: > On 4/25/2012 11:28 AM, Darrin Cardani wrote: >> >> On Apr 23, 2012, at 6:28 AM, Paul Miller wrote: >> >>> I notice that in the latest Motion update the image is up-side-down now when using getInputImage (for custom UI preview purposes). Well, technically it now matches the orientation field in the bitmap info - but FCPX is still lying/doing it the old way. >>> >>> 1. can we get this fixed in FCPX soon? >>> 2. what's the recommended way to detect the difference between Motion/FCPX now so I can work around the problem? >> >> We've isolated a case where this is still happening and are working on a fix. No ETA on when it will be available. > > Can you tell me what the fix will be? > > We're literally 5 minutes away from releasing our first major FCPX/Motion5-compatible plugin that has a custom preview, and I worked around this issue by checking for Motion 5.0.3 or greater, and flipping the image (assuming that going forward, Motion would be consistent with the orientation field). > > If you're going to change it, I'd like to know what the change will be so that when your fix appears it doesn't break my work-around. > > Will your 5.0.4 update go back to doing it the old way (the way FCPX does it), or will you fix FCPX to set the orientation value properly, so they are both consistent? > > I'd like to change my plugin NOW to handle your future fix, so I don't need to scramble to change it again later. The planned fix is that all images returned via a Motion Effect will actually have their origin in the lower left, just like when running in the Motion.app, and they will all be marked as such. At least that's the plan right now. I can't guarantee it won't change (though it seems unlikely). I also can't guarantee that it will be in the next release - that's not decided by me. Darrin _______________________________________________ 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: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: up-side-down image in Motion update
by Paul Miller 25 Apr '12

25 Apr '12

On 4/25/2012 11:28 AM, Darrin Cardani wrote: On Apr 23, 2012, at 6:28 AM, Paul Miller wrote: I notice that in the latest Motion update the image is up-side-down now when using getInputImage (for custom UI preview purposes). Well, technically it now matches the orientation field in the bitmap info - but FCPX is still lying/doing it the old way. 1. can we get this fixed in FCPX soon? 2. what's the recommended way to detect the difference between Motion/FCPX now so I can work around the problem? We've isolated a case where this is still happening and are working on a fix. No ETA on when it will be available. Can you tell me what the fix will be? Thanks! _______________________________________________ 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: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com We're literally 5 minutes away from releasing our first major FCPX/Motion5-compatible plugin that has a custom preview, and I worked around this issue by checking for Motion 5.0.3 or greater, and flipping the image (assuming that going forward, Motion would be consistent with the orientation field). If you're going to change it, I'd like to know what the change will be so that when your fix appears it doesn't break my work-around. Will your 5.0.4 update go back to doing it the old way (the way FCPX does it), or will you fix FCPX to set the orientation value properly, so they are both consistent? I'd like to change my plugin NOW to handle your future fix, so I don't need to scramble to change it again later.

1 0

Re: up-side-down image in Motion update
by Darrin Cardani 25 Apr '12

25 Apr '12

On Apr 23, 2012, at 6:28 AM, Paul Miller wrote: > I notice that in the latest Motion update the image is up-side-down now when using getInputImage (for custom UI preview purposes). Well, technically it now matches the orientation field in the bitmap info - but FCPX is still lying/doing it the old way. > > 1. can we get this fixed in FCPX soon? > 2. what's the recommended way to detect the difference between Motion/FCPX now so I can work around the problem? We've isolated a case where this is still happening and are working on a fix. No ETA on when it will be available. Darrin _______________________________________________ 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: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: FCP X parameterChanged bug?
by Darrin Cardani 25 Apr '12

25 Apr '12

Garrick, I'll have to investigate more to figure out whether it's a bug or not, but please file a Radar anyway, as clearly it needs to be better documented. Darrin On Apr 24, 2012, at 1:34 PM, Garrick Meeker wrote: > I'm not sure if this is a bug or if I'm using the API incorrectly. This works in Motion but not FCP 10.0.4. In parameterChanged, I call startAction, startUndoGroup, and currentTime. Then I call: > > FxKeyframeInfo info; > FxInitKeyframeInfo(info); > info.time = t; > info.style = kFxKeyframeStyle_Linear; > [_keyframeAPI addKeyframe:info > toParam:parmId > andChannel:chan]; > > for chan in channelCount, followed by setFloatValue. The values and keyframes are changed on the PREVIOUS frame. If I'm at frame 60, the keyframes and value changes happen at 59 (but hasKeyframe will still report that there's a keyframe at 60). > > Is currentTime (and renderOutput) starting at 1 but the parameter and keyframe API's expect to start at 0? It seems like that's the case, but I'd like to get confirmation before I file a bug. > > > _______________________________________________ > 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: > https://lists.apple.com/mailman/options/pro-apps-dev/dcardani%40apple.com > > This email sent to 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: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: up-side-down image in Motion update
by Paul Miller 25 Apr '12

25 Apr '12

On 4/24/2012 9:59 PM, Garrick Meeker wrote: I've noticed that too. Also when calling getInputImage from parameterChanged, the result is 8-bit (even if colorInfo is linear!) To make matters worse, the conversion to 8-bit doesn't appear to clamp and I get stray blue pixels (with kFxPropertyKey_DesiredProcessingColorInfo set to kFxImageColorInfo_RGB_GAMMA_VIDEO). Fortunately these issues aren't deal breakers in my case. I'll file a bug tomorrow. Since host cap still returns Motion, you need to do this. You'll need the version number too in case future versions change these behaviors. (I've heard that the identifier can be "finalcut" or "finalcuttrial".) Thanks for the sample! _______________________________________________ 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: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com I noticed the new non-clamping behavior as well. However, I also discovered that if I specify a depth of float32 in the getInputImage parameters, it does return a float image, which I can then clamp myself (this is in FCPX though). (PS it seems my emails are taking several days to make it to the list, so I apologize if it looks like I ignored you).

1 0

Re: up-side-down image in Motion update
by Garrick Meeker 25 Apr '12

25 Apr '12

I've noticed that too. Also when calling getInputImage from parameterChanged, the result is 8-bit (even if colorInfo is linear!) To make matters worse, the conversion to 8-bit doesn't appear to clamp and I get stray blue pixels (with kFxPropertyKey_DesiredProcessingColorInfo set to kFxImageColorInfo_RGB_GAMMA_VIDEO). Fortunately these issues aren't deal breakers in my case. I'll file a bug tomorrow. Since host cap still returns Motion, you need to do this. You'll need the version number too in case future versions change these behaviors. (I've heard that the identifier can be "finalcut" or "finalcuttrial".) NSBundle *appBundle = [NSBundle mainBundle]; if (appBundle != NULL) { NSString* app = [appBundle bundleIdentifier]; if ([app caseInsensitiveCompare:@"com.apple.finalcut"] == NSOrderedSame || [app caseInsensitiveCompare:@"com.apple.finalcuttrial"] == NSOrderedSame) { ... NSString *version = [[appBundle infoDictionary] objectForKey:@"CFBundleShortVersionString"]; if (version) { const char *s = [version UTF8String]; int major, minor, bug; if (sscanf(s, "%d.%d.%d", &major, &minor, &bug) == 3) { } else if (sscanf(s, "%d.%d", &major, &minor) == 2) { } } } } On Apr 23, 2012, at 6:28 AM, Paul Miller wrote: > I notice that in the latest Motion update the image is up-side-down now when using getInputImage (for custom UI preview purposes). Well, technically it now matches the orientation field in the bitmap info - but FCPX is still lying/doing it the old way. > > 1. can we get this fixed in FCPX soon? > 2. what's the recommended way to detect the difference between Motion/FCPX now so I can work around the problem? > > _______________________________________________ > 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: > https://lists.apple.com/mailman/options/pro-apps-dev/garrick%40digitalanarc… > > This email sent to garrick(a)digitalanarchy.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: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: up-side-down image in Motion update
by Paul Miller 25 Apr '12

25 Apr '12

_______________________________________________ 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: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com As an aside, I posted both of my previous emails several days ago and they are just showing up on the list - anyone had similar issues?

1 0

FCP X parameterChanged bug?
by Garrick Meeker 24 Apr '12

24 Apr '12

I'm not sure if this is a bug or if I'm using the API incorrectly. This works in Motion but not FCP 10.0.4. In parameterChanged, I call startAction, startUndoGroup, and currentTime. Then I call: FxKeyframeInfo info; FxInitKeyframeInfo(info); info.time = t; info.style = kFxKeyframeStyle_Linear; [_keyframeAPI addKeyframe:info toParam:parmId andChannel:chan]; for chan in channelCount, followed by setFloatValue. The values and keyframes are changed on the PREVIOUS frame. If I'm at frame 60, the keyframes and value changes happen at 59 (but hasKeyframe will still report that there's a keyframe at 60). Is currentTime (and renderOutput) starting at 1 but the parameter and keyframe API's expect to start at 0? It seems like that's the case, but I'd like to get confirmation before I file a bug. _______________________________________________ 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: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

up-side-down image in Motion update
by Paul Miller 23 Apr '12

23 Apr '12

1. can we get this fixed in FCPX soon? _______________________________________________ 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: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com I notice that in the latest Motion update the image is up-side-down now when using getInputImage (for custom UI preview purposes). Well, technically it now matches the orientation field in the bitmap info - but FCPX is still lying/doing it the old way. 2. what's the recommended way to detect the difference between Motion/FCPX now so I can work around the problem?

1 0

Re: Motion 5.0.3 kFxPropertyKey_PixelIndependent issue?
by Paul Miller 20 Apr '12

20 Apr '12

On 4/16/2012 3:44 PM, Darrin Cardani wrote: Please file a bug. Without more details, it's hard to know whether this is a reasonable result for your filter. The Picture-In-Picture filter is definitely not pixel independent, so setting that flag should cause it to render incorrectly. The Brightness template should be pixel independent, but I seem to recall that it also has this issue, so it's probably an indication of a bug. And Stoney, if you're still on the list, forward the bug number for the bug mentioned in the below post. I don't recall seeing this one come by, so I'm really surprised that you mentioned it that long ago and it's not addressed yet. If you can give me the bug number, I'll investigate and raise its priority. I'm seeing the same thing. Happens in FCPX too. _______________________________________________ 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: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0