Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Final Cut Pro X Released

Avid is never compatible with a brand new OS release from Microsoft or Apple, at least no immediately. It usually takes a little while for them to do internal testing and/or release an update to ensure your system doesn't break if/when you upgrade. If you switch to Avid, just don't upgrade to Lion until it's approved.

I posted, because like myself, potential users didn't know that.
 
I posted, because like myself, potential users didn't know that.

Fair enough. I started on Avid so I never upgrade an OS until I get word that it's approved from my software vendors. And even then I prefer to wait a bit for the undiscovered bugs to shake out.
 
That's what I figured. What was told to me was that XML would likely be released as an SDK (there's a new XML format within FCP X) to third party developers and that XML interchange may or may not be done in-house. It might actually be another third party i/o step, like Automatic Duck.

There's XML generation code in the app. It seems like it would be sort of silly to not have a menu command to export it. Indeed, digging around in the app yields a method structured as if it's intended to be invoked from a UI control, that brings up an XML export dialog. There wouldn't be much reason for that to exist if Apple were going to offer up XML exclusively in response to API calls, and not expose it as a user-level feature.

EDL sounded like it would definitely be third party. FCP7 project import was a big maybe. Also could be in-house or third party.

Yeah, I think both of these will probably be third-party. The former because it's pretty niche by the standards of the wider market, the latter because, I think, with all the conceptual differences in how the new timeline works, Apple can't make it work seamlessly enough that they're willing to put their name on it.

I'm fine with this, really, especially with Apple taking this approach to EDL exporting. FCP 7 was never all that strong on EDL exporting anyway. Certainly not compared with Media Composer. A third-party writing software focused entirely on this task can probably do something better. Will it cost money? Sure. So what? The base price of FCP X is lower than that of competing software. And multi-seat facilities won't have to buy this sort of workflow software for every workstation. Even if it does end up costing $1000 to get FCP X with Motion, Compressor, and all the I/O options a post facility needs (and I suspect it will be less than that once we get a little third party competition going), that's still less than half the price of Media Composer, and for any systems that are just straight edit stations, you can skip the extras and pay $300 a seat. Avid and Adobe don't give you that option.

If Apple's smart, they'll create a section in the App Store just for FCP X plugins and workflow tools. That could help build a really vibrant ecosystem around the product.

They acknowledged importance of multi-cam. They were also very sketchy about how mixing might be implemented. They didn't seem to want to do an actual mixer panel, but rather deal with it through metadata. Presumably "audio roles" would be used. Right now those are only active as search parameters.

I can't really imagine how you could mix conventional rigid audio tracks into the magnetic timeline in a sensible way, so yeah, it's going to be metadata-based.
 
If Apple's smart, they'll create a section in the App Store just for FCP X plugins and workflow tools. That could help build a really vibrant ecosystem around the product.

The more I read about this and look at history, the more this makes sense as their strategy for FCPX all along. (Note: I'm not excusing their poor communication or neglect of certain demographics). This would be similar to one of the things that's made iOS so superior -- the 3rd party ecosystem and specialization it provides.

The only challenge/difference is that -- even if you include prosumers -- the market for specialized color or motion or sound mastering apps is soooooooo much smaller than consumer demand for apps. Or even the demand of mainstream
business people for apps.

So it remains to seen if 3rd parties will be willing and able to develop incredible apps around FCPX that are profitable, yet still reasonably priced for the professionals that need them.

However, the potential is there and is an exciting possibility. I mean ... imagine Da Vinci Resolve "Lite" as many here have been clamoring for, that works seamlessly with FCPX and is only $99 or even $199. I think many would jump on it.

I can imagine being able to build a custom editing/grading/finishing suite around FCPX for around the same price as FCS3, less than MC6 (when not on sale) and around the same price as Premier.

That would be mind-blowing, and if Apple is smart they will do everything in their power to support and encourage 3rd party development around FCPX.
 
However, the potential is there and is an exciting possibility. I mean ... imagine Da Vinci Resolve "Lite" as many here have been clamoring for, that works seamlessly with FCPX and is only $99 or even $199. I think many would jump on it.

There is a Resolve Lite. It's coming out this month, it's entirely free, and it's hard to imagine it won't be able to import FCP X projects at some point in the future. Possibly within a month or two of Apple enabling XML export; Blackmagic has been really good with Resolve updates.
 
Very interesting. I'm definitely going to give it a try. You never know. I think Apple is not done yet, just going through one of their many 'let's change the world' stages.

Apple rarely misses the boat. It's often the case that when Apple appears to be missing the boat, it's because they're up to something. The most recent high-profile example of this was the atrocious nature of Apple's solution to transferring documents between computers and iOS devices (that horrid list in iTunes). Why did we get such a crappy solution? Because it was a stopgap while they were working on iCloud's transparent document syncing features.

The lack of workflow features in FCP X is so comprehensive that it just screams "Apple is up to something". Look at precisely what they say in the FAQ: "We will release a set of APIs in the next few weeks so that third-party developers can access the next-generation XML in Final Cut Pro X."

It's not just "We will add the option to export XML". It's "We will release of set of APIs..." FCP 7 never offered anything that could be plausibly described as a "set of APIs". Combine this with the evidence of Python scripting support embedded in FCP X, and there could be something very interesting in the works.
 
The plot thickens:

Notes from Apple’s Pro briefing on Final Cut Pro X in London
Looks like Apple’s softly softly actions to keep professionals onside are continuing.

Sam Johnson(of AMV LAB) was invited, amongst others, to an Apple briefing on Final Cut Pro X.

Here are is what Sam tweeted after the briefing. Follow him on Twitter where he posts as @aPostEngineer

1. FCP XML in/out is coming via 3rd party soon…no FCP 6/7 support project support coming ever it seems…

2. Ability to buy FCP7 licenses for enterprise deployments coming in the next few weeks…

3. FCPX EDL import/export coming soon…

4. FCPX AJA plugins coming soon for tape capture and layback…capture straight into FCPX bins.

5. XSAN support for FCPX coming in the next few weeks…

6. FCPX Broadcast video output via #Blackmagic & @AJAVideo coming soon…

7. Additional codec support for FCPX via 3rd Parties coming soon…

8. Customizable sequence TC in FCPX for master exports coming soon…

9. Some FCPX updates will be free some will cost…
 
I think the term "the plot thickens" is usually used when a surprising development takes place.

The fact that these things are being furiously worked on is not a surprise. The fact that these things weren't in the program to start with was.

Anyway, I'm trying to actually play around with editing in FCP X. I found some good things but also some real questions. I've posted a couple of times about that in this thread but nobody answered me (how to add an ease to a rotation keyframe, for example?). Mind directing me to a thread where we can talk about actually using Final Cut Pro X?

Bruce Allen
www.boacinema.com
 
I think the term "the plot thickens" is usually used when a surprising development takes place.

The fact that these things are being furiously worked on is not a surprise. The fact that these things weren't in the program to start with was.

The fact that these things are being worked on -- and that Apple practically seems to be working down the missing feature checklists a lot of us have been making -- isn't a surprise to people who agree with my argument that Apple is not abandoning the high-end market, but just shipped FCP X aggressively early. But that position has hardly been uncontroversial in this thread.

Anyway, there were some surprises out of this event. I wasn't expecting Apple to restore FCP 7 licensing for enterprise customers, I wasn't expecting XSAN support that soon (the timing makes me think it's Lion-related), and this is the first clear confirmation we have of 'real' video output (though I did expect that).

Anyway, I'm trying to actually play around with editing in FCP X. I found some good things but also some real questions. I've posted a couple of times about that in this thread but nobody answered me (how to add an ease to a rotation keyframe, for example?). Mind directing me to a thread where we can talk about actually using Final Cut Pro X?

Try here.
 
No Craig, you are not the only one. I want multiple sequences too. Currently working on a project with 35 sequences, which would have been a nightmare without these possibilities.
 
Has Apple released any notes as to when (or who) may develop a multi-camera tool for use in FCPX? We just finalized post-production on a 10-camera broadcast concert show, with another coming in the next month, and despite all the cool new features like background rendering and 64-bit cocoa coding, FCPX may not yet be the right tool for us.

Burke Doeren

Director of Pre & Post-Production
MindFox Productions, LLC
www.MindFoxProductions.com
 
Has Apple released any notes as to when (or who) may develop a multi-camera tool for use in FCPX? We just finalized post-production on a 10-camera broadcast concert show, with another coming in the next month, and despite all the cool new features like background rendering and 64-bit cocoa coding, FCPX may not yet be the right tool for us.

I would expect Multicam within 6months or by this time next year at the latest based on the little feedback apple has put out there, it may even get here sooner, a matter of months.
 
even if apple gets the imho standard features we are missing into fcpx via third parties.
well, the fact that you cant open fcp 7 files is such a bummer.
i know at least 10 feature film productions who now, even after they picture locked, take the time and money to recreate
their projects in avid or premiere so they can be sure they have the future possibility to re-edit.
apple actually killed all old fcp projects.
thats unreliable from them.
this like red bringing in r4d files without the possibility to read r3d files ever again.

i am sure all the plugins for fcpx end up costing some cash.
automatic duck is 500 alone.
maybe it will be awesome sometime in the future or maybe this was the wrong move for apple re pro (feature and TV) market.
nobody knows and future will tell.
i'll grab the avid crossgrade for sure. the next 7 years they should be around.
fcpx right now is perfect for web based musicvids and commercials.
 
Back
Top