-
Is anyone actually using FCPX?
-
[Hector berrebi] “which is not helping me like it more”
The more I use it, the more I like it but also the more I recognize how incomplete it is. Lots of little things need to be implemented. In Events Browser, selecting a range on a clip and going to something else and back causes the range selection to disappear on that clip.
-
[MIke Guidotti] “As of now scuttlebutt is that shared storage is not in the future for this program.”
Just curious, where’d you hear that or how do you know?
I mean it might not work right now, but how do you know it was designed as a single user experience?
Seems a little far fetched to me.
-
[Craig Seeman] “When Apple eventually hooks…”
The more I think about it, I would be happiest if Apple did next to NOTHING to actually develop these features, and focused on HOOKS for third parties.
I’ll give you an example using codecs. Would you rather have (alphabetically I think) ARRI, Canon, Panasonic, RED, Sony and the like making sure that their footage is ready to use natively, with performance that might even be faster than what Apple could do, IMMEDIATELY, every time a new format is released? Or wait for Apple to get around to working it in and maybe not have it work as well as it might.
But Apple has to provide the hooks.
They did this better than anybody else ever has with FXPlug. Look at GPU-accelerated plugs from people like CoreMelt. They not only look and act like native plug-ins, but in FCP 7, they’re far faster than anything that Apple themselves came up with, and provide titling, FX, and audio features that Apple never got around to. With products as good as these for such reasonable prices, why would Apple have bothered? I’d hope they wouldn’t.
Knowing that Apple can make hooks of that quality, now in 64 bits, I WANT third parties to lead the way with features, while Apple focuses on the core, and the hooks.
Heresy I know, and frustrating as all get-out until the features that Apple has indicated are coming (multicam, XML, etc.) actually show up, but the focus on foundation rather than features for this first release may be what excites me most.
Note that I have no comment on how Apple has managed this, their commitment to pros, blah blah blah. It’s not that I have an opinion and won’t share it for political reasons. I really don’t have one. Anyone who will ever read this knows more than I do. I’m just saying that I can imagine this working itself out in a pretty interesting way.
Of course, my opinion is worth the amount of money I make using FCP, which is zero. But I was both an editor and a developer, so my perspective on the value of lean development to maximum experience is different than most.
Hooks, baby. I’m saying it’s all about the hooks. Get that as right in the future as FXPlug, and the possibilities are very nearly endless.
-
[Craig Seeman] “Sometimes I have to wonder why professionals don’t see this potential in FCPX.”
I see it. I also see that by the time they introduce multiseat collaborative features it might be irrlelevant
-
[Craig Seeman] “Apple has already told various journalists that it will be very fast. That’s the point of App Store distribution vs disk and ship for major upgrades”
I think for me the issue is that there is a mountain – no, a Himalayas – of stuff that needs addressing which means that however fast the updates come it will still take a good long while till it all settles down comfortably, as I am increasingly thinking it will.
[Craig Seeman] “I’m finding everything works so far”
I shouldn’t have said that – I agree that it all works, although it does have a beta-like bugginess to it which means quite a few random crashes for me a least, but there are loads of things (see the Techniques forum) that don’t work remotely as well as we have reasonable justification to expect they should. Lots of sketches for ideas that will probably come good, too many things that are still cobbled together from iMovie builds (Projects!!!!!!!), I think it is reasonable to say.
But overall, and I’m risking my life saying it here, I’m starting to be a fan and am impressed by the potentiality of so much that we’re seeing as much as by what’s already implemented.
Simon Ubsdell
Director/Editor/Writer
http://www.tokyo-uk.com -
[MIke Guidotti] “As of now scuttlebutt is that shared storage is not in the future for this program.”
Stop spreading false rumors. If you can’t attribute a reliable source and not another person also spreading rumors then your post is meaningless or a deliberate troll.
-
[Simon Ubsdell] “But overall, and I’m risking my life saying it here, I’m starting to be a fan and am impressed by the potentiality of so much that we’re seeing as much as by what’s already implemented.”
The way you feel is perfectly normal according to the Kubler-Ross model.
https://en.wikipedia.org/wiki/Kübler-Ross_model
Sounds like you are almost at acceptance. You shouldn’t feel like you re putting your life on the line.
I have not downloaded and installed FCPx yet as I haven’t had time to build a clean Snow Leopard boot disk to do so quite yet. As soon as that’s ready, I will start to play with it. From what I have seen and read, I am very eager to start learning the building blocks. The organization is something that I have been dreaming about. I hate bins. They are nothing but jail cells for your footage. On a lot of my projects, the media gets completely maximized, which means the footage can take on different roles. What if I organize my footage by day in a bin? That means I have to know what day the footage was shot on. Wen working on a project for six months, those days start to lose their meaning. What if I organize by location? Meaning a shoot was in California, Arizona, Chicago and London. That means my footage is locked in those locations, but it tells me nothing about the rest of the footage.
If there’s parity in between those locations, meaning we shot a manufacturer in Chicago and a manufacturer in Arizona that both build widgets, I can now search for Chicago Widgets, Arizona Widgets, or more importantly, I can search for Widgets. If I am looking for a particular shot, I don’t have to remember, was that shot in CA or AZ? Or London? Or What day did we shoot that again?
Let’s say it was a three camera shoot. I can now search for other angles without having to go look in the bin. I can simply search for InterviewName B Cam. I also hope I can append a tc number to that. So if I need the c cam of a particular interview to cut to, I can search for InterviewName C Cam 10:23:45:23 and the angle will show up right where I need it to be to add to the timeline. I could do on and on about how this keyword functionality will make for easier editing.
I have been using P2 metadata like this extensively for a number of years now. Fcpx will make it even easier to aggregate and sort all of this data (I rely on FCP7s columns currently which is rather limiting). In my opinion, it should just be a big pool of data. There’s no need to arbitrarily segregate your media in folders as media can have properties that apply this AND that, not just this OR that. This is the biggest paradigm shift for many. Myself, I welcome this functionality with open arms. Just have to wait and see how it goes with more connectivity with other post-prod systems and hardware, but my feeling is that will come in due time.
Jeremy
-
[Michael Aranyshev] “I see it. I also see that by the time they introduce multiseat collaborative features it might be irrlelevant”
I can’t see it every being irrelevant short of Apple dropping FCPX entirely. People move one way and they move again IF (big if) it’s worthwhile.
I see Apple’s database/metadata approach begin very powerful and very flexible. I don’t think it’ll take more than a year to get there (just my guess).
The problem is people can’t add FCP7 seats until that point comes since Apple pulled FCP7. That’s their big mistake. The one thing Apple can hope for, short of putting FCP7 back for the time being, is that their Server/Shared Storage integration will be so power/affordable that it’s easy for facilities to move back.
-
[Simon Ubsdell] “it will still take a good long while till it all settles down comfortably,”
It depends on how far along the coders are. Some company have multi teared developed such that while this version is being readied, others are already well into developing the next release. We’ll probably know in about 4 months when the next update happens.
[Simon Ubsdell] “Lots of sketches for ideas that will probably come good,”
I agree. For example, Scopes look excellent but they had no ability to be configured and no way to have it default to something other that it always opening on histogram I believe.
It seems like a skeleton for an excellent NLE but they need to do a lot of work.
[Simon Ubsdell] “But overall, and I’m risking my life saying it here, I’m starting to be a fan and am impressed by the potentiality of so much that we’re seeing as much as by what’s already implemented.”
Myself as well. I think Apple’s biggest mistake was strategic. There should have been a year long transition where both FCS and FCPX were available so people would have time to learn while Apple has time to implement features.
-
I can see journalists who used to depend on professional editors, cutting out professional editors and editing news clips themselves.
I can also see students and businessman editing together presentation videos for class or a business meeting, thus effectively giving the ax to dedicated in-house A/V departments.
Will this be the end of professional editors and the beginning of bad-editing?
Apple has already shown us they prefer their users to have a limited internet-experience by banning Flash from their iOS devices — perhaps they prefer presentation videos and newsclips to start with curtain-closing transitions and end with star wipes?
All joking aside, I could see Michael Scott being VERY EXCITED for FCPX.
FCP — RIP 2011
Reply to this Discussion! Login or Sign Up