Hi @lorne.white,
The stream deck plugin can control global volume levels, but it can’t control individual levels of plugins, media players, routes etc…
What exactly do you want to do?
Brad
So far the existing functionality will do the job. I wish I invested in a stream deck earlier for the integration you have provided. In addition to the streaming I do with OBS.
When I do have some layered instruments it’s nice to be able to adjust a specific volume up or down. Is there anything in the new Binding system for that?
I think the binding system can handle this and it’s more a limitation of the StreamDeck code… but I’d need to check to be sure.
love working with the stream deck plugin and have now updated to the stream deck plus, it would be great if i could use the rotary encoders without having to go through the additional midi plugin.
are there any plans for this?
further question:
i want to trigger diffrent samples via media player, how can i manage to display the media player name under the transport button?
Hi Tobi,
I asked here about StreamDeck+ support at the end of last year to see if anyone was interested and got the impression it wasn’t that needed.
See this post.
I’m not against adding support for this, but priorities…
Brad
I just installed the Android mobile StreamDeck app and am playing with the 4 available buttons (free version) just to get an idea of what it can do. I found it handy for some OBS work I was doing.
Which SteamDeck (physical version) works best for controlling Cantabile? I would probably buy a less expensive one as I already have many buttons on my Axiom keyboards bound and working well.
EDIT - just looked at the thread link Brad posted in the post above and it looks like 15 button is the way to go?
Both are great although since I got the XL I haven’t used the 15.
Main thing I like about the XL is you can fit 6 songs/states horizontally with next/previous buttons at each end which provides pretty good navigation without having to go into a second screen (like on the 15).
If you’re not going to be using it for song/state selection, or if you need only next/previous song/state (not jump to song/state) the 15 should be good enough.
XL you can fit two rows of these, one for songs, one for states:
On the 15, you first press a “choose” button:
which shows a second screen to pick from (but then you get 12 items to pick from)
But, you can do the same thing on XL and get 28 songs/states on one screen:
1 Like
The XL is great for the studio, but I find the 15-button enough for on-stage.
If the Stream Deck+ came in a 6-wide version (or 8-wide, even better) it might interest me, but not in its current form.
1 Like
Exactly my thoughts - and my current setup: 15 buttons for live, and the XL on my studio desk…
No need for the Streamdeck+ in my setup - I have faders and dials a-plenty…
1 Like
I just ran across this slightly old thread. Seems very interesting. Is anyone using the Stream Deck+ (the one with 4 knobs)? Does Brad’s plugin support the +? My main need right now is adding some encoders with feedback and programmable labeling. I’m sure I will find some applications for buttons with labels. I mostly use my laptop’s touchscreen for buttons. But tiny little sliders are difficult.
Hi @raydyo
I do plan to add support for the plus… however when I asked about it here feedback was luke warm so I dropped it down the priority list a little. Not time frame for this yet.
Brad
Thanks, Brad.
Are these things difficult to integrate without the special plugin?
My main goal is some renamable knobs. Mostly for individual rack levels in songs. Maybe some renable buttons for states changesr.
You have a couple of options:
- The source code for the Cantabile stream deck plugin is publicly available - if you’re up to it you could add support yourself. (see here)
- Build something dedicated to your particular use case, using Cantabile stream deck plugin as basis.
- Use the third-party MIDI plugin for streamdeck. Not sure how well that will work, but probably worth investigating.
Brad
Thanks, Brad. I’m guessing that you brewed your own because the off-the-shelf plugin was lacking?
If I get a stream deck+, which is not a certainty, I may dig into your stuff. What is the programming language? I am experienced with c and c++. Not so much with more modern stuff. I have some success with plug’n’script. But it is not too far removed from c. Can an old dog learn new tricks?
The Cantabile stream deck plugin is just much more integrated than the MIDI one. With the MIDI one you’d need to configure controllers on the stream deck and then bindings in Cantabile. With Cantabile plugin you can map buttons directly to actions in Cantabile.
Javascript and HTML. Take a look at the code base I’ll think you’ll find your way around easy enough. Also check out the stream deck sdk.
Ho Brad,
I have a Stream Deck+. I’m just getting started.
My long-term goal is to make your plugin work with “+”, but just to get acquainted, I fired up the generic midi plugin. I was able to get a button command and an encoder command from Stream Deck to Cantabile working, But I could not figure out feedback from Cantabile to Stream Deck. Might be pilot error. My main interest is adding some continuous encoders to my setup. No feedback is a non-starter for that,
Moving on, I installed your plugin. It did not ask about installing profiles. Maybe because there are none for the “+”? But it does show Cantabile options in the Stream Deck App. I placed a Cantabile Midi button and assigned it to momentary, CC64 (damper pedal), and onscreen keyboard. The button moves the damper pedal in my Pianoteq, as expected. There doesn’t appear to be any feedback from Cantabile to Stream Deck for momentary, I wanted to see what feedback looked like. I changed it to toggle behavior and things got weird. Starting from black display and damper up, pressing the stream deck button goes black/down, blue/down, blue/up, black/up. No feedback from Pianoteq GUI damper to stream deck. I’m sure that this is just some ignorance on my part. I want to be sure I have the basic setup right prior to attempting any code development.
I was able to clone the repository and create a branch. I will not push anything without your prior approval. That might not even be possible unless I am added to the repository?
I am about to install the Stream Deck SDK, Wish me luck…
Hi @raydyo,
For this to work with feedback via MIDI you’re going to need to use a bi-direction MIDI binding (assuming the StreamDeck+ MIDI plugin supports receiving MIDI too).
If you’re trying to code this in the Cantabile plugin, you can avoid having to manually setup bindings as the Cantabile API allows access to all available binding points - so you can both set a plugin parameter value via a target binding point, and monitor a plugin parameter source binding point for changes - so you can update the StreamDeck display.
As I think I mentioned before, I’ve not looked at the SDK for the “+” so not sure what’s involved on that side.
The standard workflow for this is you should Fork the repository in github. That will give you your own copy of the repository that you can make changes to. To contribute your changes back to the main repository you can create a Pull Request in github - which I can review and then accept/reject etc…
Brad
Thanks, Brad.
I’m not going to spend any more time on the generic midi plugin. Bidirectional binding did not work. Encoder is sending +/-1 but needs to display the target value after in inc/dec. I tried adding a separate return binding, like a controller bar binding. No joy. The plugin does have a setting for midi input but I couldn’t make it respond. I also tried sending a value from midi-ox instead of Cantabile.
Any idea why the Cantabile plug in is taking 4 hits to cycle through a toggle? That may be a stumbling block for new code development.
I have never used fork, but I will try it before I make any changes. That will allow me to push with no effect on your stuff, right? But you can still see it if you can spare time for stupid questions? Should I retain the name in case you want to pull it in at some point?
I was able to run the elgato SDK with their example profile and make simple changes to the action. Quickstart guide was not 100% accurate, but not too bad.
My next step will be to see if I can make buttons work from my copy of your source code. Preferably with hot reload. But I am a litlle confused that your directory structure is a little different than Stream Deck’s example. If I can get that going, then I will attempt to add dial actions. I’m thinking it will be very simiar to your up/down buttons.
Hi Brad
When I went back to this last night, the 4-hit toggle business was gone. Weird.
Anyway, I uninstalled your prebuilt plugin. I believe I have succeessfully created a bitbucket account, forked your repository and cloned my fork. Now I’m stuck. I went through the Tream Deck sdk tutorial. But your repository doesn’t seem to match up with the tutorial’s structure.
You run the tutorial with “npm run watch” from the “hello world” folder. But that doesn’t work with the Cantabile folder. It is missing, among other things, package.json. Do I need to add .json files from outside the repo? Do you debug with some other tools?
If you can help me get started I will try not to bug you with a lot of questions on the code itself.
-ray
I did re-organize my project a little compared to the sdk examples, but not that much. Also I don’t remember there being a npm run watch option back then - sounds like they’ve changed some things in the SDK/example projects.
I think when I was developing it, I just created a symlink from the streamdeck plugin directory to my project directory - but I do remember it being a bit of a pain so if the SDK’s been updated it’d probably be worth try to move to that. Without digging into it, I couldn’t say what’s involved though.
Also, I forgot that the repository was still on bitbucket and I now use github. So I’ve moved the project - it’s now here. Sorry for the inconvenience but probably best to Fork it again on github and go from there.
Brad