If anyone has any advice regarding these I'd be highly interested to hear what you might have to say. I get the sense a lot of fellow editors feel the same way.Įdit: also, I believe it may have to do with codecs and preview formats. So long as I require the uber convenience of the Adobe workflow and the unbeatable value of the Creative Suite (along with the mountain of templates that speed everything up), I can't do that, but in 1-2 years we might re-evaluate. The long term solution will be to quit Premiere, bc imho the ideal Adobe customer is a high-grade dilettante and agency-wide ease of access but no single paying freelance professional. And it's always premiere causing shit, not After Effects or Illustrator. ) and like, that's my financial security, man. This keeps messing with a ton of my projects (I'm trying to adjust by using less MOGRTs and render/exporting in AE rather than interlinking, but. Often the timecode of my error isn't even within the in/out points of what I told Premiere to render, so this is some utter fuckery that I really need some insight on. The solution to my issues is nowhere to be found. If there are any intel guys in here would you be able to shed some insight into how your software has been function as of late (last 6 months). My suspicion is that this has to to with some flaw between Adobe software and AMD CPUs, and the adobe line famously does not have support for multi threading. Sometimes it just flat out refuses to work. Switching to software encoding appears to make it better, or better yet, the black magic route of quitting Pr, reopening, exporting, ad nauseum until it actually farts out the export. I consistently come up with some form of acceleration or effect render error. I posted in here a few days ago about these errors but got limited replies.
0 kommentar(er)
