• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: FxPlug Motion 4 major bug
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: FxPlug Motion 4 major bug


  • Subject: Re: FxPlug Motion 4 major bug
  • From: Darrin Cardani <email@hidden>
  • Date: Thu, 20 Aug 2009 15:18:51 -0700


On Aug 20, 2009, at 3:06 PM, Stonewall Ballard wrote:

I hope you can prove me wrong, but I've convinced myself that if kFxPropertyKey_PixelIndependent is YES in a software-only FxPlug filter, under Motion 4, the input image consists of only the lower- left quarter of the original image appearing in the upper-right quarter of the input image. The rest of the input image is black.

This worked fine in Motion 3.x, but has broken a bunch of my filters in Motion 4.0.

I put a simple demo project and built plugin here:
<http://dl.getdropbox.com/u/297034/PixelIndependentBugDemo.zip>

You'll find the filter under Filters/FxPlug Testers/FxPlug Bug Tester.

I'm going to file a bug report on this, but it's a show stopper for me, so I want to ensure that I'm right about this.


I'm able to reproduce the problem, and I'm pretty sure I know what's causing it. Please give me the bug number once you've filed it so I can escalate it and hopefully get it fixed as soon as possible.

In the meantime, setting your filters to not be pixel independent is an easy workaround. (You may want to check for both Motion and version exactly equal to 4.0.0, too just to be safe.)

Darrin
--
Darrin Cardani
email@hidden


_______________________________________________ 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
References: 
 >FxPlug Motion 4 major bug (From: Stonewall Ballard <email@hidden>)

  • Prev by Date: FxPlug Motion 4 major bug
  • Next by Date: Re: Effect In/Out points in FCP
  • Previous by thread: FxPlug Motion 4 major bug
  • Next by thread: Re: Effect In/Out points in FCP
  • Index(es):
    • Date
    • Thread