Shane Ross
Forum Replies Created
-
Sorry, but there really is no clear path from Adobe to Avid back to Adobe. It’s one that pretty much requires Resolve to do conversions, and even then it’s problematic.
Your workflow plan isn’t one that I’d want to embark on. The issues of getting it to work outweigh any benefit you might get. Bit confused when you say Premiere to online…then to Avid to offline…back to Premiere to Finish. In my world, Online and Finish are the same thing.
Why are you going to Avid at all? You can offline/online in Premiere Pro…
Shane
Little Frog Post
Read my blog, Little Frog in High Def -
1. No. It’s a color correction tool with editing capabilities at the moment. Sure, pretty much EVERYONE uses it for various purposes, from grading, to creating dailies to transitioning projects from other NLEs. But it isn’t quite mature enough as a NLE to compete with PPro or Avid. Not at this time. It’s trying to do TOO much…”Look, we grade! And now Edit! And now Mix! And now VFX!”
2. No. It’s used in 90%+ of TV shows and feature films…and does MANY things better (shared media/project workflows) than the competition. And there is a very robust ecosystem built around it that’s pretty entrenced. Plus it works great. it won’t go away until it doesn’t work great, or something does the core things avid does, better, and fits into the ecosystem.
3. use it if you want to work in Hollywood/New York/Atlanta…wherever TV shows are made. Use it if the tools it offers work best for the given editing situation you might find yourself in. I use it even on non-TV stuff for the organizational tools it offers. But I also use PPro. it still can’t open more than one sequence at a time, but most people who use it don’t need that, or will load one sequence into the PREVIEW monitor. Many ways to skin a cat. But hey, if you are seeing more jobs asking for PPro experience in the areas you are applying for…then use that.
Shane
Little Frog Post
Read my blog, Little Frog in High Def -
So, you just cut on your laptop? You don’t transcode any of the footage first? Don’t let FCP-X “optimize” it for you first? It’s that optimization that utilizes the processor. Final exports? They will be faster with an unthrottled i9…having a faster processor means it gets done sooner, and you then edit faster, and get the edit done sooner and….that’s your whole point of liking FCP-X…that it makes you faster.
It’s not only for CAD or 3D or graphics…or DITs. It’s for you, the editor. Importing, exporting…transcoding, rendering complex layers, doing graphics with Motion, rendering out something from After Effects…doing a final render in Resolve. ALL tasks editors do.
Shane
Little Frog Post
Read my blog, Little Frog in High Def -
[Bill Davis] ““In my opinion, Apple seriously screwed up here. The testing that I did was easily within Apple’s capabilities, and it is highly irresponsible of them to ship these machines out this way. …”
THATS the type of Ready- Fire – Aim, stuff I’ve been talking about.”
AH! GOTCHA! OK…and yeah, that guy who packed it up and shipped it back immediately, and a fix came an hour later…that is a bit too much. OK, I’m picking up what you’re putting down.
[Bill Davis] “By the way, that was posted under a “handle” as are most web musings these days.”
Yeah, I hate it when people do that. Protecting their reputations behind a mask. I’m all about putting it out there and backing up what I say.
Shane
Little Frog Post
Read my blog, Little Frog in High Def -
[Bill Davis] “But of course, this was NOT every user, and certainly not under EVERY load case, nor a problem making the overall computer unsuitable for most common tasks.”
Most common tasks aren’t ones that would require the i9 processor. That is for those who need the render power…video editors, 3D modeling, graphics. THEY are the ones springing for this processor, they are the ones who need this speed. I don’t see a writer, or student, or guy who writes computer code, game designer…shelling out extra bucks for the i9. They aren’t the ones who need that. The people who do, shell out the extra money specifically for it to render better than the i7…which it wasn’t. Not until the fix came about.
[Bill Davis] “That it was a problem affecting a very small class of users doesn’t make it right, of course.”
This “small class” of users is video professionals. You know…like the ones who use FCP-X. The ones you always say are a HUGE market for Apple. So first you tout them as this mass market..now you are saying they are a small class of users. Well, honestly, they are. Which is why Apple isn’t catering to them…not making the MacPro…sticking to computers that didn’t have tons of processing power because they make MORE money on the iphones. But now they are trying, only sorta. They are still trying to stick to their sleek designs that don’t cool things properly, because design is more important that function. They used to have a good balance between the two…but now they find the consumers more profitable so they go for the sleek…
Shane
Little Frog Post
Read my blog, Little Frog in High Def -
[Bill Davis] “NO. That is NOT why throttling was occurring, as I understand it from my reading.
There wasn’t a “flaw in the processor” at all. It was an unsigned snippet of code in a Power Management Unit totally separate from the processor. “
Sorry, I typed that wrong. Not a processor flaw, but computer code designed to throttle it so it wouldn’t get too hot.
[Bill Davis] “As I understand it, the computer was NEVER overheating and running the fans to cool down an actually overheating issue. “
Correct, because if it went to a certain temp, the code would “throttle” the processor, making it not function as fast as it could, in order to keep the heat down. Notice that when the computer was put in the freezer, that the processor throttling was less. because it didn’t heat things up as much. so it was allowed to do more. But make no mistake, code was there to throttle it…intentionally.
Shane
Little Frog Post
Read my blog, Little Frog in High Def -
I mean…back at the start of the digital filming revolution, I was working with P2 footage and encountered an import issue…and blogged about it. Apple then contacted me directly and offered to work with me to find the solution, which I did the following day. Two days later an update to FCP was released. Not meaning to toot my own horn here, but it is another example of this “squeaky wheel gets the grease.” In this case it wasn’t a design flaw, or intentional slowdown…but an actual small bug when it came to dealing with footage shot with a specific setting.
Shane
Little Frog Post
Read my blog, Little Frog in High Def -
[Bill Davis] “What matters most is being first. First to uncover the flaw. First to stake out the ground for your position.”
First? This isn’t a cable news story where reporters and anchors RUSH to get the news story on the air and get facts wrong…or report issues that are in flux and constantly changing. No…I guy found a flaw in the processor, it was being throttled. Several others found the same issue…Apple acknowledged the issue, and a fix was released. There’s no “fake news” here…no wrong facts due to reporting this issue quickly. An issue was found, but someone who pushes hardware to the limits every day, it was acknowledged…and fixed. True nature of why all this was happening came to light, and it wasn’t wrong. The design of the MBP isn’t optimal for the cooling needs of the processor. The push for THIN and SLEEK isn’t ideal for high end needs…needs even FCPX would have.
So I fail to see what your point is. Are you somehow not liking that a flaw in an Apple product was brought to light by at least three bloggers/vloggers? That Apple admitted wrong doing…and a fix was issued?
Shane
Little Frog Post
Read my blog, Little Frog in High Def -
You want to use the FF and RW options…they are the double triangles that point left and right in the PROGRAM monitor toolset. In Avid 2018.x, they renamed that (and changed the icon) to GO TO NEXT EVENT
Shane
Little Frog Post
Read my blog, Little Frog in High Def -
Cutting those formats native…will require a LOT of oomph…as they are highly compressed formats. So you’ll need a top of the line iMac, with the best GPU you can get, or get an eGPU to help with the load. The one you list will be decent. And I hope this is a short form project, the longer the project, especially with complex media…the more it bogs the system down.
Or get the best iMacPro you can afford. Avoid the MacPro tubes…they are 5 years old, outdated, and less powerful than the iMac.
I would suggest using the PROXY workflow with Premiere…so you can cut with easier to deal with media, and relink to the masters with the click of one button. You can have it make proxies overnight while you are asleep.
Shane
Little Frog Post
Read my blog, Little Frog in High Def