February 2011 - Pro-apps-dev

FxPlug Developer?
by Nick Grosvenor 11 Feb '11

11 Feb '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

Re: FCP Out of memory error
by Bob Currier 11 Feb '11

11 Feb '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com My hand is in the air too. Waving wildly so you'll be sure to see my vote. We had fewer memory problems as an AE plug-in (within FCP) than we do as an FxPlug. It looks like we're going to have to revive that version, despite the limitations. ----- Bob Currier rcurrier(a)synthetic-ap.com Synthetic Aperture voice: +1 949 493-3444 Helping Make Your Work Look Its Best fax: +1 949 203-2108 web: www.synthetic-ap.com On Thu, Feb 10, 2011 2:57 PM, Peter Litwinowicz <pete(a)revisionfx.com> wrote: >Good time for me to step in here.. > >It would be REALLY REALLY REALLY be useful if the memory I allocate for my >plugins are coordinated through FxPlug memory functions (instead of malloc). >Our users run out of memory all the time. And not because there isn't >memory, but because FCP doesn't seem to release some of it's cached images >(or other memory) when we request memory via malloc. > >This is becoming more and more of a really big problem for us. Our plugins >routinely run out of memory because there is no coordination between FCP >allocated memory and ours. > >I know I sound like a broken record (first asked for this 4+ years ago :-) >). > >Pete > > > >On 2/10/11 9:31 AM, "Darrin Cardani" <dcardani(a)apple.com> wrote: > >> Setting the undo to 50 would not normally cause this to happen. The most >> likely cause is that your plug-in is allocating something and not freeing it >> on every render, or every user action, if you've got a custom UI control. >> >> Changes to custom UI will go on the undo stack, so if you have a huge amount >> of custom data (like 10's or 100's of Megs), it could potentially cause this >> with an undo level of 50. It will also likely slow down your plug-in, >even if >> the machine doesn't run out of memory. >> >> You can usually find out where such a leak is coming from by using >> Instruments. If you open your project in Xcode, open the "Run" menu, >then open >> the "Run with Performance Tool" submenu, and choose "Leaks" it will >start FCP >> running under Instruments and let you see if there are any leaks. If so, you >> can click on a specific leak and see the call stack for it, which >should tell >> you exactly where in your code you're allocating the memory. You then will >> need to figure out the appropriate place to free it. >> >> Some common things that developers forget to release are: >> >> 1) Any memory allocated using malloc, new, [alloc], or any Objective-C >method >> or Core Foundation function that starts with Copy or Create (common things >> include CFStrings/NSStrings, CFData/NSData, memory buffers for intermediate >> processing, etc.) >> 2) Any images from image well parameters or the temporal API (e.g. >> -getBitmap:::: or -getTexture:::) >> 3) Various objects from other parts of the OS, such as Core Graphics, >> QuickTime, etc. (Things like CGColorSpaceRefs, CGContexts, etc.) >> >> Darrin >> >> On Feb 10, 2011, at 3:43 AM, Brian F. Summa wrote: >> >>> I'm writing my first Fxplug for FCP and keep running into an out of memory >>> error on one machine. I can recreate the error by setting the levels >of undo >>> in FCP to 50. >>> >>> Is this just a coincidence or can setting the levels of undo too high cause >>> an out of memory error? Just want to make sure I'm barking up the >right tree. >>> >>> Brian >>> >>> Sent from my iPhone >>> >>> "Don't text and drive." _______________________________________________ >>> Do not post admin requests to the list. They will be ignored. >>> Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) >>> Help/Unsubscribe/Update your Subscription: >>> http://lists.apple.com/mailman/options/pro-apps-dev/dcardani%40apple.com >>> >>> This email sent to dcardani(a)apple.com >> >> -- >> Darrin Cardani >> dcardani(a)apple.com >> >> >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) >> Help/Unsubscribe/Update your Subscription: >> http://lists.apple.com/mailman/options/pro-apps-dev/pete%40revisionfx.com >> >> This email sent to pete(a)revisionfx.com > > > _______________________________________________ >Do not post admin requests to the list. They will be ignored. >Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) >Help/Unsubscribe/Update your Subscription: >http://lists.apple.com/mailman/options/pro-apps-dev/rcurrier%40synthetic- >ap.com > >This email sent to rcurrier(a)synthetic-ap.com > _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

Re: FCP Out of memory error
by Darrin Cardani 10 Feb '11

10 Feb '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com On Feb 10, 2011, at 3:11 PM, Paul Miller wrote: > On 2/10/2011 4:57 PM, Peter Litwinowicz wrote: >> Good time for me to step in here.. >> >> It would be REALLY REALLY REALLY be useful if the memory I allocate for my >> plugins are coordinated through FxPlug memory functions (instead of malloc). >> Our users run out of memory all the time. And not because there isn't >> memory, but because FCP doesn't seem to release some of it's cached images >> (or other memory) when we request memory via malloc. > > Probably a good time for me to add my request for this. Lately we've been getting crash reports from users working on very long sequences of Red footage. I've tested my code with Instruments and memory watchers and can't find any leaks, but I can't reproduce these occasional problems. I only allocate memory on a per-frame basis and then release it but if FCP is getting very aggressive with memory crashing and I need a couple of Red-sized buffers, could this be the same situation as Pete is in? It's certainly possible. I know that some of Pete's plug-ins use the temporal API a lot. Do yours also? (That's not the only reason this would happen, but I'd bet it's a contributing factor in some cases.) Darrin -- Darrin Cardani dcardani(a)apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

Re: FCP Out of memory error
by Paul Miller 10 Feb '11

10 Feb '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7 Good time for me to step in here.. It would be REALLY REALLY REALLY be useful if the memory I allocate for my plugins are coordinated through FxPlug memory functions (instead of malloc). Our users run out of memory all the time. And not because there isn't memory, but because FCP doesn't seem to release some of it's cached images (or other memory) when we request memory via malloc. On 2/10/2011 4:57 PM, Peter Litwinowicz wrote: Probably a good time for me to add my request for this. Lately we've been getting crash reports from users working on very long sequences of Red footage. I've tested my code with Instruments and memory watchers and can't find any leaks, but I can't reproduce these occasional problems. I only allocate memory on a per-frame basis and then release it but if FCP is getting very aggressive with memory crashing and I need a couple of Red-sized buffers, could this be the same situation as Pete is in? _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

Re: FCP Out of memory error
by Darrin Cardani 10 Feb '11

10 Feb '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com We read you loud and clear! :-) Darrin On Feb 10, 2011, at 2:57 PM, Peter Litwinowicz wrote: > Good time for me to step in here.. > > It would be REALLY REALLY REALLY be useful if the memory I allocate for my > plugins are coordinated through FxPlug memory functions (instead of malloc). > Our users run out of memory all the time. And not because there isn't > memory, but because FCP doesn't seem to release some of it's cached images > (or other memory) when we request memory via malloc. > > This is becoming more and more of a really big problem for us. Our plugins > routinely run out of memory because there is no coordination between FCP > allocated memory and ours. > > I know I sound like a broken record (first asked for this 4+ years ago :-) > ). > > Pete > > > > On 2/10/11 9:31 AM, "Darrin Cardani" <dcardani(a)apple.com> wrote: > >> Setting the undo to 50 would not normally cause this to happen. The most >> likely cause is that your plug-in is allocating something and not freeing it >> on every render, or every user action, if you've got a custom UI control. >> >> Changes to custom UI will go on the undo stack, so if you have a huge amount >> of custom data (like 10's or 100's of Megs), it could potentially cause this >> with an undo level of 50. It will also likely slow down your plug-in, even if >> the machine doesn't run out of memory. >> >> You can usually find out where such a leak is coming from by using >> Instruments. If you open your project in Xcode, open the "Run" menu, then open >> the "Run with Performance Tool" submenu, and choose "Leaks" it will start FCP >> running under Instruments and let you see if there are any leaks. If so, you >> can click on a specific leak and see the call stack for it, which should tell >> you exactly where in your code you're allocating the memory. You then will >> need to figure out the appropriate place to free it. >> >> Some common things that developers forget to release are: >> >> 1) Any memory allocated using malloc, new, [alloc], or any Objective-C method >> or Core Foundation function that starts with Copy or Create (common things >> include CFStrings/NSStrings, CFData/NSData, memory buffers for intermediate >> processing, etc.) >> 2) Any images from image well parameters or the temporal API (e.g. >> -getBitmap:::: or -getTexture:::) >> 3) Various objects from other parts of the OS, such as Core Graphics, >> QuickTime, etc. (Things like CGColorSpaceRefs, CGContexts, etc.) >> >> Darrin >> >> On Feb 10, 2011, at 3:43 AM, Brian F. Summa wrote: >> >>> I'm writing my first Fxplug for FCP and keep running into an out of memory >>> error on one machine. I can recreate the error by setting the levels of undo >>> in FCP to 50. >>> >>> Is this just a coincidence or can setting the levels of undo too high cause >>> an out of memory error? Just want to make sure I'm barking up the right tree. >>> >>> Brian >>> >>> Sent from my iPhone >>> >>> "Don't text and drive." _______________________________________________ >>> Do not post admin requests to the list. They will be ignored. >>> Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) >>> Help/Unsubscribe/Update your Subscription: >>> http://lists.apple.com/mailman/options/pro-apps-dev/dcardani%40apple.com >>> >>> This email sent to dcardani(a)apple.com >> >> -- >> Darrin Cardani >> dcardani(a)apple.com >> >> >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) >> Help/Unsubscribe/Update your Subscription: >> http://lists.apple.com/mailman/options/pro-apps-dev/pete%40revisionfx.com >> >> This email sent to pete(a)revisionfx.com > > -- Darrin Cardani dcardani(a)apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

Re: FCP Out of memory error
by Peter Litwinowicz 10 Feb '11

10 Feb '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Thread-index: AcvJddappG5WzqggAk2HjADVRZAgjw== Thread-topic: FCP Out of memory error User-agent: Microsoft-Entourage/12.28.0.101117 Good time for me to step in here.. It would be REALLY REALLY REALLY be useful if the memory I allocate for my plugins are coordinated through FxPlug memory functions (instead of malloc). Our users run out of memory all the time. And not because there isn't memory, but because FCP doesn't seem to release some of it's cached images (or other memory) when we request memory via malloc. This is becoming more and more of a really big problem for us. Our plugins routinely run out of memory because there is no coordination between FCP allocated memory and ours. I know I sound like a broken record (first asked for this 4+ years ago :-) ). Pete On 2/10/11 9:31 AM, "Darrin Cardani" <dcardani(a)apple.com> wrote: > Setting the undo to 50 would not normally cause this to happen. The most > likely cause is that your plug-in is allocating something and not freeing it > on every render, or every user action, if you've got a custom UI control. > > Changes to custom UI will go on the undo stack, so if you have a huge amount > of custom data (like 10's or 100's of Megs), it could potentially cause this > with an undo level of 50. It will also likely slow down your plug-in, even if > the machine doesn't run out of memory. > > You can usually find out where such a leak is coming from by using > Instruments. If you open your project in Xcode, open the "Run" menu, then open > the "Run with Performance Tool" submenu, and choose "Leaks" it will start FCP > running under Instruments and let you see if there are any leaks. If so, you > can click on a specific leak and see the call stack for it, which should tell > you exactly where in your code you're allocating the memory. You then will > need to figure out the appropriate place to free it. > > Some common things that developers forget to release are: > > 1) Any memory allocated using malloc, new, [alloc], or any Objective-C method > or Core Foundation function that starts with Copy or Create (common things > include CFStrings/NSStrings, CFData/NSData, memory buffers for intermediate > processing, etc.) > 2) Any images from image well parameters or the temporal API (e.g. > -getBitmap:::: or -getTexture:::) > 3) Various objects from other parts of the OS, such as Core Graphics, > QuickTime, etc. (Things like CGColorSpaceRefs, CGContexts, etc.) > > Darrin > > On Feb 10, 2011, at 3:43 AM, Brian F. Summa wrote: > >> I'm writing my first Fxplug for FCP and keep running into an out of memory >> error on one machine. I can recreate the error by setting the levels of undo >> in FCP to 50. >> >> Is this just a coincidence or can setting the levels of undo too high cause >> an out of memory error? Just want to make sure I'm barking up the right tree. >> >> Brian >> >> Sent from my iPhone >> >> "Don't text and drive." _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) >> Help/Unsubscribe/Update your Subscription: >> http://lists.apple.com/mailman/options/pro-apps-dev/dcardani%40apple.com >> >> This email sent to dcardani(a)apple.com > > -- > Darrin Cardani > dcardani(a)apple.com > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/pro-apps-dev/pete%40revisionfx.com > > This email sent to pete(a)revisionfx.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Cleaning up allocated memory / resources when deleting plugin
by Darrin Cardani 10 Feb '11

10 Feb '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com On Feb 10, 2011, at 6:59 AM, Peter T wrote: > I'm noticing that it's not possible to free-up memory as and when plugins are removed. I do see, for example, that if I add 3 custom plugins, then delete one, I've no way to free the memory for that instance? I am seeing 3 calls to -dealloc for each of my custom plugin objects, so I can cleanup here, but this only when FCP quits?! > > Did I miss something, or a trick to cleanup on a plugin-instance basis? Plug-ins will not be freed when you remove them from footage because they go onto the undo stack. If the user then undoes the removal, we put them back onto the footage. So it's normal that your -dealloc method isn't called when deleting a filter. I believe that if you close the project, you'll also get deallocated. This is all expected. Darrin -- Darrin Cardani dcardani(a)apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

Re: FCP Out of memory error
by Darrin Cardani 10 Feb '11

10 Feb '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Setting the undo to 50 would not normally cause this to happen. The most likely cause is that your plug-in is allocating something and not freeing it on every render, or every user action, if you've got a custom UI control. Changes to custom UI will go on the undo stack, so if you have a huge amount of custom data (like 10's or 100's of Megs), it could potentially cause this with an undo level of 50. It will also likely slow down your plug-in, even if the machine doesn't run out of memory. You can usually find out where such a leak is coming from by using Instruments. If you open your project in Xcode, open the "Run" menu, then open the "Run with Performance Tool" submenu, and choose "Leaks" it will start FCP running under Instruments and let you see if there are any leaks. If so, you can click on a specific leak and see the call stack for it, which should tell you exactly where in your code you're allocating the memory. You then will need to figure out the appropriate place to free it. Some common things that developers forget to release are: 1) Any memory allocated using malloc, new, [alloc], or any Objective-C method or Core Foundation function that starts with Copy or Create (common things include CFStrings/NSStrings, CFData/NSData, memory buffers for intermediate processing, etc.) 2) Any images from image well parameters or the temporal API (e.g. -getBitmap:::: or -getTexture:::) 3) Various objects from other parts of the OS, such as Core Graphics, QuickTime, etc. (Things like CGColorSpaceRefs, CGContexts, etc.) Darrin On Feb 10, 2011, at 3:43 AM, Brian F. Summa wrote: > I'm writing my first Fxplug for FCP and keep running into an out of memory error on one machine. I can recreate the error by setting the levels of undo in FCP to 50. > > Is this just a coincidence or can setting the levels of undo too high cause an out of memory error? Just want to make sure I'm barking up the right tree. > > Brian > > Sent from my iPhone > > "Don't text and drive." _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/pro-apps-dev/dcardani%40apple.com > > This email sent to dcardani(a)apple.com -- Darrin Cardani dcardani(a)apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

Cleaning up allocated memory / resources when deleting plugin
by Peter T 10 Feb '11

10 Feb '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=th49YcT+eflJB5p8WSpRN/JwVsSJDu63OVatpB21w1Q=; b=bpAXSakYtCRGKeH9o4yFN9ALyHWDuAw1s4h2PKVS2Tyfg76E6Tahz33tdD3tKO7O20 knS8ep16x29BmOJWV40gClwsa0/qRureOkNASSyqtMs1d0RbUk0glXwt1aVt6DQBuc/E 8odyHN3wnvPHe1L+/iQy8Xvz7btC9tz+sizxQ= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=Q8xUtOK2iHC0/lWQoacdjh/hiCvVAOFZy5TTo2ssorj4l5fc81mrbQ2gepAZSdLOQf Pejm8117yQ3BHvaPZJWsuX6Fmhfn8LaCYyrkAGVj3S7HaFfzhjhd6RoJadrRVCXYeP+k 8KPyI2RPElTg9EZp76Zo0U2A4Nv52QmqPEhjs= _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

FCP Out of memory error
by Brian F. Summa 10 Feb '11

10 Feb '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com I'm writing my first Fxplug for FCP and keep running into an out of memory error on one machine. I can recreate the error by setting the levels of undo in FCP to 50. Is this just a coincidence or can setting the levels of undo too high cause an out of memory error? Just want to make sure I'm barking up the right tree. Brian Sent from my iPhone "Don't text and drive." _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0