Welcome to the forum.
RowinGrunder wrote:1) how to make your own knob skin?
First, the easy way! Download yourself a free little app' called
'KnobMan'. This is an indispensable little tool tailor made for creating the kind of 'animation strips' used by the "Knob - animated" (and a whole load of other GUI app's).
You could also use any other image editor to create a long strip of square 'frames' each showing the knob in a different position - but Knobman really does make it a whole lot easier.
Then simply load this bitmap into the knob from the 'properties' page (click the little 'P' in the corner of the knob GUI). Then set the 'cell size' property to the size of one square "animation frames" from the bitmap strip, and the inner workings of the module will take care of everything else.
There are other ways too - such as taking a simple bitmap and rotating it, or using FlowStone's vector graphics - but those are trickier to program, and don't have ready made modules when you first install FlowStone (worth a forum search though - there are a few examples floating around).
RowinGrunder wrote:2) how to change the input and output value of the knobs (0-127 midi)
The same 'Knob - animated' is already set up to receive MIDI messages (also set up in the 'properties' page of the module). But the MIDI input is 'hidden' by using a wireless link - so you need a wireless transmitter connected to your MIDI input device to send the messages in.
The MIDI output part is easiest done with a couple of extra parts...
1) In the knob properties, set the knob to have a min, max of 0...127
2) Grab yourself a 'MIDI Event' primitive
3) Connect the value '176' to the 'Status' input of the MIDI event - this is the code for "Controller Message"
4) Connect whatever value 1...16 to the channel input to set the MIDI channel to send on.
5) The 'Data1' input takes the number of the controller that you want to send
6) Connect 'Data2' to the knob for setting the controller value.
7) Connect the knob also to the 'Send event' input to tell the primitive when to make a new output. You must connect this AFTER connecting data2, or things will happen in the wrong order when the knob is moved!
A "Changed" module set to use integers, between the knob and 'MIDI Event' will also be useful - it will help to prevent too many MIDI messages being sent out faster than your synth can handle.
Here's all of that put together in a simple example...
There are other ways to do this too, for example writing the equivalent of the 'MIDI Event' into the Ruby code of the knob - but the method above is easiest if you want quick results before you get stuck into Ruby programming etc.