Contour

**What Contour actually does.** Krokodove Contour extracts visible image boundaries to create an edge-oriented graphic result. Blackmagic categorizes it as edge detection, not automatic rotoscoping or arbitrary semantic object selection.

**Two documented tabs.** Controls exposes Width, Threshold, Levels and three Lock switches. Render exposes Super-Sampling and Pre-Divide / Post-Multiply. Settings is visible as a tab, but its interior was not captured and its controls are not invented here.

**Useful adjustment order.** Begin with a clean source, establish a readable Width, then isolate Threshold and Levels one at a time. Changing all three at once makes it impossible to tell which setting introduces unwanted edges or removes useful ones.

**Width controls outline geometry.** The original Inspector capture shows Width = 0.009999. That is the recorded slider value, not a recommended universal setting for HD or UHD. Compare thickness at fixed viewer scale and at actual delivery resolution.

**Lock Horizontal/Vertical.** This switch links horizontal and vertical width behavior. If you disable it, inspect the fields exposed by your exact Resolve build rather than assuming undocumented names or numeric ranges for independent axes.

**Threshold gates boundary response.** Change Threshold while watching how many transitions survive and how prominent they appear. The archived value of 0.5 is only a captured example. The precise pixel response and direction must be confirmed in your target version.

**Lock Threshold.** A dedicated threshold lock is visible in Inspector. What independent fields appear after unlocking was not recorded, so inspect them in the live UI rather than assuming the implementation of an unrelated Krokodove tool.

**Levels changes the contour structure.** Levels influences the character and density of the outline response, with 5.0 shown in the original screenshot. Do not claim that this produces exactly five lines or universal posterization bands without native evidence.

**Lock Levels.** The third lock belongs to Levels, not image dimensions or supersampling. When inspecting it, toggle only that switch and record any additional controls revealed in your installed build.

**Unlike a binary Threshold node.** Contour focuses on visual boundaries; thresholding tools instead gate a selected scalar channel. A contour graphic should not be assumed to be a hard object matte: antialiased or semitransparent line pixels may remain.

**Contour versus Edge Detect.** Both concern image boundaries, but their controls and visual response can differ. Compare them on the same source image instead of copying Threshold/Width values between potentially unrelated algorithms.

**Noise and compression blocks.** Fine high-frequency texture and codec artifacts can produce many candidate boundaries. A gentle upstream Blur or noise reduction can simplify the result, provided essential subject shapes remain intact.

**1x1 is the control baseline.** Render mode 1x1 provides the starting point without extra supersampling. Establish the contour appearance first, then increase sampling only when visible stair stepping or temporal shimmer justifies the overhead.

**Available Super-Sampling choices.** The archived dropdown shows 1x1, 2x2, 3x3, 4x4, 5x5, 8x8 and 16x16. These are mutually exclusive settings, not seven separate effects or a promise of proportionally more detail.

**Sampling quality has a cost.** Higher supersampling can require substantially more processing. Compare not just single-frame appearance but actual animated playback, especially for thin moving boundaries and transitions.

**Pre-Divide / Post-Multiply.** This Render checkbox addresses processing of image color around premultiplied alpha. It is not a keying or mask-generation command. Compare its two states on an alpha-bearing source and inspect colored edge fringes.

**Alpha needs independent inspection.** Do not assume Contour automatically creates a production-quality matte that composites correctly over every background. Inspect RGB and Alpha, then compare over light and dark backdrops; a static Flow diagram cannot certify rendered pixels.

**Localized compositing.** The available screenshots do not show physical Contour sockets. Teaching examples localize the composite with Rectangle connected to the known Merge.EffectMask rather than inventing a verified Contour.EffectMask port.

**Glow belongs downstream.** Feed the contour result through Glow, then composite it with the source via Merge. Glow styles existing extracted boundaries; it cannot repair poor Contour geometry or an inappropriate Threshold.

**Native Resolve acceptance.** Final verification must capture the actual Input/Output/Mask sockets, Levels/Threshold response, Alpha behavior, performance and Settings contents in the installed build. The archive contains original Inspector PNGs but no native-verified .comp or rendered frame.