• 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: FxTemporalImageAPI memory overflow in FCP X?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: FxTemporalImageAPI memory overflow in FCP X?

  • Subject: Re: FxTemporalImageAPI memory overflow in FCP X?
  • From: Darrin Cardani <email@hidden>
  • Date: Thu, 3 Nov 2011 15:21:30 -0700
I'm not aware of this problem. Please file a bug.

Darrin

On Nov 3, 2011, at 12:43 PM, Eberhard Ammelt wrote:

> Hello,
>
> are the FxTemporalImageAPI methods considered to work correctly in FCP X (10.0.1)?
> When reading a sequence of frames, FCP X allocates more and more memory, which is never released. This occurs with all bitmap and texture reading methods in FxTemporalImageAPI.
>
> Regards, Eberhard _______________________________________________
> 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

 _______________________________________________
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: 
 >FxTemporalImageAPI memory overflow in FCP X? (From: Eberhard Ammelt <email@hidden>)

  • Prev by Date: FxTemporalImageAPI memory overflow in FCP X?
  • Next by Date: Asset start timecode ignored
  • Previous by thread: FxTemporalImageAPI memory overflow in FCP X?
  • Next by thread: Asset start timecode ignored
  • Index(es):
    • Date
    • Thread