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

Re: Can an FxGenerator Access images in the from the timeline?
by Darrin Cardani 11 Aug '08

11 Aug '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

Re: Width, Height, and Rowbytes in FxImage returning possible wrong values.
by Brad Wright 11 Aug '08

11 Aug '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Thanksi Steve: Brad Wright On Aug 10, 2008, at 9:15 PM, Steve Christensen wrote: |<- 16 x width ->||<- 16 x width ->| |<----------- rowBytes ----------->| row 0 |<---- upper --->||<--- lower ---->| row 1 |<---- upper --->||<--- lower ---->| ... row 719 |<---- upper --->||<--- lower ---->| or this: |<- 16 x width ->||<- 16 x width ->| |<----------- rowBytes ----------->| |<--- upper ---->| row 0 |<---- lower --->||<--- upper ---->| row 1 |<---- lower --->||<--- upper ---->| ... row 719 |<---- lower --->||<--- upper ---->| On Aug 10, 2008, at 8:20 PM, Brad Wright wrote: Thanks Steve: Brad On Aug 9, 2008, at 11:45 PM, Steve Christensen wrote: On Aug 9, 2008, at 6:29 PM, Brad Wright wrote: [myBitmapImage width] == 720 [myBitmapImage height] == 240 [myBitmapImage rowBytes] = 23040 The image format is Float and 32 bit wide. _______________________________________________ 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… Actually, I did some analysis on the image being returned. I actually walk the image a for loop and the values are consistent with a 1440x1080 image. I did this by running creating test patterns for the image, so I can see where the values should line up in memory. In this particular case, the values are consistent with 1440 pixels wide and not 720. I'm testing with Final Cut 5.14 and the latest FxPlug API's. It certainly could be broken in this combination. No, you're assuming that 16 x width == rowBytes. That's not always true. What I was getting at was this: 23040 bytes works out to 1440 16- byte float pixels between the start of each succeeding row. Given that you're seeing an image size of 720 x 240 (half of 720 x 480), it looks like you have imageInfo.fieldOrder set to either kFxFieldOrder_UPPER_FIRST or kFxFieldOrder_LOWER_FIRST. (This is also likely the type of input and output images your plugin is being provided.) Thus the bitmap is laid out like this: The rowBytes value is set so that you're using every other line (or one field) of the overall image. You should only be working with the first 720 pixels (or 11520 bytes) on each line since the other half of the rowBytes -may- contain the other field's pixels or it may be uninitialized -- the implementation details are unspecified. That's why you have to respect both the image dimensions as well as the rowBytes: there may be bytes at the end of each row in the image you're processing that are supposed to be left alone. >From what I'm seeing math doesn't quite add up. The row bytes reports 23040 while the image format is 32 bit float. 32 bit float is 16 bytes wide. Therefore, 23040/16 is 1440 which is the width of the sequence settings. So, it looks like something is inconsistent. What value did you supply in imageInfo.fieldOrder? If it contains something other than kFxFieldOrder_PROGRESSIVE, the bitmap may actually contain the entire image, but rowBytes is set up so you only see the pixels in every other row. If that's the case, it's not an application bug since it's doing exactly what you told it to do. I'm seeing possibly wrong values for width and height in an FxImage. The problem happens when I export to a DVC Pro 25 NTSC movie from an HD timeline. My sequence is 1440x1080, and the exported image is 720x480. In the rederOutput function I retrieve the actual image using the temporal image API. if ([tempororalImageApi getInputBitmap:(FxBitmap **) &myBitmapImage withInfo:(FxRenderInfo) imageInfo atTime:(double) renderInfo.frame]==NO) { NSLog(@"Failed to retrieve the original Bitmap image\n"); return NO; } Here's the values I get: 23040 is the correct row bytes value for the image if it's at 1440 pixels wide. When I try to process the image using these values in my loop, I get only the first part of the actual image. So it appears that the image is actually 1440 wide instead of being 720 wide. Is this a know bug? Is there a workaround? This email sent to site_archiver(a)lists.apple.com

1 0

Re: Can an FxGenerator Access images in the from the timeline?
by Steve Christensen 11 Aug '08

11 Aug '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com On Aug 10, 2008, at 8:29 PM, Brad Wright wrote: _______________________________________________ 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 sure the Apple guys will be able to answer definitively, but my feeling is that you can't get there from here. FxTemporalImageAPI looks like it only deals with the input image(s) associated with the effect itself. Plus there doesn't appear to be a programmatic means of determining where clips are on the timeline if they're not associated with your effect. I'm trying to create a FxGenerator that can access images from the timeline using the FxTemporalImageAPI. So far, it doesn't work. I'd like to use the an image from the timeline, but still have the FxGenerator on it's own video track so that it can read input from multiple clips. I know this is kind of complicated sounding, but it makes the plug-in that I'm creating work much better as a generator than an FxFilter. The FxFilter ties it to only a single clip. I have the FxTemporalImageAPI working in the FxFilter version of the plug-in. However, no luck with the FxGenerator. The documentation says that an FxGenerator doesn't require an input image. I don't know if that means it simple can't access one altogether. This email sent to site_archiver(a)lists.apple.com

1 0

Re: Width, Height, and Rowbytes in FxImage returning possible wrong values.
by Steve Christensen 11 Aug '08

11 Aug '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com No, you're assuming that 16 x width == rowBytes. That's not always true. |<- 16 x width ->||<- 16 x width ->| |<----------- rowBytes ----------->| row 0 |<---- upper --->||<--- lower ---->| row 1 |<---- upper --->||<--- lower ---->| ... row 719 |<---- upper --->||<--- lower ---->| or this: |<- 16 x width ->||<- 16 x width ->| |<----------- rowBytes ----------->| |<--- upper ---->| row 0 |<---- lower --->||<--- upper ---->| row 1 |<---- lower --->||<--- upper ---->| ... row 719 |<---- lower --->||<--- upper ---->| On Aug 10, 2008, at 8:20 PM, Brad Wright wrote: Thanks Steve: Brad On Aug 9, 2008, at 11:45 PM, Steve Christensen wrote: On Aug 9, 2008, at 6:29 PM, Brad Wright wrote: [myBitmapImage width] == 720 [myBitmapImage height] == 240 [myBitmapImage rowBytes] = 23040 The image format is Float and 32 bit wide. _______________________________________________ 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… What I was getting at was this: 23040 bytes works out to 1440 16-byte float pixels between the start of each succeeding row. Given that you're seeing an image size of 720 x 240 (half of 720 x 480), it looks like you have imageInfo.fieldOrder set to either kFxFieldOrder_UPPER_FIRST or kFxFieldOrder_LOWER_FIRST. (This is also likely the type of input and output images your plugin is being provided.) Thus the bitmap is laid out like this: The rowBytes value is set so that you're using every other line (or one field) of the overall image. You should only be working with the first 720 pixels (or 11520 bytes) on each line since the other half of the rowBytes -may- contain the other field's pixels or it may be uninitialized -- the implementation details are unspecified. That's why you have to respect both the image dimensions as well as the rowBytes: there may be bytes at the end of each row in the image you're processing that are supposed to be left alone. >From what I'm seeing math doesn't quite add up. The row bytes reports 23040 while the image format is 32 bit float. 32 bit float is 16 bytes wide. Therefore, 23040/16 is 1440 which is the width of the sequence settings. So, it looks like something is inconsistent. What value did you supply in imageInfo.fieldOrder? If it contains something other than kFxFieldOrder_PROGRESSIVE, the bitmap may actually contain the entire image, but rowBytes is set up so you only see the pixels in every other row. If that's the case, it's not an application bug since it's doing exactly what you told it to do. I'm seeing possibly wrong values for width and height in an FxImage. The problem happens when I export to a DVC Pro 25 NTSC movie from an HD timeline. My sequence is 1440x1080, and the exported image is 720x480. In the rederOutput function I retrieve the actual image using the temporal image API. if ([tempororalImageApi getInputBitmap:(FxBitmap **) &myBitmapImage withInfo:(FxRenderInfo) imageInfo atTime:(double) renderInfo.frame]==NO) { NSLog(@"Failed to retrieve the original Bitmap image\n"); return NO; } Here's the values I get: 23040 is the correct row bytes value for the image if it's at 1440 pixels wide. When I try to process the image using these values in my loop, I get only the first part of the actual image. So it appears that the image is actually 1440 wide instead of being 720 wide. Is this a know bug? Is there a workaround? This email sent to site_archiver(a)lists.apple.com

1 0

Can an FxGenerator Access images in the from the timeline?
by Brad Wright 11 Aug '08

11 Aug '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Hi ProApps: 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'm trying to create a FxGenerator that can access images from the timeline using the FxTemporalImageAPI. So far, it doesn't work. I'd like to use the an image from the timeline, but still have the FxGenerator on it's own video track so that it can read input from multiple clips. I know this is kind of complicated sounding, but it makes the plug-in that I'm creating work much better as a generator than an FxFilter. The FxFilter ties it to only a single clip. I have the FxTemporalImageAPI working in the FxFilter version of the plug-in. However, no luck with the FxGenerator. The documentation says that an FxGenerator doesn't require an input image. I don't know if that means it simple can't access one altogether. This email sent to site_archiver(a)lists.apple.com

1 0

Re: Width, Height, and Rowbytes in FxImage returning possible wrong values.
by Brad Wright 11 Aug '08

11 Aug '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Thanks Steve: Brad On Aug 9, 2008, at 11:45 PM, Steve Christensen wrote: On Aug 9, 2008, at 6:29 PM, Brad Wright wrote: [myBitmapImage width] == 720 [myBitmapImage height] == 240 [myBitmapImage rowBytes] = 23040 The image format is Float and 32 bit wide. _______________________________________________ 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… >From what I'm seeing math doesn't quite add up. The row bytes reports 23040 while the image format is 32 bit float. 32 bit float is 16 bytes wide. Therefore, 23040/16 is 1440 which is the width of the sequence settings. So, it looks like something is inconsistent. What value did you supply in imageInfo.fieldOrder? If it contains something other than kFxFieldOrder_PROGRESSIVE, the bitmap may actually contain the entire image, but rowBytes is set up so you only see the pixels in every other row. If that's the case, it's not an application bug since it's doing exactly what you told it to do. I'm seeing possibly wrong values for width and height in an FxImage. The problem happens when I export to a DVC Pro 25 NTSC movie from an HD timeline. My sequence is 1440x1080, and the exported image is 720x480. In the rederOutput function I retrieve the actual image using the temporal image API. if ([tempororalImageApi getInputBitmap:(FxBitmap **) &myBitmapImage withInfo:(FxRenderInfo) imageInfo atTime:(double) renderInfo.frame]==NO) { NSLog(@"Failed to retrieve the original Bitmap image\n"); return NO; } Here's the values I get: 23040 is the correct row bytes value for the image if it's at 1440 pixels wide. When I try to process the image using these values in my loop, I get only the first part of the actual image. So it appears that the image is actually 1440 wide instead of being 720 wide. Is this a know bug? Is there a workaround? This email sent to site_archiver(a)lists.apple.com

1 0

Re: The Temporal Image API ignores the image depth
by Steve Christensen 10 Aug '08

10 Aug '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

Re: Width, Height, and Rowbytes in FxImage returning possible wrong values.
by Steve Christensen 10 Aug '08

10 Aug '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com On Aug 9, 2008, at 6:29 PM, Brad Wright wrote: [myBitmapImage width] == 720 [myBitmapImage height] == 240 [myBitmapImage rowBytes] = 23040 The image format is Float and 32 bit wide. _______________________________________________ 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… What value did you supply in imageInfo.fieldOrder? If it contains something other than kFxFieldOrder_PROGRESSIVE, the bitmap may actually contain the entire image, but rowBytes is set up so you only see the pixels in every other row. If that's the case, it's not an application bug since it's doing exactly what you told it to do. I'm seeing possibly wrong values for width and height in an FxImage. The problem happens when I export to a DVC Pro 25 NTSC movie from an HD timeline. My sequence is 1440x1080, and the exported image is 720x480. In the rederOutput function I retrieve the actual image using the temporal image API. if ([tempororalImageApi getInputBitmap:(FxBitmap **) &myBitmapImage withInfo:(FxRenderInfo) imageInfo atTime:(double) renderInfo.frame]==NO) { NSLog(@"Failed to retrieve the original Bitmap image\n"); return NO; } Here's the values I get: 23040 is the correct row bytes value for the image if it's at 1440 pixels wide. When I try to process the image using these values in my loop, I get only the first part of the actual image. So it appears that the image is actually 1440 wide instead of being 720 wide. Is this a know bug? Is there a workaround? This email sent to site_archiver(a)lists.apple.com

1 0

The Temporal Image API ignores the image depth
by Brad Wright 10 Aug '08

10 Aug '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

Width, Height, and Rowbytes in FxImage returning possible wrong values.
by Brad Wright 10 Aug '08

10 Aug '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com [myBitmapImage width] == 720 [myBitmapImage height] == 240 [myBitmapImage rowBytes] = 23040 The image format is Float and 32 bit wide. 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'm seeing possibly wrong values for width and height in an FxImage. The problem happens when I export to a DVC Pro 25 NTSC movie from an HD timeline. My sequence is 1440x1080, and the exported image is 720x480. In the rederOutput function I retrieve the actual image using the temporal image API. if ([tempororalImageApi getInputBitmap:(FxBitmap **) &myBitmapImage withInfo:(FxRenderInfo) imageInfo atTime:(double) renderInfo.frame]==NO) { NSLog(@"Failed to retrieve the original Bitmap image\n"); return NO; } Here's the values I get: 23040 is the correct row bytes value for the image if it's at 1440 pixels wide. When I try to process the image using these values in my loop, I get only the first part of the actual image. So it appears that the image is actually 1440 wide instead of being 720 wide. Is this a know bug? Is there a workaround? This email sent to site_archiver(a)lists.apple.com

1 0