CO 22 integration with Loupedeck CT - dials inoperative
"What we've got here is a failure to communicate"
I've just started using the Loupedeck CT with Capture One 22 since the former has introduced an API-based profile for Capture One. However, for reasons as yet unknown to me the dials for the exposure tool functions (exposure, contrast, etc) and the High Dynamic range tool functions, as well as others (e.g., clarity, dehaze, levels) seem to be inoperative. Turning the dials sometimes reveals an up arrow or down arrow in the CT overlay, but no slider moves. The dials work in other applications (such as Lightroom classic and Photoshop).
I'm using the designated CT profile (Capture One default (CT)) and the keyboard shortcut profile (Loupedeck Default). A number of the CT actions fail to work as well (like assigning colour tags) - so I programmed my own shortcut key actions as a work around.
This may be something on the Loupedeck side of things, but has anyone with Loupedeck CT had similar issues, found solutions, or can offer suggestions? I'm wondering whether there might be something I've done in C1 that is causing the integration problem.
Cheers.
-
Hi Martin,
I am also using the Loupedeck CT with Capture One 22 and the same profiles as yourself. The dials are working with no issues found so far. The only issue I had was with the full screen button which did not work and if pressed too many times would cause Loupedeck to crash. I ended up replacing the function with the keyboard shortcut.
Not sure if this info helps but I am using a 2019 MacBook Pro, 16gb memory, Monterey 12.1 and Loupedeck version 5.0.3..
I hope you can resolve your issue.
0 -
works here too. sometimes you have to change the shortcuts, if you dont use an english keyboard and run your system with for example a german keyboard (different keys!)
0 -
Thanks for the replies.
I have discovered in conjunction with customer support at Loupedeck that the issues I am having using the Loupedeck CT with Capture One 22 are occurring with software version 5.0.3. Reverting to an older version, 5.0.1, resolved the issue. Loupedeck tell me that the issue should be resolved in the next update.
Martin
0
Please sign in to leave a comment.
Comments
3 comments