Blackmagic Forum

Yeah, you read that right... exporting footage results in a pink filter being applied over the image.
scrubbing timeline it's fine, normal grade. But once exporting you get a pink image.

I've encountered this on the timeline before when GPU memory is full with error message "Your GPU memory is full. Try reducing the timeline resolution or the number of correctors" so I make proxies and it's okay.
But when rendering it seems to hit that same issue, and then just destroys the final output.

The composition has Fusion elements - Spherical Cameras, Image Plane 3D, Renderer 3D and resizers for placing 2D footage into 360

as a test I set it to render a 10 second segment with some text and 2D video overlayed, it didn't apply the pink filter but failed "GPU Processing on the current clip failed because of an error". So yeah seems to be GPU related, however, there's no direction on how to resolve this or why it'll spontaneously go pink.

Is there a trick in resolve to not crash once GPU memory is full?

Render Settings (shown in attached image)
Resolve Version - 17, tried beta 7 and beta 9
Timeline - 8K 360 footage (7680x3840 30fps ProRes media)
Encoder Leave as Native, if I select NVIDIA it presents an error "select a valid resolution"
Quicktime h.264
Quality - tried best, medium, low, all show pink

System Specs
Intel i9 9900K
RTX 2070 8GB
64GB RAM

proxies live on a 1TB NVMe drive, however raw media is on a HDD, so thinking I might try and move all native media to the NVMe, relink, and try again incase being able to read the media speeds it up, no idea if that'll help with GPU issues. Any ideas are greatly appreciated.

So changed my NVIDIA drivers from Gaming to Studio
Also changed the render out drive to the NVMe from the HDD, it rendered way faster, until well it seems the GPU memory got full and now my screen is a rave party once again.




I have planned to get a 3080ti, rumoured 20GB VRAM, once released.
What am I supposed to do when 8GB VRAM isn't enough now?

Now second thought on the issue, the fusion effects have been bundled up into Macro's and applied on the main timeline outside of a fusion composition (using the new Macro abilities of v17), this may be tipping it over the limit. Here's the code of the Fusion Nodes, with the Input being a 4K 16:9 clip, and output being the warped 360 image version.

Code: Select all

{
   Tools = ordered() {
      ImagePlane3D1 = ImagePlane3D {
         Inputs = {
            ["Transform3DOp.Translate.X"] = Input { Value = -0.511719414523221, },
            ["Transform3DOp.Translate.Y"] = Input { Value = -0.0938155654965702, },
            ["Transform3DOp.Translate.Z"] = Input { Value = -1.12042054339362, },
            ["Transform3DOp.Rotate.Y"] = Input { Value = 15.2144095348194, },
            ["Transform3DOp.Scale.Z"] = Input { Value = 4.49019607843137, },
            ["SurfacePlaneInputs.ObjectID.ObjectID"] = Input { Value = 1, },
            ["MtlStdInputs.MaterialID"] = Input { Value = 1, },
         },
         ViewInfo = OperatorInfo { Pos = { 346.369, 47.5322 } },
      },
      Merge3D1 = Merge3D {
         Inputs = {
            SceneInput1 = Input {
               SourceOp = "SphericalCamera1",
               Source = "Output",
            },
            SceneInput2 = Input {
               SourceOp = "ImagePlane3D1",
               Source = "Output",
            },
         },
         ViewInfo = OperatorInfo { Pos = { 511.369, 47.5322 } },
      },
      SphericalCamera1 = SphericalCamera3D {
         Inputs = {
            ["Stereo.Nest"] = Input { Value = 1, },
            ["Stereo.Mode"] = Input { Value = FuID { "OffAxis" }, },
            ControlVis = Input { Value = 1, },
         },
         ViewInfo = OperatorInfo { Pos = { 510.703, 91.3807 } },
      },
      Resize1 = BetterResize {
         CtrlWZoom = false,
         Inputs = {
            Width = Input { Value = 7680, },
            Height = Input { Value = 3840, },
            UseFrameFormatSettings = Input { Value = 1, },
            HiQOnly = Input { Value = 0, },
            PixelAspect = Input { Value = { 1, 1 }, },
            Input = Input {
               SourceOp = "Renderer3D1",
               Source = "Output",
            },
         },
         ViewInfo = OperatorInfo { Pos = { 673.036, 88.3504 } },
      },
      Renderer3D1 = Renderer3D {
         CustomData = { ToolVersion = 2, },
         Inputs = {
            GlobalOut = Input { Value = 3219, },
            Width = Input { Value = 7680, },
            Height = Input { Value = 3840, },
            ["Gamut.SLogVersion"] = Input { Value = FuID { "SLog2" }, },
            SceneInput = Input {
               SourceOp = "Merge3D1",
               Source = "Output",
            },
            CameraSelector = Input { Value = FuID { "SphericalCamera1" }, },
         },
         ViewInfo = OperatorInfo { Pos = { 676.37, 47.5322 } },
      }
   }
}

I know resolve uses GPU more than premiere, but I've been able to edit 8K 360 videos with ambisonics audio in premiere and although it would crash (no surprise), it would render as the timeline showed.

Also this is my 4th "biggish" project in resolve, first 360 video, so no idea if this would have worked in v16 however it doesn't have the macro abilities which I've finally jumped onto v17 for

It's only that Fusion clip that's pink? Normal camera clips without effects export fine?

Hi Jim,

Sorry I should have clarified:
This is what it should look like:


The "Pink" clip is the 8K ProRes footage, this is actually in a Fusion comp with a simple panorama effect to re-orient the 360 camera position.
The small "2D 16:9" clips are on the timeline with a Fusion Macro applied, that's the heavier Spherical Cameras and 3D planar effects (the code of node tree provided in the previous message).

I've tried putting it all into a single fusion clip and merging but it gave the same results.

And in the second message's pink example, you can see a frame from a hyper-lapse building something has been stretched full screen at 50% opacity over the 360 shot of the room... this shows resolve has completely ignored the Fusion effects placed on that clip at that moment as it never looked like that on the timeline.

I opened it up this morning, and it instantly displayed the "GPU Memory Full" error then everything glitched out on the preview window and quit, just quit to desktop, no freezing or anything.

Leaving the timeline open, not doing anything on the computer, and I can hear my PC fans revving up. The error "GPU Memory Full" pops up, I click it away, it pops up again a moment later. So even though that frame has been rendered it seems to be stuck "doing something" even when just previewing the timeline.

I can't tell how this is bombing out so hard, surely it should just run slower if it can't handle the effect, and not throw an error to then sabotage the footage with rainbows haha. Maybe I'm just used to After Effects where if you hammer it your framerate preview will drop astronomically but it never just "fills up" VRAM and leaves it, it just works at a pace it can process.

You could be looking at a bug here. It is a beta.

I'm just wondering if normal media without any Fusion effects also comes out with weird colors? I'm wondering if the Fusion stuff is the culprit here.