Can you make the pads fixed velocity?

[circuitslave]

I know the pads on the Beatstep Pro are velocity-sensitive, but can you turn this off? or set to maximum when playing in real time?  Just curious. Thanks.

[DarkStar679]

I would say in the control center the min velocity value setting to max would be a solution.

[circuitslave]

I would say in the control center the min velocity value setting to max would be a solution.

Okay, thanks, for the info, Darkstar679! 

[circuitslave]

I would say in the control center the min velocity value setting to max would be a solution.

I tried this and saved the template after all pads were made 127 and it didn't work. After loading the template. All the pads still have velocity in Ableton 

[Koshdukai]

When you say "saved" was this as in "saved to disk, on my computer" or did you do a "Send To..." the BSP ?

[Danyx]

Same problem here, anything new?

@koshdukai: what do you mean by "send to" the BSP? When you're synced isn't it supposed to be sent automatically if you change a value in the control center?
This is how it reacts when I changed the MIDI ports of the pad but nothing happens when I changed velocity...

[Danyx]

Up!
Still struggling with the velociry thing....
In the MCC I put all my min velocities on 127, then I click on "store to", the MCC seems to send something to the device (progressing bar) and then... Nothing's changed on the device...

Any idea?

By the way, I'm on 1.2.0.6 but I do not see the sync button at the top left any more...My device seems to be connected but not synced. Could it be that?

Thanks

[megamarkd]

Try setting min velo. to 126.  I've had no issue with setting min velo. to 78 and max at 127.  I do have to thump pretty hard to get a 127 value though.

[Danyx]

Tried the 126 trick but nothing happened...
I tried to change the note of pad 1 to c# and it worked but nothing happens when I change the velocity...

I begin to think it might be a bug...

[megamarkd]

Hmm, are you sure it's sending the settings to the BSP successfully?  I've no issues with the max and min velocity settings, but then again I seem to still be able to use the sync button in MCC (dunno how I can when so many say they can't).  It doesn't see the BSP at first, then I fiddle a bit with which instrument MCC is editing and when I tell it to start editing the BSP again, the sync button available.  It's not always like that, but I'm yet to encounter the no sync button thing.

[Danyx]

It does send the changes I've made on the MIDI note of Pad 1 but nothing happens when I change the velocity...

About the sync button, I was wondering: is it still supposed to show up since the last MCC update? Arturia wrote:
"BeatStep Pro Sync function was replaced by drag and drop between device memories and local templates."

So did this button disappear??? Or I should see it?
I tried to delete the beatstep pro from my audio/MIDI config but the sync button is still not here.... And the sync option in the device menu is greyed out.
:-(

[turbo_kev]

Hi the sync button  is NO LONGER AVAILABLE  in the latest version of the MCC

cheers
kev

[Danyx]

Thanks Turbo_Kev!
Maybe Arturia should also remove the sync option in the device menu, it would be easier to understand.

I tried to replace the "store to" by "drag & drop", every parameters seem to be transmitted to my device except for...the velocities settings of course: when I record a MIDI track in my DAW (test on bitwig & protools) it keeps on recording different velocities.
Maybe I'm missing something into my DAW MIDI inputs setup? My BSP is plugged via the USB cable and I've selected MIDI & USB as MIDI Ports. Any idea?

[Danyx]

Surprised that nobody from arturia gives help on this thread...
Should I open a ticket with the support???

[Terrym]

Hi the velocity setting are for the pads on the bsp . so if you record from another controller the velocity will be recorded also.


regards


Terrym