| ||||||||||
| I’ve 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’s usually a prefs or corrupt app issue. NVidia seems to be the source of my problems. I have a Titan as well, and I’ve 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. And like you, Pr on my MBP rarely if ever crashes. But, I don’t really edit that much on it. Mostly on remote, on-site event recaps, that I don’t 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’ve devised a “search and destroy” technique to find it - keep removing media until it stops crashing, the last batch I removed contains the corruption. Also, Digital Rebellion’s Corrupt Clip Finder works well. However, it used to tag all stills over a certain dimension. I think that’s been fixed. 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’t 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’s 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’ve had with Pr has been in large projects, with different types of footage and codecs in the same timeline. 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 <AE-List@media-motion.tv> wrote: > > I have a project that I’ve 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’t have to deal with it. > > 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. > > 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. > > PP prefs. ugh. perhaps cloud prefs are the source of re-occuring problems. maybe I’ll nuke everything prefs and see if that matters. > > App reinstall I’ve done, never made a difference for me. > > if anything, I’ve 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. > > what I will say is I’ve spent days trying some other things like trashing all the house keeping files / caches, new projects, copy and paste into new TL’s, pretty much to no avail. I think old projects have some weird bits to them that newer vers don’t like and don’t 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’d rather have warning of items that changed and need to be fixed than I can’t get work done. well I have, export to XML and go to FCP X or resolve to finish it. > > S > > > >> On Jan 19, 2018, at 2:56 PM, Jim Curtis <AE-List@media-motion.tv> wrote: >> >> FWIW, I’ve tracked down ALL my issues with PP to usually one of these things: >> >> - 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 “bad” Project into a New Project. >> - Sequence corruption. Copy from the “bad" and paste into a new sequence. >> >> If necessary, follow all steps. >> >> So far, Zeus willing, I’ve been able to finish every job I’ve started in every version of Premiere since CS 5.5. Some versions have been more buggy than others. >> >> CC18 has been outstanding for me on my Mac. I have a client with Windows systems - I don’t know what OS version, but there have been problems there too, with cc18. Mostly crashing. >> >> Worst perp, in my experience is corrupted prefs and media. >> >> >>> On Jan 19, 2018, at 1:51 PM, Steve Oakley <AE-List@media-motion.tv> wrote: >>> >>> 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’t pretty as those are super easy to crash with. doing simple stuff like adding an transition crashes.I’ve heard similar tales from PC users. Some people seem to have stable installs, some don’t. There doesn’t 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… you do what you need to do. >> >> >> . >> +---End of message---+ >> To unsubscribe send any message to <ae-list-off@media-motion.tv> > > > +---End of message---+ > To unsubscribe send any message to <ae-list-off@media-motion.tv> |
