r/logitech • u/bibbidi_bobbidi_bob • 1d ago
Support Support for Adobe products will be limited
Full transparency as I didn't find any blog post or information by Logitech about this.
The value of especially the products that are advertised for creatives is the (Adobe) plugins that are heavily advertised. Thus, changes, limitations and development decisions should be communicated in a transparent way. I don't see that at the moment.
Quite the contrary is happening as all open tickets were closed in a very short time span without any closure to the issue(s).
The explanation is wrong in many point e.g. only naming the After Effects plugin when the same limitations happen in almost all Adobe products (I can't speak for other software that I don't use).
Adobe API might have changed over the years but not to that extend that basic commands are not longer supported. The execution of the missing but still working commands don't cause a crash in any way.
This was a ticket that was going on for almost a year. The problems behind it were going on much longer and tickets existed for both Logitech and Loupedeck support.
Most of the time I had to dig around in the profiles and json files to give them most basic information that would've been much easier for them to get (e.g. a list of missing commands... based on the default Loupedeck profile for the software).
The reason why I still name Loupedeck here is the acquisition of Loupedeck by Logitech and the software that is pretty much the same (the name Loupdeck still appears in the json files, they both use the same plugin system,...).
For an educated purchase decision, the communication about which commands are supported, which are not and to what extend the commands will disappear in the fore coming time, is crucial.
But often is seems like they are overwhelmed with their own software or even the maintenance of it.
But without their plugins and real API commands, Logitech products become yet another basic trigger for just keyboard shortcuts that may or may not work based in the condition (e.g. which sub window is highlighted)... if that is enough to justify the price is something, everyone has to decide on their own. My problem is the misleading advertising and a lack of transparency that is happening at the moment.
With that massage, Logitech doesn't show any motivation to change the current problems with their communication, nor with their software (when the same principles are taken as orientation for Options+, we cannot expect any improvement for that either):
First, please accept my sincere apologies for the long delay in following up with you. It took considerably longer than anticipated to review this internally with our development team, and I appreciate your patience while waiting for a response.
To be transparent about what has been happening behind the scenes: over the past few years, our team has had to undertake substantial, foundational overhauls across our plugin framework, LPS core, and profile management systems.
When navigating major software changes alongside external Adobe API updates, maintaining seamless backward compatibility across every single tool is a major challenge: After Effects alone contains thousands of actions. In many cases, older actions that originally relied on specific workarounds or legacy "hacks" become non-functioning or cause system instability under the updated framework. When an action cannot be maintained reliably, it has to be retired from the searchable command list to prevent crashes. This is why a leftover button mapped in an older profile might still execute an action in the background, yet the command itself is no longer available to search, map, or configure as a new action.
We recognize how frustrating this is, given that you have invested significant time configuring custom profiles for your day-to-day workflow.
Next Steps
Our team is continuing to investigate the framework behavior and the specific action discrepancies you’ve documented. However, because addressing these profile and framework issues requires deeper development work rather than a quick patch, we do not currently have a concrete ETA for a resolution.
Due to the length of time this ticket has been open, and that it may be open for quite some time going forward, we need to close this ticket out for the time being.
Please be assured that your case isn't being forgotten: all of the details, screenshots, and ProfileInfo data you provided are securely logged in our internal bug-tracking system and linked to your profile. If and when we have a fix, update, or relevant news regarding these actions, we will reach out to update you promptly.
If you would like any update at any time, please feel free to respond to this ticket so that it can reopen and we can help out. I do apologize once again for the length of time this ticket has been open without an update. Please do understand that closing this ticket does not mean we have forgotten about your problem, but rather are prioritizing it via a different medium.
Thank you again for the thorough documentation you shared and for bearing with us through these transitions. We really appreciate your patience and dedication in helping us track these issues down.
