Activity › Forums › Creative Community Conversations › Buggy Wuggy
-
Bret Williams
January 13, 2014 at 2:44 pmI looked through that and there appeared to be two issues being repeated.
1. People have merged all their projects and events into one big library because they don’t understand 10.1 media management
2. They have a corrupt user folder from the Mavericks install.
Neither are FCP bugs.
-
Franz Bieberkopf
January 13, 2014 at 4:50 pm[Bret Williams] ” People have merged all their projects and events into one big library because they don’t understand 10.1 media management”
Bret,
What is the official quantity/size limit for timelines and media in FCPX libraries?
Franz.
-
Jeremy Garchow
January 13, 2014 at 4:58 pm[Dave Gage] “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?”
That would mean Apple would have to issue white paper for every app it makes.
I think there is still onus on a user to tune their system.
The energy saving preferences have changed a bit in Mavericks systems with newer hardware (the Control Panel has different options with new vs old hardware). The Energy Saver Panel is one of the first places I visit when setting up a new machine. I have always done this, Mavericks is no different.
There’s no way that Apple can guess what each user’s needs and power requirements will be, so they put on a lot of the power saving options to save battery life. We, as “power users” have to undo a lot of those.
App Nap does not have it’s own control panel, however, so that one has to be learned the hard way. I happened to learn just be reading from other people’s experiences with it.
Here are some other power saving technologies Apple is employing in Mavericks: https://www.apple.com/osx/advanced-technologies/
Jeremy
-
Bret Williams
January 13, 2014 at 5:15 pmHow would I know? Probably depends on your RAM, your processor, etc. But I’m reading about a lot of spinning beach balls where people have just installed 10.1 and let FCP X upgrade their entire library of events and projects into one huge project. I think it’s pretty sad that Apple didn’t run us through some specific procedure to link specific projects to events and make them into libraries. But it seems fairly obvious one of the reasons for libraries was that Apple was unable to get it to perform well enough when all your projects and events were loaded at the same time, so that’s why they came up with their own idea to replace event manager X. Along the way they threw in the ability to keep the media managed externally to better facilitate sharing and keep duplication to a minimum. But in the Apple way, to have the upgrade itself describe this and assist you in all this would be some sort of admission of defeat, so they just upgraded all the projects and events (on a per drive basis) to one big library. Probably making the problem worse because before people were using event manager X to to mount and unmount. Now they’re just loading them all.
I think the reason they got rid of scrubbing projects was part of the problem too. Memory/resource hog. Neat trick though. But the fact that you had to actually highlight a project before scrubbing was always a tell tale sign to me that they were trying to limit just how much was loaded in memory.
In Premiere or legacy you certainly wouldn’t even dream of opening all the projects at once. Any nle would likely bog down. Throw in X’s unique thumbnails and scrubbing which all has to get cached into RAM or somewhere and it’s a bigger problem. My events show as a single thumbnail for each clip or list view. And I don’t use any thumbnails in the timeline FWIW.
My mavericks is an upgrade, and I had problems with my user folder with 10.0.9. I created a new user and all was well. Then the upgrade to FCP X 10.1 went effortlessly.
It seems there is definitely an issue with user corruption in the mavericks upgrade, which is why a clean install of mavericks is a sure fix. But for me a new admin user worked fine.
-
Tony West
January 13, 2014 at 5:55 pm[Bret Williams] “But I’m reading about a lot of spinning beach balls where people have just installed 10.1 and let FCP X upgrade their entire library of events and projects into one huge project.”
this is not what I did, and I didn’t really have problems updating my older projects.
What frustrated me enough to write this post was I was working on a new project.
New Library
New footage
New project
Nothing to “upgrade” So I don’t know what upgrading an old project has to do with my New project.
As I started working on the new project the edits were slow and laggy
I’m not saying that people didn’t do what you described I’m just saying that’s not what my specific problem was. (while I did link you to folks complaining about a different problem of lagging )
Started working again this morning on a snapshot project. It was spinning. Looked back at the project that I took the snapshot from and it played fine. hummmmmmmm
Quit X, copied the Library to another drive and so far both projects are fine.
Not sure why one project played fine and the other didn’t. They are using the same media.
I have been on X since the beginning and have never had a problem with updates in the past.
People are talking about clean installs and that’s great,
just saying………….I never bothered with a clean install in the past and never had a problem so if this update *requires* a clean install that would be a first for me.
-
Jeremy Garchow
January 13, 2014 at 6:06 pm[tony west] “just saying………….I never bothered with a clean install in the past and never had a problem so if this update *requires* a clean install that would be a fist for me.”
This is also the first FCPX that has required a new OS before you could even install it.
Mavericks, even in non FCPX users, seems to be happiest with a clean install.
Clean installs are never fun, but the AppStore and Creative Cloud makes things a lot easier.
Plugins, third party extensions, etc, are the harder parts.
For the most part, from what I have seen and read, FCPX 10.1 performance is better pretty much across the board.
If there’s something feels different with your system after moving to 10.1, and FCP 10.1 is running worse than 10.0, I’d take a look at trying a clean install.
It sucks, but it might be worth it.
Jeremy
-
Tony West
January 13, 2014 at 6:21 pm[Jeremy Garchow] “This is also the first FCPX that has required a new OS before you could even install it.”
Good point J
-
Bret Williams
January 13, 2014 at 6:26 pmDid you try a new user yet? That seems to accomplish the same thing as a clean install. I forget, did you update to Mavericks at 10.0.9 or just recently with 10.1?
-
Jack Zahran
January 13, 2014 at 10:28 pmIn the Apps/Utility folder, start the program called Console. Select the Clear the Display button. Then start FCP X 10.1. Each time a beach ball starts, go back to Console and select the “Insert Marker” button.
Save a copy of the Console message list using the “File-Save a Copy as…” option.
Feel free to post the console log. I’d be happy to analyze it for you.
-
David Mathis
January 14, 2014 at 1:25 amSame here. I also like the ability to hide projects I do not need to see directly inside the software. I expect this software will improve even further. Current version seems much more responsive and stable. I did a clean install just to head off any gremlins that decide to create chaos, so far everything is working like it should.
Reply to this Discussion! Login or Sign Up