raphaelquast/beatstep

A Midi Remote Script for Ableton Live 10 & 11 and the Arturia Beatstep controller

beatstep's Issues

return tracks are not deleted

• delete track in control-layer does not work with return tracks

use shift button to stop recording

• when no control-layer is active, use the shift button to stop recording a loop
  • shift is easyer to reach than stop -> better for timing

function-buttons send notes when pressed

currently shft, chan etc. send notes to midi-tracks!

add a layer to launch tracks

Add a dedicated control-layer to use pads as track-launcher

• both pad-rows should function as track-launcher
  (e.g. extend red box to 2 rows if activated)
• bottom row should automatically move "red-box" 1 layer down

double tap shift button

• double tap shift button to activate shift-pressed layer until shift is pressed again

Not working on Live 9 (Windows)

I downloaded and unzipped the latest release (v2.0) and copied the entire folder into my MIDI Remote Scripts directory. BeatStep Q shows up as a control surface option in Ableton, but after it is selected, none of the buttons/encoders function as they are supposed to. Is this something that can be solved with troubleshooting, or has Live 9 support been stopped?

I really love the idea of this tool! Thanks for putting it together

implement button to change "pad velocity curve"

The midi note velocity is always 127 instead of sensitive to velocity

transpose notes not correct after shift-pressed

transposed notes not correctly re-assigned

"load device on new-track" always creates a return-track

• using shift+ button 15 in the browser-layer always creates a return-track alongside the required new track

update overlay to include sequencer assignments

• the current overlay does not include the sequencer assignments

Live 11 script

Hello - this isn't an issue w/ your beatstep script, but a question. I've been trying to write a script for Live 11 (has to be 11) for one of my controllers and have had a horrible time. Mostly just bootstraping and improting things correclty which I dont' really understand for MIDI controllers. I'm decent w/ Python and the Live API but I'm having a terrible time getting started. I was hoping to get a paid working session with you, who clearly does understand this stuff, to get me off the ground.

Thanks, and yes that's a pic I took of Scientest in a studio as my avatar,

• TCB

scroll encoder not working when master-track is selected

change transpose encoder control for launch-layer

make the transpose encoder control master volume on clip-launch layer

disable sequencer lights while in cntrl mode

... the moving blue led (e.g. the tempo indicator of the sequencer) interferes with the light indications of the control-surfaces...
so far I have no idea how to disable those lights...

If anybody has an idea on how to change / disable the light-indications from the sequencer, some help would be highly appreciated!

updates for v1.4

• use recall, store , and chan to switch layers

  • use cc's instead of notes to avoid problems

• implement better device-controls

  • scroll through devices
  • activate / delete /collapse devices

• control 7 instead of 6 tracks

• get rid of "change light mode" button... (I never use it)

• simplify control assignments (use logical shift-pressed second functions where possible)

• update assignments image

• update readme

Device parameter issue

Hi, thanks for your great work on this, its just what I've been looking for since getting a Beatstep. I am using the most up to date midi script (1.8)

I am finding that when the beatstep is first connected to ableton the encoders (1-4 and 9-12) work the device parameters in ableton as expected in the initial layer, but if change to another layer e.g. the shift layer or control layer, then return to the initial layer, the encoders no longer function in either the initial layer or in the shift layer. They seem to work fine for manipulating the device parameters in the control layer and when the shift layer is used from the control layer.

devices not properly deactivated

device controls remain active in

• launch layer
• when switching from control to sequencer

delete track not working for return-tracks in "shift-layer"

Midi Learn on VST's

Hello community. A big congratulations and a big thank you Raphael for your work and your script which transforms the Beatstep into a real versatile controller.

However, I am unable to map encoders 1-4 & 9-12 on VSTs like Kontakt or Analog Lab, whereas with Ableton's effect or instrument macros, the mapping is done automatically and perfectly.

It's as if they were not recognized by the VST, is this normal?

Thanks in advance

avoid overwriting notes

don't overwrite existing notes when changing start-time or end-time of clip in midi sequence editor

ensure consistent scroll encoder sensitivity

• check/set sysex-states of the encoders
  • sometimes the return-values "jump"

add installation instructions for MAC to readme

• right-click the Live-icon in your program-folder and chose "show-contents"

• navigate to:
  /Contents/App-Resources/MIDI Remote Scripts/

associated discussion: Reddit - question

... wait for confirmation from a MAC user before putting it in the README

MacOS compatibility is not yet working... need to fix #58 before putting this into README

roadmap for v1.5 (assignment changes)

• exchange pad-rows in "track control" layer

• make the top row "mute/solo" tracks and the bottom row "arm" tracks (this fits better to ableton's UI)

• switch light indicators if "shift-pressed"

• again the bottom row should indicate the "arm" state and the top-row the "track-type"

• change encoder assignments in "clip-launch" layer

• the encoders should behave similar to the "track-control" layer (to easily change volume, pan and sends of each track)

• overlay design

Problem with knobs acceleration

How to control knob sensitivity?

implement browser-control feature

This is a general issue to keep track of the progress in implementing a browser-control feature.
Any ideas on what is needed or help on the implementation is highly welcome!

• basic browser controls

  • scroll
  • expand / collapse

• extended control
  (general functionality is there... just obtaining the right item remains a mystery... see ❓ )

  • prelisten samples
  • swap instruments
  • swap effects

❓ it's unclear how to access the currently selected browser-item via the python API... any help on this is highly appreciated!

not always initializing properly

I try to use this script but it's not always initializing properly because sometimes the encoders still send on channel 1 instead of 10,
and I don't see any errors in the Log file

comments ? leave a message!

shift-pressed behaviour is active if control-layer is not permanent

shift-pressed behaviour is active if control-layer is not permanent and:

• (cilp-launch) group slot tapped
• (layer 2) scene muted

Doesn't show up in Ableton 11

Hi, sorry to bring up such a fundamental question, but I installed it in the appropriate directory ( I think) X:\ProgramData\Ableton\Live 11 Suite\Resources\MIDI Remote Scripts\beatstep-2.0
When I open Abletone>Options>Preferences Beatstep Q is not in the MIDI devices list.
I'm using Ableton Live 11.3.3, and Windows 11.
Thank you for your time!

implement a sequencer/note-editor layer

controls

• 16 notes

• note-controls

  • mute state
  • velocity
  • pitch
  • start time
  • duration
  • random
  • transpose
    • all notes of selected clip
    • only notes in loop

• loop-controls

  • length
  • position

• LED feedback

  • playback position
  • note state (muted / active)
  • indicate that notes are inside/outside of loop

• general

  • update assignments images
  • update overlay design
  • focus note view on sequencer-activation
  • initialize different sequence-quantizations (e.g. 1/2, 1/4, 1/8, 1/16 notes)
  • initialize different sequence-tempos (e.g. 1, 2, 4, 6, 12, 16, 32, 64 beats sequences)
  • initialize different sequence-velocities (e.g. 0.25, 0.5, 0.75, 1)
  • allow transposing notes while in sequence-initialization layer

problem with MacOS

initialization is not performed properly on some systems using MacOS + Ableton 10

• still unclear where this problem comes from... (MIDI driver?, Ableton?, Python?, ...)

Any help on identifying problems of Beatstep_Q with MacOS + Ableton 10 is highly appreciated!

switch "mute/solo" and "arm" in track-control

• having "aim" in the second row fits ableton's UI better

control track volume & pan with encoders in clip-launch and track-control

• it's more intuitive and useful if the encoders react to the tracks in clip-launch