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 10:23:21 -0800
I’m not aware of any such changes. The OS determines which version of OpenGL is installed, not FCP, though FCP (or really Motion) does set up the frame buffer for your plug-in. In 10.1 you will get called to render the same instance of a plug-in on 2 different threads on a machine that has 2 GPUs (if you set your properties flag to say you can handle it) and there are certainly concurrency implications from that. But if you either haven’t set the flag or aren’t running on a multi-GPU machine, you probably won’t hit that case.
What are the specific errors that you’re seeing?
Also, there should be no difference in how we set up the OpenGL state between FxPlug 2 and FxPlug 3. The difference is solely in how the plug-in is packaged and how the app finds it on disk. Once it’s loaded and running, things should be the same.
Darrin
On Jan 17, 2014, at 10:16 AM, Ardo Avancena <email@hidden> wrote:
> Has there been a change with the Framebuffers from fcpx 10.0.9 to 10.1?
>
> Whenever I run my plugin in 10.0.9 I don't get glBlitFramebuffer errors but on 10.1 I do.
>
> At first I used the plugin the legacy style for FxPlug3, but still threw the errors. I also converted the plugin to FxPlug3 but still throws errors.
>
> Any thoughts on this?
> _______________________________________________
> 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