STREAM DECK XL – Control Reason with Keyboard Maestro

[PhillipOrdonez]

I used the mini app on my phone before I got the SD mk2 (15 buttons) I loved it but didn’t love having to have my phone screen on all the time. Might be different with an ipad though! It sure is a nice gateway into the sd, and if my old phone worked at all I would use it for extra functionality in addition to my SD. More buttons is always nice to have, plus you can have different profiles on each device so when you do get your physical one you can plan your profiles according to your needs with the additional buttons on the iPad to do different functions than on your SD

[joeyluck]

Yeah one of the bonuses about the app is even more buttons, if you want. And you can run multiples of the app in split view and each instance can be directed towards a different computer/app I believe.

[PhillipOrdonez]

Yeah one of the bonuses about the app is even more buttons, if you want. And you can run multiples of the app in split view and each instance can be directed towards a different computer/app I believe.

Multiple instances I didn’t know.

More buttons? The paid version has like 64 right?

[joeyluck]

Yeah one of the bonuses about the app is even more buttons, if you want. And you can run multiples of the app in split view and each instance can be directed towards a different computer/app I believe.

Multiple instances I didn’t know.

More buttons? The paid version has like 64 right?

Yeah 64, so twice as much as an XL. But note sure I would do that on an iPad Mini or need that many buttons at once on screen though. But it can also be a custom number.

[PhillipOrdonez]

Multiple instances I didn’t know.

More buttons? The paid version has like 64 right?

Yeah 64, so twice as much as an XL. But note sure I would do that on an iPad Mini or need that many buttons at once on screen though. But it can also be a custom number.

Sounds great.

I do fine with 15 on the mk2. With profiles, pages, folders, there are no limits, with a bit of planning, mind you.

[wendylou]

Yeah 64, so twice as much as an XL. But note sure I would do that on an iPad Mini or need that many buttons at once on screen though. But it can also be a custom number.

Sounds great.

I do fine with 15 on the mk2. With profiles, pages, folders, there are no limits, with a bit of planning, mind you.

Very true! I use 11 interconnected, multi-page Profiles with my Reason KB Edition, and much of it is organized just like the Reason Menu structure with plenty of room for user-defined buttons.

@joeyluck I too initially wished they would release a 32-button version with rotaries added, but from the response I got from Elgato, it didn't sound like they were planning on making it. So I added a Nektar P1 control surface with 9 sliders and plenty of rotaries, which is tightly integrated with Reason and most devices out of the box. So between the Stream Deck XL and the P1, I'm covered! I find I still reach for the mouse to move sliders or knobs out of habit, lol! But the Stream Deck I use constantly and it's a real time-saver.

[PhillipOrdonez]

Well Joey, sounds like Elgato heard your prayers:

Stream deck studio
899 buckaronis
https://www.elgato.com/eu/en/p/stream-d ... qbg8pvm81b

[joeyluck]

Haha yeah not that though!

I've actually been looking again at TouchOSC. I have Mk1 and haven't used it in a bit. You don't get the tactile control, but you can combine MIDI controls with keypress buttons. Apparently though, the newer version has removed keypress support, although supposedly you can script it using OSC...

[wendylou]

Haha yeah not that though!

I've actually been looking again at TouchOSC. I have Mk1 and haven't used it in a bit. You don't get the tactile control, but you can combine MIDI controls with keypress buttons. Apparently though, the newer version has removed keypress support, although supposedly you can script it using OSC...

Would buying a Stream Deck XL (32 buttons) plus two Stream Deck + (4 rotaries/4 buttons) meet your needs?

BTW, the free Stream Deck "MIDI" plugin by Trevliga Spel has recently been revised with very powerful features for the rotaries and MIDI capabilities.

[joeyluck]

Haha yeah not that though!

I've actually been looking again at TouchOSC. I have Mk1 and haven't used it in a bit. You don't get the tactile control, but you can combine MIDI controls with keypress buttons. Apparently though, the newer version has removed keypress support, although supposedly you can script it using OSC...

Would buying a Stream Deck XL (32 buttons) plus two Stream Deck + (4 rotaries/4 buttons) meet your needs?

BTW, the free Stream Deck "MIDI" plugin by Trevliga Spel has recently been revised with very powerful features for the rotaries and MIDI capabilities.

Perhaps! I did see some stands on etsy that combined a few different Stream Decks, like this one...

https://v.etsystatic.com/video/upload/a ... hj2auj.mp4


Maybe this is what I really want

[wendylou]

Would buying a Stream Deck XL (32 buttons) plus two Stream Deck + (4 rotaries/4 buttons) meet your needs?

BTW, the free Stream Deck "MIDI" plugin by Trevliga Spel has recently been revised with very powerful features for the rotaries and MIDI capabilities.

Perhaps! I did see some stands on etsy that combined a few different Stream Decks, like this one...

https://v.etsystatic.com/video/upload/a ... hj2auj.mp4


Maybe this is what I really want

Well my solution is perhaps not as elegant, as its two devices, but this covers all the bases for me in Reason

IMG_3295.jpeg

[mcatalao]

So i bit the bullet and got myself the Streamdeck XL.
For my case, i'm using it with my humongously huge ultra chananingans autohotkey script.

Autohotkey is an automation tool for windows that amongst (many) other things has some features that make it amazing to use with Streamdeck and a DAW:
- It responds to hotkeys and can send hotkeys to other sofware.
- It sends any kind of key strokes, either in conjunction for hotkeys or sequencial for writing stuff
- It has functions to regognize images
- It allows you to also send mouse click inputs, drag and drop stuff
- Manages file system tasks like files, folders, and so on
- Has app context like knowing if an app is running, a window is opened and active
- Has screen context with image search to gather context
- It's super extensible with com and other interfaces
- It's a scripting tool with control and logic like a programming language (very simmilar to VBA or VB6)

For now I'm just sending the hotkeys i used to this crazy script and it's working great but my idea is retrofit this into multiple scripts with parameters so that i don't have to use shortcuts and leave the keyboard for the default reason shortkeys.

So my Berries got a new friend! Yuppie kai yay!!!

[LABONERECORDINGS]

yeah still got some Autohotkey scripts for colouring up the channels / tracks / lanes depending on which screen you are in - that's the trick sometimes when you Autokey Spytooling the windows

[mcatalao]

Beauty! Control freak but in a good way...

[mcatalao]

Hi folks,

I'm having some issues with the midi controling part of the streamdeck.

I tried to automate the click button throught midi with the mackie remote and the midi plugin, plus loopbe as the midi port.
Activating the click works well, however the status is not mantained by streamdeck. Did anyone have this issue? It's not a big problem, the screen gives me enough context, for the click but i wanted to get some other data from the remote (active channel, and other stuff) and if such a simple example doesn't work that kind of context is even worse, i guess.

On a side note, I've kept evolving this with Autohotkey. There's a plugin launcher that allows to run commands passing parameters, so I created a bunch of keys to create instruments, i already mapped 50+ instruments, configured a way to create preset favourites navigating the browser, passing the name of the preset.

This is a super fun device and a perfect match for AHK and my behringer setup.

[wendylou]

Hi folks,

I'm having some issues with the midi controling part of the streamdeck.

I tried to automate the click button throught midi with the mackie remote and the midi plugin, plus loopbe as the midi port.
Activating the click works well, however the status is not mantained by streamdeck. Did anyone have this issue?

I thought the recent update to the MIDI plugin for Stream Deck has revamped Mackie control such that it can latch the button state icons to show correct status? I’ll look into this, as I want to use it for my “Play” button, which currently does not latch and display the button state.

[selig]

Hi folks,

I'm having some issues with the midi controling part of the streamdeck.

I tried to automate the click button throught midi with the mackie remote and the midi plugin, plus loopbe as the midi port.
Activating the click works well, however the status is not mantained by streamdeck. Did anyone have this issue?

I thought the recent update to the MIDI plugin for Stream Deck has revamped Mackie control such that it can latch the button state icons to show correct status? I’ll look into this, as I want to use it for my “Play” button, which currently does not latch and display the button state.

I may not be understanding the exact situation, but with Mackie Control you can get play buttons that follow the transport no matter what controller actually initiates play. But if you have more than one DAW open you'll be controlling both at once unless you turn off the MIDI routing on one (not an ideal situation, unless you are looking for a solution to being able to control two DAWs with a single controller!).

[mcatalao]

I may not be understanding the exact situation, but with Mackie Control you can get play buttons that follow the transport no matter what controller actually initiates play. But if you have more than one DAW open you'll be controlling both at once unless you turn off the MIDI routing on one (not an ideal situation, unless you are looking for a solution to being able to control two DAWs with a single controller!).

I'm just using one DAW at a time. I do have a profile for Cubase, but i didn't start to program it. My problem is really the fact that in my case it seems the midi return doesn't retain the status of the button. OTOH, i tried another midi driver, it was even worse.

I can make a video to show this better if I'm still not clear.

[selig]

I may not be understanding the exact situation, but with Mackie Control you can get play buttons that follow the transport no matter what controller actually initiates play. But if you have more than one DAW open you'll be controlling both at once unless you turn off the MIDI routing on one (not an ideal situation, unless you are looking for a solution to being able to control two DAWs with a single controller!).

I'm just using one DAW at a time. I do have a profile for Cubase, but i didn't start to program it. My problem is really the fact that in my case it seems the midi return doesn't retain the status of the button. OTOH, i tried another midi driver, it was even worse.

I can make a video to show this better if I'm still not clear.

Are you talking bi-directional control? I’ve been doing that on certain controls since day one, using the MIDI extension (Mackie Control, specifically).
Play, Record, Click on/off, Loop on/off, all work this way (off the top of my head).
You also need to program the button and add the second graphic file for the alternate positions (lit vs dark versions).

I would need more specifics before I could give further suggestions, such as what type of button you’re using and what controls you’re expecting this to work on (there is a limited number of controls shared by Mackie Control and most DAWs).

[mcatalao]

Selig, thank's for your help.

TBH, i think i'm doing everything right but the issue seems to be on the midi driver.
I'm using the midi plugin, it has a Mackie midi task.
I then select the reason profile, the midi loopBe driver (as advized in the plugin maker's site) and i used the 2 click icons of your icon pack. The mackie remote is standard, no changes at all.

I'd say it is a pretty straight forward example, but unfortunately it is not working fully as the status seems that it is not sent back. As you also stated, if i pressed the click button on reason or other device, the status should be sent to the streamdeck as it happens with my bcf2000.

Something odd is afoot. I might try their forum too... Still my sniff detector says midi driver.

[selig]

Selig, thank's for your help.

TBH, i think i'm doing everything right but the issue seems to be on the midi driver.
I'm using the midi plugin, it has a Mackie midi task.
I then select the reason profile, the midi loopBe driver (as advized in the plugin maker's site) and i used the 2 click icons of your icon pack. The mackie remote is standard, no changes at all.

I'd say it is a pretty straight forward example, but unfortunately it is not working fully as the status seems that it is not sent back. As you also stated, if i pressed the click button on reason or other device, the status should be sent to the streamdeck as it happens with my bcf2000.

Something odd is afoot. I might try their forum too... Still my sniff detector says midi driver.

Wait, are you on Windows? I ask because I'm confused by the MIDI Driver statement, since on a Mac I have no control over that other than to change the settings. If you're on a Mac I can walk you through the setup, which was not the clearest task I've ever undertake to be honest, as you need an IAC profile for both to and from StreamDeck MIDI, AND to and from DAW MIDI, so four profiles in total. And they. must be correctly assigned on both ends, which took me more than a second to figure out.

[mcatalao]

Wait, are you on Windows? I ask because I'm confused by the MIDI Driver statement, since on a Mac I have no control over that other than to change the settings. If you're on a Mac I can walk you through the setup, which was not the clearest task I've ever undertake to be honest, as you need an IAC profile for both to and from StreamDeck MIDI, AND to and from DAW MIDI, so four profiles in total. And they. must be correctly assigned on both ends, which took me more than a second to figure out.

Yep, I'm on windows 10.
The recommended process on their site is to load it with MidiLoopBe, you set up the drivers on both applications.
It seems to be right, it sends the click on to reason, but it simply doesn't get the status back. :/

My take is something odd in the loopbe driver. But I've used loopbe extensively before and it worked fine in stuff that seemed to me more complex, like controlling orchestral lybraries out of reason, or the silly punch in/out work around that i still have to do, you know why... :/

[mcatalao]

PS.: Just to confirm, you're using the Midi Plugin by Trevliga Spel, right?

Tks!

[selig]

PS.: Just to confirm, you're using the Midi Plugin by Trevliga Spel, right?

Tks!

Yes, as far as I know it is (currently) the only way to have MIDI support in ScreenDeck. It’s only the Mackie Control parameters that work bi-directionally IIRC.

[mcatalao]

Yes, as far as I know it is (currently) the only way to have MIDI support in ScreenDeck. It’s only the Mackie Control parameters that work bi-directionally IIRC.

Yep, that's it. For the click i'm using the Mackie Control, then it has a reason profile, and there i select the click. I think i'm doing everything ok so next step is going to nag the guys in their forum!!!

Again, than'k's for your help.