-
Wish list for 10.0.9
-
As I said, I’ve had very few issues with stability and performance, so features are more top of mind for me; but I agree that those things should take priority if they’re ongoing concerns for others.
-
I just want them to add Aindreas Gallagher’s headshot to the splash screen, just to piss him off.
-
They seem to think X2Pro is headed in a direction that could mimic the FCP7 media manager. My worry with this is that when a third party takes care of it (for $150) this could let Apple off the hook for doing anything about it. I’ve owned X2Pro since day one, but the reason I really want this feature isn’t for my files, but for the ones I receive. I do a fair amount of finishing work for others with Resolve and FCPX and I’m sick of getting 100GB of “used clips” for 30 second pieces…
————————–
Avid MC, PPro CS6, FCP7 – wasting away on my SSD.
I just can’t quit X.
————————– -
[Oliver Peters] “Timeline scrub bar under each window, especially when Event Viewer is open.”
I’ve read this a few times and I wonder about how it mucks with the existing UI.
Right now, skimming clips occurs whenever you mouse over them passively- and that clip shows up in your Viewer (or Event Viewer) window automatically. No clicking required.
The action your describing would necessitate having to actively click on a clip (or double click ala Legacy FCP) to “load it” in the Event Viewer. So is this clip then “locked” in the Event Viewer until you disengage it? Otherwise as you move your mouse from the clip in the Event Browser over to the Event Viewer, you’re sure to pass over other clips- what happens? Is skimming disabled until you release the active clip in the Event Viewer? As I said I think it poses some UI problems.
If I need to quickly get a longer filmstrip of a clip, I click on the clip in the event viewer and use CMD+OPT+2 to jump to the list view which gives me the longer filmstrip, then I just use CMD+OPT+1 to jump back to thumbnails when I’m done.
-
Aindreas’ stance on FCPX has seeming softened as the bloom has come off the rose on Adobe.
Many people’s concerns and criticisms of the software can be valid, as it still isn’t well suited to some workflows. But the critics are kidding themselves if they think those issues aren’t going to be addressed, and the software won’t continue to mature.
No one can seriously believe that no matter how badly bungled the FCPX launch was, that people won’t consider it when it meets their needs again. Was it really that long ago that people forget Premier was the red-headed “unprofessional” whipping boy? Things change. And people who hold a grudge forever against any company that makes a mistake are going to find themselves either quickly running out of options or changing software way more frequently than anyone should want.
-
This is indeed a hard one to call. To the overall user-base of X, audio export to a DAW might only be needed by a small percentage. If that’s the case, are those users better served by a dedicated plugin supported by a company who’s keenly invested in it’s improvement.
On the other hand, FCPX is the only of the “big” NLEs to not support OMF/AAC export natively.
On the other hand it’s also cheaper than AVID or Premier.
Is that functionality waiting in the wings to “Sherlock” X2Pro? Or is Apple content to let specific workflow requirements be satisfied by 3rd parties.
Only time will tell, I suppose…
-
I wouldn’t call collaborative editing low-hanging fruit.
I also think that FCPX/M5 integration is more complex than it seems at first blush because of the two different timeline models.
Walter Soyka
Principal & Designer at Keen Live
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
RenderBreak Blog – What I’m thinking when my workstation’s thinking
Creative Cow Forum Host: Live & Stage Events -
[Craig Seeman] “preferably with x264 codec.”
Wouldn’t hold your breath for that one Craig,
One hallmark of the modern Apple is that they seem to REALLY like to have and extremely clear IP thread running through their core products. Tying X264’s GNU-GPL into X (a commercial product) would likely make a lot of Apple’s legal team very nervous.
If I had Apple’s money, I’d prefer to OWN the technologies in my products as well.
No reason I can see for them to muddy the waters.
Know someone who teaches video editing in elementary school, high school or college? Tell them to check out http://www.StartEditingNow.com – video editing curriculum complete with licensed practice content.
-
[Marcus Moore] “no matter how badly bungled the FCPX launch was,”
I’m still siding (I think) with Tim Wilson on this one.
I don’t think it was “bungled” in any meaningful way shape or form. X was NEVER going to satisfy the legions who were wedded at their DNA to the FCP-Legacy experience.
They simply HAD to let the adolescent software into the market so that it’s “trial by fire” could begin.
In hindsight, the process simply divided the editing community into two camps. Those who let their emotional reactions delay (or even terminate) their exploration or use of the software – and those who were interested enough to continue to look into it and discover it’s potential for value.
Those of us who liked it from day one – now have an nearly 2 year jump on those who ignored it. I love that.
Yeah, it wojuld have sucked if Apple had actually made a dumb or non-functional product, but they certainly did not – I’ve NEVER failed of complete of deliver a project with it on-time.
I truly appreciate the guys like Jeremy who are still pushing for it’s still developing capabilities to meet the needs of the complex and connected “shop” workflows that the commercial style users need – but unlike him, I haven’t had a crash or slowup or lost keystroke in literally MONTHS.
So it’s certainly a YMMV deal.
FWIW.
Know someone who teaches video editing in elementary school, high school or college? Tell them to check out http://www.StartEditingNow.com – video editing curriculum complete with licensed practice content.
-
I’d agree, though I have heard that the NAB preview was a VERY last minute decision, leading to all the hubbub and bumped presenters. It it may have launched before even the developers thought it was ready.
How different would the response have been if 10.0 had had the capabilities of 10.0.3, with multicam, broadcast monitoring, XML, and other features at launch?
It’s impossible to say whether more damage would have been done by waiting another year and launching at NAB the following year, vs the way things played out.
But a large part of it for me will always be an issue of positioning. If FCPX had been handled like the OS9 to OSX transition, over a couple of years with a steady migration of features- I think much of the vitriol could have been avoided. People don’t mind change so much if it isn’t sprung on them and they feel like they’re participating in it rather than having it forced on them.
Reply to this Discussion! Login or Sign Up