Arturia Forums
Hardware Sequencers => BeatStep Pro => BeatStep Pro - Technical Issues => Topic started by: Spiegelneuronen on March 04, 2018, 11:32:55 pm
-
Hi friends of Arturia!
Yesterday I got my BSP. Im totally happy with it.
But...
I connected my Waldorf Pulse 2 to it. Now when I push record on BSP, and trigger some notes, playing with the cutoff on p2, and stop the recording, the cutoff is set back to 0 again. My P2 ist connected by Midi-cable.
That could be very awful at performing live.
Any ideas how to fix that issue?
I think this is solved. Maybe Ill have to change the record-button cc value.
Remains one question:
Is it generally possible to record the cutoff control as automation, besides the notes via BSP?
Thanks in advance for your suggestions!
-
Hi Spiegelneuronen,
I think this is solved. Maybe Ill have to change the record-button cc value.
Yes I think so too.
Is it generally possible to record the cutoff control as automation, besides the notes via BSP?
Unfortunately, no, it is not possible. BSP canly records note on, note off events.
Regards,
Y.
-
Thank you fory your reply!
For me this is solved.
-
Hi friends of Arturia!
Yesterday I got my BSP. Im totally happy with it.
But...
I connected my Waldorf Pulse 2 to it. Now when I push record on BSP, and trigger some notes, playing with the cutoff on p2, and stop the recording, the cutoff is set back to 0 again. My P2 ist connected by Midi-cable.
That could be very awful at performing live.
Any ideas how to fix that issue?
I think this is solved. Maybe Ill have to change the record-button cc value.
Remains one question:
Is it generally possible to record the cutoff control as automation, besides the notes via BSP?
Thanks in advance for your suggestions!
I have both Pulses and their CC mappings is where the issue lays. By default the BSP send CC's 50, 51 and 52 when you use the transport controls and the Waldorf standard CC map is Cutoff Freq/Filter keytrack/Filter Env Amount to CC's 50/51/52 respectively. The solution is to change the CC's that the BSP sends in MCC. I've changed them to all send omni mode-off messages (CC124), which shouldn't mess with anything unless you have set an instrument to omni mode for some weird reason.