August 29, 2013 at 4:30 pm
[Mathieu Ghekiere] “But that was something that was hinted at exactly with the ‘Guard’ system that Alex found out in the underlying code of FCPX, in an early stage:”
The Guard system there refers to tracks, not lanes, and that same post also shows what looks like a traditional tracked timeline, not the magnetic timeline. It’s possible this shows the groudnwork for a future feature, but it’s also possible that the sharing system was a scrapped idea just like standard tracks.
I have no idea to what extent Apple wishes to support collaborative editing, but I guess we’ll see soon enough!
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
August 29, 2013 at 4:34 pm
Even deeper, it would be great to see database info from Projects shared with Events, so you can see which footage has already been used IN the Event (rather than just duplicated frames ala Legacy).
It’s unclear to me whether that type of relationship is possible with the separated Event/Project structure. Right now metadata is all downstream from Events—–>Projects. Any Role data added in a Project doesn’t track back to the media in the Event. If Events and Projects were combined into a single database, this could solve those problems. Though with multi-user situations the concept of separated Events/Projects ( or Edits) does make good logical sense. If edits were part of Events, the constant database changes while multiple editors work on the same Event could be problematic.
There’s positives and negatives to both concepts.
August 29, 2013 at 4:41 pm
According to those who had sit-downs with Apple at NAB, collaborative workflows is definitely on their radar. But whether they’ll be ready with a solution for 10.1 is anybody’s guess.
As great as these features would be, my personal hope is that Apple “closes the loop” on the underlying concepts. Clean up the timeline. Provide a good mixing solution. And reintegrate a good roundtrip solution with Motion and Logic.
And please, bring back iChat theatre! God I miss that…
August 29, 2013 at 5:39 pm
My guess is a big one. Why else hold off on any real features for an entire year. The only thing that comes to mind since 10.0.6 was the added Log support in 10.0.8, other than that, nada. It looks like Maverick will include some power user features (new full screen dual screen) so hopefully FCPX will follow in it’s “serious” footsteps. Logic X is probably (hopefully) the best indication we’ve got on where Apple wants to go.
FCP X Certified Pro, Level Two
August 29, 2013 at 6:24 pm
[Nicholas Zimmerman] “Why else hold off on any real features for an entire year. “
Because they have nothing in the short term to contribute?
August 29, 2013 at 6:52 pm
I’m anxious to see what Apple comes up with next. I do think some sort of optional hybrid track mode would be cool. I also wish they’d make up their minds with Events vs. Projects – you can really slow things down on a big project if you don’t set up your Event/Project correctly – something that is not a problem in any other NLE.
I’ve been in NLE limbo the past couple of years since X… I still rely on Sony Vegas for many projects, I’m loving Premiere CC and both Win 7 and OSX and have played a little with MC 7 but Apple is always the one with the biggest surprises and let downs – I’m hoping for big things in the next rev.
Writer, Editor, Director
Downtown Long Beach, California
August 29, 2013 at 7:04 pm
[Lance Bachelder] ” but Apple is always the one with the biggest surprises and let downs – I’m hoping for big things in the next rev.
Oh, yes. Me too. My guess that it will be something. Above, I was just challenging a logical assertion by simply answering the question. But, yeah. I think the next version might be neat. Fun times!
August 29, 2013 at 7:26 pm
As I noted above, I wonder if the reason for this long gestation period means “foundational” vs “feature” changes (at least in part). Apple did 3 feature releases over the first 13 months [10.0.1, 10.0.3, and 10.0.6].
I’m not a programer, but I’d imagine with that kind of turnaround time, you’re somewhat limited in how “deep” you can dig into the code. So the features we’ve seen are ones that could be hung on the current framework: multicam, broadcast monitoring, XML improvements, Event Viewer, RED support, etc..
More substantive changes would require more time to implement across the entire application.
I think there will be new “features”, but some good under the hood stuff too. Performance, UI, probably some structural changes to accommodate Mavericks improved multi display support.
August 29, 2013 at 7:35 pm
[Marcus Moore] “‘m not a programer, but I’d imagine with that kind of turnaround time, you’re somewhat limited in how “deep” you can dig into the code. So the features we’ve seen are ones that could be hung on the current framework: multicam, broadcast monitoring, XML improvements, Event Viewer, RED support, etc..”
I think you’re right… Often during app development code gets “forked”, so the released version gets maintenance and the occasional feature, while the “new” version is being built. That’s probably what’s going on…
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~
August 29, 2013 at 7:52 pm
That’d be hip.