| Okay - so I think this is not just a gamma or a color space thing - here are the results of my tests: First of all FCP and Motion seem to get the same results, so I'm only enclosing the Motion results just now. In every case, I exported a Million color TIFF, cropped that in Photoshop, then saved a JPEG for size. This image was made by taking an image into Motion and placing a copy of it on a layer above with the blend mode set to Screen. This also matches what I get from FCP and FxScript - which makes sense, FxScript use FCP's built in routines. This next image was done within Motion using a Quartz Composition with FxFactory by taking a Screen Blend node and feeding the image input into both the foreground and background connectors. Finally, performing the same action with my own FxPlug -> Quartz Composer: FxFactory is slightly brighter than my own, but neither come close to what Motion/FCP does. Again, all of these used the same image, have passed thru Motion, and are rendered and exported from Motion, so I don't expect them to have different gammas. I also wrote a screen blend mode with a Core Image Kernel that did a pixel = 1.0 - ((1.0 - pixel1) * (1.0 - pixel2)) which did the same thing as Quartz Composer's built in Screen Blend node. As I am trying to replace an FxScript plugin, I really need to figure out what FCP and Motion are doing because just using Quartz Composer's Screen Blend node produces a result that I can't use. Any other thoughts? Patrick Sheffield Sheffield Softworks On Dec 21, 2010, at 1:55 PM, Darrin Cardani wrote: Patrick, |
_______________________________________________ Do not post admin requests to the list. They will be ignored. Quartzcomposer-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com
This email sent to [email protected]
