[Drew Lahat]

Using nodes means not using versions… which goes against the concept of using versions 🙂

I guess the best solution is to create a 3rd version, make it include the nodes from both versions (using Gallery->Append To Node Graph or a lot of Add Node + copy-paste), and then restructure the node tree in a way that’d facilitate blending with a parallel or layer node. Not exactly quick.

I don’t think the issue I raised relates much to Sascha’s issue, but the solution for both cases is to expand the scope of nodes beyond a single version. Also consider this scenario: let’s say you have a grade on 85 light-saber shots. The shots and grades are different, but the light saber components are the same. Then production wants to change the color of the light saber in the movie…

[Drew Lahat]

I would stick to two basic principles: get the primaries right first, and rely on the scopes.

Scrub through the footage and pick a reference point to match everything to. Probably either the beginning or the middle. Try correcting 3 select shots from the beginning, middle, and end of the interview until you find an acceptable medium of color temperature, gamma, noise levels etc.

A good workflow for grading is always to get the shadow right (base exposure level), then the highlights (gain), then the mids (gamma) – then color tone, and only then proceed to secondaries. Abiding by this workflow helps maintain consistency when matching multiple shots.

To help match and judge, ‘read’ the scene using the appropriate scopes and replicate where things fall.

That should get you 90% there, 98% if you’re lucky 😉

[Drew Lahat]

I believe the OP asked about personal training, not web. Also, the fxphd class is $200.

I think this is a valid question, I was also looking for personal training but gave up in favor of web classes because it wasn’t easy to find information about in-person training. (I picked the ClassOnDemand one with Bob Sliga and Steve Hullfish.)

[Drew Lahat]

There was a link chain from input to output, but the solution did have to do with the links.

From the input, I had one serial node splitting to two more nodes, and only one of those was linked to the output. As soon as I rearranged the nodes in a fully compliant manner*, the version got “unstuck” and the video & thumbnails came back.

*I organized them all serially, and added a parallel combiner node. Either way worked.

[Drew Lahat]

Hi Anish,

I can see how that would make sense. Are you basically saying that the manual should read:

“Effects such as (PTZR) are not baked into the final media and passed through” etc… unless you enable “Use Sizing Information from XML”?

[Drew Lahat]

It’s worth noting that in Resolve 9 they changed the name of the relinking feature. Worse, the documentation guys got a different memo than the programmers. The manual refers to it as “Relink Media” (in page 121), while the actual command name in the context menu is “Change Source Folder”.

Might be of use to someone (like me) who’s been learning Resolve and got lost between what you expected something to be called, what it was called in v8, what it’s called now, and what the manual says it’s called.

[Drew Lahat]

Jamie (or anyone who stumbles upon this thread),

Go to Image Scaling / Input Scaling Preset and try “center crop with no resizing” or different settings. I found that it’s important to get it right when using sizing information from XML.

Explanation of the different options is in page 434 of the Resolve 9 manual.

[Drew Lahat]

I join the request.. would be great to have a “render in native resolution” option. DaVinci has put so much effort to make round-tripping viable, and this is a serious hindrance for many workflows (like FCP7, VFX, and I suppose Premiere too).

Evidently nothing in that regard has changed in v9.

[Drew Lahat]

Hi Shane,
Haven’t seen a pattern with the file type. Last time it was ProRes Quicktime. Today it happened again – twice. I was importing an XML and the “Preparing video for display” opened and hanged on top of the XML import dialog.

[Drew Lahat]

The video latency issue was caused by the output setting, which was 1080/24PsF. As soon as I switched to 1080/60i the latency disappeared.
We use a Sony HD broadcast CRT with an HD-SDI input, the only resolutions it supports are 1080/60i, 1080/24PsF and 720/60p.

After getting the same advice from DaVinci support (helpful guys), I upgraded to v9. The scopes are definitely nicer but are still around 4fps. Time to revisit ScopeBox…

I’m just trying to understand, are the built-in scopes smooth for anyone, or that’s how they’re designed?

Might get a GeForce 570 once we upgrade to Lion. For now I’m just starting to acclimate to Resolve after years with Color and Avid Symphony…