Re: Pro-apps-dev Digest, Vol 11, Issue 20
Re: Pro-apps-dev Digest, Vol 11, Issue 20
- Subject: Re: Pro-apps-dev Digest, Vol 11, Issue 20
- From: Garrick Meeker <email@hidden>
- Date: Mon, 12 May 2014 11:12:37 -0700
It’s purely cosmetic, I believe, but your plugins won’t show up if the users clicks on “Show 4K Ready Filters Only” or something like that. But of course, the users won’t know what that affects either.
On May 12, 2014, at 11:00 AM, Paul Miller <email@hidden> wrote:
> On 5/12/2014 11:52 AM, Garrick Meeker wrote:
>> Given all the garbage frame bugs that lasted until maybe FCP 10.0.7, I
>> don’t think it’s realistic to support versions of FCP older than that
>> anyway. But we just discovered that older templates don’t show up as “4K
>> Ready”, so now we need to create one template for FCP 10.0.9 with Motion
>> 5.0.x and one template with 4K project settings and 4K Ready checked for
>> FCP 10.1.x with Motion 5.1.x. I could see this getting difficult to
>> manage in a few years if we’re still required to create templates.
>
> You mean the 106 templates I just did with the default HD template won't work in a 4k project?
>
> Paul SMASH!
>
>
>>
>> On May 9, 2014, at 1:28 PM, Peter Litwinowicz <email@hidden
>> <mailto:email@hidden>> wrote:
>>
>>> What we are mostly talking about is creating previous Motion
>>> templates for use in previous versions of FCP.
>>>
>>> That said, most of our users will ONLY have FCP and not Motion. So
>>> what to do then? There's no way for them to create templates. We
>>> are mostly talking about old versions of FCP that can only load older
>>> Motion template versions… so we want an older version of Motion to
>>> create templates for those older versions of FCP.
>>>
>>> Pete
>>>
>>>
>>> From:Dieter Becker <email@hidden
>>> <mailto:email@hidden>>
>>> Date:Friday, May 9, 2014 1:14 PM
>>> To:<email@hidden <mailto:email@hidden>>
>>> Subject:Re: Pro-apps-dev Digest, Vol 11, Issue 20
>>>
>>> Hi,
>>>
>>> if the user/client can’t/won’t update and still has the Motion version
>>> that you don’t.
>>> Then just ask him to create the template himself.
>>> Creating a template is easier than getting email Mail.
>>>
>>> I take that the cases where one cannot update for some reason, are few.
>>> So - perhaps in those cases, take 2 minutes to describe to the user
>>> how to create the template
>>> himself with your plug-in.
>>>
>>> My 2 Cents anyway
>>>
>>> — Best
>>> Morten
>>> _______________________________________________
>>> Do not post admin requests to the list. They will be ignored.
>>> Pro-apps-dev mailing list (email@hidden
>>> <mailto:email@hidden>)
>>> Help/Unsubscribe/Update your Subscription:
>>>
>>> This email sent email@hidden <mailto:email@hidden>
>>> _______________________________________________
>>> Do not post admin requests to the list. They will be ignored.
>>> Pro-apps-dev mailing list (email@hidden
>>> <mailto:email@hidden>)
>>> Help/Unsubscribe/Update your Subscription:
>>>
>>> This email sent email@hidden
>>> <mailto: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
>>
>
> _______________________________________________
> 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