Repository navigation
Main screen not updating on Loupedeck CT (Hardware Version 02.00) #3328
Description
Activity
Are you using CommandPost directly or via the official Loupedeck software as a plugin?
A lot of people have had issues with the official software, so most of our users are just using CommandPost's native/direct support.
I have installed commandpost as described on the website bellow:
https://support.loupedeck.com/setting-up-commandpost-plugin
What do I need to change to use the loupedeck CT via commandpost directly?
Thank you for your quick response!
Never mind, I just found the description. I will give it a try later today.
Tried to use CommandPost's native/direct support today, but it's still lagging quite a bit. With a slow turn on one of the dials it's keeping up, after multiple turns it start lagging. When I use my mouse to control the color wheels for example, and flip it to the sides, it reacts immediately
Is the official Loupedeck software definitely not running?
Have you tried a good old fashion restart?
Do you have any other applications running that use the Accessibility API? Check your System Settings/Preferences to see what else uses the Accessibility API, and close them to see if it makes any difference.
Yes restarted multiple times. Next to Commandpost only FCPX had permission to use accessibility API. I turned it off and tried again, but no success. I added some other functions to the dials to do some more testing (move 1 or 10 frames backward or forward via the workflow extension API), but this is even slower. When I turn the dial, first nothing happens, then the Commandpost status window opens up a few times. After a few times it finally says ping received and the playhead start moving, but also really laggy.
Commandpost.mp4
This might seem like a crazy idea, but what cable are you using? Are you using that cable that came with the device?
We have seen some users have all kinds of issues with Loupedeck products when using other USB-C cables.
I use the usb-c cable that comes with the Loupedeck CT and plug it directly into the usb-c port of my MacBook.
I started all over again by reinstalling both the Loupedeck software and Commandpost. Uninstalled Loupedeck as explained on the website, and switched commandpost over from plugin to the native support.
For some reason the input is much more direct now. Might have been a background process that was still running indeed..
Reacted by Chris HockingHowever, I now have the problem that my symbols are no longer visible. I have reset all settings and rebooted my MacBook, Commandpost and the loupedeck, but without success.
Also when switching between applications and or switching preview, no symbols are visible.
Any idea what causes this and how to fix it?
Have the icons ever shown when using CommandPost's Native/Direct support or has it always been blank?
Are you able to share a photo of the Model/Type sticker at the back of the hardware?
What version of the firmware are you running? Is it the latest (via the official Loupedeck software)?
In the past, several times Loupedeck has updated the physical hardware, and changed the way the screens work - so it's entirely possible, if this is a new hardware device, that something has changed - although generally speaking if something like this happens, we normally get a lot of emails from people.
I can't quite remember if the symbols were visible before with the use of direct support, I don't think so. I have attached a picture of the hardware and firmware version.
21 remaining items
Hi, I changed the code on line 374 to the following, given that 0.1.2 is actually a newer version than 0.2.5.
Is this a good way to go about it?if firmwareVersion > semver("0.2.5") or firmwareVersion == semver("0.1.2") then -- version 0.1.2 is newer than 0.2.5 - go figure
Yeah, quite possibly - I'll try and have a proper look at this over the next few days.
- added a commit that references this issue
on May 30, 2025 Hello, thank you very much for your support and for addressing this issue. In my case, the problem seems to be only partially resolved. The main dial still does not display any icons. Could you please advise me on how to fix this?
Hello, I recently upgraded to a new MacBook Pro (M4 Pro - Sequoia 15.6.1) and transferred all the applications and files from my previous MacBook Pro. Before starting, I checked the init.lua file to see if the changes were still present, which they were. Unfortunately, after starting Command Post and connecting the Loupedeck, the icons weren't visible. To be safe, I reset the profile and assigned new icons, but they remained grayed out. The debug console showed the following information:
CommandPost v1.5.2 (Build: 8087)
Build Date: Dec 18 2024, 17:04:23
macOS Version: 15.6.1
CommandPost Locale: en_NL
Current Keyboard Layout: U.S.
Final Cut Pro Path: /Applications/Final Cut Pro.app
Final Cut Pro Version: 11.1.1
Final Cut Pro Language: en
Developer Mode: false2025-09-28 21:36:03: Reloading CommandPost...
2025-09-28 21:36:03: -- Loading /Applications/CommandPost.app/Contents/Resources/extensions/cp/init.lua
2025-09-28 21:36:04: 21:36:04 fcpApp: Running Final Cut Pro v11.1.1 in a sandbox...
2025-09-28 21:36:04: Using sandbox path for preferences: /Users/thomasnagtegaal/Library/Containers/com.apple.FinalCut/Data/Library/Preferences/com.apple.FinalCut
2025-09-28 21:36:04:
2025-09-28 21:36:04: cp: Loading Plugins...
2025-09-28 21:36:08: 21:36:08 ** Warning: plugins: Slow Plugin: core.loupedeckctandlive.manager (1.0490560531616)
2025-09-28 21:36:08: 21:36:08 ** Warning: plugins: Slow Plugin: core.menu.menuaction (1.3030610084534)
2025-09-28 21:36:09: 21:36:09 cp: Plugins Loaded.
2025-09-28 21:36:09: Startup Time: 4.909304 seconds
2025-09-28 21:36:09: Garbage Collection Mode: generational
2025-09-28 21:36:09: -- Done.
2025-09-28 21:36:09: loupedeck: Loupedeck CT or Live connected, so lets check the firmware version...
2025-09-28 21:36:09: -- Loading extension: hs.inspect
2025-09-28 21:36:09: data: {
b = "0.1.2",
c = "0.9.0",
data = "����\t����",
i = "0.0.0",
id = 3079
}
2025-09-28 21:36:09: Loupedeck device is using firmware version: v0.1.2Your mac and macOS are probably not causing the issue. I have a M1 Max, everything worked on Sequia and is now working on Tahoe, too. Loupedeck Live (newest firmware).
Have you tried this?
Quit CommandPost, then open this file in a text editor:
/Applications/CommandPost.app/Contents/Resources/extensions/hs/loupedeck/init.lua
On line 384 it says:
self.loupedeckDeviceIsUsingRazerFirmware = false
Try changing the false to true.
Try starting CommandPost again and see if it works.
Yes, I copied everything over from my old Mac and line 384 in the initial.lua file was set to 'true'.
I did a clean install today of commandpost and changed the init.lua file, and the icons seem to be back! :)Just FYI: Setting Line 384 in the initial.lua to
truedid also work for me. Icons are displayed again on my Loupedeck CT 👍Hello, thank you very much for your support and for addressing this issue. In my case, the problem seems to be only partially resolved. The main dial still does not display any icons. Could you please advise me on how to fix this?
+1
after setting line 384, main screen is working properly, still not the dial one.Reacted by Chris Hocking
I recently purchased the Loupedeck CT for Final Cut Pro. I installed CommandPost as indicated on the site. The response of the dials is very slow in Final Cut Pro, especially in the areas of color grading (color wheels, tint, temperature, etc) and scrolling through the timeline. Am I missing something? Any help or tips would be greatly appreciated.