-
RedShark News: Opinion: Which are the best NLEs right now?
-
[David Mathis] ” I have a mid 2012 Mac Pro so this could be an issue?”
I don’t think so, I see the same thing on my late 2012 iMac. It’s seems like audio is the issue, video only sequences play back fine…
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[Charlie Austin] “[David Mathis] ” I have a mid 2012 Mac Pro so this could be an issue?”
I don’t think so, I see the same thing on my late 2012 iMac. It’s seems like audio is the issue, video only sequences play back fine…”
Hopefully they can get this issue “resolved” in the next version, pardon the pun. I still like X, and have no intentions of replacing it anytime soon.
-
[Aindreas Gallagher] “no that’s actually that answer – until the market provides a competitor – ppro is the answer.”
Unfortunately, it’s not an answer for me: I have no desire to subscribe/rent/lease software, period.
If Premiere Pro were available to buy outright at a price similar to FCPX, there’s a good chance I’d buy it.
—
https://www.peterdv.com
Blog: https://herefortheweather.wordpress.com -
Just wonder if they had stayed on course with FCP Legacy where would they stand now with Adobe?
I’m sure I read here some time back that Adobe’s Mercury Playback engine was the thing that made them throw in the towel.
-
Uh oh. Must not mention experience or awards, lest the “get off my lawn!” set start yelling in righteous (ALL CAPS) indignation.
-
[Aindreas Gallagher] “gods do get bored. It’s a hallmark.
“That’s why the gods will god themselves from our learnings over the last few millennia. We will bore them no more.
Some contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
-
From my point of a view it’s a wankel rotary engine ( https://en.wikipedia.org/wiki/Wankel_engine ) in that it’s advantages when balanced against it’s disadvantages make the price of novelty a bit high for my tastes
Ah I remember the NSU RO80 “The car of the future” with a wankel engine. https://en.wikipedia.org/wiki/NSU_Ro_80Thy released it in Beta and nobody ever forgave them. Shame … it was a wonderful car. If only more people had seen its potential.
-
Peter, I have to say I’m not sure whether to laugh or cry in response to your post. Maybe both.
I do feel your pain, having once been forced to fight with the truly awful d/Vision NLE back in the day. The difference is that d/Vision never stopped being the nightmare editor it was born to be. Whereas I’ve had more fun editing on X than I’ve had in decades of the other guys. But it wasn’t a quick and easy transition.
Yes, the renaming of certain functions and concepts might seem a bit forced. Calling a project an event (sort of) and a timeline or sequence a project – really? Kinda silly, but they’re just labels. And most of the other nomenclature makes sense once you’ve made sense of the way X wants to do things. (Yes, I know it’s just software and it’s not really a living thing with motivations and personality – just go with me here.) Compound clips, storylines, libraries, etc., all follow a certain logic. Not Avid’s logic, or my friend Dean’s logic, necessarily, but X’s logic.
The hardest thing to do with X is to stop trying to make it be FCP 7 or Avid or whatever other NLE you currently know. It isn’t any of those things. When I first encountered FCP Legacy (version 1.2!), I spent a few hours trying to make it be an Avid. Then I tried to make it be a Video Cube. When I finally got tired of that nonsense, it turned out to work very well at being FCP.
Well, X is more of a change from FCP (“Legacy”) than FCP ever was different from Avid or Premiere or even the dreaded d/Vision (may it burn in the eternal flames of dead-NLE hell). Come to think of it, X has more in common with the Video Cube than any of the others (maybe Edit Box, too?). And the Avid boys (aka, many of my colleagues) hated the Cube more than they hated FCP!
Regarding the UI (and I mean this in the nicest possible way): Get over it. It is what it is. And it actually works pretty well. I use one monitor and a picture monitor. Everything fits fine. When I go back to Avid or Legacy, the virtual requirement for 2 monitors annoys me. But they are what they are, and it would be foolish to try to make them behave like X.
Regarding finder tags and color coding: so what? Why is that such a deal breaker? Real question, not snark. I do my tagging and organizing in the NLE. And I can tag and color code all I want in finder, then drag directly into X to import if seeing the files in finder is important for some reason.
Timeline editing – which is to say, “track-based timeline editing” in the style of PPro, Legacy, Avid, Edius, EMC and other NLEs (as well as Pro Tools and the late, lamented Avid Audiovision) dating back to the 90s: you’re right. It wasn’t broken. But neither was/is it holy writ. It’s one way of working. But it’s not the only way of working, and X makes a valid argument that it’s not necessarily the best way of working. Quantel certainly didn’t think so, since they made the Edit Box (killed more by high price and poor marketing that by any lack of capability or suitability to its task). Yes, it’s a Pro Tools world in audio these days, much to the chagrin of anyone who loved the Fairlight system (cf. Michael Gissing and others on the Cow). Tracks don’t scare me, and I work with them all the time. But decades of “track Tetris” surely does make me appreciate not having to worry about it in X. And X2Pro gets the audio into the world of tracks (Pro Tools, et al) pretty simply.
As someone who has to “review, scope, slice, dice, process, demo” (and so forth) 4k and raw footage, I should think you’d be happy as the proverbial clam at high tide with X. It’s made for all that right out of the box. The proxy workflow for R3D and the like is built right in. Scopes, broadcast out, basic color correction, high-end effects (either built in or from plugins, the vast majority of which are less than 50 bucks) – what’s the problem? PPro seems to handle it all just fine, too. Avid still makes you wish you were dead with anything above HD video transcoded to their DnX codec, but they’re getting there.
Regarding hardware: any current NLE needs current hardware. Period. Especially for 4k and raw footage. Not sure why this is a perceived problem with X. Or am I misunderstanding? And $300 is pretty cheap for an NLE. Cheaper than the other guys by quite a margin. And, as you point out, no subscription. Again, what’s not to like?
In the end, being pissed off about what something is called or not being able to move/resize a window “just so” to one’s liking seems counter-productive. Trying to make one piece of software act like another is a recipe for frustration and wasted time. Been there, done that. And, frankly, anyone who is smart enough to learn one NLE (e.g., you and me and anyone else on this forum) is smart enough to learn another NLE. All the rest is just chit chat, some fun gossip and theorizing about corporate motivations, and often a bit of silly posturing and politics.
I’m happy to cut professional broadcast product on Avid or FCP Legacy. Less happy to do so on PPro, but whatever. But downright tickled to death to cut it on X. Seriously. It really is that much more enjoyable. For me. And for many others. Possibly for you, too, at some point in the future.
End of counter rant. We now return to our regularly scheduled Bill Davis bash session. (Yup…Loves me some Bill Davis…I really do.)
-
[James Ewart] “I’m sure I read here some time back that Adobe’s Mercury Playback engine was the thing that made them throw in the towel.”
That’s flattering for Adobe to be sure, but I would imagine (officially my guess only) that the effort to move the existing code base to 64-bit cocoa was a bigger effort than just starting over. They were likely bit by their own decision to drop ‘carbon’ – the effort to allow existing 32-bit apps to move over to 64-bit.
-
[David Mathis] “I would love to use Resolve for editing as well but choppy playback is a negative. In other words playback is not in realtime. “
Agreed. I have R11 on a new (mid 2014), totally tricked out MacPro and the playback is terrible. The company said it was I was trying to playback AVCHD which, of course, FCPX plays back like a champ. So I took a clip of R11’s own color bars, made a new timeline. Wouldn’t even play that back smoothly. Ouch.
I want to do any more intense CC and some finish tweaks on Resolve (after the cut in X), but the playback kills it for me. The software is sitting there gathering “digital dust” right now.
Scott Witthaus
Senior Editor/Post Production Supervisor
1708 Inc./Editorial
Professor, VCU Brandcenter
Reply to this Discussion! Login or Sign Up