Jump to content

Grid Dots on RAW image

BulletProof
 Share

Recommended Posts

BulletProof Rookie

BulletProof

Posted
Posted

This is my first digital camera.  I used to shoot film many years ago, and have had a few digital pocket cameras, but I recently bought an X-e1 to try and get into photography again. So far the process that is causing issues is:

1. Take Photo in JpegF/RAW

2. Use Adobe DNG converter to convert RAF files to DNG (so my version of Photoshop can open them)

3. Open in Photoshop and zoom in... (attached image is a clip zoomed in at 300%)

Please note: These grid/squares/dots are not visible in the jpeg image taken directly from the camera into Photoshop... so this issue may have nothing to do with the X-e1 at all... or...

Thank you for any help you can provide!

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
BulletProof Rookie

BulletProof

Posted
  • Author
Posted

As to upgrading... I am currently trying to exist in this sweet spot where I can continue to run my CS5.5 Adobe Products.  Upgrading DNG will require updating my OS which will mean I can no longer run CS.  And I am not now, not ever, going to pay Adobe monthly to use their software... I will tear my computer out of the wall, pour lighter fluid on it and ignite it before I do that.  So my OS stays where it is for now - and therefore upgrading DNG is not on the radar.  But thank you for the suggestion that that is the source of the problem!

Link to post
Share on other sites
jerryy Grand Master

jerryy

Posted
Posted

If you are using a Mac, Affinity’s Develop module will open the .RAF files using your choice of either Apple’s raw engine or Affinity’s raw engine, which you can then export as a .TIFF or or as a .PSD file that Photoshop should open. I do not know how many raw engine choices the Windows Affinity version has.

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...