Re: What problems do you run into when writing plug-ins?
Re: What problems do you run into when writing plug-ins?
- Subject: Re: What problems do you run into when writing plug-ins?
- From: Darrin Cardani <email@hidden>
- Date: Wed, 20 Oct 2010 09:54:06 -0700
On Oct 18, 2010, at 10:11 PM, Brian Gardner wrote:
> Certainly, Image Parameters have been troublesome.
> Especially, getting frames synced from timeline to
> matching frames in Image parameters.
>
> Trying to keep them in sync through user edits
> on the Timeline was very troublesome.
>
> I wrote a bunch of stereoscopic FxPlugs a while back.
> I eventually got them working as well as the
> API would allow. Some of the Dev problems were
> documentation that could be misinterpreted,
> which could have been disambiguated better
> if there were examples to clarify.
Just so you know, you can file bugs against our documentation specifying what's unclear. And of course, posting a message here saying what types of code examples you'd like to see would give me an idea of how to spend the little time I have to write examples. So let me know what needs to be clarified, and hopefully I can clarify it either in documentation or code.
> Of course, eventually, after figuring it all out,
> I realized that some necessary functionally
> was just not in the API at all. These were not just
> stereoscopic related, but missing functionality
> for image parameters in general.
These sound like enhancement requests. We don't get to them as quickly as I'd like, but we do often make new functionality based on enhancement requests from 3rd party developers. So file bugs and tell us how you'd like it improved. For example, in Motion 4, we made it easier to get frames at non-render times. In Motion 3, this wasn't possible because of threading issues, but after we saw how important it was to so many developers, we worked through those issues and made it work.
> I have never released any of these commercially.
> Mostly because I've never figured out how
> to implement licensing code for FxPlugs.
> So far, I've just been using them in-house
> for various movies roughly over the past 5 years.
>
> Which might be another thing that could be addressed
> into documentation. Like an example license gen/checker.
That's an interesting thought, but I don't know how useful it would be. If we publish docs on how to create a license gen/checker, then people who want to crack your product's license gen code already have something to start from, and it's the same code you would have started from. But it might be worth having a discussion here about when and where in your plug-in to handle it, and how to do it in a non-obtrusive way for your legit users.
Darrin
--
Darrin Cardani
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