Re: Just started and hit first bug
Re: Just started and hit first bug
- Subject: Re: Just started and hit first bug
- From: Darrin Cardani <email@hidden>
- Date: Tue, 19 Jul 2011 10:43:47 -0700
| This is a bug that we are already aware of. Your options are to wait until we release a fix (sorry, can't give a date), or return YES, but draw something into the output that shows it did not render correctly.
Darrin On Jul 19, 2011, at 10:27 AM, Peter Litwinowicz wrote: So here's a bug I reported in Motion 4 many many months ago. And it is still in Motion 5.
I'm in Motion 5 now… my plugin only handles software rendering.
If I return "NO" as the return value from –renderOutput then Motion crashes. If I always return YES then everything is good. If I change my plugin to say it rendersHardware and return NO, then all is fine.
Okay, fine. What do I do in Motion/FCP when I run out of memory (which might happen someday, even with the new memory calls in the API and 64-bit goodness… trust me, I predict it)? I certainly can't return "YES". And now that FCP uses Motion as an engine, I can't simply rely on the fact that FCP doesn't have this bug like I did in the past, because now I HAVE to use the Motion underpinnings to use our plugins in FCP.
pete -- Darrin Cardani
|
_______________________________________________
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