Delays and freezes when switching tools (CC 2017.1.2 on MacOS 10.12.5)

[Greg Janza]

[Caine Mitchell] “Premiere is a dog of an NLE, needs a complete re-write.”

The Mac experience with Premiere may get more and more frustrating due to OpenCL being inferior to CUDA.

I Hate Television. I Hate It As Much As Peanuts. But I Can’t Stop Eating Peanuts.
– Orson Welles

[Caine Mitchell]

Yep, I agree Greg. No Cuda on this machine like I had w the Mac Pro Tower.

Am keen to dive deep into Premiere plus Resolve (paid version) plus even FCX now. Just need the time! Really struggling to settle on one…and I’d really like to base my workflows going fed on just one if possible (I don’t freelance as I work direct w clients). I only really use PPro currently as it was a pretty easy migration from FCP7, plus I already pay for it and it seems a majority of post mobs / agencies / in house corporate department etc use it too so it’d be unwise to not be familiar w it.

I also struggle w going w FCX as I don’t trust that Apple won’t again neglect it’s pro app users n not support new codecs / formats etc etc as they are released in the coming yrs…of course the new mac’s they’re touting are sounding promising as we’d all agree…let’s just see what the “Apple Tax” will be on these!????

Resolve as also an NLE would be something I’d love to move to permanently! I really dig that they’ve done a lot of work on the NLE side of things including the level of audio post integration etc, plus even to the extent of how Grant Petty comes across in his preso’s when showing new products n talking about the company n products directions and their thinking…. they think like us, not like a company catering for a broad based consumer of personal products etc. Plus they seem to listen and implement based on feedback n demand n not what they want to manipulate customers into in the way that i.e. Apple forces your hand…(getting WAY off track on a rant here)… anyhow I do like where BMD have been heading w Resolve 14.

Of course to provide more “uncertainty” in the NLE I’d settle on to use predominantly looking forward I also have that gut feeling that FCX will still likely be the most responsive NLE for 4K n beyond as an NLE purely because of the 64bit architecture n code it currently employs (plus the fact that perhaps Apple will tend to favor it’s own NLE integration n supporting code over competitor’s NLE SW packages..

But really this is all speculation n here-say….I really need to just test all NLE’s n their workflows….

Either way, from recent experiences w the new top specc’d iMac I’m def not been wowed by any increase in performance inside PPro unfortunately.

…sorry for getting sidetracked here y’all!????

[Greg Janza]

hey caine, thanks for your honest thoughts. I’m sure there’s a lot of other folks out there that share your concerns.

All I can do is share my experience. I was a devout Apple user for over 20 years. And for many of those years Apple served me well. Apple was the default computer system of almost every post house that I worked for and I used it on my own projects at home so the convergence was nice.

And then in 2011, Apple makes it’s radical FCP change, infuriates its user base and Adobe perks up it’s ears to the grumblings of many within the industry. And in addition, Apple becomes primarily a phone company and professional computer development takes a backseat. Apple does release the trashcan mac but it was less than impressive. I used several trashcan macs at different post houses and I was underwhelmed.

For me personally, 2016 was the watershed year. I was working on a 2012 MBP that was maxed out and working at full capacity but I needed to update my edit system to become fully 4k compatible because I was now working almost exclusively on 4k projects. I looked at the latest offerings within the Apple portfolio and they weren’t all that impressive, with the exception of the price, which naturally was astronomical.

Through a motion graphic artist friend, I was turned onto a custom built PC. I learned that on the PC side of things there was a large amount of customization possible with motherboards, GPU’s, etc. and there was also room for future upgrading. The openness of the windows world was the exact opposite of Apple. And since Adobe CC is platform agnostic, the notion of abandoning mac became a viable thought.

And so once I got over my long developed disdain of all things PC and windows I dove in and bought a fully loaded custom built PC. I had a period in which I had to get used to the Windows environment and that was painful after 20 plus years on a mac but then I realized that the Windows environment was just fine and maybe in the larger scheme of things, even better than the OSX platform.

I have a dual setup so that if necessary I could do a FCPX project but in my market FCPX still has gained very little traction after six years. Every person decides what’s best for themselves and so I’m not making judgments on those that continue to support Apple. I’m just confirming that life indeed does go on even after leaving the fold of Apple.

I Hate Television. I Hate It As Much As Peanuts. But I Can’t Stop Eating Peanuts.
– Orson Welles

[Caine Mitchell]

Hey Greg

Thanks also for your reply. Yep as much as I can squirm about the windows ecosystem (mainly due to my own massive knowledge gap) I couldn’t agree more that a custom PC would provide some incredible options!

Thanks for the chat (we best not hijack this post any longer haha) 🙂

[Maarten Spoek]

[Kevin O'Brien] “1. Go to Premiere Pro or Edit/Preferences/media cache and clean unused.
this seemed to help a lot.”

Helped me, thanks.

[Nils Lian]

We have experienced the same issue (CC 2017.1.2 + MacOS 10.12.5 = beach balls) at our office, and wondered if anyone here knows if it has somehow been fixed with the new version that arrived earlier this October

Nils

[Kevin O’brien]

I forgot to mention that after cleaning the media cache, it appears it is best to save your project and restart Premiere.
This gets rid of the delay. I have not tried the new version because I’m currently finishing a project in the old one.

Thanks,
Kevin

[Coralee Long]

I’ve had the same problem on Premiere 2017.2 with the beachball of death, whenever switching between timeline tools. I have just upgraded to 2018 and the problem is still there. Hugely upset right now. FML. Please let me know if anyone solves this! My audio also cuts out when I make changes during playback…which was one of the best features Premiere had…until it stopped working.

Just trashed all my prefs to see if it helps. Will keep you all posted!

Mac OS 10.12.6
Mac Pro (Late 2013)
3.5GHz 6-Core Intel Xeon E5
64 GB 1866 MHz DDR3
AMD FirePro D500 3072 MB

[Kevin O’brien]

This solved it for me: In Premiere preferences, go to Media Cache and check the “Clean Unused” button, then save the project and re-start Premiere.

Thanks,
Kevin

[Sean Bates]

Kevin, you sir are a life saver. As in you saved the life of my computer which I was about to throw out the window over this issue. Did your trick and everything is working perfectly! Thanks for the tip.