Arturia Forums

Hardware Sequencers => BeatStep => General Discussion on BeatStep => Topic started by: anselmi on June 06, 2014, 09:00:53 pm

Title: Beatstep malfunction with certain programming values
Post by: anselmi on June 06, 2014, 09:00:53 pm
Hi I recently got a Beatstep for use with my Elektron gear, sending CC with the pads

When I program the pads to send an OFF value lower than an ON value everything works as it should be

But when I do the opposite (OFF value higher than ON value) then the MIDI OUT data is wrong for the ON value...you put 10 and it sports 43...there is no relationship between the value that I program and the exported data.

I checked it using MIDI Ox

Is this a known bug or I got a faulty unit?

thanks!

Daniel
Title: Re: Beatstep malfunction with certain programming values
Post by: anselmi on June 06, 2014, 09:28:37 pm
extra data: the encoders seems to suffer from the same faulty behaviour, I mean, If you set the MIN value higher than the MAX value then the exported MIDI data doesnŽt match the values you setted
Title: Re: Beatstep malfunction with certain programming values
Post by: anselmi on June 09, 2014, 08:58:32 pm
nobody found this problem before?
Title: Re: Beatstep malfunction with certain programming values
Post by: zedius on June 11, 2014, 04:12:56 am
I can confirm this problem. With a toggle switch control programmed for off value of 90 and on value of 20 my actual off value was 90 but my on value was 127.

With an encoder set to control, absolute with a min value of 90 and max value of 20, the actual midi data output was 127 for both clockwise and counterclockwise turns.

Title: Re: Beatstep malfunction with certain programming values
Post by: anselmi on June 11, 2014, 05:06:07 am
thanks zedius!

IŽd like to read what Arturia people have to say about this...I bought the Beatstep just to be used in a way it canŽt because of this bug

Knowing this problem IŽd get any other controller

Please fix it ASAP
Title: Re: Beatstep malfunction with certain programming values
Post by: Terrym on June 11, 2014, 10:10:52 am
Hi i think this is fixed in the upcoming firmware update coming very soon.

regards

Terrym