-
FCP X and Plug-ins
-
The annoying part is that it seemed to get worse after the 10.1 update and Yosemite.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Oliver Peters] “The annoying part is that it seemed to get worse after the 10.1 update and Yosemite.”
I’m using Mavericks. Do you think Mavericks is less problematic with regard to sluggishness?
-
I’ve been snapped at for rejecting plugins, but even now we keep them to a minimum – with the exception of Beauty Box and Color Finale.
That said, when we have a random project that’s more cranky than normal, we recreate a new library with it and keep on trucking.Maybe I don’t notice any big issues anymore – that’s not to say that it’s bug free – it’s just that I don’t see them. We do always make it a point to work on new machines with it, so perhaps that is part of it?
John Davidson | President / Creative Director | Magic Feather Inc.
-
[James Culbertson] “Do you think Mavericks is less problematic with regard to sluggishness?”
I see similar issues on Mac Pros running Mavericks as with others running Yosemite.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Oliver Peters] “The annoying part is that it seemed to get worse after the 10.1 update and Yosemite.”
I agree that we seem to haven taken a step backwards. Taking the good with the bad I suppose?
As to your question of plugins, I’m convinced that some plugins really slow down X. Like most add-ons, some are updated to take advantage of updates, where others are not. Anytime I get a new Mac it starts out fast and then begins to slow down after adding all the plugins. Unfortunately, I’ve never had the time to add them one at a time to determine the culprit.
Plugins are a mixed bag. On the one hand, they provide all the missing pieces in X. OTOH, if all plugins came from Apple, they’d be optimized…
Mitch Ives
Insight Productions Corp.“Criticism may not be agreeable, but it is necessary. It fulfills the same function as pain in the human body. It calls attention to an unhealthy state of things.” – Winston Churchill
-
To me, one of the main problems seems to be that after one of those updates, X started to render in the background on it’s own. Even when you have that unchecked in preferences.
From the beginning I had always turned that off and I didn’t notice any problems like this.
They need to fix that.
Other things might be causing issues also, but that is one thing I’m sure is a problem.
I used to go along cutting just fine, and when I wanted to take a break I would tell it to render. I remember it would render even faster then. I have not changed computers from the beginning (cheese grader)
I know that the plugin Neatvideo has issues. It will take forever to render and then after that, if you slide the clip left or right in the timeline you have to rerenader it. They are aware of it but haven’t done anything about it.
-
[tony west] “To me, one of the main problems seems to be that after one of those updates, X started to render in the background on it’s own. Even when you have that unchecked in preferences.”
I’ve never seen nor heard of this issue and I feel like I read just about every thread here. Might be time for a clean reinstall of the OS and X. At least a trashing of your prefs.
-
[Oliver Peters] “I have a project I’m cutting today. It’s all 1080p/23.98 shot over-cranked and transcoded to ProRes. I/O is a Decklink Extreme. In X, the output via the card is very stuttery, like it’s playing 12fps (fine on the viewer in the UI). In premiere it’s super smooth in both places.”
I’m going to have to cop to operator error on this one. In switching between a 720p/59.94 project in PPro and a 1080p/23.98 project in PPro and FCP X, this issue showed up. I checked the BMD pref pane and it indicated the correct settings. Today when I rechecked my steps after a clean power up, the BMD pref pane was in fact set to 720p/59.94 and not 1080p/23.98 like it should have been. Maybe the BMD card wasn’t correctly resetting between apps in spite of my setting it in the pane. Who knows? I set it to the correct 1080p/23.98 this morning and playback in X was smooth as expected. In any case, this particular playback frame rate stuttering is not an FCP X issue.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[tony west] “To me, one of the main problems seems to be that after one of those updates, X started to render in the background on it’s own. Even when you have that unchecked in preferences.”
I’ve noticed this, but it doesn’t appear to have anything to do with rendering video previews for me. As far as I can tell it is rendering audio waveforms. Once those are built the sluggishness goes away. Unless I open up the audio inspector and then the audio waveforms can slow things down some of the time until I close the audio inspector again. These are only problems for me with longer source files (like an hour or longer).
-
Is ther a way to disable audio waveforms? Also, when I don’t need the inspector or effects browser open, they are closed. Read somewhere this can help with response times.
Reply to this Discussion! Login or Sign Up