Return-Path: Received: from mail-ob0-f182.google.com ([209.85.214.182] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP-TLS id 5098623 for AE-List@media-motion.tv; Fri, 07 Jun 2013 16:32:02 +0200 Received: by mail-ob0-f182.google.com with SMTP id va7so6731823obc.13 for ; Fri, 07 Jun 2013 07:41:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=OXhPCGquAQa4ao9NnSVkcKRpcPrVFidhUHpxeswuTKE=; b=u969gcAq/vz+Lo/wTLamRrV9MIABSGiJB3VxnXdAoz2YqJyboUeD0PoDwG48d7K6vZ E/jSf8QtDJiy28/6UV/dAAHWSpGaNayd8owRdiX6DM+hpktm5cG4DPrsAGAw78N8rVhw BV3CnGIi6psiyF/+2Xh/WRT+t003b4z8lBTS6FguBQtZ7wBC4cdaIOSq1Pg3RdZwk/ZE HineEkwOtatcaRo6SGc0yLMtpyop5f4k2cAUxIxYRq52b7WzJHf1KHalDwX/eiEB70Ro rl2oCQErz6EWNRrCyC844NYVYD/l5WKEo5JCI5lGIsKNyit3bnVK8CQ5copkcLKs6d1N ccmg== MIME-Version: 1.0 X-Received: by 10.60.117.232 with SMTP id kh8mr21214430oeb.125.1370616106629; Fri, 07 Jun 2013 07:41:46 -0700 (PDT) Received: by 10.76.168.164 with HTTP; Fri, 7 Jun 2013 07:41:46 -0700 (PDT) In-Reply-To: References: Date: Fri, 7 Jun 2013 09:41:46 -0500 Message-ID: Subject: Re: [AE] Script for Applying Old Settings to New Effects From: Mark Walczak To: After Effects Mail List Content-Type: multipart/alternative; boundary=047d7b41419428c0c304de916e9f --047d7b41419428c0c304de916e9f Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Thanks a bunch, Drew! I'll take a close look at that script. Thanks again! On Fri, Jun 7, 2013 at 8:42 AM, Drew Gilmore wrote= : > I have no idea if this would work in your situation... but I have a plugi= n > which has Windows and Mac versions but won't survive the translation from= a > Windows project to a Mac project without becoming crash-prone and throwin= g > out lots of error messages. > > What saved me was the script "ft-Effect Instance" on AEscripts.com. It > makes a duplicate of an effect instance and its settings (either by copyi= ng > the values or by expressions.) Possibly if you used it, it would keep the > settings, but insert the newer version of the effect. > > You'd still have to do the process on each and every instance of the > effect, but it might save you from having to copy all their settings. But > given your mention about not being able to copy and paste settings, I don= 't > know if it would work. > > http://aescripts.com/ft-effect-instance/ > > Drew > > newtonscannon.com > > Just a guy made of dots and lines. > > > On Fri, Jun 7, 2013 at 3:30 AM, Mathias M=F6hl wr= ote: > >> Hi Mark, >> >> the plugin SDK contains clear instructions for plugin developers what yo= u >> 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 t= o >> 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=F6hl >> 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=3DISO-8859-1 >> >> Hi everyone, >> >> My company recently upgraded to CS6 from CS5, and we took the opportunit= y >> 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 perfect= ly >> 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 setting= s >> 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! >> >> >> > --=20 Mark Walczak ------------------- Vimeo: http://vimeo.com/mdwalczak LinkedIn: http://www.linkedin.com/in/ mdwalczak --047d7b41419428c0c304de916e9f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Thanks a bunch, Drew!=A0 I'll take a close look at tha= t script.

Thanks again!


=
On Fri, Jun 7, 2013 at 8:42 AM, Drew Gilmore <dotsandlines@gmail.com> wrote:
I have no id= ea if this would work in your situation... but I have a plugin which has Wi= ndows and Mac versions but won't survive the translation from a Windows= project to a Mac project without becoming crash-prone and throwing out lot= s of error messages.

What saved me was the script "ft-Effect Instance" on AEscript= s.com. It makes a duplicate of an effect instance and its settings (either = by copying the values or by expressions.) Possibly if you used it, it would= keep the settings, but insert the newer version of the effect.

You'd still have to do the process on each and every instance= of the effect, but it might save you from having to copy all their setting= s. But given your mention about not being able to copy and paste settings, = I don't know if it would work.

= http://aescripts.com/ft-effect-instance/

Drew

newtonscannon.com

Just a guy made of dots and lines.

On Fri, Jun 7, 2013 at 3:30 AM, Mathias M= =F6hl <mamo181@googlemail.com> wrote:
=20 =20 =20
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

--
mamow= orld.com
tools & tutorials for After Effects

dr. mathias m=F6hl
kapellenweg 36, 79100 freiburg, germany
phone +49 (0)761 - 4774 584
info@mamo= world.com



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

--001a11c1c5568293e604de81401d
Content-Type: text/plain; charset=3DISO-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 perfec=
tly
fine on our boxes.  It simply seems that Tiffen didn't implement any wa=
y
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!





--
Mark Walczak
-------------------
Vimeo: http://vimeo.com/mdwalczak
= LinkedIn: http://www.li= nkedin.com/in/mdwalczak
--047d7b41419428c0c304de916e9f--