C1 20 and Loupedeck+
Jonathan
-
me too 0 -
Yeah, that's unfortunately true for me too. Just a few sliders work if you enter their shortcuts directly on the keyboard but none of the knobs on the Loupedeck device seem to work.
Loupedeck has released a new version v3.02 of its software at the same time as Phase One published C1 v20. I'm not sure if that was the reaction with appropriate adjustments ... But if I look on the long list of posts in the MAC subforum I tend to claim C1 as the cause of the problem. As more as Windows is my main system and here the Loupedeck+ is working flawless.0 -
Quote from Loupedeck received 9 Dec. 2020:
"We will extend the beta support for Capture One 20 in our upcoming software release which will most likely be released sometime next week."
Hope the wait is not too long 😊0 -
There's a new version 3.1 of the Loupedeck software for download since today and with that version the Loupedeck device works under MacOS. Though the in the release notes announced support for the new HDR tools Black and White doesn't work, neither on Windows nor Mac. 0 -
Are you perhaps on an AZERTY keyboard ?
There are still plenty of AZERTY/QWERTY keyboards (like "undo" will "close the window" if you are on AZERTY).
And some things that I cannot understand:
Why was D2 assigned to Brightness in driver v3, but disappeared in 3.0.2 (and above).
LoupeDeck+ is a nice product, but they really need to improved their driver support.
At the very least fix the Keyboard layout conflicts - one nice guy at the support promised it "some moment before the end of the year", so no hop is yet lost (even if I would have loved to see it in the 3.1 release)
PS: on an MacPro 5.1 running Mojave 10.14.60 -
No, my systems are German with a QWERTZ keyboard and all Loupedeck hotkeys for me also work on the normal keyboard. I don't think this is an issue with the keyboard layout, rather it is other applications on the computer that use the same keyboard shortcuts.
On my Windows PC this caused a conflict with the AMD Radeon software. Here the clarity control only went into the negative range. By coincidence I found the combination for positive clarity values ​​was used by a performance log in the Radeon software. After changing that to a new fantasy combination, the clarity control on the Loupedeck device worked immediately.Claude-1300 wrote:
Why was D2 assigned to Brightness in driver v3, but disappeared in 3.0.2 (and above).
I can't confirm that, on my Windows PC and as well the Mac D2 changes the brightness since v3.02, I did not use prior versions.
Well, Loupedeck clearly says that Capture One support is still beta. In my opinion this is less due to Loupedeck than up to Phase One. Seems they do not offer a reasonable API for their product and so far only gave Tangent direct access to the Capture One functions, while Loupedeck has to go the workaround via hotkeys. So this way restrictions are to be expected unfortunately.
I sent a request about to Phase One support a few days ago, the answer was sobering:
"All I can do is forward your comments on to our product management team. We cannot comment on future plans for the software.
It's also worth getting in touch with Loupedeck about this as it is a two way street when it comes to hardware integration."
But from a mail exchange with Loupedeck I know that they are exactly doing that and applying to Phase One for a better integration. Let each one draw his own conclusion by that.0 -
Strange enough that your D2 still changes brightness, while mine just beeps and does nothing 🤬
And assigning brightness to D1 doesn't work either..
I know for the integration - i suspect some bad will at one of the sides ... or perhaps just a question of money...0 -
Okular wrote:
There's a new version 3.1 of the Loupedeck software for download since today
Thanks for picking up on that. Still not perfect but getting there.
Jonathan0 -
For what it's worth (reg. Okular reply):
When I switch the main keyboard layout of my Mac to QWERTY - US International, then D2 works as Brightness as well...0 -
Claude-1300 wrote:
Hmm, strange ...
When I switch the main keyboard layout of my Mac to QWERTY - US International, then D2 works as Brightness as well...
Btw I have to correct my earlier remark regarding the new controls Blacks & Whites: If you only install the current software version over the existing one the old Capture One profile is retained. Then you have to reset the application profile to default and the new controls work.0 -
Haha, funny !
That's exactly what the LoupeDeck support replied to me 15 minutes ago ! 😊0 -
Okular wrote:
Claude-1300 wrote:
Hmm, strange ...
When I switch the main keyboard layout of my Mac to QWERTY - US International, then D2 works as Brightness as well...
Btw I have to correct my earlier remark regarding the new controls Blacks & Whites: If you only install the current software version over the existing one the old Capture One profile is retained. Then you have to reset the application profile to default and the new controls work.
Actually, you are more lucky than me:
No change after a reset.
Black knob works, white not.
And still no brightness.
BUT (again):
If I change the Mac keyboard layout from AZERTY (Belgian) to QWERTY (US International), then it works...0 -
Claude-1300 wrote:
What setting changes the Blacks knob? Before reset (means in v3.02) mine has changed the bottom line levels black (I hope translated correct).
No change after a reset.
Black knob works, white not.Claude-1300 wrote:
If you look in C1 which hotkey is used for brightness, it says in my German installation: Ctrl + Shift + W (+5) or Alt + Shift + W (-5).
And still no brightness.
BUT (again):
If I change the Mac keyboard layout from AZERTY (Belgian) to QWERTY (US International), then it works...
So it really could be due to the different layout where on the French keyboard the W is on a different key than on the German and US keyboard, where it is in the same place.
Look in C1 in the menu Edit / Edit keyboard combinations ("Loupedeck beta" should be set) under Other, there you find among others Brightness and try the combination set there directly on the normal keyboard on both language layouts (and btw which hotkey is set in your installation?)0 -
For those of you using LoupeDeck+ with Capture One 20, how did you set it up? LoupeDeck's instructions are not valid anymore.
Thanks.0 -
jdmuys wrote:
For those of you using LoupeDeck+ with Capture One 20, how did you set it up? LoupeDeck's instructions are not valid anymore.
Thanks.
Depends.
What keyboard do you have ?
AZERTY or QWERTY ?0 -
I am using a QWERTY keyboard. Thanks for helping me setup C1 for the LoupeDeck+ 0 -
What do you mean by the "... instructions are not valid anymore ..."? The instructions are still correct, nothing has changed in installation and setup: Download the software from the Loupedeck website (what is your operating system?) and start the installer. Then installation is finished open the Edit menu in C1 and open the Keyboard Shortcuts item, Loupedeck_Beta should now be selected, if not, choose it yourself.
What Claude speaks about is an issue that seems to appear with French keyboards. Because Loupedeck does not have access to the C1 APi (Phase 1 apparently does not give Loupedeck access, only to the competitor Tangent), they use the Keyboard Shortcuts as a workaround and assigned them to the controllers on the device. As some keys on the French keyboard are assigned differently than e.g. on the US English and German keyboards, apparently a few controls don't work. But with a QWERTY one it should be ok.0 -
I confirm.
AZERTY is not supported by LoupeDeck for CaptureOne - at least not yet.
When I want to use the controls mentioned by LoupeDeck, I have to chose the QWERTY layout, and then, it works as before.0 -
Claude, btw, did you open a support case with Loupedeck about the keyboard layout issue? 0 -
HAhaha ! ONE support case ?
Yes, one in the beginning. Many since then.
Even forwarded them an annotated copy of their manual, listing every single command that didn’ work as expected in AZERTY.
And since then, I keep on reminding them every 2nd week !!!
They had promised a multi-layout driver, and it came...
...unfortunately -as always- only for LightRoom.
So I keep pushing...0 -
Hi Claude,
I'm from Belgium too and so I also use an AZERTY keyb. Can you explain to me what the problem is if I don't use a QWERTY keyb? I understand some functionality is lost, but can't this be solved by editing the keyb config file in C1? AFAIK the keyb file in C1 is some kind of remapping of a letter, symbol or key combination to a command in C1 so I thought it must be possible to remap A<->Q, Z<->W and so on? But as this seems to be a big issue I guess my solution is way too simple. I don't have a LDCT yet, planning to buy one so I can't test.
0 -
Hello Ivo,
The problem is that if you want LoupeDeck+ to work, you have to change your keyboard to QWERTY (US) every time. The pref file doesn't hold info for pre-defined rotating buttons, so with AZERTY these become "hazardous" at least.
I have asked for ages to LoupeDeck to make a pref file that would use the current layout in service (even sent them the full conversion or remapping), but that was not deemed important enough.
After many weeks of patience and promises from their Tech Support that "it will be in the next release", followed by "no, it will not be", I sent the LD+ back and got a refund, based on the fact that the "limited compatibility" with Capture One as they mentioned it on the site never made a reference to the mandatory US QWERTY layout.
Since then, they have added it in the details of the products, but you have to navigate quite deep to find it. But that covers them juridically.
0 -
Thanks Claude for you fast and clear answer.
I didn't think about the rotating buttons. I will do some tests too and send it back if the keyboard layout switching is too annoying. Probably I also need to switch my language to English (US), now I use English (Belgium) or (UK) as I don't like the reverse date notation of US. Also the lack of a real API solution for Capture One and Affinity Photo is bothering me for a product in this price range. (I want to buy the CT version for the smaller footprint)
I wanted to use this HW solution to reduce the RSI problems in my right hand, so I want to switch as much as I can from mouse to tablet pen and other tools like a LoupeDeck.
Have a nice day,
Ivo
0 -
Be careful that the return of the product is not a standard procedure of LoupeDeck, especially now that the requirement of an US QWERTY is mentioned on their site.
They accuse C1P to not be willing to open the API (which may be true - or not), and at the same time, C1P gave a go to the AppleScript based "Palette Gear" - and also stopped supporting the Tangent hardware - a smart move, et the price of this equipment.
I think that the truth is more that LightRoom has a huge established customer base that would guarantee immediate profits on LoupeDeck for LightRoom, while C1P is more of a niche, and therefore has no room for development spendings.
0 -
Thanks for the advice, but I will buy from a reseller, I learnt my lesson buying directly from GoPro in the past. I also got the feeling both parties are not on speaking terms anymore to find a acceptable solution.
Certainly C1P (and Affinity) is more "nichy" than Adobe products, but I ran away from Adobe because of their subscription platform. I'm an amateur animal photographer and hate subscriptions for software.
0 -
Just a little update, a bit off topic as this is about the LD CT.
I tried to love this device but I will return it to the shop. Here is a small review for the use with C1.
+ The built quality is very nice, regarding turn knobs, buttons and overall feel.
+ Having a knob to turn makes editing a picture nicer in some cases.
- The touch screen is way too sensitive, even touching the border in between the LD logo and the screen activates a function.
- You need to control the device with two hands as with one hand you will touch the middle dial and that one has a very sensitive touch screen. But many functions can not be emulated with keyboard shortcuts so you still need one hand on the mouse. E.g. resetting a slider to 0 or clicking on the name of a slider to temp. reset it isn't possible.
- I use auto levels very much, no shortcut for that.
- Switching your view from screen to the LD CT to look at the touch screen or function of the dials is contra productive. Also editing a curve or colour wheel really needs a mouse.
+ I had no problems using an AZERTY layout keyboard with the device without switching to US or UK layout, and if so you can change the shortcuts in the software.
Overall the device looks great but doesn't improve my workflow. And it is just too expensive for the small benefits it is adding. I also noticed that a turn knob is nice, but moving a slider with your mouse is better. I.e. I sometimes pull a slider from far left to far right just to see where on the picture it affects the image and then dial in the value I want. That is not possible with a turn knob as it moves in too tiny steps, to get from min. to max. you need to turn it many times. I made a macro to move the settings by 5 with one click of the knob but even then it doesn't feel good. The turning knobs are linear, they should be exponential controlled by the speed you turn them.
The only thing I liked was color / star tagging and filtering, but a StreamDeck will do that for less money.
BTW: The integration for C1 using the LD Live or CT is way better than the LD+.
My 2c.
0
Please sign in to leave a comment.
Comments
26 comments