Activity › Forums › Creative Community Conversations › I wish FCPX adopted these Premiere Pro features
-
I wish FCPX adopted these Premiere Pro features
Jeff Markgraf replied 10 years, 7 months ago 28 Members · 151 Replies
-
David Mathis
September 6, 2015 at 12:38 amOliver you overlooked one minor detail:
21. Rental only. 😉
-
Oliver Peters
September 6, 2015 at 12:43 am[David Mathis] “21. Rental only. ;-)”
LOL. Everyone’s a comedian 😉
Just to be clear. I’m not arguing that one is better than the other. I certainly have my own issues with Premiere Pro. These are simply things that would be beneficial to make a good application even better.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
David Powell
September 6, 2015 at 4:44 amWhat am I doing wrong? I have a nearly identical setup 24 gigs of ram and Premiere 2015 crashes every 5 minutes. It’s horrible. Any time I ff on the source side it crashes using prores proxy! I guess I’ll post in the PP forums but UI response and stability has been a nightmare! I agree with all the feature requests though and would add
* Duplicate Frames Detection
*Roll Previous/Next Edit To Playhead -
Gabe Strong
September 6, 2015 at 5:35 amThat’s a pretty good list, I had about 7 or 8 of those on ‘my list’ as well.
The only one that you don’t have that I personally would like to see,
is the ability to attach secondary storylines to other secondary storylines
instead of being forced to connect every secondary storyline to the primary
storyline.Gabe Strong
G-Force Productions
http://www.gforcevideo.com -
Jeff Markgraf
September 6, 2015 at 5:56 amInteresting list. Concur with 5, 12, 17 & 18 in particular.
Really don’t care much about the UI things. Interestingly (well, interesting to me, at least 😉 ), I find that these days I end up customizing my Avid interface to be more like the 1 screen layout of X. Go figure.
I guess because I don’t usually do graphics heavy editing (I have graphics people who do the graphics), I don’t see such a need for a send-to-motion, though a tight X-Motion-Logic integration might be nice.
What I really don’t get, though, is the frequent call for flattening a multi-cam. Why? What is gained? Is it a performance thing for older hardware? Genuinely puzzled.
-
Ken Pugh
September 6, 2015 at 2:44 pmWhat I really don’t get, though, is the frequent call for flattening a multi-cam. Why? What is gained? Is it a performance thing for older hardware? Genuinely puzzled.
One reason might be to enable the export of a simplified EDL or XML. Or to facilitate round-tripping… it’s a handy feature.
Best, Ken.
-
Andrew Kimery
September 6, 2015 at 3:22 pm[Ken Pugh] “One reason might be to enable the export of a simplified EDL or XML. Or to facilitate round-tripping… it’s a handy feature.”
Yeah, if you are sending it out for grading you don’t want to waste time sending a bunch of camera angles that are never used. Also, if you want to make an archive of the final project you either need a way to flatten it or to tell the program to only copy the media from the active camera angles.
-
Herb Sevush
September 6, 2015 at 3:27 pm[Bill Davis] “On my laptop my timeline performance is currently wicked fast. Not because I’m a fanboy, David. Exactly the opposite. I’m a fanboy BECAUSE my X system is running that well.“
Except for the fact that you’ve loved X even when it wasn’t running so well. You’ve loved it since the first day you saw it, you’ve loved it with or without multicam, without export options, lagging UI or no. You have loved it in each one of it’s revisions, even while more fickle admirers were pulling out their hair. It is lovely to see such consistency as yours, Romeo has nothing on you.
Herb Sevush
Zebra Productions
—————————
nothin’ attached to nothin’
“Deciding the spine is the process of editing” F. Bieberkopf -
Oliver Peters
September 6, 2015 at 4:05 pm[Jeff Markgraf] “What I really don’t get, though, is the frequent call for flattening a multi-cam. Why? What is gained? Is it a performance thing for older hardware? Genuinely puzzled.”
Part of it is performance (old and new hardware), part of it is for clean lists to the outside, and part is just plain anal retentiveness. I follow the “you will be judged by your timeline” mantra and prefer to have a cleaned up, finalized timeline when I’m done. Get rid of the unnecessary angles in the finished timeline. From a standpoint of consistent UI design, if you can finalize an Audition clip, you should also be able to finalize a multicam clip.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
David Roth weiss
September 6, 2015 at 4:19 pm[Herb Sevush] ”
Except for the fact that you’ve loved X even when it wasn’t running so well. You’ve loved it since the first day you saw it, you’ve loved it with or without multicam, without export options, lagging UI or no. You have loved it in each one of it’s revisions, even while more fickle admirers were pulling out their hair. It is lovely to see such consistency as yours, Romeo has nothing on you.”And then there’s the whole thing about comparing the performance of his beloved Julliet to that of Adobe Premiere, which he has, by his own admission, never used. By his own rules, isn’t that THE most egregious violation of the rules of debate here?
David Roth Weiss
Director/Editor/Colorist & Workflow Consultant
David Weiss Productions
Los AngelesDavid is a Creative COW contributing editor and a forum host of the Apple Final Cut Pro forum.
Reply to this Discussion! Login or Sign Up