Correct String for Setting LED in APC 40 MK2

Hey there,

i try to set a colour status fpr my led on APC 40 Mk2.

When i take a look at the Communication Diagram is written down that:

Format of Type 1 outbound Midi note-on messages

Byte Number

Value

Description

1

0x9<chan>

MIDI Note-on. The 4-bit <chan> value will be used for the track strips

2

<ControlID >

Identifier for LED object (“note number”)

3

State

Control value (This value will describe the state or color of the LED: OFF/ON/blinking, etc.)

Assignment of Note number messages to LEDs. Note 0x30 to 0x39 use MIDI Channel 0 to 7 to indicate Tracks 1-8. All other note values ignore the MIDI Channel.

Version 1.2 – January 19, 2015 Page 13

Note Number

MIDI Channel

Corresponding LED

Velocity

0x00

0-15 = RGB Type

Clip Launch 1

See “RGB LEDS” Table below

0x01

0-15 = RGB Type

Clip Launch 2

See “RGB LEDS” Table below

Akai APC40 Mk2 Communication Protocol

MIDI Channel

Corresponding LED

Velocity

0-15 = RGB Type

Clip Launch 3

See “RGB LEDS” Table below

0-15 = RGB Type

Clip Launch 4

See “RGB LEDS” Table below

0-15 = RGB Type

Clip Launch 5

See “RGB LEDS” Table below

0-15 = RGB Type

Clip Launch 6

See “RGB LEDS” Table below

0-15 = RGB Type

Clip Launch 7

See “RGB LEDS” Table below

0-15 = RGB Type

Clip Launch 8

See “RGB LEDS” Table below

0-15 = RGB Type

Clip Launch 9

See “RGB LEDS” Table below

0-15 = RGB Type

Clip Launch 10

See “RGB LEDS” Table below

0-15 = RGB Type

Clip Launch 11

See “RGB LEDS” Table below

0-15 = RGB Type

Clip Launch 12

See “RGB LEDS” Table below

0-15 = RGB Type

Clip Launch 13

See “RGB LEDS” Table below

0-15 = RGB Type

Clip Launch 14

See “RGB LEDS” Table below

0-15 = RGB Type

Clip Launch 15

See “RGB LEDS” Table below

0-15 = RGB Type

Clip Launch 16

See “RGB LEDS” Table below

0-15 = RGB Type

Clip Launch 17

See “RGB LEDS” Table below

0-15 = RGB Type

Clip Launch 18

See “RGB LEDS” Table below

0-15 = RGB Type

Clip Launch 19

See “RGB LEDS” Table below

0-15 = RGB Type

Clip Launch 20

See “RGB LEDS” Table below

0-15 = RGB Type

Clip Launch 21

See “RGB LEDS” Table below

0-15 = RGB Type

Clip Launch 22

See “RGB LEDS” Table below

0-15 = RGB Type

Clip Launch 23

See “RGB LEDS” Table below

0-15 = RGB Type

Clip Launch 24

See “RGB LEDS” Table below

0-15 = RGB Type

Clip Launch 25

See “RGB LEDS” Table below

Note Number

0x02 0x03 0x04 0x05 0x06 0x07 0x08 0x09 0x0A 0x0B 0x0C 0x0D 0x0E 0x0F 0x10 0x11 0x12 0x13 0x14 0x15 0x16 0x17 0x18

Version 1.2 – January 19, 2015

Page 14

Akai APC40 Mk2 Communication Protocol

Note Number

MIDI Channel

Corresponding LED

Velocity

0x19

0-15 = RGB Type

Clip Launch 26

See “RGB LEDS” Table below

0x1A

0-15 = RGB Type

Clip Launch 27

See “RGB LEDS” Table below

0x1B

0-15 = RGB Type

Clip Launch 28

See “RGB LEDS” Table below

0x1C

0-15 = RGB Type

Clip Launch 29

See “RGB LEDS” Table below

0x1D

0-15 = RGB Type

Clip Launch 30

See “RGB LEDS” Table below

0x1E

0-15 = RGB Type

Clip Launch 31

See “RGB LEDS” Table below

0x1F

0-15 = RGB Type

Clip Launch 32

See “RGB LEDS” Table below

0x20

0-15 = RGB Type

Clip Launch 33

See “RGB LEDS” Table below

0x21

0-15 = RGB Type

Clip Launch 34

See “RGB LEDS” Table below

0x22

0-15 = RGB Type

Clip Launch 35

See “RGB LEDS” Table below

0x23

0-15 = RGB Type

Clip Launch 36

See “RGB LEDS” Table below

0x24

0-15 = RGB Type

Clip Launch 37

See “RGB LEDS” Table below

0x25

0-15 = RGB Type

Clip Launch 38

See “RGB LEDS” Table below

0x26

0-15 = RGB Type

Clip Launch 39

See “RGB LEDS” Table below

0x27

0-15 = RGB Type

Clip Launch 40

See “RGB LEDS” Table below

RGB LEDs Type

RGB LEDs

Akai APC40 Mk2 Communication Protocol

MIDI Channel

Function

0

Primary Color

1

Secondary Color – Oneshot 1/24

2

Secondary Color – Oneshot 1/16

3

Secondary Color – Oneshot 1/8

4

Secondary Color – Oneshot 1/4

5

Secondary Color – Oneshot 1/2

6

Secondary Color – Pulsing 1/24

7

Secondary Color – Pulsing 1/16

8

Secondary Color – Pulsing 1/8

9

Secondary Color – Pulsing 1/4

10

Secondary Color – Pulsing 1/2

11

Secondary Color – Blinking 1/24

12

Secondary Color – Blinking 1/16

13

Secondary Color – Blinking 1/8

14

Secondary Color – Blinking 1/4

15

Secondary Color – Blinking 1/2

Name

Color

Velocity

60

#000000

0

59

#1E1E1E

1

58

#7F7F7F

2

57

#FFFFFF

3

1

#FF4C4C

4

2

#FF0000

5

3

#590000

6

4

#190000

7

5

#FFBD6C

8

6

#FF5400

9

so the Synthax i Try to speak to the LED is as follows

1.Midi Note On= 09

2.NoteNumber e.g.= 01 (ClipLanch 01)

3.State= 01(Secondary Color – Oneshot 1/24)

4.Color= 57 ( color) 01 (Velocity)

so my string is

09 01 01 57 01

this is what i write in outgoing / Midi Mesage / Raw Midi Message exclusive

but it doesnt work ... maybe you can help me , i try to search the whole google but dont find a paper where i can see the correct string to set the led by outgoing message.

thank and best regards

Basti

Hi Note on message for MIDI Channel 1 note 1 would be in hex 90 01 xx.  Where xx is the velocity (color) you want.

For the first byte, 9n is the Note on Message where the “n” is the MIDI channel-1 in hex (0-F)

The second byte is the note number 00-7F in hex (0-127 decimal)

The third byte is the color value from the table you indicated.

In MT Pro you can either send it as raw MIDI:

90 01 05

Or select

Note On Channel 1 Note 1 value 5

Let me know if this helps get you on your way.

Steve Caldwell
Bome Q and A Moderator and
Independent Bome Consultant/Specialist
bome@sniz.biz

 

Hey Steve ,

thanks for your very fast reply.
That works now and i understand a bit more whats going on there .

There are a bit more Questions i have:

Why can i not OR how can edit several Translators at one time ?
When i try to select 10 Rows and than set e.g. “outgoing” to “none” only the first row except the command
other 9 are not except the change

I can Export a Preset to an txt document so i can edit the txt with notepad ++ and change e.g. all values 7F to 15
but how can i import the edited version of preset in the bome ??

The last Question i have is ,i have a init preset to set all led to red which look like this:

90 00 07 90 01 07 90 02 07 90 03 07 90 04 07 90 05 07 90 06 07 90 07 07 90 08 07 90 09 07 90 10 07 90 11 07 90 12 07 90 13 07 90 14 07 90 15 07 90 16 07 90 17 07 90 18 07 90 19 07 90 20 07 90 21 07 90 22 07 90 23 07 90 24 07 90 25 07 90 26 07 90 27 07 90 1A 07 90 1B 07 90 1C 07 90 1D 07 90 1E 07 90 1F 07 90 0A 07 90 0B 07 90 0C 07 90 0D 07 90 0E 07 90 0F 07

this is a bad view to edit it in the Raw Midi Cell , is there a way to make it much better looking and better editable with the rules ?? or does that not work ?
Sorry for the foolish question i try to google all the themes before but its very hard to find something.

Thanks and best Regards

Basti

See comments below:

Hey Steve ,

thanks for your very fast reply.
That works now and i understand a bit more whats going on there .

There are a bit more Questions i have:

Why can i not OR how can edit several Translators at one time ?

SJC> Unfortunately bulk editing of translators is not possible at this time.

When i try to select 10 Rows and than set e.g. “outgoing” to “none” only the first row except the command
other 9 are not except the change

SJC> Sorry bulk editing of translators is not currently possible.

I can Export a Preset to an txt document so i can edit the txt with notepad ++ and change e.g. all values 7F to 15
but how can i import the edited version of preset in the bome ??

SJC> Great questions but there is no import feature.  The project file is somewhat editable in a text editor but you have to be careful as the rules don’t always have line feeds and have other “magic” type of data. What I do with some success is to save a backup of the existing .bmtp project file, then edit the new copy in a general purpose text editor. Then save it being careful not to mess up any of the “magic” stuff (which is why I make a backup). Then re-open the newly edited file the Bome MIDI Translator Pro. It’s not perfect but it works in many cases.

The last Question i have is ,i have a init preset to set all led to red which look like this:

90 00 07 90 01 07 90 02 07 90 03 07 90 04 07 90 05 07 90 06 07 90 07 07 90 08 07 90 09 07 90 10 07 90 11 07 90 12 07 90 13 07 90 14 07 90 15 07 90 16 07 90 17 07 90 18 07 90 19 07 90 20 07 90 21 07 90 22 07 90 23 07 90 24 07 90 25 07 90 26 07 90 27 07 90 1A 07 90 1B 07 90 1C 07 90 1D 07 90 1E 07 90 1F 07 90 0A 07 90 0B 07 90 0C 07 90 0D 07 90 0E 07 90 0F 07

this is a bad view to edit it in the Raw Midi Cell , is there a way to make it much better looking and better editable with the rules ?? or does that not work ?

SJC> Another great question. There are a few approaches that I use.

1. If I want it all in a single translator, I create a spreadsheet to create what I want and use the spreadsheet auto increment feature. I then export to a text file and copy and paste it into the raw MIDI cell.
2. If you don’t mind more than one translator, you can create an incoming event that fires on project open that triggers a timer  a number of times.  The timer can then iterate through the output numbers that you want so essentially it is doing all the work for you.  Here is what it might look like if you have 64 sequential notes going from 0 to 63 with velocity of 0.

Incoming : Project Open

Rules: ga=64

Outgoing : Timer “Iterate” ga times

Incoming : Timer “Iterate”

Rules:

pp=64-ga

ga=ga-1

 

Outgoing: Raw MIDI : 90 pp 00

 

So essentially you would get 90 00 00 , 90 00 01, … 90 3F 00

Sorry for the foolish question i try to google all the themes before but its very hard to find something.

SJC> None of these are foolish questions.  I’m happy to help!

 

Thanks and best Regards

Basti