-
Serious X Editing for Speed
-
[Oliver Peters] “Nope. Doesn’t work at all and in fact that function seems to be broken. “
Weird. Works here.
Plus-One-Zero-Period-period-Enter which translates to plus 10 minutes.
The HUD turns blue and once you hit the periods it adds the zeros to frames and seconds.
Adding Control-p before that moves just the play head the entered amount (plus or minus) or to an exact sequence tc without the plus or minus.
I’m working on a 30 min show and use this function a lot along with the TL index.
I find editing longer form to be really easy in X, but as we all know, I’m a weirdo.
-
[Oliver Peters]”That’s not universally true”
I agree but my observations have been that it is generally true. Speed differences have so many components but in order of importance we rarely acknowledge that the operator can be the problem or the hardware rather than assuming the software is the most important.
I still stand by the idea that dedicated controllers and skilled operators are the greater contributors to the ability to work fast, comfortably and get a creative result in the minimum time.
-
[Jeremy Garchow] “Plus-One-Zero-Period-period-Enter which translates to plus 10 minutes.
The HUD turns blue and once you hit the periods it adds the zeros to frames and seconds. “Yep, that’s exactly what I’m doing, but I don’t get the same results. It is a 25fps project and migrated from FCP7, though, so let me retest with a different frame rate and a fresh project.
[Jeremy Garchow] “I find editing longer form to be really easy in X, but as we all know, I’m a weirdo.”
I like editing long-form in X as well, but definitely NOT because of the mag TL. 😉 OTOH, I find long-form performance with X on a MP tower (as opposed to MBP or nMP) to be very tedious at anything other than ProRes Proxy. With mixed formats and older machines, I find Premiere/FCP7/MC to be waaaaaaay more responsive.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Oliver Peters] “so let me retest with a different frame rate and a fresh project.”
Yep, doesn’t work magnetically at all for me. Does work in position mode, but that’s an overwrite, of course.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Oliver Peters] “I find Premiere/FCP7/MC to be waaaaaaay more responsive.”
I find the magnetic timeline to be of great help, but you do have to work it and yes, sometimes that involves modifying connection points, and even anticipating the modification of those points.
UI speed has never been a selling point of X, but I’m willing to deal with a bit of slowness in exchange for overall workflow gains.
-
[Jeremy Garchow] “UI speed has never been a selling point of X”
Edit with X … it feels so good when you stop. 😉
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Oliver Peters] “With mixed formats and older machines, I find Premiere/FCP7/MC to be waaaaaaay more responsive.”
I am currently testing 4k H264 on Premiere CC and FCP X on a variety of machines. In general FCP X is much more responsive, although it depends how you define that.
Premiere JKL response to user input in a 4k H264 timeline is very sluggish, even on a top-spec 2015 iMac. It’s likewise on a 4Ghz Windows machine, so it’s not the OS. Also the program monitor update rate in fast forward or reverse is very laggy, often several seconds. By contrast JKL response on FCP using identical media and hardware is much faster — by about 10x.
OTOH in Premiere when the playhead starts moving at any FF speed, it moves very consistently and smoothly. They are apparently running that on a separate high-priority thread. Even though the program monitor lags severely, the playhead keeps moving. By contrast FCP X on the same material has a jerky playhead, but the lags are much smaller — 1/2 sec or less vs up to 4-5 sec for Premiere — and the viewer stays in sync with the playhead. That is with Premiere on 1/4 res and FCP X viewer on “performance”. I personally prefer a higher viewer update rate than a smoothly-moving playhead.
In Premiere if you give up on JKL and just drag the playhead it’s somewhat better. The playhead response is very smooth and lag-free and you can hear the audio. However program monitor update is sluggish, with up to 1 sec delays. In FCP X dragging the skimmer across the timeline has much faster updates on the viewer — about 10Hz or 10x faster than Premiere.
Multicam H264 4k is similar but with magnified effects. In general it’s borderline unusable on Premiere and sluggish but usable on FCP X. That is with both on a 4Ghz i7 Skylake CPU with 32GB RAM and 1TB SSD. With FCP there is built-in seamless proxy mode, so it’s easy to just use that, which makes editing 4k lightning fast. With Premiere you’d have to manually transcode before import, copy around files by hand and deal with re-sync issues.
However the general UI responsiveness of Premiere is very good. E.g, I don’t recollect it lagging severely when dragging an effect to the timeline. FCP X can get in states (apparently when running a compute-intensive plugin) where the UI itself becomes quite choppy when dragging an effect to the timeline. It’s as if the UI thread is not decoupled from the background processing, like in the old days of cooperative multitasking.
-
-
[Jeremy Garchow] ” I’m willing to deal with a bit of slowness in exchange for overall workflow gains”
I know. I don’t even acknowledge the UI “slowness” because I know overall I am working faster. And have more creative tools easily at hand. Then again, Pr CC2015 has come a long way for the better since CS6.
Maybe we should ask Murch? 😉
While we are on the topic of speed, I posted this on the Premiere Basics forum with no responses. Maybe someone here would know:
“Please note I don’t use Premiere very often, only when required to, so I am no expert.
I have a late 2013 MacPro, 3.5 ghz 6-core Xeon E5, 32 gig ram, AMD FirePro g-card
A while back, I commented on a weird visual “echo” I was seeing when using PrP CS6. Basically if I scrub around in the source viewer and let go, the playhead mimics my movements before settling to the spot I am currently parked. Same thing happens in program viewer. If I scrub in the timeline however, that acts normal, but I get the “visual echo” in the program monitor. Very odd.
Some folks advised me to upgrade to CC as that might solve the issue, and it hasn’t. Is this a computer setup issue? A bug? Feature? Not a show-stopper but rather annoying.”
Scott Witthaus
Senior Editor/Post Production Supervisor
1708 Inc./Editorial
Professor, VCU Brandcenter -
[Scott Witthaus] “Then again, Pr CC2015 has come a long way for the better since CS6.”
No question about it, Pr certainly has come a very long way in a relatively short time.
But the fundamentals still remain in Pr. I hop in and out of it (I have to use it for a finishing/translation conduit sometimes) but for most editing, I try and stick with FCPX. I really love how you can very easily “section” off areas of the timeline and move them freely without harming other sections of the timeline. Much more care needs to be taken in track based programs because the track is the governor, at least that’s they way I interact with it. My timeline usually falls in to more vertical sections, with loose horizontal boundaries (different chapters/scenes). Rarely do I need a horizontal line drawn through every clip.
Unfortunately, I can’t help you with your Pr CS6 issue, apologies.
Reply to this Discussion! Login or Sign Up