Apple finally responds to FCP X fallout

[Chris Kenny]

What a laugh, first you bash every critique that Apple is gonna address the issues and make official statements "soon", when they finally do you say people shouldn't read into what Apple's saying today.

What I said was that it was too early for people to read much into Apple not having provided a statement, because even if they were going to it would take a week or two. People argued with me about this. It took 8 days.

I never claimed Apple would necessarily issue a statement at all, let alone that it would contain definitive information about every question people have.

Even more funny, you read into a lot of stuff without them saying anything and say others shouldn't read into what Apple officially are saying.

I'm saying other people shouldn't read a lack of future R3D support into a statement acknowledging a lack of present R3D support.

I'm still curious why you need to defend Apple all the time and altering what you are saying based on what happens, now you say their default operation is secrecy about future plans. How do you know that? Isn't this just another assumption based on the fact that you weren't right about them addressing all the shortcomings the first time?

How do I know that Apple is a secretive company? Seriously?

Your credibility is getting lesser and lesser for each post.

How ironic.

Apple addressed the issues and when they don't really say anything to sooth the climate of critique you still say: "they are gonna say something, soon just wait".
Seriously?

Huh? I am not predicting that Apple will make another public statement soon. And it's kind of hilarious that you're dismissing this statement as nothing, given that just yesterday people were attempting to cast doubt on the information Apple had released via Pogue, etc. and this confirms it. (With the exception of the R3D thing, which I had guessed was just Pogue misinterpreting because he's not an expert.)

 

[Tom.Wong]

best third party support for fcp x is already out. it's called adobe creative suite.

 

[Scott Crawley]

Have you never heard of monitoring for reversed interlaced footage? That is one of the main reasons people use a broadcast monitor.

When handling interlaced source material that I understand the need to monitor for possible reverse interlacing, but that is not the primary reason I use a "broadcast" CRT monitor. I use it for color management reasons.

But I still misunderstand your concern that Apple is trying to "kill the TV". Are you concerned that you will have difficulty working with older interlaced material? Is it because you are a proponent of interlacing itself for some other reason? If so what would that be? Is it because you have a very expensive monitor that you are afraid will be useless?

 

[Andrae Palmer]

Have you never heard of outputting directly to tape for broadcast deliverables?

 

[Scott Crawley]

Have you never heard of outputting directly to tape for broadcast deliverables?

So you are afraid that Apple is trying to kill off the NTSC standard for broadcasting to legacy CRT's? I don't mean to be disrespectful and guess about what you meant when you complained that "Apple is trying to kill the TV", but I am beginning to get the impression that you are trying to obfuscate here. Just kindly clarify... As if I were a layperson.

 

[Peter Plevritis]

Apple went back and thought about it. You see this was a 'silent' release. The real release will be Oct 21st.

 

[Andrae Palmer]

So you are afraid that Apple is trying to kill off the NTSC standard for broadcasting to legacy CRT's? I don't mean to be disrespectful and guess about what you meant when you complained that "Apple is trying to kill the TV", but I am beginning to get the impression that you are trying to obfuscate here. Just kindly clarify... As if I were a layperson.

Have you never heard of the ATSC standards?

 

[Scott Crawley]

Have you never heard of the ATSC standards?

Yes, but that doesn't clarify your meaning.

 

[Andrae Palmer]

Yes, but that doesn't clarify your meaning.

If you really want more clarification you can send $100 to my paypal account. I'll give you a one hour of explanation of why interlaced formats are still relevant due to the mass adaption of 1080i HDTV plasma/LCD sets and broadcast bandwidth limitations.

 

[Scott Crawley]

If you really want more clarification you can send $100 to my paypal account. I'll give you a one hour of explanation of why interlaced formats are still relevant due to the mass adaption of 1080i HDTV plasma/LCD sets and broadcast bandwidth limitations.

Sure, hold your breath until you receive payment.

So you are not concerned that "Apple is trying to kill the TV." You were being melodramatic and deliberately vague, perhaps to feed the mob's ire.

 

[Jose Alvarez]

There is NOTHING I can possibly say here in RED land (for obvious reasons [-r3d]) to add something constructive to this discussion, except that I've been using FCPX everyday for the last few days on some complex "re-edits" of some of my old shows, and the more I use it the more I like it.

I'm only "re-editing" a few older shows I KNOW I'll be revisiting in the future, but I'm mostly doing it as training. I'm even reconstructing the last feature I worked on to see how the software behaves handling a 103min film.

I know drivers are coming for my Black Magic hardware, OMF export is already available, XML is already confirmed as coming, my r3d workflow has always been based on ProRes anyways (only one steady customer shooting r3d right now), so as far as I'm concerned, the sky is NOT falling and I see a nice future for FCPx in my studio.

I understand ALL points, in favor and against, so I can only express my personal view. I cut with AVID for many years so I know what I like and don't like about MC.

Every time I've tried to give Adobe's PP a try, just for the sake of learning the application, something goes terribly wrong. I'm not judging PP by my experience with it because I know it is a-typical. But it is what it is.

So the fact that I'm cutting on FCPx just as fast (or faster) that with 7, gives me hope. My last comment is the actual video quality of the playback engine. My old videos look awesome on the FCPx viewer. Lets hope they look just as good or better playing thru SDI.

 

[michael zaletel]

If they were sincere about leaving the past behind and embracing the future, why wouldn't they have included R3D support at launch?

-michael zaletel

 

[Scott Crawley]

If they were sincere about leaving the past behind and embracing the future, why wouldn't they have included R3D support at launch?

-michael zaletel

I wish they did, but if they couldn't replicate the FCP7 base functionality in time for release why would they spend a single second adding .r3d support?... Particularly when they might expect not only that Red could do it themselves, but maybe even do it better? It's just time management, I think.

 

[Andrae Palmer]

Because they want you to save time by transcoding the footage first. They'll also give you the pleasure of purchasing a RED Rocket card to make that transfer speed realtime.

 

[Tim Whitcomb]

All I am going to say is that my girlfriend, who uses iMovie, LOVES this new release and is excited as hell to finally understand how to move up to this PRO app.

As for all the pro's lamenting this BETA release, do you realize how co-dependent you all sound? Like a bofriend who still loves the woman who he claims is verbally abusing him daily.

Kind of fucked up if you think about it, may I suggest a new girlfriend named Avid or Adobe?

This is a ground up re-wrote and for the first time in a LONG TIME... Apple fucked up by releasing it TOO SOON

But my money is on 95% of the haters on here and other boards will be using this NLE daily by the end of the year

 

[Joe Carney]

My money is for people to switch to Avid or Adobe, then in 2 or 3 years time, revisit FCP and make a decision then. Nothing written in stone.

I'm also upset that Avid hasn't yet offered a crossgrade program for people using Windows based NLE's. But C'est la vie.
But I'll find out more tonight.

 

[András Puiz]

Here's their suggested RED workflow...

No, it isn't. Here it is:

Some camera manufacturers will need to update their import plug-ins to work with the new 64-bit architecture of Final Cut Pro, and we are working with them to provide these updates as quickly as possible. Until then, you can use your camera manufacturer’s import software to convert video for Final Cut Pro X.

And then comes the REDCINE-X to ProRes suggestion as an example of a temporary solution. Mkay? Real support is coming soon. As Apple says, "quickly."

Look, I'm not happy with this FCPX rollout. I'm not happy with Apple's new FAQ either. But the truth is bad enough, you don't need to distort it to make it look even worse. There has been more than enough FUD already, no need to add misinformation to the mix as well.

 

[Scott Crawley]

Well if Apple's Red support isn't improved by the time I have Epic, I will likely move to my plan B.

 

[Andrae Palmer]

But my money is on 95% of the haters on here and other boards will be using this NLE daily by the end of the year

Do you think they can have version 3 out by then?

 

[andrewhake]

Reading all of these "responses" is just depressing. Hi-end customers are just such a pain in the ass, haha. You are never going to satisfy everybody, and you are absolutely never going to completely satisfy the hi-end market in this industry. I have no real interest in people who are worried about small workflow details of an application when there are way larger concerns about how projects and media are handled by the app.

I don't know, at the same time I am happy if this opens up creative editing to more people in the world. It is a blast for me actually watching everyone piss their pants over this because they aren't as hi-end as they think they are.