• 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
FCP X and parameterChanged
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

FCP X and parameterChanged


  • Subject: FCP X and parameterChanged
  • From: Garrick Meeker <email@hidden>
  • Date: Thu, 30 Jun 2011 22:17:49 -0700

I'm seeing some issues here that could seriously affect our products.  First, we get the current time in the parameterChanged method with:

id <FxCustomParameterActionAPI> actionAPI = [_apiManager apiForProtocol:@protocol(FxCustomParameterActionAPI)];
double t = [actionAPI currentTime];

That works in Motion 5 and has always worked before, but in FCP X it seems to always be 0.

And we also need access to images outside of renderOutput, specifically in parameterChanged and from on-screen controls (or custom UI in FxPlug 1).  I realize this isn't guaranteed by the API but it works in Motion 4 and 5.  FCP X seems to return a solid color.  I've only tried the bitmap calls here.  Stuffing the current OpenGL context into an FxRenderInfo to get a texture seems problematic.  Trying to cache a frame from the render calls seems difficult too because of FCP's timeline rendering.

I can file a bug but I'm really hoping there are workarounds for this release.

 _______________________________________________
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

  • Prev by Date: Re: Publishing parameters for FCP X
  • Next by Date: FxProgressAPI
  • Previous by thread: Re: Publishing parameters for FCP X
  • Next by thread: FxProgressAPI
  • Index(es):
    • Date
    • Thread