Beatstep Pro - Play button over MIDI

[meeeearcus]

Has anybody had luck with the blank sequence? I have definitely initialized/cleared the sequencer on the Mother and had no luck.

No, the blank sequence is actually just a single note repeating. There's no such thing as a blank sequence as far as I know.

[JoeFuture]

I'm very excited to hear this. I have exactly the same problem, and it's been driving me nuts. Between this and the 0-10v output on the Pitch CV signals, using the BSP with a Mother 32 has been an exercise in frustration. I love the interface and capabilities of the BSP, so I'm really glad to hear some of the rough edges in the experience are getting smoothed out. Let's hope this update comes very soon!

[OliverAlex]

I'm very excited to hear this. I have exactly the same problem, and it's been driving me nuts. Between this and the 0-10v output on the Pitch CV signals, using the BSP with a Mother 32 has been an exercise in frustration. I love the interface and capabilities of the BSP, so I'm really glad to hear some of the rough edges in the experience are getting smoothed out. Let's hope this update comes very soon!

Hi all any news on this?
I updated recently but no changes yet , right?

I agree with Joefuture when BSP + MM32 there is not yet a satisfacotry result:
- with midi cable we run into the sequence play issue, as described in this topic
- with CV/Gate there is only a 'span' of +/- 1 octave  usable. I mean only 1 octave gives different notes, while all the notes/octaves above and below trigger the same note.

Can someone confirm that these are the issues, so that i can stop trying to solve them?

thanks

[JoeFuture]

I don't have the 2nd issue you mentioned. My problem with CV and the Mother32 is that the BSP outputs 0-10v, and the M32 expects -5v to +5v. I bought an EMW DC Shifter module to drop the BSP's pitch CV down by -5v, and that seems to have helped.

I'm currently trying to use the 3.5mm to MIDI output jack on the BSP to drive the M32, and despite turning off all MIDI transport in Arturia configuration app for the BSP, it still sends the START message and triggers the Mother32's sequencer.

[astrostasis]

So after an entire day of searching to find out what I was doing wrong and even many times skipping over this thread and the video come to find out that it seems to be a bug :/

[tshock]

Hello,

I just found this forum. i recently purchased a Korg minilogue and am having the same issue with BSP sending transport start and stop messages. I did make my sequences blank and that is an ok temp fix but I would really like to disable the midi transport controls messages. Any luck here? any update?

Thanks in advance!

[shinyless]

Bump,

I just received my BeatStep Pro and I have the exact same problem with the Mother 32. Disabling transports message in MCC doesn't solve the problem, and of course it's impossible to disable the sequencer on the Mother 32's side. Any chance to get an update on the status of this bug ?

[Terrym]

Hi , this should be fixed in the next update . i have not seen a test of this yet though so i do not know when it will be released.



Terrym

[shinyless]

Hi , this should be fixed in the next update . i have not seen a test of this yet though so i do not know when it will be released.



Terrym

Thanks for the quick reply. Can't wait for the update to be deployed ! 

[nimbo77]

Hi, first post here.

I too am having this very issue with both my Roland JU-06 and Korg Monotribe (midi modded).  I have tried turning off MCC for transport, but it still triggers the onboard sequencers on both the JU-06 and the Monotribe. This is a pretty severe bug IMO, any word on the update to fix this?

[meeeearcus]

Hi, first post here.

I too am having this very issue with both my Roland JU-06 and Korg Monotribe (midi modded).  I have tried turning off MCC for transport, but it still triggers the onboard sequencers on both the JU-06 and the Monotribe. This is a pretty severe bug IMO, any word on the update to fix this?

Sadly no, there has been no movement with the firmware upgrade for the BSP. The last update from 8/16/16 was:

Sorry for the delay.

The test team has sucessfully reproduced your issue.

This bug is now logged and will be analysed by our Dev team.

Thanks for your feedback.

[nimbo77]

Just received a reply to my ticket. It stated thhat the next update is scheduled for release in 2-4 weeks time. (crosses fingers)

[meeeearcus]

Can anyone confirm that this has been fixed in v2 firmware? I don't see it explicitly named. I can test tomorrow and report back. I'm excited to be able to use this piece of gear for my synths with built in sequencers!

V 2.0.0.2
Bug fixes
Chains are properly handled in reverse mode
Program changes are now properly handled when "Wait to load pattern" is off

V 2.0.0
Bug fixes
Shift + Swing now properly work together
Pad velocity in Controller Mode now functional
Pads now light up when setting Program Changes
Knobs can now be set to control Aftertouch in Controller Mode
Selected Pad of Drum Sequencer is properly lit in Real-Time recording
Step + Pad now working with Drums sequencer with record active
Pressing step buttons to change Project doesn't send unwanted CC messages
No more crashes on pattern change after external transpose with transpose link
Improvements to HUI protocol when using Pro Tools 10
Sequences are now properly updated with Preset Link
First pattern of a chain is now played once when Wait to Load Pattern = Off
Transpose link + chaining pattern now properly work together
No more stuck notes on Stop/Pause using analog clock
No more drifting of the MIDI clock output when using internal clock
No more notes jumped when using the Looper with MIDI, USB or Clk Sync
Exiting Looper now plays the right note information
Control mode = Knob jumping from 127 to 0 with slow acceleration

[Terrym]

Hi  i asked this question in testing and the answer i got was midi clock ,start and stop messages cannot be deactivated . only midi cc for start /stop which is different.

Terrym

[egjanuary]

I can confirm this was not fixed for using M32 with the last update.
Kind of disappointing.

"Can't be done" ?

BS