Release Notes: Capture 2.1.8 (No longer supported)

Modified on Tue, 9 Aug, 2022 at 11:46 AM

Requirements

OS versions: 10.14 (Mojave), 10.15 (Catalina) 

Capture One Pro versions: 12 (Mojave), 20 (Catalina) 

Adobe CC versions: 2018 - 2021

Access to a ShotFlow “2.0” platform studio app

NOTE: If you are upgrading from ShotFlow Capture 2.0.x, please be aware that there are significant technical changes to ShotFlow Capture to support the new ShotFlow “2.0” platform, and this release is NOT backward compatible with ShotFlow “1.0” (QuickBase). 


Upgrade Procedure

  1. Download ShotFlow capture 2.1.8
  2. Extract the files from the ZIP archive
  3. Drag any older ShotFlow Capture release(s) to the trash
  4. Launch ShotFlow Capture 2.1.8 and log in

 

What’s New?

  • Automated notification that a newer release is available with built-in update support. When a newer release of ShotFlow Capture becomes available, the user will receive a pop-up notification that informs of the new release and the associated Release Notes, with the option to download and install the update from within ShotFlow Capture.
  • New custom metadata Adobe CEP panels support bulk metadata editing in Adobe Bridge. Now a user in Adobe Bridge can select many images that share a common ShotFlow custom XMP schema, and make a single update that is applied to all of them. This is perfect for applying a single Retouching Note to many images, or adding editorial metadata that was not auto-tagged at capture point.
  • Support for Adobe CC 2021. Both Photoshop and Bridge 2021 have been tested and passed as compatible with our latest CEP panels.

 

What Did We Fix?

  • Active Talent records not auto-linking to Shots. If the talent window is left open while selecting and shooting multiple shots, the active talent resource(s) were not being auto-linked to the shots.
  • 'Related Products' pane missing when adding or cloning Shots. When adding a new Shot to a Shot List locally (via either Add Shot or Clone Shot), the related products pane was not being displayed for the Shot.

  • Switching Sets did not always clear the user from the prior Set. The Set should now be available for log-in as soon as a user selects a new Set via the "Switch Set" menu option

  • Fixed a bug preventing Shots from being sorted by their Modified field. Some clients want the most recently modified Shots at the top of the Shot List (e.g. the ones most recently added to the Shot List). The Modified field for each Shot was not behaving properly when utilized for Shot sorting.
  • Invalid Sample barcodes scanned into the Accessories panel caused a crash. This was true of both truly invalid values (those that don't exist in the Shot List's brand app) as well as values that may exist in the brand app but were not shared with the studio app via a Shipment.
  • # character at the beginning or end of a Product field name may break visibility to those Product(s) in Related Products panel. 
  • / character in Capture - Subfolder - Naming Format field created unexpected subfolder. The "/" character was not being properly isolated and was causing a subfolder to be created when present in the data.
  • Several stability improvements.

 

Known Issues (Carried over from prior releases)

  • When adding multiple products or scanning multiple barcodes, if any are "invalid" (not located in the Samples table of the related brand app), there is no confirmation of those invalid products.

  • Sorting Shots in a Shot List by the Status field does not behave as expected.

  • If multiple versions of Capture One are installed on a single machine, ShotFlow Capture does not correctly store a preference for which to connect with, and continues to prompt for a selection at application launch

 

Future Enhancements

  • Preparing ShotFlow Capture 2.2 for client beta, including a completely new UI for “product centric” capture workflows, to supplement the current “shot centric” List View


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article