Jump to content

Recommended Posts

When external mic is plugged in (Sennheiser AVX MKE2) the booster grip, camera switches to external audio.

When monitoring the incoming audio (with the right levelling) I notice some heavy distortion in the headphone audio, even when audio is nicely levelled. (sounds like clipped audio)

 

When importing the clips into Avid, the audio is not clipped at all and of good quality.

 

So, or I have a bad booster grip or this is a firmware issue. A review on Digital Trends (https://www.digitaltrends.com/digital-camera-reviews/fujifilm-x-h1-review/) mentioned it before...

 

Is someone else having this issue? I have the latest firmware installed and Fuji is not mentioning this issue.

 

 

 

 

Link to post
Share on other sites

  • 2 months later...

I have the same problem too, and I was one of the early birds in my country.

Audio sounds "dirty" with almost static like distortions. I believe the guy from cinema 5d experienced the same problem too.

I have contacted Fuji Singapore about this and sadly the higher HQ denies this being a problem with our grips. Instead they claim that because they have tested it on their end with mic from Sennheiser and rode to clean results, the problem lies with my audio equipment.

It's highly disappointing.

Link to post
Share on other sites

  • 3 weeks later...

First, ensure that your internal mic is disabled. 

Second, this seemingly is a known issue across not just this board but many others as well. You're not alone. Unfortunately (and in my case, anyway), in addition to what sounds (but actually is not) clipping when monitoring through the grip, I've noticed that there's a background hiss from the internal pre's even when switching internal mics off. It's *better* than leaving them enabled, but marginally. The best bet is to use an external recorder, it would seem.

Best of luck to everyone. I'm in the same boat. Hopefully a FW update clears this up.

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