Create profile range for each note. (do this after issue 17)

[likevvii]

This will replace our tables with multipler and offset in const.py.

• [ ] Each piano key will have its own profile. A profile will have: -TARGET_MIN -TARGET_MAX -other things like duration may be added if necessary.

• [ ] Profile data CAN NOT be inside a .py file. It has to be read from an external .txt file or maybe a csv file. The method of reading a profile will need to be flexible in the future. Currently we are using a .txt that is read within the same folder, but maybe in the future It will be some other form of "list" or possibly directly given by hardware. Try your best to make it very flexible. If in the future after changes or merges, it becomes incompatible and needs major changes, I will pay full to have it rewritten.

• [ ] idea for the format of profile: I don't know if it should be in the format of an array or in text, and then converted to an array inside python. You can decide what is best.

  
  PROFILE:evan_kwong1
  DATE:xxxx
  REVISION:xxxxx
  ETC:xxxx

(soon, our constants will be stored here)

TARGET_MIN:130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130,130

TARGET_MAX:180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180,180

[ludennis]

For the formatting, I will use the colon as the separator for variable name, and commas for delimiter.

[ludennis]

Also, making the values to be in the same line with the variable would help a lot.