Return-Path: Received: from mail-bk0-f47.google.com ([209.85.214.47] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP-TLS id 5098371 for AE-List@media-motion.tv; Fri, 07 Jun 2013 10:20:55 +0200 Received: by mail-bk0-f47.google.com with SMTP id jg1so1882514bkc.6 for ; Fri, 07 Jun 2013 01:30:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type; bh=FjppHhTj2rmQThYRTuW/p5KywMF/LIdtos+dPKeUrF8=; b=eJj/LcBC7eMRf3OzyULhEAiJN3tnYnoGuwZYetAdWT37T04W6peZkWPlio0bbN+Cp0 czwSaqHB/2e9X0GTACe9jJrYh3w2Htw4OiDMi4SYvuKK74CTO3/ir3XhgrWPK0GFZfN7 LG4CZKZfhtEO2Ej4EKtKj4jcSjqIOZ0yRtvZOwjHn6ncHImvpn462EeNPUK20tLD4hna qLD9OFoi3nkRVGuGQCk+vCLpZdQvXTgGKfNxM09QCX6ME5NIozsVq6sW+GGu1bMQvS4K fo5Ka1c9eCbFDlBPy6u0RN6VdCUQyjFz8vR09IdwrNCOTqnZ6EpQIwZ2HUyD0j+TvkGv ptUw== X-Received: by 10.205.114.138 with SMTP id fa10mr257957bkc.30.1370593840302; Fri, 07 Jun 2013 01:30:40 -0700 (PDT) Return-Path: Received: from [192.168.14.23] (p5DC651C1.dip0.t-ipconnect.de. [93.198.81.193]) by mx.google.com with ESMTPSA id rj5sm28990684bkb.1.2013.06.07.01.30.33 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 07 Jun 2013 01:30:35 -0700 (PDT) Message-ID: <51B19A20.2040402@googlemail.com> Date: Fri, 07 Jun 2013 10:30:24 +0200 From: =?ISO-8859-1?Q?Mathias_M=F6hl?= User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: After Effects Mail List Subject: Re: Script for Applying Old Settings to New Effects References: In-Reply-To: Content-Type: multipart/alternative; boundary="------------010309010809070404010405" This is a multi-part message in MIME format. --------------010309010809070404010405 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Hi Mark, the plugin SDK contains clear instructions for plugin developers what you need to do to ensure backwards compatibility of your plugins. Essentially reordering parameters and adding new ones is no problem, but as soon as you decide to exchange some controls by different ones, you loose the backwards compatibility (as there is obviously no way for AE to know how to turn the values from the old control into the new ones). As scripting has the limitations mentioned by David, there won't be a fully automated solution in general. Cheers, Mathias -- ------------------------------------------------------------------------ *mamoworld.com tools & tutorials for After Effects* dr. mathias möhl kapellenweg 36, 79100 freiburg, germany phone +49 (0)761 - 4774 584 info@mamoworld.com Am 07.06.2013 00:00, schrieb After Effects Mail List: > From: Mark Walczak > > --001a11c1c5568293e604de81401d > Content-Type: text/plain; charset=ISO-8859-1 > > Hi everyone, > > My company recently upgraded to CS6 from CS5, and we took the opportunity > to upgrade many of our plugins as well. Tiffen was part of this > transition, and we went from v2.0.2.1 to 3.0.9.6. > > Every time that we go to open a CS5 project that was created using v2 > Tiffen effects, AE reports that the project contains several links to > effects that don't exist. In reality, the effects are installed perfectly > fine on our boxes. It simply seems that Tiffen didn't implement any way > for v3 effects to naturally inherit settings/keyframes from v2. > > I just opened a trouble ticket with Tiffen, but the broader question I > wanted to ask pertains to upgrading plugins in general. > > Is there any sort of script/tool that can batch apply old plugin settings > to new effects with the same name/attributes? Unfortunately, you can't > even copy/paste between the two versions:-( > > Thank you so much for your help! --------------010309010809070404010405 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
Hi Mark,

the plugin SDK contains clear instructions for plugin developers what you need to do to ensure backwards compatibility of your plugins.
Essentially reordering parameters and adding new ones is no problem, but as soon as you decide to exchange some controls by different ones, you loose the backwards compatibility (as there is obviously no way for AE to know how to turn the values from the old control into the new ones).

As scripting has the limitations mentioned by David, there won't be a fully automated solution in general.

Cheers,
Mathias

--

mamoworld.com
tools & tutorials for After Effects

dr. mathias möhl
kapellenweg 36, 79100 freiburg, germany
phone +49 (0)761 - 4774 584
info@mamoworld.com



Am 07.06.2013 00:00, schrieb After Effects Mail List:
From: Mark Walczak <mdwalczak@gmail.com>

--001a11c1c5568293e604de81401d
Content-Type: text/plain; charset=ISO-8859-1

Hi everyone,

My company recently upgraded to CS6 from CS5, and we took the opportunity
to upgrade many of our plugins as well.  Tiffen was part of this
transition, and we went from v2.0.2.1 to 3.0.9.6.

Every time that we go to open a CS5 project that was created using v2
Tiffen effects, AE reports that the project contains several links to
effects that don't exist.  In reality, the effects are installed perfectly
fine on our boxes.  It simply seems that Tiffen didn't implement any way
for v3 effects to naturally inherit settings/keyframes from v2.

I just opened a trouble ticket with Tiffen, but the broader question I
wanted to ask pertains to upgrading plugins in general.

Is there any sort of script/tool that can batch apply old plugin settings
to new effects with the same name/attributes?  Unfortunately, you can't
even copy/paste between the two versions :-(

Thank you so much for your help!

--------------010309010809070404010405--