Jump to content

Recommended Posts

I have been trying to shoot gokarts at our local track with the xt2, battery pack and a 50-140 zoom.

Shutter speeds between 1/1000 and 1/3000 to freeze the karts, apertures f2.8 and f4.

The custom focus was set to 3 which shows a gokart in the setup, should be ideal I thought.

Focussing was done using back button afc focus, held in all the time I was tracking the karts, I also tried assigning afc to the shutter button. Just for consistency I left the focus bracket in the centre of the image and used the two smallest squares to track the karts.

 

The results were a disaster, the focus was never where I wanted it, I shot at 11 fps to try that also, when I pressed the shutter on the lead kart coming towards me, it was not sharp but the 4th or 5th kart behind was reasonably sharp,

 

There is no problem with the outfit as the static shots I took are pin sharp as they should be.

 

Any ideas anyone?

Link to post
Share on other sites

Afraid not, I deleted them in disgust.

 

In its simplest form, where I had 3 or 4 karts coming towards me, having tracked the first kart, it was the third or fourth kart that was the sharpest, sometimes the focus was too close to me and none of the Karts were sharp.

I deliberately used the centre single point for focus and kept the kart in the centre of the viewfinder to the best of my ability.

 

I was so disappointed because I used the centre focus point in afc mode on some static shots and they were pin sharp.

 

I shall have to go out on the street and test this setup with oncoming cars.

Link to post
Share on other sites

I may have found the partial answer to my problem,

Apparently if you shoot at greater than 5 fps you will have a lag in the viewfinder,

So with me shooting at 11fps what I see in the evf whilst I am tracking a fast gokart is the lastt frame exposed, not the current view.

Therefore I am tracking the subject based on the last exposed view of the sequence, meanwhile the subject has moved quite some distance suffucient to render it soft or out of focus.

 

The only thing I can not apply this solution to, is why the first frame of each sequence is not sharp?

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