Brett Sherman
7
COW Coins
Forum Replies Created
-
Cmd – Option – Up in the still image timeline to move them out of the primary into a secondary. Select the secondary timeline. Hit Command-C to copy, then paste into your main timeline. Cmd – Opt – Down in the still image timeline to move the clips back into the primary.
-
[Aindreas Gallagher] “I think the last piece of it is – they’re going to kill final cut. they’re going to say go to premiere.””
By the same token, you could say Apple is going to kill Logic Pro X, roll it into Garageband, call it Apple Music and tell people to use ProTools. Anyone that thinks that’s going to happen is living in an alternative universe. This is all baseless speculation. Nothing to see here.
-
I’ve noticed the same thing. For me they playback without dropping frames in the timeline, but the images are extremely slow to refresh when skimming (maybe 2 or 3 frames/second). GH4 footage seems to work better with i5 or i7 processors. My MacBook Pro does a much better job. I think this has something to do with built-in H.264 decoding.
-
I’m talking decoding. My MacBook Pro refreshes when skimming H.264 media 3X faster than my Mac Pro. That’s just the facts. And generally feels slightly snappier when editing.
-
[Noah Kadner] “unless you’ve got a 12-core new Mac Pro with D700s and a lot of ram. Performance is just a lot better…”
Except the H.264 decoding performance on the Mac Pro is actually pretty pathetic. Honestly, if I were buying a new computer I’d probably choose the iMac 5K over the Mac Pro. Based on my experience with a new MacBook Pro the more modern processors make editing snappier. Undoubtedly rendering is better on the Mac Pro, but I’ll take real time performance over rendering speed any day.
-
Woo hoo! I’ll be first in line. Link to sign up for notification: https://coming.colorgradingcentral.com/colorfinale/
-
There’s no reason FCP X can’t do what you are talking about. Look at this free plug-in from Alex4D to do much of what you want:
https://www.alex4d.com/10-alex4d-inside-outside-effect
The built-in color correction also let’s you set areas to color correct differently, just not blurring. For stabilizing, you can use the built-in stabilizer which is good, or Core Melts Lock ‘N Load which saves analysis time since it only calculates stabilization based on the used material in the timeline.
-
I think the feature list comparison really sort of misses the point of the differences between Premiere and FCP X. I think the real differences are the connected timeline versus tracked timeline and the different styles of media browsing.
There are those of us that find we work more efficiently in the FCP X way of working. And find it more “fun” to edit with. There are those the find they work better in the Premiere Pro way. I’m not sure there is one right answer here. A lot of it depends on the type of project you are working on.
Right now, I’m not sure there is a feature lacking in either program that would be a complete deal killer beyond personal preference.
-
[John Rofrano] “That means the 4-Core is 33% faster at single threaded tasks. So if scrubbing the timeline in CS6 is single-threaded, then a 4-Core Mac Pro will kick the butt of your 12-Core Mac Pro.”
Yes. I find my MacBook Pro snappier than my 8-core Mac Pro in skimming. This is especially true when skimming GH4 .mov footage. My MBP operates about 3X faster than the Mac Pro. My guess is something having to do with MPEG-4 processing and the Xeons is not great. Or maybe better graphic drivers on the MBP? I haven’t exactly figured it out.
-
[Oliver Peters] “Again, I disagree. I think it’s entirely personal. There might be resistance because of the “if it ain’t broke, don’t fix it” approach. But there are plenty of editors in the category you describe that have taken quite happily to FCP X. In fact, I know more older editors using X than younger editors. In fact, most of the younger editors I see have moved to Premiere.”
There is another way to understand this. It’s not so much that there is a lack of willingness or capability to learn it. An editor that has trained themselves with a certain logic in the timeline have to learn a new logic which can conflict with the old one. Some adjust faster than others, but that’s just sort of the way the brain works. I certainly had this issue when learning X. And I’d have the same issue trying to switch back to a tracked timeline, even though I had it mastered at one time.