Jump to content

Fuji GFX 100 II... had a play


Andrew Reid
 Share

Recommended Posts

EOSHD Pro Color 5 for Sony cameras EOSHD Z LOG for Nikon CamerasEOSHD C-LOG and Film Profiles for All Canon DSLRs
12 hours ago, androidlad said:

Fuijifilm provided IDT for ACES:

https://fujifilm-x.com/en-ie/support/download/lut/

Thanks.

I downloaded the IDTs and installed them in Resolve Studio. I get inconsistent results with them. If I use my standard way of setting up ACES, like this:

image.png.646e16d677d28067b3a585d138127219.png

I get a washed out image.

If I instead select ARRI LogC3 as the input transform, I get a nice looking image.

Any idea what's going on here? What am I doing wrong?

Link to comment
Share on other sites

14 hours ago, Jedi Master said:

Thanks.

I downloaded the IDTs and installed them in Resolve Studio. I get inconsistent results with them. If I use my standard way of setting up ACES, like this:

image.png.646e16d677d28067b3a585d138127219.png

I get a washed out image.

If I instead select ARRI LogC3 as the input transform, I get a nice looking image.

Any idea what's going on here? What am I doing wrong?

May I ask how you installed the IDT? I didn't follow Resolve development lately but I was under the impression that they only support DCTL format. What Fuji provides is in CTL format, for me it doesn't even shop up in the IDT list, even though I copied it to Resolve's IDT directory.

Link to comment
Share on other sites

6 hours ago, Attila Bakos said:

May I ask how you installed the IDT? I didn't follow Resolve development lately but I was under the impression that they only support DCTL format. What Fuji provides is in CTL format, for me it doesn't even shop up in the IDT list, even though I copied it to Resolve's IDT directory.

You need to change the file extension from .ctl to .dctl and add one line to the top of the file. I’m at lunch right now, so I don’t have access to my computer. I’ll post the line you need to add when I get home. After that, you just need to restart Resolve and the new IDT will show up in the list.

Link to comment
Share on other sites

On 12/7/2023 at 7:40 PM, Jedi Master said:

You need to change the file extension from .ctl to .dctl and add one line to the top of the file. I’m at lunch right now, so I don’t have access to my computer. I’ll post the line you need to add when I get home. After that, you just need to restart Resolve and the new IDT will show up in the list.

That's why I asked. A CTL is not a DCTL, you can change the extension and add the necessary line, it will then show up in the IDT list, but it won't be executed, I assume it even generates some error logs in the background. 

Link to comment
Share on other sites

The Fuji IDT file needs to be modified to conform to DCTL syntax, extension renamed to .dctl and placed in /Blackmagic Design/DaVinci Resolve/ACES Transforms/IDT/

Quote

// ACES IDT for FUJIFILM F-Log2

// FUFJIFILM Corpration

// Version:1.00

 

DEFINE_ACES_PARAM(IS_PARAMETRIC_ACES_TRANSFORM: 0)

 

__DEVICE__ inline float FLog2ToSceneLinearReflection(float x)

{

if (x > 0.100686685370811f)

return (pow(10.f,(x - 0.384316f) / 0.245281f) - 0.064829f) / 5.555556f;

else

return (x - 0.092864f) / 8.799461f;

}

 

__DEVICE__ float3 transform(int p_Width, int p_Height, int p_X, int p_Y, float p_R, float p_G, float p_B)

{

float r_lin = FLog2ToSceneLinearReflection(p_R);

float g_lin = FLog2ToSceneLinearReflection(p_G);

float b_lin = FLog2ToSceneLinearReflection(p_B);

 

float rOut = r_lin * 0.62021930886364f + g_lin * 0.18821587793692f + b_lin * 0.19156481319944f;

float gOut = r_lin * 0.00494087068593f + g_lin * 0.89909785987571f + b_lin * 0.09596126943836f;

float bOut = r_lin * -0.03660757899425f + g_lin * 0.03316228790203f + b_lin * 1.00344529109222f;

 

return make_float3(rOut, gOut, bOut);

}

Credit to Hook Stowers from LGG.

Link to comment
Share on other sites

Try this. Save it to a file with .dctl extension and copy it to the place where Resolve looks for DCTL files.

DEFINE_ACES_PARAM(IS_PARAMETRIC_ACES_TRANSFORM: 0)

__DEVICE__ inline float log_to_linear(float in)
{

    float out;

    if (in < 0.100537775223865f)
    {
        out = (in - 0.092864000000000f) / 8.735631000000000f;
    }
    else
    {
        out = _powf(10.0f, (in - 0.790453000000000f) / 0.344676000000000f) / 0.555556000000000f - 0.009468000000000f / 0.555556000000000f;
    }

    return out;
}

__DEVICE__ float3 transform(int p_Width, int p_Height, int p_X, int p_Y, float p_R, float p_G, float p_B)
{

    float r1 = log_to_linear(p_R);
    float g1 = log_to_linear(p_G);
    float b1 = log_to_linear(p_B);

    float r2 = r1 * 0.69545200f + g1 * 0.14067900f + b1 * 0.1638690f;
    float g2 = r1 * 0.04479460f + g1 * 0.85967100f + b1 * 0.0955343f;
    float b2 = r1 * -0.00552588f + g1 * 0.00402521f + b1 * 1.0015000f;

    return make_float3(r2, g2, b2);
}
 

Link to comment
Share on other sites

Create sliders for basic tools that function in a similar way that they would in capture one. Exposure, wb, shadow, highlights, contrast, saturation, etc. 

 

Most of this exists in existing dctl's or even in resolve already but it's either not user friendly, or doesn't function in a way that's pleasing enough. 

 

I'm going to try hacking things together but I know I'll definitely need help. 

Link to comment
Share on other sites

39 minutes ago, D Verco said:

Create sliders for basic tools that function in a similar way that they would in capture one. Exposure, wb, shadow, highlights, contrast, saturation, etc. 

 

Most of this exists in existing dctl's or even in resolve already but it's either not user friendly, or doesn't function in a way that's pleasing enough. 

 

I'm going to try hacking things together but I know I'll definitely need help. 

Sounds relatively straight-forwards if you work methodically.

I suggest the following:

  • Start with a working DCTL that does similar things
  • Make a copy of it in the DCTL folder, run Resolve and get it loaded up and confirm it works
  • Open it in a text editor
    (Once you've done this you can save the DCTL file, and reload it in Resolve without having to restart)
  • Then make a single change to the DCTL, reload it, and confirm it still works
  • If it doesn't work then undo whatever change you made and you should be back to having it work again, and have another go.  Depending on your text editor the save might clear the un-do history, so maybe keep a copy of the whole thing in another document ready to paste back in if you have a challenge
  • Keep making incremental changes until you get it how you want it

You should be able to copy/paste functions from other scripts, change the math / logic, add controls to the interface etc.  The key is doing it one change at a time so that you don't spend ages making lots of changes then even more time trying to troubleshoot it when it doesn't work.

Link to comment
Share on other sites

  • 5 months later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

  • EOSHD Pro Color 5 for All Sony cameras
    EOSHD C-LOG and Film Profiles for All Canon DSLRs
    EOSHD Dynamic Range Enhancer for H.264/H.265
×
×
  • Create New...