Jump to content

Recommended Posts

In addition to the X100V being a handy camera, I have encountered a strange problem several times: I have taken a lot of pictures and put the memory card in the computer but do not get all the pictures. About 80% - maybe -  and I see them ALL in the display on the camera but in the file manager in Windows (or Linux / Mac) I only get to a certain number and then it's over. However, if I connect the camera to the computer via USB cable, ALL image files are visible and can be transferred.

Has anyone encountered this and if so, what to do? FujiSupport has no answer to this question.

The memory cards are of the best quality Sandisk Extreme Pro 170 MB / s SDXC V30 I U3 C10 and work perfectly normally in my cameras such as Sony a6300 where no such problems are shown at all.

Link to post
Share on other sites

I only encountered this when the camera split the images between TWO or more folders.  Since I use Lightroom, when I select to upload from a memory card all I have to do is select the "UNTITLED" (as the memory card is never named), and select ALL FOLDERS.  If you are on a pc using the file system i wonder if you try Adobe Camera Raw (it's free) and try uploading there.  I can't imaging that Adobe Camera Raw is not available for a Windows machine.  Not sure if I've helped but please let us know.

I do remember a ways back where not all my image would show up because the computer was only looking at one specific folder and the images were split into two as I had reached the 9999 limit on one folder - so the camera created another folder.  

Does the X100V have two card slots?  If it does, maybe some of the images rolled over to the second card?  Just thinking out loud here to try and help you.

Good Luck!

 

Link to post
Share on other sites

There is a problem with MacOS (and probably some versions of Linux) where the computer won't read over 4096 files from an SD Card formatted as exFAT (from a Fujifilm camera).

IS the card over 32GB (i.e. formatted as exFAT)?

Do you have over 4096 files (raw + jpeg counts as two files)?

If you have access to a Mac try opening the card in Finder and click on one of the JPEGs to bring up Preview.

Now check and see if you have access to all the files. 

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