Stephen Bakopanos
Forum Replies Created
-
[Chris Kenny] “Do these more reasonable defaults make the app easier to use for consumers? Sure. But that’s because they make more sense, not because they remove control. I’m unclear precisely what it is about an interface that makes more sense that supposedly makes it unsuitable for professional users.”
Chris, you’ve been a voice of reason in amongst a sea of hysteria – thanks for keeping things a little bit grounded here. FCPX certainly does have some BIG limitations in it’s current incarnation which makes it unsuitable for broadcast editing – that much is certain – but it’s by no means a consumer app.
I wonder what the reaction would be if people had been using the FCP X workflow and magnetic timeline for the last 10 years and then Apple brought out the FCP7 workflow and timeline to replace it? I reckon we’d be seeing a similar negative response. People don’t like change.
-
[Michael Largé] “I don’t see an option to select ProRes422 in the prefs. I only see boxes for transcoding. I’m assuming FCPX automatically uses that codec?”
Yep. Although I’d advise bringing in Canon DSLR footage via Grinder or FCP7 with the E1 plugin in order to retain time of day timecode information.
-
[Tom Olsen] “It is called Final Cut Pro, not Final Cut Indie. “
Nor is it called “Final Cut Broadcast”. Some people here seem to think that being a “pro” is the exclusive domain of broadcast editing.
-
I’d wait.
FCP7 does a pretty good job, so there’s no reason to go running away from it right now.
Give Apple a bit of time to right the wrongs they’ve made with this launch product – with XML, OMF, EDL and Multicam FCPX will be a pretty solid package.
In the meantime, use any downtime to acquaint yourself with the new workflow of FCP X.
If you’re DETERMINED to switch however, Adobe would be my bet. It’s quite similar to FCP7 and you can easily remap the keyboard shortcuts to match those of FCP. Most of the industry already have it installed on their machines as part of Creative Suite, so I reckon it will be the most popular choice.
But again, I’d hold out to see what happens with FCP X.
-
[Michael Largé] “I remember being excited upon hearing that FCPX would edit DSLR footage natively (no more transcoding I thought), but it’s not true. It still transcodes the footage; just in the background so the waiting has been eliminated (makes my system real laggy when I try to edit while transcoding). Here’s what’s bothering me – even though I unchecked the “Copy files to folder” option on the import preferences, my footage is still being copied and now I have a new 111 GB folder on my drive. Am I doing something wrong or is this just the way FCPX works? “
If you want to edit natively without transcoding, you need to turn transcoding off in the preferences. By turning off “Copy files to event folder”, you’re just stopping it from copying the original files over. If you leave transcoding on, FCPX will still transcode them and place them in an “optimized media” folder. If you have both turned off, FCPX will edit the original files natively and leave them wherever they are. This can be dangerous as you might inadvertently delete them (for instance, if they’re still on your camera card). Despite native support, it’s still advisable to convert any H264 files to ProRes422.
-
[Charles Wannop] “My App Store “receipt” calls it self a Tax Invoice at the top of the form BUT has no mention of GST anywhere on the rest of the form. “
I got an email receipt which had this at the very bottom:
ABN 46 002 510 054. Total Includes GST. You can find the iTunes Store Terms of Sale and Sales Policies by launching your iTunes application and clicking on Terms of Sale or Sales Policies
So it should be included.
-
[Andrew Richards] “The difference is the removal of hard tracks in the FCPX timeline allows for more flexible handling of audio that still maps to specific output busses. That’s the whole point of the Magnetic Timeline- collisions can be avoided when you abstract the role of the media from its physical placement in the timeline.”
This is indeed where the power of FCPX lies. Sure, it’s got a limited feature set at the moment, but the potential for the future is huge. Those who want to write it of as a consumer product (i.e. iMovie Plus), are being incredibly closed minded.
-
[Matt Callac] “Problem is most people aren’t paying enough attention to the details. they’re too busy assuming they know what apple is doing and planning to jump platforms.”
Spot on Matt. I wish some people would spend less time blogging and spreading FUD and more time actually learning how to use the program. Take this blog for example:
https://jefferyharrell.tumblr.com/post/6865416226/project-management-in-fcp-x-no-just-no
He spends multiple paragraphs whinging about not being able to filter out keyworded clips, before declaring it “impossible” to do. The reality of course, is that it is indeed possible. In fact, it’s painfully simple – just click on a simple drop menu on top of the event browser (or hit CTRL+X). If he’d spent the hour that he probably spent composing that post, he might have actually worked it out for himself…
-
[Tim Vaughan] “By that logic, 2 lines up it says (void)importiMovieProject:(800)arg1. So they obviously haven’t figured out if they want it to be iMovie Pro or FCP.”
That makes no logical sense whatsoever. It just means that Apple intend to support multiple formats for import. The more formats it can support, the better. In fact, I’d say that’s a pretty good measure of a “pro” app. Just because it can import iMovie files, doesn’t make it iMovie.
FCPX has some serious professional underpinnings, which, as we can see, are yet to be fully exploited.
-
Hopefully some of the hysteria will die down now. Apple have messed up the release without a doubt, but it’s becoming clear that they haven’t abandoned pro users and that they do intend on making Final Cut Pro live up to the final part of its name. In time I can see it being quite a powerful program.