The crop box is much improved but still doesn't interact how I'd prefer. My Adobe indoctrinated fingers want it to behave in a more familiar way, but its getting there!
|
|
The crop box is much improved but still doesn't interact how I'd prefer. My Adobe indoctrinated fingers want it to behave in a more familiar way, but its getting there!
And it will be awesome even more if this RCX can generate a LUT for another grading machine. Phew...!Go Red team...!
I think this is a great question. It really goes to the heart of how we structure out workflows. I think the short answer for right now is that since the Alchemy box is all post-debayer effects, and they are not yet in the SDK that Premiere uses, you have to render out to some RGB format and go to Premiere from there. In some ways, I'm beginning to think that it would be better if RCX could work like a plugin in an editing program, so that the editing software would not always be behind the color-science curve. If RCX could be responsible for debayering and rendering an RGB stream that it handed off to the editing program, any update to RCX would be an instant update to Premiere or Avid or whatever you were using.
As wonderful as these tools are (RCX, Premiere, Resolve, etc....) their interoperability is a challenge. I'd love it if someone at Red would publish a short "Theory of operation" on this. What does Red think is the best way to interact with other software?
For example, if I'm using RCX Pro on set, and I use Alchemy to create the look, it can't go back to the camera. So maybe it's not a good idea to open that box on set.
Another question: If Alchemy is "destructive" in the way sharpening is, you'd want it to be applied very late in the signal chain. Does that mean that if you're going to do your final grade in Resolve or Baselight or elsewhere you should stay away from Alchemy? Obviously testing is in order, but it would be great to know what the guys who wrote it are thinking about these things.
Yes, I'm asking myself the same question... Not even for Alchemy, but because RCX is a great tool, and I would like to adjuste my raw setting inside such an app, rather than the Premiere Pro Box (where I cannot zoom for exemple). But when I tryed to generate a RMD file, I didn't understand how import to it into Premiere.
Built into the NLE, I mean. Like FCP's 3-way color corrector plug-in. Or whatever comes with Premiere. As opposed to a dedicated package, like Color or Resolve.
I was thinking the same thing, but didn't want to say anything ;) Happens all the time in software development, give people too much, and they just want more! But yeah, in my dream world, I'd be able to edit R3D files directly in my NLE of choice, and have an RCX plugin that lets me non-destructively apply color corrections whenever I want in the editing process. And it would have keyframes, and masks, and give me backrubs and make me breakfast...
Per haps what I really mean is not a plugin, but something more like Adobe's Dynamic Link, where an AE sequence inside Premiere is rendered using AE's render engine, and the result handed off to Premiere for the rest of whatever you're doing with it. I don't really want a plugin, and all that implies. RCX is a great stand-alone app. But I'd like to somehow solve the problem of the SDK continually lagging behind what Red is doing in RCX.
Really basic free tutorial that I threw together for people just starting out - hoping to help make the introduction to the power of Redcode Raw very easy for the uninitiated:
http://www.youtube.com/watch?v=J9IIpFvx0uA
Very cool of you Dan, thank you
| « Previous Thread | Next Thread » |