Skip to main content
Participant
October 9, 2018
Answered

Lag/pinwheel with every action on 2013 Mac Pro

  • October 9, 2018
  • 4 replies
  • 743 views

I am trying to edit projects that have been created 2 and 3 years ago. The projects are quite large.

Upon opening these projects, I get the mac pinwheel for a couple of seconds with each action I make i.e. clicking, scrolling, playing, etc.

It seems as though I can open these projects with no problem on my macbook pro.

This all doesn't seem to be a problem with new projects.

But this is unacceptable as I assume that I am running a very capable Mac Pro.

Mac Pro Late 2013

12Core Intel Xeon E5

2.7GHz

Memory: 64GB

Please help.

Josh

This topic has been closed for replies.
Correct answer joshuac3250

I have just switched the hard drive I've been working on to a

Macbook Pro 15 Inch, 2017

2.9GHz Intel Core i7

16GB 2133MHzLPDDR3

running macOS Sierra.

The project is functioning fine.

Any suggestions on what to do to get back to using the Mac Pro?

4 replies

Participating Frequently
November 27, 2019

I've been having this issue with vers 14 Premiere.  What's the deal with this?  FCPX is my go to anymore.  

joshuac3250AuthorCorrect answer
Participant
October 15, 2018

I have just switched the hard drive I've been working on to a

Macbook Pro 15 Inch, 2017

2.9GHz Intel Core i7

16GB 2133MHzLPDDR3

running macOS Sierra.

The project is functioning fine.

Any suggestions on what to do to get back to using the Mac Pro?

Kevin J. Monahan Jr.
Legend
November 9, 2018

JoshuaC,

Sorry about that! First, open a case with support here: Contact Customer Care

You might try repairing Adobe folder permissions: Premiere Pro CC, CC 2014, or 2014.1 freezing on startup or crashing while working (Mac OS X 10.9, and later)

You can also try a new user account.

Let us know if any of those items work.

Thanks,
Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
Kevin J. Monahan Jr.
Legend
October 9, 2018

JoshuaC,

Sorry for the anomaly. Neil provided the pro tip for salvaging the project: that is, you must import that old project into a new one. Did this work for you? If so, please give Neil credit by marking his response as the correct one. Glad your new projects, at least, operate OK.

Word to the wise: avoid updating project files, as such things frequently happen.

Let us know what happens.

Thanks,
Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
Participant
October 15, 2018

Kevin,

Thanks for the tip on avoiding updating project files. That was news to me.

Unfortunately that process had a worse outcome and I only got the pinwheel. Had to force quit Premiere after letting it think about things for close to an hour.

Josh

R Neil Haugen
Legend
October 9, 2018

One would love it if just being a 12-core CPU was forever enough. That is an OLD 12-core though, on an equally ancient (computer terms) motherboard. So ... first, that is no longer up to 'modern' standards for internal operating speed.

My first comment to the issue is wondering if you're opening the older projects in the version of PrPro they were created in or just opening them in the newest one?

My first choice would be working a say 2015.4 project in 2015.4 if you still have it available, but for many, the kerfluffle between Dolby Laboratories and Adobe corporate means you many not have all your older versions still available.

Next ... when bringing a project forward, and from experience ... I always create a new project in the new version, then from the Media Browser of the new version in that project, navigate to a copy of the old project's .prproj file and import the assets of that project into the current project.

This seems to work best.

Neil

Everyone's mileage always varies ...
Participant
October 15, 2018

Neil,

Thanks for replying. Sad but true on my fossil on my desk right now.

I have always only opened the newest project after Premiere updates. Never had I tried creating a new project and then imported the assets. I'll probably do that from now on since that seems like a good idea. However, I had no such luck with the attempt this time. I got the pinwheel and Premiere froze. After a good amount of time I decided to force quit.

Josh