Jump to content

Recommended Posts

I used DxO when I had Pentax kit and the original X100, but moved to Capture One when I got the X-T4 with the X-Trans sensor. 

I still prefer the results of DxO, I feel that it's Clearview & Smart Lighting tools are far far superior to the only just introduced De-Haze tool on Capture One.  Overall, I feel DxO livens up an image a lot better than Capture One.

So, today I used Fuji X Raw Studio to convert RAW files into 16-bit TIFF files, which I was then able to edit in DxO and output to JPEG.

One issue is that the TIFF file is 155MB compared to the RAW 52MB, but assuming you don't want to edit the TIFF file again you can just delete it.

Has anyone else tried this out, and have you encountered any issues and problems???

Link to post
Share on other sites

The one thing to keep in mind is that X RAW Studio can only process files made with that specific type of camera. So, whenever you trade-in your X-T4 to a future 'X-T5', you can no longer process your X-T4 files in X RAW Studio connected to your new X-T5. For that reason you might want to hang on to your TIFF-files.

Link to post
Share on other sites

I use LR for minimal adjustments and mostly for the digital asset management.  I have over 250,000 images in LR right now.  However, I use Capture One Pro for 95% of all my editing needs.  My jpegs (from my GFX50r) are 40mb, and the TIFF's from raw are 310mb in size.  My XT files are much smaller.

I have folders set up in LR (which are actually on my desktop) where I drop files into.  Then I open C1Pro and sync that folder which I have set as a preset in C1Pro.  Once I'm done processing in C1, I export into another folder called "Roundtrip from C1Pro which is also a default in C1pro and in LR.  Back in LR, I then synch that folder and any jpegs and tiffs I generated are dropped in there.  I can then move the finished images to the library for cataloging, keywording etc.  Sounds complicated but I have it setup automatically and it works flawlessly for me.

Hope this helps.

Link to post
Share on other sites

On 10/5/2021 at 2:55 PM, jlmphotos said:

I use LR for minimal adjustments and mostly for the digital asset management.  I have over 250,000 images in LR right now.  However, I use Capture One Pro for 95% of all my editing needs.  My jpegs (from my GFX50r) are 40mb, and the TIFF's from raw are 310mb in size.  My XT files are much smaller.

I have folders set up in LR (which are actually on my desktop) where I drop files into.  Then I open C1Pro and sync that folder which I have set as a preset in C1Pro.  Once I'm done processing in C1, I export into another folder called "Roundtrip from C1Pro which is also a default in C1pro and in LR.  Back in LR, I then synch that folder and any jpegs and tiffs I generated are dropped in there.  I can then move the finished images to the library for cataloging, keywording etc.  Sounds complicated but I have it setup automatically and it works flawlessly for me.

Hope this helps.

This is interesting. Similar to you, I have close to 300K images cataloged in LR as I have yet to find a better database. I'm diligent about key-wording so I can find any image or shoot I need in a second or two.

I start my workflow in Photo Mechanic for a couple reasons: 1. It's super fast. 2. When key-wording and rating in PM, it writes to both the RAW and JPEG (I shoot raw+jpeg) which the LR import module does not do.

I plan to try a migration of my LR images to ON1 Photo Raw and C1 to see how they do. Based on others' experiences I sort of expect C1 to fail but in talking with ON1 I think Photo Raw should be able to handle it. The question is how it will perform once there are a few hundred thousand images cataloged. I'll post my results here once I do it.

So do you do your culling and rating in C1 along with the editing? And then move them to your "Roundtrip" folder for subsequent import/cataloging into LR?

Thanks for the input.

Happy shooting!
Joel

Link to post
Share on other sites

H Joel,

I do ALL my preliminary culling in LR first.  Quick pass through.  The ones I'm not sure about, I'll round-trip to C1 and then I'll edit them in C1.  I'll then bring them back to LR where I'll make a final determination as to the keepers.  I also keyword extensively as I sell enlargements, as well quite a bit of stock every year.

Thanks

J

Link to post
Share on other sites

  • 2 weeks later...
14 hours ago, Rene Theberge said:

DxO just announced that the new update announced a few days ago their new update will support X-trans files.

https://www.fujirumors.com/dxo-photolab-5-and-filmpack-6-released-with-support-for-fujifilm-x-trans-sensor-cameras/

Downloaded it last night.  Quick open shows it DOES handle my .RAF files quite well.  Now for the "Learning Curve".  :)

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
  • Similar Content

  • Posts

    • 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 😕  
    • 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  
    • Thanks for the insights. I think it's really hard to make a decision without having the two side by side! 
    • I don’t have the 23 f2 but I have read several times that it is considered a little soft at close distance, compared to the 23 f1.4 lenses. These will also focus at shorter distance from the subject, esp. the new one. So that might make a difference. The new 23 f1.4 LM WR  has better resolution, esp. in regard to the 40Mpix sensors, which you don’t have on the X-T2. What practical difference that makes for the value of the pictures one makes is disputable and subjective.  f1.4 will gather more light but with a smaller DOF, which may be desirable in some situations but not so in others, depends. If you like to shoot close ups, you will probably use higher f numbers to get a bigger DOF. Same for landscapes. If you are a bokeh fan, yes the f1.4 lens are better.  The older 23 f1.4 lens that you are considering is a very good and respected lens. The f1.4 vs f2 aperture per se is perhaps not so important. The 23 f2 is very small, light and practical and a great lens for travel and landscapes. So, go figure. I am afraid I just sent you further down the road to insanity !
    • First post here but long time fuji shorter. I use the XT2 with the 23mm f2 / 35mm 1.4 / 16-80mm f4 I'm considering the 23mm f1.4 r (Non-WR) About me: - I shoot black and white only. - I like macro details to wide open landscapes and everything in-between. - I shoot mostly for art, intrigue and creativity of the image. My question - is the 23mm f1.4 going to offer me any meaningful difference over the f2 for the above scenarios Thanks and sorry for bringing it up again...
×
×
  • Create New...