Pesky green Flashframe

I have a very strange issue that is consistent since the first Beta of Resolve 15: A sequence imported via XML from FinalCutProX consists entirely of UHD XAVC-I footage from the very same Sony FS-7 camera.

There is one shot in there that always renders with a green flash-frame as it's first frame when I render the sequence from the DELIVER page.

On this shot I have animated a slight push-in. It's not the only shot that has animated Position and Zoom, but it's the only that specific one that gets this green Fram at the start.

I have removed the animation - no green frame.

I have done the animation in the edit page - green frame

I have done the animation in the color page - green frame

I do not see the green frame when working in the Edit, Color or Deliver page. Also when I switch on RENDER CACHE and have Resolve render the sequence I do not see the green frame.

When I export the Sequence via the deliver page and turn on "use render cached images" I do not get the green frame in final output.

But as soon as I have Resolve deliver without using the cache, I get the green frame.

I have even tried to ripple trim the shot to use a slightly different part of it to see if the media file is damaged somehow, but the green flash frame is always the first frame of the specific shot.

Any thoughts?

sounds like your hard disk is too slow, limit the render speed in the deliver page (check the manual if you don't know how) and see if this helps

I doubt that it's a HDD speed issue. I'm working off a Promise RAID that delivers around 680MB/s read and 640MB/s write. Also it's always happening on that one specific clip and only if it has the size/position animation on it.

have you tried limiting the render speed anyway? i had this problem just yesterday on an edit share, and limiting the render speed worked.

Yes I tried reducing the render-speed, but it did not change anything. After a lot of experimentation I switched the GPU processing mode from AUTO to METAL (which still did the green flash frame) and then to openCL. Under openCL I did not have any flash frames yet. Than can mean one of two things: either Apples METAL ist buggy. Something that would explain the bad benchmarks it got from a recent test. Or Resolve's METAL integration is flaky.
I have upgraded to R15B6 today and will retest the issue, as soon as I have time.

Try the latest update to High Sierra too. Metal sometimes still looks like a work in progress…

I'm current macOS-wise. 10.13.5

OK, your signature said 10.13.4.