-
So I went off on a rant about FCPX on the “FCP” forum…
-
[Andy Field] “I’m consulting with a large federal agency that has over 500 seats of FCP 7 and 6. It integrates with their Dalet server and they broadcast programs around the world. Some are still on FCP 6…some are still cutting SD DV material……”
I think I know said agency and even if I didn’t – the bigger issue for large enterprises (be it gov, edu or broadcast) is that editing is a part of a larger toolset. Because of this, I would say that the integration between other systems (Dalet in this case) and Adobe are the central issue. To this point, Adobe has really been embraced as the successor to Avid and Apple in terms of integration with over 120 vendors showing Adobe at NAB with over 40 with working panels directly inside of Premiere Pro. This level of integration is unique among NLEs and provides a tightness of integration that cannot be found elsewhere to my knowledge.
Its because of this integration capabilities that I think Adobe serves large enterprises including gov agencies well…
Cmd+Tab to switch to another app for the creative process is just so 2007… 😉
Dennis – Adobe guy
-
[Scot Walker] “Want to delete the media in an Event that isn’t being used? Simple, right? Just tell FCP X to select the unused media and then press the DELETE key, right? Nope. That basic feature isn’t there. The workaround is to duplicate the entire project and hundreds of gigs of referenced and rendered media and then delete the one you duplicated.”
No. If you want to delete the unused media in an event, select the media and CMD+Delete it. If you’re not sure which media is used, then you have to do the exact same thing you had to do in FCP7 which is create a consolidated project and then delete the original. The only difference between the way FCPX does things and FCP7, is that FCPX won’t trim media to only what’s used in the sequence, a mixed blessing to be sure.
Andy
https://www.timesavertutorials.com
-
[John Heagy] “Collaborative workflows on shared storage is what Apple needs to fix before we could use FCPX. It comes down to the nature of events for a local storage single user vs groups using shared storage. In a local system events can be shared with all projects, in shared storage they can’t. Oh… and copying is not sharing… it’s copying.
Admittedly not a concern for the vast majority of users and therefore not a concern for Apple it seems.
“If you’re on NAS, X works essentially exactly the same as 7. Also, could multiple editors work on the same FCP 7 project at the same time? I wasn’t aware of that. Don’t use a SAN,so I can’t comment on that…
————————————————————-
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
Many of these are things that can be addressed via feature requests – Apple has been pretty good so far about making substantial improvements to the software.
The Event Manager X issue, I’m not sure – they may leave that as-is as an opportunity for the third-party developers.
-
I didn’t mean to dog on Adobe, it’s just that most of the people I see switching from FCP7 to Premiere do it because of how similar it is to 7. My biggest point of the rant is that unless you have a very specific reason to stay FCP7, you are better off by going with any of the 3 modern systems.
————————–
Avid MC, PPro CS6, FCP7 – wasting away on my SSD.
I just can’t quit X.
————————– -
You can blur the text now using the text parameters itself. Those could be animated to create a position, but it is possible that someone with great Motion authoring skills (since every FCPX transition is a Motion project) could look at the current blur transition and make one that both works to only blur the top layer and still respects the alpha channel of each layer. I tried playing with it and haven’t cracked it yet.
-
While the Blur transitions certainly could have been set up better, I think it’s at least a good thing that they’re all now editable in Motion. That was what sold me on FCPX.
-
[Andy Field] “Actually there are quite a few reasons. I’m consulting with a large federal agency that has over 500 seats of FCP 7 and 6. It integrates with their Dalet server and they broadcast programs around the world. Some are still on FCP 6…some are still cutting SD DV material……”
I can understand this, it’s such a large workforce that any change is going to be painful. The rant was inspired by the hundreds of people I’ve encountered that have to freedom to switch to another NLE, but stick with 7 because they know it well and aren’t will to learn a new system. It’s like an editing purgatory, where every passing day they stay with 7 is another day they could have gotten better at Media Composer, Premiere, or X. Not everyone using 7 is averse to change, but I think it’s a very strong majority, especially with independent editors and small companies that have the flexibility to change.
————————–
Avid MC, PPro CS6, FCP7 – wasting away on my SSD.
I just can’t quit X.
————————– -
[Nicholas Zimmerman] “My biggest point of the rant is that unless you have a very specific reason to stay FCP7, you are better off by going with any of the 3 modern systems.”
Many people do have great reasons:
1) It still works. It does what they need, they know how to use it, they have very tried and true workflows that still work great, do exactly what they need to do.
There is no reason to change, just because something new and shiny came out. You change when you need to change…when something in the production/post pipeline requires it, THEN you change. Changing for the sake of change…that’s no reason. “But this is better and faster and slicker!” For you…not for everyone. FCP 7 is still the best option for many people. I have several clients who still use it, several large companies do as well. NOW one of them is thinking of changing, as they just got asked to do a 4K show. Now they have a reason to change.
2) Cost. As mentioned, there are many large facilities that have built their post around FCP 7. HUGE number of seats and servers. To change will cost a lot of money. In new licenses, possible new hardware/OS, training/down time. So when they look at the options, typically they stick with what they have because…well…look up at number 1.
3) Comfort factor/muscle memory. Editors, like martial artists, rely on muscle memory. We are fast because we know what commands are where, what tricks do what…and all sorts of things that enable us to use the NLE very quickly. Switching means relearning everything. Thus why many are considering PPro Next.
You use and love FCX. Great! We all aren’t like you and moved onto the next shiny new thing. Just like we shouldn’t judge you for using FCX, and think it a toy (I don’t, some do), you also shouldn’t judge others for staying behind. People use what works for them. Get over it.
FCX is a new forum for a new editing app. Many have said that before…it isn’t an update, it’s new. Thus, a new forum.
Shane
Little Frog Post
Read my blog, Little Frog in High Def -
Well, no, in FCP7 it was easy to delete the unused material. Highlight the sequence, press cmd+f and find unused media. Then, deleted the unused media. Or you cold mark the used media with a label. Nice stuff. I’d like to see a find unused function in X for sure. And a trim/handles function when duplicating a project. That’s all I feel is missing from the media management.
Reply to this Discussion! Login or Sign Up