monome wiki mapd documentation

h2. 1. overview

tehn — Thu, 17 Aug 2006 04:19:28 +0000

h2. 1. overview
…
…
here are the mapd extended midi messages
…
Content was also deleted

Each of the widgets also has an option to set it so that mapd sends out osc messages that interpolate between the current and new values. The interpolation occurs over a time-interval defined by the interpolation time (you can only set the interpolation time once you have clicked the initial condition toggle button.

franzson — Thu, 17 Aug 2006 01:53:58 +0000

…
Each of the widgets also has an option to set it so that mapd sends out osc messages that interpolate between the current and new values. The interpolation occurs over a time-interval defined by the interpolation time (you can only set the interpolation time once you have clicked the initial condition toggle button.
…
Each widget also allows the user to store an initial value for the widget. By clicking the send initial condition toggle button, the initial value will be sent out on load or any time that the current mapping gets turned on.
…
both press and toggle buttons allow you to send out osc messages when you either press or release a button on the 40h. this is done by leaving either the up or down value for the given widget empty.
…
[[insert Picture of down_press]]

…
…
…

h2. mappings

mapd allows the user to create mappings. a mapping is a complete set of pages, presets and layout for the 40h. mappings allow the user to switch easily between instruments or song setups. when mappings are switched, all temporary information of the old mapping get cleared away, and all initalization values get sent out.

h2. pages

pages allow the user to set the 40h to use multiple different layouts or maps in a single patch. each page contains a number of widgets. when a page gets switched, all the temporary data on the page stays unchanged, and the temporary state of the new page gets recalled. when a page is switched, no information gets sent out. we can think of pages as a way of extending the 40h into multiple levels, allowing us to use more than just 64 buttons to control an instrument (an example would be the pattern and step-sequencer views in 64 step).

by setting a button down so that it sends the message:

/system/page pagename

we can switch between pages on the fly.

h2. presets

presets store and recall the temporary state of a given mapping. you can add presets using the + button, and remove them with the - button. you store and recall the presets using the S and R buttons.

by setting a button down so that it sends the messages:

/system/preset/save presetname
/system/preset/recall presetname

you can store and recall presets on the fly.
…
Content was also deleted

h2. clearing space on the 40h

joe lake — Sat, 03 Jun 2006 01:53:03 +0000

h2. clearing space on the 40h
…

h2. midi address patterns

so you want to send midi? okay, okay, I guess you can send midi, but at least PRETEND you're using open sound control! I'm going to describe the make-believe osc address pattern and value structure for sending midi, but there are a few things you need to know.

mapd let's you select 4 different midi destination to send message to. these devices can anything connected to your computer or any piece of software that knows how to create a virtual midi endpoint (that's what the 'to Max/MSP1' and 'to Max/MSP 2' devices are that show up when you open Max/MSP). within an address pattern, these devices are represented by the letters a, b, c, and d. in the midi setup dialog you can select which device is represented by each letter.

the second thing you need to know is that mapd lets you send 3 different types of values: integers, floating point decimal numbers, and strings. when I tell you how to send a certain type of midi message, I'm going say something incomprehensible, like "note on messages must have the following structure:

"/midi/note_on [device:(string)a-d] [note number:(int)0-127] [velocity:(int)0-127] [channel:(int)1-16]"

and you're going to know that I want you to write something like:

/midi/note_on a 60 64 1

to send out a note_on midi for note number 60 with velocity 64 to device 'a' on channel 1.

what the hell are you talking about?

[device:(string)a-d] means that that this place in the address pattern tells mapd what devviice to send midi to and must be an atom of the type string that is one of the following letters: 'a', 'b', 'c', or 'd'.

[note:(int)0-127] means whatever is in this place in the address pattern tell mapd what midi note number to output. it must be an integer between 0 and 127, inclusive.

[velocity:(int)0-127] means whatever is in this place in the address pattern tells mapd what midi velocity to output. it must be an integer between 0 and 127, inclusive.

[channel:(int)1-16] means that whatever is in this place in the address pattern tell mapd what midi channel to send the note on to. it must be an integer between 1 and 16, inclusive.

got it? good! here we go:

h3. note on

/midi/note_on [device:(string)a-d] [note number:(int)0-127] [velocity:(int)0-127] [channel:(int)1-16]

example: /midi/note_on a 60 64 1

h3. note off

/midi/note_off [device:(string)a-d] [note number:(int)0-127] [channel:(int)1-16]

example: /midi/note_off a 60 1

h3. after touch

/midi/aftertouch [device:(string)a-d] [note number:(int)0-127] [pressure:(int)0-127] [channel:(int)1-16]

example: /midi/aftertouch 60 126 1

h3. control change

/midi/controller [device:(string)a-d] [controller number:(int)0-127] [controller value:(int)0-127] [channel:1-16]

example: /midi/controller a 7 127 1

the midi spec has some special controllers than generally do the same thing on every midi device. for example, controller number 7 usually controls the volume. there are also some controller types are actually controlled by two controller numbers. did you know that on most midi devices you can set a 14bit volume by sending the high 7 bits to controller number 7 and the lower 7 bits to controller number 39? mapd has some special address patterns to make this easy for you. they take the form

/midi/controller [device:(string)a-d] [controller:(string)bank|modwheel|volume...] [value:(int)0-127|(float)0.0-1.0] [channel:(int)1-16]

here we go!

h4. bank select (controller numbers 0 and 32)

/midi/controller [device:(string)a-d] bank [value:(int)0-16383] [channel:(int)1-16]

example: /midi/controller a bank 1000 1

h4. modulation wheel (controller numbers 1 and 33)

/midi/controller [device:(string)a-d] modwheel [value:(float)0.0-1.0] [channel:(int)1-16]

example: /midi/controller a modwheel 0.5 1

h4. breath controller (controller numbers 2 and 34)

/midi/controller [device:(string)a-d] breath [value:(float)0.0-1.0] [channel:(int)1-16]

example: /midi/controller a breath .5 1

h4. foot pedal (controller numbers 4 and 36)

/midi/controller [device:(string)a-d] foot [value:(float)0.0-1.0] [channel:(int)1-16]

example: /midi/controller a foot .5 1

h4. portamento time (controller numbers 5 and 37)

/midi/controller [device:(string)a-d] portamento_time [value:(float)0.0-1.0] [channel:(int)1-16]

example: /midi/controller a portamento_time .5 1

h4. data entry (controller numbers 6 and 38)

/midi/controller [device:(string)a-d] data [value:(int)0-16383] [channel:(int)1-16]

example: /midi/controller a data 1000 1

h4. volume (controller numbers 7 and 39)

/midi/controller [device:(string)a-d] volume [value:(float)0.0-1.0] [channel:(int)1-16]

example: /midi/controller a volume .5 1

h4. balance (controller numbers 8 and 40)

/midi/controller [device:(string)a-d] balance [value:(float)0.0-1.0] [channel:(int)1-16]

example: /midi/controller a balance .5 1

h4. pan position (controller numbers 10 and 42)

/midi/controller [device:(string)a-d] pan [value:(float)0.0-1.0] [channel:(int)1-16]

example: /midi/controller a pan .5 1

h4. expression (controller numbers 11 and 43)

/midi/controller [device:(string)a-d] expression [value:(float)0.0-1.0] [channel:(int)1-16]

example: /midi/controller a expression .5 1

h4. effect control 1 (controller numbers 12 and 44)

/midi/controller [device:(string)a-d] effect1 [value:(float)0.0-1.0] [channel:(int)1-16]

example: /midi/controller a effect1 .5 1

h4. effect control 2 (controller numbers 13 and 45)

/midi/controller [device:(string)a-d] effect2 [value:(float)0.0-1.0] [channel:(int)1-16]

example: /midi/controller a effect2 .5 1

h4. general purpose slider 1 (controller number 16)

/midi/controller [device:(string)a-d] slider1 [value:(int)0-127] [channel:(int)1-16]

example: /midi/controller a slider1 127 1

h4. general purpose slider 2 (controller number 17)

/midi/controller [device:(string)a-d] slider2 [value:(int)0-127] [channel:(int)1-16]

example: /midi/controller a slider2 127 1

h4. general purpose slider 3 (controller number 18)

/midi/controller [device:(string)a-d] slider3 [value:(int)0-127] [channel:(int)1-16]

example: /midi/controller a slider3 127 1

h4. general purpose slider 4 (controller number 19)

/midi/controller [device:(string)a-d] slider4 [value:(int)0-127] [channel:(int)1-16]

example: /midi/controller a slider4 127 1

h4. pedals (controller numbers 64 through 69)

there are several standard controllers that are basically just switches that can be either on or off. for these controllers midi values 0 - 63 are treated as off and midi values 64 - 127 are treated as on. for the value field mapd treats a 0 as off (outputting midi value 0) and any non-zero integer as on (outputting midi value 127). so even though for the hold pedal midi value 1 would signal an off, in mapd to signal an on for hold pedal you could write

/midi/controller a hold 1 1

h5. hold pedal (controller number 64)

/midi/controller [device:(string)a-d] hold [value:(int)] [channel:(int)1-16]

example: /midi/controller a hold 0 1

h5. portamento (controller number 65)

/midi/controller [device:(string)a-d] portamento [value:(int)] [channel:(int)1-16]

example: /midi/controller a portamento 0 1

h5. sustenuto pedal (controller number 66)

/midi/controller [device:(string)a-d] sustenuto [value:(int)] [channel:(int)1-16]

example: /midi/controller a sustenuto 0 1

h5. soft pedal (controller number 67)

/midi/controller [device:(string)a-d] soft [value:(int)] [channel:(int)1-16]

example: /midi/controller a soft 0 1

h5. legato pedal (controller number 68)

/midi/controller [device:(string)a-d] legato [value:(int)] [channel:(int)1-16]

example: /midi/controller a legato 0 1

h5. hold2 pedal (controller number 69)

/midi/controller [device:(string)a-d] hold2 [value:(int)] [channel:(int)1-16]

example: /midi/controller a hold2 0 1

h4. sound variation (controller number 70)

/midi/controller [device:(string)a-d] variation [value:(int)0-127] [channel:(int)1-16]

example: /midi/controller a variation 127 1

h4. sound timbre (controller number 71)

/midi/controller [device:(string)a-d] timbre [value:(int)0-127] [channel:(int)1-16]

example: /midi/controller a timbre 127 1

h4. release time (controller number 72)

/midi/controller [device:(string)a-d] release [value:(int)0-127] [channel:(int)1-16]

example: /midi/controller a release 127 1

h4. attack time (controller number 72)

/midi/controller [device:(string)a-d] attack [value:(int)0-127] [channel:(int)1-16]

example: /midi/controller a attack 127 1

h4. brightness (controller number 74)

/midi/controller [device:(string)a-d] brightness [value:(int)0-127] [channel:(int)1-16]

example: /midi/controller a brightness 127 1

h4. sound control 6 (controller number 75)

/midi/controller [device:(string)a-d] control6 [value:(int)0-127] [channel:(int)1-16]

example: /midi/controller a control6 127 1

h4. sound control 7 (controller number 76)

/midi/controller [device:(string)a-d] control7 [value:(int)0-127] [channel:(int)1-16]

example: /midi/controller a control7 127 1

h4. sound control 8 (controller number 77)

/midi/controller [device:(string)a-d] control7 [value:(int)0-127] [channel:(int)1-16]

example: /midi/controller a control7 127 1

h4. sound control 9 (controller number 78)

/midi/controller [device:(string)a-d] control7 [value:(int)0-127] [channel:(int)1-16]

example: /midi/controller a control7 127 1

h4. sound control 10 (controller number 79)

/midi/controller [device:(string)a-d] control10 [value:(int)0-127] [channel:(int)1-16]

example: /midi/controller a control10 127 1

h4 general purpose buttons (controller numbers 80 through 83)

the general purpose buttons work like the pedals. a value of 0 is treated as off and midi value 0 is outputted. any non-zero value is treated as on and midi value 127 is outputted.

h5. general purpose button 1 (controller number 80)

/midi/controller [device:(string)a-d] button1 [value:(int)0-127] [channel:(int)1-16]

example: /midi/controller a button1 0 1

h5. general purpose button 2 (controller number 81)

/midi/controller [device:(string)a-d] button2 [value:(int)] [channel:(int)1-16]

example: /midi/controller a button2 0 1

h5. general purpose button 3 (controller number 82)

/midi/controller [device:(string)a-d] button3 [value:(int)] [channel:(int)1-16]

example: /midi/controller a button3 0 1

h5. general purpose button 4 (controller number 83)

/midi/controller [device:(string)a-d] button4 [value:(int)] [channel:(int)1-16]

example: /midi/controller a button4 127 1

h5. effects level (controller number 90)

/midi/controller [device:(string)a-d] effects [value:(int)0-127] [channel:(int)1-16]

example: /midi/controller a effects 127 1

h5. tremulo level (controller number 91)

/midi/controller [device:(string)a-d] tremulo [value:(int)0-127] [channel:(int)1-16]

example: /midi/controller a tremulo 127 1

h5. chorus level (controller number 92)

/midi/controller [device:(string)a-d] chorus [value:(int)0-127] [channel:(int)1-16]

example: /midi/controller a chorus 127 1

h5. celeste level (controller number 93)

/midi/controller [device:(string)a-d] celeste [value:(int)0-127] [channel:(int)1-16]

example: /midi/controller a celeste 127 1

h5. phaser level (controller number 94)

/midi/controller [device:(string)a-d] phaser [value:(int)0-127] [channel:(int)1-16]

example: /midi/controller a phaser 127 1

h4. data buttons (controllers 96 and 97)

data button increment and data button decrement typically cause some registered or non-registered parameter to be either incremented or decremented. the controller value is ignored for these controller numbers.

h5. data button incremenet (controller number 96)

/midi/controller [device:(string)a-d] data_button_inc [channel:(int)1-16]

example: /midi/controller a data_button_inc 1

h5. data button decrement (controller number 97)

/midi/controller [device:(string)a-d] data_button_dec [channel:(int)1-16]

example: /midi/controller a data_button_dec 1

h4. non-registered parameter (controller numbers 98 and 99)

/midi/controller [device:(string)a-d] nrp [value:(int)0-16383] [channel:(int)1-16]

example: /midi/controller a nrp 1000 1

h4. all sound off (controller number 120)

all sound off midi messages ignore the controller value, so it's not used in the address pattern value string

/midi/controller [device:(string)a-d] all_sound_off [channel:(int)1-16]

example: /midi/controller a all_sound_off 1

h4. all controls off (controller number 121)

all controls off midi messages ignore the controller value, so it's not used in the address pattern value string

/midi/controller [device:(string)a-d] all_controls_off [channel:(int)1-16]

example: /midi/controller a all_controls_off 1

h4. local keyboard on/off (controller number 122)

works like foot pedal.

/midi/controller [device:(string)a-d] local_keyboard [value:(int)] [channel:(int)1-16]

h4. all notes off (controller number 121)

all notes off midi messages ignore the controller value, so it's not used in the address pattern value string

/midi/controller [device:(string)a-d] all_notes_off [channel:(int)1-16]

example: /midi/controller a all_notes_off 1

h4. omni mode off (controller number 124)

all notes off midi messages ignore the controller value, so it's not used in the address pattern value string

/midi/controller [device:(string)a-d] omni_off [channel:(int)1-16]

example: /midi/controller a omni_off 1

h4. omni mode on (controller number 125)
omni mode on midi messages ignore the controller value, so it's not used in the address pattern value string

/midi/controller [device:(string)a-d] omni_on [channel:(int)1-16]

example: /midi/controller a omni_on 1

h4. mono operation (controller number 126)

/midi/controller [device:(string)a-d] mono [value:(int)0-127] [channel:(int)1-16]

example: /midi/controller a mono 127 1

h4. poly operation (controller number 126)

/midi/controller [device:(string)a-d] poly [value:(int)0-127] [channel:(int)1-16]

example: /midi/controller a poly 127 1

h3. program change

/midi/program [device:(string)a-d] [program number:(int)0-127] [channel:(int)1-16]

example: /midi/program a 64 1

h3. channel pressure

/midi/channel_pressure [device:(string)a-d] [pressure:(int)0-127] [channel:(int)1-16]

example: /midi/channel_pressure a 64 1

h3. pitch wheel

/midi/pitch_wheel [device:(string)a-d] [pitch bend:(float)-1.0-1.0] [channel:(int)1-16]

h3. song position pointer

/midi/song_position [device:(string)a-d] [position:(int)0-16383]

example: /midi/song_position a 1000

h3. song select

/midi/song_select [device:(string)a-d] [song:(int)0-127]

h3. tune request

/midi/tune_request [device:(string)a-d]

example: /midi/tune_request a

h3. midi clock

/midi/clock [device:(string)a-d]

h3. midi tick

/midi/tick [device:(string)a-d]

h3. midi start

/midi/start [device:(string)a-d]

h3. midi stop

/midi/stop [device:(string)a-d]

h3. midi continue

/midi/continue [device:(string)a-d]

h3. midi active sense

/midi/activesense [device:(string)a-d]

h3. midi reset

/midi/reset [device:(string)a-d]

h3. alternate forms of the midi realtime messages

h4. midi clock

/midi/realtime [device:(string)a-d] clock

h4. midi tick

/midi/realtime [device:(string)a-d] tick

h4. midi start

/midi/realtime [device:(string)a-d] start

h4. midi stop

/midi/realtime [device:(string)a-d] stop

h4. midi continue

/midi/realtime [device:(string)a-d] continue

h4. midi active sense

/midi/realtime [device:(string)a-d] activesense

h4. midi reset

/midi/realtime [device:(string)a-d] reset
…
Content was also deleted

[[mapd can be downloaded here => http://monome.org/file/mapd-0.1.tar.gz]]

franzson — Wed, 31 May 2006 03:27:26 +0000

[[mapd can be downloaded here => http://monome.org/file/mapd-0.1.tar.gz]]

…
the mapd window is separated into two main fields.
…
* on the left side there is a virtual monome for selecting buttons to assign to widgets and to monitor button presses and widget status.
* on the right side, preferences retaining to the creation of a widget, or to the behavior of a selected widget becomes visible when needed.
…
[[insert Picture of mapd main window]]

…
mapd allows the user to select a number of buttons on the virtual monome on the left hand side of the mapd window, by either clicking and shift-clicking any number of buttons, or by dragging a square over the virtual monome.
…
[[insert Picture of widget creation]]
…
once one or more buttons have been selected on the virtual monome, the right hand side will change to an interface that allows the user to select one of four basic widget types:
…
[[insert Picture of which widget]]

…
[[insert Picture of shared preferences]]

…
first you define the host address. this is:
…
* the ip address of the computer that is running the software you are targeting,
* a colon, (:)
* and the port that you are addressing.

most of the current max patches will respond to localhost:8000. each widget can be set to a different host address. this may not seem important, but that means that you can easily communicate with many different pieces of software at the same time by assigning different ports, and even use a single monome to operate software on multiple computers simultaneously on the same local network by assigning different ip addresses to the different widgets.

…
the address pattern is the osc message that will be used to identify a message sent over OSC (currently serialio uses /box/press 0 0 1; /box/led 7 0 0; etc...).
…
one of the lovely things about mapd is that you can use any naming convention that fits OSC (see OpenSound Control) and mapd will check to see if the address pattern is legal. if it isn't, a little yellow triangle will pop up on the right hand side of the address pattern box. if you click on the triangle, a message box with a more detailed error message pops up.
…
[[insert Picture of yellow error]]
…
To insert a variable, use $1 and $2 to designate where the variable should fall in the OSC message ($2 is only needed in a two dimensional slider).
…
By using the same address pattern for more than one widget, a network of widget behaviors can be set up, so that for example one slider will interpolate, a series of radio buttons will assign different values and a second slider will not interpolate but have more steps than the first one, all only by using the same address pattern. play around with this to get a good feel for this feature of mapd.
…
…
…
h2. press button
…
[[insert Picture of press button]]
…
the preferences and proposed conventions vary in different ways over the four basic widget types. the press button allows you to set a down value and an up value to send over OSC. let us say that you want it to send out the value 1 when you press it down and the value 0 when you release it. if the host address is localhost:8000 and the address pattern is /rock/lobster, it will send the message /rock/lobster 1 when you press it and /rock/lobster 0 when you release it.
…
you can enable interpolation by clicking the interpolation toggle button. mapd will send out 10 values a second between ??button down value?? and ??button up value??. if both values are integers, mapd will output a series of integer messages, and if both values are floats, mapd will output a series of floats.
…
you can set the time that the widget will interpolate over, but the sampling rate is currently hardwired (this might change in the future).
…
you can delete the widget using the ??delete this widget?? button.
…
…
note: in this example, the x and y value of the button is set using fixed coordinates. this is a good convention that the community might want to take note of.
…

h2. toggle button

[[insert Picture of toggle button]]

the toggle button behaves very similarly to the press button, except you need to push it twice to turn it on and off.

h2. radio button

[[insert Picture of radio button]]

the radio button widget allows the user to set a separate return value for each button in the widget. interpolation is allowed, but as usually, only as long as all values are of the same type (i.e. integer or float). values are assigned by pressing on the corresponding button in the ??edit button?? graphic.

h2. 1d slider

[[insert Picture of 1d slider]]

to create a 1d slider, select a number of buttons on the virtual monome that all belong to the same row or column. you then assign a min and max value for the slider, and mapd will map the steps in-between on the selected buttons. otherwise it works similar to the toggle and press buttons.

h2. 2d slider

[[insert Picture of 2d slider]]

once again there is not a gigantic leap of functionality between the widget preference settings. the main difference with the 2d slider is that each axis of the slider can be assigned to a different host address and a different address pattern. independent ranges can be set for the x and y so that each dimension can send out different values to different programs on different computers.

h2. clearing space on the monome

when you want to delete a widget, or place a widget where you have previously placed a widget, select the buttons you want to use, and mapd will ask you if you want to delete all widgets that use any button that you have just chosen. yes will delete these widgets. re-select the buttons and assign the new widget.
…
Content was also deleted

DISCLAIMER: THIS IS A FAST DOCUMENTATION OF MAPD TO GET IT TO YOU ALL FASTER. MORE ACCURATE DOCUMENTATION WILL BE FORTHCOMING WITH SOME PICTURES AND FUN STUFF, AND MAYBE SOME CANDY, CAUSE I LIKE CANDY, AND ICECREAM, AND FRO-YO... (AND MAYBE SOME REAL-WORLD EXAMPLES)...

franzson — Tue, 30 May 2006 01:22:42 +0000

DISCLAIMER: THIS IS A FAST DOCUMENTATION OF MAPD TO GET IT TO YOU ALL FASTER. MORE ACCURATE DOCUMENTATION WILL BE FORTHCOMING WITH SOME PICTURES AND FUN STUFF, AND MAYBE SOME CANDY, CAUSE I LIKE CANDY, AND ICECREAM, AND FRO-YO... (AND MAYBE SOME REAL-WORLD EXAMPLES)...

h2. 1. overview of mapd

the mapd window is seperated into two main fields.

* on the left side there is a virtual monome for selecting buttons and to monitor button presses and widget status.
* on the right side, dialogs retaining to the behavior of a selected widget or a set of buttons becomes visible when needed.

h2. 2. adding a widget

mapd allows the user to select a number of buttons on the monome (on the virtual monome on the left hand side of the mapd window), by either clicking and shift-clicking any number of buttons, or by draging a square over the virtual monome.

once one or more buttons have been selected, the right hand side will first change to an interface that allows the user to select one of four types of widgets.

the widget types are:

* press button
* toggle button
* radio button
* slider (1d and 2d)

h2. 3. configuring a widget

once a widget type has been chosen, the right hand side changes to an interface that allows the user to configure the parameters of each widget. all of the widgets share the same basic behavior.

h3. host address

first you define the host address. this is the ip address of the computer that is running the software you are targeting, a colon, and the port that you are addressing. most of the current max patches will respond to localhost:8000. each widget can be set to a different host address. this may not seem important, but that means that you can easily communicate with many different pieces of software at the same time without having to filter anything, and even use a single monome to operate multiple computers on the same local network. (we will post a howto on this)

h3. address pattern

the address pattern is the osc message that will be used to send information over OSC (currently serialio uses /box/press 0 0 1, /box/led 7 0 0, etc...). you can use any naming convention that fits OSC (see OpenSound Control). mapd will check to see if the address pattern is legal. if it isn't, a little yellow triangle will pop out to make that clear to us. To insert a variable, you can use $1 and $2 ($2 only needed in a two dimentional slider).

after this point, each of the four widgets behaves slightly differently.

h3. press button

the toggle button allows you to set a down value and an up value to send over OSC. let us say that you want it to send out the value 50 when you press it and the value 3.796 when you release it. if the host address is localhost:8000 and the address pattern is /rock/lobster, it will send the message /rock/lobster 50 when you press it and /rock/lobster 3.796 when you release it.

the next settings have to do with interpolation. by turning interpolation on, the button will return a number of values between the up and down values over the time defined by interpolation time, 10 times a second (this will be definable later).

if we set the interpolation time to 1000 ms we should get a list of 10 values from 50 down to 10.

h3. toggle button

the toggle button behaves identical to the press button except you need to push it twice to turn it on and off.

h3. radio button

coming

h3. 1d slider

the 1d slider allows us you to set the min and max range of the slider in a similar way as the on/off messages in the toggle and press buttons.

if you define two sliders with the same address pattern, and have them interpolate, using each will update the value that the other will interpolate from. we will post examples of this

h3. 2d slider

the 2d slider can work either by sending out an address pattern with two arguments for x and y (by using $1 and $2 in the address pattern definition), or by suplying mapd with either a seperate host address or a seperate address pattern for the y value. NOTE! if you split the address patterns, you need to use $1 for the x value in the x address pattern and also $1 for the y value in the y address pattern.
…