Hardware LEDs Send CC on receive multiple CC off

Hi, I am using my Nektar Pacer with software and I am trying to get the LEDs to correspond to software state.

I have 6 footswitches assigned to CCs 1 through 6

I am looking for a rule ( or more elegant way ) to send one CC on message from pacer and receive the other 5 CC off messages.

for example I press Footswitch 1 which send CC1 on

I want pacer to receive back CCs 2-5 off ( which will shut off all other LEDs except Footswitch 1.

And obviously do the same as I press other fooswitches so pressing Footswitch 2 ( CC2 on ) Send CC off for the others ( CC1,CC3,CC4,CC5CC6 ) and so on....

I can achieve this with a laundry list of separate translators but I’d imagine a rule would be much more elegant.

thanks so much!

Hi for just 5 footswithes, the below should work. If you have more than 10, however then you would need to use global variables (there are only 10 locals) and a timer to iterate through all of the off footswitches.

I also set up a MIDI thru path for your application to talk to the Pacer LED's

The rules look at which of the 5 CC's you pressed and set only the one pressed to a value of 127. The rest are left at 0.

 

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

This did control the LEDs properly but for some reason MTP wont send output to my DAW anymore. I tried setting an output as MTO virtual Out. tried LoopB1... cant seem to get messages to my DAW with this project... What am I doig wrong? I am using Bitwig btw.

Thanks again for your help

This did control the LEDs properly but for some reason MTP wont send output to my DAW anymore. I tried setting an output as MTO virtual Out. tried LoopB1... cant seem to get messages to my DAW with this project... What am I doig wrong? I am using Bitwig btw.

Thanks again for your help

Hi,

In MT Pro go to the MIDI router and draw a line between your Pacer and the application as shown in the diagram below. That should let all other MIDI messages pass through untouched.

If you have any other controllers talking to Bitwig. You will have to draw routes to and from them to Bitwig as well.

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

Hey Steve, I just literally tried every combination of ins and outs but can’t get the messages through to bitwig. I wonder if I can  ask what my inputs and outputs should be and I’ll go from there...

First off when I open your project file a dialog box pops up...

says please select midi devices

Pacer:

Input: ?

Application:

Input: ??

Output: ???

( photo attached )

Secondly Bitwig

I set up a new controller

what should the input be?

( photo attached )

From here if there are any other instructions I’ll do that and test... this way we are both on the same page..

ps when you refute to “application” fay as midi inputs and outputs.. are we talking about bitwig or Bome? If it’s bitwig there is no way as far as I can see to have bitwig send out anything.. it can only receive midi as far as I can tell.

OK, you are setting up as generic keyboard controller so you won't get feedback from BitWig.

Also, I don't think Bitwig understands long MIDI port names so go into Bome MIDI Translator Pro

Menu -> View Settings and then set Options to use short names as shown in the attached illustration.

 

Then you can set the Aliases as shown in the second illustration.

 

Set up Bitwig as shown in the third illustration.

 

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

Ok! This works! One question though... How would I add an additional Footswitch I.e CC6. I thought it would be just adding If pp==6 then vv=127 .... but that did not work.

I got it ! Disregard last message. Needed to edit outgoing message with vv Thanks so much Steve!!

Ok! This works! One question though... How would I add an additional Footswitch I.e CC6. I thought it would be just adding If pp==6 then vv=127 .... but that did not work.

 

In rules change:

If pp>5 then exit rules, skip outgoing action

to:

If pp>6 then exit rules, skip outgoing action

under:

uu=0

put:

vv=0

 

under:

if pp==5 then uu=127

put

if pp==6 then vv=127

 

Then on output add to the existing output (at the end)

B0 06 vv

 

 

 

It’s all working now thanks so much Steve!

Hi Steve, I am having an issue with this same setup and cakewalk.. when I try to run MTP to Cakewalk ( triggering matrix clips ) .. Cakewalk starts to act irrattic. Triggering wrong scenes double presses, turning random global features on and off... this does not happen if I just run pacer to cakewalk however.. only when BMT is in the middle. 

my setup is exactly the same as it's set up here. 

thanks again.

If I had to guess I would say Cakewalk is getting double messages... the behaviors after testing seems to be double pressing on each Footswitch w pacer mimics what happens when Bome is in between.