Re: Why is there a difference...
Re: Why is there a difference...
- Subject: Re: Why is there a difference...
- From: Ben Syverson <email@hidden>
- Date: Tue, 21 Dec 2010 19:44:09 -0600
Patrick,
This is a result of Radar #8301052: Motion does not correctly interpret still images. You need to be using video rather than stills.
Here is a copy + paste of that bug:
Summary:
Motion destructively interprets still images, leading to image data corruption immediately upon input.
Steps to Reproduce:
1. Import an into the Motion composition.
2. Choose File > Export, and in the dialog, switch "Export:" to "Current Frame," and "After Export:" to "Import into project." Give the file a unique name and click the Export button.
3. Repeat step 2 as many times as you like. You will notice that the image gets progressively brighter. See attached for screen recording.
Expected Results:
I expect to be able to input and output images without massive color transformations.
Actual Results:
Motion does something terribly wrong on import, creating a lossy input/output cycle.
Regression:
QuickTime movies do not seem to be affected.
Hope this helps,
Ben
On Dec 21, 2010, at 7:36 PM, Patrick Sheffield wrote:
> 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.
>
> <builtin1.jpg>
>
> 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.
>
> <fx1.jpg>
>
> Finally, performing the same action with my own FxPlug -> Quartz Composer:
>
> <ss1.jpg>
>
> 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
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden