Jedi Master Posted December 5, 2023 Share Posted December 5, 2023 7 minutes ago, androidlad said: But each clip is around 900MB though. I see that now that the 21.5GB ZIP file has downloaded. Time to try grading them in Resolve and look for a workaround to the fact that there's no Fujifilm F-log input transform in either ACES or DWG color spaces. Quote Link to comment Share on other sites More sharing options...
Jedi Master Posted December 5, 2023 Share Posted December 5, 2023 2 hours ago, eatstoomuchjam said: Do you have a google drive/dropbox/whatever where you'd like me to share it? I could also share with something like Resilio if you use that. I got what I needed from the link posted above and don't need your footage. I appreciate the offer! eatstoomuchjam 1 Quote Link to comment Share on other sites More sharing options...
androidlad Posted December 6, 2023 Share Posted December 6, 2023 9 hours ago, Jedi Master said: I see that now that the 21.5GB ZIP file has downloaded. Time to try grading them in Resolve and look for a workaround to the fact that there's no Fujifilm F-log input transform in either ACES or DWG color spaces. Fuijifilm provided IDT for ACES: https://fujifilm-x.com/en-ie/support/download/lut/ Quote Link to comment Share on other sites More sharing options...
Jedi Master Posted December 6, 2023 Share Posted December 6, 2023 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: 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? Quote Link to comment Share on other sites More sharing options...
D Verco Posted December 6, 2023 Share Posted December 6, 2023 I've never used aces, but I can tell you that the correct cst inputs are ARRI LogC3 and rec2020. Quote Link to comment Share on other sites More sharing options...
Jedi Master Posted December 6, 2023 Share Posted December 6, 2023 4 minutes ago, D Verco said: I've never used aces, but I can tell you that the correct cst inputs are ARRI LogC3 and rec2020. Thanks. Yes, that looks much better. Quote Link to comment Share on other sites More sharing options...
D Verco Posted December 6, 2023 Share Posted December 6, 2023 On 12/6/2023 at 6:48 AM, androidlad said: https://mocfilmmaker.wetransfer.com/downloads/8d56d6ccf62e7bc1682da8c61735b79220230929102636/c7962e Are you able to repost? Andrew Reid 1 Quote Link to comment Share on other sites More sharing options...
Attila Bakos Posted December 7, 2023 Share Posted December 7, 2023 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: 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. Quote Link to comment Share on other sites More sharing options...
Jedi Master Posted December 7, 2023 Share Posted December 7, 2023 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. Quote Link to comment Share on other sites More sharing options...
Jedi Master Posted December 7, 2023 Share Posted December 7, 2023 Here's the line you need to put at the top of the file (after the comments, but before the first non-comment line): DEFINE_ACES_PARAM(IS_PARAMETRIC_ACES_TRANSFORM: 0) kye 1 Quote Link to comment Share on other sites More sharing options...
Attila Bakos Posted December 10, 2023 Share Posted December 10, 2023 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. Quote Link to comment Share on other sites More sharing options...
androidlad Posted December 10, 2023 Share Posted December 10, 2023 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. kye 1 Quote Link to comment Share on other sites More sharing options...
Jedi Master Posted December 10, 2023 Share Posted December 10, 2023 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); } Quote Link to comment Share on other sites More sharing options...
D Verco Posted December 11, 2023 Share Posted December 11, 2023 Do you have experience with dctl's? I'm attempting to make one when I have spare time Quote Link to comment Share on other sites More sharing options...
kye Posted December 11, 2023 Share Posted December 11, 2023 26 minutes ago, D Verco said: Do you have experience with dctl's? I'm attempting to make one when I have spare time I have a small amount of experience with them. What are you trying to do? Quote Link to comment Share on other sites More sharing options...
D Verco Posted December 11, 2023 Share Posted December 11, 2023 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. Quote Link to comment Share on other sites More sharing options...
kye Posted December 11, 2023 Share Posted December 11, 2023 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. Quote Link to comment Share on other sites More sharing options...
Attila Bakos Posted December 11, 2023 Share Posted December 11, 2023 9 hours ago, Jedi Master said: Try this. Save it to a file with .dctl extension and copy it to the place where Resolve looks for DCTL files. FYI that's an F-Log DCTL, I thought you wanted an F-Log2 one, which androidlad posted already. Quote Link to comment Share on other sites More sharing options...
Jedi Master Posted December 11, 2023 Share Posted December 11, 2023 9 hours ago, Attila Bakos said: FYI that's an F-Log DCTL, I thought you wanted an F-Log2 one, which androidlad posted already. Yes, I know. I was working with F-Log yesterday to compare it with F-Log2. Quote Link to comment Share on other sites More sharing options...
kye Posted May 23 Share Posted May 23 Looks pretty good.... The poor-shooters Alexa 65? eatstoomuchjam, SRV1981, mercer and 2 others 5 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
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.