Desired Workflow
I want to trigger a deck by selecting a track in Cubase.
Question
I'm transferring my workflow from old Lemur apps to be all in Soundflow. I want to be able to trigger a deck when I select a track in Cubase.
Previously this was done by sending MIDI on CC126 to a virtual MIDI input, which would then trigger a return of CC127 to tell the selected track in Cubase to send out a program number informing the Lemur app which channel had been selected.
I can send the CC126 value onto SoundFlow Custom Midi input, but can't select that as a MIDI trigger input in Soundflow. Is this possible, or is there a better way of triggering a script/deck from selecting a track in Cubase?
Command Info
ID: user:ckiw2dm4d00003b105kcazwgy:ckiw2uo0500053b10ve8nxdzk
Name: Select track trigger
Source
sf.midi.send({
midiBytes: [0xB0, 127, 127],
outputNum: 1
});
Links
User UID: DQEOP03AytW99aWebOncnWRfVOz2
Feedback Key: sffeedback:DQEOP03AytW99aWebOncnWRfVOz2:-MOw_-snMb1EH3yqwpvg
- Christian Scheuer @chrscheuer2020-12-19 21:28:02.256Z
cc @JesperA
I think you're right that SoundFlow Custom Midi Input cannot be used for triggers, AFAIK.
https://help.ableton.com/hc/en-us/articles/209774225-How-to-setup-a-virtual-MIDI-bus
You'd need to use an IAC Bus (virtual midi bus) for this:Christian Scheuer @chrscheuer2020-12-19 21:29:00.540Z
CC'ing Jesper here who is our Cubase/Nuendo nerd. Jesper I'm pretty sure you would find this workflow interesting – we've been looking for a way to get MIDI through the selected track in Cubase for ages. So we may be able to all learn from setting this up, if it is possible.
- In reply toAlex_Watson⬆:Jesper Ankarfeldt @JesperA2020-12-20 03:55:24.195Z
Hi Alex.
So you can definitely enable it the same way as we've done it with Cubase.
There's also another way I've used myself, which uses quick control and the channel settings window.
- If you have Quick controls enabled, they will fire out a message every time you change a track.
- If you have the QC out going to soundflow this can trigger a script in Soundflow, that could look like this (just cut and cleaned it a bit from on of my scripts):
var app = sf.ui.cubendo var closeChannelSettingsAgain = false // This will open the channel settings window if it's not already open if (!app.getWindowWithTitleStartingWith('Channel Settings').exists) { sf.ui.cubendo.performAction({ actionName: "Edit Channel Settings", categoryName: "Edit", }); // The perform Action requires SKI. You could use a keycommand to open it instead. closeChannelSettingsAgain = true; } // this will clean out the name from the channels settings window title var trackName = app.getWindowWithTitleStartingWith('Channel Settings : ').title.value.replace('Channel Settings : ', '').split(' [')[0] // This will trigger the deck if the name has changes since the last message. if (globalState.lastTrackSelected !== trackName) { // Put here the command to change the deck aka: //sf.soundflow.runCommand({commandId: '*Decks command ID'}) globalState.lastTrackSelected = trackName } // This will close the channel settings window again, if it wasn't open. I myself usually have a dedicated monitor for it. if (closeChannelSettingsAgain) app.getWindowWithTitleStartingWith('Channel Settings').windowClose()
What's great about this is that you are not relying on a whole bunch of different midi messages, but instead a name, so it creates some transparency. And you would not have to set up the midi send for each track.
Hopefully one day we can get the track name information from Cubase/Nuendo more "natively" in SF, as it has huge potential :)
Let me know if you need more help!- AAlex Watson @Alex_Watson
Amazing.
I was looking at using "Rename first selected track" and copying the name to the clipboard, but this is much better.
Thanks so much for the help.