Jump to content

Moire-like Noise and Horrific Image Artifacts in ACR

BiffBurger
 Share

Recommended Posts

BiffBurger Newbie

BiffBurger

Posted
Posted

Good afternoon,

 

This is my first time ever posting in a photography related forum. I apologize if I mess up the formatting in any way. I've recently purchased a used Fuji GFX 50s, which which I'm generally extremely happy. However, now that I've started using it for night photography (which is a huge part of my work), I'm noticing some unfortunate issues while processing my RAW files using Adobe Lightroom or ACR.

 

Whenever I shoot any image at or above about 3200 ISO, and expose the image for a few seconds,  a strange moire-like pattern appears in ACR. This becomes apparent whenever I raise the exposure even slightly. In addition, the images fall apart at the seams when even the slightest levels adjustments are applied. Curves adjustments are an indispensable part of processing images of the night sky. Interestingly, images that receive shorter exposure times are fine even at higher ISOs - for the most part. Even so, I've seen very bad deterioration of these files on occasion. Fujifilm has been very helpful and have suggested that I give Capture One a try. I admit that the problem isn't as bad in Capture One. However, I don't want to re-invent my entire workflow - especially since I'll be stacking these images in Adobe after preliminary adjustments are made anyway.

I never had issues like this even with my Canon 5d Mark II. Since the Fuji is superior I'm forced to conclude that I either have a bad camera, or that Adobe isn't able to process these files for some reason.

Has anyone else seen this issue w/ the GFX? Is this related to Adobe's handling of the RAW files? There has to be some workaround... please let me know. Worst case I end up returning the camera under warranty. 

Welcome, dear visitor! As registered member you'd see an image here…

Simply register for free here – We are always happy to welcome new members!

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing

  • Similar Content

  • Posts

    • jerryy
      Fungus

      By jerryy · Posted

      A fungus in the forest.

      Welcome, dear visitor! As registered member you'd see an image here…

      Simply register for free here – We are always happy to welcome new members!

      (p.s. Open Topic.)  
    • Don Barar
      LUT doesn't works on resolve

      By Don Barar · Posted

      The backslashes you are referring are just symbols denoting path.  Once you import into these LUTS into Davinci Resolve those backslashes are removed by default and you only see is the true file name which has no backslashes.  Convince yourself of this by opening the LUT folder from the Davinci Resolve Project Settings.  Do you see any backslashes in those LUT names? Of course not.  The only name you see is the one that has the underscores and the periods. These LUTS work as designed without having to change any path names.  However, they need to be set up properly through CSTs and by what is supported in Davinci Resolve.  Hence, the FLog2C film simulation LUTS cannot be used because Davinci Resolve does not support Fuji Gamut color space and the FLog2C gamut. Alternatively, Davinci Resolve does support Flog2 film simulation LUTS because the color space for FLog2 is Rec 2020 and there is an FLog2 gamut. If all you are doing is changing the path names then you are not getting the correct results.
    • PoorAlchemist
      LUT doesn't works on resolve

      By PoorAlchemist · Posted

      I found the reddit topic i refere to :  https://www.reddit.com/r/davinciresolve/comments/1pc3f1e/cant_apply_new_fujifilm_gfx_55_lut/ "Update for y'all, It's just like what @ExpBalSat said, it's because of the backslashes in the names break them. I changed the file name and it works now. "   For me it was the solution. Realy annoying if it doesn’t work for you 😕  
    • Don Barar
      LUT doesn't works on resolve

      By Don Barar · Posted

      Here is the solution to using the Eterna 55 file simulation LUTs in Davinci Resolve.   In general, do not use the FLog2C to film simulation LUTs as they are not supported by Davinci Resolve for two reasons: 1) Davinci Resolve does not support Fuji Gamut Color Space and 2) Davinci Resolve does not support FLog2C gamma.  Instead, use Flog2 which is supported by Davinci Resolve.  Here is an example.  Let's say that you want to use Classic Chrome simulation.  Do the following: Complete your color grade and use a CST to get to Rec 709. Add a node.  Use a CST to convert from Rec 709 to FLog2.  Output Color space is Rec 2020 and Outout Gamut is FLog2. Add a node.  Apply the FLog2 to Classic Chrome LUT Create a combination node from node in steps 2 and 3. Apply a Key to the combination node and adjust the Key Output Gain to get the amount of the combination node that you want applied. So that you do not have to do this over and over again, generate a LUT for the combination node.  Remember to turn off all other nodes before generating the LUT. Hope this helps others. Don  
    • crazyfields
      Please save me from insanity 23mm f2 vs F1.4r

      By crazyfields · Posted

      Thanks for the insights. I think it's really hard to make a decision without having the two side by side! 
×
×
  • Create New...