Return-Path: Received: from rotring.dds.nl ([85.17.178.138] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP id 4870308 for AE-List@media-motion.tv; Fri, 12 Oct 2012 20:31:52 +0200 Received: from localhost (localhost [127.0.0.1]) by rotring.dds.nl (Postfix) with ESMTP id 1E2FC58D53 for ; Fri, 12 Oct 2012 20:34:06 +0200 (CEST) Received: from [192.168.1.108] (d39155.upc-d.chello.nl [213.46.39.155]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by rotring.dds.nl (Postfix) with ESMTPSA id 0E2C258D3F for ; Fri, 12 Oct 2012 20:33:59 +0200 (CEST) From: coen Content-Type: multipart/alternative; boundary="Apple-Mail=_AF6400FA-5708-426E-A0DF-EA8D55FEDC81" Message-Id: <902B9AB5-5AFD-4C26-845F-6F7B549612CC@dds.nl> Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: [AE] [AE] Disc Cache bug fix? Date: Fri, 12 Oct 2012 20:33:59 +0200 References: To: "After Effects Mail List" In-Reply-To: X-Mailer: Apple Mail (2.1499) X-Virus-Scanned: clamav-milter 0.97.5 at rotring X-Virus-Status: Clean --Apple-Mail=_AF6400FA-5708-426E-A0DF-EA8D55FEDC81 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 Yup, tried most of that, purging everything. Imported the project into a = new project. Put the audio into a comp of it's own. Preview didn't work well then, = works well now after the update.=20 As said earlier, all was fine till after working maybe one week on this = project. Working at 48 khz btw. What's maybe not so regular is how I started the project. It's a fcp = xml, that I imported into premiere. I had to export the edit in premiere to fcp xml again and reimport that = into premiere. ( otherwise premiere would crash on the copy part below) I copy pasted the clips from premiere into AE and all was great till = till this preview blues started when I was well on my way. I'll leave it for what it is since I'm hours from the deadline and have = managed so far :) ------------------------------------ KEYFRAMES Motion Graphics Design Damrak 68-2 1012 LM Amsterdam tel 06 1092 1603 ------------------------------------ On 12Oct, 2012, at 8:07 PM, Greg Balint wrote: > Wiped media cache in settings?=20 >=20 > Also, does this happen if you create a new project and just import = that one file into a comp and preview? >=20 > You working at 48khz or 44.1? >=20 >=20 > ////Greg Balint > ///Art Director / Motion Graphic Designer > delRAZOR.com/ >=20 > On Friday, October 12, 2012 at 1:19 PM, coen wrote: >=20 >> I hadn't tried wav, just tried but alas... >>=20 >> This started happening midway a project with an audio file that = worked fine before=85 >> It's somewhat a large project. 12 minutes, 300+ layers in the main = comp itself. >> But never much going on at the same time, 6 layers stacked at the = most. >> And as said before, switching off the audio solves my problems. >>=20 >> As a work around a render to a images sequence, and use premiere as = my viewer when I need the audio. >> Not ideal, but workable.. >>=20 >>=20 >>=20 >> On 12Oct, 2012, at 6:41 PM, Greg Balint wrote: >>=20 >>> Have you tried other audio formats? Wav possibly? >>>=20 >>> ///Greg Balint >>> //Art Director / Motion Graphics Designer >>> /321.514.4839 >>> delRAZOR.com/ >>>=20 >>> On 10/12/2012 12:40 PM, coen wrote: >>>> Hi, >>>>=20 >>>> I have an issue where ram previewing with sound gives me a message = in the info panel "locking existing keyframes". >>>> I than have to wait for about 15 sec before anything happens. = Switching audio off resolves the problem. >>>> Google tells me this one has been around for a while. >>>>=20 >>>> Before the update, if I would just drop the aif into it's own = composition the problem would persist. >>>> That doesn't seem to happen now after the update. It is still a = problem in the comp that I'm working in though. >>>>=20 >>>> Cheers, >>>>=20 >>>> Coen >>>>=20 >>>>=20 >>>>> On 12Oct, 2012, at 4:46 PM, Todd Kopriva = wrote: >>>>>=20 >>>>>> Be sure to let us know whether your specific issue has been = fixed. We squashed a lot of bugs in this update, but we want to know if = we missed some. >>>>=20 >>>> +---End of message---+ >>>> To unsubscribe send any message to >>>=20 >>>=20 >>> +---End of message---+ >>> To unsubscribe send any message to >>=20 >>=20 >> +---End of message---+ >> To unsubscribe send any message to >=20 --Apple-Mail=_AF6400FA-5708-426E-A0DF-EA8D55FEDC81 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252 Yup, = tried most of that, purging everything. Imported the project into a = new project.
Put the audio into a comp of it's own. Preview didn't = work well then, works well now after the update. 
As said = earlier, all was fine till after working maybe one week on this = project.

 Working at 48 khz = btw.

What's maybe not so regular is how I started the = project. It's a fcp xml, that I imported into premiere.
I = had to export the edit in premiere to fcp xml again and reimport that = into premiere. ( otherwise premiere would crash on the copy part = below)
I copy pasted the clips from premiere into AE and all was = great till till this preview blues started when I was well on my = way.

I'll leave it for what it is since I'm = hours from the deadline and have managed so far = :)


Motion Graphics = Design
tel 06 1092 = 1603

On 12Oct, 2012, at 8:07 PM, Greg Balint <greg@delrazor.com> = wrote:

Wiped media cache in settings? 

Also, does this = happen if you create a new project and just import that one file into a = comp and preview?

You working at 48khz or 44.1?


////Greg Balint
///Art = Director / Motion Graphic Designer
delRAZOR.com/

On Friday, October 12, 2012 at 1:19 PM, coen = wrote:

I hadn't tried wav, just = tried but alas...

This started happening midway = a project with an audio file that worked fine before=85
It's = somewhat a large project. 12 minutes, 300+ layers in the main comp = itself.
But never much going on at the same time, 6 layers = stacked at the most.
And as said before, switching off the = audio solves my problems.

As a work around a = render to a images sequence, and use premiere as my viewer when I need = the audio.
Not ideal, but = workable..



On = 12Oct, 2012, at 6:41 PM, Greg Balint <greg@delrazor.com> = wrote:

Have you tried = other audio formats? Wav possibly?

///Greg = Balint
//Art Director / Motion Graphics = Designer
/321.514.4839

O= n 10/12/2012 12:40 PM, coen wrote:
Hi,

I have an issue where = ram previewing with sound gives me a message in the info panel "locking = existing keyframes".
I than have to wait for about 15 sec = before anything happens. Switching audio off resolves the = problem.
Google tells me this one has been around for a = while.

Before the update, if I would just drop = the aif into it's own composition the problem would = persist.
That doesn't seem to happen now after the update. It = is still a problem in the comp that I'm working in = though.

Cheers,

Coen


On 12Oct, = 2012, at 4:46 PM, Todd Kopriva <kopriva@adobe.com> = wrote:

Be sure to let us = know whether your specific issue has been fixed. We squashed a lot of = bugs in this update, but we want to know if we missed = some.

+---End of = message---+
To unsubscribe send any message to <ae-list-off@media-motion.tv>




=20 =20 =20 =20
=20


= --Apple-Mail=_AF6400FA-5708-426E-A0DF-EA8D55FEDC81--