Jump to content

Strange behaviour on X-H1 when filming slo-mo HELP!

WillsM
 Share

Recommended Posts

WillsM Newbie

WillsM

Posted
Posted

Hey guys / gals,

First post on here.

I've had an x-h1 for a couple of years and it has been an amazing camera.

I recently started using its video functions, specifically the high speed 120fps functionality. Blown away by its crisp video.

So I decided I wanted an external monitor, to make things a bit easier. I got hold hold of a smallHD focus 5" monitor, runs off the HDMI output and has its own power source.

So everything was okay. The monitor is great. I have found a really odd bug though and I am wondering if anyone else might have come across this and has any thoughts / solutions.

High speed shooting has  number of different modes, some at 120p, some at 100p. When I connect the monitor and select "EVF" only view using the display button on the right side of the viewfinder, then start recording at a mode which uses 120p, after about 9 - 20 seconds I get an error thrown in the display screen, showing "write error".

So if I connect a different monitor through the hdmi out, the problem is still there, so i know it is not the monitor that is the issue.

If I do not connect the external monitor, the problem never occurs.

I have raised a support ticket with fujifim, and they are looking into it, however I was wondering if anyone else has experienced issues like this? I am using 2 UHS 3 sony memory cards, brand new. Also have swapped them around in the slots. Run a health check on them also. I do not believe it to be a memory card issue at this time.

What is strange is that there seem to be 3 variables at play:

1. The output 120/100p in the high speed recording mode

2. The display mode being set to "EVF only".

3. An external monitor being plugged in

The reason I am setting the mode to EVF only, is to stop the camera from outputting the live picture to the LCD screen when I am filming. I am doing this to conserve battery life on the camera.

So it would seem that "EVF" mode + 120fps + an external montior = write error to the SD card. When the error occurs, the recording quits and this keeps happening unless I switch the mode to use the LCD screen OR i switch the mode to 100p OR i disconnect the external monitor! Bonkers right?!?!?!?!

Anyone had similar issues? Could it be the write speed on my SD cards? I am using sony M UHS 3 write speed 100MB/s, so can't see them underperfoming!

HELP!! I's doing my head in!

 

 

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