v1.8-beta83

v1.8-beta83 - 2019 July 12

• Nikon Silent Shooting now supported with new driver
• Nikon cameras in AF mode now use LV to avoid trigger AF during capture

v1.8-beta82

v1.8-beta82 - 2019 July 9

• Fix for an error with 3rd gen Sony and the new driver after a few thousand frames (due to a memory limit)
• Fix for Dx000-series Nikon support with the new driver, tested with the D5100
• Slight improvements to startup times (more to come after the new driver fully replaces libgphoto2)

v1.8-beta81

v1.8-beta81 - 2019 July 1

This is the final release before the July 2 eclipse. Make sure to test your setup: https://vimeo.com/345399867

• The tracking corrections on the app (in the motion/focus section) allow for smaller adjustments (0.1° now instead of just 0.5°)
• The tracking corrections on the app are now available immediately after starting rather than after it moved a little
• Liveview reliability improvements from the app for cameras using the new driver
• HDR improvements and fixes when using the new driver (new from beta80)

v1.8-beta79

v1.8-beta79 - 2019 June 27

• Fix for an occasional crash with older Sony cameras with the new driver
• Better focus position tracking with Nikon and the new driver
• Correction for Canon cameras not starting after a schedule auto-ramping time-lapse

v1.8-beta78

v1.8-beta78 - 2019 June 25

• Bugfixes (mostly with Nikon)
• Adding Nikon focus support to new driver -- most Nikon cameras are now supported

v1.8-beta77

v1.8-beta77 - 2019 June 21

• Fixed a bug causing an auto-ramping scheduled time-lapse to not start with some cameras
• Adding Nikon support to new driver -- most Nikon cameras are now supported and include native HDR support, focus support not compete yet but will be soon
• Fixed a bug with eclipse HDR setup from the app

v1.8-beta76

v1.8-beta76 - 2019 June 14

Note: this still needs more testing -- testing will continue over the weekend as weather permits

Known issue: on certain cameras, a scheduled time-lapse may not start. This will be corrected in the next release. This probably works in beta67 or earlier (not certain yet).

• Fixed a bug in the new driver (Sony and Fuji) that could cause shutter to get stuck at 30s
• Adding Nikon support to new driver -- so far the D3200 is added

v1.8-beta75

v1.8-beta75 - 2019 June 11

Preparing for the upcoming eclipse on July 2

• Updated app to include eclipse mode
• Fixed a bug causing manual location data not to be used after disabling GPS

v1.8-beta73

v1.8-beta73 - 2019 May 28

• Bug fix from beta70-72 for failure to change exposure for cameras using old driver

---

beta70 notes:

• NEW low-level driver for Sony Alpha and Fuji X, more cameras to be added in the future

The new driver has been in the works for a while, with the intent to be included in the next release after v1.8, but some Sony cameras were not performing as well with the more recent v1.8 beta releases, so it has been moved up to this release with partial camera support. For cameras not yet supported by the new driver, it will automatically use the old driver, LibGPhoto2.

To disable the new driver and only use the old one, go to Settings->Camera Driver. To see which driver your camera is using, connect it via USB and go to Information->Camera Info.

Performance is expected to be significantly improved with the new driver, and eventually it will fully replace LibGPhoto2 in the VIEW for all supported cameras.

Note: focus control and multi-camera support are not yet supported in the new driver, but will be added soon.

v1.8-beta68

v1.8-beta68 - 2019 May 1

• Corrects an issue where the VIEW may change the camera exposure upon connection

This bug was caused by a "feature" where if the camera is disconnected during a time-lapse, it will ensure the exposure is set the same again when it's reconnected. This is important for some cameras like Nikon, where the exposure will reset to what it was before it was connected, which would cause a problem during a time-lapse when changing the battery between frames. However, the original implementation would reset the exposure even if a time-lapse wasn't running. This is now fixed.