supporting tethering for non supporter camera/camera manufacturer

François Léger

• October 24, 2023 08:46

I fully understand you can't support all cameras nor camera manufacturers. I am an Olympus camera owner and OMDS ( as well as olympus previously) provide a tethering solution that fits my needs.

It is possible to set the output directory of the third party tethering software match the capture folder of the CaptureOne catalog/session physical directory. However, this will still miss some of the functionalities provided in the standard tethering toolset from CaptureOne (namely: next capture naming, next capture location, next capture adjustments and Overlay) that are all independant of the camera tethering support of CaptureOne (my cameras are all supported by CaptureOne, but not for tethering).

Can't you add to the camera selection pane on the toolset a 'temporary transfer directory' choice when no camera is available that can serve the role of the camera transfer protocol, allowing the rest of the tethering import manipulation to take place for such unsupported camera model/manufacturer?

This would allows the rest of the tethering input process to work, even for such camera ?

Thanks,

François Léger

1

• 

  Marcin Mrzygłocki

  • October 24, 2023 11:49

  

  I think that a good idea would be to include the versions of Capture One the feature is missing, it might have been either added later or started suffering regression bugs.

  0
• 

  François Léger

  • October 24, 2023 18:39

  There is no direct relation with the version of Capture One, while this request will be more concerning with the future release as the style processing become more and more efficient.

  The issue of tethering import is not the issue here, what is the issue is the extra processing available if the camera is supported versus if it isn't.

  Automated import with external tethering is available since, at least version 5 of Capture One (as far as i remember, i don't know for the previous version as i never bought them then.)

  What is at stake here is the import naming choice, the styles and other metadata information management that can be manipulated during the tethering import but not during injection using the capture folder (or the Hot folder in case of a catalog). Changing the appropriate fields in the import tool or the tethering toolset does have any effect in the photo inserted using such 'hot folder' processing.

  Using an intermediate folder could allows the tethering tool set to process the image metadata and style processing as if it was produce from an USB or WIFI connection, while copying the image to the capture repository, an action distinct from adding a picture in the capture repository directly.

  I hope this is more understandable.

  François

   

  1

Post is closed for comments.