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

Re: QC in FxPlug
by Darrin Cardani 31 Jul '08

31 Jul '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com On Jul 31, 2008, at 3:06 PM, Peter Litwinowicz wrote: Along the lines of, but not exactly, you probably want y = height - 1 - y 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… y = height - y; (pixels are indexed from 0 to height-1). Good catch! (In my defense, I did say "something along the lines of..." ;) ) This email sent to site_archiver(a)lists.apple.com

1 0

Re: QC in FxPlug
by Peter Litwinowicz 31 Jul '08

31 Jul '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Thread-index: AcjzWaGq4Ga79F9MEd2epgAfWzOy/A== Thread-topic: QC in FxPlug User-agent: Microsoft-Entourage/11.4.0.080122 > y = height - y; Along the lines of, but not exactly, you probably want y = height - 1 - y (pixels are indexed from 0 to height-1). Of course all bets are off if you are dealing with pixels as areas and not as points... Then all the math can change again :-) Pete _______________________________________________ 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: QC in FxPlug
by Darrin Cardani 31 Jul '08

31 Jul '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com On Jul 31, 2008, at 11:07 AM, David Yamnitsky wrote: y = height - y; 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… I've been trying to render out Quartz Composer compositions into FxPlug using a QCRenderer, and have had a lot of success by first rendering the composition to an FBO, and then drawing the output to the actual destination. To avoid this unnecessary step, I've been hoping to draw using the QCRenderer directly, and have gotten it working properly in Motion, but in FCP it's been more difficult. First of all, the coordinate system is flipped, so all rendering is flipped (except drawing of the input image (for an FxFilter)). This can usually be dealt with by either setting your transformation matrix correctly, or if you're operating directly on the pixels yourself, you can use something along the lines of: With my FBO implementation, rendering scale, pixel aspect ratio, and half height fields were all handled because I could control the context of the FBO. How would I handle all those directly? I've done several tests and found that the "Rendering Destination Dimensions" in QC do not reflect those considerations. See the example plugin called Scrolling Rich Text. It describes how to deal with all of these things in your code. This email sent to site_archiver(a)lists.apple.com

1 0

Re: What causes FCP to reject a Quicktime Movie
by Darrin Cardani 31 Jul '08

31 Jul '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com On Jul 31, 2008, at 11:04 AM, Brad Wright wrote: 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… I've seen this many times. Quicktime move created with Quicktime Pro that get rejected by Final Cut. What are the rules that Final Cut uses to accept or reject Quicktime MOV files? Can you be more specific about what you mean by "accept or reject"? Do you mean that it won't even import the movie into FCP, or that it will import but you can't put it into a sequence? Or that you can't apply a filter to it? Or that you can, but the results are wrong? Is there a specific error message you're receiving? This email sent to site_archiver(a)lists.apple.com

1 0

QC in FxPlug
by David Yamnitsky 31 Jul '08

31 Jul '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Organization: Boris FX, Inc. Hi, I've been trying to render out Quartz Composer compositions into FxPlug using a QCRenderer, and have had a lot of success by first rendering the composition to an FBO, and then drawing the output to the actual destination. To avoid this unnecessary step, I've been hoping to draw using the QCRenderer directly, and have gotten it working properly in Motion, but in FCP it's been more difficult. First of all, the coordinate system is flipped, so all rendering is flipped (except drawing of the input image (for an FxFilter)). With my FBO implementation, rendering scale, pixel aspect ratio, and half height fields were all handled because I could control the context of the FBO. How would I handle all those directly? I've done several tests and found that the "Rendering Destination Dimensions" in QC do not reflect those considerations. 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: 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

What causes FCP to reject a Quicktime Movie
by Brad Wright 31 Jul '08

31 Jul '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Brad Wright _______________________________________________ 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… I've seen this many times. Quicktime move created with Quicktime Pro that get rejected by Final Cut. What are the rules that Final Cut uses to accept or reject Quicktime MOV files? This email sent to site_archiver(a)lists.apple.com

1 0

Re: Color shifted 240 degrees in Hue
by Darrin Cardani 31 Jul '08

31 Jul '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com On Jul 31, 2008, at 7:42 AM, Brad Wright wrote: 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… I'm trying to track down an issue where I see the color shift 240 degrees in Hue from inside the Core Image Filter chain. As a test to track down the problem, I'm using a Core Image Filter that I created that will display a solid color to the screen. The Core Image filter works in stand alone application and displays the correct color to the Open GL context. I'm using the passed in FxTexture from RenderOutput and wrapping that to a CIImage. The image is drawn to the Open GL context and the color in the original video frame is displayed correctly in color. There's no shift in the original FxTexture. However, when the core image filter is applied to this image, the solid color being displayed by the core image filter is shifted around 240 degrees in Hue. I've tried a bunch of standard core image filters for manipulating the color in the image and they all have the same problem. In the CIColor used for this custom core image filter, specifying a solid blue color results in a red color being displayed to the screen. Creating a solid green CIColor displays as solid blue. Creating a solid red CIColor displays as solid green. So while the FxTexture is displayed on the screen correctly, any manipulation of the image with Core Image filters or anything of that sort is shifted around 240 degrees in Hue. Again, all the core image filters that I've applied all exhibit this color shift. Any ideas what could cause this? It sounds like a channel order problem. Are you declaring all of your buffers with their actually channel order? I believe that FxTextures will be in RGBA format. If your CoreImage filters expect BGRA, or ARGB, you might see problems similar to what you're describing. (Though from you description, it sounds like one buffer would be in GRBA or BRGA order, which is not valid in any system I know of.) Is it possible that somewhere along the line you've specified an incorrect swizzle order? This email sent to site_archiver(a)lists.apple.com

1 0

Color shifted 240 degrees in Hue
by Brad Wright 31 Jul '08

31 Jul '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Hi Pro Apps Team: Brad _______________________________________________ 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… I'm trying to track down an issue where I see the color shift 240 degrees in Hue from inside the Core Image Filter chain. As a test to track down the problem, I'm using a Core Image Filter that I created that will display a solid color to the screen. The Core Image filter works in stand alone application and displays the correct color to the Open GL context. I'm using the passed in FxTexture from RenderOutput and wrapping that to a CIImage. The image is drawn to the Open GL context and the color in the original video frame is displayed correctly in color. There's no shift in the original FxTexture. However, when the core image filter is applied to this image, the solid color being displayed by the core image filter is shifted around 240 degrees in Hue. I've tried a bunch of standard core image filters for manipulating the color in the image and they all have the same problem. In the CIColor used for this custom core image filter, specifying a solid blue color results in a red color being displayed to the screen. Creating a solid green CIColor displays as solid blue. Creating a solid red CIColor displays as solid green. So while the FxTexture is displayed on the screen correctly, any manipulation of the image with Core Image filters or anything of that sort is shifted around 240 degrees in Hue. Again, all the core image filters that I've applied all exhibit this color shift. Any ideas what could cause this? This email sent to site_archiver(a)lists.apple.com

1 0

Re: FxTemporalImageAPI return zero'd out buffers
by Paul Schneider 30 Jul '08

30 Jul '08

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

FxTemporalImageAPI return zero'd out buffers
by Brad Wright 30 Jul '08

30 Jul '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Brad Wright _______________________________________________ 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… I updated everything to the latest versions of FCP and the FXPlug SDK, but I still get zero byte buffers from FCP. Here's the code that I'm using: tempororalImageApi = [_apiManager apiForProtocol:@protocol (FxTemporalImageAPI)]; if (tempororalImageApi==NULL) { NSLog(@"Unable to get temporal image API\n"); return NO; } imageInfo.depth = kFxDepth_UINT8; imageInfo.qualityLevel = renderInfo.qualityLevel; if ([tempororalImageApi getInputBitmap:(FxBitmap **) &myBitmapImage withInfo:(FxRenderInfo) imageInfo atTime:(double) renderInfo.frame]==NO) { NSLog(@"Failed to retrieve the original Bitmap image\n"); return NO; } char* testPointer = [myBitmapImage dataPtr]; //<--- The data pointer is all zero'd out. There's no image data whatsoever. I could get this to work in the previous versions of FCP 5 and 6 by placing a clip in the timeline that didn't match the sequence settings. For some reason that made FCP return the correct image data. This email sent to site_archiver(a)lists.apple.com

1 0