Unleashed 22 - known bugs

[Oliver]

This Post will be updated regularly, to let you know of Bugs that we have found, or that have been reported, which we are already working on fixing.

Current Firmware: A3.2.1 B3.2.1 C3.1.0
Current iOS App: 3.1.0
Current Android App: 3.1.0

Canon

• [Fixed in FW 3.0.1]Geotagging does not work on some newer Canon Cameras, like the R5
  - fixed

• [Fixed in FW 3.0.1]"Unleashed is initialising" message does not go away on the R5 and other newer Canons
  - On an R5 with a 512 GB CF Express card, this message always showed up. Without the card, it worked fine. It turns out that we were too quick trying to establish a USB connection. We fixed the issue.

• [Fixed in FW 3.0.1] R5 and similar: Image review for RAW only shows option "S" (small) for RAW images, and these don't work
  - Canon made changes in the CR3 Raw format - we'll update our parser

• [Fixed in FW 3.0.1] R5 and similar: Image review for JPG "L" (Large) transmits a small image on Android phones
  - Small bug in our Android app - fixed but not yet released

• [Fixed in FW 3.0.1] R5 and similar: when using a card in the second slot only, no images are shown in the Gallery
  - Canon responds with 0 photos on when we request all photos from all cards. We'll need to ask for each card separately

Nikon

• [Fixed in FW 3.0.1] Geotagging didn't work when turning on the camera while the app was in the background

• [Fixed in FW 3.1.1] Nikon Z f, Z fc and others that only work with the Unleashed M, would have its disk access LED blink green, and have the battery drained when the camera was turned off
  - We attempted a fix, but just missed the mark, will fix in next update (3.0.3 or 3.1.0)

• [Added in FW 3.1.1] Nikon Z f, Z fc and others that only work with the Unleashed M, don't support geotagging.
  - We did not mean to promise this feature, but with the addition of the Z f, the list of cameras without an accessory terminal seems to be expanding, so we will implement Geotagging via BLE.
  - We implemented it, and it works, but will still be improved: viewtopic.php?p=5197#p5197

Sony:

• [Fixed in FW 3.0.1] Holy grail does not ramp any settings
  Fixed -> Thumbnails cannot not be retrieved via the usual command so luminance was not parsed. Implemented ramping based on the embedded JPEG thumbnail in the original image. Also camera settings cannot be changed that fast, added a delay for that.

• [Fixed in FW 3.0.1] Taking images in quick succession or with RAW+JPEG quality setting or with a slow SD card does not display a preview reliably
  Fixed -> Images will now be dequeued from the cameras internal RAM one by one and produce a preview each. Also increased internal timeouts.

• [Fixed in FW 3.0.1] Older cameras (e.g. a7Riii) crash after triggering with quality set to RAW. Preview options have duplicate 'L' item.
  Reproduced, still looking for a fix -> Attempt to retrieve or delete the buffered image in RAM results in the camera shutting down unexpectedly. Replaced 'L' option by 'XL' option.

• [Fixed in iOS App 3.1.0]Only one image preview is visible in the app. New preview is only shown if preview was cleared manually.
  Because the images are fetched from RAM buffer, they do not have unique IDs so the app merged them with the previous image.

Fuji

• [Fixed in FW 3.0.1] Some newer cameras show a red/green blinking LED and don't allow taking more pictures or turning off the camera
  - Fuji waits for the USB host to download then delete the photos from the camera's RAM when triggered via USB. We already do that, but it seems that under certain circumstances, we miss the information that there are new photos in RAM. We'll check manually every few seconds to avoid this error

• [Fixed in FW 3.1.2] X-T5 and X-H2(s) cameras still show a red/green blinking LED and don't allow taking more pictures or turning off the camera
  - Fuji changed the Release status values in the latest generation of Fujifilm cameras, so we were waiting for a value we'd never get, stalling the state machine for Fuji triggering.

• [Fixed in FW 3.1.2] X-T1 cameras would not trigger correctly
  - Similar to previous issue, X-T1 sends slightly different Release values to all the other Cameras (probably the reason it was dropped from the official SDK supported camera list!

• [Fixed in FW 3.1.3]Fuji X-S10 still behaves weirdly.
  - Fuji only added USB tethering support for this camera in a firmware update, and it seems to behave differently from all the other Fuji cameras.
  See explanation here: viewtopic.php?f=13&t=1918

• X-T5 has issues with Image Review, Gallery and Holy Grail Algorithms
  - We found a bug in the Fuji X-T5 Firmware - for no apparent reason, this one camera no longer supports a command that we heavily rely on for these features, which allows us to get a few bytes of an image at a time, rather than the entire image. We already have some ideas and are implementing a workaround for this problem, and hope to convince Fuji to add the command in a firmware update.

Panasonic

• [Fixed in FW 3.0.3] Metering Area icons do not match what camera shows
  - Indeed, though we prepared the correct icons in a table for Panasonic, we used the wrong table in our code.

• [Fixed in FW 3.0.3] GH5 shutterspeed greys out with values above 1s. Similar behaviour with some Apertures
  - In a remote debugging session with a customer, we found a bug in Panasonic's firmware that would explicitly tell us a setting is currently invalid, and not available, in the main USB command we use for settings. But luckily there's a second command to get just the current value, and this does not have the bug. So we now ignore the invalid current value from the main command, and the Unleashed will then still have the (real) current value from the other command.

iOS

• [Fixed in App 3.1.0]Last error message keeps being displayed until you tap another setting or go to another screen
  - We already found and fixed the issue, will be released with the next app update

Android

• [Fixed in App 3.0.4]Turning on Geotagging on Android 14 crashes the app
  - Fixed

• [Fixed in App 3.0.4]Trying a firmware update on Android 14 crashes the app
  - Fixed

• [Fixed in App 3.0.4]Storage permission request that can't be granted
  - Fixed

• [Fixed in App 3.0.4]Requesting Preview image size L in many cases resulted in size S being transmitted
  - We already found and fixed the issue, will be released with the next app update

• [Fixed in App 3.0.4]In Gallery, downloading larger sizes would download correctly, but only size S would be displayed
  - We already found and fixed the issue, will be released with the next app update

• [Fixed in App 3.1.0]In Holy Grail, after starting, Errors are shown about Ramping order and Ramp mode being not available while an intervalometer is running
  - This is not a bug, as it is correct that you can't change those two settings, but they shouldn't be displayed at all in this case and make it look like there's a major problem, when there isn't

• Sometimes, after the upgrade to 3.1.0, the timelapse arrows might be in a weird state that shouldn't be allowed.
  - This only happens if you had changed these to a specific value before updating, and the new version loaded this previously set value, but interpreted it differently. This is already fixed in the next update, but if you encounter it, simply change both arrows to another value, then back to what you want, and it will be solved.