Blackmagic Forum

There is known Cross Hatching problem described in this thread viewtopic.php?f=2&t=51936&start=400
As you may know it can be fixed by shifting XY position to 0.5px. https://ursa-mini-fpn-grid-pattern-nois ... 18/fix-46k

it seems in Resolve 15 beta5 (tested non studio) it don't works as it should. It produces artifact at the edges. It is also visible at the rendered images. (see full sized images)

This is still don't fixed n Resolve 15.1.1
Dear developers please take attention to this problem! It worked well in Resolve 14 but you destroy things in Resolve 15 and still don't fix it.

Resize mode "Sharper" in Settings:
Edit Page XY 0.5 px transform produce = 1 pixel black frame edge on rendered image
Color Page Node sizing Pan/Tilt 0.5 px node transform = 1 pixel black frame edge on rendered image
Color Page Input sizing Pan/Tilt 0.5 px node transform = 1 pixel black frame edge on rendered image

Resize mode "Bicubic" in Settings:
Color Page Node sizing Pan/Tilt 0.5 px node transform = 1 pixel black frame edge
Color Page Input sizing Pan/Tilt 0.5 px node transform = NO pixel black edge.
Edit Page XY 0.5 px transform = NO pixel black edge.

But If you essentially select "Force sizing to highest quality" in render settings there is always 1 pixel black frame edge on rendered image with ANY previous settings.

BTW, don't you thinking about some kind of dedicated OFX plugin or some kind of setting button in RAW tab to fix Cross Hatching? This can make workflow way simpler.

P.S. There is a huge thread about this problem, Cross Hatching Wont Go Away viewtopic.php?f=2&t=51936 Setting Pan/Tilt 0.5 px is the ONLY way to fix it yet.

Problem still NOT fixed in Resolve 16 b6

Currently the only way to avoid side pixel edge is:
- set clip attributes to to super scale 2x
- set clip Input sizing or Edit sizing Pan/Tilt to 0.5px

Dmitry Shijan wrote:There is known Cross Hatching problem described in this thread viewtopic.php?f=2&t=51936&start=400
As you may know it can be fixed by shifting XY position to 0.5px. https://ursa-mini-fpn-grid-pattern-nois ... 18/fix-46k

it seems in Resolve 15 beta5 (tested non studio) it don't works as it should. It produces artifact at the edges. It is also visible at the rendered images. (see full sized images)

Hey Dmitry, Do you know if there is a download file anywhere for Camera settings: RAW, resolution 1920 x 1080?

Not sure if i understand what download are you talking about? Is it about That thumblr post? It just contains preset with two nodes: One node with Node Pan/Tilt position 0.5px. And another node with Pan/Tilt position -0.5px. I post that link just to show that Cross Hatching fix, exists and that i am not the only one who cares about it.

It is way simpler to add node manually than download those presets baked to different project resolutions.

Things became even more confused when multiple are settings combined:

Project Resize Filter Sharp + Clip Attributes SuperScale + Input sizing Pan/Tilt 0.5px = No Pixel line Edge
Project Resize Filter Sharp + Input sizing Pan/Tilt 0.5px = Pixel line Edge

Project Resize Filter Smooth or Bicubic + Clip Attributes SuperScale + Input sizing Pan/Tilt 0.5px = Pixel line Edge
Project Resize Filter Smooth or Bicubic + Input sizing Pan/Tilt 0.5px = No Pixel line Edge

Resolve 16.3 b3 - no any changes

I’m not aware of what the node does, but I assume it does some sort of node shifting.

As workaround, can you get the result of the tool and layer it on top of the original image so you effectively duplicate the last row of pixels?

waltervolpatto wrote:I’m not aware of what the node does, but I assume it does some sort of node shifting.

Yes, node shifts image to X/Y 0.5px and another node shifts back to X/Y -0.5px. As a result image sharpness and position became 100% unchanged but cross hatching pattern is 100% gone.
There are few rows of technical "hidden" pixels in DNG files that allow those tiny shifts without edges artifacts. But for some strange reason starting from Resolve 15 those technical "hidden" pixels from Left and Right edges are somehow cropped internally and so image produce black pixel line at the left and right edges when apply node pan/tilt 0.5px.
Same time Top and Bottom edges are OK. Resolve still can see technical "hidden" pixels at Top and Bottom and don't produce black pixel lines there when apply node pan/tilt 0.5px.

waltervolpatto wrote:IAs workaround, can you get the result of the tool and layer it on top of the original image so you effectively duplicate the last row of pixels?

Can you explain your idea in more details?

Also note that Cross Hatching and FPN is near invisible in original BMPCC and way more visible in 4.6K sensors DNG if compare it to BMMCC. I guess it depends of sensor dynamic range factory "overclock". BMPCC have less effective cooling and so most FPN and cross-hatching pattern is permanently hidden inside noise structure.
BMMCC and 4.6K sensors have less noise in shadows due better sensor cooling but as side effect FPN and cross-hatching pattern became way more visible.

In Resolve 17 Pan/Tilt 0.5px now seems always produce edge artifacts even if applied to Input sizing or Edit sizing or in Timeline inspector.
Instead of fix that stupid cross-hatched input bug with DNG somehow internally, developers just change something in resize code and completely kill that partially existing option in Resolve 17. This is very bad.

Hi Dmitry,

I dont understand why this problem is still not fixed...

Meanwhile, you can use my "fix" which is even more tinkered than the orignal one..

Edit: Iam using this with 1920*1080 RAW cDNG footage from my BMMCC, maybe the Window Pan/Tilt has to be adjusted for other resolutions

did you try to use the new custom filters? while bicubic does cross hatch, "mitchell" does not.