diff options
| author | DaveHodder67 <dave.hodder@focusrite.com> | 2015-06-16 14:26:13 +0100 |
|---|---|---|
| committer | DaveHodder67 <dave.hodder@focusrite.com> | 2015-06-16 14:26:13 +0100 |
| commit | a2915837e934d24ea337b010ff96ccfee0b092ff (patch) | |
| tree | 9c55d20cc59e9e332679c6d1cae85318f4430419 | |
| parent | cb506c00731140dd08b8d26a52bceeb743975399 (diff) | |
| download | launchpad-polymaker-a2915837e934d24ea337b010ff96ccfee0b092ff.tar.gz launchpad-polymaker-a2915837e934d24ea337b010ff96ccfee0b092ff.zip | |
updated README further
| -rw-r--r-- | README.md | 13 |
1 files changed, 10 insertions, 3 deletions
| @@ -1,5 +1,11 @@ | |||
| 1 | # Launchpad Pro | 1 | # Launchpad Pro |
| 2 | Open source firmware for the Novation Launchpad Pro grid controller | 2 | Open source firmware for the Novation Launchpad Pro grid controller! By customising this code, you can: |
| 3 | |||
| 4 | - Implement your own unique standalone modes | ||
| 5 | - Create chorders, sequencers, light shows, games and more | ||
| 6 | - Learn a little about firmware development! | ||
| 7 | |||
| 8 | You definitley need *some* C programming experience, but we've deliberately kept much of the firmwarey nastiness tucked away, to make the process a little friendlier. | ||
| 3 | 9 | ||
| 4 | # Philosophy | 10 | # Philosophy |
| 5 | We could have released the full source for the factory shipping firmware, but we've decided not to for a variety of reasons. Instead, we created a simplified framework for developing "apps" on Launchpad, which comprises a build environment, application entry points / API, and a library of low level source code. Our reasoning is as follows: | 11 | We could have released the full source for the factory shipping firmware, but we've decided not to for a variety of reasons. Instead, we created a simplified framework for developing "apps" on Launchpad, which comprises a build environment, application entry points / API, and a library of low level source code. Our reasoning is as follows: |
| @@ -33,12 +39,13 @@ The most crucial parts of the API are: | |||
| 33 | 39 | ||
| 34 | - Recieving messages from the pads and buttons | 40 | - Recieving messages from the pads and buttons |
| 35 | - Writing colours to the LEDs | 41 | - Writing colours to the LEDs |
| 36 | - Sending and receiving messages from the USB and MIDI ports | 42 | - Sending and receiving messages from the MIDI ports |
| 37 | - Receiving a tick message to drive timing based code | 43 | - Receiving a tick message to drive timing based code |
| 38 | 44 | ||
| 39 | Up for debate: | 45 | Up for debate: |
| 40 | 46 | ||
| 41 | - Flash read / write access | 47 | - USB MIDI support (why not just implement on the host in programmer mode using the factory firmware?) |
| 48 | - Flash memory read / write access | ||
| 42 | - Setup button behaviour | 49 | - Setup button behaviour |
| 43 | 50 | ||
| 44 | # Debugging | 51 | # Debugging |