FCPX 10.1.4 PRE-RELEASE DISCUSSION

It concerns me that Apple does not have a clear strategy going forward, killed of livetype/dvd studio pro/soundtrack pro and color, leaving only motion-compressor and a new video editing NLE.

If you dislike Apples ( in your eyes missing ) strategy so much, why can´t you just use something else...
It would make life better for you and others!

It is not that I dislike, if you check I said quote "It concerns me that Apple does not have a clear strategy going forward" end quote.

It is a concern, that is I am worried and a bit confused, Apple went down a road with the 10.0 series, then had to do a 270 hard to port turn, introduced the 10.1 series Final Cut, it is this haphazard way of doing things..

Surely the big players in NLE editing, the Ripple Training, the Larry Jordan's of the world either have a direct influence on the course of FCP X development, or they do not...

How did FCP X go from the classic 7 interface to the 10.0 to the 10.1 in under 4 years?

Is Apple truly interested in pro apps anymore? It is almost as if this is a problem child they created and spend as little time as possible correcting it.. 10.0 was a disaster in every way, if you want lessons on how to take a brand to the point of collapse, FCP X 10.0.0 is how not to do it..

Then the 10.1 series is released, and it works, with a number of confusing and somewhat conflicted aspects, and the user base is somewhat placated, satisfied, yet we ask for more, most of the stuff seems trivial, so coding it into the interface should not be that hard.

Or will there be a complete re-write using Swift and Yosemite, is the 10.1 series terminal and will the new post Swift/Yosemite be 10.2 or series 11?

Does Apple listen, I question that, as the evidence tends towards a negative to the question does Apple listen, if they Apple did listen, then how did they get the 10.0 series wrong and the 10.1 series right? Who suggested the 10.0 and the 10.1?

The ideas of trackless interface, and the improved multicam, along with the vastly improved subclipping with used and unused ranges, keyword collection, smart collections all lead to a better workflow.

The range selection, could be improved, the listview full clip, no zoom into clip, a mistake, some short cuts are missing, all of this is nothing massive, so why the many months delay..

My suggestion of having Apple announce what they are looking for to improve with each update, as they do with the hundreds of Yosemite/Mavericks developer updates, so we know with zero certainty what is upcoming, is exciting, will we see what they promised or more..

Why do it with the operating systems, and not a tiny pro app portion of the business??

MsJustine wrote: It is not that I dislike, if you check I said quote "It concerns me that Apple does not have a clear strategy going forward" end quote.

It is a concern, that is I am worried and a bit confused, Apple went down a road with the 10.0 series, then had to do a 270 hard to port turn, introduced the 10.1 series Final Cut, it is this haphazard way of doing things..

Surely the big players in NLE editing, the Ripple Training, the Larry Jordan's of the world either have a direct influence on the course of FCP X development, or they do not...

How did FCP X go from the classic 7 interface to the 10.0 to the 10.1 in under 4 years?

Is Apple truly interested in pro apps anymore? It is almost as if this is a problem child they created and spend as little time as possible correcting it.. 10.0 was a disaster in every way, if you want lessons on how to take a brand to the point of collapse, FCP X 10.0.0 is how not to do it..

Then the 10.1 series is released, and it works, with a number of confusing and somewhat conflicted aspects, and the user base is somewhat placated, satisfied, yet we ask for more, most of the stuff seems trivial, so coding it into the interface should not be that hard.

Or will there be a complete re-write using Swift and Yosemite, is the 10.1 series terminal and will the new post Swift/Yosemite be 10.2 or series 11?

Does Apple listen, I question that, as the evidence tends towards a negative to the question does Apple listen, if they Apple did listen, then how did they get the 10.0 series wrong and the 10.1 series right? Who suggested the 10.0 and the 10.1?

The ideas of trackless interface, and the improved multicam, along with the vastly improved subclipping with used and unused ranges, keyword collection, smart collections all lead to a better workflow.

The range selection, could be improved, the listview full clip, no zoom into clip, a mistake, some short cuts are missing, all of this is nothing massive, so why the many months delay..

My suggestion of having Apple announce what they are looking for to improve with each update, as they do with the hundreds of Yosemite/Mavericks developer updates, so we know with zero certainty what is upcoming, is exciting, will we see what they promised or more..

Why do it with the operating systems, and not a tiny pro app portion of the business??

Just use something else then and please stop the constant nagging in this forum.

"Then the 10.1 series is released, and it works, with a number of confusing and somewhat conflicted aspects, and the user base is somewhat placated, satisfied, yet we ask for more, most of the stuff seems trivial, so coding it into the interface should not be that hard."

All due respect, you're stating your opinion as fact, and much of what you're saying is just not true.

What is wrong specifically with what I stated? Most of which yes is opinion, a shared opinion, most members would not publically share the same, but it is common knowledge, if you watch tutorials, read forums, there is a confused coding to FCP X.

I am not nagging, I am expressing a valid view, I question the methodology used by Apple Pro Apps Dev team. Not every aspect of the thread from 10.0.1 has been implemented into 10.1.3, why not? What has taken so long for aspects to be coded into the app?

Just to confirm that the title of this thread is FCP X 10.1.4 PRE-RELEASE DISCUSSION..

For those struggling with the concept, I am in fact having a discussion, I pose a number of questions, so either ignore the questions or answer them.. That is what this is a discussion...ANd discussions always are opinion based.. This is not a technical forum thread, but a discussion..

"Not every aspect of the thread from 10.0.1 has been implemented into 10.1.3, why not? What has taken so long for aspects to be coded into the app?"

Well, writing an app isn't like writing a book. Maybe they have a plan. Sort out events/libraries. then move on to the timeline, then to the next bit. Your "most member" generalization is way off the mark. In my opinion.

I respect your opinion, it is a valid opinion. I am sure that members of the Dev team value very comment, despite the vastly divergent nature or range of every comment.

Just one last thing, my questions are mostly rhetorical in nature, designed to stimulate thought, debate and voice a concern I have, I mean no malice in what I say, I enjoy the product, it is so superior to other systems, and I am a concerned user about the slow progress.

My writings are somethings a bit confusing, that is why I am an editor not a book keeper, so apologies for confused writings!

Dear Justine,

You mix up things like marketing, programming and product development.
That doesn't make sense - at least not here.

Regarding Apple responses: I personally have the experience that nearly everything was answered (not each the way I hoped)

I recommend to listen to Baz Luhrmann's song once a week on idle tuesdays at 4 pm


- Andreas

MsJustine wrote: What was the rate of updates for FC Classic, all the apps in the studio? Was it as many as we have had just with FCP and Motion?

It concerns me that Apple does not have a clear strategy going forward, killed of livetype/dvd studio pro/soundtrack pro and color, leaving only motion-compressor and a new video editing NLE.

I would love to see what Apple brings to replace livetype/color/dvd studio pro/soundtrack pro, but with the demise of aperture in favour of the new and improved photo app sometime in 2015 or more likely 2020...

I will be very surprised if there are updates for X in 2014 for those running Mavericks, I guess a rush job hatchet patch for Yosemite users, but for Mavericks, we are done with updates, giving the lateness of the year already...Heading into winter slow down holiday period..I guess Feb or March 2015 before any news from Apple, Inc

Sounds to me your don't have enough knowledge what is going on and don't understand marketing strategy!
Bringing up LiveType and DVD Studio Pro is silly! Motion replaced LiveType before FCPX came out.
DVD Studio Pro is a dead weight in Apple books and it seems they are right. Welcome to 2014 the age of Digital Media and the Internet!

Your comments on Mavericks makes no sense at all. Could specify what you are talking about?

Thanks

Interesting.... I especially like number2.

fcpx.tv/Pages/waitingonfcpx4.html

In their preview of the Apple Event tomorrow, 9to5mac reiterate their belief that iLife, iWork, and more interesting to us- iMovie and Final Cut; will be updated,

We reported in July that Apple was said to be preparing updates to both iMovie and Final Cut Pro to bring support for editing, exporting, and importing video taken with 4K resolution-capable cameras. That would be a great feature to introduce beside new higher-resolution desktops…

"support for editing, exporting, and importing video taken with 4K resolution-capable cameras. That would be a great feature to introduce beside new higher-resolution desktops"

I think that, if there is an X/iMovie update, that's a likely reason. I like RT's wish list. We'll see how good he is at guessing.

Nothing against Richard, but much of this is carried over from his 10.1.2 wish list. Consider it his, "top of mind" wants.

Disproportionate Pictures wrote: Nothing against Richard, but much of this is carried over from his 10.1.2 wish list. Consider it his, "top of mind" wants.

Changing "expect" to "hope" would work for me.

"It concerns me that Apple does not have a clear strategy going forward.
It is a concern, that is I am worried and a bit confused, Apple went down a road with the 10.0 series, then had to do a 270 hard to port turn, introduced the 10.1 series Final Cut, it is this haphazard way of doing things."

Super way off base, and factually untrue. Apple has had a very clear strategy going forward. There was no hard to port turn between 10.0 and 10.1, they are evolution of a single app, with a clear structure, ever growing, just like all other NLE's do. There is nothing haphazard anywhere with FCPX.

I've been told the story of how the dev team went through FCP 8 & 9, ending up trashing both and coming forth with 10. I've posted it more than once here. There was nothing wrong or confusing about what they did, it is just a very little known story.

Seriously, there is a point where uninformed negativity just gets to be too much.

BenB wrote: "

Seriously, there is a point where uninformed negativity just gets to be too much.

Totally agree.

Very much agree. If you don't like the app, AND you don't like the way it's being developed... then just move on.

There are other options. Even free ones.

Darren Roark wrote:

BenB wrote: "

Seriously, there is a point where uninformed negativity just gets to be too much.

Totally agree.

There are a lot of people who are very mad at Apple for EOL-ing FCS and some hardware. There may have even been some justification for this 3 years ago. At this point it's just silly. If you want FCP 8, use Premiere. All the modern codec capabilities, tracks, a mixer, and all the fun that goes with it. I've been cutting in Pr and X at the same time this week, (2 jobs) Pr is very nice in a lot of ways, but it's even more of a fiddly mess than FCP 7 was/is.

Oh well...

Such a good point, PP is in so many ways so far behind the streamlined yet going back to it for any reason still frustrating mess that is FCP 7. The folks that are still angered by the EOL'ing of FCP7 are really tough to convince that Apple had the best of intentions.

As soon as I heard the initial rumblings of a trackless workflow I said "Yes please!"

After finally getting away from FCP 7, I haven't seen the "Out of Memory" error once. Good riddance.