Medien Wiki - User contributions [en]

GMU:Tutorials/Networking/Controlling MAX-MSP with TheCaptury

2016-10-22T18:50:01Z

Ben: /* Grabbing the Bone Vector Coordinates */

= Controlling Max-Msp with The Captury =

== Overview ==

The following tutorial covers the process of connecting Max/Msp (short: Max) with "the Captury" tracking software and explains how use the out coming information.

[[File:overview.png|400px]]

== UDP ==

UDP (User Datagram Protocol) is an internet protocol which provides communication which no handshaking. It also let you define which port on the destination IP you want to address. In our case it is used to transmit messages in OSC format.

In Max/Msp you set up an udpsend object. It need two parameters: IP address and port number (e.g.: "141.54.0.1." or "kosmos.uni-weimar.de" and "1065").

[[File:img01.png|400px]]

== OSC-Syntax ==

OSC-messages are build up like an path in your PC (e.g.: "/Animal/Dog/Dackel/Colour/ brown" or "/Animal/Dog/Dackel/Amount/ 45").
Under this path syntax you can send any datatypes (symbol, integer, float as given in the example). This message order is important. Because you can only find what has been sent under the exact path.
You would not search the amount of Dackels under path ".../Colour".

== Custom Port Configuration ==

Since we can change the port number on that we want to receive messages (in case you want to split up channels on one machine or distribute messages to different receivers), we can configure the port we want to receive messages on.
In our case we use this feature to tell "the Captury" software where we want to receive any kind of messages.

In Max we can make this work by calling the [udpsend] object with following message: "/configure/port $1" ($1 is the Max syntax style for variables).

[[File:img02.png|400px]]

== Subscribe to any Skeleton ==

After we have been setting up the port we want to receive on, we can tell "the Captury" what we want to receive. We are doing this by calling the following message to [udpsend]: "/subscribe/John-Doe/blender/Root/vector 50. 0. 100.".

Since subscriptions will expire after a while, we call this message every 10 seconds. Therefore we use the Max own metronome object called [metro] which will repeat to put out bangs and so trigger the message. The toggle [X] will turn ON the metro.

[[File:img03.png|400px]]

== Grabbing the Bone Vector Coordinates ==

The [udpreceive] object work the other way around. It can receive messages coming from a specific IP and port.
After [udpreceive] we can route the out coming array of information by using the OSC-Syntax again.
With the [route] object we can exactly determine what branch of the string we want to access, in this case we write "/route/John-Doe/blender/Root/vector" to get exactly what we asked for. Afterwards we unpack the containing floats, which represent the x, y and z value of our subscripted bone.

[[File:img08.png|400px]]

== Using the Data Stream from The Captury ==

In the Max domain - instead of patching cords - we can send and receive data as well. To do this we simply write [send] or [receive] and a unique name, which serves as a kind of address: in our case it is [s x-coord] (s as the short form for send is also possible).

Now we can receive the values that have been sent and use them for very own purposes. In my example I display the data first - to have a kind of overview - to see which direction the information is heading to or where it is coming from.

[[File:img06.png|400px]]

Happy patching!

For questions please contact me: benjamin[.] vossler[at] uni-weimar[.] de

File:Img08.png

2016-10-22T18:49:58Z

Ben: File uploaded with MsUpload

File uploaded with MsUpload

GMU:Tutorials/Networking/Controlling MAX-MSP with TheCaptury

2016-10-22T18:47:06Z

Ben: /* UDP */

= Controlling Max-Msp with The Captury =

== Overview ==

The following tutorial covers the process of connecting Max/Msp (short: Max) with "the Captury" tracking software and explains how use the out coming information.

[[File:overview.png|400px]]

== UDP ==

UDP (User Datagram Protocol) is an internet protocol which provides communication which no handshaking. It also let you define which port on the destination IP you want to address. In our case it is used to transmit messages in OSC format.

In Max/Msp you set up an udpsend object. It need two parameters: IP address and port number (e.g.: "141.54.0.1." or "kosmos.uni-weimar.de" and "1065").

[[File:img01.png|400px]]

== OSC-Syntax ==

OSC-messages are build up like an path in your PC (e.g.: "/Animal/Dog/Dackel/Colour/ brown" or "/Animal/Dog/Dackel/Amount/ 45").
Under this path syntax you can send any datatypes (symbol, integer, float as given in the example). This message order is important. Because you can only find what has been sent under the exact path.
You would not search the amount of Dackels under path ".../Colour".

== Custom Port Configuration ==

Since we can change the port number on that we want to receive messages (in case you want to split up channels on one machine or distribute messages to different receivers), we can configure the port we want to receive messages on.
In our case we use this feature to tell "the Captury" software where we want to receive any kind of messages.

In Max we can make this work by calling the [udpsend] object with following message: "/configure/port $1" ($1 is the Max syntax style for variables).

[[File:img02.png|400px]]

== Subscribe to any Skeleton ==

After we have been setting up the port we want to receive on, we can tell "the Captury" what we want to receive. We are doing this by calling the following message to [udpsend]: "/subscribe/John-Doe/blender/Root/vector 50. 0. 100.".

Since subscriptions will expire after a while, we call this message every 10 seconds. Therefore we use the Max own metronome object called [metro] which will repeat to put out bangs and so trigger the message. The toggle [X] will turn ON the metro.

[[File:img03.png|400px]]

== Grabbing the Bone Vector Coordinates ==

The [udpreceive] object work the other way around. It can receive messages coming from a specific IP and port.
After [udpreceive] we can route the out coming array of information by using the OSC-Syntax again.
With the [route] object we can exactly determine what branch of the string we want to access, in this case we write "/route/John-Doe/blender/Root/vector" to get exactly what we asked for. Afterwards we unpack the containing floats, which represent the x, y and z value of our subscripted bone.

[[File:img05.png|400px]]

== Using the Data Stream from The Captury ==

In the Max domain - instead of patching cords - we can send and receive data as well. To do this we simply write [send] or [receive] and a unique name, which serves as a kind of address: in our case it is [s x-coord] (s as the short form for send is also possible).

Now we can receive the values that have been sent and use them for very own purposes. In my example I display the data first - to have a kind of overview - to see which direction the information is heading to or where it is coming from.

[[File:img06.png|400px]]

Happy patching!

For questions please contact me: benjamin[.] vossler[at] uni-weimar[.] de

GMU:Tutorials/Networking/Controlling MAX-MSP with TheCaptury

2016-10-22T18:44:32Z

Ben: /* Overview */

= Controlling Max-Msp with The Captury =

== Overview ==

The following tutorial covers the process of connecting Max/Msp (short: Max) with "the Captury" tracking software and explains how use the out coming information.

[[File:overview.png|400px]]

== UDP ==

UDP (User Datagram Protocol) is an internet protocol which provides communication which no handshaking. It also let you define which port on the destination IP you want to address. In our case it is used to transmit messages in OSC format.

In Max/Msp you set up an udpsend object. It need two parameters: IP address and port number (e.g.: "141.54.0.1." or "kosmos.uni-weimar.de" and "13000").

[[File:img01.png|400px]]

== OSC-Syntax ==

OSC-messages are build up like an path in your PC (e.g.: "/Animal/Dog/Dackel/Colour/ brown" or "/Animal/Dog/Dackel/Amount/ 45").
Under this path syntax you can send any datatypes (symbol, integer, float as given in the example). This message order is important. Because you can only find what has been sent under the exact path.
You would not search the amount of Dackels under path ".../Colour".

== Custom Port Configuration ==

Since we can change the port number on that we want to receive messages (in case you want to split up channels on one machine or distribute messages to different receivers), we can configure the port we want to receive messages on.
In our case we use this feature to tell "the Captury" software where we want to receive any kind of messages.

In Max we can make this work by calling the [udpsend] object with following message: "/configure/port $1" ($1 is the Max syntax style for variables).

[[File:img02.png|400px]]

== Subscribe to any Skeleton ==

After we have been setting up the port we want to receive on, we can tell "the Captury" what we want to receive. We are doing this by calling the following message to [udpsend]: "/subscribe/John-Doe/blender/Root/vector 50. 0. 100.".

Since subscriptions will expire after a while, we call this message every 10 seconds. Therefore we use the Max own metronome object called [metro] which will repeat to put out bangs and so trigger the message. The toggle [X] will turn ON the metro.

[[File:img03.png|400px]]

== Grabbing the Bone Vector Coordinates ==

The [udpreceive] object work the other way around. It can receive messages coming from a specific IP and port.
After [udpreceive] we can route the out coming array of information by using the OSC-Syntax again.
With the [route] object we can exactly determine what branch of the string we want to access, in this case we write "/route/John-Doe/blender/Root/vector" to get exactly what we asked for. Afterwards we unpack the containing floats, which represent the x, y and z value of our subscripted bone.

[[File:img05.png|400px]]

== Using the Data Stream from The Captury ==

In the Max domain - instead of patching cords - we can send and receive data as well. To do this we simply write [send] or [receive] and a unique name, which serves as a kind of address: in our case it is [s x-coord] (s as the short form for send is also possible).

Now we can receive the values that have been sent and use them for very own purposes. In my example I display the data first - to have a kind of overview - to see which direction the information is heading to or where it is coming from.

[[File:img06.png|400px]]

Happy patching!

For questions please contact me: benjamin[.] vossler[at] uni-weimar[.] de

GMU:Tutorials/Networking/Controlling MAX-MSP with TheCaptury

2016-10-22T18:44:12Z

Ben: /* Overview */

= Controlling Max-Msp with The Captury =

== Overview ==

The following tutorial covers the process of connecting Max/Msp (short: Max) with "the Captury" tracking software and use the outcoming information.

[[File:overview.png|400px]]

== UDP ==

UDP (User Datagram Protocol) is an internet protocol which provides communication which no handshaking. It also let you define which port on the destination IP you want to address. In our case it is used to transmit messages in OSC format.

In Max/Msp you set up an udpsend object. It need two parameters: IP address and port number (e.g.: "141.54.0.1." or "kosmos.uni-weimar.de" and "13000").

[[File:img01.png|400px]]

== OSC-Syntax ==

OSC-messages are build up like an path in your PC (e.g.: "/Animal/Dog/Dackel/Colour/ brown" or "/Animal/Dog/Dackel/Amount/ 45").
Under this path syntax you can send any datatypes (symbol, integer, float as given in the example). This message order is important. Because you can only find what has been sent under the exact path.
You would not search the amount of Dackels under path ".../Colour".

== Custom Port Configuration ==

Since we can change the port number on that we want to receive messages (in case you want to split up channels on one machine or distribute messages to different receivers), we can configure the port we want to receive messages on.
In our case we use this feature to tell "the Captury" software where we want to receive any kind of messages.

In Max we can make this work by calling the [udpsend] object with following message: "/configure/port $1" ($1 is the Max syntax style for variables).

[[File:img02.png|400px]]

== Subscribe to any Skeleton ==

After we have been setting up the port we want to receive on, we can tell "the Captury" what we want to receive. We are doing this by calling the following message to [udpsend]: "/subscribe/John-Doe/blender/Root/vector 50. 0. 100.".

Since subscriptions will expire after a while, we call this message every 10 seconds. Therefore we use the Max own metronome object called [metro] which will repeat to put out bangs and so trigger the message. The toggle [X] will turn ON the metro.

[[File:img03.png|400px]]

== Grabbing the Bone Vector Coordinates ==

The [udpreceive] object work the other way around. It can receive messages coming from a specific IP and port.
After [udpreceive] we can route the out coming array of information by using the OSC-Syntax again.
With the [route] object we can exactly determine what branch of the string we want to access, in this case we write "/route/John-Doe/blender/Root/vector" to get exactly what we asked for. Afterwards we unpack the containing floats, which represent the x, y and z value of our subscripted bone.

[[File:img05.png|400px]]

== Using the Data Stream from The Captury ==

In the Max domain - instead of patching cords - we can send and receive data as well. To do this we simply write [send] or [receive] and a unique name, which serves as a kind of address: in our case it is [s x-coord] (s as the short form for send is also possible).

Now we can receive the values that have been sent and use them for very own purposes. In my example I display the data first - to have a kind of overview - to see which direction the information is heading to or where it is coming from.

[[File:img06.png|400px]]

Happy patching!

For questions please contact me: benjamin[.] vossler[at] uni-weimar[.] de

GMU:Tutorials/Networking/Controlling MAX-MSP with TheCaptury

2016-10-22T18:36:39Z

Ben: /* Using the Data Stream from The Captury */

= Controlling Max-Msp with The Captury =

== Overview ==

[[File:overview.png|400px]]

== UDP ==

UDP (User Datagram Protocol) is an internet protocol which provides communication which no handshaking. It also let you define which port on the destination IP you want to address. In our case it is used to transmit messages in OSC format.

In Max/Msp you set up an udpsend object. It need two parameters: IP address and port number (e.g.: "141.54.0.1." or "kosmos.uni-weimar.de" and "13000").

[[File:img01.png|400px]]

== OSC-Syntax ==

OSC-messages are build up like an path in your PC (e.g.: "/Animal/Dog/Dackel/Colour/ brown" or "/Animal/Dog/Dackel/Amount/ 45").
Under this path syntax you can send any datatypes (symbol, integer, float as given in the example). This message order is important. Because you can only find what has been sent under the exact path.
You would not search the amount of Dackels under path ".../Colour".

== Custom Port Configuration ==

Since we can change the port number on that we want to receive messages (in case you want to split up channels on one machine or distribute messages to different receivers), we can configure the port we want to receive messages on.
In our case we use this feature to tell "the Captury" software where we want to receive any kind of messages.

In Max we can make this work by calling the [udpsend] object with following message: "/configure/port $1" ($1 is the Max syntax style for variables).

[[File:img02.png|400px]]

== Subscribe to any Skeleton ==

After we have been setting up the port we want to receive on, we can tell "the Captury" what we want to receive. We are doing this by calling the following message to [udpsend]: "/subscribe/John-Doe/blender/Root/vector 50. 0. 100.".

Since subscriptions will expire after a while, we call this message every 10 seconds. Therefore we use the Max own metronome object called [metro] which will repeat to put out bangs and so trigger the message. The toggle [X] will turn ON the metro.

[[File:img03.png|400px]]

== Grabbing the Bone Vector Coordinates ==

The [udpreceive] object work the other way around. It can receive messages coming from a specific IP and port.
After [udpreceive] we can route the out coming array of information by using the OSC-Syntax again.
With the [route] object we can exactly determine what branch of the string we want to access, in this case we write "/route/John-Doe/blender/Root/vector" to get exactly what we asked for. Afterwards we unpack the containing floats, which represent the x, y and z value of our subscripted bone.

[[File:img05.png|400px]]

== Using the Data Stream from The Captury ==

In the Max domain - instead of patching cords - we can send and receive data as well. To do this we simply write [send] or [receive] and a unique name, which serves as a kind of address: in our case it is [s x-coord] (s as the short form for send is also possible).

Now we can receive the values that have been sent and use them for very own purposes. In my example I display the data first - to have a kind of overview - to see which direction the information is heading to or where it is coming from.

[[File:img06.png|400px]]

Happy patching!

For questions please contact me: benjamin[.] vossler[at] uni-weimar[.] de

File:Img06.png

2016-10-22T18:32:30Z

Ben: File uploaded with MsUpload

File uploaded with MsUpload

GMU:Tutorials/Networking/Controlling MAX-MSP with TheCaptury

2016-10-22T18:28:25Z

Ben: /* Controlling Max-Msp with The Captury */

GMU:Tutorials/Networking/Controlling MAX-MSP with TheCaptury

2016-10-22T18:27:59Z

Ben: /* Grabbing the Bone Vector Coordinates */

= Controlling Max-Msp with The Captury =

== Overview ==

[[File:overview.png|400px]]

== UDP ==

UDP (User Datagram Protocol) is an internet protocol which provides communication which no handshaking. It also let you define which port on the destination IP you want to address. In our case it is used to transmit messages in OSC format.

In Max/Msp you set up an udpsend object. It need two parameters: IP address and port number (e.g.: "141.54.0.1." or "kosmos.uni-weimar.de" and "13000").

[[File:img01.png|400px]]

== OSC-Syntax ==

OSC-messages are build up like an path in your PC (e.g.: "/Animal/Dog/Dackel/Colour/ brown" or "/Animal/Dog/Dackel/Amount/ 45").
Under this path syntax you can send any datatypes (symbol, integer, float as given in the example). This message order is important. Because you can only find what has been sent under the exact path.
You would not search the amount of Dackels under path ".../Colour".

== Custom Port Configuration ==

Since we can change the port number on that we want to receive messages (in case you want to split up channels on one machine or distribute messages to different receivers), we can configure the port we want to receive messages on.
In our case we use this feature to tell "the Captury" software where we want to receive any kind of messages.

In Max we can make this work by calling the [udpsend] object with following message: "/configure/port $1" ($1 is the Max syntax style for variables).

[[File:img02.png|400px]]

== Subscribe to any Skeleton ==

After we have been setting up the port we want to receive on, we can tell "the Captury" what we want to receive. We are doing this by calling the following message to [udpsend]: "/subscribe/John-Doe/blender/Root/vector 50. 0. 100.".

Since subscriptions will expire after a while, we call this message every 10 seconds. Therefore we use the Max own metronome object called [metro] which will repeat to put out bangs and so trigger the message. The toggle [X] will turn ON the metro.

[[File:img03.png|400px]]

== Grabbing the Bone Vector Coordinates ==

The [udpreceive] object work the other way around. It can receive messages coming from a specific IP and port.
After [udpreceive] we can route the out coming array of information by using the OSC-Syntax again.
With the [route] object we can exactly determine what branch of the string we want to access, in this case we write "/route/John-Doe/blender/Root/vector" to get exactly what we asked for. Afterwards we unpack the containing floats, which represent the x, y and z value of our subscripted bone.

[[img05.png|400px]]

== Using the Data Stream from The Captury ==

GMU:Tutorials/Networking/Controlling MAX-MSP with TheCaptury

2016-10-22T18:27:30Z

Ben: /* Grabbing the Bone Vector Coordinates */

File:Img05.png

2016-10-22T18:27:28Z

Ben: File uploaded with MsUpload

File uploaded with MsUpload

GMU:Tutorials/Networking/Controlling MAX-MSP with TheCaptury

2016-10-22T18:18:08Z

Ben: /* Subscribe to any Skeleton */

File:Img03.png

2016-10-22T18:18:06Z

Ben: File uploaded with MsUpload

File uploaded with MsUpload

GMU:Tutorials/Networking/Controlling MAX-MSP with TheCaptury

2016-10-22T18:17:18Z

Ben: /* Controlling Max-Msp with The Captury */

File:Overview.png

2016-10-22T18:17:15Z

Ben: File uploaded with MsUpload

File uploaded with MsUpload

GMU:Tutorials/Networking/Controlling MAX-MSP with TheCaptury

2016-10-22T18:16:24Z

Ben: /* Custom Port Configuration */

= Controlling Max-Msp with The Captury =

== UDP ==

UDP (User Datagram Protocol) is an internet protocol which provides communication which no handshaking. It also let you define which port on the destination IP you want to address. In our case it is used to transmit messages in OSC format.

In Max/Msp you set up an udpsend object. It need two parameters: IP address and port number (e.g.: "141.54.0.1." or "kosmos.uni-weimar.de" and "13000").

[[File:img01.png|400px]]

== OSC-Syntax ==

OSC-messages are build up like an path in your PC (e.g.: "/Animal/Dog/Dackel/Colour/ brown" or "/Animal/Dog/Dackel/Amount/ 45").
Under this path syntax you can send any datatypes (symbol, integer, float as given in the example). This message order is important. Because you can only find what has been sent under the exact path.
You would not search the amount of Dackels under path ".../Colour".

== Custom Port Configuration ==

Since we can change the port number on that we want to receive messages (in case you want to split up channels on one machine or distribute messages to different receivers), we can configure the port we want to receive messages on.
In our case we use this feature to tell "the Captury" software where we want to receive any kind of messages.

In Max we can make this work by calling the [udpsend] object with following message: "/configure/port $1" ($1 is the Max syntax style for variables).

[[File:img02.png|400px]]

== Subscribe to any Skeleton ==

After we have been setting up the port we want to receive on, we can tell "the Captury" what we want to receive. We are doing this by calling the following message to [udpsend]: "/subscribe/John-Doe/blender/Root/vector 50. 0. 100.".

Since subscriptions will expire after a while, we call this message every 10 seconds. Therefore we use the Max own metronome object called [metro] which will repeat to put out bangs and so trigger the message. The toggle [X] will turn ON the metro.

== Grabbing the Bone Vector Coordinates ==

== Using the Data Stream from The Captury ==

File:Img02.png

2016-10-22T18:16:22Z

Ben: File uploaded with MsUpload

File uploaded with MsUpload

GMU:Tutorials/Networking/Controlling MAX-MSP with TheCaptury

2016-10-22T18:14:35Z

Ben: /* Subscribe to any Skeleton */

= Controlling Max-Msp with The Captury =

== UDP ==

UDP (User Datagram Protocol) is an internet protocol which provides communication which no handshaking. It also let you define which port on the destination IP you want to address. In our case it is used to transmit messages in OSC format.

In Max/Msp you set up an udpsend object. It need two parameters: IP address and port number (e.g.: "141.54.0.1." or "kosmos.uni-weimar.de" and "13000").

[[File:img01.png|400px]]

== OSC-Syntax ==

OSC-messages are build up like an path in your PC (e.g.: "/Animal/Dog/Dackel/Colour/ brown" or "/Animal/Dog/Dackel/Amount/ 45").
Under this path syntax you can send any datatypes (symbol, integer, float as given in the example). This message order is important. Because you can only find what has been sent under the exact path.
You would not search the amount of Dackels under path ".../Colour".

== Custom Port Configuration ==

Since we can change the port number on that we want to receive messages (in case you want to split up channels on one machine or distribute messages to different receivers), we can configure the port we want to receive messages on.
In our case we use this feature to tell "the Captury" software where we want to receive any kind of messages.

In Max we can make this work by calling the [udpsend] object with following message: "/configure/port $1" ($1 is the Max syntax style for variables).

== Subscribe to any Skeleton ==

After we have been setting up the port we want to receive on, we can tell "the Captury" what we want to receive. We are doing this by calling the following message to [udpsend]: "/subscribe/John-Doe/blender/Root/vector 50. 0. 100.".

Since subscriptions will expire after a while, we call this message every 10 seconds. Therefore we use the Max own metronome object called [metro] which will repeat to put out bangs and so trigger the message. The toggle [X] will turn ON the metro.

== Grabbing the Bone Vector Coordinates ==

== Using the Data Stream from The Captury ==

File:Bildschirmfoto 2016-08-29 um 18.54.07.png

2016-10-22T18:14:32Z

Ben: File uploaded with MsUpload

File uploaded with MsUpload

GMU:Tutorials/Networking/Controlling MAX-MSP with TheCaptury

2016-10-22T18:08:02Z

Ben: /* Custom Port Configuration */

= Controlling Max-Msp with The Captury =

== UDP ==

UDP (User Datagram Protocol) is an internet protocol which provides communication which no handshaking. It also let you define which port on the destination IP you want to address. In our case it is used to transmit messages in OSC format.

In Max/Msp you set up an udpsend object. It need two parameters: IP address and port number (e.g.: "141.54.0.1." or "kosmos.uni-weimar.de" and "13000").

[[File:img01.png|400px]]

== OSC-Syntax ==

OSC-messages are build up like an path in your PC (e.g.: "/Animal/Dog/Dackel/Colour/ brown" or "/Animal/Dog/Dackel/Amount/ 45").
Under this path syntax you can send any datatypes (symbol, integer, float as given in the example). This message order is important. Because you can only find what has been sent under the exact path.
You would not search the amount of Dackels under path ".../Colour".

== Custom Port Configuration ==

Since we can change the port number on that we want to receive messages (in case you want to split up channels on one machine or distribute messages to different receivers), we can configure the port we want to receive messages on.
In our case we use this feature to tell "the Captury" software where we want to receive any kind of messages.

In Max we can make this work by calling the [udpsend] object with following message: "/configure/port $1" ($1 is the Max syntax style for variables).

== Subscribe to any Skeleton ==

== Grabbing the Bone Vector Coordinates ==

== Using the Data Stream from The Captury ==

GMU:Tutorials/Networking/Controlling MAX-MSP with TheCaptury

2016-08-29T19:19:28Z

Ben: /* UDP */

GMU:Tutorials/Networking/Controlling MAX-MSP with TheCaptury

2016-08-29T19:19:09Z

Ben: /* UDP */

File:Img01.png

2016-08-29T19:18:37Z

Ben: File uploaded with MsUpload

File uploaded with MsUpload

GMU:Tutorials/Networking/Controlling MAX-MSP with TheCaptury

2016-08-29T19:16:42Z

Ben: /* UDP */

GMU:Tutorials/Networking/Controlling MAX-MSP with TheCaptury

2016-08-29T19:14:55Z

Ben: /* OSC-Syntax */

GMU:Tutorials/Networking/Controlling MAX-MSP with TheCaptury

2016-08-29T19:04:09Z

Ben: /* UDP */

User:Nele schacht

2016-08-06T21:39:59Z

Ben: /* Nele Schacht - Arbeiten */

==Nele Schacht - Arbeiten==

'''Wintersemester 2011/2012'''

<div style="float:right;">
<gallery location="left", perrow="4">
File:neleschacht_schuhe1.jpg|Musterkiste - Schuhsammlung
File:neleschacht_kit1.jpg|Bauhaus - do it yourself!
File:neleschacht_abfall1.jpg|Micromuseum - Abfall
</gallery>
</div>

[[MODEN:MUSTERKOFFER_2011-2012|''Musterkoffer (Dozent: Felix Sattler)
'']]
<br>
<br>
:*[[MODEN:MUSTERKOFFER_2011-2012/arbeiten/musterkisten#Nele_Schacht|Musterkiste: Die gute Form - eine Schuhsammlung]]

:*[[MODEN:MUSTERKOFFER_2011-2012/arbeiten/kofferkit#Nele_Schacht|Koffer-Kit: MAKE YOUR BAUHAUS BETTER THAN MINE - ein Koffer-Kit]]

:*[[MODEN:MUSTERKOFFER_2011-2012/arbeiten/micromuseum#Nele_Schacht|Micromuseum: Ab|fall - eine Studie über die Ästhetik des Überflüssigen]]

<br>
<br>

User:Nele schacht

2016-08-06T21:39:32Z

Ben: /* Nele Schacht - Arbeiten */

IFD:GenerativeBauhaus WS2012/Nele

2016-08-06T21:38:28Z

Ben: /* weitere Arbeiten */

IFD:GenerativeBauhaus WS2012/Nele

2016-08-06T21:38:17Z

Ben: /* Schrift */

==[[User:Nele_schacht|weitere Arbeiten]]==

[[Category:Bauhaus-Vorkurs]]

IFD:GenerativeBauhaus WS2012/Nele

2016-08-06T21:38:09Z

Ben: /* Farbe II */

IFD:GenerativeBauhaus WS2012/Nele

2016-08-06T21:38:01Z

Ben: /* Kontrast, Farbe I */

==Farbe II==

''Farb-Patterns (interaktiv auf [http://www.openprocessing.org/sketch/82708 openprocessing.org])''
<gallery perrow=6>
File:Blau1NeleS.png
File:Blau2NeleS.png
File:Rot1NeleS.png
File:Rot2NeleS.png
File:Gelb1NeleS.png
File:Gelb2NeleS.png
</gallery>

<div style="clear: both;"></div>

==Schrift==

[[File:Schnurrbart.jpg|thumb|left|250px|]]
[[File:Monster.jpg|thumb|left|220px|]]
<div style="clear: both;"></div>

==[[User:Nele_schacht|weitere Arbeiten]]==

[[Category:Bauhaus-Vorkurs]]

IFD:GenerativeBauhaus WS2012/Nele

2016-08-06T21:37:51Z

Ben: /* Raum, Raster, Layout */

IFD:GenerativeBauhaus WS2012/Nele

2016-08-06T21:37:41Z

Ben: /* Format */

IFD:GenerativeBauhaus WS2012/Nele

2016-08-06T21:37:34Z

Ben: /* Form */

IFD:GenerativeBauhaus WS2012/Nele

2016-08-06T21:37:20Z

Ben: /* Linie */

IFD:GenerativeBauhaus WS2012/Nele

2016-08-06T21:37:10Z

Ben: /* Punkt */

ME:Animalation/Nele

2016-08-06T21:33:08Z

Ben: /* weitere Arbeiten */

==[[User:Nele_schacht|Nele Schacht]]==

ME:Animalation/Nele

2016-08-06T21:33:01Z

Ben: /* Abschlussfilm */

==[[User:Nele_schacht|Nele Schacht]]==

==[[User:Nele_schacht|weitere Arbeiten]]==

ME:Animalation/Nele

2016-08-06T21:32:56Z

Ben: /* Animatic */

==[[User:Nele_schacht|Nele Schacht]]==

==Abschlussfilm==
<br>
<videoflash type=vimeo>60564957|380|300</videoflash>
<div style="clear:both"></div>

==[[User:Nele_schacht|weitere Arbeiten]]==

ME:Animalation/Nele

2016-08-06T21:32:50Z

Ben: /* Storyboards */

ME:Animalation/Nele

2016-08-06T21:32:44Z

Ben: /* Characterdesign */

ME:Animalation/Nele

2016-08-06T21:32:37Z

Ben: /* Basics Übungen */

==[[User:Nele_schacht|Nele Schacht]]==

==Characterdesign==

<div style="float:left;">
<gallery location="left">
File:Kroko1.jpg
File:Kroko2.jpg
File:Kroko3.jpg
File:Kroko4.jpg
File:Kroko5.jpg
File:Kroko6.jpg
File:Kroko7.jpg
File:Pferd1.jpg
File:Pferd2.jpg
File:Pferd3.jpg
File:Pferd4.jpg
File:Pferd6.jpg
File:zzz_fisch.jpg
</gallery>
</div>

<div style="clear:both"></div>

==Storyboards==

[http://www.uni-weimar.de/medien/wiki/images/NeleSchachtStoryboard1.pdf Fisch]
<br>
[http://www.uni-weimar.de/medien/wiki/images/NeleSchachtStoryboard2.pdf Krokodil]
<div style="clear:both"></div>

==Animatic==

[[File:NeleSchachtAnimaticKroko1.png|thumb|left|200px|Animatic Version 1]]
[[File:NeleSchachtAnimaticKroko2.png|thumb|left|265px|Animatic Version 2(1)]]
[[File:Bildschirmfoto_2013-06-27_um_17.14.54.png|thumb|left|265px|Animatic Version 2(2)]]
<div style="clear:both"></div>

==Abschlussfilm==
<br>
<videoflash type=vimeo>60564957|380|300</videoflash>
<div style="clear:both"></div>

==[[User:Nele_schacht|weitere Arbeiten]]==

ME:Animalation/Nele

2016-08-06T21:32:27Z

Ben: /* Animationsprinzip */

==[[User:Nele_schacht|Nele Schacht]]==

==Basics Übungen==

''Übung 1 (Walking Cycle)''
<videoflash type=vimeo> 52383288 |380|300</videoflash>

''Übung 2 (Sprung)''
<videoflash type=vimeo> 52848649 |380|300</videoflash>

''Übung 3 (Stein)''
<videoflash type=vimeo>52847060|380|300</videoflash>

==Characterdesign==

<div style="float:left;">
<gallery location="left">
File:Kroko1.jpg
File:Kroko2.jpg
File:Kroko3.jpg
File:Kroko4.jpg
File:Kroko5.jpg
File:Kroko6.jpg
File:Kroko7.jpg
File:Pferd1.jpg
File:Pferd2.jpg
File:Pferd3.jpg
File:Pferd4.jpg
File:Pferd6.jpg
File:zzz_fisch.jpg
</gallery>
</div>

<div style="clear:both"></div>

==Storyboards==

[http://www.uni-weimar.de/medien/wiki/images/NeleSchachtStoryboard1.pdf Fisch]
<br>
[http://www.uni-weimar.de/medien/wiki/images/NeleSchachtStoryboard2.pdf Krokodil]
<div style="clear:both"></div>

==Animatic==

[[File:NeleSchachtAnimaticKroko1.png|thumb|left|200px|Animatic Version 1]]
[[File:NeleSchachtAnimaticKroko2.png|thumb|left|265px|Animatic Version 2(1)]]
[[File:Bildschirmfoto_2013-06-27_um_17.14.54.png|thumb|left|265px|Animatic Version 2(2)]]
<div style="clear:both"></div>

==Abschlussfilm==
<br>
<videoflash type=vimeo>60564957|380|300</videoflash>
<div style="clear:both"></div>

==[[User:Nele_schacht|weitere Arbeiten]]==

GMU:Tutorials/Networking/Controlling MAX-MSP with TheCaptury

2016-07-07T17:31:10Z

Ben: Created page with "= Controlling Max-Msp with The Captury = == UDP == == OSC-Syntax == == Custom Port Configuration == == Subscribe to any Skeleton == == Grabbing the Bone Vector Coordinates =..."

= Controlling Max-Msp with The Captury =

== UDP ==

== OSC-Syntax ==

== Custom Port Configuration ==

== Subscribe to any Skeleton ==

== Grabbing the Bone Vector Coordinates ==

== Using the Data Stream from The Captury ==

GMU:Performance Platform

2016-06-22T10:57:26Z

Ben: /* Project Groups */

The '''''Interactive Performance Platform''''' is a lab for artistic research operated by the [[GMU:Start|GMU]].
== Location ==

'''Interactive Performance Platform'''
Digital Bauhaus Lab, Room 001 (Ground Floor)
Bauhausstr. 9a
99423 Weimar

== Hardware ==

[[Image:performance-platform-videowall.png|thumb|left|200px|The videowall in action]]
[[Image:the-captury-screenshot.png|thumb|left|300px|Screenshot from the tracking software]]

<br style="clear:both;">

* markerless multi-person tracking
* highspeed camera for longterm-recording
* 12.2 channel audio system
* 4 x 4 tiled video wall
* 4 mac workstations

== Setup ==

[[Image:performance-platform-setup.png|500px]]

== Schedule ==

The Performance Platform is used for artistic research.<br>
However there are occasional workshops and modules inside the lab to introduce the participants to the technology and foster the emergence of cross-disciplinary projects.

The place may be crowded during modules and workshops.
Please try not to disturb during those times.
Thank you :)

=== Regular Schedule ===

Note:
Starting June 13th the Lab will be used for Project-Work and Workshops.
If you want access to the lab please get in contact with [[Martin Schneider]]

{|align="left" {{Prettytable}}
|
!Monday
!Tuesday
!Wednesday
!Thursday
!Friday
!Saturday
!Sunday
|-
!09:15 - 10:45
|Lab-Time
|Lab-Time
|Lab-Time
|Lab-Time
|Lab-Time
|Lab-Time
|Lab-Time
|-
!11:00 - 12:30
|Lab-Time
|Lab-Time
|Lab-Time
|Lab-Time
|Lab-Time
|Lab-Time
|Lab-Time
|-
!13:30 - 15:00
|Lab-Time
|Lab-Time
|Lab-Time
|Lab-Time
|Lab-Time
|Lab-Time
|Lab-Time
|-
!15:15 - 16:45
|Lab-Time
|Lab-Time
|Lab-Time
|Lab-Time
|Lab-Time
|Lab-Time
|Lab-Time
|-
!17:00 - 18:30
|Lab-Time
|Lab-Time
|[[GMU:Digital_Puppetry_Lab|Tutorium]] / Lab-Time
|Lab-Time
|Lab-Time
|Lab-Time
|Lab-Time
|-
!19:00 - 20:30
|Lab-Time
|[[GMU:Digital_Puppetry_Lab|Tutorium]]
|[[GMU:Digital_Puppetry_Lab|Tutorium]] / Lab-Time
|Lab-Time
|Lab-Time
|Lab-Time
|Lab-Time
|}

=== Workshops ===

{|align="left" {{Prettytable}}
! workshop title
! first day
! last day
|-
| [[GMU:Digital_Puppetry_Lab|Digital Puppetry Lab]] - Martin Schneider (GMU/EXPTV)
| Friday, 15. April
| Sunday 17. April
|-
| [[EXPTV:Start|UNITY-Workshop]] - Stephan Iserman (EXPTV)
| Thursday, 12. May
| Friday 13. May
|-
| [[GMU:Minecraft Ecologies|Minecraft Ecologies I]] Martin Schneider (GMU)
| Friday, 13. May
| Sunday 15. May
|-
| [[GMU:Human_and_Nonhuman_Performances_II_SS16|Bio-Semiotics]] - Dario Martinelli (GMU)
| Friday, 17. May
| Sunday 19. May
|-
| [[GMU:Minecraft Ecologies|Minecraft Ecologies II]] - Martin Schneider (GMU)
| Friday, 20. May
| Sunday 22. May
|-
| [[GMU:Minecraft Ecologies|Minecraft Ecologies III]] - Daniel Braun, Thomas Hawranke (GMU)
| Friday, 24. May
| Sunday 26. May
|}

<br style="clear:both;">

=== Group Work ===

The following 12 dates are available for group work. Please mention at least 3 days, that would would work for you in your group profile! We will activate you for the day and send you a short email when once you are active.

By working in the lab you agree that you have read and understood, and that you will honour the [[GMU:Nutzungsordnung_IPP|Nutzungsordnung]]. You are fully responsible for any damage that occurs during your group work period. (Even if caused by somebody else).

<br>

* '''SLOT 1''' – 16. June (Thu) – PASSED
* '''SLOT 2''' – 17. June (Fri) – Group 7
* '''SLOT 3''' – 18. June (Sat) – Individuals: Jessica Hüttig, Tim Vischer
* '''SLOT 4''' – 20. June (Mon) – Individuals: Jessica Hüttig, Tim Vischer

* '''SLOT 5''' – 23. June (Thu) – Group 2
* '''SLOT 6''' – 27. June (Mon) – Group 8
* '''SLOT 7''' – 28. June (Tue) – Group 4
* '''SLOT 8''' – 29. June (Wed) – Group 5

* '''SLOT 9''' – 30. June (Thu) – Individuals: Di Yang
* '''SLOT 10''' – 01. July (Fri) – Group 2
* '''SLOT 11''' – 02. July (Sat) – Group 6
* '''SLOT 12''' – 03. July (Sun) – Group 7

== Project Groups ==

NOTE:
The person printed in bold face is responsible for the lab, in case anything goes wrong.

* Group 1 – '''[[GMU:Minecraft_Ecologies|Minecraft Ecologies]] – GMU'''
** Preferred Slots: ???
** '''Meike Halle'''
** Marcel Gohsen
** Asha Murali
** Andre Faupel
* Group 2 – '''[[Physical Sound Environment]] – GMU'''
** Preferred Slots: 10, 11, 12
** '''Kan Feng''' – Tutorial: [[GMU:Tutorials/Performance_Platform/Capture_with_Processing|Defining Trigger Spaces with Processing]]
** Shuyan Chen – Tutorial:[[Custom Setup to track People using a Camera on the Ceiling]]
** Shih-Li Chao – Tutorial: [[GMU:Tutorials/Performance_Platform/Sound_System_Stereo|Play Stereo on the Sound System]]
* Group 3 – '''[[/Multiple Gravity|Multiple Gravity]] – ExpTV'''
** Preferred Slots: ''none''
** '''Benjamin Vossler''' – [[GMU:Tutorials/Networking/Controlling_MAX-MSP_with_TheCaptury|Controlling Max MSP with the Captury]]
** Gianluca Pandolfo – [[GMU:Tutorials/Networking/Controlling_Unity_with_TheCaptury|Controling Unity with The Captury]]
* Group 4 – '''[[/Madre Monte|Madre Monte]] – ExpTV'''
** Preferred Slots: 6, 7, 8
** '''Emilio Aguas''' – Tutorial: [[GMU:Tutorials/Performance Platform/Tracking Platform Export|Using the Multi-Speaker-System]]
** Fiona Mortimer – Tutorial Title 2
** Eduardo Oliviera – Tutorial Title 3
* Group 5 – '''[[/Bounce & Rebound|Bounce & Rebound]] – ExpTV'''
** Preferred Slots: 6, 7, 8
** '''Jonas Jülch''' – Tutorial: [[GMU:Tutorials/Performance_Platform/Tracking_Platform_Rigging|Using Tracking Data in Blender]]
** Leif Weitzel – Tutorial Title 2
* Group 6 – '''[[/Escape or Kill|Escape or Kill]] – ExpTV'''
** Slot: 11
** '''Florian Froger''' – Tutorial: [[GMU:Tutorials/Performance Platform/Tracking Platform Export|Exporting Tracking Data]]
* Group 7 – '''[[/Dependance|Dependance]] – ExpTV'''
** Preferred Slots: 2, 3, 10, 11, 12
** '''Alicia Kremser''' – Tutorial Title 1
** Tim Vischer
** Adam Streicher - [[GMU:Tutorials/Networking/Controlling_Unity_with_TheCaptury|Controling Unity with The Captury]]
* Group 8 – '''[[/Group dynamics|Group Dyamics]] – ExpTV'''
** Preferred Slots: 6
** '''Kei Kitamura''' – Tutorial Title 1
* Group 9 – '''[[https://www.uni-weimar.de/medien/wiki/GMU:Human_and_Nonhuman_Performances_II_SS16/Group_FLL|/Wool's World|Wool's Word|]] – GMU'''
** Preferred Slots: 6, 7, 8, 9, 10
** '''Yun Liu''' - Tutorial: [[GMU:Tutorials/Visual Interaction/Using Unity for simulation|Control 3D knot by the data of position and velocity in real-time]]
** '''Xiangzhen Fan'''[[GMU:Tutorials/Visual Interaction/Using Unity for simulation|Simulating 3D knot in real-time]]
** '''Qianqian Li'''- Tutorial: [[GMU:Tutorials/Performance_Platform/Using the tracking system|Using the Tracking System to Track the position of arthrosis]]

== Individuals ==
* Jessica Hüttig – Tutorial: [[GMU:Tutorials/Performance Platform/Tracking Platform Calibration|Calibrating the Tracking System]]
**Preferred slots: 3
* Di Yang – Tutorial: [[GMU:Tutorials/Performance Platform/Videowall Calibration|Calibrating the Videowall]]
** preferred slots: 8, 9, 10
* Rachel Smith - [[GMU:Tutorials/Performance_Platform/Recognizing_Gestures_with_Wekinator|Recognising Gestures with Wekinator]]
** Preferred slots: 10, 11, 12
* Christopher Dake-Outhet – Tutorial: [[GMU:Tutorials/Performance Platform/Tracking Platform Calibration|Recording Tacking Data]]
** preferred slots: 6, 8, 12

== Highlights ==
* Student projects from the [[GMU:Spacial_Information_Lab#Participants|Spacial Information Lab]]
* Tracking 3 dancers for the [https://vimeo.com/156704320 3D-Pitoti project]

== Tutorials ==
As part of the [[GMU:Digital_Puppetry_Lab|Introduction to the Lab]] the students will create [[GMU:Tutorials#Performance_Plattform_Tutorials|Online Tutorials]].<br>
The tutorials will explain how to use the technology available at the Performance Platform.

== Mailing-List ==
There is an internal mailing list for everyone that has their working space on the DBL groundfloor.<br>
Please contact [[Martin Schneider]] if you think you should be on that list.

== Links ==
* [https://www.uni-weimar.de/en/media/institutes/digital-bauhaus-lab Digital Bauhaus Lab Website]
* [[GMU:Nutzungsordnung_IPP|Nutzungsordnung]]

GMU:Digital Puppetry Lab

2016-06-21T18:10:26Z

Ben: /* Examples */

[[Image:Digital-puppetry.png|thumb|left|200px|''Chinese Shadows'' by Ferdinand du Puigaudeau]]

'''Digital Puppetry Lab''' — Introduction to the ''Interactive Performance Platform''

[[:Category:Werkmodul|Werkmodul]]/[[:Category:Fachmodul|Fachmodul]]<br>
''Lecturer:'' [[Martin Schneider]]<br>
''Credits:'' 6 [[ECTS]], 4 [[SWS]]<br>
''Date:'' Tuesday 19:00 - 20:30 (weekly) + Wednesday 17:00 - 20:30 (biweekly) <br>          '''Blockmodul (15. - 17. April)''' <br>
''Venue:'' [[Performance Platform]], Digital Bauhaus Lab<br>
''First meeting:''' TUESDAY, 12. April, 19:00h'''

<br style="clear:both">

'''This is a hands on course that is required for project modules by GMU and EXPTV.'''

== Tutoriums ==

Note: this plan may be subject to changes.
Please follow the mailing list for updates.

The tutoriums are split into two groups.<br>
'''They take place on Tuesday at 19:00 and every other Wednesday at 17:00.'''
=== April ===
* 19. April, Tue, 19:00 (Su, Max): Learning Blender
* 20. April, Wed, 17:00(Su, Max): Learning Blender
* 26. April, Tue, 19:00(Luca, Ben): Learning Blender

=== May ===
* 03. May, Tue, 19:00 (Luca, Su): Learn how to get a simple Blender model into Unity
* 04. May, Wed, 17:00 (Martin, Luca, Su): Learn how to use OSC to connect Iannix and Unity
* 10. May, Tue, 19:00 (Martin, Luca, Ben): Introduction to MAX MSP + Connecting Iannix to MAX MSP
* 17. May, Tue, 19:00
* 18. May, Wed, 17:00
* 24. May, Tue, 19:00
* 31. May, Tue, 19:00

=== June ===
* 01. June, Wed, 17:00 Q+A (Luca / Ben)
* 07. June, Tue, 19:00 Q+A (Luca / Ben)
* 14. June, Tue, 19:00 Q+A (Luca / Ben)
* 15. June, Wed, 17:00 Q+A (Luca / Ben)
* 21. June, Tue, 19:00 Q+A (Luca / Ben)
* 28. June, Tue, 19:00 Q+A (Luca / Ben)
* 29. June, Wed, 17:00 Q+A (Luca / Ben)

=== July ===
* 05. July, Tue, 19:00 Q+A (Luca / Ben)
* 12. July, Tue, 19:00 Q+A (Luca / Ben)
* 13. July, Wed, 17:00 Q+A (Luca / Ben)

== Weekend Workshop ==

=== Be Prepared ===

Please make sure to install the software on your laptops at home. <br>
We will start using it right away and have no time for installation during the course.

* [https://www.blender.org/download/ Blender]
* [https://unity3d.com/get-unity/download?ref=personal Unity]
* [http://www.iannix.org/en/download-iannix/ Iannix]
* [https://processing.org/download/?processing Processing] (Version 3.0.2)
* [https://puredata.info/downloads/pd-extended/releases/0.43.4 Pure Data Extended] (0.43.4)

=== Schedule ===

{| class="wikitable"
! colspan="3" | FRIDAY
|-
!11:00 - 11:45
|Intro to the Wiki
|Martin
|-
!11:45 - 12:30
| Intro to OSC, Iannix and Processing
| Martin
|-
| colspan="3" style="text-align:center"| ''Lunch Break''
|-
!13:30 - 14:15
| Intro to MAX-MSP + Puredata
| Martin, Benjamin
|-
!14:15 - 15:00
| Intro to Blender + Unity
| Luca, Miga
|-
!15:15 - 16:00
| Intro to Unity I
| Luca
|-
!16:00 - 16:45
| Intro to Unity II
| Luca
|-
! colspan="3" | SATURDAY
|-
! 10:00 - 12:30
| Hands-On Blender
| Su Li, Benjamin
|-
| colspan="3" style="text-align:center"| ''Lunch Break''
|-
! 13:30 - 16:00
| Hands-On Blender
| Su Li, Benjamin
|-
! 16:00 - 18:30
| Hands-On Blender
| Su Li, Benjamin
|-
! colspan="3" | SUNDAY
|-
!10:00 - 12:30
| Hands-On Blender
| Su Li, Max
|-
| colspan="3" style="text-align:center"| ''Lunch Break''
|-
!13:30 - 16:00
| Hands-On Blender
| Su Li, Max
|-
!16:00 - 16:45
| Demo in the DBL
| Martin, Luca
|}

== Beschreibung ==

Das Modul vermittelt die nötigen Grundkenntinisse um interaktive Performances mit Hilfe der Performance-Plattform des Digital Bauhaus Labs zu erstellen.

Nach einem einführende Blockmodul (15. - 17. April) geht es im Rahmen der wöchentlichen Veranstaltung um den praktischen Umgang mit den entsprechenden Software-Werkzeugen und Programmier-Umgebungen.

Am Ende des Moduls sollen die Studierenden in der Lage sein, eigene Setups zu erstellen, die aus menschliche Bewegung, Interaktion, und Tanz immersive visuelle und akkustische Umgebungen erzeugen.

== Description ==

This course will teach you basic skills required to create interactive performances, using the Peformance Platform of the Digital Bauhaus Lab.

By the end of the course you will be able to create your own immersive setup for generating live audio and visuals from human motion, interaction and dance.

== Language ==

The course is in English, because not all participants are speaking German.

== Eligible Participants ==

Undergraduates and graduates enrolled in the faculties of:

* Media Art + Design
* Media Architecture
* Visual Communication
* Product Design

== Participants ==
* [[/Jasmine|Jing Zhao]]
* [[/Jack|Jixiang JIANG]]
* [[/Martin Schneider|Martin Schneider]]
* [[/Fiona Mortimer|Fiona M]]
* [[//Emilio Aguas|''Emilio Aguas'']]
* [[/Jessica Hüttig|Jessica Hüttig]]
* [[/Kan Feng|Kan Feng]]
* [[/Priyanka Srinivasagopalan|Priyanka Srinivasagopalan]]
* [[/Tim Vischer|Tim Vischer]]
* [[/Rachel Smith|Rachel Smith]]
* [[/Taissa Fromme|Taissa Fromme]]
*[[/FANXZ|Xiangzhen Fan]]
* [[/Minsoo Hwang|Minsoo Hwang]]
* [[/Di Yang|Di Yang]]
* [[/elenaliv|Elena Liv Felderer]]
* [[/Kei Kitamura|Kei Kitamura]]
*[[/Qianqian Li|Qianqian Li]]
* [[/Yun Liu|Yun Liu]]
* [[/Logic|Ji Luo]]
* [[/Florian Froger|Florian Froger]]
* [[/Anna Hack|Anna Hack]]
* [[/Shubhra Bhatt | Shubhra Bhatt]]
* [[/Jane doe|Jane doe]]
* [[/Jonas Jülch|Jonas Jülch]]
* [[/Seb|Sebastian Richter]]
* [[/Rama Bielewski|Rama Bielewski]]
* [[/Edu_Oliveira| Eduardo Oliviera]]
* [[/Shih Li Chao|Shih Li C]]
* [[/Shuyan|Shuyan Chen]]
* [[/Junyuan WU|Junyuan WU]]
* [[/Christopher Dake-Outhet|Christopher Dake-Outhet]]
* [[/Leif Weitzel|Leif Weitzel]]
* [[/Alicia Kremser|Alicia Kremser]]
* [[/Amy Jean Barnett|Amy Jean Barnett]]

== OSC Projects ==

[https://github.com/bitcraftlab/digital-puppetry-lab OSC-Example Code]

[[File:OSC_THE_CAPTURY.zip]]

Add your projects here:

* [[/Group Ben & Luca|Ben & Luca]]
* [[/Group A Midsummer Night's Dream|Yun & Qianqian & Xiangzhen & Junyuan & Yuxin]]
* [[/Group Play with rhythms |Di Yang & Jixiang Jiang & Kan Feng & Shuyan Chen]]
* [[/Group Shih Li & Sebastian & Adam & Jessica|Shih Li & Sebastian & Adam & Jessica]]
* [[/Group B0XJUMP |Alicia/Tim/Elena/Chris]]
* [[/Group KittenRemote |Amy/Jonas/Florian]]
*[[/Group Swarm|Emilio Aguas/ Fiona Mortimer/ Eduardo Oliveira ]] – Hornet swarm
* [[/Group Leif/Rachel/Kei |Leif/Rachel/Kei]]

== Tutorials ==
* [https://www.uni-weimar.de/medien/wiki/GMU:Tutorials/Networking/Controlling_Unity_with_IanniX Controlling Unity with Iannix] (Martin Schneider)
Please add your tutorials below.
''All tutorials developed at the GMU can be found [[GMU:Tutorials|here]]''.

== Examples ==

* [https://www.dropbox.com/sh/czkyhsz57fokqdm/AADDMv23wN4Zs0GVXSn69Z-ja?dl=0|OSC Example in Max/Msp]
* [https://www.dropbox.com/sh/9j3qc700t2bdq91/AAAtS1FXUKTBXiALVxm5KlfTa?dl=0 Smooth Out Jittery Data] in Max/Msp (e.g. for TouchOSC Input)
* [https://www.youtube.com/playlist?list=PL12DC9A161D8DC5DC Pure Data Video Tutorial] on Youtube

*[https://www.dropbox.com/sh/lew8lel0q81tm0g/AACmkCgCxScvCELVEL1yOx0Ha?dl=0 | 3D Motion Simulator and Receiver]

*[https://www.zhdk.ch/index.php?id=icst_ambisonicsexternals | Ambisonics External for Max & Pd]

== Application ==

Applications from students that have signed up for the project modules at GMU or EXPTV, will be favoured, because this course is a requirement for those modules.

'''To:''' [[User:ms|Martin Schneider]]<br>
'''Subject:''' Digital Puppetry Lab /// Application<br>
'''Content:'''

* Name, Surname
* program and semester (Studienprogramm und Fachsemester)
* matriculation number (Matrikelnummer)
* Valid email address @uni-weimar.de
* Your project module

== Syllabus ==
* First Meeting 12. April (Tuesday)
* Block-Weekend 15. - 17. April

The syallbus includes:
* Introduction to the Tracking System
* Basics of Networking with OSC
* Basics of 3D-Modelling and Rigging
* Programming Interactive 3D Graphics
* Programming interactive Sound in Space

== Evaluation ==
* 20% Presence and active participation
* 50% Creation of an interactive setup (documented in the form of a tutorial)
* 30% Documentation on the wiki

== Books ==
''to be done''

== Links ==

* [[www.thecaptury.com|The Captury]]
* [[www.blender.org|Blender]] (3D Modelling)
* [[www.unity3d.com|Unity]] (3D Game Engine)
* [[www.iannix.org|Iannix]] (Visual Synthesizer for OSC)
* [[www.sojamo.de/libraries/oscP5/|OSC for Processing]]
* [[trippylighting.com/teensy-arduino-ect/touchosc-and-arduino-oscuino|TouchOSC + OSCuino]]
* [[Pure Data]]
* [[Max MSP]]

[[Category:SS16]]
[[Category:Werkmodul]]
[[Category:Fachmodul]]
[[Category:Martin Schneider]]

[[Category:Tracking]]
[[Category:OSC]]
[[Category:Blender]]
[[Category:Dataflow]]

Physical Sound Environment

2016-06-21T17:28:17Z

Ben: /* Title */

== Name ==
Kan Feng

Shuyan Chen

== Slot ==
10, 11 & 12

== Title ==

Physical Sound Environment

Notes:

- Count the People on the platform
-> count vie Face-Detection (Processing)

-> subscribe to all skeletons (count them, in Max or Pd or Processing)

GMU:Performance Platform/Working Title

2016-06-14T16:24:42Z

Ben: /* Ben und Luca */

= Ben und Luca =

== Idea ==

We are building a survival game. You have to escape from a 'Black Hole', therefore you have to use the gravity from different planets to flee away.

GMU:Performance Platform/Working Title

2016-06-14T16:20:03Z

Ben: Created page with "= Ben und Luca ="

= Ben und Luca =