Launchpad Pro Mk3 support
faroit opened this issue · comments
We all appreciated the open source move for the LPP. Now that the new version is out devs and pro users will likely be interested in
- will it support the open firmware?
- will the sensitivity issues #6 be addressed?
Also curious about open firmware for Pro MK3. For now I have doubts as a checksum was implemented in the firmware update process for X, Mini MK3 and Pro MK3; and I'm unsure if it's just to enforce error-checking or to actively prevent tampering with the device's firmware.
Interested in open firmware for Pro MK3 as well
Either way, the checksum's been reversed, it's just regular crc32. I had used a reimplementation of it to hack together some X and Mini MK3 firmware that featured a proper Drum Rack layout with side buttons included before Legacy mode was released.
Pro MK3 seems to be running on multiple processes/threads, it's using FreeRTOS. Funnily enough debug asserts are compiled in.
@dvhdr as this is open since nearly a year soon - could we get an answer on this, please? Would really be great to know if this is a possibility! Simple quick yes/no would be really nice...
BTW, even though slightly off topic: it would also be really really great, if the sources of the components JS app would be published, there are tons of features to be added and some bugs to be fixed... (e.g. it fails - as in "does nothing when communicating with the device" - on Linux even though connection is "green", should be supporting not only chrome but also chromium, the circuit editor should be able to select multiple samples to import at once, and a bunch of other additions that your users would love to add, so you can concentrate on making great machines while we add to the editors what we need)
I contacted Novation Technical Support asking this question, and linked this thread.
Thanks for your email.
Take a look at r_cycles, our open source solution for hacking our Launchpads: https://novationmusic.com/en/news/hack-making-music
This is our solution to open source firmware for these devices.
Correct me if I'm wrong but r_cycles works on the host machine so it's not much different from e.g. "writing a firmware in pymidi", no?