Jump to content

Copying images from camera/ Windows 11, no more MyFinePix


Recommended Posts

I have a new computer and as such no longer have MyFinePix Studio that I used and really liked for transferring files.  I would like to know how others are transferring images from camera to computer.  This link, https://digitalcamera-support-en.fujifilm.com/digitalcameraengpcdetail?aid=000005058&p=a062w0000035yOdAAI&wd=image+transfer&_ga=2.62903276.1570090719.1676656395-1876888618.1676656395

talks about how to do it with Windows 10 but I have Windows 11.  My old process was very simple, I'd connect the camera to the computer, start MyFinePix Studio and transfer the images to a well defined location (it would create the dated directory for me).  Now it seems harder, either remove the sd card, find my card reader, create a directory for the images and copy them from the sd card OR camera with the card in.

I would like to know what 'workflow' others are using and what suggestion people have for simplest possible transfer to well named directory.  I know this might not be a big deal for others, but the loss of MyFinePix transfer is an annoyance I've not yet resolved.

Link to post
Share on other sites

  • 2 weeks later...

Thanks Jerry, but still not so much.  I keep my uploaded photos in D:\CameraUploads.  I don't want to keep them under C:\Pictures (or whatever default it's using).  I don't use OneDrive.  I just want to get the photos from my camera to D:\CameraUploads\<date>\ which is exactly what MyFinePix used to do for me.  Now I have to either futz with the different folder on the card and create the date folder myself for each upload.  I am pretty frustrated with both Fuji (for not making legacy MyFinePix downloadable) and MS for not providing 'Photos' a simple way to change the default upload destination beyond C:\Pictures.  I don't need or want a OneDrive cloud eco system.  I have a special drive for unprocessed photos that I want to keep using.  Not every picture is worthy of cloud storage, they need to get reviewed and processed. 

I guess I'll have to keep doing it manually.

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

    • 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.)  
    • 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.
    • 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! 
×
×
  • Create New...