FCP X 10.4.7 is out

[Ken Bennett]

I still havenʻt gotten a solid answer on my original question. Will Mojave run M$ Word: Mac 2011 and Excel: Mac 2011 as well as Adobe Suite 6.6 (Encore 6.6, Photoshop 6.6, Illustrator 6.6, After Effects 6.6 etc.)?

Iʻm still running macOS High Sierra 10.13.6 with FCPX 10.4.6. I canʻt update to FCPX 10.4.7 and Mojave unless all of the above works 100%.

Ken Bennett
Video Adventures
Capturing Your Life’s Adventures!

[Oliver Peters]

[Ken Bennett] “Will Mojave run M$ Word: Mac 2011 and Excel: Mac 2011 as well as Adobe Suite 6.6”

MS Office, yes. Adobe CS6, not sure.

– Oliver

Oliver Peters – oliverpeters.com

[Warren Eig]

I run Adobe CS6 fine under Mojave 10.14.6. Just did a clean install.

Warren Eig
O (424) 293-1164

email: info@babyboompictures.com
website: https://www.BabyBoomPictures.com
Vimeo: https://vimeo.com/babyboompictures

For Camera Accessories – Monitors and Batteries
website: https://www.EigRig.com

[Michael Gissing]

Thanks for the responses, although the specific issue I raised of the pace of development and improvements wasn’t commented on. Interesting.

It falls on familiar lines. For some X is and always was perfect. For others not liking Resolve is OK but seriously the pace of X developments compared to Resolve should be of some concern. I’ve read previous posts with long dusty wish lists of things X could do to improve. Maybe the people who want more from X have moved on and no longer bother to comment here.

Beyond the obvious of preference for an NLE which can be based on familiarity or how it is a best fit for your workflow, I’m asking if people are happy with the pace of development. It seemed this update just became a commentary on other software and the Catalina OS. In other words almost no comment on the actual update. Made me wonder.

[James Culbertson]

<>

You’re question is kind of abstract. I’m editing fast and efficiently with FCP 10 doing the job I am asked to do which is tell stories. (I’m also able to color correct and sweeten audio so that my clients are happy.) Resolve doesn’t compete with FCP 10 yet with regard to efficiency and speed of essential editing tasks so whatever pace its development is moving at relative to FCP 10 isn’t particularly relevant yet. I would answer similarly for Premiere. Does that answer your question?

[Michael Gissing]

Thanks James.

[Steve Connor]

[Michael Gissing] “It falls on familiar lines. For some X is and always was perfect. For others not liking Resolve is OK but seriously the pace of X developments compared to Resolve should be of some concern.”

In feature terms I honestly don’t feel that FCPX is going to be developed a great deal further than it is at the moment. I think everything seems to be concentrating on performance and “under the hood” development.

I do wish they’d continued down the path of innovation that they started with the release, but at the moment it works very well for me and I’m happy to stick with it, but if they EOL’d it now, I think I’d be quite happy to jump to Resolve.

[James Culbertson]

The other thing I will say is that if I have to choose between stable and fast (FCP 10) and constant fancy new features (Premiere) I will choose FCP 10 every time. Premiere (in my experience) is buggy and much slower. Resolve seems to be inbetween… considering how much it can do it does not have the feel of a bloated app. But it could easily become that way if BM Product Mangers are not careful.

[Oliver Peters]

[Michael Gissing] “although the specific issue I raised of the pace of development and improvements wasn’t commented on”

Isn’t that in the eye of the beholder? Blackmagic’s pace has been fast with Resolve, but a lot of that effort has been in making it an all-in-one solution, developing the cut page, and the editor keyboard. If these are things you like, then the speed of development is great. But if you mainly want a better editor (using the edit page) and a better color corrector, then that pace could be viewed as rather slow – simply because those features haven’t received the same attention. Given that, then Resolve wouldn’t stack up as well. So it’s perception.

I do think development pace could be better with FCPX, but I want additional and/or improved features. If those aren’t features that are on the development path, then I’m going to view X as slow development. That’s even though other aspects are being addressed that might actually be way more important from the POV of Apple’s larger goals. Like stability, tweaking for the Mac Pro, better HDR support, and so on.

As far as features go, maybe Apple has decided FCPX is more or less done and improvements will be incremental or come in other areas, like machine learning functions.

– Oliver

Oliver Peters – oliverpeters.com

[Michael Gissing]

I agree Oliver that attention in some areas has been slower than I would like. The Fairlight page got off to a flyer then has slowed with some much needed features only just making it in. I still use the stand alone version mostly but I’m now in a position to consider the Resolve version for my work. However the area that needed most work was the edit page and I’m undecided about the Cut page. When you look at performances and feature improvements to all pages in Resolve over the past three years and compare it to all other NLEs, Blackmagic is clearly out in front with the pace and scope of developments. Even in areas like color grading where they were not lagging.

But when I look at other NLEs they all seem pretty ordinary in areas that Resolve is clearly ahead like the Fusion, Fairlight integration and Color. To consider that all that has been achieved plus the developments in cameras and other hardware, I cannot agree that it is a matter of perception.