Chris Frantz
Forum Replies Created
-
I’m not sure why you would have a single bin with 100’s of SFX not organized any more than that, that seems like a FCPX problem where there’s only a few layers of organization. Events, folders, keyword collections. 😉
-
Yep, premiere now does let you publish to those sources via media encoder (which is easy to do with a batch export, wink wink).
The motion template is cool, but the only time I’ve ever used the custom one is to create a batch lower thirds or slate. You can use ae projects and publish them with text you can manipulate in Premiere. Most other effects are just workarounds for things you can do natively in Premiere (adjustment layers anyone?).
Premiere has a pretty fantastic media browser as well, I might even say a better one as you can have multiple open and explore all kinds of different media types. -
Just chiming in here, FCPX lags embarrassingly slow on brand new hardware, with fiber attached storage nonetheless. Didn’t use to be nearly this bad, I can move more quickly in FCP7 then 10 at this point. It is kind of strange watching Apple take such a beating from Adobe on this stuff. I can’t think of any other division in their company they’re getting so thoroughly owned in.
-
This is an easy one for me. Being able to turn off waveforms, way faster waveform handling, extending multiple clips at once, disabling video only without a workaround, multiple workspaces, syncing settings across multiple stations in one click, proper integration with a DAW, compositer, logging tool, etc. also assignable colors, multiple tabs, the superior media explorer, full screening any window, way better A/V support, Avid keyboard shortcut defaults, customer support, curves, rapid updates, track mixer, setting master eq’s, scrolling timeline, the list goes on and on. I still like FCPX, but premiere is pretty clearly the stand-out winner (currently). I expect the Yosemite update will even the playing ground again however.
-
I never called it stupid. It’s fine software for some use cases, just not for long form. It’s just software buddy, no need to get personally offended on its behalf. And, once again, FCP7 could handle it no problem albeit without subframe accuracy and premiere pro can handle it with subframe accuracy in just a few seconds. It’s a bug, Apple has acknowledged it. It crashes when I import broadcast ready files and try to work with them others have said similar. If you don’t have a solution, that’s ok, hopefully it will be fixed in the next release. Enjoy your weekend, relax it’s just software.
-
I realize you’re a staunch defender of this software, but please realize I and others (even in this very thread) have said this is indeed a problem. I don’t think it’s from looking too closely at the problem, more like it’s unable to do the work that other NLE’s can do, including it’s older counterpart. This isn’t a matter of sequence settings, or problems with QC’d source material. Encode a 50 min prores 422(HQ) file, embed 8 channels of audio, then drop it in a timeline of your choice and whatever settings you want. Tell me it doesn’t beachball or take 10-20 minutes to draw the waveforms. If one works, two or three certainly will not. Work can’t be done with these types of files, which make up a ton of long form stuff. It makes sense then that this isn’t well documented, as there’s not very much long form stuff cut on FCPX, quite possibly for reasons such as this. I’ve talked to Apple, they’ve acknowledged the issue now. Test it out and you may as well.
-
Wait you’re kiddibg, you’re waiting overnight to start working because of waveform rendering? How do you bill your client for that wasted day? I can take these same files into FCP7 and Premiere, with the same sequence settings and they work fine. I’m able to get to work right away. I’m not the only one with this issue. For the record, premiere also can do sub frame audio editing and can also import plenty of different types of footage. Again, FCP7 handles these prores files delivered for broadcast just fine.
-
All audio analysis is off in the preferences. The odd thing is that it seems to draw for a few seconds, then hang, then when you force quit the beachball, it will come back with a few of the waveforms partially drawn. Then you zoom in one step, and they disappear entirely, even you zoom back out another step. On top of all that, FCPX by default will draw waveforms in the inspector, event browser, and the timeline. These seem to be independent of each other. And because of the way it displays audio, it draws a mix down of however many audio channels to display as the general audio track. On top of all of that, the only place you can zoom in and interact with the waveforms is in the timeline.
So it’s doing all of the extra lifting for nothing and still not letting us use the program without letting it digest a 52 minute file for 15 or 20 minutes. How is this not the biggest problem with FCPX? IMO it contributes to massive program lag, cache bloat, and general system performance. Apple are you there?
-
I have reported it to them in different ways a few times and haven’t heard anything back. I don’t expect to either without an enterprise contract. This is a crippling bug that knocks this NLE out of the running for any long-form TV.
-
They are stored locally. All leave in place media.