I am using the seaboard 49 with Mainstage 3. I have a variety of patches and channel strips, within Mainstage, some of which use the Equator Synth engine as an input source, and others which use the Logic/Mainstage ESX24 sampler or one of the many other instruments available in Mainstage as an input source.To make the Seaboard correctly control the Equator synth, I have to set the dashboard pitch bend range to 48. But, to correctly control most of the Logic/Mainstage instruments, I have to set the dashboard pitch bend range to 2.I need some way to automatically change the dashboard pitch bend range when I call up the different patches in mainstage. Right now I have to have dashboard open as well as Mainstage and then jump between programs to make the dashboard pitch bend changes as the different channel strips require. This takes time between songs and opens up the door to user error with disastrous sonic consequences! I suppose with time I could re-create all of my channel strips to use the equator synth as an input (it is quite a powerful synth!), but that is not practical in the near future. So, what options do I have to be able to change the dashboard pitch bend range from within Mainstage?For that matter, it would be useful to be able to change the Dashboard Mode settings and the Midi Settings remotely, via a sys exclusive command or CC message or Program change message, etc.
Here are the main MIDI messages used to configure the Seaboard RISE.
And now to the RISE's configuration MIDI messages:
Please see instructions on manually resetting the RISE firmware below:
How to reset the firmware (MacOS)
How to reset the firmware (Windows)
It will be excellent if we'll have dashboard plugin to insert it on track, and have all of these params stored in song template
Really interesting comments above!
This is an issue for me because I'd like to perform with just the Roli keyboard, but have different modes of use for different synths and patches.
Since I have an iPad, I'm using Duet Display and then dragging Roli Dashboard there, and then can use my main computer screen fully for my daw and synth pages. So it's kind of like having a Dashboard iPad app in a way.
What I would love is a Block devoted to this -- several buttons that you can press that will instantly call up the modes on your Dashboard. (Maybe one of the existing Blocks could be customized to do this?)
As with Peter, my use case is just switching profiles by name while using Blocks, and I'm guessing that would solve 90+% of the use cases for this.
I haven't tried it yet but I really like the idea of being able to use different tracking modes for different patches. I'm also going to try out controlling the Glide Sensitivity remotely, so I can use a pedal to choose between smoother glides and staying on pitch more easily. (Right now, I'm constantly reaching over on the left to adjust that.) I imagine it might be a little like (and not) using a pedal to control the Glide function on a MiniMoog.
Are there any (hidden and unsupported) ways to change the channel mode or turn MPE on and off remotely? I saw Frank G. asked about that but didn't see these included in your list of hidden and unsupported items. I regularly switch between newer and older synths with varying capabilities so this would be super helpful.
Lastly, in CC mode, I think it'd be nice to be able to update the slider LED display by sending the RISE regular MIDI messages (instead of SysEx) so we could easily have them reflect the correct value when another controller adjusts that parameter.
I have an even more complex set of patches in Dashboard that I use with various instruments in MainStage. If I was able to send good old fashioned patch changes to Dashboard that would solve everything. Seem like a much more elegant and simple solution. I have a gig tonight that I was hoping to use my Rise 49 at but always think twice because of the need to flip between Dashboard and MainStage to have the correct set of parameter activated every time I use a different instrument. I am using Equator, Cypher 2, Kontakt and Omnisphere.
I agree with Kirill, this *IS* a must have.
If I play a quick demo for a Youtube video, I do not need this feature.
But, in live session I would need to change the mode each time I change the expander configuration., for example from a guitar sound to a violin, using different polyphony (6 to 2),transposition and sensitivity setup. Without automatisable configuration, I have to change the mode manually between each song, and so I have to stop playing, and focuss on technical stuff :(
Configuration using MIDI messages would be sufficient,if it embraces all the configuration parameters. I think program changes relative to modes would be a better choice.
Going further, the use of split zones, each assignable to a mode would be the most versatile approach. With this feature, I could use the first octave in piano mode and the others using MPE to a violin. Without this feature, I need a companion keyboard managing splits with Mono Polyphonic expression...
@Red, could you please provide MIDI implementation soon ?
Thank you,Red :)
This would be a huge time saver for me as well. I'd mostly need to set MIDI channel ranges and MPE mode as well as the pitch bend range. Say when I switch from Equator to Omnisphere (8 channels, pitchbend range +-24, MPE Off) or Kontakt (1 to 16 channels, pitch bend range +-12, MPE Off) and back.
Not sure about Rise, but Dashboard and ROLI Blocks already do communicate via SysEX, half of this communication keeps showing up at my DAW's MIDI input, forcing me to use a plugin to filter the chatter out. But as of now I wasn't able to make sense of the messages, not to mention sending a sysex to a block and have it react. Still I can't get rid of the itching feeling that at least some setting measures would be working right now if I just found the correct messages to send.
I have been asking for some SysEx documentation several times at different channels, but nothing appeared yet, as far as I know.
Good question. Currently it's not possible to control the Seaboard Block's behavior using SysEx messages, although I definitely see the use case for this functionality, and we hope to look into this in the future.