Re: glBlitFramebuffer behaves differently on FCPX 10.1 from 10.0.9 with FxPlug
Re: glBlitFramebuffer behaves differently on FCPX 10.1 from 10.0.9 with FxPlug
- Subject: Re: glBlitFramebuffer behaves differently on FCPX 10.1 from 10.0.9 with FxPlug
- From: Darrin Cardani <email@hidden>
- Date: Fri, 17 Jan 2014 13:54:35 -0800
There are a number of ways depending on what you’re trying to do. The easiest way is to make the variable a member variable so that each instance gets its own copy.
If you need to share the variable but need to avoid accessing it at the same time from multiple instances, then you need to use some sort of mutex or lock so it’s not accessed on 2 threads at once. (You need to be careful doing this, though, as if the user applies 2 instances to the same footage, you could potentially end up with a deadlock.)
Or if you have some other scenario, describe what you’re trying to do and I’m sure someone can offer a suggestion.
Darrin On Jan 17, 2014, at 1:30 PM, Ardo Avancena < email@hidden> wrote: Hm, it seems like the error only happens where there are two or more instances of the plugin.
Is there a way for me to keep the plugins from pointing to the same variable?
|
_______________________________________________
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