Rob Mackintosh
Forum Replies Created
-
Every other NLE I’ve used allows you to manage sequences within the same window as your media.
FCPX makes the distinction between nested sequences and master sequences. Nested sequences or “compound clips” can be created, key-worded and viewed in the event browser; master sequences or “projects” have there own special browser with a reduced feature set.
Apple should do away with the project browser and allow all sequences to use FCPXs metadata tools.
If there’s architectural reasons this can’t be done, they’ve got the architecture wrong. -
Yes that’s a fairly common issue Philip.
There’s something horribly inefficient in the way FCPX composites titles.
Each FCPX title is effectively a motion project with a text layer and drop zone with access to whatever is underneath it.
So in AE terms with three layers of text the top layer is essentially a comp containing a precomp, containing a precomp that contains the video on the primary storyline and a text layer.
In terms of a Motion project – my mental model is of a single group with a video layer and three layers of text, when what you probably have is four groups, each a clone of what’s below it in the stack, and with a layer of text in the top three groups.
It’s late down here in the Antipodes and that may not make any sense.
-
On reflection (and reading Ben Balser’s response to his post) some of the advice he received might be BS.
That said, the performance of FCPX is still a real concern and a deal-breaker for me continuing to use it.
-
What about this from the same post:
Q: Are multiple projects in the project library continuing to be processed while working on a current open project, thus impacting the performance of FCPX?
A: YES…things such as rendering thumbnails or effects that have not been completed while the project was open will continue to be processed in the background, even though they are not the currently opened project.WTF? They haven’t prioritized UI responsiveness.
Ironic considering iOS shines in this area compared with Android
Check his system specs
Bought a new mac pro 12 core with 48 gig ram and two 500 gig solid state Crucial M4 drives.
If he’s having problems . . .
-
No worries. Are you adapting FCPx titles or generators?
In a PAL project the NTSC titles and generators can be used – FCPX deals in absolute time so a 60 frame intro is remapped to 2 seconds.
I have used a copy of the continuous title (with the kooky 3d effects stripped out) for similar lists.
Stacking anymore than 5 of these on top of each other, so the text appears as the word is spoken, is bit of a drag on my system. What you are doing in motion may be a better option. -
Use the Finder and copy it to a location outside of the Motion Templates folder.
When you open it and “save as” you get the regular save dialogue not the FCP X generator version.
By the looks of it you could skip this step and export any FCP X generator via the Share menu.
That way it’s also available as a proxy in FCPX.
-
[David Roth Weiss] “I’m guessing that great up/down and standards conversions may be in the future of Blackmagic I/O devices and cards.”
I agree with that. I also wonder how long it will be before we see a DaVinci hardware accelerator.
Or does the pace of GPU development make that unnecessary?
Could they create a system to rival Quantel?
I guess they already have one with the Linux version of Resolve ( and it’s support for 16 GPUs).
-
Also a pretty close match with LUT Buddy loading the Technicolor supplied LUT into AE.
To use it like a LUT add it to an adjustment layer (text-less title) and stretch that out along your timeline.
Grade your clips with the color board or by adding other effects to the actual clip.If necessary for your workflow you can use it like a viewer LUT in Nuke and turn it off for export by disabling the adjustment layer (select then press V).
-
[Steve Connor] “f you don’t want major bugs and you want stability, NEVER use a version 1.0 product of ANY software, FCPX is a complete code rewrite, what did everyone expect? It will be at least a year if not more before it reaches even a basic level of maturity.
I’m using it, knowing full well there will be issues, as it happens I think it’s surprisingly stable and usable for a first release.”
I expected bugs, just not quite as many show-stopping ones.
FCP is ” surprisingly stable and usable” until it isn’t.
I place a title, blade a compound, or add one too many markers and the UI becomes sluggish and the project unstable.
I was an iPad’s breadth away from upgrading to a new iMac until I read about people on the latest and greatest hardware having similar problems.
I don’t even mind paying to participate in a public beta program but a little more guidance from Apple would be nice.
Compare this with the release of Lightroom, when Adobe ran a free public beta, and I could listen to podcasts featuring Thomas Knoll explaining the intricacies of the exposure algorithm.
-
[Oliver Peters] “What I completely resent in all of this is that none of us has a clue as to what will of will not bloat the Events and Projects folders. Apple is completely unwilling (or so it seems) to generate any sort of best practices tutorials or documentation. They seem to want to rely on the 3rd party training resources. Those are all great at the very basic level, but inadequate for anyone who needs to do something complex with the software. This application is the most unintuitive product they’ve created in a long while if you want to do more than just slap some cuts together.”
Very well said.
I’m sick of all the half-assed testing I’ve had to do to make this software usable.