Jump to content

Recommended Posts

I'm a videographer. I have an internal and external micro configured in Manual -30db mode (low sensitivity).
Every time I turn on the X-H2s, the micro works in Automatic mode (image 1), ignoring the saved manual adjustment, being necessary to enter the volume adjustment menu (image 2), not changing anything, then exiting again to for Manual mode to work (image 3).

I compared two clips in an editing program (image 4), the first one on the left, I didn't go to the micro's menu. In the second, from the right, I went to the menu and came back.

It also happens with an external microphone. I have a extrenal wireless microphones and this manufacturer recommends reducing the camera input volume so that the sound does not clip.

Please, help me, because it's very annoying to have to change the menu every time I turn on the camera, a bigger problem if I forget.

 

 

 

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!

Edited by RuiBit
Link to post
Share on other sites

I already have the solution!! :)) Check it out!...

Until now I had the camera in these settings:

video mode:
Internal Mic Level Adjustment: -30dB
External Mic Level Adjustment: -30dB

Photo mode:
Internal Mic Level Adjustment: AUTO
External Mic Level Adjustment: AUTO

What did I modify?:

video mode:
Internal Mic Level Adjustment: -30dB
External Mic Level Adjustment: -30dB

Photo mode:
Internal Mic Level Adjustment: -30dB
External Mic Level Adjustment: -30dB

Easy Pisy

Now, when I turn on the X-H2s, the micro is immediately in Manual mode, in my case, with low sensitivity.

I hope this experience of mine helps you in a similar case! Well act everyone, and like this thread, THX

Link to post
Share on other sites

  • 4 months later...

Fantastic, RuiBit!

I have a similar problem: I always use the videocamera through the C1-C7 presets: I set the camera volume to the proper manual value for my ext mic and stored it in the Cx config; everything ok up to switching off.

Then, switching on, the camera went to -30 dB even if the menu value was the right one!

Simply by touching again the value in the menu, the volume set properly, up to the next switch off.

Thanks to your hint, I went in the Video position of the PASM wheel and discovered that the volume was set to -30 dB: every time the X-H2s was switched on, it gets these settings, not the settings of the Cx's!

Now I set the volumes of both the Video position and the Cx positions to the correct value and it goes fine!

It's a fault of Fujifilm: a FW debug is neccesary.

A big thanks to you!

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