Zum Hauptinhalt gehen

please develop API for the Windows version of Capture One

Kommentare

4 Kommentare

  • FirstName LastName

    I would also like to know if C1 will be releasing the API for windows - functionality with Loupedeck etc is limited to shortcuts and can be very clunky/slow 

    0
  • Nathan Vergin

    I came here for the same reason.  The functionality within Capture One Pro for Windows is not optimal (primarily dials/scroll wheels) because of this limitation. Please release an API so that hardware developers such as Loupedeck can better integrate with your software within Windows. Doing so would help allow the hardware devices to have a more seamless integration with your software and further boost productivity.

    0
  • Okular

    Well, I would not call it horrible (using Loupedeck+ myself) but a native API is of course the better solution, since the shortcut workaround might be limited.

    0
  • Nathan Vergin

    @Okular, you are correct and I have edited my previous comment to roll my criticism back a bit and be more fair. The functionality isn't horrible across the board, but there are some controls (dials/wheels) that don't work as smoothly as I would like. I'm sure I could adapt over time, but I'm finding it problematic at the moment. Have you simply gotten used to the beaviors or found a better way to handle them? If you have any tips or suggestions, I'd be happy to learn from your experiences.

    For anyone else who may see this, single action button keypresses work as expected, I've had no issues there. For example, toggling an option on/off (like before/after) or entering a specific keyboard shortcut to perform a single action.  However, some controls such as dials or scroll wheels, need to rely on the entry of multiple keypress to make them work vs direct access to the underlying controls.  So instead of directly increasing/decreasing the value of an adjustment in one smooth action, as if you clicked a slider with the mouse and drag it back and forth, they need to register multiple keypresses for every +/- entered via the spin or turn of the control. This makes them less responsive and also results in an extensive history so you cannot simply undo the "overall" change like you may be used to because it registers every keypress increment from your starting point to where you ultimately ended up.

    0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.