Welcome to our community

Be a part of something great, join today!

Register Log in
  • 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

Just stay with FCP7 for now.
 
Dave Blackham said:
So wheres Color ? and soundtrack ? and DVD Studio Pro ?
Click to expand...

by the sounds of the overview it got integrated into FCPX, only Motion and compressor didn't

it says it right about where the talk of sound and colour go in "the power of final cut studio has been moved into FCPX" or something like that...

I'm only assuming thats the case because the least they should do is say that Colour and Soundtrack aren't ready yet or at least give a date for those two...

Seems weird to give only 2 portions of the entire suite...but never know...this is Apple...no RED support for FCPX so...clearly more...errr...

pleasant? surprises to come

Odd thought. There was a paper that went around, saying about thunderbolt and RED Rocket...wouldn't apple just allow for RED Rocket to do the decoding instead of the CPU? Given it also said that it was in the case that one wanted to free up CPU space...hinting for RED support perhaps?
 
ChristopherKenworthy said:
Have Red stopped talking to Apple? They seemed like good friends when Red were first on the scene. Is this a parting of the ways?
Click to expand...

I'm sure Red kept talking to Apple! I'm not as sure that Apple kept talking back though? They are kinda the opposite of Red in terms of openness, friendliness, etc.

There are Avid and Adobe and Foundry employees on this forum, all being awesome to you guys, all doing their best to make their software RED-friendly. Why not reward them by switching over :p

That said, I'm still downloading the new FCP to play with it - likely there are some great ideas still that we can ask the (more responsive) folks on the opposing software teams to implement in their software :)

Bruce Allen
www.boacinema.com
 
I think the panic might need to be tempered with some time using the new FCP. In other words, it just dropped, so how many hours has everyone used it and given it a thorough test drive? Are there reasons to be concerned? Sure. There are things missing in this initial release. There is 3rd party support not integrated yet. I think what needs to happen with this initial release is the editing community needs to see if they like the dramatic change Apple has made. If the answer becomes yes, then they have succeeded and can build on the new app, adding features that are heavily requested, and perhaps not adding features they believe take the app backwards. Personally, I will need a month or so to come to a conclusion. That will involve working with various types of footage, learning the ins and outs of the interface, investigating workflows, creating a list of wants/needs, etc. Until then I can say I know very little about this app or its potential. I do know that all of the NLEs have strengths and weaknesses, including Avid. It really comes down to the needs of you and your facility. Only you know what kind of work you do and know what it takes to get it done.

Although not ideal in the long run, I do like the way Apple has allowed both versions of FCP to be installed. Smart move on their part.
 
Be careful when playing around with FCP X people!

Final Cut Pro X: "Open in Timeline" edits cause permanent change to source media

Symptoms
Editing a clip after using the "Open in Timeline" command in the event browser changes the source media file.

Products Affected
Final Cut Pro X
Resolution
If Final Cut Pro X has not been restarted, the Undo command is available to restore the original media. To undo, click Edit and choose Undo.

If Final Cut Pro X has been restarted after the change has been made, the clip will need to be reimported in order to restore the original. To do this, mount the camera or camera archive and import the clip again. This will create a new clip in the event browser.
Click to expand...

http://support.apple.com/kb/TS3816?viewlocale=en_US
 
Last edited:
Brandon J.F. said:
http://library.creativecow.net/adcock_gary/FCPX/1

The available output options:

output-options.jpg


I love the YouTube and Facebook options :rolleyes5:
Click to expand...

Well yes, I suppose it has to be useful for something. We had FCP 1.25 so have been at this a while now, There is deep unhappyness here. Tears from upstairs, if any one is listening please sort this out and whilst your at it ask for my iPhone 4 ariel to be fixed too.
 
Appears Apple's primary focus is to support iPhone, iPad and streaming internet, at least for this release. Can't believe they don't support milticamera with all the people using multiple DSLRs. Even the WEVA market is going to have issues with what is missing. Colorsync and Audition are nice, but not enough to convince me to switch. I wonder how 3rd party codec like Cineform will operate?
 
I will stick to FCP7 for a while, probably 6 months, before upgrading. I'm sure there will be some bugs. Hopefully the full Color, R3D support, OMF, XML, EDL functionality, etc. are added in by then. I look forward to trying out all the new features, though. I hope some of my friends buy it today :)

Is it available to play with in the physical Apple stores?
 
looks like a toy and what a disappointment from Apple.
Sorry to say that the day has certainly come to jump ship for sure.

Any one know if Avid are still doing there deal?
 
MattGahan said:
Anyone know if the gamma issues have been fixed? Or will we need to wait for Lion for that?
Click to expand...
Havent checked that but so far Ive managed to render over AFP network using files over 2GB. Now thats ProRES files, next test Uncompressed.
 
I personally prefer Vegas Pro 10 over Premiere 5.5 (i own both). It's quite flexible, and in many ways more intuitive to work with than any other editor i've used. Supports 4K and 32 bit colorspaces, dpx:s, multicamera, uses Red files natively etc. and has audio tools that make using an external audio app feel like a good workaround to a problem that shouldn't exist in the first place ;-)

Not saying it's better for everyone, just that it's better for me personally - and at least worth a look for people considering a switch.

PS: I do envy the mercury playback engine though, i get much better real time performance on Premiere than on Vegas. On my oldish machine (it was great in 2007), with a low end CUDA enabled card, i get a realtime playback at what appears to be half resolution when editing .r3d:s in a 1080p timeline in Premiere - on Vegas, i need to drop to quarter rez for real time: i get around 15 fps at half rez, and around 5 fps at full. Despite this, i'm willing to sacrifice the performance for the Vegas workflow...
 
I was hopeful for Apple to get it together in FCPX.. They've been messing with this a long time.. It's very clear they are putting a lot of attention on the iphone market here. They may improve this a few versions down the road, but I think they will lose a lot of people in the meantime.

Until then, I hope black magic can get themselves straightened out and start supporting Premiere and the PC. (I mean resolve)

Jay
 
Steve Sherrick said:
I think what needs to happen with this initial release is the editing community needs to see if they like the dramatic change Apple has made. If the answer becomes yes, then they have succeeded and can build on the new app, adding features that are heavily requested, and perhaps not adding features they believe take the app backwards.

[SNIP]

Although not ideal in the long run, I do like the way Apple has allowed both versions of FCP to be installed. Smart move on their part.
Click to expand...

I definitely respect your opinion. Still, I can't help but feel like they put consumers (way) before the pros for this release. Support for keeping the old version seems like an implicit admission that this version doesn't serve pro needs, at least not yet. At best, it will take months to add all the missing features. At worst, they won't come at all.

FCPX is two steps foward (resolution/performance), many steps back (tape support, multicam, CC, EDL, XML, etc), and no R3D support to boot. Not to mention alleged bugs (modifying source footage - really?). Meanwhile, other stable products that run on the same platform provide resolution/speed plus all the missing features today...

If Apple's plan is to treat this as a preview for a subsequent pro release, it seems like they should have messaged that better. Instead, the message seems to be that their first priority is the consumer market. That doesn't bode well for the future, and creates the possibility (likelihood?) that falling back to FCP7 is just continuing down a dead end street. Just my .02...

IMO, this release was Apple's chance to let the pro community know that they've been listening. Apparently our call was dropped - they must have been using an iPhone!
 
Now is the time for Adobe to offer a cross-grade special!

The overview video mention that FCPX includes "key" features from Color and Soundtrack, but apparently not all. No multicam support? Talk about a huge step backward. Maybe better said as, "One step forward, two steps back." (Edit: Tim said it better before me)

I'm all for intuitive interfaces but WHY does that often mean de-contented and dumbed down? I'm very disappointed that so much was left out.
 
You must log in or register to reply here.
Back
Top