February 2007 - Pro-apps-dev

Re: FxPlug adding color cast.
by Paul Schneider 14 Feb '07

14 Feb '07

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Hi, all, Thanks, - Paul On Feb 13, 2007, at 12:14 PM, Paul Schneider wrote: Hi, list, Thanks, - Paul On Feb 13, 2007, at 9:48 AM, Gabriele de Simone wrote: On Feb 12, 2007, at 7:31 PM, Paul Schneider wrote: Hi, all, - Paul On Feb 12, 2007, at 7:10 PM, Dave Howell wrote: Begin forwarded message: Dave, et al, -- Emile Tobenfeld, Ph. D. Video Producer Image Processing Specialist Video for your HEAD! Boris FX http://www.foryourhead.com http://www.borisfx.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 I spoke with Emile offline, and we figured out that his issue doesn't have anything to do with FxPlug. His media was coming into Final Cut as (254, 0, 0) and not (255, 0, 0) - that is, the color shift happened on import, with no effects applied. This seems to be because (255, 0, 0) is either not a valid YUV value, or is truncated when compressed with the DV-NTSC codec. I was able to get (255, 0, 0) by switching to an RGB render using the Animation (lossless) codec. We have not quite figured out what is going on here, but we have ruled out FxPlug. I've also been trying to reproduce Trevor's problem, without success. I have tried a passthrough filter on several types of media on both Intel and PowerPC, and one of our QA engineers has also run some pretty extensive tests. We haven't found any color shifts, except for the 8-bit YUV issue I mentioned earlier. Here is the passthrough filter I used in my testing. It can run on either the GPU or the CPU; I tested on both. I tested using the Digital Color Meter application (in /Applications/Utilities) to compare pixel values with and without the filter. JustCopy.zip Trevor, can you try with this filter and see if you still see the problem? Also, if you could send me the media and project you see the problem with, that would be very helpful. If they are too big to email, let me know and I will find another way. If your media is sensitive, it would be very helpful if you could reproduce the problem with benign media. Has anyone else on this list seen this issue? If you have, please let me know, and include media and projects if possible. I think I may have misspoken earlier. We recently found an issue with running YUV FxPlugs on PowerPC in 8-bit, where the image would be darkened by one after going through the FxPlug. This is something that will be fixed in an upcoming version. This issue only happened in 8-bit YUV renders on PowerPC. It sounds like the issue that Trevor reports happens with RGB effects as well as YUV, and in float as well as 8-bit. This is not something we're aware of, and not something we've seen internally. You don't say if the issue happens on x86 as well; is this something you're able to test? Also, what kind of image are you applying the effect to? Does it have a fully opaque alpha channel? Are the red and blue channels significantly brighter than the green channel? So is this true in all cases? In other words, the workaround to fix it under FCP 5.1.2 would be to add 1 to the output whenever the plug-in is asked to render in 8 bit RGB/YUV, on PowerPC? Emile: the color shift is actually visible on the computer screen, but it is understandably quite small so you'll catch it easily only with bright scenes (e.g. a sky) or by building a passthrough filter and keeping an eye on the scope and toggling the filter on/ off. sorry I was silent on this topic - it somehow didn't come across my radar. This is in fact a bug in Final Cut, which only happens on PowerPC. We've identified the problem, and a fix should appear in an upcoming version. Sorry about the inconvenience! From: Emile Tobenfeld <emilet(a)borisfx.com> Date: February 12, 2007 4:09:09 PM PST To: Trevor Anderson <andtrev(a)gmail.com>, Gabriele de Simone <gds(a)noiseindustries.com>, dhowell(a)apple.com, pro-apps- dev(a)lists.apple.com Subject: Re: FxPlug adding color cast. At 3:29 PM -0800 2/12/07, Trevor Anderson wrote: I found the problem. I logged the pixel data by running two plugins, one after the other. Final cut is decreasing all values by one. If you simply pass back the input values in the plugin, FC then subtracts one from them, after fixing this in the plugin, passing back the input data plus one, the cast went away and everything works as expected. Seems like there is a bug in there somewhere, and it's in Final Cut after it gets the frame back from the plugin. Thanks to everyone who helped me out, I'm glad it was this simple, as I really wanted to avoid the workaround. Trevor Good catch, Trevor -- though it sounds like the shift affects all RGB colors and is not really a cast. I'd noticed some 254's in my debugging code where I expected 255's , but had been too busy with other issues to dig further. Can you comment on this. We don't really want to bump our input values by 1 every time we are called. "Now, here, you see, it takes all the running you can do, to keep in the same place. If you want to get somewhere else, you must run at least twice as fast as that!" -- The Red Queen

1 0

Re: FxPlug adding color cast.
by Emile Tobenfeld 13 Feb '07

13 Feb '07

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com I have tested this on ppc only, Hi, list, Thanks, - Paul On Feb 13, 2007, at 9:48 AM, Gabriele de Simone wrote: On Feb 12, 2007, at 7:31 PM, Paul Schneider wrote: Hi, all, sorry I was silent on this topic - it somehow didn't come across my radar. - Paul On Feb 12, 2007, at 7:10 PM, Dave Howell wrote: Begin forwarded message: I found the problem. I logged the pixel data by running two plugins, one after the other. Final cut is decreasing all values by one. If you simply pass back the input values in the plugin, FC then subtracts one from them, after fixing this in the plugin, passing back the input data plus one, the cast went away and everything works as expected. Seems like there is a bug in there somewhere, and it's in Final Cut after it gets the frame back from the plugin. Thanks to everyone who helped me out, I'm glad it was this simple, as I really wanted to avoid the workaround. Dave, et al, -- Emile Tobenfeld, Ph. D. Video Producer Image Processing Specialist Video for your HEAD! Boris FX http://www.foryourhead.com http://www.borisfx.com -- Emile Tobenfeld, Ph. D. Video Producer Image Processing Specialist Video for your HEAD! Boris FX http://www.foryourhead.com http://www.borisfx.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… In my case I was applying to an image which includes a block of pixels whose RGBA values are 255 0 0 255, and when I printf these values I get 254 0 0 255. The image itself is not fully opaque. At 12:14 PM -0500 2/13/07, Paul Schneider wrote: I think I may have misspoken earlier. We recently found an issue with running YUV FxPlugs on PowerPC in 8-bit, where the image would be darkened by one after going through the FxPlug. This is something that will be fixed in an upcoming version. This issue only happened in 8-bit YUV renders on PowerPC. It sounds like the issue that Trevor reports happens with RGB effects as well as YUV, and in float as well as 8-bit. This is not something we're aware of, and not something we've seen internally. You don't say if the issue happens on x86 as well; is this something you're able to test? Also, what kind of image are you applying the effect to? Does it have a fully opaque alpha channel? Are the red and blue channels significantly brighter than the green channel? So is this true in all cases? In other words, the workaround to fix it under FCP 5.1.2 would be to add 1 to the output whenever the plug-in is asked to render in 8 bit RGB/YUV, on PowerPC? Emile: the color shift is actually visible on the computer screen, but it is understandably quite small so you'll catch it easily only with bright scenes (e.g. a sky) or by building a passthrough filter and keeping an eye on the scope and toggling the filter on/off. This is in fact a bug in Final Cut, which only happens on PowerPC. We've identified the problem, and a fix should appear in an upcoming version. Sorry about the inconvenience! From: Emile Tobenfeld <emilet(a)borisfx.com> Date: February 12, 2007 4:09:09 PM PST To: Trevor Anderson <andtrev(a)gmail.com>, Gabriele de Simone <gds(a)noiseindustries.com>, dhowell(a)apple.com, pro-apps-dev(a)lists.apple.com Subject: Re: FxPlug adding color cast. At 3:29 PM -0800 2/12/07, Trevor Anderson wrote: Trevor Good catch, Trevor -- though it sounds like the shift affects all RGB colors and is not really a cast. I'd noticed some 254's in my debugging code where I expected 255's , but had been too busy with other issues to dig further. Can you comment on this. We don't really want to bump our input values by 1 every time we are called. "Now, here, you see, it takes all the running you can do, to keep in the same place. If you want to get somewhere else, you must run at least twice as fast as that!" -- The Red Queen "Now, here, you see, it takes all the running you can do, to keep in the same place. If you want to get somewhere else, you must run at least twice as fast as that!" -- The Red Queen This email sent to site_archiver(a)lists.apple.com

1 0

Re: FxPlug adding color cast.
by Paul Schneider 13 Feb '07

13 Feb '07

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Hi, list, Thanks, - Paul On Feb 13, 2007, at 9:48 AM, Gabriele de Simone wrote: On Feb 12, 2007, at 7:31 PM, Paul Schneider wrote: Hi, all, - Paul On Feb 12, 2007, at 7:10 PM, Dave Howell wrote: Begin forwarded message: Dave, et al, -- Emile Tobenfeld, Ph. D. Video Producer Image Processing Specialist Video for your HEAD! Boris FX http://www.foryourhead.com http://www.borisfx.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 think I may have misspoken earlier. We recently found an issue with running YUV FxPlugs on PowerPC in 8-bit, where the image would be darkened by one after going through the FxPlug. This is something that will be fixed in an upcoming version. This issue only happened in 8-bit YUV renders on PowerPC. It sounds like the issue that Trevor reports happens with RGB effects as well as YUV, and in float as well as 8-bit. This is not something we're aware of, and not something we've seen internally. You don't say if the issue happens on x86 as well; is this something you're able to test? Also, what kind of image are you applying the effect to? Does it have a fully opaque alpha channel? Are the red and blue channels significantly brighter than the green channel? So is this true in all cases? In other words, the workaround to fix it under FCP 5.1.2 would be to add 1 to the output whenever the plug-in is asked to render in 8 bit RGB/YUV, on PowerPC? Emile: the color shift is actually visible on the computer screen, but it is understandably quite small so you'll catch it easily only with bright scenes (e.g. a sky) or by building a passthrough filter and keeping an eye on the scope and toggling the filter on/off. sorry I was silent on this topic - it somehow didn't come across my radar. This is in fact a bug in Final Cut, which only happens on PowerPC. We've identified the problem, and a fix should appear in an upcoming version. Sorry about the inconvenience! From: Emile Tobenfeld <emilet(a)borisfx.com> Date: February 12, 2007 4:09:09 PM PST To: Trevor Anderson <andtrev(a)gmail.com>, Gabriele de Simone <gds(a)noiseindustries.com>, dhowell(a)apple.com, pro-apps- dev(a)lists.apple.com Subject: Re: FxPlug adding color cast. At 3:29 PM -0800 2/12/07, Trevor Anderson wrote: I found the problem. I logged the pixel data by running two plugins, one after the other. Final cut is decreasing all values by one. If you simply pass back the input values in the plugin, FC then subtracts one from them, after fixing this in the plugin, passing back the input data plus one, the cast went away and everything works as expected. Seems like there is a bug in there somewhere, and it's in Final Cut after it gets the frame back from the plugin. Thanks to everyone who helped me out, I'm glad it was this simple, as I really wanted to avoid the workaround. Trevor Good catch, Trevor -- though it sounds like the shift affects all RGB colors and is not really a cast. I'd noticed some 254's in my debugging code where I expected 255's , but had been too busy with other issues to dig further. Can you comment on this. We don't really want to bump our input values by 1 every time we are called. "Now, here, you see, it takes all the running you can do, to keep in the same place. If you want to get somewhere else, you must run at least twice as fast as that!" -- The Red Queen This email sent to site_archiver(a)lists.apple.com

1 0

Re: FxPlug adding color cast.
by Emile Tobenfeld 13 Feb '07

13 Feb '07

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com I'd add it to the input. On Feb 12, 2007, at 7:31 PM, Paul Schneider wrote: Hi, all, sorry I was silent on this topic - it somehow didn't come across my radar. - Paul On Feb 12, 2007, at 7:10 PM, Dave Howell wrote: Begin forwarded message: I found the problem. I logged the pixel data by running two plugins, one after the other. Final cut is decreasing all values by one. If you simply pass back the input values in the plugin, FC then subtracts one from them, after fixing this in the plugin, passing back the input data plus one, the cast went away and everything works as expected. Seems like there is a bug in there somewhere, and it's in Final Cut after it gets the frame back from the plugin. Thanks to everyone who helped me out, I'm glad it was this simple, as I really wanted to avoid the workaround. Dave, et al, -- Emile Tobenfeld, Ph. D. Video Producer Image Processing Specialist Video for your HEAD! Boris FX http://www.foryourhead.com http://www.borisfx.com -- Emile Tobenfeld, Ph. D. Video Producer Image Processing Specialist Video for your HEAD! Boris FX http://www.foryourhead.com http://www.borisfx.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… At 9:48 AM -0500 2/13/07, Gabriele de Simone wrote: So is this true in all cases? In other words, the workaround to fix it under FCP 5.1.2 would be to add 1 to the output whenever the plug-in is asked to render in 8 bit RGB/YUV, on PowerPC? Emile: the color shift is actually visible on the computer screen, but it is understandably quite small so you'll catch it easily only with bright scenes (e.g. a sky) or by building a passthrough filter and keeping an eye on the scope and toggling the filter on/off. FCP could use an info palette like AE's. Actually I did notice some 254's coming in in test cases where I expected 255;s, but was too busy dealing with other stuff to investigate,. This is in fact a bug in Final Cut, which only happens on PowerPC. We've identified the problem, and a fix should appear in an upcoming version. Sorry about the inconvenience! From: Emile Tobenfeld <emilet(a)borisfx.com> Date: February 12, 2007 4:09:09 PM PST To: Trevor Anderson <andtrev(a)gmail.com>, Gabriele de Simone <gds(a)noiseindustries.com>, dhowell(a)apple.com, pro-apps-dev(a)lists.apple.com Subject: Re: FxPlug adding color cast. At 3:29 PM -0800 2/12/07, Trevor Anderson wrote: Trevor Good catch, Trevor -- though it sounds like the shift affects all RGB colors and is not really a cast. I'd noticed some 254's in my debugging code where I expected 255's , but had been too busy with other issues to dig further. Can you comment on this. We don't really want to bump our input values by 1 every time we are called. "Now, here, you see, it takes all the running you can do, to keep in the same place. If you want to get somewhere else, you must run at least twice as fast as that!" -- The Red Queen "Now, here, you see, it takes all the running you can do, to keep in the same place. If you want to get somewhere else, you must run at least twice as fast as that!" -- The Red Queen This email sent to site_archiver(a)lists.apple.com

1 0

Re: FxPlug adding color cast.
by Gabriele de Simone 13 Feb '07

13 Feb '07

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com On Feb 12, 2007, at 7:31 PM, Paul Schneider wrote: Hi, all, - Paul On Feb 12, 2007, at 7:10 PM, Dave Howell wrote: Begin forwarded message: Dave, et al, -- Emile Tobenfeld, Ph. D. Video Producer Image Processing Specialist Video for your HEAD! Boris FX http://www.foryourhead.com http://www.borisfx.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… So is this true in all cases? In other words, the workaround to fix it under FCP 5.1.2 would be to add 1 to the output whenever the plug- in is asked to render in 8 bit RGB/YUV, on PowerPC? Emile: the color shift is actually visible on the computer screen, but it is understandably quite small so you'll catch it easily only with bright scenes (e.g. a sky) or by building a passthrough filter and keeping an eye on the scope and toggling the filter on/off. sorry I was silent on this topic - it somehow didn't come across my radar. This is in fact a bug in Final Cut, which only happens on PowerPC. We've identified the problem, and a fix should appear in an upcoming version. Sorry about the inconvenience! From: Emile Tobenfeld <emilet(a)borisfx.com> Date: February 12, 2007 4:09:09 PM PST To: Trevor Anderson <andtrev(a)gmail.com>, Gabriele de Simone <gds(a)noiseindustries.com>, dhowell(a)apple.com, pro-apps- dev(a)lists.apple.com Subject: Re: FxPlug adding color cast. At 3:29 PM -0800 2/12/07, Trevor Anderson wrote: I found the problem. I logged the pixel data by running two plugins, one after the other. Final cut is decreasing all values by one. If you simply pass back the input values in the plugin, FC then subtracts one from them, after fixing this in the plugin, passing back the input data plus one, the cast went away and everything works as expected. Seems like there is a bug in there somewhere, and it's in Final Cut after it gets the frame back from the plugin. Thanks to everyone who helped me out, I'm glad it was this simple, as I really wanted to avoid the workaround. Trevor Good catch, Trevor -- though it sounds like the shift affects all RGB colors and is not really a cast. I'd noticed some 254's in my debugging code where I expected 255's , but had been too busy with other issues to dig further. Can you comment on this. We don't really want to bump our input values by 1 every time we are called. "Now, here, you see, it takes all the running you can do, to keep in the same place. If you want to get somewhere else, you must run at least twice as fast as that!" -- The Red Queen This email sent to site_archiver(a)lists.apple.com

1 0

Re: FxPlug adding color cast.
by Paul Schneider 13 Feb '07

13 Feb '07

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 adding color cast.
by Trevor Anderson 13 Feb '07

13 Feb '07

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=In4xxHJLK9yDLnzutj25fuCN2s2yJxfvSJ8f9KUCQA0wSBD5kSbPpAhUYWRg/11/LNRYWu0PBplCXS7oUPOuu1jrn3UizqmAq1Bggkf29DmqYkrxu3NkB2VzMoGl3sHMB5ylLcWB+iBkflhJkuwh7tTsoH/tK1GoGOGyL1IHW8Q= Emile, Good question. I don't really want to increment my values at all, but it seems to be the quick fix. If you look at the RGB parade, it seems to mostly affect the red and blue channels, with the green staying the same, hence the green color cast I was getting on my images. This should be true for RGB values as well, remember they are being converted back to yuv so it has a similar effect. I haven't really tested it on rgb yet, but it does seem to fix the yuv problems, which is the color space I want to work in anyhow. I have submitted a bug report to Apple. Everytime the fxplugin is added, it decreases consistently. So you would have to add one everytime you had a plugin added. (i.e. running two plugins on one clip decreases values by two, three plugins by three) I'm not sure if this happens in motion, probably not seems that it would be only Final Cut as this plugin architecture was just added to it. Trevor _______________________________________________ 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 adding color cast.
by Emile Tobenfeld 13 Feb '07

13 Feb '07

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com I found the problem. I logged the pixel data by running two plugins, one after the other. Final cut is decreasing all values by one. If you simply pass back the input values in the plugin, FC then subtracts one from them, after fixing this in the plugin, passing back the input data plus one, the cast went away and everything works as expected. Seems like there is a bug in there somewhere, and it's in Final Cut after it gets the frame back from the plugin. Thanks to everyone who helped me out, I'm glad it was this simple, as I really wanted to avoid the workaround. Dave, et al, -- Emile Tobenfeld, Ph. D. Video Producer Image Processing Specialist Video for your HEAD! Boris FX http://www.foryourhead.com http://www.borisfx.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… At 3:29 PM -0800 2/12/07, Trevor Anderson wrote: Trevor Good catch, Trevor -- though it sounds like the shift affects all RGB colors and is not really a cast. I'd noticed some 254's in my debugging code where I expected 255's , but had been too busy with other issues to dig further. Can you comment on this. We don't really want to bump our input values by 1 every time we are called. "Now, here, you see, it takes all the running you can do, to keep in the same place. If you want to get somewhere else, you must run at least twice as fast as that!" -- The Red Queen This email sent to site_archiver(a)lists.apple.com

1 0

Re: FxPlug adding color cast.
by Trevor Anderson 12 Feb '07

12 Feb '07

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=SeVhq/9mkU3Q9KaauJHyvFyi/LgGaftkGmF+U0qdFttG3MI0myJUJsIeMkG8ve5X1jvwQ6CbqpcVIBi8LPktaAo+jpY5Tncvy6XeBzJS3X3USuTvkXoufvN/pVCBHXT3xsG9G4WDeneJlm6EElNON3hKBN3EPYkXVD9RG7duY9g= I found the problem. I logged the pixel data by running two plugins, one after the other. Final cut is decreasing all values by one. If you simply pass back the input values in the plugin, FC then subtracts one from them, after fixing this in the plugin, passing back the input data plus one, the cast went away and everything works as expected. Seems like there is a bug in there somewhere, and it's in Final Cut after it gets the frame back from the plugin. Thanks to everyone who helped me out, I'm glad it was this simple, as I really wanted to avoid the workaround. Trevor _______________________________________________ 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 adding color cast.
by Trevor Anderson 12 Feb '07

12 Feb '07

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=felflaGgsyNfjAuLnm0/OvEx1qlbB3blLNyR/sTcxqEDiyxfJ/clG5rge0rGhHJ8aI+0Ngui3rPdtp9y2h3711lZVpm9MdxF/VW78lqW7kYcB0oZDuVf2RRy96QWiimWLUtZewm126UzphlE+KYAxrH8UbAyHjCc7SdDI7CVxr0= I'm guessing the FxPlug implementation here is somewhat lacking. Nothing else has this problem, FxScripts work perfect. I'm also not using the correct hardware here, this is perhaps the problem? I'm on a powerpc g4, but I only have a radeon 9200, so it won't let me render it out with high precision selected. This is also only on my plugin, is there some setting I'm missing? It tells me I need a more powerful graphics card, but magic bullet looks render fine with the high precision setting as does everything else. Emile - the color cast appears on the computer screen, I haven't checked with the dv out to monitor yet, but I'm sure it's there as well. Gabe - As for the workaround I'm sure it works, even though not on my system, the problem is who wants to continually render to check their work? The preview rendering pipeline is different than the actual rendering pipeline? This seems strange to me and improper. The preview uses different color conversion processes than the renderer? I guess I don't understand the internal workflow of Final Cut here. Dave - I am using the filter Xcode template, it's the basic one, instead of processing any data though, I am simply sending it back unchanged. I tried clipping the values to fit into the specified r408 color space, as Apple explained it, but it still happens. Also does it in float, but as I said it won't allow me to render the clip, only preview it. Thanks for the quick replies, this is perhaps the best outlet for help on this matter that I have found yet, and hopefully in the future I can help someone else who needs it, FxPlug is very exciting to me as it goes way beyond what FxScript could do, perhaps these are problems that will only exist for awhile, as this plugin specification is fairly new to final cut (I haven't tried anything in motion yet). Thanks again, Trevor _______________________________________________ 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