API-level support for the Loupedeck CT
Implemented
May I ask for the Loupedeck CT to be supported at the API level?
Currently one can use the Loupedeck CT in combination with C1 via keyboard shortcuts but I understand that an integration via C1's respective API could increase performance, avoid issues with input focus, and/or unlock opportunities that currently don't exist.
The C1 FAQ suggests to reach "out to Loupedeck support as the integration is wholly developed by their team", however I wonder whether Loupedeck has access to the API and its documentation.
If the latter is the case, I'd very much appreciate a confirmation.
If it isn't the case then my feature request is to make the API available to Loupedeck.
N.B., consoles currently compatible with C1 at the API level unfortunately do not have the right form factor. I cannot consider their use, regardless of the price point.
-
It would be very useful and incredible to enable full MIDI support via API, plugins like Adobe Lightroom and not only via translators of MIDI commands to keyboard shortcuts. For example, when I used Lightroom, my workflow contained MIDI controller Behringer X-Touch with motorized faders something like this one: https://www.youtube.com/watch?v=VFCWoEIgU5Y I don't like Tangent controllers very much and I want to continue working with Behringer X-Touch and utilize motorized faders.
2 -
Loupedeck has no access to the API (yet). They claim to be in discussion with C1, but give no sign of reaching an agreement.
That, and Loupedeck's inability to support other keyboards than QWERTY (which casues a problem as they use the keyboard combination functions in C1 just now) made me return the LoupeDeck+ console.
1 -
Hi there,
Than you for your comments.
We have similar requests on the official Loupedeck support in Capture One.
Whilst we cannot comment on future releases, we take all suggestions on board and hopefully your feedback contributes towards a future version of Capture One.
1 -
Hello,
I too would love full API-based Loupedeck integration in C1 Pro. Currently I use a Tangent device for C1, which works seamlessly and easily. Only problem is that it doesn't play as nicely with Photoshop, IMO. Loupedeck is practically built for PS. I would love one device that functions to the BEST of its capabilities in both worlds so my desk isn't cluttered with single-application/eco-system hardware. If the problem is licensing fees, I hope the parties can come to some agreement for the good of the end user. Isn't the end user what all this is about?
Thanks.
-Doug
4 -
Now with the rise of C1 21, I see that the C1 team really has an eye on efficient editing. For some that might be shortcuts, for others, it is a dedicated console. I hoped then C1 released the support for plugins that this open-minded attitude would spread on other parts of the software. It would be great to see such innovative companies like C1 and Loupedeck join forces and collaborate for more freedom of choice for creatives like us.
2 -
A strong LOUPEDECK CT integration with C1 will lead to better sales of C1.
0 -
Also a vote from me for LOUPEDECK CT integration with C1.
It would be very nice to speed up the workflow with this device and not only with hotkeys from CO21.1 -
I sincerely think we can forget about it.
It has been a couple of years since this feature was requested, and that even LoupeDeck claims to have asked access to C1P's API, but as almost all requests detailed in this forum, none is taken into account and implemented by C1.
Don't ask why - that's just how it is.
1 -
I see this has been an issue for a while (years), but I just bought Capture One after seeing an excellent demo at a trade show, assured that it would work with Loupedeck. Only minimal keyboard shortcuts work, and there's STILL no API support? Is this a C1 refusal to release API info, or Loupedeck's failure to implement it? I'm starting to think I've wasted a lot of money...
0 -
As to where the delay/refusal is, Loupdeck posted three months ago:
It seems unlikely to me that they would pretend that they have not been given access to C1's API, if it weren't true that only Tangent (and any others in the meantime?) were privy to C1's API.
Personally, I find it unfortunate that Capture One heavily invests into second level functionality like HDR and panoramas, and puts a huge effort into developing a mobile version which will only be available on Apple hardware, while core functionality is neglected.
I understand that it is important to pursue strategic directions to maintain/increase the revenue, but I find it very unfortunate that it comes at the expense of getting the basics right. I have a long laundry list of small little things that are broken/suboptimal in C1 which, if fixed, would make working with C1 a lot better.
I consider console support to be a pretty basic aspect of a professional editing software, Capture One agree that the "Loupedeck + / Loupedeck CT is a popular editing console", and there have been numerous requests by users. So why is there still no support?
In this instance, it seems like Capture One would not even have to do one bit of coding. They would just have to make the API documentation available to Loupedeck who would then do the actual work.
It is frustrating not knowing why no progress has been made all these years.
@FirstName LastName
Which Loupedeck console are you expecting to work with C1?
The models vary regarding their flexibility to adapt to C1.
The Loupedeck CT/Live are the most flexible and while they still only offer keyboard shortcut based customisation, which is not optimal in all regards, they can be very powerful C1 companions.
Loupedeck managed to squash the bug which sometimes dropped keyboard shortcut modifiers and thus had made the device unusable for C1, and migrated from a network-based to a USB-based communication, which addresses past issues, e.g., when using VPNs. Making it easy to use custom icons for actions with a rather useful library of icons to pick from has also been a positive development.
The new configuration UI by Loupedeck is also quite good and I'm closer than ever to finally evaluating whether moving from my Contour ShuttlePro V2 to the Loupedeck CT will be an improvement. Loupedeck are not helping by still not supporting toggle/cycle macros and refusing to make the "Enter" key customisable, but overall, I'd say one should be able to get a lot out of a Loupedeck CT/Live for C1, despite the lack of API support.
0
投稿コメントは受け付けていません。
コメント
10件のコメント