Michael Hancock
Forum Replies Created
-
[Bill Davis] “You argue that there are “many many flaws” in X.
I argue that after nearly 200 delivered programs with it personally, I haven’t experienced a single program construction flaw to the extent I couldn’t complete and deliver my jobs with speed and success. So I’d suggest what you are seeing as “flaws” are perhaps really just minor assaults on traditional expectations and minor inconveniences that can safely be ignored in most use cases.”I will admit, flaws is probably not the right word to use, because it implies a bug in the program. I haven’t run into any show stopping bugs in FCPX (or Premiere or Avid, if we’re being fair), so it’s poor word choice on my part. I’m talking more about weaknesses/limitations in the program that cause a noticeable drop in efficiency for me.
For example, these shortcomings affect me on a regular basis:
– The lack of true background rendering/transcoding/export in FCPX
– The inability to read .mts files natively without rewrapping (and other codecs the program doesn’t natively support)
– The inability to flatten multicam edits or apply stabilization to them
– Lack of multiple timecode displays
– Lack of keyboard control when working with connected clips and secondary storylines
– Inability to mix proxy and original/optimized media in an edit
– Poor relinking
– Lack of layout customization
– No CDL or custom LUT support (without a third party program – I want batch, source side custom LUT/CDL application)
– No ability to apply roles in the event, after an edit has started, and update a sequence with the new roles
– Lack of roles based audio effects (to act like a track based effect in other NLEs)
– Sync indicators when detaching audioThat’s a short list. As you can imagine, my full list is pretty long. You may consider these ‘minor inconveniences that can safely be ignored” – I consider them “flaws” or weaknesses in the program that I’d like to see addressed by Apple. A lack of Feature X doesn’t mean I can’t get my work done. It just means it’s going to take longer, when it doesn’t have to.
And to be clear, I’m not saying that my list of feature requests means the program is unusable. That’s never been my argument because it’s not true. As you said – you’ve delivered 200+ programs with it. I’ve also delivered lots of projects with it and haven’t missed a deadline, but I’ve also delivered projects just as quickly and effectively using Premiere, Avid, and Resolve (which was more of an experiment, but it worked). I just see areas where FCPX is deficient, and I want that improved.
Perhaps it’s my use of multiple NLEs that makes me more sensitive to this stuff. No matter which program I’m using, I end up wishing I had feature A from NLE X, or feature B from NLE Y. When I’m in FCPX I want Avid’s level of trimming, timecode displays, true subclips, and bin/timeline/program custom layouts. When I’m in Avid or Premiere I want the keywords, favorites, skimmer, and smart collections from FCPX (smart collections need to be in every NLE – they are, in my opinion, the most valuable thing Apple has brought to NLE design). When I’m in Avid I want Premiere’s superior keyboard control in my bins and timeline (Premiere has by far the most advanced keyboard control of any NLE I’ve used). Everything is a tradeoff, but that’s not going to stop me from expecting each NLE to look at the competition, see where they’re deficient, and improve. And I’ll continue to badger each company to implement the features I want to improve my editing experience. That’s why they have feature request pages. ?
[Bill Davis] “As to our need to advocate to “make it better” – Apple is already doing that. I say that with confidence as someone who got to see the NDA presentations at NAB. They regularly listen. I’ve seen them videotaping editor surveys at NAB and other professional venues. They also tend to go well beyond “just listening” with an eye to real innovation – something I think that will become clear very soon. “
It can’t be soon enough. I’ve seen Premiere, Resolve, and even Avid update and improve their programs more than Apple has in the last year and half, so my expectations for Apple are incredibly high. I just hope it’s not another 3D text style update with lots of flash but very little substance (for the type of work I do).
[Bill Davis] “I’ve contended for a long time that the editors most likely to dismiss X’s capabilities are those who bring hardened workflow expectations to X – and keep seeing it in terms of what they have “lost” – as opposed to what they have gained.
“How about, I know what I’ve gained and know what I’ve lost, and I want what I’ve lost to be added back in? I don’t agree that everything Apple has done that’s been an improvement makes up for what they’re missing. That’s an odd argument to make. If Ford released a car that got 300 miles per gallon but didn’t have a seats, should we not ask for seats? Why not have great mileage and seats?
I send Apple feedback constantly. I hope you do too. And if you do, what types of things are you requesting? I’d be interested to know where you think FCPX needs improvement, and I’d be happy to submit feature requests for the same thing. Squeaky wheel and all.
[Bill Davis] “But feel free to list its flaws from your perspective. And let’s examine them from the view of what “most” editors are likely to require.”
See above for a short list of things. See this thread for more: https://forums.creativecow.net/thread/335/84031
But I don’t understand why my list should have anything to do with what “most” editors are likely to require. If most editors require tracks, would you want Apple to add them back in?
My list is for me – I’m the one using the program, so I’ll list what I want in the program. You also use the program so you make a list of what you want. If our lists converge, that’s great. If they don’t, maybe I should look at your list and ask if there’s stuff on it that I haven’t considered. I would probably find things I would like but I had never thought about – so I’ll submit feedback for them. And you would probably find things on my list that you never thought about but would save you lots of time. You could submit feedback. I learn more from people’s list of feature requests than hearing about how great an NLE is by rehashing what it can already do. Tell me what it can’t do but should – that’s the exciting stuff.
—————-
Michael Hancock
Editor -
[Bill Davis] “So if you weren’t here for the first few years, my advice is to ignore the tone and look for the actual arguments lurking beneath. “
I’ve been reading this forum since day one. I’m well aware of the early days of FCPX and the vitriol and silly arguments that were hashed out here. This forum is my guilty pleasure, in a way. It’s like politics, but safer. LOL.
I also know how people’s tone online can be misconstrued and how to read past it and look at the arguments. I try to do that, but even if I ignore the tone I seem to read into Robin’s posts, I still find the arguments trite, overly semantic, condescending and dismissive. And I don’t think I’m alone in this. But maybe I am, and if so – I apologize.
[Bill Davis] “So don’t be surprised if we occasionally jump. “
Maybe take a deep breath and realize it’s just an NLE, and one with many, many flaws? Like all of them. If you really want to introduce people to the wonders and joys of FCPX, you can’t be afraid to recognize where it’s inadequate and needs improvement. Go hang out on the official Avid forums for a week. You’ll see pretty quickly how people can both love and loathe their software in the interest of making it better.
—————-
Michael Hancock
Editor -
To quote your earlier post:
[Robin S. Kurz] ” I for one have maybe used the position tool TWICE and one of those times was for mere demonstration purposes. So much for essential or “need to know”.”
I read this as, you don’t use it, therefore it’s unnecessary. Or perhaps that was hyperbole? In which case, how does that advance the conversation? Or perhaps you were referring still to noobs here? For me, the ease-of-use for an amateur is of little consequence to me – I want an edit system that is fast, deep, and gets out of my way when I edit. If that means I have to use a modifier, so be it. I mean, I have to use a modifier to “go to in” and “go to out” in FCPX, and that’s a pretty important function in my day to day life. There are aspects of FCPX that have greatly improved my day to day editing, but there are still massive improvements that could be made. Do you agree with that, or is the app perfect as is?
The idea that your way is the right way and others are doing it wrong is a common element to your posts Robin. It seems that, if you can’t understand why a person would do something a certain way, or you don’t like they way they do it, then it’s the wrong way and they’re wrong. Perhaps I’m just reading your posts wrong, but they come across as very condescending and dismissive most of the time, and I feel like it limits what could otherwise be a interesting and honest conversation about FCPX and it’s strengths and weaknesses, particularly in regards to the design choices Apple has made and whether they are an improvement over the classic NLE design, given different workflows.
—————-
Michael Hancock
Editor -
[Robin S. Kurz] “Whether it’s “hidden” or not, no one really needs it in the end anyway.”
The position tool is for more than just moving clips around with ripple mode. It’s also used when trimming, where you may not want everything to ripple. In fact, I was finalizing an edit today and spent half the time going into “position” mode to make some trims, then hitting P to get out of it for others.
To say that no one needs or it’s unnecessary shows a complete lack of understanding or imagination in regards to other people’s workflows or methods of working.
—————-
Michael Hancock
Editor -
Nope. You have to close them, then select your edit point, to roll them together. If you have the video or audio selected when they’re expanded and close them, it will still only roll what was selected when they were expanded.
It’s a lot of unnecessary clicks. Submit a feature request if you’d like to see it changed. I have.
https://www.apple.com/feedback/finalcutpro.html
—————-
Michael Hancock
Editor -
It gets major improvements about as often as the MacPro! Oh…wait….
To the OP though – when Apple released FCPX they said they had a 10 year plan. It’s 5 years in, so you could reasonably expect 5 more years before they toss it out and start over.
—————-
Michael Hancock
Editor -
[Darren Roark] “but a Mac Pro refresh of any significance has only really been possible since April as that’s when all the new GPUs came out that were a large enough leap forward. “
But this is also because Apple decided to redesign the MacPro so you couldn’t swap out the graphics cards when new ones came on the market that were considerably better (like the handful of cards nVidia has released). So their inability to update with any significant leap forward is entirely of their own design.
—————-
Michael Hancock
Editor -
[Noah Kadner] “Are you certain you’re not colliding with any system settings in Accessibility?”
Checked that – nothing colliding there. And I can remap Shift Down in other apps just fine, and the setting sticks. Try it on your system – I’d be interested to see if it sticks for you, or if it resets when you shut down/reopen FCPX.
[Noah Kadner] “File a report with Apple FCPX feedback.”
I filed a report about zoom bugs a while ago. May as well file another one.
—————-
Michael Hancock
Editor -
You have Zoom In and Zoom Out mapped to Shift Up and Shift Down and you aren’t seeing this issue?
I just remapped my keyboard (US English) to test what Michael Paul is seeing, and I’m seeing exactly what he is. It works when you first map it, but when you restart the Zoom Out is no longer mapped.
It shows it’s mapped when you search for Zoom Out, but if you select the Down Arrow it’s no longer listed, and no longer works.
—————-
Michael Hancock
Editor -
[Michael Paul] “So it’s a common bug and there is no fix so the solution is to just give in and surrender? “
For now – yes. Sorry.
In the meantime – submit a bug report.
https://www.apple.com/feedback/finalcutpro.html
—————-
Michael Hancock
Editor