It'd be great if we could choose which Stream Deck devices to manage with Talon, and which ones not to, similar to the way gamepad definitions support targeting specific devices using their identifiers (e.g.: gamepad(0300.6d04.15c2.0402:south:down)).
The main reasons I see for this are:
If you use a Stream Deck at all with Talon, it tries to connect to all decks that you have, including the visual ones.
Talon doesn't yet support setting images on visual decks.
There's a long tail of official Stream Deck software that will take us some time to replicate in the community (such as direct integrations with Discord and Zoom, OBS, Key Light, etc.); pagination, folders, and so on.
Conversely, Talon's support for the pedal is already superior to the official software, because it supports down and repeat events (the official software does not), and it supports Talon's context matching.
Therefore it's conceivable that a user would want to use Talon for their pedal, but the official software for the visual deck for now.
Given decks have serial numbers, it seems intuitive that the syntax could mirror the gamepad syntax -- such as deck(DL51K1A81415:pedal_left).
Filing this along with #631 in case they are similar, although this is much lower priority.
It'd be great if we could choose which Stream Deck devices to manage with Talon, and which ones not to, similar to the way gamepad definitions support targeting specific devices using their identifiers (e.g.:
gamepad(0300.6d04.15c2.0402:south:down)).The main reasons I see for this are:
Therefore it's conceivable that a user would want to use Talon for their pedal, but the official software for the visual deck for now.
Given decks have serial numbers, it seems intuitive that the syntax could mirror the gamepad syntax -- such as
deck(DL51K1A81415:pedal_left).Filing this along with #631 in case they are similar, although this is much lower priority.