Looking Ahead to 10.1

[Jeremy Garchow]

[Marcus Moore] “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.”

It’s easy, put it in a compound clip and that compound will track back to the Event and it will also change in any Event it is situated, not just the Event it was created in.

I think, as it stands, this is more of a bug than a feature, but it does show a proof of concept,

*puts on rosy glasses*

and it also might be a hint of what’s to come and, certainly(?), hints at what is possible between a Project and Event relationship.

I like the separate Projects and Events. It just needs a bit more heft.

[Dan Stewart]

Ahahaahahaahahaha

[Jeremy Garchow]

[Dan Stewart] “Ahahaahahaahahaha”

https://www.youtube.com/watch?v=RjxqaqV-qdA

Some contents or functionalities here are not available due to your cookie preferences!

This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.

[David Mathis]

My Top 10 List:

1. Make it subscription based only — just kidding!!!
2. I like the idea of a hybrid timeline
3. Add individual sliders for color correction
Example: Shadows, mid and highlight for each channel
4. Bring back the color wheel, the box very much annoys me
5. Add curves
6. Allow key frames for color correction
7. The ability to disable connected clips
8. Real three-point editing
9. Bring back Send to Motion, please!
10. Give Motion its X

[Charlie Austin]

[David Mathis] “7. The ability to disable connected clips”

~ + SHIFT does that now. (hit ~ first and hold, then press SHIFT) Hitting ~ again turns connections back on…

————————————————————-

~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Michael Sanders]

I’ve never understood why, with OS X built on Unix – an OS designed for multi users – that FCP has never been better for sharing, or Aperture for that matter.

Michael Sanders
London Based DP/Editor

[Marcus Moore]

[David Mathis] “8. Real three-point editing “

Maybe I’m missing something but…

https://www.fcp.co/final-cut-pro/tutorials/690-the-basics-of-3-point-editing-in-fcpx-from-steve-martin-and-mark-spencer

Two source, one program. One source (in or out) and two program.

[Charlie Austin]

[Marcus Moore] “Maybe I’m missing something but…”

Yeah, i wondered about that one too… 😉

————————————————————-

~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Oliver Peters]

[Marcus Moore] “It will have been a year since FCPX’s last feature update [10.0.6] in October 2012. That’s by far the longest interval since the FCPX launch. This is about the same timeframe for big updates from the major NLEs.”

Most likely the reality is that at 10.0.6, Apple delivered everything that was originally designed for “version 1”. In other words they were out of the “beta”. People here are fond of thinking that the features from 10.0.0 to 10.0.6 were added in response to customer requests. I sincerely doubt that. In fact, a comment was made to me that “the clock started last October” – i.e. at 10.0.6. This would mean that anything in this newest version, probably will actually be the features prioritized by customer feedback.

Plus, engineering will need to make sure that it works with the new MacPro and Mavericks, without breaking anything in other machines or OS versions. So this might add to the wait.

– Oliver

Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com

[Ronny Courtens]

I concur with Oliver’s assessment.

For our daily editing tasks FCPX already has all the features we need in our shop. Improving these features where required, taking into account what users have frequently requested, would be perfect to start with.

When it comes to new features a (very) deep integration with Logic X and an updated Motion X are highest on my list. This would instantly add a powerful audio mixer + much, much more on the audio side and professional keyframing, simple but effective motion tracking, animatable multipoint masking + much, much more on the compositing side. Most of these features have also been frequently requested by professional users.

I can’t imagine a perfectly seamless integration between the NLE timeline and advanced finishing tools like we have in our Smoke 2013 workflow will be possible in FCPX, at least not in 10.1 yet. If we already could send FCPX projects back and forth to Motion and Logic without any glitches, the existing features get improved and we see a significant boost in overall FCPX performance on the new MacPro, I will be a very happy editor.

– Ronny