You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a heads up, you must include the "Pro Mk3" name when checking or opening the Launchpad Pro Mk3 on Raspberry Pi OS Buster. This is with the default installation of Python 3.7.3 and Pygame 1.9.4 and using local launchpad.py (current 0.9.1). It's a fresh installation with nothing but an apt update && upgrade run.
Using the default check and open methods (such as in the hello.py example), the Launchpad is recognized only as a Pro and not a Pro Mk3. This results in no LED methods functioning properly, but button events fire properly with pressure.
This is the output from information.py:
Running...
- OS : posix
- Platform: Linux
- Release : 5.10.17-v7l+
- Arch : 32bit
- struct : 32
- Python : 3.7.3
- PyGame : 1.9.4.post1
Available MIDI devices:
0 (b'ALSA', b'Midi Through Port-0', 0, 1, 0)
1 (b'ALSA', b'Midi Through Port-0', 1, 0, 0)
2 (b'ALSA', b'Launchpad Pro MK3 MIDI 1', 0, 1, 0)
3 (b'ALSA', b'Launchpad Pro MK3 MIDI 1', 1, 0, 0)
4 (b'ALSA', b'Launchpad Pro MK3 MIDI 2', 0, 1, 0)
5 (b'ALSA', b'Launchpad Pro MK3 MIDI 2', 1, 0, 0)
6 (b'ALSA', b'Launchpad Pro MK3 MIDI 3', 0, 1, 0)
7 (b'ALSA', b'Launchpad Pro MK3 MIDI 3', 1, 0, 0)
I know that my "documentation" sucks, because it's just
onegiantbigfilemess, hehe, but that's written in there and
also in the examples for the Pro Mk3:
Opening it with "0" will not work, yes. This shall be "1", because
it comes with three MIDI-devices per Launchpad and we need the
second one.
Hi. The same is needed with the Mini MK3; it has to be opened using name Mini MK3 (notice the capital 'K') instead of the default. Tested with a Raspberry Pi 3 the latest (as of december 2021) Raspbian.
As a heads up, you must include the "Pro Mk3" name when checking or opening the Launchpad Pro Mk3 on Raspberry Pi OS Buster. This is with the default installation of Python 3.7.3 and Pygame 1.9.4 and using local launchpad.py (current 0.9.1). It's a fresh installation with nothing but an
apt update && upgrade
run.Using the default check and open methods (such as in the hello.py example), the Launchpad is recognized only as a Pro and not a Pro Mk3. This results in no LED methods functioning properly, but button events fire properly with pressure.
This is the output from information.py:
Output from various methods:
Using the Open(0, "Pro Mk3") does seem to work and my initial testing hasn't found any issues. I'll update if I come across anything.
The text was updated successfully, but these errors were encountered: