From: "Jim Curtis" Received: from sonic311-29.consmr.mail.gq1.yahoo.com ([98.137.65.210] verified) by media-motion.tv (CommuniGate Pro SMTP 6.1.0) with ESMTP id 6391254 for AE-List@media-motion.tv; Sat, 20 Jan 2018 00:05:37 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=flash.net; s=s2048; t=1516403291; bh=antXeZyaC2g/h4gQNpfUZyPfg7g+3sHDm9DtpCEUC8s=; h=Subject:From:In-Reply-To:Date:References:To:From:Subject; b=g8L9j2rNUUiutxI3zQCnEfIuVil7tWApuG7IRFIFKVGjsbmibaZYZ4BuEAeEpCFCr/jZYCkNsSgn0UqbwPwrCFIdjHaKt5yCo2wS2wAVX9sbtypB/qZA2/mcAlKc38T5hoB/NsmD+qGiWAOUzUhqfhbcxIvKiMsnhGnlD6kMae2snA7SZUK9cR0jo0YKC/cWB8/mY+y4Ks7Zi7CI0LzCu3DVjrmdnGHCDVe298ZF6WTOEGLiaQGfzEuHl/fJ9MTr2cNJ2ENi3ct5zhMv5c47+nU4Gwg7l5ArFzad+QjlbtVcYU9ehT6xZvdqsvt/PQibDTtQP3lNlWEJBQ5RzLWaHw== X-YMail-OSG: gTf9bmcVM1n_4FttFzY59nLkVZ43nXG7oENl9eKsyxt6qAz.GBlNfmquj71q3gD R6i7lzU5RR8jRyn9VbbWE0oEWhtx_JQNoQJ1DKi2NKS8ABjrGaHl1V40uZqO6rp26vBEgWgd0dBP za3ri2E8n4ehnSKkKULsLLAOYjwGzTwbvWY1g4i81fqOuiSsYfo2AspQFHXE56EU6pnVPZTP2nPT H9XiTXxBsBMhdvwF4IT7cB0V.TQxdlg5fvm6OeWRiU4aSheEcOFuVcl1LFMbC9YB9.ZLjxhPOpa0 Kha7Y7PXcJqwaIx281sosEwW3yJsgAYju.9_zIgA4TMLi4gjyMZoBWqBhhhJJrJxbm7FGMjML170 mzqF57b3OGHQW049BgYt2Cn4ZRt8XTPFCzZS4iLTekO5.IxzXR8tEVglp4njC_tdPrCIXeILP4Yq 4PSvP_amw9RbHyObU4nRmmTOrBPV.8bSW3BZ1aptUiEhkzcCYuFqQsQqfUIGjrzCHN_cNvJbDyjm RCezatPG53aIbkG86pJZLnlA2smj4EcJZgBNcSFY.b9vZbE2d Received: from sonic.gate.mail.ne1.yahoo.com by sonic311.consmr.mail.gq1.yahoo.com with HTTP; Fri, 19 Jan 2018 23:08:11 +0000 Received: from smtp105.rhel.mail.gq1.yahoo.com (EHLO jims-mac-pro.attlocal.net) ([68.180.227.8]) by smtp403.mail.gq1.yahoo.com (JAMES SMTP Server ) with ESMTPA ID dd422008085ef1a092b9b7c567f7e37d for ; Fri, 19 Jan 2018 23:08:09 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: [AE] Premiere/AE/Audition and the missing Dolby audio decoder In-Reply-To: Date: Fri, 19 Jan 2018 17:08:07 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <1AF24EBD-6EFA-4AFD-A86A-29AFA0F0C053@flash.net> References: To: After Effects Mail List X-Mailer: Apple Mail (2.3124) I=E2=80=99ve had some problems two or three times that a reinstall of = the app cleared right up. When the app starts acting differently than = it should, and not crashing, that=E2=80=99s usually a prefs or corrupt = app issue. NVidia seems to be the source of my problems. I have a Titan as well, = and I=E2=80=99ve gotten multiple Kernel Panics when it gets hot. I use = a fan utility now to ramp up the fans when doing renders that tax the = GPU. That solves the KP issue. The Titan is a mixture of pleasure and = pain. =20 And like you, Pr on my MBP rarely if ever crashes. But, I don=E2=80=99t = really edit that much on it. Mostly on remote, on-site event recaps, = that I don=E2=80=99t do much of any longer. Corrupt media also caused Avid MC to go nuts when I was using that, = which has been about 15 years. That may happen across all NLEs. I=E2=80=99= ve devised a =E2=80=9Csearch and destroy=E2=80=9D technique to find it - = keep removing media until it stops crashing, the last batch I removed = contains the corruption. Also, Digital Rebellion=E2=80=99s Corrupt Clip = Finder works well. However, it used to tag all stills over a certain = dimension. I think that=E2=80=99s been fixed. =20 Also, Pr used to crash at very large JPEG stills, and the fix was to = turn them into TIFs, or just downscale them by 50%. That may have been = fixed in a Pr update. Haven=E2=80=99t experienced it lately. I have a concern that if my prefs get corrupted, the app is saving them = to the cloud, which is no good at all. Here=E2=80=99s a tip. Locate your CC Profile folder that contains the = Pr prefs, and make an alias to your desktop. Start with a totally clean = set of prefs the way you like them, and then zip the file in the Profile = folder. That way, you can restore them by opening the alias, trashing = the prefs, and unzipping your clean copy. By and large, the most trouble I=E2=80=99ve had with Pr has been in = large projects, with different types of footage and codecs in the same = timeline. =20 And if I can ever find the dude who invented the AVCHD codec, I will = kick him in the balls. > On Jan 19, 2018, at 4:46 PM, Steve Oakley = wrote: >=20 > I have a project that I=E2=80=99ve tried to purify. reimported into = new project, even exported to XML and imported that into new project, = still highly unstable and crashy. thankfully delivered and done for over = a year now, so I don=E2=80=99t have to deal with it.=20 >=20 > media is fine. thats generally easy to find because you crash playing = or doing things with that one clip, or clips from a particular folder.=20= >=20 > nVidia driver is more interesting. I do installs often enough through = regular updates though that its probably low on my list but a good / = fast / easy one to do. >=20 > PP prefs. ugh. perhaps cloud prefs are the source of re-occuring = problems. maybe I=E2=80=99ll nuke everything prefs and see if that = matters. >=20 > App reinstall I=E2=80=99ve done, never made a difference for me. >=20 > if anything, I=E2=80=99ve almost come to suspect nVidia related things = and that AMD is more stable. my laptop seems to be more stable than my = tower with Titan X. >=20 > what I will say is I=E2=80=99ve spent days trying some other things = like trashing all the house keeping files / caches, new projects, copy = and paste into new TL=E2=80=99s, pretty much to no avail. I think old = projects have some weird bits to them that newer vers don=E2=80=99t like = and don=E2=80=99t have code to detect the problems and fix. what we need = is a project purifier that filters a project for questionable things and = fixes them. I realize that might mean your project gets changed, but = I=E2=80=99d rather have warning of items that changed and need to be = fixed than I can=E2=80=99t get work done. well I have, export to XML and = go to FCP X or resolve to finish it. >=20 > S >=20 >=20 >=20 >> On Jan 19, 2018, at 2:56 PM, Jim Curtis = wrote: >>=20 >> FWIW, I=E2=80=99ve tracked down ALL my issues with PP to usually one = of these things: >>=20 >> - corrupt media. Remove or transcode to a different codec. >> - Nvidia driver corruption. Reinstall. (One time I had to wait a few = days for a driver update to fix a known issue.) >> - Pr preferences corruption. Reset >> - app corruption. Reinstall >> - an effect or transition has become corrupted. Remove and replace. >> - project corruption. Import the =E2=80=9Cbad=E2=80=9D Project into = a New Project. >> - Sequence corruption. Copy from the =E2=80=9Cbad" and paste into a = new sequence. >>=20 >> If necessary, follow all steps. >>=20 >> So far, Zeus willing, I=E2=80=99ve been able to finish every job = I=E2=80=99ve started in every version of Premiere since CS 5.5. Some = versions have been more buggy than others. =20 >>=20 >> CC18 has been outstanding for me on my Mac. I have a client with = Windows systems - I don=E2=80=99t know what OS version, but there have = been problems there too, with cc18. Mostly crashing. >>=20 >> Worst perp, in my experience is corrupted prefs and media. >>=20 >>=20 >>> On Jan 19, 2018, at 1:51 PM, Steve Oakley = wrote: >>>=20 >>> My experience on PP 2018 is that it took me no less than 5 minutes = to crash it. Opening up previous projects for updates isn=E2=80=99t = pretty as those are super easy to crash with. doing simple stuff like = adding an transition crashes.I=E2=80=99ve heard similar tales from PC = users. Some people seem to have stable installs, some don=E2=80=99t. = There doesn=E2=80=99t seem to be commonality to it. Even new clean = projects can be crashers, so I gave up and moved on. sad but when you = just need to get things done rather then send crash logs off=E2=80=A6 = you do what you need to do.=20 >>=20 >>=20 >> . >> +---End of message---+ >> To unsubscribe send any message to >=20 >=20 > +---End of message---+ > To unsubscribe send any message to