To troubleshoot compression artifacts during video fades, compare a short, high-quality reference export with your delivery file. In DaVinci Resolve on Mac, this helps separate preview problems, source banding and export compression before you change the edit.

This workflow is for a Mac editor whose fade to black or dissolve develops visible stripes, blocky patches or uneven changes in brightness. It uses controls documented in the DaVinci Resolve 21 reference manual and Apple’s current Compressor guide. Match the instructions to your installed version; available encoding options can depend on the selected format and hardware.

Identify what changes during the fade

Start with a few seconds that include the image before the fade, the entire transition and its ending. Watch at normal playback speed, then pause where the defect is clearest. Describe the visible pattern before choosing a remedy.

Broad stripes across a smooth gradient suggest banding. Blackmagic explains that low bit-depth images may lack enough color values to represent a shallow gradient smoothly. Higher processing precision can help preserve subsequent adjustments, but it does not remove banding already present in the source. DaVinci Resolve 21 Reference Manual, “Color Bit Depths”

Block-shaped patches, bands and a general brightness mismatch are useful observations, but their appearance alone does not establish where the problem began. Use the comparisons below as a diagnostic sequence. The conclusions are working inferences to test, rather than guarantees about a particular codec.

What you observe What to test next
The preview looks poor, but the reference export looks smooth Check proxy and render-cache quality.
The reference looks smooth, but the delivery encode develops artifacts Test delivery bitrate and bit depth.
The original graphic or clip already contains stripes Replace or repair that source before encoding again.
Artifacts appear after a particular effect Compare with that effect temporarily bypassed.
The same file looks different between applications Investigate playback and color interpretation before altering the fade.

Keep the same display, viewing size and approximate brightness throughout these comparisons. Changing the viewing conditions at the same time as an export setting makes the result harder to interpret.

Rule out proxies and cached preview images

Resolve can play proxy media during editing and can optionally reuse proxies, optimized media or rendered cache files during export. Those are separate choices. A smooth original can therefore pass through a lower-quality intermediate unless you check the relevant controls. DaVinci Resolve 21 Reference Manual, chapters 8 and 187

For a diagnostic preview in the Edit page:

  1. Choose Playback > Proxy Handling > Disable All Proxies to force original-media playback.
  2. Confirm that the affected clip remains online. This setting displays missing originals as offline rather than substituting a proxy.
  3. Choose Playback > Render Cache > Off to compare without rendered cache playback.
  4. Examine the affected frames again. If playback becomes slow, use paused frames and the reference export in the next section to assess image quality.

These menu choices are documented in Resolve 21. Using Disable All Proxies is useful here because Prefer Camera Originals can still fall back to a proxy when an original is unavailable. DaVinci Resolve 21 Reference Manual, “Switching Between Proxy Media and Original Media” and render-cache controls

If bypassing the cache changes the image, review Project Settings > Master Settings and the Render cache format. Blackmagic recommends formats such as ProRes 4444, ProRes 4444 XQ, DNxHR 444 or 16-bit float when grading cached material, particularly where preserving out-of-range image values matters. Choose a format appropriate to the project before rebuilding the cache. DaVinci Resolve 21 Reference Manual, “Choosing the Appropriate Cache Media Format for Your Project”

Treat a cache improvement as evidence about the preview path. You still need to inspect an exported file before deciding that the delivery problem is solved.

Make a reference export that preserves the fade

Export the short problem section before rendering the whole project again. Keep its resolution, frame rate, grade and fade duration unchanged so the export path is the main variable.

On the Deliver page:

  1. Select Custom Export and render as Single clip.
  2. Set the render range to include the complete fade and a little material on either side.
  3. Select QuickTime with an available Apple ProRes 422 HQ codec option.
  4. In the video Advanced Settings, deselect Use proxy media, Use optimized media and Use render cached images for this diagnostic render.
  5. Give the file a distinct name, add it to the render queue and render it.

Resolve documents these reuse options as ways to save rendering time. Disabling them avoids deliberately exporting through a lower-quality proxy, optimized file or cache. Apple documents ProRes 422 HQ as supporting 10-bit, 4:2:2 video, making it a useful reference for this comparison. It remains a compressed format. DaVinci Resolve 21 Reference Manual, “Rendering Media”, About Apple ProRes

Import the reference back into Resolve and compare the same transition frames with the timeline. Also play the file in the Mac application intended for delivery. If the reference is smooth while the smaller delivery encode breaks up, concentrate on delivery settings. If both show the defect, inspect the source, processing and playback path before spending time on higher bitrates.

Change delivery settings one variable at a time

Test bitrate when the reference is clean

Return to your intended H.264 or H.265 export settings. Keep the resolution, frame rate and encoding profile fixed, then make a second short export with a higher bitrate limit. Resolve documents the Restrict to control as a maximum data-rate setting; the available compression controls depend on the format and codec. DaVinci Resolve 21 Reference Manual, “Optional MP4, H.264, H.265, VP9, or HEVC Controls”

For example, if your existing limit is 8,000 Kb/s, compare it with 16,000 Kb/s. These are illustrative test inputs, not recommended delivery rates. If the higher-rate version improves the fade, continue testing within your actual file-size and playback requirements. If it barely changes, move to bit depth instead of repeatedly increasing the number.

Do not change the fade duration during this test. That creates different image content and weakens the comparison between encoding settings.

Test 10-bit output for smooth gradients

Bitrate and bit depth control different aspects of the output. Resolve documents H.265 Main as an 8-bit profile and Main10 as a 10-bit profile. If your installed encoder exposes Main10 and your intended playback application accepts it, compare a short export using that profile. Do not assume every H.265 file is 10-bit. DaVinci Resolve 21 Reference Manual, encoding profiles

Keep the project’s intended color space unchanged while testing. Choosing 10-bit output does not require turning an SDR edit into HDR. Apple also cautions that transcoding an existing 8-bit SDR file into a 10-bit HDR option cannot recreate detail absent from the original. Modify video color space and HDR metadata in Compressor

If the required delivery format cannot preserve the reference’s smoothness, keep the high-quality master and make the delivery version from it. Record the compromise you accept—visible banding, file size or playback compatibility—so later exports use the same deliberate choice.

Repair banding that exists before delivery compression

If the reference export contains the same stripes, compare the original clip or graphic before its grade and effects. Temporarily bypass one suspect adjustment at a time. For a synthetic gradient or neutral title background, check whether replacing a previously exported image with its editable original removes the problem.

For Fusion work, distinguish the integrated Fusion page from the separate Fusion Studio application. Blackmagic states that Resolve’s Fusion page always processes images at 32-bit float precision per channel; Fusion Studio offers selectable processing depths. Searching for an 8-bit-to-32-bit project switch in Resolve’s Fusion page is therefore unnecessary. Existing banding in an imported image can remain despite high-precision processing. DaVinci Resolve 21 Reference Manual, chapter 75, “Color Bit Depths”

Use targeted debanding in Resolve Studio

Resolve’s Deband effect is documented as Studio-only. It reduces visible band boundaries by dithering pixels around detected edges. Blackmagic recommends isolating the affected region with a window or qualifier because unrestricted application can soften other edges. DaVinci Resolve 21 Reference Manual, chapter 163, “Deband”

If you have Studio, apply Deband to a separate color node and limit it to the affected gradient. Use Display Edge to inspect detected boundaries, then adjust Edge Threshold, Radius and Post Refine while comparing with the effect bypassed. Check nearby text and graphic outlines for unwanted softening, and judge the complete moving fade before accepting the result.

If you use the free edition, continue with source replacement, a less demanding adjustment or the delivery tests above. The documented Deband workflow requires Studio.

Try video dithering in Apple Compressor

If Compressor is available, test its documented video dithering control using the cleanest reference export as input:

  1. Apply the intended video preset and select its output row.
  2. In the Video inspector, find the Quality section.
  3. Enable Dithering and transcode the short test section.
  4. Compare against an otherwise identical export with dithering disabled.

Apple describes this control as adding noise to reduce distracting patterns such as banding, and advises disabling it if the rendered result becomes excessively noisy. Evaluate the compressed output itself before keeping the change. This is Compressor’s video control; Fairlight audio adjustments do not address image gradients. Set retiming and resizing quality in Compressor

Compressor’s available properties depend on the source, preset format, other selected properties, hardware and software. For HEVC, its Profile control selects output color depth; the presence of a particular option should be checked in the actual job. Video properties of presets in Compressor

Verify the finished fade in its intended playback path

Once a short test succeeds, apply those settings to the complete export. Check the start, middle and final visible frames of each affected fade, then watch at normal speed. Compare with the reference master and verify that titles remain sharp and the intended black endpoint is preserved.

If the file’s overall brightness changes between applications, keep that investigation separate from banding repair. In Compressor, changing the source assignment in the Job inspector changes how the source is interpreted; converting the output color space is a separate setting in the Video inspector. Randomly changing either can complicate the comparison. Modify video color space and HDR metadata in Compressor

Keep the reference master and a brief record of the settings that passed your test. A useful stopping point is a fade that plays acceptably in its intended application, preserves surrounding detail and meets the delivery requirements. The reference comparison gives you a repeatable way to reach that decision on the next edit.

Sources