still driving me nuts

[Mike Warmels]

It does it too after some time just editing without importing. I dunno why? Why doesn’t to SHOW me what it’s doing?

[Jeremy Garchow]

[Mike Warmels] “The point I was making that only using SSD thunderbolt drives would be a ridiculous solution. I think the Apple is equipment is already quite prices to make such demands, while other NLE’s don’t need so much hard drive power.”

I don’t think you need SSD thunderbolt drives. I never said that. If I did, please point me to where I did and I’ll edit it.

[Jeremy Garchow]

Isn’t the very warning you are talking about showing you what it’s doing?

[Mike Warmels]

I was just saying: just buying faster drives (and even SSD drives costs money, and a bay etc etc) should not be the solution. Because USB3 should, I think suffice. Simply because other NLE’s manage fine with it. Why does FCPX need so much more power and speed? That is the question I keep asking and not getting answered..

[Mike Warmels]

Nope. It’s the ‘Cancelling Background tasks” thing every one gets once in a while.

It’s not a warning really. It’s cancelling them so I don’t have to wait for it to shut down. So fine. But it shows it doing something, while the Background processes window is idle… So to me that shows FCPX is doing stuff… stuff maybe that could be slowing my NLE down. But since I don’t know what it’s doing, there’s not a sensible thing to be said about it.

[Jeremy Garchow]

[Mike Warmels] “Why does FCPX need so much more power and speed? That is the question I keep asking and not getting answered..
“

I have said, over and over, that fcpx is its own NLE.

I told you many posts ago that you don’t have to buy anything else.

I have told you what will help.

1) Update to the latest OS and NLE version

2) Try putting your library and cache on a separate drive than your media. I recommend the boot drive because:
A). You have it
B). It’s the fastest drive you have.

When all of the is done, let’s see how you’re doing.

Fcpx doesn’t need a whole lot of power for editing. It benefits from fast disks because of the way it works, with the constant auto saving, thumbnail/waveform generation, and sometimes, background processing of rendering, media, or exporting. It is also constantly working in very high quality floating point calculations. I think X performance is pretty good if you take all of this in to consideration.

If you don’t want to work at that quality, you can switch to better performance. You’ve indicated you don’t want to do that.

[Mike Warmels]

Yeah, I will move the cache to internal hard drive. And upgrade to the latest versions of OSX and FCP as soon as I can. Both are not an option at this time. (due to client and AVID functionality (i.e. not supported yet on the latest version of Yosemite)).

[Jeremy Garchow]

I swear you are not reading any of these posts.

Every good boy deserves fudge.

[Mike Warmels]

I am. But I don’t feel any sympathy for the issues I’m addressing. The answer to every problem I run into is: use the fastest drives you have, update to the lastest versions.

FCPX10.2.1 better be the Messiah some of you claim it to be. 😉

[Jeremy Garchow]

i don’t think anyone said fcpx is a savior, it’s just that 10.2 is noticeably better. It’s not going to save all the suffering of all humanity. I think should should have that in mind when updating.

Here’s some recent real world feedback:

https://forums.creativecow.net/readpost/335/81235

https://forums.creativecow.net/readpost/335/80377

https://fcpxpert.net/2015/04/13/fcp-x-10-2-first-look/

https://forums.creativecow.net/thread/344/36762