Very quick question. I just got hold of a Sensory Percussion 2 setup (I previously had V1) and I am just exploring the software while away from home so don’t have access to the sensors and portal so am using the virtual inputs. I can map speed to different parameters without any trouble but when I map timbre and use the virtual inputs to trigger sounds I only seem to get a minimum value of zero when hitting the centre pad and a maximum value when I hit any other pad (edge, rim shoulder, etc) but no values in between. Because I’m away from the hardware I can’t test if this is working fine when using the sensors. Is this just a downside of using the virtual inputs and can they not send continuous timbre values? Thanks!
Hi @MNDMTH – yeah, exactly. The timbre comes from analyzing hits on actual drums. There’s no way to get the in-between hits when just clicking on the virtual inputs, unfortunately. For sound design purposes, I’d recommend assigning something else to the same timbre param that you can control, like a macro knob, or even an LFO. Then you can just turn that off or delete it when you’re back at your drums.
Let me know if that helps
Thanks @tenoch. I thought that was the case. I’m now back at home and got it all set up with the hardware and it’s all working great. The new sensors in combination with the EVANS Portal seem to have a much more consistent response than V1. Really enjoying exploring it so far and have also got all the MIDI notes and CCs working pretty nicely with Ableton Live. The new pad input feature is super nice too. Got that setup really quickly with my Mandala drum, SPD-SX Pro, etc thanks to the great “learn” feature.
1 Like
Awesome, that’s great to hear. We still have a lot of cool stuff planned!