FW 1.4.0.20 on website

[jahasw]

There is a download link on website to a new firmware file.
Though it's dated february 12th 2016, I've not seen it before.

Check https://www.arturia.com/beatstep-pro/resources

Not many features added but supposedly fixes some bugs and seems to work mostly.

What's with the date? 

[yield27]

Dated april 5th now.

[jasonvezina]

Well I installed the firmware and it works, in that I can see the new features (the note tie thing is nice).

Unfortunately they didn't fix the issue with the tempo getting wonky when changing patterns. The reply I got from support on the issue specifically said this was addressed in the update

[faster]

THANKS....for heads up

So is it save to try? Any feedback?

[Valentin Arturia]

Unfortunately they didn't fix the issue with the tempo getting wonky when changing patterns.

The fact that tempo drift is NOT a bug !!!! If you see some drift it is not the BSP fault it's your master device (computer, sequencer...) that does not send clock accurately.

there is a post concerning this point in our faq :
https://www.arturia.com/faq/utilization/beatstep-pro-general-questions

[Zymos]

I don't think that's what they are saying- read it again- says its something happening when changing patterns.

[jasonvezina]

Unfortunately they didn't fix the issue with the tempo getting wonky when changing patterns.

The fact that tempo drift is NOT a bug !!!! If you see some drift it is not the BSP fault it's your master device (computer, sequencer...) that does not send clock accurately.

there is a post concerning this point in our faq :
https://www.arturia.com/faq/utilization/beatstep-pro-general-questions

The BSP is the only device sending clock out in my case, it IS the master device. It's running off of the internal clock and sending midi out, it isn't getting MIDI in from anywhere. Is the internal clock on the BSP broken?

[atte]

Since the logic seems to be "it's always the master that's the problem", Valentin must arrive at the conclusion that it's in fact the BSP that has problems with the clock

[atte]

Ok, installed the 1.4.0.20, and it has huge problems!

I'm running BSP as slave over USB, with renoise as master, using it only for controlling my modular (over CV). Did a lot of tests this morning with this and 1.3.0.23, recording the triggers CVs and clock CVs in renoise and measured the timing. Took me about two hours, here are my findings:

in 1.4.0.20 the triggers are delayed about 22ms compared to the clock out (and everything in 1.3.0.23):

in 1.3.0.23 the triggers are about 1ms delayed (I can live with that) compared to the clock.

This means that in 1.4.0.20 I can't use both clock and triggers with my modular. Downgraded and everythings fine again.

Additional finding:
in 1.3.0.23 there's a hickup in the clock when going from pattern to the next in renoise if "send song position pointers" is on in renoise prefs
in 1.4.0.20 the BSP actually stops sending clocks when switching renoise patterns with "send song position pointers" is on
Can't believe I didn't notice this hickup in 1.3.0.23 (didn't do this level of testing before), with 1.4.0.20 it's obvious (clock stops), so in any case "song song position pointers" should be off...

EDIT: i didn't try the new "factory reset" feature and I'm not going to, although there's a slight possibility that it might remedy the issue. I'm out of time and out of patience...

[Chi]

Ok, installed the 1.4.0.20, and it has huge problems!

in 1.4.0.20 the triggers are delayed about 22ms compared to the clock out (and everything in 1.3.0.23):

in 1.4.0.20 the BSP actually stops sending clocks when switching renoise patterns with "send song position pointers" is on

Correct! I am using the ERM-Multiclock which provides an incredibly stable master clock but the BS-"Pro"-hahaha - is the only piece of gear I own which remains unstable.  Anyone want to buy a BSPro the sequencer which cannot sequence?

[DJRickDawson]

Ive found 1.4 much more stable than 1.3 for me
synching with Ableton Live. although its more stable running slave to Ableton Live being master, rather than the BSP being master

[megamarkd]

When I updated the firmware, it defaulted all the global settings like transport cc's, transpose latch and pattern change options.  I adjusted all but the pattern change which I left as the default wait to complete option.  I have never used it like this so I'm not sure if it's something I've never seen or if it's an update thing, but now when I hold shift while in seq 1 or 2 the step buttons light up with a bluish tint on some of them.  I can't seem to work out what they correspond to.  Anyone know?

[jasonvezina]

When I updated the firmware, it defaulted all the global settings like transport cc's, transpose latch and pattern change options.  I adjusted all but the pattern change which I left as the default wait to complete option.  I have never used it like this so I'm not sure if it's something I've never seen or if it's an update thing, but now when I hold shift while in seq 1 or 2 the step buttons light up with a bluish tint on some of them.  I can't seem to work out what they correspond to.  Anyone know?
[/quote

This shows notes that are tied together.

[megamarkd]

This shows notes that are tied together.

Cheers Mate!

[guidewire]

oh hi,

I just upgraded to 1.4 and I noticed that that "16/32/48/64" sequence lights don't traverse anymore.  They still do when the << >> are pressed, but not otherwise. I guess I relied on it when playing and now that it's gone I find it super annoying.

I'll also say that I would really like it when selecting patterns it revealed which are available just like when you save a pattern it illuminates which already have content in it.