preferences/plugins/

[giscus[bot]]

preferences/plugins/

CommandPost is made up of many Lua-based plugins, all contained within the CommandPost application bundle.

https://commandpost.io/preferences/plugins/

[junction10]

Is there any way you can 'batch' disable plugins - or at least disable them without the app having to restart each time? I want to disable all the plugins I don't need at the moment but could really do with being able to disable them in one go - and THEN restart the app.. ? Thanks

[junction10]

Hi Chris - I'm trying to use Command Post with a Loupedeck CT device for Final Cut Pro (and using the Loupedeck CT for Lightroom Classic as well) but the LoupedeckConfig app runs so slow when I enable the LoupeDeck Plugin in CommandPost. If I disable it, LoupeDeckConfig runs quite quickly but I'm getting spinning beach ball for 2-3 minutes when changing settings when the plugin is enabled in CommandPost. I figured I'd try and disable plugins that I don't need from Command Post to see if it might speed things up, but I do notice in the CP Log file:

2023-07-26 11:45:06: 11:45:06 ** Warning: plugins: Slow Plugin: finalcutpro.setup.scan (48.542414903641)
2023-07-26 11:45:08: 11:45:08 ** Warning: plugins: Slow Plugin: core.loupedeckctandlive.manager (1.4122850894928)
2023-07-26 11:45:08: 11:45:08 ** Warning: plugins: Slow Plugin: core.menu.menuaction (1.809287071228)

So maybe these have something to do with it?

Best regards,

J.

[latenitefilms]

My sincerest apologies for the insanely delayed reply! I don't think disabling CommandPost Plugins will have any impact on the official Loupedeck application. The official Loupedeck application has a bunch of bugs and issues - that have been acknowledged by the Loupedeck (and now Logitech) team. One of those issues is that the Loupedeck app just grinds to a half once you have a certain number of actions in it - and obviously the CommandPost plugin adds a LOT.

This has been an issue for at least two years now (see here) - but I don't see Loupedeck/Logitech fixing it anytime soon.

If you want to control Final Cut Pro with a Loupedeck device, you're better off just ditching the official Loupedeck software, and using CommandPost's direct/native support. Really, the only reason I'd use the official Loupedeck app is if you're in the Adobe ecosystem. For Lightroom Classic, have a play with MIDI2LR.

[junction10]

Thanks Chris.. I spoke to LoupeDeck last year as they haven't made a native silicon version of the software yet, which is a bit pants really.. I can't image that's helping with speed..

I'll be honest - I didn't actually realise you could ditch the LoupeDeck software and JUST use CommandPost.. Certainly worth trying.. but I can't see any way of changing the wheel screen, or the side / button screen banks... is that possible?

[latenitefilms]

Absolutely! You can customise EVERYTHING with CommandPost - you have a lot more control.

[junction10]

Am I right in thinking that if I had Bank 1 with various options on the 12 LED buttons, and the Wheel screen was set to the 'master' colour nudge feature and I wanted to be able to double click the CT wheel screen to switch to, for arguments sake, shadows color nudge.. I'd need to duplicate the whole bank, to Bank 2 for instance, and then change the Wheel Screen functionality in bank 2?
Is there a simpler way of changing the wheel screen function without requiring a duplicate bank?
Same goes for the 12 LED buttons and side wheels - the Loupedeck config lets you swipe across those to switch to a different bank of features for that panel only..

What's the best config workflow to be able to switch the functions of the wheel and dials, without having to have duplicate banks?

J.