Return-Path: Received: from nk11p00mm-asmtp002.mac.com ([17.158.161.1] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP id 5414365 for AE-List@media-motion.tv; Sun, 23 Mar 2014 01:18:27 +0100 MIME-version: 1.0 Content-type: multipart/alternative; boundary="Boundary_(ID_AXqJz7XxOFKBBtCz/Idg8Q)" Received: from [192.168.1.68] (99-152-153-100.lightspeed.dllstx.sbcglobal.net [99.152.153.100]) by nk11p00mm-asmtp002.mac.com (Oracle Communications Messaging Server 7u4-27.08(7.0.4.27.7) 64bit (built Aug 22 2013)) with ESMTPSA id <0N2V0022U4VV3440@nk11p00mm-asmtp002.mac.com> for AE-List@media-motion.tv; Sun, 23 Mar 2014 00:19:09 +0000 (GMT) From: Jim Curtis Message-id: <441E04EC-94DE-4BB8-8728-FBCA450ABFCA@me.com> Subject: Re: [AE] Adobe Premier Importing Problem Date: Sat, 22 Mar 2014 19:19:07 -0500 References: To: After Effects Mail List In-reply-to: X-Mailer: Apple Mail (2.1510) x-icloud-spam-score: 34444444 f=me.com;e=me.com;is=no;ir=yes;pp=ham;spf=n/a;dkim=n/a;dmarc=n/a;wl=n/a;pwl=n/a;clxs=n/a;clxl=n/a X-MANTSH: 1TEIXREEbG1oaGkdHB0lGUkdDRl5PWBoaGBEKTEMXGx0EGx8SBBscHwQdGxAbHho fGhEKWE0XSxEKbX4XGhEKTFkXGxobGxEKWUkXEQpZXhdoY3kRCkNOF0sbGxpiTk0ZBBtCQxl4c wcYZBoaGxMTGxEKWFwXGQQaBB0HTUsdEkhJHEwFGx0EGx8SBBscHwQdGxAbHhofGxEKXlkXYXM SGnMRCkxGF2JraxEKQ1oXExMEGx8YBBsfGQQbGhoRCkJGF2MYfGl4eFlIelsBEQpCRRdnehJTf BJwUx1uHhEKQk4XbHBgeUAdYlJpGmIRCkJMF2sdUhoFH0JDGEEcEQpCbBdlHHJHZ39PWmVgZhE KQkAXYFMYTkxeYR0fRRkRCkJYF2lhQ25nW155XkRyEQpwZxdpTn5dRWZPc2VeXxEKcGgXaGZ8Q n5CARNkeUsRCnBoF20TXGJaZQVNf2MeEQpwaBdpb0AaUmBicFNzYxEKcGgXbVgSSFJNTXpOb0U RCnBoF2tOcFhnaEFJSWEdEQpwZxdlfF0bXkFBbUhCfxEKcGwXel99Y0xHc1hicEsRCnBMF25kS VweYWcTSG9vEQ== X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.11.87,1.0.14,0.0.0000 definitions=2014-03-22_03:2014-03-21,2014-03-22,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=2 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1403220183 --Boundary_(ID_AXqJz7XxOFKBBtCz/Idg8Q) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT The memory leaks have also been improved on Pr CC. I used to keep the Console and Activity Monitor open, and enter purge whenever the inactive RAM took up all the free RAM. That was a big problem in Mac CS6. I had to purge often. Having no free RAM left didn't cause crashes, but rather very sluggish performance. On Mar 22, 2014, at 3:15 PM, Carey Dissmore wrote: > I have painfully experienced this recently when I was taking projects I cut on a remote mac-based edit system with one set of drives, and moving them to my best PC based workstation. These projects were not super large (by my standards) but were certainly pretty big and had perhaps 15 timelines and 10 hours of footage. (mine can get much larger). > > That section of the codebase seems really quirky and a bit shaky. Multiple attempts sometimes get you there, other times I have to cancel out of the auto relink process and let the project open disconnected, then painstakingly select smaller subsets of media at a time and relink them. That seems to keep it from bumping into various errors and complete chokes. > > For reference, the machine in question has 64GB of RAM, and a 6-core i7 running at 4Ghz. > carey > > On Mar 22, 2014, at 1:16 PM, Stephen van Vuuren wrote: > >> Premiere (C6 through latest CC) is prone to severe memory links when relinking and importing footage on very large projects. You might doing some testing to see if memory issues are present. > --Boundary_(ID_AXqJz7XxOFKBBtCz/Idg8Q) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable The = memory leaks have also been improved on Pr CC.

I used = to keep the Console and Activity Monitor open, and enter purge whenever = the inactive RAM took up all the free RAM. That was a big problem = in Mac CS6. I had to purge often. Having no free RAM left = didn't cause crashes, but rather very sluggish = performance.

On = Mar 22, 2014, at 3:15 PM, Carey Dissmore <carey@imugonline.com> = wrote:

I have = painfully experienced this recently when I was taking projects I cut on = a remote mac-based edit system with one set of drives, and moving them = to my best PC based workstation. These projects were not super large (by = my standards) but were certainly pretty big and had perhaps 15 timelines = and 10 hours of footage. (mine can get much = larger).

That section of the codebase seems really = quirky and a bit shaky. Multiple attempts sometimes get you there, other = times I have to cancel out of the auto relink process and let the = project open disconnected, then painstakingly select smaller subsets of = media at a time and relink them. That seems to keep it from bumping into = various errors and complete chokes.

For = reference, the machine in question has 64GB of RAM, and a 6-core i7 = running at = 4Ghz.
carey

On Mar = 22, 2014, at 1:16 PM, Stephen van Vuuren <stephen@sv2studios.com> = wrote:

Premiere (C6 through latest CC) is prone to severe memory links = when relinking and importing footage on very large projects. You might = doing some testing to see if memory issues are = present.

<= /div>= --Boundary_(ID_AXqJz7XxOFKBBtCz/Idg8Q)--