ullanta
Veteran
http://alex4d.wordpress.com/2011/07/06/notes-from-apples-london-pro-briefing-on-final-cut-pro-x/
If ya can believe it... whatever soon is...
If ya can believe it... whatever soon is...
Last edited:
FCP7 site licenses, FCPX EDL, XML, XSAN soon!
- Thread starter ullanta
- Start date
Hawk Teflon
Veteran
"9. Some FCPX updates will be free some will cost…"
That's a shame.
That's a shame.
Hawk Teflon
Veteran
But if it's a component that was a part of the older studio already, then no I don't see it as something that should cost. FCS 6 and 6.0.6 were of no difference in price. Just software updates.
cheezweezl
Veteran
But I thought millions of iMovie customers would be buying fcpx. There's the revenue. And why would you hope that it costs? You don't like free stuff?
vegas06
Well-known member
I think that it seems like Mulitcam (which Apple seemed to have let slip the other day would be (should be) FREE) and other updates that are in FCP7 would be free.
However, the updates that will cost are those that are being developed by 3rd party developers, like XML support (from Automatic Duck) etc. that Apple won't produce or support.
Also, things such as previewing (PCI cards), filters and the like that were not developed by Apple are not supported by Apple but rather 3rd parties. Apple didn't release any code to these developers and as such have to be developed and tested before release.
This is one of the things that I think have people peeved, as their current systems and workflow depend on some of these things.
That's how it is for me slightly, as I prefer PluralEyes to FCPX sync feature. The FCPX sync works ok, but it's not as fast as Plural Eyes seems to be.
Also, I have been previewing externally via Black magic Intensity Pro card, which currently won't work in FCPX. Hopefully Black Magic will have driver updates soon for the card.
FCPX is useable for me right now, but external previewing is critical for me as I deliver a lot of DVD formats as well as online content. I can preview the preview monitor using the share feature and my ATI Radeon HD 5770 Video card, but it's only preview quality, and I don't know how accurate the color actually is in FCPX.
I know that FCP 7 wasn't reliable for color work, but the BM Intensity from FCP 7 was.
This was supposed to be corrected in FCPx, but I haven't been able to test or seen any tests yet confirming this.
However, the updates that will cost are those that are being developed by 3rd party developers, like XML support (from Automatic Duck) etc. that Apple won't produce or support.
Also, things such as previewing (PCI cards), filters and the like that were not developed by Apple are not supported by Apple but rather 3rd parties. Apple didn't release any code to these developers and as such have to be developed and tested before release.
This is one of the things that I think have people peeved, as their current systems and workflow depend on some of these things.
That's how it is for me slightly, as I prefer PluralEyes to FCPX sync feature. The FCPX sync works ok, but it's not as fast as Plural Eyes seems to be.
Also, I have been previewing externally via Black magic Intensity Pro card, which currently won't work in FCPX. Hopefully Black Magic will have driver updates soon for the card.
FCPX is useable for me right now, but external previewing is critical for me as I deliver a lot of DVD formats as well as online content. I can preview the preview monitor using the share feature and my ATI Radeon HD 5770 Video card, but it's only preview quality, and I don't know how accurate the color actually is in FCPX.
I know that FCP 7 wasn't reliable for color work, but the BM Intensity from FCP 7 was.
This was supposed to be corrected in FCPx, but I haven't been able to test or seen any tests yet confirming this.
Last edited:
filmguy123
Veteran
Multicam will be a free upgrade -> http://www.fcp.co/forum/4-final-cut-pro-x-fcpx/346-my-take-on-the-apple-fcpx-briefing-in-london-6711 (more extensive info @ this link)
Vultch
Well-known member
FCPX is too expensive for the average iMovie user
vegas06
Well-known member
Yep saw this post today.
Glad that multicam will be a FREE update. But it should be a FREE one anyway, as this should be part of FCPX anyway, as it's a critical pro feature that most if not all NLEs (Premiere, Vegas, Edius, Avid etc.) seem to have these days.
Especially if it's to justify the price difference between iMovie (FREE) and FCPX. As much of what's in FCPX was already available in iMovie.
Ya know what's funny is that I wonder how new the code actually is, since it seems that FCPX is built on the iMovie platform.
Yes it was written for 64 bit, but how much of the code past that is really different?
Glad that multicam will be a FREE update. But it should be a FREE one anyway, as this should be part of FCPX anyway, as it's a critical pro feature that most if not all NLEs (Premiere, Vegas, Edius, Avid etc.) seem to have these days.
Especially if it's to justify the price difference between iMovie (FREE) and FCPX. As much of what's in FCPX was already available in iMovie.
Ya know what's funny is that I wonder how new the code actually is, since it seems that FCPX is built on the iMovie platform.
Yes it was written for 64 bit, but how much of the code past that is really different?
filmguy123
Veteran
I would assume there is some code from iMovie in regards to skimming and other features (it would be a waste not to use it), but it is for the most part undoubtedly all new code. It's not just that it's 64-bit, it's written in cocoa whereas FCP7 was in written in carbon. iMovie was originally written as a pro-app, a companion to FCP for importing footage (called "first cut") used to quickly skim and select footage for import/make a rough cut.
Pro Res isn't available in iMovie. Just AIC. That's significant.
Beyond that, how much have you worked in iMovie and FCP X?
It would be great if you would detail what identical features exist in both, and the features absent in one or the other.
Thanks.
Last edited:
vegas06
Well-known member
"It would be great if you would detail what identical features exist in both, and the features absent in one or the other."
Well for starters the obvious one is that the interface is identical and how the application functions. The color and audio functions, transitions/effects, speed controls (even time ramping), skimming, magnetic timeline, precision editor, seem to be identical in both applications.
There are the obvious differences, in that FCPX is 64 bit and can work with additional codecs such as ProRes (BTW, Apple why did you take away ProResLT. I would use it often instead of the standard ProRes.).
Once Apple adds additional features like XML import and Multicam, the divide widens even more.
But in the normal operation of the application and tools available, the apps are pretty similar.
Well for starters the obvious one is that the interface is identical and how the application functions. The color and audio functions, transitions/effects, speed controls (even time ramping), skimming, magnetic timeline, precision editor, seem to be identical in both applications.
There are the obvious differences, in that FCPX is 64 bit and can work with additional codecs such as ProRes (BTW, Apple why did you take away ProResLT. I would use it often instead of the standard ProRes.).
Once Apple adds additional features like XML import and Multicam, the divide widens even more.
But in the normal operation of the application and tools available, the apps are pretty similar.
Wait, what? Is that true? That's not good at all if so.
vegas06
Well-known member
Yep, its true. On import you can transcend to standard process or proxy, but that's all.You can export prlt via compressor, which is good. But no way to transcend on import to prlt.Maybe Apple did away with prlt on import because FCPX works with avchd files natively now.
Last edited:
stoneinapond
Veteran
Color work in FCP X is far, far ahead of what is availbale in iMovie. Speed controls are far, far ahead of what is availbale in iMovie. I would say that the control of transistions and such is also much, much deeper in FCP X. Media management is light years away from the smaller sibling and background rendering is a joy to work with (due in part because of the utilization of the GPU I would venture a guess).
There is so much more, but that is just the beginning. Where I would like to see improvements other than the usual list of suspects, is in refining the audio workflow, although once export is enabled, I'd be more than happy to do the final work in Pro Tools.
The interfaces look pretty similar, but the controls in virtually all the "identical features" you mentioned are significantly deeper and far more powerful in FCP X than iMovie.
Those include what you mention: "color and audio functions, transitions/effects, speed controls (even time ramping), skimming, magnetic timeline, precision editor" and others not mentioned.
Same with the management of media, which is more powerful.
The availability of pro res is significant, and also DVCProHD in all its variants. Auditioning for both audio and video is a huge feature.
Have you used FCP X extensively? Many have, and I'm still going through to sets of tutorials, one free and one commercial, and I have to affirmatively disagree with your observations.
I believe others will as well.
Those include what you mention: "color and audio functions, transitions/effects, speed controls (even time ramping), skimming, magnetic timeline, precision editor" and others not mentioned.
Same with the management of media, which is more powerful.
The availability of pro res is significant, and also DVCProHD in all its variants. Auditioning for both audio and video is a huge feature.
Have you used FCP X extensively? Many have, and I'm still going through to sets of tutorials, one free and one commercial, and I have to affirmatively disagree with your observations.
I believe others will as well.
vegas06
Well-known member
David I agree with what you say. That FCPX and iMovie controls are virtually identical, but FCPX has deeper control sets in each.
My original point was that it seemed that Apple based the framework of FCPX on iMovie, both in look and functionality. Albeit with new code and a deeper control set. This isn't unusual in software as many software manufacturers have consumer/pro apps that use the same interface, but the pro app has a deeper, more robust feature set (Adobe Premeire/Premiere Express, Sony Vegas/Vegas Studio etc.). This way one can start with the consumer version and move up to the pro application without a great deal of learning a new program. This is what I see Apple doing with FCPX and iMovie.
The problem for many pro's though is that they left the UI of FCP and a lot of pro features behind.
I have no doubt that a lot of those features will work they're way back into FCPX. But may long time FCP users that are upset aren't happy about learning a new UI. For me this is the norm in the IT software game. I am constantly learning new applications, as old ones go away all of the time, or I outgrow a program. I'm planning on using FCP7 when needed, but try to migrate to FCPX, which for me isn't that hard at the moment. Just that I need some additional features to migrate to a full time basis.
I have used FCPX quite a bit, as I went through the Ripple Training tutorials. I haven't cut my chops yet in a full edit, but might actually tackle a basic wedding edit that I have coming up.
Now with that being said I am going to take Adobe on the Creative Suite FCP Upgrade. As the price is a god deal for what you get and I am curious to see what Premiere with the Mercury engine can do.
I shoot on DSLR and Sony NX5U cameras, so my media is AVCHD, with no tape involved. I have been transcoding to ProRes LT in FCP, but to tell you the truth it's time consuming for me, as I really need to capture and edit right away in most instances. I am working on a 2006 Intel Mac Pro with 12GB of ram, but did upgrade my graphics card recently to the AIT Radeon HD 5770, so I should be able to run the mercury engine. I also have an Intel 2008 MacBook Pro that has compatible graphics card.
I know my system is slow by today's standards, but it still does the job just fine. Waiting to see if Apple decides to launch a new Mac Pro, or I go with an iMac or MacBook Pro and Thunderbolt storage.
All in all, I am up to learning a new program, as all of these (FCP7, FCPX, Sony Vegas 10, Adobe Premiere) are just tools, and the more tools I have in my toolbox to chose from the better I am for different situations.
My original point was that it seemed that Apple based the framework of FCPX on iMovie, both in look and functionality. Albeit with new code and a deeper control set. This isn't unusual in software as many software manufacturers have consumer/pro apps that use the same interface, but the pro app has a deeper, more robust feature set (Adobe Premeire/Premiere Express, Sony Vegas/Vegas Studio etc.). This way one can start with the consumer version and move up to the pro application without a great deal of learning a new program. This is what I see Apple doing with FCPX and iMovie.
The problem for many pro's though is that they left the UI of FCP and a lot of pro features behind.
I have no doubt that a lot of those features will work they're way back into FCPX. But may long time FCP users that are upset aren't happy about learning a new UI. For me this is the norm in the IT software game. I am constantly learning new applications, as old ones go away all of the time, or I outgrow a program. I'm planning on using FCP7 when needed, but try to migrate to FCPX, which for me isn't that hard at the moment. Just that I need some additional features to migrate to a full time basis.
I have used FCPX quite a bit, as I went through the Ripple Training tutorials. I haven't cut my chops yet in a full edit, but might actually tackle a basic wedding edit that I have coming up.
Now with that being said I am going to take Adobe on the Creative Suite FCP Upgrade. As the price is a god deal for what you get and I am curious to see what Premiere with the Mercury engine can do.
I shoot on DSLR and Sony NX5U cameras, so my media is AVCHD, with no tape involved. I have been transcoding to ProRes LT in FCP, but to tell you the truth it's time consuming for me, as I really need to capture and edit right away in most instances. I am working on a 2006 Intel Mac Pro with 12GB of ram, but did upgrade my graphics card recently to the AIT Radeon HD 5770, so I should be able to run the mercury engine. I also have an Intel 2008 MacBook Pro that has compatible graphics card.
I know my system is slow by today's standards, but it still does the job just fine. Waiting to see if Apple decides to launch a new Mac Pro, or I go with an iMac or MacBook Pro and Thunderbolt storage.
All in all, I am up to learning a new program, as all of these (FCP7, FCPX, Sony Vegas 10, Adobe Premiere) are just tools, and the more tools I have in my toolbox to chose from the better I am for different situations.
We are on the same pages then.
Interestingly, I also like learning new interfaces/approaches/paradigms to achieving things. The learning process, at least for me, enables me to adjust my workflows for particular projects.
The deeper, more robust control set for FCP X does facilitate a pretty fast organizational head start for some of my projects.
But I still am more comfortable with FCP 5/6/7.
I'm guessing a big event for Apple late next week. Lion for certain and probably new Sandy Bridge MacBook Airs with Thunderbolt. Also, a possible new MacPro.
Interestingly, I also like learning new interfaces/approaches/paradigms to achieving things. The learning process, at least for me, enables me to adjust my workflows for particular projects.
The deeper, more robust control set for FCP X does facilitate a pretty fast organizational head start for some of my projects.
But I still am more comfortable with FCP 5/6/7.
I'm guessing a big event for Apple late next week. Lion for certain and probably new Sandy Bridge MacBook Airs with Thunderbolt. Also, a possible new MacPro.