Buggy Wuggy

[Tony West]

[Jeremy Garchow] “Also, be sure App Nap is off.

Jeremy
“

Thanks for this heads up also Jeremy

[Tony West]

[Bret Williams] “Lots of issues with people screwing media management up”

Bret, wouldn’t this pertain more so to updated projects that you were brining over from the last version?

How could this explain a fresh new project started in 10.1?

[Tony West]

OK, thanks to Jeremy’s tip I turned off that App Nap and so far it’s running a lot better.

It seems crazy to me that could have had that much of an impact on the performance.

[Dave Gage]

[tony west] “OK, thanks to Jeremy’s tip I turned off that App Nap and so far it’s running a lot better.
It seems crazy to me that could have had that much of an impact on the performance.”

Wouldn’t ya think that maybe in the in the next release, 10.1.1, that Apple would have this off by default for this app. I’m still at 10.0.x, but have already read numerous times where people have had this problem in the new Mavericks/10.1 combo. Was this ever mentioned in the White Papers or a similar release by Apple?

[Bret Williams]

Sure. Where are all these bugs ? I’m looking through the posts.

[Bret Williams]

I have app napp off for After Effects too, but the other night I had a 4 hr render going. At 3 hrs my system went to sleep and the render just paused. WTH? I’ve been using AE since 1996 and the computer should never go to sleep when it’s cranking out a 7 core render. Seems like it’s pretty busy!

[Tony West]

Here are some folks talking about the same thing I was

“FCPX 10.1 Very slow on iMac and lots of spinning beach balls”

https://discussions.apple.com/thread/5691549?start=45&tstart=0

[Oliver Peters]

I’ve generally updated all OS changes, but after doing a completely clean install with Mavericks, I’m a convert to the school of thought that says you should do a clean install with every full 10.x update. There’s just a lot of stuff that gets rearranged in the new OS version, leaving a lot of orphaned files scattered throughout your system.

I realize that this isn’t always practical. As I posted before, I did a Mavericks update on a Mac Pro and FCP X 10.1 still had some issues. These were fixed by trashing the contents of the User Library/Preferences/ByHost folder (make sure you get any lock files). This fixed the issues I was having.

So far on two different Mac Pros (1 clean install, 1 update install) FCP X 10.1 has been pretty solid. The only issues I see are the persistent stickiness in going between the event browser and the timeline and sometimes not having the viewer correctly latch onto the right source. This has always been there. Otherwise, a major improvement for me.

Oliver

Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com

[Rhett Murphy]

When I initially upgraded to Mavericks, FCPX 10.0.9 was sluggish — very sluggish. After pushing live projects through their edits, I did a clean install of Mavericks (I’m on a Mac Pro with an SSD for OS and apps) before upgrading to FCPX 10.1. Was a bit a work, but things are fast and smooth. No problems and happy.

Rhett Murphy
REDWHOOSH PRODUCTIONS
BALTIMORE, MD

[Keith Koby]

We haven’t found anything wrong with fcpx – just trying to master the new world of mavericks on the san…

As a matter of fact, we’re finding nice “bug” fixes. One huge issue for us in the past was the lack of text formatting information support in fcpxml in the past. Happy to see that fixed. It’s a great way to pass graphic builds between editors as a starting point for new projects. Making compound clips and distributing them in an xml is better than motion generator templates in some ways (contain audio and you can trim, not retime, trim compounds, and I don’t need to install the generator in ~/Movies/whatever…).

One thing I do miss is scrubbing through projects in the project library. I wish that “closed” projects could be scrubbed in their new event home.