FCPX 10.1.2 PRE-RELEASE DISCUSSION

There definitely seems to be some memory leak issues of some sort- working for several hours in my 7min sequences sees noticeable performance slowdowns. Either relaunching X or doing a full restart definitely resets things back to a more fluid experience.

Let's hope the time they're taking with 10.1.2 helps with some of these issues.

I'm sure you have, but please do report this. Anyone seeing this issue should report it, over and over if necessary.

artofoe wrote: And poor rendering performance of K5000 card in 10.1.1 should be improved!
10.0.9 is faster about 2-3 times at rendering and exporting than 10.1.1 using nvidia K5000.

Check your NVIDIA card. Make sure is up to date.

Thanks to Alex4D for spotting that RED has released an updated version of the RED WORKFLOW TOOL.

www.red.com/downloads/5340f90826465a7c2b000338

GENERAL CHANGES:

Added: SCARLET-X DRAGON support.
Added: DRAGON MONOCHROME support.
Fixed: Issue where DRAGON and MONOCHROME clips could have an incorrect look applied.


Unfortunately no 3rd party dual GPU support.

Latest CUDA is 6.0.37.

artofoe wrote: And poor rendering performance of K5000 card in 10.1.1 should be improved!
10.0.9 is faster about 2-3 times at rendering and exporting than 10.1.1 using nvidia K5000.

Also, make sure, turn off the background render in your FCPX (pref. settings)

BenB wrote: Latest CUDA is 6.0.37.

yup, the cuda card must up to date. this is depends on which type mac you're using for fcpx, compressor and motion

Yes I would love to see some major Motion Updates. I tell myself they are coming because the app hasn't been X'ed yet.

Compressor not so much, I honestly think it's time it was put out to pasture and replaced with a program that does everything concerned with preflight and final delivery. Including things like broadcast safe, burnt in code, presentation menus and buttons.

What I think is really telling is that just about all the big plugin makers seem to be sitting on their hands.
Nothing from Coremelt, Neat Video and little new stuff from the others.

This tells me they are waiting to release when this next version comes out as there will be some fairly significant changes in the way things work with plugins?

It's hard to guess what Apple will do with the naming schemes.

Final Cut Pro jumped 2 whole numbers from 7 to X- but it was a complete rethink of the application (or so I've heard)

Logic Pro X was the next logical step up from version 9. But it also received a major overhaul in UI and functionality. Just not as radical as X's.

Motion 5 received the same UI overhaul when it launched with X, but relatively few new features. 5.1 was even lighter on features. If there's a Motion X in the works, it could still be years away. And what would justify the X'ing of Motion I can't even imagine. Perhaps the integration of features from Shake or the much rumoured Phenomenon? I can't even imagine.

Aperture is the most in need of attention. It seems to me Lightroom has lapped it several times over at this point. Before Adobe went subscription only, I would have said Apple probably missed the boat on that one by now, but with things being the way they are- there is definitely room for a non-subscription alternative- even if it's still chasing Lightroom on some features. Richard Taylor has said on twitter that an Apple rep hinted this was coming, but there's no telling when.

If Apple has a 4K Cinema Display to show off at WWDC, a new Aperture X would make for a great demo (though ProApps never get stage time at WWDC- so maybe just a mention). So would FCP X for that matter, but that's just being optimistic....

Plug-in support for Motion has never been strong, and honestly I think it's the biggest thing keeping Motion from being a viable competitor to AE for a lot of users. As I said above, I'm hoping FXPlug3 support is a step towards better 3rd party support.

Seanus wrote: Nothing from Coremelt

The new versions of SliceX and TrackX came out a few days ago. Take a look at www.coremelt.com/component/content/artic...ositing-release.html

Strangely, neither SliceX or TrackX work in Motion- which is honestly where I could see myself using them more.

rgilman wrote:

Seanus wrote: Nothing from Coremelt

The new versions of SliceX and TrackX came out a few days ago. Take a look at www.coremelt.com/component/content/artic...ositing-release.html

Oh really?! I wonder why I didn't get an email.

THANKS!

Disproportionate Pictures wrote: Strangely, neither SliceX or TrackX work in Motion- which is honestly where I could see myself using them more.

I thought the initial enthusiasm around SliceX was based on its ability to give a little bit of Motion like functionality in FCPX

[quote="merc"

I thought the initial enthusiasm around SliceX was based on its ability to give a little bit of Motion like functionality in FCPX [/quote]

The Mocha roto and tracking is awesome. Doing rough previz VFX in the edit is amazing.

merc wrote:

Disproportionate Pictures wrote: Strangely, neither SliceX or TrackX work in Motion- which is honestly where I could see myself using them more.

I thought the initial enthusiasm around SliceX was based on its ability to give a little bit of Motion like functionality in FCPX

Well, I guess it would be- except that using Mocha via SliceX or Track X is much more integrated than the Mocha/Motion workflow.

I completely agree Marcus.

Part of me does miss the RT-ing between FCP & Motion, but having the core melt plugs allow me to do that work in the actual timeline is the way I like to work now. Being able to make editing changes without leaving the app is great.

When I cut, I do temp composites of VFX shots, replacing the green screen with a guess of what would be back there from google image search. Being able to track the moving camera in FCP X is huge. Not having green backgrounds is an even bigger deal.

I remember about five years ago I heard a rumor that Apple was going to make the next version of FCP 'all in one' with motion, color, and compressor built in.

That's definitely the case with color, and about halfway with motion. I'd even argue that compressor is partly built in being able to share in the background while still cutting.

Seanus wrote: ... Compressor not so much, I honestly think it's time it was put out to pasture and replaced with a program that does everything concerned with preflight and final delivery....

from the hobbyist corner:
It would be a masterstroke, if Apple would buck-up some long forgotten iDVD-features back into Compressor! That drop-dead-simple customizing of discs was and is still unsurpassed. Reading hundreds of requests in the iMovie (and some in the FCPX) sections of ASC, there's still a wish to ban memories on antiqué discs.

Not overloaded as legacy iDVD with tons of spinning templates, but the 'main' features: autostart, main menu, chapter selection; customizable drag'n drop buttons & backgrounds - done.

.. yepp, I know, discs is obsolete for more than 8y in the Apple ecosphere .... as a 'hobby', in some well hidden tab in Compressor... would be nice, and 'boom' sales-numbers... probably.

.. just an idea...

@Darren

Based on the timeframe, I wonder if what you heard was related to the dead-ended version of FCP that was theoretically being worked on for 64bit Carbon. Impossible to say for sure, of course.

This will be forever the conversation- an "all in one" solution vs tightly integrated separate apps. To me, the idea of a single "Final Cut Pro" that contains everything that FCS used to have would be a giant bag of hurt. There's just too much code to go wrong, and it's all your eggs in one basket. Of course, proper round-tripping can be equally dodgy, as the old Motion/FCP7 RT proves. But in my mind at least you're compartmentalizing your potential problems.

I think the only big issue with the old Motion round-trip was that you'd very easily get crashes if you tried to play unrendered Motion assets in FCP7, AND that those Motion "pre comps" often became rendered for seemingly no reason.

What I'd like to see is this-

1. Like the old version, to be able to lasso clips in a Project and go "send to Motion".
2. Have a good interchange so that any effects or CC applied in FCP transferred to Motion
3. When jumping back to FCP when you're done in Motion, FCP NEVER tries to pay back unrendered Motion comps. If it's not rendered, there's a screen that tells you you have to. Though some simple comps could absolutely be played back in real-time (as published comps prove)- I think the potential for crashes is too great if you're dealing with the unknown complexity of Motion projects.

The only way I could see unrendered Motion projects working is if there's some kind of built-in "playbackability" test that Motion could run. If Motion determines you're hardware can't play the project at the full framerate, then you're prompted to render.

or something...

I have some little requests I think would be very useful:

-Ability to group the libraries by disc, just as we could do with Events until 10.0.9

-A useful Event Viewer, where you could see the same clues as in the browser thumbnail: the rating and keyword lines and the range selections, just to have a more precise place to make selections.

-Ability to match frame + open in the Event Viewer in just one shortcut.

-A search box in the Import window. I can't believe this is not there from the very beginning.

-Ability to colour clips in the Timelines. I guess this could be a good Roles improvement.

-Please return the marks comments back to the screen. Please. Please. I mean... PLEASE.

-Improve the visual representation for selected range in the Timeline. Now it seems you've just selected the clips in the Primary storyline. It would be more clear as in Motion: an In/Out line clearly separating the range.

-Make the keyframes mess a little bit usable. Not amazing, not awesome. Just... working.

-Make the Crop and Transform animations linear by default... and let us decide if we want them smooth.

"-Ability to group the libraries by disc, just as we could do with Events until 10.0.9"

Or at least be able to make folders in the libraries panel in which we could place libraries.

"-A useful Event Viewer, where you could see the same clues as in the browser thumbnail: the rating and keyword lines and the range selections, just to have a more precise place to make selections."

Not sure how this would work in the event viewer. You'd see the bars appear on the clip as you played through it?

"-Please return the marks comments back to the screen. Please. Please. I mean... PLEASE."

??? Who's Mark, and what are his comments? I must have slept through this.

Nice list.