Take only one of two streamdecks
Hi,
I'd like to connect one of my stream decks to an app which uses a streamdeck (not the elgato software). But everytime when I start soundflow it grabs both stream decks. Is it possible to restrict soundflow to use only the one streamdeck and ignore the other, so the other streamdeck can be locked by my 3rd party app?
Many thanks
Mike
Linked from:
Christian Scheuer @chrscheuer2023-03-24 17:17:04.003ZHi Mike,
Both the Elgato app and SoundFlow app will seize all devices that are connected, so it's not possible to use our direct integration at the same time as using the Elgato app.
If you are forced to using the Elgato app for other reasons, you could use the SoundFlow plugin inside the Elgato app to connect. Bear in mind that this will result in reduced performance, due to having to talk through their API instead of directly to the devices, and you'd lose a lot of the easy setup possible in SoundFlow.
If possible, it would probably be a more portable solution if you were able to move your Elgato setups to SoundFlow. If there are things that SF can't do yet that you'd like support for, please let us know about them :)
- MIn reply toMike⬆:Mike @Mike
Hi Christian,
sorry, I may not have been clear. I am NOT using the Elgato software, but an application from cb-electronics that connects directly to a streamdeck and that I can control comfortably via the streamdeck.
But if I then start soundflow, then soundflow claws all streamdecks that are connected. Would it be possible to exclude individual streamdecks that are used by soundflow?
Of course, I can write a deck to connect to cb-electronics devices via MIDI or OSC, but it takes time and it would be so much easier, if I could configure which devices soundflow uses and which not :)
Regards
Mike
Christian Scheuer @chrscheuer2023-03-25 02:15:34.673ZHi Mike,
It's not possible to exclude certain Stream Decks from being controlled by SoundFlow for this use case, unfortunately - it's either/or.
- Christian Scheuer @chrscheuer2023-03-25 10:37:49.469Z
It's possible that SF could build an official integration with their monitor controllers, I'd definitely be keen to look into that. Do you have any contacts at CB Electronics we should talk to?
- MIn reply toMike⬆:Mike @Mike
Hi Christian,
the Dock is used by cb-electronics with their digital Patchbays (xpatch) see: https://www.cbelectronics.co.uk/electronic-patch
II have had very nice email exchange directly with Colin, I'll send you the email contact via email direct to you.
Regards
Mike - EIn reply toMike⬆:Eli Crews @Eli_Crews
Hi Christian, I have various MIDI configurations already worked out in the Elgato software on my laptop, but when I hook the Stream Deck + up to my Pro Tools computer I can't access any of it. I know you sell a very reasonably-priced MIDI package, but I've put a lot of time into implementing it already, so I imagine I'd have to start over. Do you know if there is there any other advantage to using your MIDI package over the free one from the Elgato store, other than the fact that it will work with SF running? My ideal solution, since it would be the fastest for me, would be to tell SF to "let it go" when I want to use it for MIDI, but it sounds like that's not possible...
Thanks,
Eli- Christian Scheuer @chrscheuer2024-10-13 18:45:41.614Z
Hi Eli,
I think it sounds like you have a good overview of the options/limitations.
You could either:a) move everything over to SoundFlow, as you suggested (and buying the MIDI app/integration in the process). This would likely give you the most stable and portable solution as everything is in one app and all synced to the cloud, and there's no complexity to deal with by having 2 apps try to communicate to the same Stream Decks.
b) or, try to use SoundFlow and Stream Deck together, which is more complex to set up, and involves using the SoundFlow plugin for the Stream Deck app. Since the Stream Deck app's API doesn't give us as much control or performance as when we talk directly to the Stream Decks, you end up having to rebuild a lot of stuff inside the Stream Deck app, or live with the limitations. You'd also deal with the complexity that it isn't portable to other computers without a lot of manual work.
You'd probably end up doing some work to copy things no matter which way you go. From a pure perspective of having a portable, easily backup'able, cloud synced solution that removes complexity, obviously that'd be option a (even with the investment needed). Option B might sound easier, but instead of remaking your MIDI stuff in SoundFlow, you'd then have to remake decks from SoundFlow in the Stream Deck app (or use our Full Size decks), so you'd also need manual work for this option, yet you'd end up with more complexity to maintain.
The choice is yours, of course :)
- EEli Crews @Eli_Crews
Chose A before I even saw your reply, ha! I see now how much easier it is to program it in SF anyhow, so recreating my controllers will be a lot easier, and I see value in having it integrated with my other SF scripts... in any case thanks for the response!