I can't find any documentation describing how Waveform configures the Roli Songmaker Kit when Waveform is set to "Take control of BLOCKS". I've fumbled my way through most of the Loop block with the exception of the lower middle button ... but I have no idea how I'd go about mapping the XYZ pad to any controls via MIDI Learn, given it sends CC 113-115 simultaneously when pressed.. and there is a constant stream of SysEx being sent to/from the Blocks as well. I also have no idea what the glide range is set to.. or what CC slide is set to (looks like 1 / modwheel?)... It feels to me like having Waveform control the Blocks is a bad idea. I can't even use the "Rise" mode to adjust the 5D.
Is any of this documented anywhere? How does Tracktion expect Roli Blocks users to take full advantage of their hardware, given the configuration Waveform puts the Blocks in when it takes control?
Edit: I see that I can at least keep the Lightpade M Block in "Rise" mode if I deselect "Send XYZ program to Lightpad Blocks", so that's good...
Waveform & the Roli Songmaker Kit / Roli Blocks
-
- KVRAF
- 1790 posts since 30 Dec, 2012
Hi there, the program sent to the Seaboard block is the standard MPE setup:
• global channel 1
• note channels 2-16
• pitch bend range +-48
• "press" is channel pressure
• "slide" is CC 74 - timbre
This is the same as the range sent from Waveform to MPE compatible plugins (this is to ensure that you can play live and from a clip on the same track etc. Otherwise you'd have live input, clips and synths all configured differently which would be chaos).
The default Lightpad program is the XYZ but as you say, you can disable this.
As you've found it's difficult to MIDI learn from a Lighpad due to the multiple dimensions, you can do this manually from the "Automation" -> "Create MIDI Controller Mappings" window.
The control block is a custom program that gives us full control over it (the program is just used to set the lights).
The mortarboard button toggles help on or off.
Hope that helps!
• global channel 1
• note channels 2-16
• pitch bend range +-48
• "press" is channel pressure
• "slide" is CC 74 - timbre
This is the same as the range sent from Waveform to MPE compatible plugins (this is to ensure that you can play live and from a clip on the same track etc. Otherwise you'd have live input, clips and synths all configured differently which would be chaos).
The default Lightpad program is the XYZ but as you say, you can disable this.
As you've found it's difficult to MIDI learn from a Lighpad due to the multiple dimensions, you can do this manually from the "Automation" -> "Create MIDI Controller Mappings" window.
The control block is a custom program that gives us full control over it (the program is just used to set the lights).
The mortarboard button toggles help on or off.
Hope that helps!
-
- KVRian
- Topic Starter
- 1000 posts since 26 Sep, 2013 from The Frozen North
That definitely helps. Thank you!
Hopefully my post didn't come off as being overly negative. I was somewhat frustrated, but I love Roli and Waveform.
I will have to give that manual MIDI assignment a try. Some plugins rely on MIDI Learn and don't have manual assignment capabilities, but if that can be done in Tracktion instead of the plugin, it sounds like I'd be good to go to be able to map the XY(Z) to XY pads in plugins. I guess that is dependent on the plugin exposing it's automatable parameters, though...
Hopefully my post didn't come off as being overly negative. I was somewhat frustrated, but I love Roli and Waveform.
I will have to give that manual MIDI assignment a try. Some plugins rely on MIDI Learn and don't have manual assignment capabilities, but if that can be done in Tracktion instead of the plugin, it sounds like I'd be good to go to be able to map the XY(Z) to XY pads in plugins. I guess that is dependent on the plugin exposing it's automatable parameters, though...
-
- KVRist
- 57 posts since 18 Mar, 2018
Sorry, I don't understand something. I was using Equator with Seaboard/Lightpad but without "Take control of BLOCKS" option selected. Seaboard Block is listed in Midi Devices setttings window. And now:
- when I have Seaboard Block input enabled and when I click "Take control of BLOCKS", I see the message "No BLOCKS connected"
- when I have Seaboard Block input disabled, I can select "Take control of BLOCKS", so all connected BLOCKS are listed below but I cannot enable MIDI input of Seaboard Block ("Couldn't open the MIDI port" hint).
What's the purpose of "Take control of BLOCKS"? Does this option just send the setup program as Dashboard does? I made some tests and it seems that after Waveform is closed, the setup goes back to the previous one (at least Lightpad behaves this way - XYZ program is off). But on the other hand I cannot use the device because its input cannot be selected.
Btw. when switching between these MIDI options related to BLOCKS I got a blue screen system crash (Windows 10) but cannot replicate it.
- when I have Seaboard Block input enabled and when I click "Take control of BLOCKS", I see the message "No BLOCKS connected"
- when I have Seaboard Block input disabled, I can select "Take control of BLOCKS", so all connected BLOCKS are listed below but I cannot enable MIDI input of Seaboard Block ("Couldn't open the MIDI port" hint).
What's the purpose of "Take control of BLOCKS"? Does this option just send the setup program as Dashboard does? I made some tests and it seems that after Waveform is closed, the setup goes back to the previous one (at least Lightpad behaves this way - XYZ program is off). But on the other hand I cannot use the device because its input cannot be selected.
Btw. when switching between these MIDI options related to BLOCKS I got a blue screen system crash (Windows 10) but cannot replicate it.
-
- KVRian
- Topic Starter
- 1000 posts since 26 Sep, 2013 from The Frozen North
@MBO I was all set to try and help .. until I got down to the Windows 10 part. 
I'm using a Songmaker Kit with a Mac. The only thing I think I can answer is that I believe your guess about "Take control of BLOCKS" is correct. It sends a configuration to the BLOCKS that maps a bunch of stuff to work properly in Waveform without the need to map it yourself (mostly useful for the Loop block, I've found). As to your issues with it not showing up, I don't think I can help. They've always shown up for me.
Hopefully one of the kind folks from Tracktion can chime in and help you!
I'm using a Songmaker Kit with a Mac. The only thing I think I can answer is that I believe your guess about "Take control of BLOCKS" is correct. It sends a configuration to the BLOCKS that maps a bunch of stuff to work properly in Waveform without the need to map it yourself (mostly useful for the Loop block, I've found). As to your issues with it not showing up, I don't think I can help. They've always shown up for me.Hopefully one of the kind folks from Tracktion can chime in and help you!
-
- KVRist
- 57 posts since 18 Mar, 2018
Thanks, right now I don't have access to Mac and be able to check it with Mac next week. But I managed to run everything on Linux (Ubuntu 16.04) and it works in Linux as expected (no blocking of MIDI input if "Take control of Blocks" is selected) I returned to Windows and started again but with no success. I have a feeling that it was working before (even in another topic two weeks ago I wrote about it as if it was working at that time), maybe I'm wrong.
Dashboard works ok, Equator ok, I compiled and run all Juce Blocks demo programs in VS2017 without problems. It doesn't matter if I have Seaboard + Lightpad or just one Block connected: there is no way to have input enabled when "Take control" is on. I assume it's not a big problem as I can send all needed data earlier by Dashboard but it would be nice to clarify these things.
Dashboard works ok, Equator ok, I compiled and run all Juce Blocks demo programs in VS2017 without problems. It doesn't matter if I have Seaboard + Lightpad or just one Block connected: there is no way to have input enabled when "Take control" is on. I assume it's not a big problem as I can send all needed data earlier by Dashboard but it would be nice to clarify these things.