Sysex to control Launchpad lights… works on one computer but not another… same bome file.

  • Q&A Forum
  • [RESOLVED] Sysex to control Launchpad lights... works on one computer but not another... same bome file.
0
0

Ok. This is a wierd one to me. I developed a template for SonicCouture Pan Drum. It maps the launchpad grid for the different pan drums and also the different keyboard layouts that come with the Pan Drum Instrument.

Now, I was using sysex to map the colored lights to be able to visualize the keypad.

Without having to understand all of these details, here is the problem.

Same file on both machines.

On both machines, the sysex messages are transmitted to the device. On one machine, the transmission is received as indicated by the colored LEDs being set properly.

On the other machine, the transmission is apparently not received. As, the lights are not effected and remain the way they are.

I have attached an image of the inputs and outputs on each machine, and an image of the log files side by side. If you look at it you will see that the laptop, outputs to bome virtual 1 and also back to the lauchpad. I didn’t ask it to do this, but that is what is desired. The workstation just outputs to bome virtual 1. I need to find a way to get the workstation to output launchpad 2 as well. But, the file is identical on each machine. So, I am lost.

 

I hope someone can help.

Thanks in advance.

 

 

Attachments:
RESOLVED
Marked as spam
Posted by (Q&A Forum: 2, Answers: 8)
March 26, 2019 1:26 am
42 views
0
Private answer

Actually, I spoke too soon. It isn’t resolved. On the workstation, the original input to the launchpad is output again. On the laptop, this doesn’t happen. I am careful to be swallowing all of the original input.

If you’ll notice the posted picture, there are output ports for the workstation and output ports for the laptop. Notice that the laptop has an output port called MIDIOUT2 Launchpad >Launchpad. On the workstation, this does not exist. The laptop uses this port rather than just a plain “launchpad 2” And everything works fine. So, how can I create this port on the workstation?

Attachments:
Marked as spam
Posted by (Q&A Forum: 2, Answers: 8)
March 27, 2019 8:36 pm
On your workstation, click on MIDIOUT2 and reassign the alias to go to Launchpad Pro2 instead of Bome MIDI Translator 1 Virtual port. Once you assign your aliases correctly on each of your PC’s they should remember them for the future (unless you delete the aliases). If you have further questions or issues, please post your project file here (as a question as attachments cannot be posted in comments), and I’ll be happy to help further. Or visa versa if the laptop is the one having the problem. Steve Caldwell Bome Q and A Moderator and Independent Bome Consultant/Specialist bome@sniz.biz
( at March 28, 2019 1:01 am)
0
Private answer

Ok. So the issue was that I had ports defined on the translator level, that worked properly on the laptop. But, the device name was worded slightly different on the workstation and so the Sysex wasn’t being outputted to the launchpad. I changed all the translators to default to project ports and all is well. I’ve been a programmer for 35 years now. And, it never fails. The computer is doing exactly what you are telling it to do. The error is always in the human being. LOL

Marked as spam
Posted by (Q&A Forum: 2, Answers: 8)
March 26, 2019 2:03 pm

Yes, this is the primary reason I use aliases in my project file. Much more portable. Glad you found the issue!

( at March 26, 2019 4:14 pm)
0
Private answer

Hi, on the first image it shows Input Launchpad Pro 2 as pending so maybe on that machine there is another application already connected to your launchpad pro. It is important to connect only one application to a given MIDI port.

 

I hope this helps. If you post your project file I may be of additional help.

It is important to note, that you define all your inputs and outputs on the main screen. Then you define within preset the inputs and outputs for the devices only in that preset. The preset will override the project defaults. Then if you want to override the preset defaults you can do that at a translator level.  I usually use the preset level to override project defaults. For instance I might have a preset for controller feedback controller out -> controller in and another preset for controller to app controller out -> MT Virtual port to application.

For MIDI thru connection understand they will always go through unless overridden by a translator, AND the translator has “Swallow” set AND the output executes or is None (ie you don’t exit translator with a rule like “Exit rules, skip outgoing action”. If you use Exit rules, skip outgoing action and there is a MIDI thru connection set, the output will still follow the MIDI Thru path.

I know this is more information than you asked. so again if you are still stumped post your project file but my guess is it is not working because your input port on your controller is pending and not open and is probably pending because some other application or device is accessing it.

 

 

 

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

 

Marked as spam
Posted by (Q&A Forum: 38, Answers: 3211)
March 26, 2019 4:33 am
0
Private answer

The obvious suggestion might be to check launchpad2 on the midi output for the whole project. But, that has no effect on the log file. Nor the lights (sysex still not getting to the launchpad).

Marked as spam
Posted by (Q&A Forum: 2, Answers: 8)
March 26, 2019 1:29 am
Votes
Answers
Topic
0
votes
1
answer
asked 2 weeks ago by
updated 2 weeks ago by
0
votes
1
answer
asked 2 months ago by
updated 2 months ago by
0
votes
1
answer
asked 8 months ago by
updated 8 months ago by
Tags:
0
votes
3
answers
asked 11 months ago by
updated 11 months ago by