Jump to content

Recommended Posts

I've tried both of my X Pro2s' with the Fujifilm remote app and can't get either of them to work correctly. I've downloaded the app on my iPad 4 and iPhone 5c and get the same issue on both devices.

The camera connects as it should do and allows me to take one picture. The phone/iPad then displays 'Processing' and locks up. The app will allow the transfer of images already on the camera SD cards and will allow video to be recorded but will take no more than one still image. I've tried all combinations of JPEG size and memory card slots, both slots set to JPEG and have removed a reinstalled the app on both devices but no joy. The app works perfectly with my X30. Any ideas on what else I can try?

Link to post
Share on other sites

  • 2 months later...

I have the same issue. Sent Xpro 2 back twice to Fuji Australia for repairs and each time it came back with the same issue. Processing OK! error. Discussed this with Fuji reps, redid settings, swapped out cards, batteries, lens etc. Tried with different devices. Tried with other people's devices. Same issue. Finally the store that I purchased it from replaced the camera. Worked great. Then I updated the firmware from 1.01 to 1.02 and bingo the same Processing Ok error occurred. Upgraded to 2.01, same issue. Fuji seems to think it only applies to me, but hey, I now have gone through 2 Xpro 2 cameras and tried it on at least a dozen devices so I am sure its not me. I am sure its something from 1.01 to 1.02 that is causing the issue. I have been toing and froing with Fuji now for 4 months. All the Fuji Love, nearly gone. Love the camera but this issue is needling me in the back of my mind and I find that I am picking up my Nikon D610 more and more these days. In between eye-fi cards, the WU-1b and qDSLRDashboard app I can do pretty much what I want. (and what I want to do with the Xpro 2, but can't at the moment). I am hoping for a firmware fix one day.

Link to post
Share on other sites

  • 1 month later...

It works! I had the Perth Fuji guy come and visit me and together we went side by side to see what the difference was between his working Xpro2 and my "processing ok" Xpro2. A bit of this and a bit of that and finally the penny dropped! The camera rear screen MUST be in LCD (live view mode), not in the info screen that I always use. Just by habit, I have always placed the rear screen into info mode, even after countless camera resets. But today.. So problem solved - thank you Fuji. So,

1. Put the rear screen into LCD mode

2. Create the connection with your device

3. Camera Remote - shoot away!

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