There's lots of stuff out in internet land for what these mean. Specifically for just a table of notes and their numbers just Google "MIDI note table".
Here are a couple:
http://computermusicresource.com/midikeys.html
http://www.phys.unsw.edu.au/jw/notes.html

Here's some other links that I found helpful when I was researching my MIDI file library.
MIDI.ORG very detailed but has all the info. Can be confusing at times. http://www.midi.org/techspecs/midimessages.php
More (similar) detail explained differently http://www.gweep.net/~prefect/eng/reference/protocol/midispec.html

BTW, I don't expect you tho think I am stupid, you just need to explain stuff to others in great detail as we cannot guess what you are trying to do, and it can get frustrating.

What do you mean by 'adding values'? Assume I am really stupid (which I am about what is in your head) and explain it in detail

The code you have posted runs the fluxamsynth and you clearly have a library that will control that device, including examples of how to turn notes on and off and change performance parameters.

How you implement the interface to your instrument switches is really a matter of how your instrument works and what you are trying to achieve in the way of performance. Assuming that you have implemented the echanter according to the web site instructions, you have the inputs necessary to do what you need.

I have to say that I am still confused as to what you really need from the forum.

What hardware are you using? The sd card and the Ethernet stuff run completely independently and do not affect each other on my Uno.

There are about 3 things that I think you need to be able to do here
1. Read the on or off state of a button
2. Be able to send a message through the serial port (or instruct the fluxamasynth to do something)
3. Understand what midi instrument you are trying to use as a voice for the midi stream.

Can you do the above?  If you you have all the elements you need to carry out this project.

What libraries do you think that you need and why?

At the bottom of Mike's design section is a link to a zip file for the code that drives his pendulum thing. I assume that is what he means about the code. Easy to miss.

Not sure if this will help your situation, butI have just written a library that can read midi files on the Arduino and push the data out to a controller or synth.  Look in the Audio forum.

I got mine from eBay and they work fine for my purpose, which is hobby experimental stuff Not sure how they do it for the price, but the quality seems to be good enough if you don't mind the usually long wait for stuff coming through the post from China.

It should be possible. The main issue will be making sure that you have enough I/o pins to do everything you want. Hoe to start? Each of the functions on their own are simple, so create them independently to get experience on using the software and circuits you will need. Then build up the final project function by function using the knowledge and subsystems you have worked on as prototypes.

Good luck, sounds like fun!

Sorry but I understood that you were going to make an instrument using the fluxamasynth as a base for the electronics. What exactly are you trying to do?

This version (0.4) now works with everything I have been able to throw at it.

I have reworked the timing section so that it is tighter and more accurate in keeping the music to time. There were also serious logical errors in the processing of MIDI run on messages that caused the some files to play badly or not at all (see my first post).

I think there is a bit of tidy up to do and then it can be released as v1.

One way to reduce complexity and size may be to define a class for a pump (assuming they work similarly) and have parameters (variables) that hold the values that make these pumps different from the standard ( such as the name of liquid being pumped, the amount, time to pump, i/o pins, etc).

What you have created is generally know as a recipe handling system in industrial environments and there is a lot of experience in how to do these efficiently. The key is to separate the data from the code and idealize the equipment so that you can reuse the same object multiple times.

Try using the flash library to remove the strings from RAM. That will free up quite a bit of space for you.

Look at the blink without delay example.

Here's a schematic to start with http://www.fluxly.com/blog/2010/11/fluxamasynth.html