Jump to content

Recommended Posts

Lonelyspeck.com said its not so good, but i dont think he really tested it.

I have it but have not tried astro yet. Fujifilm says it good for lowlight due to OIS, but you dont use that when astroshooting for 20 sec or so.

So i might report back on next clear night ;-)

 

Sent from my Nexus 6 mobile

Link to post
Share on other sites

The OIS is only usable for handheld shots, you don't need it for tripod shots. The 10-24 is allright for astrophotography but has a bit of coma (stretched stars at the edge of frame) and the f/4.0 doesn't really help. If you want a great astrophotography lens for a low price try the Samyang 12mm f/2.0 (also known as Rokinon or Walimex) which has almost no coma, chromatic aberration and a brighter aperture. 

Link to post
Share on other sites

I think on the Pro2 and T2, the extra stop of ISO to noise performance compared to the T1 helps bail you out a little bit on the f/4 aperture, but my go-to lens for astro among Fuji branded lenses remains the 23mm f/1.4. I own the 10-24mm, but haven't really tried it because I've been very happy with the 23mm for my purposes. If I were to go wider and start shooting more astro photos, I would almost certainly just buy a Samyang specifically for it given the low price.

Link to post
Share on other sites

Thanks everyone for your reply.  I have considered the Rokinon 12mm but am trying to carry less, not more.  That and the weight limit on cabin baggage for the trip limits what I can take.  (one of the reasons I switched to Fuji - much lighter than my Nikon gear!)  I have the XT-1 so I am not sure that in combo with the 10-24 would work as Nero points out.

Link to post
Share on other sites

Thanks everyone for your reply.  I have considered the Rokinon 12mm but am trying to carry less, not more.  That and the weight limit on cabin baggage for the trip limits what I can take.  (one of the reasons I switched to Fuji - much lighter than my Nikon gear!)  I have the XT-1 so I am not sure that in combo with the 10-24 would work as Nero points out.

The 12 is pretty small if that helps.

Link to post
Share on other sites

Thanks everyone for your reply.  I have considered the Rokinon 12mm but am trying to carry less, not more.  That and the weight limit on cabin baggage for the trip limits what I can take.  (one of the reasons I switched to Fuji - much lighter than my Nikon gear!)  I have the XT-1 so I am not sure that in combo with the 10-24 would work as Nero points out.

Then we can't help you ;)  The 10-24 isn't ideal but you'll definitely be able to take some nice shots in dark environments. It's up to you if you thin the extra lens is worth the money/weight. You could also consider the 12mm instead of the 10-24, it depends on how much wide angle you shoot. The lens is fairly easy to use without AF, but if you use it a lot you might miss it. Image quality wise the 12mm is great.

Link to post
Share on other sites

I have used the 10-24 for night sky photography quite a lot. Setting the camera to f4, ISO 3200 and 20s exposure gives you reliable results.

 

Admittedly, there is some minor distortion at the extreme edges, but if this is a problem, that can be cropped out.

 

I am also using a Samyang 8mm fisheye on night shoots. Similar settings, but you may need to keep the centre on the horizon level to avoid severe distortion. This may require some heavy cropping at the bottom. However, the angle is wide enough to still give you a very impressive sky.

Link to post
Share on other sites

  • 2 weeks later...

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