arturia keystep step position with launchpad pro

I wanted to use the bomebox with my keystep and launchpad. The keystep is great but I hate not being able to see the step position so I would like a tip on how to show the step position by lighting up the step on the launchpad pro in red and any sequencer notes that are being played from the keystep if possible showing in green. I am sure the bomebox was made for this. I have mt pro licence. it would be nice to use the launchpad to send a note to the keystep to record it in the sequence but I think its best to stay simple first.

Hi,

Here is a summary of what you need to do.

  1. Set up a MT Pro project file on your computer to do this. Later you will upload to Bomebox if you do not want the computer involved. The project file should have at least 2 presets. One for the MIDI going from the Beatstep to the application or device, and the other for going from the Beatstep to your Launchpad for status.
  2. At the project level you define both the input device and 2 output devices. I would assign aliases for all devices as this will let you make it easier to use them if the BomeBox decides to call the raw device something differenton you computer.
  3. Under the preset “Preset to App/Device”. You would then only define input from Beatstep out output to device (overriding project default routing)
  4. You would then put any translators there for handling whatever you want to send to the App/Device. I assume so far you have all of this working
  5. On the other preset which I call “LED Feedback to Launchpad”, you define the Beatstep for Input and Launchpad for Output which again overrides the project defaults. This is where you will put your translators going to the Launchpad.
  6. On the translators to launchpad you essentially use the same inputs as you would normally do to the device/application but the output message would need to be modified for what the Launchpad needs. You could probably start by copying and pasting the translators from the other preset and the modifying the output.
  7. On the Novation site, download the Launchpad Manual, it will tell you what note or controller each button generates. If you can find that, you can temporarily assign launchpad as input and push the button and write it down. The output note or controller will be the same as the input note or controller. The velocity will be the color you want to produce. Do a search on “launchpad color values” or something like that on google and you should be able to see the velocity assigned to each color. If you can’t find it, let me know.
  8. Now modify each translator output in the “LED Feedback to Launchpad” preset for the desired output. Keep in mind the launchpad buttons are momentary, so you will need to have a global variable maintain the state of each LED. A typical translator will have

input: (whatever input Beatstep produces)

rules

 

// ga us the global variable we use to track the button

// state. It will be different for each translator/button

// This toggles the value of ga from 1 to 0 and 0 to 1

ga=ga^1

// This sets note on or of on MIDI Channel

// note on

if ga==1 then pp=90

// note off

if ga==0 then pp=80

// velocity send color value 0=off

if ga==0 then qq=0

// velocity – set this to the color value you want . I think 127 is yellow

if ga==0 then qq=127

Output Raw MIDI ga pp qq

Now do this for every LED you want to light.

When you are done, you can the upload the project file to BomeBox and start the project there. In BomeBox you will need to assign the proper ports to the aliases you set up first.

Let me know if I can be of further assistance.

Steve Caldwell

Bome Q&A Moderator and

Independent Bome Programming Consultant/Specialist

P.S. If you are not using a translator for notes going from Beatstep to App/Device. You can simply draw lines on the main project file between them. Anything going through this path will pass through directly to your App/Device. But if you do this, make sure in the LED Feedback Preset you have \"swallow\" turned off in each translator, otherwise any translators will not allow that specific event to pass through.

 

The part I am unsure of, when I use mtpro in this way should the launchpad be plugged into the usb port of the computer or the bomebox and same rule applies for the keystep, of course when they are being used in isolation away from the computer will the bomebox still find them if I set them up on mtpro via the computers usb? I hope that makes sense.

When you set it up, you attach and test everything on your computer. Once you have it working there, you upload the project file to the BomeBox and start it there. You will need to attach your devices to BomeBox instead of the computer at that time.
When you start it on BomeBox, you may need to go to the web interface initially to ensure your aliases are properly defined. This is a one time thing. After that, any time you restart BomeBox, it will start with it’s last project file and you needn’t do anything from there.

A lot you said below I am un familiar with as I am new to mtpro and bomebox. I will have a look at the novation and keystep specs. I am assuming that I can capture the start signal from the keystep and advance the launchpad position indicator somehow as obviously I dont think anything is sent from the keystep as to its actual position, I guess thats related to the keysteps tempo.

OK, go ahead and give it a try and if you get stuck you can post your project file and where you are and I should be able to help from there. Do everything and get it working with your computer before you try moving the project over to BomeBox.

There is also a link on this page to our tutorials. They can be quite helpful. I recommend you start by just reviewing the first two. This should get you familiar with the MT Pro interface.

Launchpad MK 2 color chart:

http://forum.launchpad-pro.com/viewtopic.php?id=4055

Lauchpad MK2 Note Layout. Left diagram is the mode it powers up in.

 


Attachments:
![](upload://mNfEzbRqeTj3feO3WVUgFP9D7sT.png)

ok I got the physical part done I think, I am not sure what to do next. I know I guess I need a translator to advance a light on the steps somehow.

 

Ive added the project file so maybe you could confirm the setup is ok.

 

Then I guess the question is how to go about the translators. Ive set the midi in to the launchpad pro too just in case I can send that to the keystep without creating a midi loop.

I am thinking that it will be impossible for the launchpad or translator to know the keystep sequencer length so I guess I have to set it to 64 and leave it at that.

Unless of course the keystep sends its step position in a stream.


Attachments:
1525013888451_Keystep-Visualiser.bmtp

I think the keystep sends the standard FA message for start so I think I need to find that first first in a translator then work out the f8 sync messages they appear a lot in between sequenced notes.

Hi,
From what I understand, you want to know the current step sequence by lighting LED’s as each step in the sequence occurs. If it is an 8 step sequence you would use the first 8 lights. If a 16 step sequence, the first 16 lights. Is this correct?

In order to do this, we need to decide what MIDI signals the Keystep sends out at each sequence. This I don’t know and it is unclear to me in the manual that I found. Do you know?

For instance if you can get it to output MIDI notes 0,1,2,3,… in order based on the current sequence steps, it would be a simple matter of translating these notes to light messages on your Launchpad Pro. However, it is possible that you cannot get your KeyStep to do this. We might have to use MIDI sync signals and then set up a counter to determine which step we are in the sequence. If we do that, we would have to first, have a mechanism to set the sequence at 0 at start of play. We could do this by monitoring the MMC play message if the device sends this or MIDI time clock start . Otherwise we would probably need to manually reset the counter to 0 and then start the sequencer and then count sync messages from there.

The MIDI trigger for a MMC play command is F0 7F 7F 06 02 F7
Input for midi time clock start is FA
Input for midi time clock clock is F8

According to the below link, F8 would be sent at a rate of 24 per quarter note. We would use this to calculate how often we need to increase the sequence count (light).

See : https://en.wikipedia.org/wiki/MIDI_beat_clock

If you can turn on logging in MT Pro and then start a short sequence, maybe we can determine what your KeyStep is sending and take it from there, or if you could provide more information on what MIDI messages your KeyStep output would support that we could use in MT Pro to trigger sequence events.

Steve

You might want to also read this post and do a search on this site for “sync”

https://www.bome.com/forums/viewtopic.php?t=4706

In the cross over time I found a similar post about the counting and the wiki article. I will create a known sequence and see what it spits out. I’ve seen the fa start message and f8 timing messages but I guess it also depends on the time division setting too but not sure. Yes you are correct in fact the sequence can be any length but let me set up a simple 8 step pattern using 16th notes and see what it spits out. Your response is correct about what I am trying to achieve.

Try this.

 

You may need to change the note numbers in the translators “Timing Clock” and “Stop Sequence”

I’m using a LaunchPad MK2 and I think the note numbers on a Launchpad Pro might be different.

 


Attachments:
1525024441813_Keystep-Visualiser-2018-04-29.bmtp

This is what the keystep spat out with 8 notes division 1/8

Note Off on ch. 1 with note:50 (0x32) and velocity:64 (0x40)
Note Off on ch. 1 with note:50 (0x32) set ‘pp’ to velocity
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI 90 34 64
Note On on ch. 1 with note:52 (0x34) and velocity:100 (0x64)
Note On on ch. 1 with note:52 (0x34) set ‘pp’ to velocity
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI 80 34 40
Note Off on ch. 1 with note:52 (0x34) and velocity:64 (0x40)
Note Off on ch. 1 with note:52 (0x34) set ‘pp’ to velocity
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI 90 35 64
Note On on ch. 1 with note:53 (0x35) and velocity:100 (0x64)
Note On on ch. 1 with note:53 (0x35) set ‘pp’ to velocity
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI 80 35 40
Note Off on ch. 1 with note:53 (0x35) and velocity:64 (0x40)
Note Off on ch. 1 with note:53 (0x35) set ‘pp’ to velocity
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI 90 37 64
Note On on ch. 1 with note:55 (0x37) and velocity:100 (0x64)
Note On on ch. 1 with note:55 (0x37) set ‘pp’ to velocity
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI 80 37 40
Note Off on ch. 1 with note:55 (0x37) and velocity:64 (0x40)
Note Off on ch. 1 with note:55 (0x37) set ‘pp’ to velocity
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI 90 39 64
Note On on ch. 1 with note:57 (0x39) and velocity:100 (0x64)
Note On on ch. 1 with note:57 (0x39) set ‘pp’ to velocity
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI 80 39 40
Note Off on ch. 1 with note:57 (0x39) and velocity:64 (0x40)
Note Off on ch. 1 with note:57 (0x39) set ‘pp’ to velocity
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI 90 3B 64
Note On on ch. 1 with note:59 (0x3B) and velocity:100 (0x64)
Note On on ch. 1 with note:59 (0x3B) set ‘pp’ to velocity
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI 80 3B 40
Note Off on ch. 1 with note:59 (0x3B) and velocity:64 (0x40)
Note Off on ch. 1 with note:59 (0x3B) set ‘pp’ to velocity
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI 90 3C 64
Note On on ch. 1 with note:60 (0x3C) and velocity:100 (0x64)
Note On on ch. 1 with note:60 (0x3C) set ‘pp’ to velocity
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI 80 3C 40
Note Off on ch. 1 with note:60 (0x3C) and velocity:64 (0x40)
Note Off on ch. 1 with note:60 (0x3C) set ‘pp’ to velocity
MIDI F8
Timing Clock
MIDI F8
Timing Clock
MIDI 90 30 64
Note On on ch. 1 with note:48 (0x30) and velocity:100 (0x64)
Note On on ch. 1 with note:48 (0x30) set ‘pp’ to velocity
MIDI B0 33 7F
Control Change on ch. 1 with CC#:51 (0x33) and value:127 (0x7F)
Control Change on ch. 1 with CC#:51 (0x33) set ‘pp’ to value
MIDI 80 30 40
Note Off on ch. 1 with note:48 (0x30) and velocity:64 (0x40)
Note Off on ch. 1 with note:48 (0x30) set ‘pp’ to velocity
MIDI FC
Stop Sequence
MIDI B0 33 00
Control Change on ch. 1 with CC#:51 (0x33) and value:0 (0x00)
Control Change on ch. 1 with CC#:51 (0x33) set ‘pp’ to value

 

I will look at this and try to get to grips with it. Thank you

I tried this after making sure the ports were ok and the launchpad pro does nothing, yet, so it must be a value somewhere in the rules

I found this maybe it helps, maybe I need this in hexa decimal

 


Attachments:
![](upload://l9bWvgkJNISOHBNHT55oXubl0GN.jpeg)

I also found this.


Attachments:
![](upload://gDIEb9jT2lVd3AJ5KR8ynfJZc6k.jpeg)

this picture is the wrong mode the programmers mode matches the send sequence rule but I think the message is not right as the lp does not light up