Re: Plugins render only white picture
Re: Plugins render only white picture
- Subject: Re: Plugins render only white picture
- From: Christoph Vonrhein <email@hidden>
- Date: Thu, 03 May 2018 12:34:06 -0400
I was able to narrow it down.
A simple pass through plugins that just copies the input to the output frame
buffer works. The standard plugins and examples also work. So my installation
of Motion is ok.
The reason for my plugins to fail is related to the pixel buffers that I use.
(Yes I know that PBuffers are deprecated).
To create a pixelBuffer I get the current context with CGLGetCurrentContext()
and then create a new one with CGLCreatePBuffer. This worked great for the last
decade.
Since I installed Motion 5.4, CGLCreatePBuffer returns error 10005
(kCGLBadDrawable). This means that the original sharedContext of the Motion
framebuffer must have changed in a way that my attempt to attach a new
framebuffer fails.
Can you find out what has changed?
Thanks!
Christoph
> On May 2, 2018, at 1:02 PM, Darrin Cardani <email@hidden> wrote:
>
> I’m not aware of anything that would cause that. Can you narrow down where
> the problem is? For example, if you make a pass-through plug-in that just
> copies the input to the output, does that work? Does the example FxBrightness
> work properly? Are you using any other technologies in your rendering such as
> QC or CI? (I’m not aware of any changes to those technologies either, but it
> adds more possibilities to the pile.)
>
> Darrin
>
>> On May 2, 2018, at 9:05 AM, Christoph Vonrhein <email@hidden>
>> wrote:
>>
>> So…
>>
>> it’s not OSX that’s causing it. It’s the latest update of Motion / FCP X.
>>
>> What did change for the FxPlug plugins that renders only white pictures?
>>
>> Christoph Vonrhein
>>
>>
>>> On May 1, 2018, at 9:36 PM, Christoph Vonrhein <email@hidden>
>>> wrote:
>>>
>>> Hi everybody,
>>>
>>> all my plugins worked just fine under High Sierra until the last update of
>>> High Sierra. Just by updating OSX now all my plugins suddenly only render a
>>> white picture.
>>>
>>> Before I dig deep into the code I like to ask: Is there something that I
>>> should know about the latest OSX High Sierra 10.13.4 update? What has
>>> changed that could cause this to happen?
>>>
>>> Thanks!
>>> Christoph Vonrhein
>>
>> ___
_______________________________________________
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