Jump to content

dmaksan

Members
  • Posts

    10
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

dmaksan's Achievements

  1. @Superstition. Nice timelapses. For Holy grail day-to-night, I think we just have to work around it with one of these methods, until Sony releases a fix: 1) use an external intervalometer in A priority and hope it handles maximum exposure time you want (e.g. 10 seconds) 2) use built-in intervalometer before it gets to a certain darkness (the critical Exposure x ISO value of 8000), then switch to S priority (memorised beforehand with the right settings) together with an external intervalometer 3) As mentioned before, use exposure compensation +3, +4 and +5 progressively as it gets darker. This will be difficult to implement in field. 4) Buy an A1 and hope that Sony has fixed it in that model. Then get ready to mortgage the house
  2. I sent an email to Sony Australia (sony_supportps.au@ap.sony.com), and got this reply, which did not help. If more people complain, maybe Sony will do something about it. Trying their Web Chat might be the way to go:
  3. Great workaround! I tried it last night and setting Exposure Comp to +3 gives you 1 extra stop of exposure, and +5 (by using exposure setting rather than the dial) gives you 3 extra stops, which is good enough for dark milky way timelapses (f/2.8, 10s, ISO 6400). Although trying to implement this for day-to-night timelapses will be tricky, because will need to know when the camera hits the limit, then a few minutes later dial in exp comp +3, then again +4 and finally +5.
  4. This is a software bug which needs to be addressed via a firmware release. I have asked Sony Australia to pass this onto their software developers, but they didn't verify it was passed on.
  5. No, focal length doesn't make a difference. Tried 24-105mm lens @105mm, but still the same problem. If you leave the lens cap on and do an interval shoot, the first photo is correctly exposed, but all the rest are limited to the Shutter x ISO=8000 rule. Can't see a way around it unless using an external intervalometer.
  6. Hmmm, I wonder if the problem applies only to short focal lengths, although can't see why it would. I've been using 14mm or 24mm.
  7. The workaround, if you want to do day to night timelapses of dark skies, is to use an external intervalometer in Aperture priority for the whole thing. It will be more flickery, but something that will need to be cleaned up afterwards in LRTimelapse anyway. OR use the built-in intervalometer in Aperture priority mode until ISO/Shutter speed gets high (close to Shutter speed x ISO = 8000), then switch to Shutter priority (assign settings to a memory) and use an external intervalometer for the rest.
  8. Have contacted Sony, but their reply suggested trying a different AE Tracking sensitivity, which makes no difference. Boxhead Mike discusses this issue in the comments section of his YouTube video on "Day to Night Timelapses with Sony A7III" -> https://www.youtube.com/watch?v=LthqP0TQm88 Sort comments by Newest first and go down a couple of pages to comment by "Ralph Shieke" who is having the same problem.
  9. If I set it so that there is plenty of time between shots (in case the camera is busy writing/processing), it makes no difference, as does 30s between shots. Long Exposure Noise Reduction is off. First exposure is 13" @ ISO 12800, all subsequent exposures are 8" @ ISO 1000.
  10. Hi Everyone, I was hoping to do some really cool day-to-night timelapses or timelapses of the Milky Way at night using the built-in intervalometer ("interval shooting") that was introduced in firmware v3.0. However, I've come across a big problem with it, and wondered if anyone else has. The camera is not exposing near enough for a dark sky, leading to shots that are way too underexposed. It works OK for a relatively bright scene, such as city lights at night, but not dark skies. To demonstrate this, simply turn on the camera, leave the lens cap on, and start an Interval shoot (10s interval, Auto ISO 100-12800, Aperture priority, F4). The first picture in the series uses a shutter speed of 10 seconds at ISO 12800 (correctly, because it's the maximum exposure it can do based on our settings), but every picture after that uses a shutter speed of 0.6 seconds at ISO 12800. This doesn't make sense - it should be the same. If I lower the ISO value, it will use a longer shutter speed, but the overall exposure is the same - way too dark. Of course, when the lens cap is off, the same thing happens outside taking photos of the night sky. I have tried all sorts of settings - Program mode, a different lens with bigger aperture, different exposure modes, changed AE tracking sensitivity, but it doesn't make any difference. It seems like a limit was introduced where the shutter speed x ISO value is limited to 8000. People using firmware v3.0 don't seem to have this problem, but I am on v3.1 (the latest), and also had it with v3.01. Unfortunately you can't go back to a previous firmware to confirm.
×
×
  • Create New...