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

Re: QT Rates
by Pierre Jasmin 06 Aug '10

06 Aug '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Organization: RE:Vision Effects User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.11) Gecko/20100711 Thunderbird/3.0.6 Hello, one of my users came up with something somewhat surprising. He had a QT movie that reported a clip frame rate of 23.98 and a video frame rate of 29.97 within FCP (CMD-9). The genesis was unclear (as in: there was no way to figure out how he had gotten there). The footage had been shot in a Canon still camera (Mark 2 5D?). You can use Cinema Tools to change the frame rate reported :) Thanks, Rainer Standke XMiL Workflow Tools http://www.xmil.biz _______________________________________________ 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/jasmin%40revisionfx.com This email sent to jasmin(a)revisionfx.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… On 8/5/2010 6:36 PM, Rainer Standke wrote: This leads to the question: Are there ever times when the clip's frame rate is not the frame rate of the video? Or is it safe to assume that the clip's frame rate is always going to be the same as the clip's video's frame rate? This email sent to site_archiver(a)lists.apple.com

1 0

QT Rates
by Rainer Standke 06 Aug '10

06 Aug '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Hello, one of my users came up with something somewhat surprising. He had a QT movie that reported a clip frame rate of 23.98 and a video frame rate of 29.97 within FCP (CMD-9). The genesis was unclear (as in: there was no way to figure out how he had gotten there). The footage had been shot in a Canon still camera (Mark 2 5D?). This leads to the question: Are there ever times when the clip's frame rate is not the frame rate of the video? Or is it safe to assume that the clip's frame rate is always going to be the same as the clip's video's frame rate? Thanks, Rainer Standke XMiL Workflow Tools http://www.xmil.biz _______________________________________________ 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: FxTexture size for image well images
by Darrin Cardani 05 Aug '10

05 Aug '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com I don't think so. But then I didn't think the main render path was doing that anymore, either, so it's possible the same bug is there in that path, as well. Darrin On Aug 5, 2010, at 11:16 AM, Ben Syverson wrote: > Darrin, > > Yes, this is in Motion (4.0.2 to be exact). Will the TemporalAPI also return images with antialiased edges? > > Ben > > > On Aug 5, 2010, at 1:04 PM, Darrin Cardani wrote: >> Ben, >> I assume this is in Motion and not FCP, right? Motion will sometimes render anti-aliased edges around objects. I thought we had fixed cases where we passed these to plugins, but it appears not. >> >> If you want to get the full-sized images, you can always use the TemporalAPI. That will always return a full-sized image. You can pass it the current time if you want. >> >> [FxTexture width] is the correct way to get the width of an FxTexture. You can also ask for its texture coords and see what those say. >> >> Let me know if you have any other questions. >> >> Thanks, >> Darrin >> -- >> Darrin Cardani >> dcardani(a)apple.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… This email sent to site_archiver(a)lists.apple.com

1 0

Re: FxTexture size for image well images
by Ben Syverson 05 Aug '10

05 Aug '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Darrin, Yes, this is in Motion (4.0.2 to be exact). Will the TemporalAPI also return images with antialiased edges? Ben On Aug 5, 2010, at 1:04 PM, Darrin Cardani wrote: > Ben, > I assume this is in Motion and not FCP, right? Motion will sometimes render anti-aliased edges around objects. I thought we had fixed cases where we passed these to plugins, but it appears not. > > If you want to get the full-sized images, you can always use the TemporalAPI. That will always return a full-sized image. You can pass it the current time if you want. > > [FxTexture width] is the correct way to get the width of an FxTexture. You can also ask for its texture coords and see what those say. > > Let me know if you have any other questions. > > Thanks, > 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: FxTexture size for image well images
by Darrin Cardani 05 Aug '10

05 Aug '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com On Aug 5, 2010, at 11:01 AM, Ben Syverson wrote: > Hi all, > > I have an FxPlug that takes extremely small images as parameters, and I'm having trouble determining the "true" size of the source image. When I pass a 60x10 pixel image in, sometimes the FxTexture reports its width and height as 62x13, but sometimes it reports it as 60x10. > > If [fxTexture width] is the wrong way to get the "true" width of the texture, I would love to know the correct way. Is the problem that the image is getting resampled/antialiased before becoming a texture? > > Also, it would be great to be able to access the source image at full scale, even if the render is not full scale. In other words, when rendering a thumbnail, I still need all 60x10 pixels of that parameter image. As it is, it's getting downscaled to a useless 6x4 pixels. > > I'm now forced to implement a custom UI so I can load images from the file system. It's the only way I can reliably produce an FxTexture exactly the size of the image. I really hate reimplementing the functionality of a built-in parameter type. It's such a hacky workaround. > > Any advice would be appreciated! Ben, I assume this is in Motion and not FCP, right? Motion will sometimes render anti-aliased edges around objects. I thought we had fixed cases where we passed these to plugins, but it appears not. If you want to get the full-sized images, you can always use the TemporalAPI. That will always return a full-sized image. You can pass it the current time if you want. [FxTexture width] is the correct way to get the width of an FxTexture. You can also ask for its texture coords and see what those say. Let me know if you have any other questions. Thanks, 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

FxTexture size for image well images
by Ben Syverson 05 Aug '10

05 Aug '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Hi all, I have an FxPlug that takes extremely small images as parameters, and I'm having trouble determining the "true" size of the source image. When I pass a 60x10 pixel image in, sometimes the FxTexture reports its width and height as 62x13, but sometimes it reports it as 60x10. If [fxTexture width] is the wrong way to get the "true" width of the texture, I would love to know the correct way. Is the problem that the image is getting resampled/antialiased before becoming a texture? Also, it would be great to be able to access the source image at full scale, even if the render is not full scale. In other words, when rendering a thumbnail, I still need all 60x10 pixels of that parameter image. As it is, it's getting downscaled to a useless 6x4 pixels. I'm now forced to implement a custom UI so I can load images from the file system. It's the only way I can reliably produce an FxTexture exactly the size of the image. I really hate reimplementing the functionality of a built-in parameter type. It's such a hacky workaround. Any advice would be appreciated! Ben _______________________________________________ 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: Out of range premultiplied images in FxPlug/FCP
by Paul Schneider 02 Aug '10

02 Aug '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Hi Eberhard, It sounds like your plugin may be generating some illegal pixel values. FxPlug output must be premultiplied; that is, the color components must be <= the alpha component. You have to be careful not to break the premultiplied state of the pixels during processing. FCP will unmultiply your images after processing, so you will immediately see artifacts if you produce non-premultiplied images. In the simple case, Motion will often just display the color buffer to the screen, so issues with non-matching alpha won't be visible. But you will still see artifacts if you do more complicated processing, such as compositing the output over other layers. Can you double-check your algorithm to make sure that you are always generating premultiplied pixels? - Paul On Jul 29, 2010, at 12:42 PM, Eberhard Ammelt wrote: > Hello, > > we have a problem with some of our OpenGL based fxplug filters. > In some cases the rendered image doesn't look as expected where alpha is > 0 and < 1. > This problem does only occur with FCP but not with Motion at any bit depth. > It seems that the color values of the filter output get out of range when unpremultiplied by FCP internally (?) > > As Motion seems to handle this, is there a way we could change this behavior in FCP - maybe by changing an OpenGL attribute? > > Thanks, > Eberhard Ammelt - Pixlock _______________________________________________ > 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