[Jacob Fenn]

You still selling the MC Color?

Thanks.

[Jacob Fenn]

Paul,

Just wanted an update on your situation. Did you end up attempting Resolve with the Avid Artist Control panel?

I would assume the keyboard mapping software provided lets you control anything in Resolve that is mappable to a keyboard shortcut, but beyond that you have no further control. Would that be about the jist of it? Would you recommend any advantages in combining the two? If I could map rotary encoders to control lift/gamma/gain RGB values Etch-a-Sketch style I’d save desk space and use the Control and mouse/keyboard combo. Feel like I end up heading back to the mouse for a lot anyway. Maybe I’m just not as efficient as others with panels.

Another frustrating thing is how well the Artist Control panel interfaces with Final Cut Pro, but Adobe has left Premiere lacking in utilizing it. Audition supports EuCon from the looks of things.

Let us know if you have an update or if you really did hold out to NAB in which case you’ve likely gone the Element route 🙂

[Jacob Fenn]

Don, just curious if you resolved your issue with the 5770 and 285 running simultaneously. I’m also going to be running the 285 for its CUDA capabilities, but using the 5770 to drive the GUI in Resolve and for better system performance in other areas so just wanted to check in. Did your issue end up being system related or was it specific to C4D not recognizing the card?

[Jacob Fenn]

Would this work to prevent Resolve from re-linking new media w/ identical timecode over top of old?

Import your new media (the identical timecode stuff that Resolve automatically inserts for you) to a new subfolder named ‘v2’ or whatever you like. Verify that the clip has updated in your timeline to replace new media in place of old. Now right-click in timeline and ‘Reconform from folders’ DESELECTING ‘v2’. Confirm that your ‘old media’ is back in place with its original grade.

Not super-convenient, but seems workable.

[Jacob Fenn]

I have found a solution–far from ideal, but workable should anyone stumble upon this thread. From all I can tell, Resolve will not interpret the RED settings differently for two instances of the same clip imported with an EDL/XML. The basic solution is to import the clip from the browser as seperated clips–already divided into those you specifically will need to change independent of one another.

I specifically needed a V2 track with lower ISO settings for highlight protection so I made a folder called RED Dark and added all my RED media and interpreted it at a low ISO. You could use “Split and add” here if you require clip specific adjustments rather than just darkening everything. Then I loaded my normal XML into a timeline twice, the second time conforming to my “dark” folder in the media pool and pasted this on V2 in the neutrally exposed version. An alpha output on V2 let me get my highlights back on the clips where I needed it.

I still hope I’m missing something, but if not, hope this helps someone else…

[Jacob Fenn]

You are a wise man. So that did eliminate the border, but it almost looks like it’s mirroring pixels or something. See the bordering in the attached image?

The pictures show the FCP 150% scale on a corner of the image in the canvas at 400% and the Resolve scale and render with no grade applied. Resolves scale does appear superior (or at least sharper) as claimed, but what is this bordering the result of?

[Jacob Fenn]

Now, after the accolades…

I still see a very small black band of several pixels around my image scaled in Resolve. This band appeared in FCP after round-tripping and having FCP scale 720p material 150% on previous versions of Resolve. In 8.1, when “use sizing info from XML'” is checked from the COLOR thumbnail, the rendered file persists with this black border of several pixels. Again, this is 720p material scaled up to 1080p in Resolve and rendered out with the sizing info from the XML applied.

Any advice?

Thanks again!

[Jacob Fenn]

A formal note of gratitude to our busy friends at Black Magic:

Thank you very much for implementing an impressive list of features we’ve been specifically requesting and for responding so quickly! I’m very excited about the future of Resolve if the appropriateness and efficiency of its updates continues this trend.

I recently downloaded the 8.1 upgrade and am already benefiting from more than one of the improvements.

Thank you!

[Jacob Fenn]

Well, thank you both for the responses. I feared that may be the case. It wasn’t too much hassle to bake it all into one export and preconform to an EDL in Resolve.

Thanks again.