Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

ADOBE HAVE DONE IT !!!! REAL TIME R3D editing & grading on a LAPTOP!

Whether it be layers or nodes, it's about time that grading gets more neatly integrated into the editorial process. While the nuances and requirements of first rate color grading may remain a highly specialized craft, integration into the pipeline needs to move beyond the dark ages. CMX 3600 EDLs in 2012, really?

I also agree that one of the real draws of FCP was how many things you could do without leaving it. I figured out how to do 98% of what I used to do in AE right in the motion tab in FCP. Great timesaver and as others have noted, made changes much simpler. It always made sense to me that I could select any element from the timeline, click on a tab and see it's properties, then alter them as desired. The 3-way color corrector filter in FCP was limited in scope, but it sure was easy to manage...

NLE as the core app with specialty apps running "on board" as plug ins/filters/nodes sure seems like the holy grail. When you need to send a cut out for a grading session, what if the NLE project files could be sent out to Baselight, Scratch, Resolve, etc with all parameters included, then round tripped back to editorial with only the image metrics altered? Forget XML, ALE and the rest of the alphabet soup: if you want to sell a color grading solution in 2012 and beyond it needs to be able to take a project file from Adobe, AVID, Apple, etc and just work.

Cheers - #19

Thank you Blair for neatly summarizing my rant. It is a bit frustrating to wait a whole 18 months expecting your NLE of choice to really grow up. Especially when the company owns some of the most advanced technologies and has some of the industries most intelligent minds under their employ.
The basic question Adobe gurus need to ask is, what can you do in Avid, or FCP that could or should be done better in PPro. What have the AE users been searching for over the last 10 years. Are the coders just incapable of implementing real-time GPU based performance in AE as it is in Apple Motion? Why spend a whole 36 months implementing about 10 features, when the most requested feature in AE are real-time performance and node?

Adobe do you know how frustrating it is to edit a show in high speed only to see premiere pro come to a grinding halt as slow as AE as soon as you add a third party effect.
 
The max for thunderbolt displays is 2x27 on a laptop, isn't it?
 
I have a funny feeling your onto something there... but when editing in FCP.. no probe at all with the same footage...
Im sure ADOBE are going to solve this.

All i can say is, if APPLE CAN DO IT, they can...

PS. Background support from ADOBE has been amazing. I have had long phone conversations with a couple of ADOBE guys very very interested in solving problems. I'm impressed.
They couldn't fix mine.. but they will.

Hi All,

First off I haven't been responding as much recently but I am still here... Just crazy busy with the launch. Mark has done a great job working with us. He found a really interesting Quicktime bug that we now understand... He also is seeing an OpenCl problem we have been trying to narrow down. He very nicely spent an hour on the phone with me working through these issues. So thanks Mark you are helping to make premiere better :)

Cheers

Dave
 
Back
Top