Jump to content

dgbarar

Members
  • Posts

    38
  • Joined

  • Last visited

Posts posted by dgbarar

  1.  

    Why?  I have version 6 on my X-H2S that I use to video birds.The tracking AF for video in version 6 does not work any better than subject detect in the previous firmware.  In fact, I find it to be a PITA.  With my eye to eyecup I have to use the joystick to select the subject.  Version 6 still loses the tracked subject and goes OOF.  Why?  Because it is essentially the same autofocus algorithm that does not work well for subject detect.

    These folks have had years to perfect their phase detect autofocus and two years with the X-H2S.  But it is still the lack of video autofocus performance we have come to expect from FujiFilm.  Not certain why this is the case.  Is it lack of technical skill from the autofocus team?  If it is, then they should be terminated.  Maybe there are issues with X-Trans and this is the best they can do.  If that's the case this is a management issue.  All I can tell you is that Fuji is yet to figure out video autofocus.  At this time there should be no more excuses.

  2. Hi Gems:

    Skip the variable ND filters as they are basically polarizing filters.  It won't matter how much you pay, they will always end up looking bad.  If your clip is static and using a longer lens then you might be OK.  However, if you are using a wider lens and you pan, then the sky will vary in darkness as you pan--it looks awful.  In fact, you might even see the darkened band of polarized light running across the sky even if you don't pan with a wider lens.

    To the fairest,

    Eris

  3. Hi All:

    I am attempting to find a thin, screw in 67 mm VND filter for iPhone 15 Pro and Neewer rig that does not vignette the 13 mm lens.  This is what I have tried:

    • K&F 72 mm and 67 - 72 mm step up ring.  This has a thickness above threads of 12 mm and vignettes the 13 mm lens.
    • K&F 67 mm.  This has a thickness of 7.3 mm and vignettes the 13 mm lens.

    Any suggestions?   Irix produces a 2-5 stop VND that is only 4.7 mm thick.  Has anyone tried to see if it vignettes?

    Thank you in advance.

    Don Barar

  4. Hi All:

    I decided to bite the bullet and upgrade to firmware version 3.0.  I am delighted to report that communications with the RS2 did not change as a result of this firmware.

    As for for video auto focus, I took 8 clips at 60 FPS of ring tail doves against trees denuded of leaves.  Of these 8 clips, only 1 was out of focus.  Balance were sharp.

    I also took 4 clips at 120 FPS.  Three of them were of ring tail doves against the same denuded trees.  All three clips were in-focus.  The fourth clip was of grackle in the same de-nuded trees.  Because there was more contrast between the bird and trees I expected that this clip would remain in focus.  It did not.  That was a disappointment.

    More testing is required.  But my first impression was the video autofocus for version 3.0 is an improvement over 2.1.  However, FujiFilm still needs to continue to make improvements.  I look forward to the next update.

    Don

     

  5. Hi Django:

    I have seen some of these reports as well, but there are very few.  I own a X-H2S using version 2.1.  Bird subject detect works against uncomplicated backgrounds.  But, if there is a clear shot of a bird in a tree (think of bird in front of a tree), then subject detect is basically worthless.  I am reluctant to change firmware because with firmware 2.1 the X-H2S plays well with a DJI RS2 gimbal for no improvement.

    Has anyone tested X-H2S/Firmware 3.0 video autofocus using subject detect for birds with complicated backgrounds  Has Fuji made any subject detect autofocus improvements with version 3.0 for the above described situation?

    Don 

  6. Hi JoeRay,

    I own a 5D Mark II.  This camera came with an application called EOS utility.  I used this application along with functionality built into the camera to calibrate each lens for focus.

    You might want to consider investigating whether-or-not the R5 has the same functionality of calibrating you lenses.

    Don

  7. Hi All:

    I recently updated the firmware in my X-T3 to version 4.00.   Since making this update I have had issues with the camera in video mode.  Camera becomes un-responsive, LCD froze, and was unable to turn off camera--had to remove the battery.

    Anyone else experience this on their X-T3 with an upgrade to firmware version 4.00.

    Don Barar

  8. Hi Aquias,

    I know that you are considering a wireless system.  I have a Sennheiser G4.  Works well, but on are occasions there are issues with electronic interference that prevents you from finding a band to sync the transmitter and receiver.  I am assuming the Sony would have similar issues.

    Recently I have transitioned to wireless belt packs.  TentacleSync manufactures their Track E which is 32 bit unit with a lavaliere microphone.  These are $350US/unit.  A couple of these and the Tentacle Sync E connected to the camera would be about $950 US.  More expensive than a wireless system, but much more convenient to use and no interference.

    Don Barar

  9. Hi All,

    I just received a TentacleSync Track E audio recorder.  On occasion, I have a need to shoot video with an iPhone.  There is a mobile telephone app called RecVideo that supposedly picks up the time code from the Track E audio recorder.  Has anyone used this application?  What are your thoughts?

    Don Barar

  10. Hi All,

    I am considering purchasing a Ronin SC2 with RavenEye and have the following question.  In know that I need my mobile telephone to launch the DJI application and Active Track.  One I establish an object that I want to track does the mobile telephone still have to on.  I ask, because once I have started Active Track I would like to turn off the telephone to conserve battery.

    With my correct Ronin SC using Active Track it rapidly drains the battery on the mobile telephone.

    Thank you in advance.

    Don Barar

  11. Hi Xavier:

    Thank you for pointing this out as a possibility.  I was unaware of the possibilities of mis-match between full levels for 8 bit.  Why would applications make this change?  What applications are you aware of that do this?  Do they have a way to toggle on/off?

    BTW.  The examples captured in 10 bit.

    Don

  12. HI Majkel:

    The solution is to transcode to Prores 422 in FCPX.  This is how I do it.  When you import your files, allow FCPX to generate optimized files.  Optimized files are a Prores 422 transcode.  Do your editing.  Then when you complete your project, delete the optimized files to conserve storage space.

    For some reason Compressor is not properly transcoding to Prores 422 and with my X-T3 exposure was being added..  However, optimized files in FCPX do not have this problem.  I have written to Apple on their bug reporting and they have never responded.

    If you are an FCPX user, this is a far better process than first transcoding to Prores using Compressor or any other transcoding software.  Why? because when you are done with your project you do not have large Prores files to store.

    Hope this helps.

    Don Barar

  13. This might be a little off topic and it may or may not help others using FCPX.   Never transcode your H265 files to Proress 422 before importing into FCPX.  Allow, FCPX to generate optimized files upon importing.  The optimized files are ProRes 422.  Do your editing.  Once you have completed your project, delete the optimized media and you will be left with a smaller project file that only has the H265 media.  If you ever need to edit your project, allow FCPX to again generate the optimized media.

    Hope this might be of help to others.

    Don

  14. Hi Jay,

    Thank you for performing these additional tests.  Hmmm.  I am beginning wonder if this is a Fuji bug or if companies not properly updating their software to properly handle 10 bit HEVC.

    Any one out there with a camera brand other than Fuji that can test 10 bit HEVC to see if when transcoding to Prores 422 there is shift up in the RGB parade?

    Don Barar

  15. Hi Jay,

    Thanks for writing.

    I am using MacOS 10.15.6 Catalina on a late 2016 MBP15.  That is what I found with Video Pass Through.  It leaves the video untouched and does not transcode to Prores 422--even through it still names the file Prores 422.

    However, the main issue remains as to why Compressor shifts the RGB parade up for when transcoding to Prores 422 from .h265, 10 bit, 420 files.

    As an experiment, I tried transcoding to Prores 422 the same .h265, 10 bit, 420 file using Adobe Media Encoder.  It seems to process the files just fine without shifting the RGB parade up.

    I am at a loss as to what to do other than file a bug report with Apple.

    Don

     

×
×
  • Create New...