Shawn Miller
1
COW Coin
Forum Replies Created
-
[Simon Ubsdell] “But am I really the only person who is a bit stunned that the technology was put before the talent in this case?”
Nope, I don’t think it’s just you. 🙂
Shawn
-
[Bill Davis] “[Shawn Miller] “The Mercury Playback Engine, Warp Stabilizer, support for native file formats (which many FCP editor were against, before FCP had it), masking and tracking, and adjustment layers to name a few. You can decide for yourself if Premiere Pro 2014 can do things that other NLE’s didn’t do a decade ago.”
The Mercury Engine is NOT about Premier. It’s underlying technology.”
Underlying technology of…
I know your original question was about the “editing engine”, but if MPE isn’t about editorial, what is it about? Also, weren’t your questions about the state of Pr 2014 vs Pr 1.5?
[Bill Davis] ” I don’t fully understand the Warp Stabilizer, but if it’s primarily about removing camera shake then X has it’s own version which may or may not be similar.”
Bill, you asked what exists in the Premiere Pro editorial engine that didn’t exist in other NLEs 10 years ago, and what made Premiere Pro 2014 as superior to Premiere Pro 1.5 as FCPX is to FCP Classic… you didn’t say anything about comparing FCPX to Premiere Pro 2014.
[Bill Davis] “My essential point is that none of what you list is UNIQUE to Premier.”
I didn’t say any of those features are unique to Premiere Pro TODAY. I was comparing Premiere Pro 2014 to Premiere Pro 1.5… in response to you original statement and question:
[Bill Davis] “I’d be interested in a list some of what the editorial engine in Premier does today that other NLEs didn’t do 10 or even 5 years back?“
[Bill Davis] “…are there areas where today’s Premier outshines yesterday’s Premier in the same fashion that range tagging, and multi-res background rendering, magnetism and roles have made X a far superior and faster editorial assembly system when compared to FCP Legacy?“
Premiere Pro 2014 is a COMPLETELY different animal from Premiere Pro 1.5; from the Mercury Playback Engine, to masking and tracking, to native file handling, to a host features that would have seemed like magic to any NLE in 2005. And yes, these features make editing in Premiere Pro 2014 a LOT faster than editing in Premiere Pro 1.5.
Shawn
-
[Bill Davis] “Personally, since I don’t edit in Premier,I’d be interested in a list some of what the editorial engine in Premier does today that other NLEs didn’t do 10 or even 5 years back?”
The Mercury Playback Engine, Warp Stabilizer, support for native file formats (which many FCP editor were against, before FCP had it), masking and tracking, and adjustment layers to name a few. You can decide for yourself if Premiere Pro 2014 can do things that other NLE’s didn’t do a decade ago.
https://en.wikipedia.org/wiki/Adobe_Premiere_Pro
Shawn
-
[Jeremy Garchow] “Premiere just added this capability not long ago, and that software is much more mature than X.”
Do you mean the ability to output sequences with trimmed media via the media manager? I think that’s been around since Premiere Pro 1.0… or maybe 1.5… it was a while ago.
Shawn
-
[Walter Soyka] “I keep trying to pass this off as Soyka’s Law: “Expectations rise at the same rate as capabilities.””
lol – I might argue that expectations seem to rise slightly faster than capabilities. I call this the “Can’t you just” request. 🙂
Shawn
-
Wow, that is just depressing.
Shawn
-
[Michael Gissing] “Thanks to our government the internet in Australia rates lower than Mongolia.”
Dang… way off topic here, but how did that happen? No investment in infrastructure… no competition… ?
Shawn
-
[David Mathis] ” I remember in AE you could save an expression into a program like Text Edit and anytime you needed it just simply a matter of pasting it back over. Really useful for those long expressions.”
Yes, absolutely. You can also save expressions in an animation preset – very useful.
https://helpx.adobe.com/after-effects/using/expression-basics.html#save_and_reuse_expressions
Shawn
-
[David Mathis] “Just attempted to bring in BMCC raw footage with the result of it being brought in as an image sequence, playback was a bit choppy. Frames were skipped, don’t think they were dropped. So it looks like transcoding is necessary.”
Ah, good to know. The upside is that you may not need RT playback for certain things, like keying. Better to at least have the option. 🙂
Shawn
-
Ah, I see. I was curious to know if you could work with a raw format inside Motion. I have a similar workflow to yours with Resolve>XML>Premiere/Ae>XML> Resolve. Although, sometimes it’s Cineform>Premiere/Ae, or just straight to AE… depending on what it is, and how fast I need to get it out.
Shawn