Hi, I'm hoping someone can help me with this as it's become quite frustrating for me..
I set up all midi learn parameters as I want them and then save the Midi Map in Speedrum as default. However when I reload the saved preset or even a new project, all my midi learn assignments either don't work or control completely different parameters. I've tried 2 different midi controllers (my Alesis VI25 & Behringer X-Touch Mini) and get the same results.
Midi CC numbers are correct in Speedrum eg Knob 1 transmits CC25 and Speedrum Vol CC assigned reads CC25 but nothing happens when I turn the knob. Another example.. I assigned a knob to control sample end point but when I load the template or a new project turning the knob changes 10 plus parameters in the layers section including sample randomisation.
Am I doing something wrong here or is this feature broken in Speedrum?
Appreciate any input on this.
Midi Map Recall issues with Speedrum
-
- KVRist
- 386 posts since 19 Aug, 2020 from Earth
Which system and which DAW / host?
When loading a kit you can include what you want to load with the kit (three buttons SEQ TRG MCC at the bottom of the browser), sequencer state, pads trigger map, midi cc map.
The current state of the pads trigger map and midi cc map are saved and loaded with the state of the plugin.
For a new instance, the default trigger map and midi cc map are loaded.
When loading a kit you can include what you want to load with the kit (three buttons SEQ TRG MCC at the bottom of the browser), sequencer state, pads trigger map, midi cc map.
The current state of the pads trigger map and midi cc map are saved and loaded with the state of the plugin.
For a new instance, the default trigger map and midi cc map are loaded.
-
- KVRer
- Topic Starter
- 13 posts since 9 May, 2019
Thanks for your response. I'm on Windows 10 / Cubase 14
I'm still getting the erratic behaviour described in my original post regardless despite wether the MCC toggles are active or not.
Could you either confirm it working as it should in either Cubase or Nuendo? If not, how can I send a small video recording to better show what's happening?
I'm still getting the erratic behaviour described in my original post regardless despite wether the MCC toggles are active or not.
Could you either confirm it working as it should in either Cubase or Nuendo? If not, how can I send a small video recording to better show what's happening?
-
- KVRist
- 386 posts since 19 Aug, 2020 from Earth
-
- KVRist
- 386 posts since 19 Aug, 2020 from Earth
I'm sorry, but I've been busy, so I haven't had time to configure the test PC to match the requirements yet.
-
- KVRer
- Topic Starter
- 13 posts since 9 May, 2019
As there hasn't been any update since (and unless confirmed otherwise by any other Cubase users) the midi learn maps function in v2.2.2 doesn't work so am going to discard my attempts in resolving it. Hopefully it can be addressed in the next update.
-
- KVRist
- 386 posts since 19 Aug, 2020 from Earth
Ok, I can reproduce it, although I can't say what the problem is yet. Thanks for reporting it.