First of all, I just want to say how awesome I think Zynthian is (and has the potential to be)! You really have achieved something great with this software + hardware combo. I recently bought the 5.1 kit and the assembly instructions are really thorough and spot on, well done!
I have an old Launchpad Pro lying about and hoped to get it working to launch sequences and develop things further for it. However, I have run into some problems and since I’m not the most proficient Python developer, I could really need some help with the inner workings of Zynthian.
I can launch clips just fine with it, but have no feedback to the Launchpad itself, I wonder if there is some differences between MK 2 and MK 1.
Is there someone out there that uses a Launcpad Pro (not mk3) with Zynthian and can confirm that it is working for them as it seems the Launchpad Mini Mk 3 does?
I’ve been setting some rudimentary prints in /zynthian/zynthian-ui/zyngine/ctrldev/zynthian_ctrldev_launchpad_pro_mk2.py to get a grip on how it works and I think the initialization into Live-mode works as it should so the Launchpad can at least accept SysEx messages as the one in the init() function.
I run this via the .sh script to get logs, but it seems that despite my changes, the python files are cached in the pycache directory or something. Is there some way to disable that caching to get some immediate changes and be able to test them quicker?
Thanks @wyleu I will setup a github repo of my own and do a proper pull request and an issue when I get to a computer with working wlan iface. Now I’m doing the “development” on an ancient laptop with a crossed cat6 cable straight into the zynthian in a hotel room without wired internet. Sorry about that…