Return-Path: Received: from moutng.kundenserver.de ([212.227.17.9] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP-TLS id 5237399 for AE-List@media-motion.tv; Wed, 02 Oct 2013 00:28:39 +0200 Received: from remote.animares.com (p578bf67e.dip0.t-ipconnect.de [87.139.246.126]) by mrelayeu.kundenserver.de (node=mrbap2) with ESMTP (Nemesis) id 0MOlGA-1VW6Fp0ZMs-005fhr; Wed, 02 Oct 2013 00:28:59 +0200 Received: from SERVER.animares.local ([fe80::8533:d097:c65f:118a]) by SERVER.animares.local ([fe80::8533:d097:c65f:118a%14]) with mapi id 14.01.0438.000; Wed, 2 Oct 2013 00:28:57 +0200 From: Rodrigo Olmos | ANIMA RES GmbH To: After Effects Mail List Subject: Re: [AE] response time of the interface in CC Thread-Topic: [AE] response time of the interface in CC Thread-Index: AQHOvsJZRwVBzulLIE+4g+vX87uwo5ngbbbW Date: Tue, 1 Oct 2013 22:28:56 +0000 Message-ID: References: In-Reply-To: Accept-Language: de-DE, en-US Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-Type: multipart/alternative; boundary="_000_F4DB272D30BE48C0B6AA0E89E517B458animarescom_" MIME-Version: 1.0 X-Provags-ID: V02:K0:fBB4QvB6R/DrH3IbR+gsBbrP/VEtpAjbuqq2Uwl/IU2 sut0YQnFElTBxCrYXJYxfmTqHnd4IHFKGe0cZf4MNHIYuA1xAM RemRLmGi8TEOrrpdgTWaCvhhh6ZkCqRTFufZQWDWbggq4Nu4/+ 6Ew3A+gGuwb5LQqifBSpeIrXALNnUp8QaMbSjiab3C8N2PTUff 2TKdBu5lfMRPTmrj6UNUBpdmkvzAOchtZPXauCgCwaPOUvWwPy 0AG3KsGB2QzkNnm5dXHIvZqn+vmNPo5xMIj80k7ulbInp/A/zK AZX9H2JWjws4W8n1kk0MyK/8uWXJg4b2Uw9ccv6EML46Vyk0o4 d9a2Q7lhA+RLeevlL8+6GrO5BKnU5GfxeIw8IHwAQBZNa0/gZD RwSvaME4IXwXU3OW57xcsgX+y7wnHu4PVc= --_000_F4DB272D30BE48C0B6AA0E89E517B458animarescom_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Hi Todd, thanks for your reply. I forgot to write that I tried your workaround, but = it didn't help. I=92ve verified the fix for this bug in internal builds of After Effects CC= (12.1), so I=92m confident in saying that you will have access to this fix= very soon (in a couple of weeks). That's good news. Then there is nothing I can do but wait and stick to CS6. - rodrigo Am 01.10.2013 um 18:22 schrieb "Todd Kopriva" >: There is information about how to avoid and work around this problem in the= tread that you linked to, in my first post on that thread: http://forums.adobe.com/message/5508252#5508252 =93In the meantime, here's how you should be able to mitigate the problem: Make sure that your software is installed on the fastest disk that you have= , preferably an SSD. If you don't have an SSD, then at least make sure that= your software (applications and OS) are not stored on the same drive from = which you're reading footage or to which you're writing output files. And c= ertainly don't run applications with high disk access (like WinZip or anti-= virus software that intervenes at every disk access, just for a couple of e= xamples) while you are working with After Effects. (BTW, this is all good a= dvice for high performance even without this bug.)=94 Note that the only way that we=92ve been able to reproduce this problem is = to use a very slow disk for applications or have high disk activity (contin= uous reads and writes) to the disk where the application is installed. I=92ve verified the fix for this bug in internal builds of After Effects CC= (12.1), so I=92m confident in saying that you will have access to this fix= very soon (in a couple of weeks). From: After Effects Mail List [mailto:AE-List@media-motion.tv] On Behalf Of= Rodrigo Olmos | ANIMA RES GmbH Maybe someone of you have got a workaround for it? --_000_F4DB272D30BE48C0B6AA0E89E517B458animarescom_ Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable

Hi Todd,

thanks for your reply. I for= got to write that I tried your workaround, but it didn't help.

I=92ve verified the fix for this bug in internal builds of After Effects CC= (12.1), so I=92m confident in saying that you will have access to this fix= very soon (in a couple of weeks).

That's good news. Then there is nothing I can do but wait= and stick to CS6.

- rodrigo

Am 01.10.2013 um 18:22 schrieb "Todd Kopriva" <kopriva@adobe.com>:

There is information a= bout how to avoid and work around this problem in the tread that you linked= to, in my first post on that thread:

http://forums.adobe.com/message/5508252#5508252

=93In the meantime, here's how you should b= e able to mitigate the problem:

Make sure that your software is installed on the f= astest disk that you have, preferably an SSD. If you don't have an SSD, the= n at least make sure that your software (applications and OS) are not stored on the same drive from which you're reading footage= or to which you're writing output files. And certainly don't run applicati= ons with high disk access (like WinZip or anti-virus software that interven= es at every disk access, just for a couple of examples) while you are working with After Effects. (BTW, this= is all good advice for high performance even without this bug.)=94<= o:p>

Note that the only way that we=92ve been able to reproduce this prob= lem is to use a very slow disk for applications or have high disk activity = (continuous reads and writes) to the disk where the application is installed.

I=92ve verified the fix for this bug in internal builds of After Eff= ects CC (12.1), so I=92m confident in saying that you will have access to t= his fix very soon (in a couple of weeks).

From: After Ef= fects Mail List [mailto:AE-List@= media-motion.tv] On Behalf Of Rodrigo Olmos | ANIMA RES GmbH

Maybe someone of you have got a workaround for it? <= span lang=3D"DE">

--_000_F4DB272D30BE48C0B6AA0E89E517B458animarescom_--