inscore osc reference

8/2/2019 INScore OSC Reference

1/57

INScoreOSC Messages Reference

v.0.98

Grame, Centre national de cration musicale

ANR-08-CORD-010

April 5, 2012


2/57

INScore was initiated in the Interlude project, funded by the French National Research Agency [ANR- 08-CORD-010].


3/57

Contents

1 General format 11.1 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

1.2 Address space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

2 Application messages 4

3 Scene messages 6

4 Common components messages 74.1 Positioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

4.1.1 Absolute positioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84.1.2 Relative positioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94.1.3 Components origin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94.1.4 Components transformations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

4.2 Color messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104.2.1 Absolute color messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104.2.2 Relative color messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

4.3 The effect messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124.3.1 The blur effect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124.3.2 The colorize effect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134.3.3 The shadow effect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

4.4 The click and select messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

5 Time management messages 15

6 The set message 16

7 The get messages 197.1 Special get forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

8 Component specic messages 208.1 Pen control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208.2 Width and height control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208.3 Score pages management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

9 Time to space mapping 22

3


4/57


5/57

17.7 Differences to version 0.81 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4617.8 Differences to version 0.80 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

17.9 Differences to version 0.79 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4617.10Differences to version 0.78 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4617.11Differences to version 0.77 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4717.12Differences to version 0.76 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4717.13Differences to version 0.75 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4717.14Differences to version 0.74 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4717.15Differences to version 0.63 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4717.16Differences to version 0.60 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4817.17Differences to version 0.55 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4817.18Differences to version 0.53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4817.19Differences to version 0.50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

17.20Differences to version 0.42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49


6/57


7/57

Parameters types policy is relaxed: the system makes its best to convert a parameter to the expected type,which depend on the message string. When an incorrect type and when no conversion is applied, an incor-rect parameter message is issued.

1.2 Address space

The OSC address space is made of static and dynamic nodes, hierarchically organized as follows (gure1.1):

/ITL

/scene /scene /scene

/sync /signal /object /object /object

/sig /sig

Application

Scenes

Components

Signals

Figure 1.1: The OSC address space. Nodes in italic/blue are dynamic nodes.

OSC messages are accepted at any level of the hierarchy:

the application level responds to messages for application management (udp ports management, load-ing les, query messages)

at scene level, each node is associated to a window and respond to specic scene/window manage-ment messages.

the component level contains the scene objects and two static nodes: a signal node that may be viewed as a folder containing signals a sync node, in charge of the synchronization messages

the signals level contains signals i.e. objects that accept data streams an d that may be graphicallyrendered as a scene component.

In addition, an alias mechanism allows an arbitrary OSC address to be used in place of a real address. Analias message is provided to describe aliases:

alias

OSCAddress alias 1

OSCAlias message

2

[1] sets OSCAlias as an alias of OSCAddress . The alias may be optionally followed by a messagestring which is then taken as an implied message i.e. the alias is translated to OSCAddress message .

2


8/57

[2] removes OSCAddress aliases.

Note that regular expressions are not supported by the alias mechanism and could lead to unpredictableresults.

3


9/57

Chapter 2

Application messages

Application messages are accepted by the static OSC address /ITL . It covers the following messages:

ITLMsg

quit

rootPath path

port int32

outport int32

errport int32 mouse

show

hide

defaultShow

int32

load lePath

require int32

oscMsg

hello

quit : requests the client application to quit. rootPath : rootPath of an Interlude application is the default path where the application reads or

writes a le when a relative path is used for this le. The default value is the user home directory.Sending the rootPath message without parameter resets the application path to its default value.

port , outport , errport : changes the UDP port numbers. port denes the listening port number,outport and errport dene the ports used to send messages and error messages. The int32 pa-rameter should be a positive value in the range [1024-49150] .The default port , outport and errport values are 7000, 7001 and 7002.

mouse : hide or show the mouse pointer. defaultShow : changes the default show status for new objects.

4


10/57

The default defaultShow value is 1. load : loads a le previously saved using the save message (see section 4 p.7). Note that the load

operation appends the new objects to the existing scene. Whe necessary, its the sender responsabilityto clear the scene before loading a le.

hello : query the host IP number. The message is intended for ITL applications discovery. Answerto the query has the following format:

IP inPort outPort errPort where IP is sent as a string and port numbers as integer values. require : check for a version number equal or greater to the number given as argument. The version

number should be encoded as an integer value (for example: 76 for version 0.76, 112 for version1.12). An OSC message is associated to the require message with the same syntax and semanticdescribed in section 15 p.39. This message is triggered when the check fails.

The application supports the get messages for its parameters (see section 7 p.19). In addition, it providesthe following messages to query version numbers.

ITLRequest

get

version

guido-version

musicxml-version

version : version number request. guido-version : Guido engine version number request. musicxml-version : MusicXML and Guido converter version numbers request. Returns "not avail-

able" when the library is not found.

5


11/57

Chapter 3

Scene messages

A scene may be viewed as a window on the score elements. Its address is /ITL/ sceneIdentifier where sceneIdentifier is the scene name. It handles the following messages:

sceneMsg

new

del rootPath

pathload

lePathreset foreground

fullscreen

int32

commonMsg

new : creates a new scene and opens it in a new window. del : deletes a scene and closes the corresponding window. rootPath : rootPath of a scene is the default path where the scene reads or writes a le when a relative

path is used for this le. When no value has been specied, the application rootPath is used. load : loads an INScore le to the scene. Note that the OSC addresses are translated to the scene

OSC address. reset : clears the scene (i.e. delete all components) and resets the scene to its default state (position,

size and color). foreground : put the scene to foreground. fullscreen : requests the scene to switch to full screen or normal screen. The parameter is inter-

preted as a boolean value. Default value is 0 . commonMsg : see section 4 p.7.

6


12/57

Chapter 4

Common components messages

Common messages are mainly intended to control the graphic appearance of the components and of thescene. They could be sent to any address with the form /ITL/scene or /ITL/scene/ identifier whereidentifier is the unique identier string of a scene component.

commonMsg

show int32

del

export fullPathFileName

path

save lePath

+ rename

namePositionMsg

ColorMsg

TimeMsg

clickSelectMsg

show : shows or hides the destination object. The parameter is interpreted as a boolean value. Defaultvalue is 1 .

del : deletes the destination object. export : exports an object to an image le.

The rst form exports to the parameter le, which species a full path name. The le extension isused to infer the export format. Supported extensions and formats are: pdf, bmp, gif, jpeg, png, pgm, ppm, tiff, xbm, xpm .

7


13/57

The second form exports to path/ identifier .pdf . When path is a relative path, it exports torootPath/path/ identifier .pdf . A scene identier is scene .The third form exports to rootPath/ identifier .pdf .When the destination le is not completely specied (third form or missing extension), there is anautomatic numbering of output names when the destination le already exists.

save : recursively saves objects states to a le. The filePath can be relative or absolute. Whenrelative, an absolute path is build using the current rootPath . The optional + parameter indicatesan append mode for the write operation. The message must be sent to the /ITL address to save thewhole application state.

rename : rename the destination object. Changes its OSC address. Warning : OSC pattern match-ing allows to give the same name to a whole collection of objects; in this case, there is no way toindividually address an object when its name is shared with other objects.

PositionMsg are absolute and relative position messages. ColorMsg are absolute and relative color control messages. TimeMsg are time management messages. They are described in chaper 5 p.15.

clickSelectMsg are provided to query objects relative positions.

4.1 Positioning

PositionMsg

absPosMsg relPosMsg

originMsg

Graphic position messages are absolute position messages or relative position messages.

4.1.1 Absolute positioning

absPosMsg

x float32

y float32

z float32

angle

float32

scale float32

x y : moves the x or y coordinate of a component. By default, components are centered on their x , ycoordinates. The coordinates space range is [-1,1] .For a scene component, -1 is the leftmost or topmost position, 1 is the rightmost or bottommostposition. [0,0] represents the center of the scene .For the scene itself, it moves the window in the screen space and the coordinate space is orthonormal,based on the screen lowest dimension ( i.e. with a 4:3 screen, y=-1 and y=1 are respectively the exacttop and bottom of the screen, but neither x=-1 nor x=1 are the exact left and right of the screen).Default coordinates are [0,0] .

8


14/57

z : sets the z order of a component. The range is [0, [. z order is actually relative to the scenecomponents: objects of high z order will be drawn on top of components with a lower z order.Components sharing the same z order will be drawn in an undened order, although the order willstay the same for as long as they live.Default z order is 0.

angle : sets the angle value of a component, which is used to rotate it around its center. The angle ismeasured in clockwise degrees from the x axis.Default angle value is 0.

scale : reduce/enlarge a component. The range is [0, [. Default scale is 1 .

4.1.2 Relative positioning

relPosMsg

dx

float32

dy float32

dz float32

dangle float32

dscale float32

dx ,dy , etc. messages are similar to x ,y , etc. messages but the parameters represents values representa displacement of the current target value.

dscale is similar to scale but the parameters represents a scale multiplying factor.

4.1.3 Components origin

The origin of a component is the point ( xo , yo) such that the ( x, y) coordinates and the ( xo , yo) point coincidegraphically. For example, when the origin is the top left corner, the component top left corner is drawn atthe ( x, y) coordinates.

originMsg

xorigin

float32

yorigin float32 dxorigin

float32

dyorigin float32

xorigin ,yorigin are relative to the component coordinates space i.e. [ 1, 1], where -1 is the topor left border and 1 is the bottom or right border. The default origin is [0, 0] i.e. the component iscentered on its ( x, y) coordinates.

dxorigin ,dyorigin represents displacement of the current xorigin or yorigin .

9


15/57

4.1.4 Components transformations

A component tranformation species 2D transformations of its coordinate system. It includes shear andobject rotation.

transformMsg

rotatex

rotatey

rotatez

float32

shear x y

rotatex rotatey rotatez : rotates the component around the corresponding axis. Parameter valueexpresses the rotation in degrees.

shear transforms the component in x and y dimensions. x and y are oat values expressing thetransformation value in the corresponding dimension.

4.2 Color messages

ColorMsg

absColorMsg

relColorMsg Color messages are absolute or relative color control messages.

4.2.1 Absolute color messages

absColorMsg

color hsb

red

colorvalue

green colorvalue

blue colorvalue

alpha colorvalue

hue colorvaluesaturation

colorvaluebrightness

colorvalue

10


16/57

where

colorvalue

int32 float32

The value of a colors may be specied as integer or oat values. When expressed as oat, the value rangeis [-1,1] . The correspondence between the oat and integer ranges is expressed below.

color

color

r

g

b

r

g

b

a

hsbhsb

h

s

b

h

s

b

a

color : sets an object color. The color scheme is RGBA. When A is not specied, the color isassumed to be opaque. The integer data range for each color component is [0,255] . The oat datarange [-1,1] is linearly mapped to [0,255] . Default color value is [0,0,0,255] .

hsb : similar to color but using an HSBA scheme. When A is not specied, the color is assumed tobe opaque. The data range for S, B is [0,100] , [0,360] for H, and [0,255] for A.The oat data range [-1,1] is mapped to [0,100] for S and B.For H, 0 refers always to the red color and thus [0,1] is mapped to [0,180] and [-1,0] is mappedto [360,180] .

red ,green ,blue , hue ,saturation ,brightness ,alpha messages address only the specied part of the color using the ranges and schemes described above.

4.2.2 Relative color messages

relColorMsg

dcolor color dhsb

hsbdred

colorvalue

dgreen colorvalue

dblue colorvalue

dhue colorvalue

dsaturation colorvaluedbrightness

colorvaluedalpha

colorvalue

11


17/57

dred ,dgreen , etc. messages are similar to red ,green , etc. messages but the parameters valuesrepresent a displacement of the current target value.

dcolor and dhsb are similar andeach color parameter represents a displacement of the correspondingtarget value.

4.3 The effect messages

The effect message sets a graphic effect on the target object. These messages are experimental and couldbe changed or removed in a future version.

effectMsg

effect

none blur colorize

shadow

params

none : removes any effect set on the target object. blur, colorize, shadow : sets the corresponding effect. An effect always replaces any previous

effect. The effect name is followed by optional specic effects parameters.

Note that an effect affects the target object but also all the target slaves.

4.3.1 The blur effect

blurParams

radius

blurHint

Blur parameters are the blur radius and a rendering hint. The radius is an int32 value. By default, it is 5pixels. The radius is given in device coordinates, meaning it is unaffected by scale.

blurHint

performance

quality

animation

Use the performance hint to say that you want a faster blur, the quality hint to say that you prefer ahigher quality blur, or the animation when you want to animate the blur radius. The default hint value isperformance .

12


18/57

4.3.2 The colorize effect

colorizeParams

strength

color Colorize parameters are a strength and a tint color. The strength is a oat value. By default, it is 1.0. Astrength 0.0 equals to no effect, while 1.0 means full colorization.The color is given as a RGB triplet (see 4.2 p.10) by default, the color value is light blue (0, 0, 192).

4.3.3 The shadow effect

shadowParams

xoffset yoffset

color

blur

xoffset and yoffset are the shadow offset and should be given as int32 values. The default value is 8pixels. The offset is given in device coordinates, which means it is unaffected by scale.The color is given as a RGBA color (see 4.2 p.10) by default, the color value is a semi-transparent dark gray(63, 63, 63, 180)The blur radius should be given as an int32 value. By default, the blur radius is 1 pixel.

4.4 The click and select messages

Warning : the click and select messages are deprecated and will be removed in a future version.The click and select messages can be sent to any address with the form /ITL/scene/ identifier where identifier is the unique identier string of a scene component. They are intended to provideinformation about components relative positions: it returns a list of components identiers that are underthe clicked component: z order of the components is used for the under relationship.

click

click

clickMode

clickMode

topleft

bottomright

topright bottomleft

center

13


19/57

topleft , bottomright , topright , bottomleft , center : collects the components that are respec-tively under the top-left, bottom-right, top-right, bottom-left or center point of the target component.The clicked point is computed from the component bounding box.

Sent without parameter, the click message is equivalent to click topleft .

Reply of the click message has the following form:

clickReply

OSCAddress clickMode

identier

where identier is a component name. Note that identiers are sorted by decreasing z order.

select

select

selectMode

selectMode

intersect

include

intersect : looks for the components that are under the clicked component and that intersect withits bounding box.

include : looks for the components that are under the clicked component and that are included in itsbounding box.

Sent without parameter, the select message is equivalent to select intersect .

Reply of the select message is similar to click reply:

selectReply

OSCAddress selectMode

identier

14


20/57


21/57

Chapter 6

The set message

The set messages can be sent to any address with the form /ITL/scene/ identifier . The global formof the message is:

setMsg

set type dataIt sets a scene component data. When there is no destination for the OSC address, the component is rstcreated before being given the message. When the target destination type doesnt correspond to the messagetype , the object is replaced by an adequate object.Supported types are the following:

txt : a textual component.

html : an html component dened by an HTML string. gmn: a Guido score dened by a GMN string. svg : SVG graphics dened by a SVG string. graph : graphic of a signal. See section 13 p.32 for details about the graph objects data. rect : a rectangle specied by a width and height. Width and height are expressed in scene coordi-

nates space, thus a width or a height of 2 corresponds to the width or a height of the scene . ellipse : an ellipse specied by a width and height. polygon : a polygon specied by a sequence of points, each point being dened by its (x,y) coordi-

nates. Those coordinates are expressed in the scene coordinate space, but only taking in acount therelative position of the points ( i.e a polygon A = { (0,0) ; (1,1) ; (0,1) } is equivalent to a polygon B= { (1,1) ; (2,2) ; (1,2) } ).

curve : a sequence of 4-points bezier cubic curve. If the end-point of a curve doesnt match the start-point of the following one, the curves are linked by a straight line. The rst curve follows the lastcurve. The inner space dened by the sequence of curves is lled, using the object color. The pointscoordinates are handled as in a polygon .

line : a simple line specied by a point (x,y) expressed in scene coordinate space or by a width andangle. The point form is used to compute a line from (0,0) to (x,y), which is next drawn centered onthe scene.

txtf : a textual component dened by a le. htmlf : an html component dened by an HTML le. gmnf : a Guido score dened by a GMN le. svgf : vectorial graphics dened by a SVG le. img : an image le based component. The image format is infered from the le extension. video : a video le based component. The video format is infered from the le extension. Note that

navigation through the video is made using its date .

16


22/57

file : a generic type to handle le based objects. Actually, the file type is translated into a one of the txtf , gmnf , img or video types, according to the le extension (see table 6.1).

Format of the set message is:

setMsg

set

txt txtStream

html string

svg svgString

gmn

gmnString

graph signals

rect width height

ellipse width heightpolygon

x y

curve

x1 y1 x2 y2 x3 y3 x4 y4

line

xy x y

wa width angle setFile

Note that the default position of any component is [0,0] . Objects are drawn centered on their position.

txtStream

string

int32

float32

17


23/57

setFile

txtf

textFilePath

htmlf htmlFilePathgmnf

gmnFilePathsvgf

svgFilePathimg imgPathvideo

videoPathfile

lePath

See also: the application rootPath message (section 2) for le based objects.

Table 6.1: File extensions supported by the file translation scheme.

le extension translated type.txt .text txtf.htm .html htmlf

.gmn .xml gmnf.svg svgf

.jpg .jpeg .png .gif .bmp .tiff img.avi .wmv .mpg .mpeg .mp4 video

18


24/57

Chapter 7

The get messages

The get messages can be sent to any valid OSC address. It is intended to query the system state. It is thecounterpart of all the messages modifying this state. The result of the query is sent to the OSC output portwith the exact syntax of the counterpart message. The global form of the message is:

getMsg

get

getParam

The get message without parameter is the counterpart of the set message.

7.1 Special get forms

The get message without parameter addressed to a container (the application /ITL , a scene /ITL/scene ,the signal node /ITL/scene/signal ) is actually relayed to each of the container component.The get width and get height messages adressed to components that have no explicit width and height(text, images, etc.) return 0 as long as the target component has not been drew.

19


25/57

Chapter 8

Component specic messages

Some of the messages are specic to the component type . These messages can be sent to addresses of theform /ITL/scene/ identifier . They are ignored by objects that dont support the message.

8.1 Pen control

Messages accepted by the components types rect | ellipse | polygon | curve | line | graph .

penMsg

penColor color

penWidth float32 penStyle

penstyle

penstyle

solid

dash

dot

dashDot dashDotDot

The pen width default value is 0 (excepted for line objects, where 1.0 is the default value). It is expressedin arbitrary units (1 is a reasonable value). The pen style default value is solid .The color scheme is described in section 4.2.

8.2 Width and height control

Messages accepted by the components types rect | ellipse | graph.

20


26/57

whMsg

width

float32

height float32

8.3 Score pages management

Messages accepted by the components types gmn | gmnf .

scoreMsg

page int32

dpage int32

pageFormat float32

float32

columns int32

rows int32

get

pageCount

page : set the score current page dpage : set the score current page

pageFormat : set the page format. The parameters are the page width and height. Note that themessage has no effect when the score already includes a \ pageformat tag.

columns : for multi pages display: set the number of columns. rows : for multi pages display: set the number of rows. pageCount : a read only attribute, gives the score pages count.

21


27/57

Chapter 9

Time to space mapping

Time to space mapping refers to the description of relationship between an object local graphic space andits time space.

9.1 The map message

The map messages can be sent to any address with the form /ITL/scene/ identifier . It is intendedto describe the target object relation to time and sets a relation between an object segmentation and a timesegmentation. The global form of the message is:

mapMsg

map

mapName relation del

relation1

oat2DSegment relativeTimeSegment

2int2DSegment relativeTimeSegment

3

int1DSegment relativeTimeSegment

Segments are expressed as a list of intervals. For a 1 dimension resource, a segment is a made of a singleinterval. For a 2 dimensions resource, a segment is a made of 2 intervals: an interval on the x-axis and oneon the y-axis for graphic based resource, or an interval on columns and one on lines for text based resources.Intervals are right-opened.The different kind of relations corresponds to:

[1] a relation between a 2 dimensions segmentation expressed in oat values and a relative timesegmentation. These segmentations are used by rect, ellipse, polygon, curve, line com-ponents.

22


28/57

[2] a relation between a 2 dimensions segmentation expressed in integer values and a relative timesegmentation. These segmentations are used by txt, txtf, img components.

[3] a relation between a 1 dimension segmentation expressed in integer values and a relative timesegmentation. These segmentations are used by the graph component and express a relation betweena signal space and time.

Table 9.1 summarizes the specic segmentations used by each component type.The specied map can be named with an optional mapName string; this name can be further reused, duringobject synchronization, to specify the mapping to use. When mapName is not specied, the mapping has adefault empty name .The del command deletes the mapping specied with mapName, or the empty name mapping if no mapname is specied.

Table 9.1: Mapping resources for each component

component type segmentation typetxt, txtf int2DSegments

img int2DSegmentsrect, ellipse, polygon, curve oat2DSegments

graph int1DSegments

Note for html, htmlf + guido score mappings

relativeTimeSegment

( relativeTimeInterval )

oat2DSegment

( oatInterval oatInterval

)

int2DSegment

( intInterval intInterval

)

int1DSegment

(

intInterval )

relativeTimeInterval

[ rational , rational [

oatInterval

[ float32

, float32

[

intInterval

[

int32

,

int32

[

23


29/57

Relative time is expressed as rational values where 1 represents a whole note.

rational

int32 / int32

9.2 The map+ message

The map+ messages is similar to the map message but doesnt replace the existing mapping data: the speci-ed relations are added to the existing one.

mapAddMsg

map+

mapName

relation

9.3 Mapping les

The mapf messages is similar to the map message but gives the path name of a le containing the mappingdata, along with the optional map name.

mapfMsg

mapf

mapName

mapFilePath

24


30/57

Chapter 10

Synchronization

Synchronization between components is achieved at scene level: a sync node is automatically embeddedin the scene, its address is /ITL/scene/sync and it supports messages to add or remove a master / slaverelation between components or to query the synchronizations state.

sync

syncIdentier1

syncIdentier

syncmode

2

3get

identier

[1] this is the slave master form followed by an optional synchronization mode. It adds a slave / master relation between components identied by identier1 and identier2.

[2] this is the slave form that removes the slave synchronization for the component identied byidentier1.

[3] the get message is intended to query the synchronization state. The optional parameter is the

identier of a component,

Synchronization between components has no effect if any of the required mapping is missing (see table9.1).

syncIdentier 1

identier 2

identier : mapName Synchronization identiers indicates 1) the name of a scene component or 2) the name of a scene compo-nent associated to a mapping name.

25


31/57

Note that the sync node doesnt responds to common component messages, but accept the get message.The get message without parameter is equivalent to a get message addressed to each object declared in thesync node.

10.1 Synchronization modes

syncmode

syncAlignment syncStretch

mapName

syncAlignment

syncOver

syncTop

syncBottom

syncStretch

h v hv

Synchronizing a component A to a component B has the following effect:

A position (x,y) is modied to match the B time position corresponding to A date. depending on the optional syncStretch , A width and/or height are modied to match the corre-

sponding B dimensions (see below). if A date has no graphic correspondance in B mapping (the date is not mapped, or out of B mapping

bounds ), A wont be visible.

The synchronization alignment modes have the following effects on the slave y position: syncOver : the center of the slave is aligned to the master center. syncTop : the bottom of the slave is aligned to the top of the master. syncBottom : the top of the slave is aligned to the bottom of the master.

The default synchronization mode is syncOver .The synchronization stretch modes have the following effects on the slave dimensions:

h: the slave is horizontally stretched to align its begin and end dates to the corresponding masterlocations.

v: the slave is vertically stretched to the master vertical dimension. hv : combines the above parameters.

26


32/57

By default, no stretching is applied.The optional mapName string argument species which mapping of the master object should be used (see

map message). If the master doesnt have a mapping with the specied mapName, the slave object wontbe visible. Not specifying the map name is equivalent to an empty name mapping.

27


33/57


34/57

11.2 Score browsing and layout

scoreMsg

page int32

pageFormat float32

float32

columns int32

rows int32

page : sets the rst displayed page. Index starts at 1 . Default: 1 . pageFormat : sets the scores page format, in cm (Warning: the pageFormat is not used when another

page format is hard-coded in the scores Guido code). Default: (21.0 , 29.7) .

columns : as multiples pages can be displayed and organized in a grid of pages , columns sets thenumber of columns in the grid. Default: 2 . rows : as multiples pages can be displayed and organized in a grid of pages , rows sets the number of

rows in the grid. Default: 1 .

11.3 Score queries

scoreQuery

get

pageCount

pageDate

int32

pageCount : gives the score page count. pageDate : gives the time location of a page, which number is given as argument. The system

reply has the form pageDate pageNum date where pageNum is the request page number given asargument and date is the page time location expressed as a ra tional number.

Note that a score object duration is automatically set to the score duration. It can be retrieved using a getduration message.

29


35/57

Chapter 12

Virtual address space

Virtual address space extends the OSC address scheme to objects automatically embedded into other objects.

12.1 File watcher

The fileWatcher is a component automatically embedded at scene level.It receives messages at the address /ITL/scene/fileWatcher .The fileWatcher service monitors les on demand; it is aware of le modications and le removals (orrenamings, which is equivalent). The fileWatcher works with associations between a le and an OSCmessage : when a le change occurs, the le watcher posts the associated OSC message.The fileWatcher is controlled with 4 messages:

the add message is used to add a new le - OSC message association ; the remove message is used to remove a le - OSC message association. the clear message is used to clear all existing associations. the get message is used to retrieve the current associations.

leWatcher

add lePath OSCMessage

remove lePath OSCMessage

OSCAddress clear

get

where OSCMessage is any message complying to the format desscribed in section 1 p.1.Example:

/ITL/scene/fileWatcher add fuga.gmn /ITL/scene/score set gmnf fuga.gmn;

Note that the get query returns a set of messages complying to the add message format.

30


36/57


37/57

Chapter 13

Signals and graphic signals

The graphic representation of a signal is approached with graphic signals . As illustrated in gure 13.1,a graphic representation of a signal could be viewed as a stream of a limited set of parameters : the ycoordinate, the graph thickness h and the graph color c. A graphic signal is a composite signal including aset of 3 parallel signals that control these parameters. Thus the INScore library provides messages to createsignals and to combine them into graphic signals .

Figure 13.1: A simple graphic signal, dened at time t by a coordinate y, a thickness h and a color c

13.1 The signal virtual address space.

A scene includes a virtual address space, which OSC address is /ITL/scene/signal . This address spaceis reserved for simple signals as well as for composing signals in parallel.The signal virtual address space supports only the get messages that gives the list of the dened signalswith a set of messages complying to the syntax dened in section 13.1.1 .

13.1.1 Simple signals.

The signal messages can be sent to any address with the form /ITL/scene/signal/ identifier , whereidentifier is a unique signal identier. The set of messages supported by a signal is the follow-ing:

32


38/57

simpleSignal1

float32

2size

int32

3default

float32

4get

size

default

5 reset 6

del

[1] push an arbitrary data count into the signal buffer. The data range should be [-1,1] . Note thatthe signal buffer behaves like a ring buffer, thus data are wrapped when the data count if greater thanthe signal size.

[2] the size message sets the signal buffer size. When not specied, the buffer size value is the sizeof the rst data message.

[3] the default message sets the default signal value . A signal default value is the value returnedwhen a query asks for data past the available values.

[4] the get gives the signal values. The size and default parameters are used to query the signalsize and default values.

[5] the reset message clears the signal data. [6] the del message deletes the signal from the signal space. Note that it is safe to delete a signal

even when used by a graphic signal.

Example:

/ITL/scene/signal/null 0.0;

creates a constant signal named null , which value is 0 .

13.1.2 Composing signals in parallel.

Composing signals in parallel produces a signal which value at a time t is a vector of the composed signalsvalues. Thus an additional property is dened on parallel signals : the signal dimension which is size of the signals values vector. Note that the dimension property holds also for simple signals. The format of themessages for parallel signals is the following:

33


39/57

parallelSignal1

set

signal

2 projectionString

float32

3

get

dimension

where

signal4

identier 5float32

[1] denes a new signal composed of the signals list and which address is the message OSC address.A signal list element is dened as:

[4] an identifier i.e. a signal name refering to an existing signal in the signal virtual addressspace.

[5] or as a oat value. This form is equivalent to an anonymous constant signal holding thegiven value.

[2] sets the values of the signals addressed by a projection string. See section 13.1.3 p.34. [3] in addition to the get format dened for signals, a parallel signal supports the get dimension

message, which gives the number of simple signals in parallel. It is actually the sum of each signaldimension. The dimension of a simple signal is 1.

Note that for a parallel signal:

the get message gives the list of the signals in parallel with the exact form of the composing messagein [1].

the get size message gives the maximum of the components size. the get default message gives the default value of the rst signal.

13.1.3 Signals projection.

Individual components of a parallel signal may be addressed using a projection string which is denedas:

projectionString

[ int32

int32

]

The projection string is made of a index value , followed by an optional parallel marker ( ), followed byan optional step value , all enclosed in brackets. The index value n is the index of a target signal. When

34


40/57

the parallel marker option is not present, the values are directed to the target signal and the message isequivalent to: /ITL/scene/signal/target values...where target is the name of the target signal addressed by n .Note that:

the message is ignored when n is greater than the number of signals in parallel. Default n value is 0 . setting directly the values of a simple signal or as the projection of a parallel signal are equivalent.

The parallel marker ( ) and the step value w options affect the target signals. Lets consider s[n] as thesignal at index n . The values are distributed in sequence and in loop to the signals s[n], s[n+w]...s[m]where m is the greatest value of the index n+(w.i) that is less than the signal dimension. The default stepvalue is 1 .Example:

the message:

/ITL/scene/signal/target [2] 0.1 0.2

is equivalent to the following messages:

/ITL/scene/signal/target [2] 0.1/ITL/scene/signal/target [3] 0.2

13.2 Graphic signals.

A graphic signal is created in the standard scene address space. A simple graphic signal is dened by aparallel signal controling the y value, the graphic thickness and the color at each time position. The coloris encoded as HSBA colors (Hue, Saturation, Brightness, Transparency). The mapping of a signal value([-1,1] ) to the HSBA color space is given by the table 13.1.

Figure 13.2: The HSB color space

A graphic signal responds to common component messages (section 4 p.7). In addition, it supports thefollowing messages:

35


41/57

Table 13.1: HSBA color values.

parameter mappinghue [-1,1] corresponds to [-180,180] angular degree where 0 is red.saturation [-1,1] corresponds 0% to 100% saturation.brigthness [-1,1] corresponds 0% (black) to 100% (white) brithgness.

transparency [-1,1] corresponds 0% to 100% tranparency.

graphicSignal

set

graph signalIdentier

get

get dimension

the set message is followedby the graph type and a signalIdentifier , where signalIdentifier

must correspond to an existing signal from the signal address space. In case signalIdentifierdoesnt exist, then a new signal is created at the signalIdentifier address with default values.

the get message is the counterpart of the set message (see section 7 p.19). the get dimension message gives the number of graphic signals in parallel (see section 13.2.2 p.36).

13.2.1 Graphic signal default values.

As mentionned above, a graphic signal expects to be connected to parallel signals having at least an ycomponent, a graphic thickness component and HSBA components. Thus, from graphic signal viewpoint,the expected dimension of a signal should be equal or greater than 6. In case the signalIdentifierdimension is less than 6, the graphic signal will use the default values dened in table 13.2.

Table 13.2: Graphic signal default values.

parameter default valuey 0 the center line of the graphic

thickness 0hue 0 meaningless due to brigthness value

saturation 0 meaningless due to brigthness valuebrigthness -1 black

transparency 1 opaque

13.2.2 Parallel graphic signals.

When the dimension d of a signal connected to a graphic signal is greater than 6, then the input signal isinterpreted like parallel graphic signals. More generally, the dimension n of a graphic signal is:

n | n N 6.(n 1) < d 6.n

where d is the dimension of the input signal.Note than when d is not a mutiple of 6, then the last graphic signal makes use of the default values men-tionned above.

36


42/57

Chapter 14

FAUST plugins

FAUST [Functional Audio Stream] 1 is a functional programming language specically designed for real-time signal processing and synthesis. A FAUST/INScore architecture allows to embed FAUST processorsin INScore, for the purpose of signals computation. A FAUST/INScore plugin is viewed as a parallelsignal and thus it is created in the signal address space. Thus and similarly to signals, a FAUST plugin isassociated to OSC addresses in the form /ITL/ scene /signal/ name where name is a user dened name.

faustprocessor

set faust path

A FAUST processor is created with a set message followed by the faust type, followed by the plugin pathname. Thus the faust name is a reserved signal name.

14.1 Specic messages

A FAUST processor is characterized by the numbers of input and output channels and by a set of param-eters. Each parameter carries a name dened by the FAUST program. The set of messages supported bya FAUST processor is the set of signals messages extended with the parameters names and with specicquery messages.

faustmessage

signalMsgs 1 msg float32 2

get in

out

1 msg is any of the FAUST processor parameters, as dened by the FAUST program.2 the get message is extended to query the FAUST processor: in and out give the number of input

and output channels.

1http://faust.grame.fr

37
http://faust.grame.fr/http://faust.grame.fr/


43/57

14.2 Feeding and composing FAUST processors

A FAUST processor accepts oat values as input, which are taken as interleaved data.From composition viewpoint, a FAUST processor is a parallel signal which dimension is the number of output channels. Thus, a FAUST processor can be used like any parallel signal. However, the signalidentier dened in 13.1.2 is extended to support adressing single components of parallel signal as fol-lows:

signal

identier

/ n

float32

where n selects the signal #n of a parallel signal. Note that indexes start at 0.

38


44/57

Chapter 15

Events and Interaction

Interaction messages are user dened messages associated to events and triggered when these events occur.These messages accept variables as message arguments.The general form of the message is:

interactMsg

watch

watch+

1 what

oscMsg

watch : clears the messages associated to the event and when specied, associates the new messageto the watched event. watch without arguments ([1]) clears all the messages associated to all events.

watch+ : adds a message to the watched event message list.

The associated OSC message is any valid OSC message (not restricted to the Interlude message set), withan extended address scheme, supporting IP addresses or host names and udp port number to be speci-ed as OSC addresses prex. The message parameters are any valid OSC type or variables (see section15.3).

oscMsg

fullAddress

OSCAddress parameters variable

fullAddress

IPAddress hostname

: port

39


45/57

15.1 Interaction messages

Events currently watchable are:

what

mouseDown

mouseUp

mouseEnter

mouseLeave

mouseMove doubleClick

Example:

/ITL/scene/myObject watch mouseDown "/ITL/scene/myObject" "show" 0;

Request the object myObject to watch mouseDown events and send a message to itself.

/ITL/scene/myObject watch mouseDown "host.domain.org:12100/an/address" "start";

Request the object myObject to watch mouseDown events and send a "start" message to host.domain.org onudp port 12100 to OSC address /an/address

15.2 Notication messagesEvents currently watchable are:

what

timeEnter timezone

timeLeave timezone

newElement

timezone

int32 int32 int32 int32 A time zone is dened by 2 dates expressed as rational values (i.e. with 4 integers).The newElement event is supported at scene level only and triggered when a new element is added to thescene.

15.3 Variables

Variables denote values computed when an event is triggered. These values are send in place of the vari-able. A variable name starts with a $ sign. Currently, the following variables are supported by mouseevents:

40


46/57

variable

xy absx absy

sx

sy date

name

address

xy

x y

[low,high]

$x $y : denotes the mouse pointer position at the time of the event. The values are in the range [0, 1]

where 1 is the object size in the x or y dimension. The value is computed according to the objectorigin: it represents the mouse pointer distance from the object x or y origin (see 4.1.3 p.9). $xand $y variables support an optional range in the form [low, high] that transforms the [0, 1] values

range into the [low , high ] range. $absx $absy : denotes the mouse pointer absolute position at the time of the event. The values

represent a pixel position relative to the top-left point of the target object. Note that this positionis unaffected by scale. Note also that the values are not clipped to the object dimensions and couldexceed its width or height or become negative in case of mouse move events.

$sx $sy : denotes the mouse pointer position in the scene coordinates space.

date

date

rdate

: mapname

[n/d]

$date : denotes the object date corresponding to the mouse pointer position at the time of the event.

It is optionnaly followed by a colon and the name of the mapping to be used to compute the date.The $date variable is replaced by its rational value (i.e. two integers values). The optional rationalenclosed in brackets may be used to indicate a quantication: the date value is rounded to an integercount of the specied rational value.

$rdate : is similar to $date but ignores the target current date: the date is relative to the objectmapping only.

$name , $address : replaced by the target object name or OSC address. Note that in case of newElementevent, the target object is the new element.

Note that a variable can be used several times in a message, but several $date variables must always referto the same mapping.

41


47/57


48/57

Chapter 16

Scripting

Since INScore saves its states as text les containing lists of OSC messages, it becomes natural to designINSCore scenes using these messages as a textual scripting language. For a better support of scripting,variables have been introduced to provide a better parameters control and programming languages havebeen embedded to generate messages algorithmically.

16.1 Variables

A variable may hold any value supported by the parameter types. string must be enclosed in simple ordouble quotes. It is declared as follows:

variabledecl

ident = int32 float32

string

;

A variable may be used in place of any message parameter. A reference to a variable must have the form$ident where ident is a previously declared variable.Note that interaction messages may also use variables with similar reference forms ($ident). There ishowever no ambiguity concerning these references: interaction variables are always passed as strings andshould be quoted, scripts variables as used without quotes.Example:

x=0.5;/ITL/scene/a x $x;/ITL/scene/b x $x;

16.2 Languages

INScore supports Javascript and Lua as scripting languages. Javascript is embedded by default (using the v8engine - see http://code.google.com/p/v8/ . You need to recompile INScore to embed the Lua engine(http://www.lua.org/ ).The principle of scripting using a programming language is the following: you can embed javascript of lua code in an INScore le in a way similar to scripts embedded into html les. This code is expected to

43
http://code.google.com/p/v8/http://code.google.com/p/v8/http://www.lua.org/http://www.lua.org/http://www.lua.org/http://code.google.com/p/v8/


49/57

produce INScore messages on output.

lang

The output of the script section is parsed like INScore messages.Note that INScore variables are exported to the current language environment.Example:

44


50/57

Chapter 17

Changes list

17.1 Differences to version 0.96

objects position, date and watched events preserved through type change bug in quantied dates corrected (null denominator set to the quantied value) new alias message providing arbitrary OSC addresses support bug in parser corrected: backslash escape only and " chars, otherwise it is literal guido score map makes use of the new guidolib extended mapping API for staff and system chords map correction (corrected by guido engine)


switch to v8 javascript engine lua not embedded by default


new mouse show/hide message supported at application level (see section 2 p.4) graphic signal supports alpha messages at object level javascript and lua embedded and supported in inscore scripts (see section 16.2 p.43). bug correction in sync delete (introduced with version 0.90)


bug corrected: crash with messages addressed to a signal without argument date and duration messages support one arg form using 1 as implicit denominator value the one arg

form accepts oat values (see section 5 p.15).


bug in sync management corrected (introduced with the new sync parsing scheme)

45


51/57


at application level: osc debug is now on by default new scripting features (variables) (see section 16.1 p.43). ITL le format change:

- semicolon added at the end of each message- // comment not supported any more- % comment char replaced by !- new variables scripting features- single quote support for strings- messages addressed to sync node must use the string format

new grid object for automatic segmentation and mapping


new Faust plugins for signals processing colors management change: all the color models (RGBA and HSBA) accept now oat values that are

interpreted in the common [-1,1] range. For the hue value, 0 always corresponds to red whateverthe scale used.

stretch adjustment for video objects (corrects gaps in sync h mode) support for opening inscore les on the command line system mapping correction splash screen and about menu implemented by the viewer


behavior change with synchronization without stretch: now the system looks also in the slave mapfor a segment corresponding to the master date.

$date variable change: the value is now (0,0) when no date is available and $date is time shiftedaccording to the object date.

date message change: the date 0 0 is ignored


corrects the map not saved by the save message issue corrects get map output: 2D segments were not correctly converted to string


crash bug corrected for the save message addressed to /ITL message policy change: relaxed numeric parameters policy (oat are accepted for int and int for oat) bug in get watch for time events corrected (incorrect reply)

Known issues:

map not saved by the save message

46


52/57


guido system map extended: supports at map or subdivided map (see section 11.1 p.28). new shear and rotate transformations messages (see section 4.1.4 p.10). new rename message to change an object name (and thus its OSC address) (see section 4 p.7). relaxed bool parameter policy: objects accept oat values for bool parameters automatic numbering of exports when destination le is not completely specied i.e. no name, no

extension. (see section 4 p.7). quantication introduced to $date variable (see section 15.3 p.40). reset message addressed to a scene clears the scene rootPath


get guido-version and musicxml-version messages supported by the application (see section 2

p.4). save message bug correction - introduced with version 0.70: only partial state of objects was saved rootPath message introduced at scene level (see section 3 p.6). scene name translation strategy change: only the explicit scene name is translated by the scene load

message handler into the current scene name, other names are left unchanged. bitmap copy adjustment in sync stretched mode is now only made for images


new require message supported by the /ITL node (see section 2 p.4). new event named newElement supported at scene level (see section 15.2 p.40). new name and address variables (see section 15.3 p.40). new system map computation making use of the new slices map provided by the guidolib version

1.42 INScore API: the newMessage method sets now the message src IP to localhost With the previous

version and the lack of src IP, replies to queries or error messages could be sent to undened addresses(and mostly lost).

bug corrected with ellipse and rect : integer graphic size computation changed to oat (preventsobjects disappearance with small width or height)

bug in scene export: left and right borders could be cut, depending on the scene size corrected byrendering the QGraphicsView container instead the QGraphicsScene

crash bug with $date:name corrected: crashed when there is no mapping named name .

17.14 Differences to version 0.74 new map+ message (see section 9.2 p.24). the click and select messages are deprecated (but still supported). They will be removed in a

future version (see section 4.4 p.13).


new dpage message accepted by gmn objects (see section 8.3 p.21). x and y variables: automatic range type detection (int | oat) set txt message: accepts polymorphic stream like parameters (see section 6 p.16). drag and drop les support in INScore viewer

47


53/57

interaction variables extension: $sx , $sy variables added to support scene coordinate space (seesection 15.3 p.40).

automatic range mapping for $x , $y variables. new $self and $scene variables in the address eld (see section 15.5 p.42). OSC identiers characters set extended with _ and - (see section 1 p.1). support for multiple scenes: new , del and foreground messages (see section 3 p.6). load message supported at scene level (see section 3 p.6). get watch implemented. watch message without argument to clear all the watched events (see section 15.3 p.40). order of rendering and width, height update corrected (may lead to incorrect rendering) bug with gmn score corrected: missing update for page, columns and rows changes. package delivered with the Guido Engine version 1.41 that corrects minimum staves distance and

incorrect mapping when optimum page ll is off.

17.16 Differences to version 0.60 new mousemove event (see section 15.1 p.40). interaction messages accept variables ($x, $y, $date...) (see section 15.3 p.40). SVG code and les support (see section 6 p.17). set line message change: the x y form is deprecated, it is replaced by the following forms:

xy x y (equivalent to the former form) and wa width angle (see section 6 p.16). new effect message (section 4.3 p.12). utf8 support on windows corrected transparency support for stretched synchronized objects corrected multiple application instances supported with dynamic udp port number allocation. command line option with port portnumber option to set the receive udp port number at startup.


new xorigin and yorigin messages (section 4.1.3 p.9). new interaction messages set (section 15 p.39). alpha channel handled by images and video bug correction in line creation corrected (false incorrect parameter returned) bug correction in line get message handling memory leak correction (messages not deleted)

Known issues:

incorrect graphic rendering when sync a b is changed to sync b a in the same update loop incorrect nested synchronization when master is horizontaly stretched,


ITL parser corrected to support regexp in message string (used by messages addressed to sync node) format of mapping les and strings changed (section 9.1 p.22). format of sync messages extended to include map name (section 10 p.25). signal node: garbage message removed new reset message for the scene (/ITL/scene) (section 3 p.6). new version message for the application (/ITL) (section 2 p.4). new reset message for signals (section 13.1.1 p.32).

48


54/57

bug parsing messages without params corrected slave segmentation used for synchronization new H synchronization mode (preserves slave segmentation) crash bug corrected for load message and missing ITL les


Graphic signal thickness is now symmetrically drawn around y position. ITL le format supports regular expressions in OSC addresses. IP of a message sender is now used for the reply or for error reporting. new line object (section 6 p.16). new penStyle message for vectorial graphics (section 8 p.20). new color messages red, green, blue, alpha, dcolor, dred, dgreen, dblue (section 4 p.7

and 4.1.2 p.9).

color values for objects are bounded to [0,255] get map message behaves according to new map message (section 7 p.19). get width and get height is now supported by all objects (section 7 p.19). bug in signal projection corrected (index 0 rejected) bug in signals default value delivery corrected new pageCount message for guido scores debug nodes modied state propagated to parent node (corrects the debug informations graphic up-

date issue) rational values catch null denominator (to prevents divide by zero exceptions).


identifier specication change (section 1 p.1). new application hello and defaultShow messages (section 2 p.4). new load and save messages (sections 2 p.4 and 4 p.7). click and select messages (section 4.4 p.13):

rightbottom and leftbottom modes renamed to bottomright and bottomleft new center mode for the click message query mode sent back with the reply both for click and select messages

new file , html and htmlf types for the set message (section 6 p.16). get syntax change for the scene (section ?? p.?? ). fileWatcher messages completely redesigned (section 12.1 p.30). mappings can be identied by names (section 9.1 p.22). rect, ellipse, curve, line and polygon object support graphic to relative-time mapping new synchronization modes for Guido scores: voice1, voice2, ... , staff1, staff2, ... , system, page

(section 11.1 p.28). Guido mapping manages repeat bars. Graphic signals messages design (section 13.2 p.35).

49


55/57

Index

ColorMsg, 10 ITLMsg, 4 ITLRequest, 5OSCAddress, 1OSCMessage, 1PositionMsg, 8

absColorMsg, 10absPosMsg, 8alias, 2blurHint, 12blurParams, 12click, 13clickMode, 13clickReply, 14color, 11colorizeParams, 13colorvalue, 11commonMsg, 7

date, 41debug, 31effectMsg, 12 faustmessage, 37 faustprocessor, 37 leWatcher, 30 oat2DSegment, 23 oatInterval, 23 fullAddress, 39getMsg, 19graphicSignal, 35hsb, 11identier, 1int1DSegment, 23int2DSegment, 23intInterval, 23interactMsg, 39lang, 44mapAddMsg, 24mapMsg, 22mapfMsg, 24msgVar, 42originMsg, 9oscMsg, 39 parallelSignal, 33

penMsg, 20 penstyle, 20 projectionString, 34rational, 24relColorMsg, 11relPosMsg, 9

relation, 22relativeTimeInterval, 23relativeTimeSegment, 23sceneMsg, 6 scoreMapMsg, 28scoreMsg, 21 , 29scoreQuery, 29select, 14selectMode, 14selectReply, 14setFile, 17 setMsg, 16 , 17

shadowParams, 13signal, 34 , 38simpleSignal, 32sync, 25syncAlignment, 26 syncIdentier, 25syncStretch, 26 syncmode, 26 time, 15timeMsg, 15timezone, 40transformMsg, 10txtStream, 17 variable, 40variabledecl, 43whMsg, 20what, 40 xy, 41

Common messagesalias, 2angle, 8click, 13

bottomleft, 14bottomright, 14

50


56/57

center, 14topleft, 14topright, 14

color, 11alpha, 11blue, 11brightness, 11green, 11hue, 11red, 11saturation, 11

del, 7 dx, 9dy, 9dz, 9

export, 7 get, 19hsb, 11map, 22map+, 24mapf, 24save, 7 scale, 8select, 14

include, 14intersect, 14

set, 17 show, 7 x, 8 y, 8 z, 8

Effect messageseffect

blur, 12colorize, 12shadow, 12

faustprocessor in, 37

max, 37 min, 37 out, 37 set, 37

leWatcher, 30add, 30clear, 30get, 30remove, 30

Graphic signaldimension, 36 get, 36

set, 36

Interactiontimezone, 40doubleClick, 40mouseDown, 40mouseEnter, 40mouseLeave, 40mouseMove, 40mouseUp, 40newElement, 40timeEnter, 40timeLeave, 40variable

absx, 41

absy, 41address, 41date, 41name, 41sx, 41sy, 41 x, 41 y, 41

watch, 39watch+, 39

ITL messagesdefaultShow, 4

errport, 4guido-version, 5hello, 4load, 4mouse, 4musicxml-version, 5outport, 4 port, 4require, 4rootPath, 4version, 5

Position messagesabsolute

angle, 8scale, 8 x, 8 y, 8 z, 8

color dalpha, 12dblue, 12dbrightness, 12dcolor, 12dgreen, 12

51


57/57

dhsb, 12dhue, 12dred, 12dsaturation, 12

relativedangle, 9dscale, 9dx, 9dxorigin, 9dy, 9dyorigin, 9dz, 9 xorigin, 9 yorigin, 9

Scene messages, 6 del, 6 foreground, 6 fullscreen, 6 load, 6 new, 6 reset, 6 rootPath, 6

Scriptinglanguage, 44variable, 43

Set type

curve, 17 ellipse, 17 le, 18gmn, 17 gmnf, 18graph, 17 html, 17 htmlf, 18img, 18line, 17 polygon, 17 rect, 17 svg, 17 , 18txt, 17 txtf, 18video, 18

signal, 33 parallel signal, 34

get, 34list, 34 projection string, 34

i l i l

reset, 33size, 33

Specic messagesheight, 21 penColor, 20 penStyle, 20

dash, 20dashDot, 20dashDotDot, 20dot, 20solid, 20

penWidth, 20score

columns, 21dpage, 21

page, 21 pageCount, 21 pageFormat, 21rows, 21

width, 21Synchronization, 25

syncIdentier, 25get, 25Guido map, 28

page, 28staff, 28system, 28systemat, 28voice, 28

syncAlignment, 26 syncBottom, 26 syncOver, 26 syncTop, 26

syncmode, 26 syncStretch, 26

h, 26 hv, 26 v, 26

Time messages

absolutedate, 15duration, 15

relativeclock, 15ddate, 15dduration, 15durClock, 15

Transform messages

inscore osc reference

Documents