arturia keystep step position with launchpad pro

peter.andaluz

2018-04-28 11:43:39

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.

Steve-Bome Forum Moderator

2018-04-28 16:36:41

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.

 

peter.andaluz

2018-04-28 18:24:58

comment

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.

Steve-Bome Forum Moderator

2018-04-28 18:38:18

comment

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.

peter.andaluz

2018-04-28 18:48:18

comment

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.

Steve-Bome Forum Moderator

2018-04-28 18:56:23

comment

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.

Steve-Bome Forum Moderator

2018-04-28 19:19:38

comment

Launchpad MK 2 color chart:

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

Steve-Bome Forum Moderator

2018-04-28 19:22:19

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

 


Attachments:

Launchpad-MK2-Note-Layout.PNG

peter.andaluz

2018-04-29 17:01:49

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:

Keystep Visualiser.bmtp

peter.andaluz

2018-04-29 17:53:18

comment

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.

Steve-Bome Forum Moderator

2018-04-29 18:06:41

comment

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

Steve-Bome Forum Moderator

2018-04-29 18:18:35

comment

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

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

peter.andaluz

2018-04-29 19:15:48

comment

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.

Steve-Bome Forum Moderator

2018-04-29 19:54:05

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:

Keystep-Visualiser-2018-04-29.bmtp

peter.andaluz

2018-04-30 09:58:28

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

 

peter.andaluz

2018-04-30 10:00:20

comment

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

peter.andaluz

2018-04-30 10:25:44

comment

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

peter.andaluz

2018-04-30 10:56:16

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

 


Attachments:

lppronlayout.PNG

peter.andaluz

2018-04-30 11:11:18

I also found this.


Attachments:

lppronlayout2.PNG

peter.andaluz

2018-04-30 11:59:11

comment

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

Steve-Bome Forum Moderator

2018-04-30 15:27:39

comment

Yes, I believe the LP Pro has a different LED map than the LP Mk2. You would think that since it is the same manufacturer, they would make them the same. It is even different that the LP MINI but I understood that since the lights on the LP MINI are only two primary colors.

Steve-Bome Forum Moderator

2018-04-30 15:31:26

comment

The only thing I see missing is the start message.

FA

Maybe you will need to start it manually or with the first timing clock.

Steve-Bome Forum Moderator

2018-04-30 15:34:28

comment

Yes, most computers calculators have a conversion (programmers) mode to help you with the coversion.
If you go to the Novation Music site and search on Launchpad Pro Programmers Reference Guide, you should find what you need

Steve-Bome Forum Moderator

2018-04-30 15:43:01

comment

Also, if you enter the values in rules in hex (ie ox0a), when you come back to them MT Pro will convert them to decimal (10) automatically. So you might as well enter the values in the rules in decimal.

peter.andaluz

2018-04-30 16:14:48

I found the programmers manual and I believe the project translator pp numbers are correct but I am not sure if the output message is correct it looks too long but I am not sure. The programmers note layout is attached.


Attachments:

1525024441813_Keystep-Visualiser-2018-04-30.bmtp
lppronlayout2.PNG

Steve-Bome Forum Moderator

2018-04-30 16:21:24

comment

Apparently this device has different modes each with their own note layout. You might want to ensure that it is in the mode you want. Look at page 4.

In the output, I’m turning on the new note and then turning of the last note.
90 pp 127 = Note on
80 qq 0 = Note off (last note)

peter.andaluz

2018-04-30 16:43:24

comment

Ive put it in the programmers mode as that corresponded I believe to the project file that was sent where it starts at 81 decimal for pp. The message makes sense now. So I wonder why it doesnt light up.

peter.andaluz

2018-04-30 16:55:31

comment

Success! The controller has to be on port 2, so now I have 16 lighting up so just to amend the rules to use all the grid. I dont know what the sequencer spits out so we know when it gets back to its repeat cycle. The keystep has a max of 1 to 64 steps.

Steve-Bome Forum Moderator

2018-04-30 16:55:53

comment

81 would be in stand alone mode programmer layout. I’m not sure what the default is. If Note layout it would be 71 (both in decimal). I would recommend that upon startup you send the Sysex to put in the mode you want to ensure consistency. F0 00 20 29 02 10h 2D 01 F7 – Stand alone mode F0 00 20 29 02 10h 2C 03 F7 – Programmer layout Then 90 51 7F should light up the first row column 1 (51 is hex for 81 decimal)

Steve-Bome Forum Moderator

2018-04-30 17:16:37

comment

Glad to hear you are making progress. Looking forward to seeing the final solution. Maybe you can post it here for others when done? Also once you get working, please mark the thread as resolved. Let me know if you run into any other snags, Peter.

Steve

peter.andaluz

2018-05-01 08:50:37

Ive attached a 64 step version so far matched to the color red the same as the keystep.

It goes to programmer mode now as you suggested.

 

The sequence length is interesting as the keystep appends dynamically so I think its best left across the whole grid of 64 and the shorter sequences just repeat around that. Of course your ideas are welcome.

The note mode would be nice as I could see the notes the sequence is playing but mapping then might be problematic.

I wonder if I could set the length first before i start the sequence by pressing the desired length but not sure about it.

maybe other users can give some thoughts too as I would like this to show off the beauty of the bomebox and MT pro


Attachments:

1525024441813_Keystep-Visualiser-64 step working.bmtp

Steve-Bome Forum Moderator

2018-05-01 14:34:05

comment

Hi Peter,

I’m glad you got it working and thanks for posting! Yes, you could set the length by maybe doing something like this.

Set up a translator to monitor incoming notes from your Launchpad Pro to set the length. You can have it monitor the note value and set a global variable based on the note value (button pressed). Then in you current translator that cycles through the note (Send Sequence) put in a line that monitors for that note value and when equal, restart the sequence. from there.

Steve-Bome Forum Moderator

2018-05-02 07:07:13

Hi Peter,

I made a few mods to your project file but I don’t have a Launchpad Pro to test it.

  1. Instead of hard coding each number played, I calculate it based on the note counter
  2. I set a last note to play so you can restart the sequence at any pad you wish.
  3. I use a one shot timer (named Init) to initialize global variables either the start sequence or pressing computer keyboard ESC key

 

To change the number of steps, you set the global variable gg in the Init Preset, Init Global Variables translator.

I also document and initialize all global variables here.

All the calculations and heavy lifting is done in the KeyStep Visualiser Preset, Send Sequence translator

I hope you find this useful.

Steve-Bome Forum Moderator

2018-05-02 07:08:19

Whoops, here is the attachment


Attachments:

Keystep-Visualiser-64-step-working-caldwell-2018-05-01.bmtp

peter.andaluz

2018-05-06 16:16:58

Ive created a new version that has a global variable gs ive split out a 16 step and 8 step translator. each individually will work, if i have both translators ticked then the 16 will work if i press pad 16 to set the variable but the 8 step will not work unless the 16 is off. I am not sure why that is.

However I think it is getting close. I guess I need 64 translators and I would like to set the length to whatever.

I had hoped I could use just one translator and have an if then end block but I wasnt sure that was possible so I went for a different translator.

A point in the right direction would help a lot as I just cannot see why the translators are conflicting. I think its a translator mindset thing.


Attachments:

1525024441813_Keystep-Visualiser-64 step input step size.bmtp

peter.andaluz

2018-05-06 16:24:17

comment

Ive just posted a new comment, I didnt see how I could restart the sequence from the launchpad pro, yet so havnt restarted from within the one code block.

Youll see what I did in latest post before this one now. it is crucial that the sequence size remain identical to the keystep but I think thats best done manually and set before I start the sequencer for now.

Steve-Bome Forum Moderator

2018-05-06 19:36:53

comment

H Peter did you try the one I created and attached ?

Keystep-Visualiser-64-step-working-caldwell-2018-05-01.bmtp

The way I set that up is you could change the last LED by changing the global variable gg. This can be changed in Preset 0 Translator 1 or you can set up other mechanisms to change the variable gg if you would like.

I also calculated the LaunchPad Pro LED lights to light instead of hard coding them.

If you look at rules under 1.2 (send sequence) you can see the calculations. I calculate the right note value by row and column.
According to the documentation Row 1 square pads are 0x80 – 0x89 Row 2 0x71-0x79 etc. I don’t have a Launchpad Pro so I hope my calculations are correct.

Please check it out before spending more time on yours. You can actually set the length of the sequence to stop
at any note number.

Steve-Bome Forum Moderator

2018-05-06 20:13:08

Hi,

I found a few bugs in last version. Try this one instead.  Turns out programmer mode of Lauchpad Pro has same notes as Session Mode in LaunchPad Mk2 so I was able to test it.

You can press any of the square pads on your Launchpad Pro and it that sets the last note sequence of your lights.

 


Attachments:

Keystep-Visualiser-64-step-working-caldwell-2018-05-06.bmtp

peter.andaluz

2018-05-07 07:55:04

comment

I missed this one.

peter.andaluz

2018-05-07 17:49:24

I have added a translator to get the value put iit in a global variable then ive assigned that to the other translator variable. it now wants too start at the second block column and then it reverts to the first thereafter. I tried to make it set a value first based on my choice before I start the sequencer then dynamically during the sequence after that. It makes sense to me that I might stop the sequence and alter the length but as soon as I do that it starts at column two again. However, I think it is close.


Attachments:

1525237696662_Keystep-Visualiser-64-step-working-caldwell-2018-05-01.bmtp

Steve-Bome Forum Moderator

2018-05-07 17:54:36

comment

I have a new version that I created after posting the one I did yesterday.
It will clear the sequence when you set your last note and also turn off all pad LED’s
I fixed a bug that always ensure that it goes back to the first column when it hits note 18. The issue before is if you pressed a key to set the last note and the sequence was already past that note, it kept going.

I will post shortly when I get back to my PC. On my Chromebook right now.

peter.andaluz

2018-05-07 18:04:26

comment

Thats cool, yes I was playing around with it in the code this morning. Ok I think our time zones are quite apart as its my evening now and I just had a double eye procedure so cant see properly so I will sign off. I look forward to seeing it, the coding methodology is fascinating. I tried to find in the translator where the magic was taking place mathematically but I couldnt find it.

Steve-Bome Forum Moderator

2018-05-07 19:02:33

Hi Peter,

Here is the latest

The calculation for note number is found in 1.0 “Send Sequence LP Pro”

// This sets the last note Last note played. We use that to turn of previous note on
qq=gf

// This is a general purpose counter. We set at 0 when we start the timer and increment it each time it

// runs.  We set it back to 0 when we have completed the sequence
ga=ga+1

// This looks at sync signals. It is a  MOD operator and will set rr to 0 every 24 sync signals
rr=ga%24

// If it is not a multiple of 24, we move on without doing anything else
if rr!=0 then exit rules, skip Outgoing Action

// gc is used to calculate the note to play. It is the base number where all note calculations are done
gc=gc+1
// skip over 9 and 0 – We are only insterested in 81-88 71-78  etc if it ends in 0 we want to skip over it

// Again we use  the MOD operator to determine if it is a multiple of 10

pp=gc%10

// We also skip over if the remainder is 9  (ie 89, 79, 69 etc)
if pp==9 then gc=gc+1
// Calculate led to light
// gd = row ge = column
// calculate column
ge=gc%10

// If remainder is 0 we increment the note value
if ge==0 then gc=gc+1

// and set to the next column
if ge==0 then ge=ge+1
// calculater row

// Since rows go from top to bottome down, we have to reverse 10’s digit (which is row number)
gd=gc/10
gd=8-gd
// put together 10’s digit is row (reversed) and 1’s digit is column
pp=gd*10
pp=pp+ge
// pp now contains the note number
// capture last note for next iteration
gf=pp

// reset gp counter
ga=0
//set this to the last note (light displayed) before restarting
if pp==gg then ga=0
if pp==gg then gc=-1

// Special case to ensure we never go past last note on pad

if pp==18 then ga=0

if pp==18 then gc-1

 

You can find what every global variable is used for in 0.1 Init Global Variables

 


Attachments:

Keystep-Visualiser-64-step-working-caldwell-2018-05-07.bmtp

peter.andaluz

2018-05-08 16:03:37

comment

This one works with the exception that if I stop the sequencer and start again it doesnt start from the first column first row it starts from second column first row. Cell 82

Steve-Bome Forum Moderator

2018-05-08 16:34:16

Hi Peter,

 

Try this version.  It actually has support for LaunchPad Mk2 and APC40 MK2, but it should open with only presets open for Launchpad Pro.

When you open it it will prompt you for aliases for the other devices. You can simply select "None- Don’t ask again".

 


Attachments:

Keystep-Visualiser-64-step-working-caldwell-2018-05-07a.bmtp

peter.andaluz

2018-05-10 17:35:24

comment

I think this is the latest. I am finding that it works but if I stop the keystep sequencer, then restart the sequencer the visualizer will then only ever start on cell 82 and not on cell 81 after the restart.

Steve-Bome Forum Moderator

2018-05-10 17:43:12

comment

Hmm, check the translator for the stop sequence. I’m not at my computer right now but if I remember gc should be set to negative 1 and ga to 0. You can set it either at the end of the stop rules or at the beginning of the start rules.

The translator that sets the lights looks at gc and calculates which light to set from there. I set it to -1 so that when the timer starts it starts at 0. The timer increments by one at the beginning of each iteration.

If you get stuck, chime in again and I will help. The objective of this board is not just to do it for you but to help you understand how it is done yourself to make you more self sufficient. It you want a complete solution, I’m available for contract to do work for you. Just email me if you want me to help with a complete solution.

This board is primarily to help new users get over the learning curve or to get them unstuck when they run into an issue.

Steve Caldwell
Bome Q&A Moderator and
Indepedent Bome Programmings Consultant/Specialist
bome@sniz.biz

peter.andaluz

2018-05-12 18:39:13

I’ve spent a couple of days digging into the code and it was the stop routine causing the start bug. It would stop and turn off all the lights, on restart the led the first was turned off so although the counting was perfect the led on the first cell just could not light on start once the sequencer was stopped. I added a turn on light instruction on start, it now functions. I’ve added the project here. I am going to use this as a Bome MT pro example in a video demo I am making of the software and post that to my youtube channel as it’s a great real world example of “The power of Bomebox with MP pro”.


Attachments:

Keystep-Visualiser-MultiStep.bmtp

Steve-Bome Forum Moderator

2018-05-12 18:43:32

comment

Wonderful! Post a link here when it is complete. I’d love to watch it.

Steve

peter.andaluz

2018-05-12 18:43:36

comment

of course I meant MT Pro at the end.