From: "Jim Curtis" Received: from production003.einsteinsname02.net ([67.228.43.50] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP-TLS id 5546383 for AE-List@media-motion.tv; Mon, 11 Aug 2014 19:30:19 +0200 Received: from 99-152-153-100.lightspeed.dllstx.sbcglobal.net ([99.152.153.100]:51097 helo=[192.168.1.68]) by production003.einsteinsname02.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.82) (envelope-from ) id 1XGtQH-0002mp-9p for AE-List@media-motion.tv; Mon, 11 Aug 2014 12:30:17 -0500 Content-Type: multipart/alternative; boundary="Apple-Mail=_6F22D0C9-495B-422A-A91D-BF5437B8C617" Message-Id: <3FB2C56F-287D-403B-929C-A751DA9C028D@me.com> Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: [AE] Premiere Question Date: Mon, 11 Aug 2014 12:30:16 -0500 References: To: After Effects Mail List In-Reply-To: X-Mailer: Apple Mail (2.1510) X-EinsteinsEyes-MailScanner-Information: Please contact the ISP for more information X-EinsteinsEyes-MailScanner-ID: 1XGtQH-0002mp-9p X-EinsteinsEyes-MailScanner: Not scanned: please contact your Internet E-Mail Service Provider for details X-EinsteinsEyes-MailScanner-SpamCheck: X-EinsteinsEyes-MailScanner-From: jpcurtis@me.com X-Spam-Status: No X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - production003.einsteinsname02.net X-AntiAbuse: Original Domain - media-motion.tv X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - me.com X-Get-Message-Sender-Via: production003.einsteinsname02.net: authenticated_id: jim@hartprods.com X-Source: X-Source-Args: X-Source-Dir: --Apple-Mail=_6F22D0C9-495B-422A-A91D-BF5437B8C617 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 I'm still not getting all the list emails, and haven't seen Teddy's = answer; so excuse if this is redundant. Pr on Mac has an uncanny ability to corrupt its own prefs often. = Deleting or refreshing them fixes 96% of my Pr issues. Other things = that help are trashing Previews and Media Caches. Corrupt media is the = next thing I check (using Digital Rebellion's Corrupt Clip Finder). =20 Failed exports can result from a corruption on a clip effect. = Re-appying the effect has fixed it. My experience: No. 1 cause of Project corruption seems to be use of the = Warp Stabilizer. When I use that, I export the stabilized clip; import = the render into Pr, then delete the Warp Stabilization (Those also bloat = Project file size.). Otherwise, Pr CC has been extremely stable and dependable for me... Up until I discovered a new bug with the latest revs of CC 2014 of Pr = and Ae, though. Re-rendering a clip that's in an open Pr Sequence = crashes Pr. So, I have to close my Project before re-rendering a clip = in Ae; then re-open it on completion. On Aug 11, 2014, at 12:11 PM, John Morgan = wrote: > Was out all last week. I agree with Teddy=92s answer, but will add = another angle: failed installation or update might cause what you=92re = seeing. > I=92ve never seen this kind of behavior in a normally-functioning CC = install, but HAVE seen some really weird playhead probs happen from a = failed update. But if the prob is consistent from CS6 to CC, probably = hardware related. > J > =20 > From: After Effects Mail List [mailto:AE-List@media-motion.tv]=20 > Sent: Sunday, August 03, 2014 11:27 AM > To: After Effects Mail List > Subject: [AE] Premiere Question > =20 > Hello, > =20 > I know we had some lengthy discussions on Premiere Pro over the past = couple weeks. I can't seem to get any consistent operation from this = program. The most annoying two things I keep getting (across CS6 through = CC 2014) is failed imports even when the file has been imported before. = For whatever reason, restarting the program generally fixes that. = Second, it constantly says files media is offline and I can't figure out = what the heck is going on. One time it will play and then I go back and = it says they are offline and see no image/video. > =20 > Are there any obvious fixes, settings that will help on this? > =20 > Thanks, > Eric > =20 > -- > Eric D. Kirk | Kirk Productions > Hidden in the Woods | VFX > The Night Visitor | VFX > 443.206.1347 > www.kirkproductions.com > kirkproductions@gmail.com > IMDB: http://www.imdb.com/name/nm3351363/ > =20 >=20 > This message, and any attachments, is intended only for the use of the = addressee and may contain information that is privileged and = confidential or otherwise exempt from disclosure under applicable law. = If the reader of this e-mail is not the intended recipient, you are = hereby notified that any unauthorized use, dissemination, distribution = or reproduction of this message is prohibited. If you have received this = communication in error, please notify the sender by return e-mail and = delete this e-mail and any attachments from your system. =AD=AD =20 --Apple-Mail=_6F22D0C9-495B-422A-A91D-BF5437B8C617 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252 I'm still not getting all the = list emails, and haven't seen Teddy's answer; so excuse if this is = redundant.

Pr on Mac has an uncanny ability to = corrupt its own prefs often.  Deleting or refreshing them fixes 96% = of my Pr issues.  Other things that help are trashing Previews and = Media Caches.  Corrupt media is the next thing I check (using = Digital Rebellion's Corrupt Clip Finder). =  

Failed exports can result from a = corruption on a clip effect.  Re-appying the effect has fixed = it.

My experience:  No. 1 cause of Project = corruption seems to be use of the Warp Stabilizer.  When I use = that, I export the stabilized clip; import the render into Pr, then = delete the Warp Stabilization (Those also bloat Project file = size.).

Otherwise, Pr CC has been extremely = stable and dependable for me...

Up until I = discovered a new bug with the latest revs of CC 2014 of Pr and Ae, = though.  Re-rendering a clip that's in an open Pr Sequence crashes = Pr.  So, I have to close my Project before re-rendering a clip in = Ae; then re-open it on = completion.



On Aug = 11, 2014, at 12:11 PM, John Morgan <AE-List@media-motion.tv> = wrote:

Was out all last week. I agree with Teddy=92s = answer, but will add another angle:  failed installation or update = might cause what you=92re seeing.
I=92ve never seen this = kind of behavior in a normally-functioning CC install, but HAVE seen = some really weird playhead probs happen from a failed update.  But = if the prob is consistent from CS6 to CC, probably hardware = related.
J