Zum Hauptinhalt gehen

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Exposure Bracketing, Focusing Stacking controlled by CO?

Kommentare

3 Kommentare

  • Paul Steunebrink
    Such a feature does not exist. Would be a nice addition, I think.
    0
  • Permanently deleted user
    I am actually really surprised Capture One doens't have this option of exposure bracketing (in version 12).
    Does anyone know if this is in the pipeline?
    Any recommendations to do this without the need for an Adobe programme?

    Thanks, Menno
    0
  • Eric Valk
    Thre are a number of similar use cases that involve manipulation of related sequential images

    • Panoramas

    • Focus Stacking

    • Incremental action overlays

    • Exposure Bracketting (which can be by Shutter Speed, Aperture or ISO)

    • Whitebalance Bracketting

    • Burst action sequences


    I've published several Applescripts to handle these, but they are hampered by the fact that only metadata of variants can be changed, not of images.

    If Capture One were to implelement some automatic feature to support these use cases, they would have to impllement an immense amount of detail fto handle many types of camera bodies. And then they likely will still be faced with dissapointed users asking that their use case or their new or old camera body be supportted.

    With so many variantions, trying to be all things to all people will be an expensive development, and expensive to maintain.

    I've asked Capture One to make the Sequence ID and Sequence related Image Metatdata fields user writeable (by Applescript, and by extension, by plugins). They said they would consider it.

    This would open the door to user and third party companies writing scripts and plugins to handle these uses cases, and one might for example buy a plugin for handling Panoramas with Nikon and Canon Cameras, or Exposure Bracketting with Olympus cameras.

    This would benefit Phase One as they would get a new Capture One feature set without having to do expensive development and maintenance, and also benefit users with a richer feature set that bwould likely be updated and changed more rapidly.
    0

Post ist für Kommentare geschlossen.