Thanks, Jim.  I just remembered that setting.  I inherited a project from another editor, and that's how my renders ended up in the default location.  Derp. ... View more

You may have inadvertently answered a question I have.  I'm having some issues with 12.0.1 (Mac) and was thinking about un and reinstalling the app, but I don't want to be stuck with 12.1.  If 12.0.1 is still an option in the CC apps installer, I may give it a try.  I'm in the middle of a big project, and am not ready to brave 12.1, especially given the reports of how FUBAR it is on Macs. ... View more

Use Dynamic Link to take your Seq into Ae, and export from there, using the Output module settings for DNx with alpha. ... View more

I'm on a MacPro3,1 (2008) running 10.11.6, and since updating the latest CUDA driver (I use the OSX driver for my GPU; NOT the ones from Nvidia, which continue to be awful), I'm able to report no issues thus far working on a revision to a project for a big box retailer from about a year ago that was started on an earlier version of Pr.  Footage is a grab back of file types, but mostly mp4 variants and ProRes.  Video Effects are limited to color grading effects and crops.  The only Audio effect I'm using is SoundSoap, a nifty real-time BBNR. I updated another project that was all ProRes and had a host of problems, which seems counter-intuitive, other than the fact there was a lot of UltraKey and secondary color grading with tracking masks.  I tracked one crashing issue down to unrendered use of Gaussian Blur on a mask.  When I deleted the effect, the crashing stopped. Count me as "cautiously optimistic" that Pr CC 2017 is ready for professional use. ... View more

New Pr CC 2017 11.0.1 shows an improvement in Open CL Preview option.  My RAM usage doesn't max out as before, which means the app doesn't crash while playing. However, enabling CUDA brings back the RAM maxing, and crashing while playing. I guess that's progress.  I might try it out on a paying job with Open CL Previews.  Wish me luck. ... View more

Moderator: title changed for better search ability. The title change doesn't even come close to reflecting the issues I explained in my original post. I'll recap:  Pr CC 2017 is not ready for professional use. If you rely on Pr for your business, CC 2015.2 (9.2.0) is likely your best option. ... View more

RameezKhan wrote: Hi Jim, Sorry for my delayed response! I wanted to report back on my results after changing this setting to Memory. It helps a lot! Thanks for reporting back. Really appreciated! I'm glad that it helped. Note that this success story is on Open CL ONLY. When I switch to CUDA, I see my Program screen go black on several clips, but come back on others. I don't see a rhyme or reason though. Some clips that go black just have one Lumetri on them. If it's CUDA only, I suspect it to be the video driver. Just a wild guess though! Because I don't get this behavior in Pr 2015.2, but do get it in 2015.4 and now 2017, my educated guess is that this is still a software problem in Premiere that needs fixing. Are you comparing the same project in all the 3 versions? Additionally, I'd advice you to file a bug report here: Bug Report Form Note that you won't necessarily get a response to that report, but, they are surely checked by the engineers themselves. Best, Rameez Hi Rameez, To answer your question, yes, I have described this behavior for three versions.  On 2015.2, the memory fills up to 100%, but my video does NOT go black, and the app does NOT crash after my RAM is 100% used.  It just starts dropping frames and overall performance gets laggy. I have similar problems with 2015.4 and 2017.  In both versions, the Program screen (and Mercury Transmit) will go black, and can only be brought back by quitting and relaunching Premiere.  And so far, 2017 is the only version that both loses video and crashes.  And 2017 is the version where switching to Open CL shows improvement in my experience so far. All due respect, your guess about it being a driver issue seems to be disputed by the fact that my issues in 2014.2 are almost non-existent, with the exception that I have to manually purge the RAM to bring back good functioning when it starts dropping frames or gets laggy.  I have the same driver installed, no matter which version of Pr I am running.  Seems to me if it was a driver issue, the problem would manifest in all versions of Pr. 2015.2 is the version I trust to get me through my paying projects, and it's CUDA enabled all the way. I will file a bug report.  Thank you. ... View more

RameezKhan wrote: Decrease the amount of RAM Adobe apps are using. Additionally, change the rendering optimization from Performance to Memory. Hi Rameez, I wanted to report back on my results after changing this setting to Memory.  It helps a lot! I just played my entire Sequence without Pr crashing.  Memory varies between 70-something and 100%, and doesn't stay on 100% for long.  I'm still seeing a lot of frames dropping, but I've got a lot of effects, including Ultra Key, several instances of two Lumetris (a primary and secondary with masks), etc. that are pushing the app pretty hard. Note that this success story is on Open CL ONLY.  When I switch to CUDA, I see my Program screen go black on several clips, but come back on others.  I don't see a rhyme or reason though.  Some clips that go black just have one Lumetri on them.  Because I don't get this behavior in Pr 2015.2, but do get it in 2015.4 and now 2017, my educated guess is that this is still a software problem in Premiere that needs fixing. It might be helpful to point out that I've done a few VERY simple projects (cuts and dissolves; titles) in Pr 2015.4 and not had problems.  The problems I've had have started when I start adding effects to my Sequences.  I hope that helps. Jim ... View more

RameezKhan wrote: Jim, thanks for a detailed post. My pleasure! I did as you suggested and deleted all my Media Cache files. Did you clean the cache files within Premiere Pro preferences or did you manually delete the files? I do both.   Within Ae and Pr Preferences, we can Browse for a location for our Cache files.  I use a very fast external RAID, and I choose them to go there. Pr is still ignoring the location I select and putting some files in my selected location, and others in my Library>Application Support>Adobe>Common>Media Cache Files folder. Did you change the location of both Media Cache Files and Media Cache Database? Yes, both as I described above.  If I happen to launch Pr and my RAID (or just the Cache partition I selected) is off-line, Pr automatically resets the Cache locations to the default path on my boot drive (Library>Application Support>Adobe>Common>Media Cache Files folder). I also have to reset my Cache locations again every time I delete Pr Preferences (which is something I've had to do less and less since Pr 2015 came out.  Thanks for that!). Pr is still ignoring the location I select and putting some files in my selected location, and others in my Library>Application Support>Adobe>Common>Media Cache Files folder. Which OS are you on? I'll try to repro this on my machine and see if I get the same result. I'm on 10.11.6 now, but this has been going on for several OS versions, and as far back as Pr CS6.  Todd Kopriva, an Ae guy of years past told me that Adobe has this done intentionally, as there is some method to having a shared location.  I didn't like it then, and I still don't. Anyway, taking your advice and deleting all the cache files hasn't helped at all. Pr still stops displaying video and/or crashes if I let it play after my RAM meter is showing 100" usage. Do you get a specific error message? If you've a crash log, that would be helpful. Have you installed any third party plugins for Premiere Pro? About your advice not to let my RAM usage get so high, that's not even anything under my control. I meant this: Decrease the amount of RAM Adobe apps are using. Additionally, change the rendering optimization from Performance to Memory. I usually set this to 4 or GB, but the latest versions of Pr and AE, it Defaults to 6, and so I leave it there.  I have 32 GB of RAM.  I've experimented with toggling between Performance and Memory, and can't tell a difference; but I'm depending on my memory here, too.  I haven't noticed a trend, but I'll try your suggestion of using Memory. What are your computer specs? MacPro3,1 - 32G RAM - Nvidia Quadro K5000 GPU (latest CUDA driver 8.0.51 / Mac OSX video driver) - 10.11.6  - Projects, Media and the Caches I select are all on and ATTO SAS RAID 16TB (500MB to 2GBs reads and writes) As a freelance editor, I get a variety of source media types: AVC, H.264, Sony, Canon, RED, Alexa.  I haven't tried all these formats on the new build of Pr yet, though. Again, thank you for your reply here. Jim ... View more

Hi Rameez, Thank you for addressing my post. I did as you suggested and deleted all my Media Cache files. Pr is still ignoring the location I select and putting some files in my selected location, and others in my Library>Application Support>Adobe>Common>Media Cache Files folder. I wish you all would fix that.  I bet a lot of your customers don't realize their boot disk is being bloated with cache files that they don't know about on projects completed long ago.*  More about this below. (Workaround:  I've set up aliases to those folders (There's one folder for each major version of Pr on your system.) on my Desktop, and I delete the contents manually periodically.) Anyway, taking your advice and deleting all the cache files hasn't helped at all.  Pr still stops displaying video and/or crashes if I let it play after my RAM meter is showing 100" usage. About your advice not to let my RAM usage get so high, that's not even anything under my control. Pr takes all the RAM all on its own without any way for me to avoid it, other than watching it constantly instead of my video, and using the Terminal sudo purge command to purge unused RAM.  Pr should have a routine built in that purges unused RAM constantly. I need to correct an error I made on my OP:  My source files for this project are ProRes, not the H.264 I first mentioned.  They started as H.264, but I transcoded them.  I expect poor performance from H.264 sources, but not ProRes. Chapter Two As another test, I opened a recent project that had XMF media from a Sony camera.  On this project, I had better results.  Although my RAM usage would periodically peak at 100%, it would also then go down and fluctuate between 70 and 100, and I got no crashing or video outages.  I infer that the type of media plays a role in this memory issue. BTW, I have slightly better luck choosing Open CL and not CUDA in the Project Settings (meaning the crashes come later).  When Pr has crashed, my Digital Rebellion Crash Reporter has fingered the graphics card.  I have the NVidia Quadro K5000 for Mac installed, and I suspect their Mac support is terrible.  I use the OSX driver, not the Nvidia Web Driver, which I have determined has been a source of a series of Kernel Panics I've kept to a minimum by not using them (any version - all bad).  So, I acknowledge that my problems, and those of people in my situation may be due to an incompatibility with third party hardware or their drivers.  This is an issue inherent with all NLEs and DAWs that depend on third party hardware.  And it's also a source for a lot of finger pointing.  This is the reason Avid started out selling bundled systems with specific approved hardware only. * You guys have also not fixed the behavior that if I create separate cache folders for Ae and Pr, they all go into the last one I selected in either app.  This is a major productivity killer.  I prefer to delete the caches (which add up to multiple GBs) after each Ae session, but I want to keep my Pr caches around for the entirety of the project (until I start having problems and deleting them and my prefs are the first order of attempts to fix).  This "feature" you have of a shared cache location is very inconvenient. Regards, Jim ... View more

Looks like thumbs down for CC 2017 ... View more

I'm a full time editor who works from home 30-60 hours a week using Adobe products. I wish Adobe would stop adding new features before they fix what is broken. It's absolutely pointless to add features to a tool that nobody wants to use. Pr 10.4.0 and Ae 13.8.1 was a major flop for me and many other users here.  If this new version isn't rock solid, it's going to create a major opportunity for BMD or other company to swoop in and take Adobe's Pr customers.  Enough is enough. I'm downloading the new apps now, and I'll dip my toes in on a non-paying job.  But, we're getting dangerously close to instituting a Three Strikes Rule. ... View more

Adobe doesn't typically say when new versions are coming, unless they're imminent - days away. Work with 2015.2, and cross your fingers that the next release works.  Use XML to go backwards. 2015.4 works OK for me on VERY simple projects.  It starts acting up when I start adding video layers and effects. I'm fairly convinced conflicts with my NVidia card is the root of my issues. ... View more

You have every right to be frustrated.  We pay money, they take it, and we are entitled to working software. I worked for Avid for a while in the 90s, when NLEs were new to post-production.  What I learned is that NLEs are probably one of the most resource intensive apps that people run on desktops.  They use a computer's audio, video, io, GPU, and CPU resources to the hilt.  They are very complicated.  All those things have to work together.  The reason that Avid stuck to their own configurations for so long was because they could support a limited amount of hardware far better than every possible configuration of boxes, accessories, peripherals, OS, drivers, etc. out there. I'd dare say that most of the issues people have with Pr are not caused by the Pr app, but rather drivers, etc. from third parties.  I've tracked most of my issues down to conflicts with my Nvidia card and it's manufacturer provided drivers.  My second most frequent source of problems is from corrupted media, which drives Pr bonkers. I'd also say that most people who say "I've tried everything" haven't.  That's because of what I just wrote up there, about NLEs being complicated and using all a computer's resources, and the potential for conflicts. This isn't to say that Pr isn't often buggy, and Adobe doesn't release versions that aren't ready.  It happens.  I edit for a living, and at least I'm happy there is a version that is stable on my hardware.  I use the latest build for my personal projects, where a deadline and my reputation isn't on the line.  Working at a slower pace helps me to see if there's a cause and effect for the problems in the new versions. I've noticed that my problems start with 2015.4 when I start adding video layers to my Sequences.  Anything but cuts and dissolves brings trouble.  So, I can use 2015.4 to import, and use the nice BG transcode feature, lay out rough sequences, then use XML export to go back to 2015.2 to do my fine tuning. ... View more

I'm editing on Pr 2015.2, which is the last reliable release for me.  I have problems Dynamic Linking to its companion version of AME as well.  It just doesn't work. So, my workaround is to Export my Sequences, using Match Sequence Settings, which goes quickly because my timeline is usually rendered (my Seq Settings are ProResHQ, which is a high quality mastering codec).  I can then take that master over to AME 10.4.0, which works well on my system, and do my encoding of multiple sizes, etc. there. ... View more

See my post about purging RAM.  My guess is there is a Windows equivalent. I work on Macs.  I have a utility that puts a pie chart and percentage of RAM used on my toolbar (iStat Menus).  When I notice Pr getting sluggish (ie, timeline doesn't scrub smoothly), I look at the percentage of RAM used, and it's usually 99 or 100%.  I purge RAM, and Pr behavior goes back to normal.  The RAM gets tossed quicker with Long-GOP than intraframe, by my observations. Seems to me that Adobe could build a script into Pr that purges the RAM in the background when the computer starts running low.  ... View more

This has been an ongoing problem with Premiere over the many years I've used it.  I think it went away with the last build of CS6.  But, it's been back with CC for most of its history I'm on Mac.  When performance gets sluggish because RAM is used up, a temporary fix is to open a Terminal window, type sudo purge, and then resume work, until it happens again, which won't be long. ... View more

Of course.  How else would you know that cross dissolves don't transfer over? ... View more

Replace with After Effects Composition is ignoring Cross Dissolves when the clips are sent to Ae.  Is this normal behavior, or a new "feature?" ... View more

I keep getting these messages.  I'd be willing to be $100 that your problem is a driver conflict, or you upgraded your OS too soon.  Pr CC 2015 is working great for many of us.  I suspect many of these "I tried everything" claims are not factual.  You haven't tried everything if you haven't reinstalled your OS, the CC suite, and your third-party drivers from the ground up.  Those are drastic measures indeed, but some times, that's the solution to get you back in business. If Pr works fine on some projects, but not on others, that casts suspicion on the media in your problem projects.  Transcoding the media in those can be a workaround.  It's not ideal in an NLE touted to work natively, but at least you'll get projects done.  I depend on Pr to make my living.  I wouldn't work with it if it was as broken as some of you describe. ... View more

An update came out today.  Fingers crossed all these playback issues have been fixed. ... View more

I just launched Ae CS6 on 10.10.4, and did a couple things with it.  Seems to be working. ... View more

Cineform is now included in Pr CC 2014 (8.1?  Maybe 8.0 as well. Can't remember.). It's a pretty nice cross-platform codec.  Supports alpha, too. ... View more