LaunchPad Pro MK3 not working on Oram(staging) but Lauchpad Mini MK3 is working

Using Zynthian
1

Hello everybody

First of all , Happy New Year

Now comes my “problem”

I have both LP Mini MK3 and LP Pro MK3

The driver for the LP Mini MK3 is working fine and I get the Session Mode where I can use ZynPAD

But since the LP Mini MK3 does not have velocity possibilities i decided to try ZynthianOS with the LP Pro MK3

So in Zynthian Admin Mode , I go to “MIDI Input Device” and I see that Zynthian has chosen in “Controller Drivers” : Lauchpad_pro_mk3 (which seems fine) but the session mode is not activated

and if I am in “Note” mode or “Chord” mode on the LP Pro MK3 ,I see the “m” indicator on Zynthian flashing but there is no sound coming out from Dexed .

If I uncheck the “Controller Drivers” mark I can use Note mode and Chord mode on the LP Pro MK3

But of course the “Session” mode is still unavailable.

My setup is like that

I have the ZynthianOS Oram(staging) running on a RPI4 the LP Pro MK3 is connected to the PI on one of his USB3 ports (like I had done previously with the LP Mini MK3)

I am not enough “Python Wizard” to be able to analyze the LP Pro MK3 driver of the Zynthian so any kind of help would be very appreciated

Thank You for reading

Alain

2

Okay with my very limited Python skills I have checked the LP Pro MK3 driver and it seems to me that there is a mistake

def send_sysex(self, data):
    if self.idev_out is not None:
        msg = bytes.fromhex("F0 00 20 29 02 0E {} F7".format(data))
        lib_zyncore.dev_send_midi_event(self.idev, msg, len(msg))
        sleep(0.05)

I think it should be self.idev_out instead of self.idev

Thank You for reading
3

So I modified the “zynthian_ctrldev_launchpad_pro_mk3.py” file , but it is still not working

I checked the “zynthian_ctrldev_launchpad_mini_mk3.py” , where the sysex function is defined in another way and tried with

def send_sysex(self, data):
    if self.idev_out is not None:
        msg = bytes.fromhex(f"F0 00 20 29 02 0E {data} F7")
        lib_zyncore.dev_send_midi_event(self.idev_out, msg, len(msg))
        sleep(0.05)

But still not working so back to Windows and MidiOX to "play" with sysex commands
4

I think I am up to something

In the programmer guide of the LP Pro MPK3 it is said:

“LPProMK3 DAW In / Out (or third interface on Windows)
This interface is used by DAWs and similar software to interact with the Launchpad Pro [MK3]’s
Session mode”

And I checked it with MidiOX on Windows , it is the 3rd interface that must be used to “speak” sysex

so the interface for DAW mode and session mode should be the 3rd one

And if I make no mistake it seems that the Zynthian driver “speaks” to interface 1

So I think the issue is with the driver not “speaking” to the interface which is able to understand sysex messages

Maybe I am totally wrong , if so please excuse me for bothering

Alain

5

Please, could you try to modify the value of this variable in the driver:

dev_ids = ["Launchpad Pro MK3 IN 1"]

to the right value and test?
To find the right value it could help to take a look at MIDI IN menu in zynthian UI.

Regards,

6

If you have doubts, send and screenshot from MIDI IN menu.

regards,

7

Okay so the modifications I made are

class zynthian_ctrldev_launchpad_pro_mk3(zynthian_ctrldev_zynpad):

dev_ids = ["Launchpad Pro MK3 IN 3"]

PAD_COLOURS = [6, 29, 17, 49, 66, 41, 23,
               13, 96, 2, 81, 82, 83, 84, 85, 86, 87]
STARTING_COLOUR = 21
STOPPING_COLOUR = 5

def send_sysex(self, data):
    if self.idev_out is not None:
        msg = bytes.fromhex("F0 00 20 29 02 0E {} F7".format(data))
        lib_zyncore.dev_send_midi_event(self.idev_out, msg, len(msg))
        sleep(0.05)

And there is some kind of progress because during the boot when the "Daphne Oram" appears the Session button briefly lights up and then down
8

I then replaced “Launchpad Pro MK3 IN 3” with “Launchpad Pro MK3 IN 1” and the Session button does not light up at all so it must be the right interface

Great thanks for taking my problem in consideration.

1 Like
9

I managed to keep the Session button lit up by pressing it when it briefly appeared , so now I can press the “Note” or the “Chord” button and then back to the “Session” button.

But in “Session” mode all the pads of the LaunchPad are down.

I suppose it should be something like with the LP Mini MK3 , a Zynpad screen …

I guess it is difficult to find the cause of the problem if you do not have the physical device but anyway , thank you for helping

Alain

1 Like
10

So now I reboot the Zynthian with the LP driver enabled and the “Session” button light up

And if I go to the Zynthian MIDI Input Device menu and check and uncheck the Controller Drivers ,

I see the “Session” button light up and light down

But and It is a BIG But I can no longer input notes in “Note” or “Chord” mode of the LP.

Very tricky ….

It seems that the “LaunchPad Pro MK3 1” is no longer sending midi notes to the synth but in Webconf midi logging I see Notes On and Notes Off for “LaunchPad Pro MK3 1” and on the Zynthian screen the “m” flashes

11

I have now reloaded the original driver for the LP Pro MK3 (without modifications)

And this is what happens the “Session” button on the LP Pro MK3 lights up but all pads are down

If I go in “Note” or “Chord” mode I cannot play the synth which is loaded (Dexed)

If I uncheck the “Controller Driver” , I can play Notes and Chords

I replace in the driver config “LaunchPad Pro MK3 1” with “LaunchPad Pro MK3 3”

I can light up or down the “Session” button by checking and unchecking the “Controller Driver”

but I can no more play the Dexed Synth.

If I change self.idev with self.idev_out in the driver configuration , no difference with precedent settings

Thank You for Reading

Alain (nearly 70 yo)

12

Hello again

I have activated the VNC connection and I have Screen captures of the Zynthian Midi input settings

but I do not know how to send them to you

And can you tell me please if I was right thinking that there is a mistake for the syntax of the send sysex command in the Python script

def send_sysex(self, data):
    if self.idev_out is not None:
        msg = bytes.fromhex("F0 00 20 29 02 0E {} F7".format(data))
        lib_zyncore.dev_send_midi_event(self.idev, msg, len(msg))
        sleep(0.05)

self.idev should be self.idev_out ??

Thank You for reading

Alain
13

This should be already solved in Oram & Vangelis.

Thanks

14

Okay

So I reloaded the Oram(staging) and I see that the driver for LP Pro MK3 has been changed

(self.idev_out instead of self.idev)

I have the same problem

If in the midi input device (wich is Lauchpad Pro MK3 1 ) I check Controller Drivers launchpad_pro_mk3 , the Note mode of the LP does not work (it works if I uncheck)

The programmer guide says

The Launchpad Pro [MK3] has three MIDI interfaces:
LPProMK3 MIDI In / Out (or first interface on Windows)
This interface is used to receive MIDI from Note/Chord mode and Custom modes; and is used to
provide external MIDI input or light LEDs in Custom Modes and Programmer Mode.
LPProMK3 DIN In / Out (or second interface on Windows)
This interface is used to receive MIDI sent/received via MIDI DIN.
LPProMK3 DAW In / Out (or third interface on Windows)
This interface is used by DAWs and similar software to interact with the Launchpad Pro [MK3]’s
Session mode.

So in the py driver I changed “LaunchPad Pro MK3 1” with “LaunchPad Pro MK3 3”

If now I check or uncheck Controller Drivers launchpad_pro_mk3 (which is now affected to interface 3) I can activate or deactivate the Session mode of the LP Pro MK3 and the “Note” mode and the “Chord” mode are working

But in “Session Mode” the pads are still unlit

And by the way I do not understand why in the driver configuration in Midi input Device

I have “mackiecontrol” and “Fostex MixTab” since I do not have any of these devices

Thank You for reading

15

Hi @AL1-1956 !

The problems with the Launchpad Pro MK3 must be solved by users that own the device. We can’t solve issues with devices we don’t own, unless they are trivial bugs, like the “idev_out” one. Of course this applies to any other driver/device.

Please, try modifying dev_ids to the right value:

dev_ids = ["Launchpad Pro MK3 IN 3"]

and take a look to the device developer’s documentation to check that the sysex sequences we are sending are the right ones, etc. Probably you have to do some test/error before getting some advance. And please, keep us informed and don’t hesitate to ask, but please, remember we can’t test, so the help we can bring you is limited.

Regards,

16

These are generic drivers or drivers that can be loaded to unidentified/generic devices, like those connected to the DIN-5 serial interface or a USB-to-DIN5 converter.
Currently they are always listed for each device but we are thinking a better way to allow this list to grow without annoying.

Regards,

17

Okay I understand

About using dev_ids = [“Launchpad Pro MK3 IN 3”] I allready did it by I misnamed it in my previous message , sorry

I was wondering if there is a way to test the driver in a python mode so I tried in a ssh window

python3 /zynthian/zynthian-ui/zyngine/ctrldev/zynthian_ctrldev_launchpad_pro_mk3.py

while the Zynthian is running

and I get this error

File “/zynthian/zynthian-ui/zyngine/ctrldev/zynthian_ctrldev_launchpad_pro_mk3.py”, line 31, in
from zyngine.ctrldev.zynthian_ctrldev_base import zynthian_ctrldev_zynpad
ModuleNotFoundError: No module named ‘zyngine’

My Python skills being very limited I do not know what to do

Anyway Thanks a lot for your kindness

Alain

18

Not an easy way to do this, sorry. Perhaps we could try to implement a more dynamic loading of drivers, so you can modify the code and reload the driver to test, instead of having to restart the UI. Let me take a look to this.

Regards,