FCPX And El Capitan

On a 2013 6 core Mac Pro with dual D500's and getting laggy playback when playing anything more than 3 streams of 4K (using "Better Performance"). I thought I should get more than that according to Apple's website. Anyhow, I think I'll go down to Yosemite to see if it changes anything. I just got this machine so I don't know how it performs on Yosemite yet, hopefully somebody can chime in and give me good news (like it will play back 4 or more streams of 4K without stuttering in Yosemite). Just gave my wife the 5K iMac, I guess I should've kept it and gave her the Mac Pro...

What hard drive are your Libraries and media on?

Hi Ben, I tried both an external Thunderbolt SSD RAID and the internal SSD. Same result. Just finished installing Yosemite, gonna give it try in a few minutes.

Wow, what a difference. 6 streams of 4K from GH4 playing smooth as butter on FCPX 10.2.2 and Yosemite 10.10.5. Crazy. No lag or stuttering at all, feels like the beast it's supposed to be.

Hi Tom, who gives a @$%^ about off set text? Apple should, this is a symptom of broken windows syndrome, take care of the small things before they grow into a huge issue.

It shows a lack of care by Apple, as if they are not interested in the product, it is not what you do that is important, but what is important is that you are seen doing something, and in this case, Apple are clearly doing nothing to fix the issue.

At worst release a press statement saying "We are aware of the text offset issue, an update is soon to be released", at best release an update, without fanfare, just quietly publish it. No harm, no foul!!!

This thread is nearly 200 posts long, most of them are issues in regards performance issues, something Apple in it's wisdom remains mute on, why remain mute? Why not either say something or do something?

I am concerned that the silence means something huge, that Apple are demoting FCPX to a 3rd tier project, small development budget, staff once working on FCPX, sent to work on other more valuable projects.

This lack of communication plays out in the hardware domain, under-powered devices, the decision to solder in parts, rendering upgrade impossible speaks of an attitude of "We don't care about the consumer...They buy what we think is best" when clearly Apple do not know what is best...

What is more frustrating is your attitude Tom, you should care, clearly this comment about who gives a foxtrot uniform charlie kilo about text offset, demonstrates that you accept and submit, well I don't accept and I won't submit to the whims of Apple, I am forced to submit as i do not have the power to change Apple, if I could I would...

Apple is always silent. They live by their own rules. A display glitch in the dashboard is the least of our problems. It'll probably be fixed the next time there's an update, and if it isn't I wouldn't care, as long as they did something else worthwhile.

The time code UI glitch in FCP X on El Capitan has been reported and confirmed by hundreds of people on different forums, even in the early beta stages of the new OS. So everybody knows that when you do upgrade to EC you will have this little glitch in FCP X. When you know this, there are two things you can do:

- You wait with updating the OS until FCP X has been updated as well and the glitch has been fixed. Perfect.

- You update anyway because, like many people, you absolutely don't care about this glitch. Perfect as well.

But updating anyway and still complaining about the UI glitch is a bit ridiculous. You knew this would happen. If it bothers you, you should not have updated at all. Period.

The many contributions to this thread have been very useful in helping people decide wether they should update their OS in this early stage or not. And I would like to thank everyone who has made a contribution to it. But abusing this thread to spit completely uninformed and unfounded criticism, and even personal attacks, is something I don't accept.

Be an early updater and accept the fact that this might have consequences, or wait with updating until all the usual initial bugs have been ironed out. It really couldn't be easier.

- Ronny

I'm with Ronny completely on this subject. Users have had plenty of warning, and if you update, accept it. Apple hasn't done anything wrong, immoral, or unacceptable. In fact just the opposite. Their bug updates come out faster than any other OS on the market. Good for Apple!

Users knew Apple's business model going in, and accepted it willingly and freely upon the first purchase.

If you don't like Apple products or the way they handle things, don't use their products. A very simple and easy move to make. Go to Windows or some other UNIX flavor. Best of luck with that...

Hi Ronny

Mock me, curse me, say what I write is tripe, I have worked in corporate environments for over 20 years, I know how they work. I am that hated kid who asked a great question and was forever hated by his town...

If Apple knew of this error in beta, and it was released, then what does that mean? I am reading between the lines, as Catholics know only too well sins of omission are as bad or worse than sins of commission...

Not publishing any statement or update sends a clear message, maybe you do not want to hear it, and that is fine, I hear the message loud and clear, this is akin to the Pro Video Codec debacle, that dragged on for weeks, until something was done, this update has been out long enough for Apple to have published an update. Why they have not worries me....

I do like FCPX, I don't agree with the decisions to render upgrades nigh impossible, that was a senseless strange decision that really has no merit, it was done to maybe satisfy the owners of Apple Inc, possibly, but technically it was a stinker!!

I am not complaining about the update, I was spared that pain as I don't have enough data to download El Capitain...

I am merely commenting on what I see, my thoughts about the present state of our beloved Apple Inc, you may not like or agree with my views, and that is fine.

I have not told you to go away, leave the platform, give up my business, no I have not, I respond kindly and with good grace. Why is it ok to bash me? Have I abused you here?

This is a thread about FCPX and El Capitan, from the posts previous to me coming in, this is heading into a pr disaster down the line, and then we all just have sit and wait for someone to finally publish updates.

AU units not working, EC has been in beta in one form or another for over a year, and still Apple publish updates that break systems, or render plugins useless... That cannot be a good way to do business...

All I am doing is holding Apple to a very high standard, that once long ago they had, since Steve turned into a farmer, Apple has lost focus, look FCPX has had a terrible painful birth, and maybe they are a bit shy now about mistakes, this debacle now is heading down a path that has the markings of a bad PR joke....

Oh well...I believe I am not wrong, I will not bash or abuse anyone here...

"EC has been in beta in one form or another for over a year,"

No, it hasn't. El Capitan went into beta at WWDC in June and was released before the end of September.

I was wrong, I do apologize, only in June it was in beta...Gosh..time flies when you are busy..

The new OS was released because it was considered fit for the absolute majority of Mac users, which it is. The little UI bug in FCP X was totally irrelevant for this release because:

a) 95% of all OSX users do not even work with professional video tools.
b) This UI bug can only be fixed by the FCP X team, just like some remaining issues with third-party products can only be fixed by the third-party developers. When they do this, everything will be fixed. Simple as that.

That's why ranting at Apple because they have released an update that works perfectly fine for the vast majority of OSX users, sounds ridiculous.

- Ronny

MsJustine wrote: Hi Ronny

Mock me, curse me, say what I write is tripe, I have worked in corporate environments for over 20 years, I know how they work. I am that hated kid who asked a great question and was forever hated by his town...

If Apple knew of this error in beta, and it was released, then what does that mean? I am reading between the lines, as Catholics know only too well sins of omission are as bad or worse than sins of commission...

Not publishing any statement or update sends a clear message, maybe you do not want to hear it, and that is fine, I hear the message loud and clear, this is akin to the Pro Video Codec debacle, that dragged on for weeks, until something was done, this update has been out long enough for Apple to have published an update. Why they have not worries me....

I do like FCPX, I don't agree with the decisions to render upgrades nigh impossible, that was a senseless strange decision that really has no merit, it was done to maybe satisfy the owners of Apple Inc, possibly, but technically it was a stinker!!

It means the update for FCPX that will take care of these issues hasn't hit. Just hold your horses it is coming this Month. :whistle:

"I respond kindly and with good grace."

I'd not agree with that.

Well I for one am a lousy programmer, but I have taught myself to program in several different languages, starting with Basic, a long time ago.
OSX is estimated to have over 100 million lines of code. Any complex app like FCPX is likely to have 10s of millions lines of code that need to interact with the OS coding on lots of different hardware configurations.
Each added or altered line of code may affect 10s, 100s, 1,000s lines of other code. I think anyone who thinks it is easy should take a course in coding and attempt to build just a couple of simple interacting apps and see what happens.
I think it was Tom who said that instead of complaining about a few glitches, we should focus or remember that there are very few problems.
Apple does fix the issues, but it may not be a simple change. Plus each change has to be tested to see if it busted something else. Remember, the software is part of an ecosystem that covers years of hardware and must also interact with different OSs. If you are that good a coding, Apple wants to hire you.
As Ronny says, fixing a small problem that only a very small percentage of people need is not ample evidence of Apple's indifference or ineptitude. Chill.
Bugs Happen! Report them to Apple.
Just my not so humble opinion.
Hope this helps, Greg

Ms Justine ...

Quite frankly, if you have not updated to El Capitan, or recently purchased a new computer that would require it's use ... why all the angst over the expected update to fix these issues with FCP X?

While I am all for letting Apple know when they drop the ball and may have lost focus about the best interests of their customers ... customers must also keep things in perspective as well.

Don't overlook the fact that EVERY user that has purchased FCP X since June 26, 2011 has only encountered a total expenditure of $299 USD (plus any associated taxes and currency exchange rates).

FCP X 10.2.2 is a very different and much more capable app than was 10.0 ... and we ALL received those additional updates at no additional cost. Keep in mind while 10.0 was less than capable than FCP 7 ... no one was forced to upgrade to FCP X ...

To put this in perspective, if we had been using Premier Pro CC for the same time period it would have cost users a minimum of $1,020 USD (plus any associated taxes and currency exchange rates).

Not to mention, Apple has not charged one penny to any OS X user for that past several OS system upgrades.

Additionally, not one single user is compelled to install and run El Capitan. Upgrading to OS 10.11 is purely optional, not a requirement. As mentioned earlier, you can even roll back or install Yosemite on newly sold production models if needed.

I'm all for holding Apple's feet to the fire when they screw up ... and they do from time to time ... however, I think if one truly wishes to be fair, we must consider all the aspects of the situation, not just the 'expectations' side of the scale. Your assertions would be more credible if they were more balanced.

I too am a bit disappointed we haven't seen an update for FCP X to fix the El Cap issues by now ... it's a bit uncharacteristic of Apple to have taken this long after a new OS is released ... I'm hoping they are polishing off support for Metal in the awaited update ... if so, I'll be very grateful and forget about my disappointment in a heartbeat.

Good point ButchM!

Also I think there would be less complaining if Apple would still charge for there OS updates.
People update finger wouldn't be so itchy.

Yes I also think we see a update for Final Cut Pro X in November.

Well, I think it is more than fixing bugs for EC. I think there are other things like Metal and split screen that they want to introduce all at the same time. I'm not beta testing, don't know anyone who is at the moment. So this is speculation. But if you're going to release an OS X 10.11 compatibility update, you'll want to be all inclusive. So I'm more than willing to give them the time they need to get a full featured upgrade out. So for my money, I'm expecting more than just bug fixes, I'm expecting EC specific functions to be included.

BenB wrote: ...if you're going to release an OS X 10.11 compatibility update, you'll want to be all inclusive. So I'm more than willing to give them the time they need to get a full featured upgrade out....

Exactly right. For a major software product like FCP X it is very costly to do a release for a tiny cosmetic problem. They can't just compile it and ship it. Even if they touch one little item in the source, the entire product must undergo extensive regression testing, stability testing, internal Alpha testing, etc. The test team for that is busy right now on the next major version. So doing that one little fix would delay the next major release.

There have been countless times when software development teams yielded to the temptation to make one little fix without a full test cycle. "How could this break anything? It is just one little thing." Then after thousands of customers are running it in mission-critical scenarios, they discover it broke something.

What about synchronizing the release cycle with OS X? That is also easier said than done. What if the FCP X team had engineering changes underway that would not be possible to meet by that release date. Then they'd have to curtail those or partition the work in two segments which could entail additional inefficiency and development risk.