Medien Wiki - User contributions [en]

GMU:Tutorials/Networking/Controlling MAX MSP with IanniX

2016-07-27T14:33:12Z

LeifWEi: /* Introduction */

== ''Introduction'' ==

So you want to do a workflow from IANNIX to Max MSP aren't sure how to receive, unpack and use the IANNIX OSC data in Max? We've got you covered.

== '''Preparing IANNIX''' ==

IANNIX makes it crazy easy to send nice OSC-Data. For this tutorial I created a simple Rosette (Files Tab -- Examples -- Rosette -- Quantity 5)
You can use something else, I don't care. For the sake of this tutorial just be sure it has cursors and triggers.

[[File:leif_bild1.png|thumb|200px|left|Simplified Rosette in IANNIX]]

IANNIX automatically sends OSC-Data locally through port 57120, but better check back with this (Config Tab -- Network -- Enable OSC)

[[File:leif_bild2.png|thumb|200px|left|IANNIX OSC Configuration]]

Press Play and boom, stuff is being sent. Well done so far!

== '''Receiving data in Max''' ==

For receiving data Max you'll want to use the '''udpreceive''' function and the host you want to listen to. In our case this comes to

[[File:leif_bild3.png]]

You may want to check if you got everything communicating by using a print command and checking the console, where lots of words and numbers should appear by now (if IANNIX is still playing of course). If nothing appears, check your Hosts or IP-Adresses. If you work on different computers, the udpreceive also needs the sender's IP-Adress, so you should write something like: '''udpreceive [IP-Adress]:[Host]'''

[[File:leif_bild4.png|thumb|200px|left|Checking out if stuff works]]

== '''Working with data in Max''' ==

So let's look at the data received and check out what it means. Back in IANNIX you can hover over any cursor or trigger to see how it's OSC-String is build:

[[File:leif_bild5.png|thumb|200px|left|IANNIX OSC-String]]

So this is what Max is receiving. We've just looked at a trigger, so let's say we want to continue working with data from the triggers exclusively. We can do that with a command in Max:
'''route /trigger'''
This only lets OSC-messages from the triggers through the grid.
To make sense of the string and use only the data we want, we'll use the unpack command, which unpacks (duh) the OSC string, followed by the string's logical structure. In our case this leaves us with
'''unpack 0 0. 0. 0. 0. 0. 0.'''
Now we can do with any of the unpacked information whatever we like (I suggest you do some nice art with it), for this tutorial we'll be fine with just printing them to the console piece by piece, and you're done! '''Nice work!'''
(Tutorial by Leif Weitzel)
[[File:leif_bild6.png|thumb|200px|left|Max Patch to print out individual parts of an OSC-string]]
[[File:leif_bild7.png|thumb|200px|left|Checking back with the console]]

GMU:Tutorials/Networking/Controlling MAX MSP with IanniX

2016-07-27T14:31:56Z

LeifWEi: /* Working with data in Max */

== ''Introduction'' ==

So you want to work with IANNIX and aren't sure how to receive, unpack and use the IANNIX OSC data in Max? We've got you covered.

== '''Preparing IANNIX''' ==

IANNIX makes it crazy easy to send nice OSC-Data. For this tutorial I created a simple Rosette (Files Tab -- Examples -- Rosette -- Quantity 5)
You can use something else, I don't care. For the sake of this tutorial just be sure it has cursors and triggers.

[[File:leif_bild1.png|thumb|200px|left|Simplified Rosette in IANNIX]]

IANNIX automatically sends OSC-Data locally through port 57120, but better check back with this (Config Tab -- Network -- Enable OSC)

[[File:leif_bild2.png|thumb|200px|left|IANNIX OSC Configuration]]

Press Play and boom, stuff is being sent. Well done so far!

== '''Receiving data in Max''' ==

For receiving data Max you'll want to use the '''udpreceive''' function and the host you want to listen to. In our case this comes to

[[File:leif_bild3.png]]

You may want to check if you got everything communicating by using a print command and checking the console, where lots of words and numbers should appear by now (if IANNIX is still playing of course). If nothing appears, check your Hosts or IP-Adresses. If you work on different computers, the udpreceive also needs the sender's IP-Adress, so you should write something like: '''udpreceive [IP-Adress]:[Host]'''

[[File:leif_bild4.png|thumb|200px|left|Checking out if stuff works]]

== '''Working with data in Max''' ==

So let's look at the data received and check out what it means. Back in IANNIX you can hover over any cursor or trigger to see how it's OSC-String is build:

[[File:leif_bild5.png|thumb|200px|left|IANNIX OSC-String]]

So this is what Max is receiving. We've just looked at a trigger, so let's say we want to continue working with data from the triggers exclusively. We can do that with a command in Max:
'''route /trigger'''
This only lets OSC-messages from the triggers through the grid.
To make sense of the string and use only the data we want, we'll use the unpack command, which unpacks (duh) the OSC string, followed by the string's logical structure. In our case this leaves us with
'''unpack 0 0. 0. 0. 0. 0. 0.'''
Now we can do with any of the unpacked information whatever we like (I suggest you do some nice art with it), for this tutorial we'll be fine with just printing them to the console piece by piece, and you're done! '''Nice work!'''
(Tutorial by Leif Weitzel)
[[File:leif_bild6.png|thumb|200px|left|Max Patch to print out individual parts of an OSC-string]]
[[File:leif_bild7.png|thumb|200px|left|Checking back with the console]]

GMU:Tutorials/Networking/Controlling MAX MSP with IanniX

2016-07-27T14:31:25Z

LeifWEi: /* Working with data in Max */

== ''Introduction'' ==

So you want to work with IANNIX and aren't sure how to receive, unpack and use the IANNIX OSC data in Max? We've got you covered.

== '''Preparing IANNIX''' ==

IANNIX makes it crazy easy to send nice OSC-Data. For this tutorial I created a simple Rosette (Files Tab -- Examples -- Rosette -- Quantity 5)
You can use something else, I don't care. For the sake of this tutorial just be sure it has cursors and triggers.

[[File:leif_bild1.png|thumb|200px|left|Simplified Rosette in IANNIX]]

IANNIX automatically sends OSC-Data locally through port 57120, but better check back with this (Config Tab -- Network -- Enable OSC)

[[File:leif_bild2.png|thumb|200px|left|IANNIX OSC Configuration]]

Press Play and boom, stuff is being sent. Well done so far!

== '''Receiving data in Max''' ==

For receiving data Max you'll want to use the '''udpreceive''' function and the host you want to listen to. In our case this comes to

[[File:leif_bild3.png]]

You may want to check if you got everything communicating by using a print command and checking the console, where lots of words and numbers should appear by now (if IANNIX is still playing of course). If nothing appears, check your Hosts or IP-Adresses. If you work on different computers, the udpreceive also needs the sender's IP-Adress, so you should write something like: '''udpreceive [IP-Adress]:[Host]'''

[[File:leif_bild4.png|thumb|200px|left|Checking out if stuff works]]

== '''Working with data in Max''' ==

So let's look at the data received and check out what it means. Back in IANNIX you can hover over any cursor or trigger to see how it's OSC-String is build:

[[File:leif_bild5.png|thumb|200px|left|IANNIX OSC-String]]

So this is what Max is receiving. We've just looked at a trigger, so let's say we want to continue working with data from the triggers exclusively. We can do that with a command in Max:
'''route /trigger'''
This only lets OSC-messages from the triggers through the grid.
To make sense of the string and use only the data we want, we'll use the unpack command, which unpacks (duh) the OSC string, followed by the string's logical structure. In our case this leaves us with
'''unpack 0 0. 0. 0. 0. 0. 0.'''
Now we can do with any of the unpacked information whatever we like (I suggest you do some nice art with it), for this tutorial we'll be fine with just printing them to the console piece by piece, and you're done! '''Nice work!''' (Tutorial by Leif Weitzel)
[[File:leif_bild6.png|thumb|200px|left|Max Patch to print out individual parts of an OSC-string]]
[[File:leif_bild7.png|thumb|200px|left|Checking back with the console]]

GMU:Tutorials/Networking/Controlling MAX MSP with IanniX

2016-07-27T14:27:40Z

LeifWEi: /* Working with data in Max */

== ''Introduction'' ==

So you want to work with IANNIX and aren't sure how to receive, unpack and use the IANNIX OSC data in Max? We've got you covered.

== '''Preparing IANNIX''' ==

IANNIX makes it crazy easy to send nice OSC-Data. For this tutorial I created a simple Rosette (Files Tab -- Examples -- Rosette -- Quantity 5)
You can use something else, I don't care. For the sake of this tutorial just be sure it has cursors and triggers.

[[File:leif_bild1.png|thumb|200px|left|Simplified Rosette in IANNIX]]

IANNIX automatically sends OSC-Data locally through port 57120, but better check back with this (Config Tab -- Network -- Enable OSC)

[[File:leif_bild2.png|thumb|200px|left|IANNIX OSC Configuration]]

Press Play and boom, stuff is being sent. Well done so far!

== '''Receiving data in Max''' ==

For receiving data Max you'll want to use the '''udpreceive''' function and the host you want to listen to. In our case this comes to

[[File:leif_bild3.png]]

You may want to check if you got everything communicating by using a print command and checking the console, where lots of words and numbers should appear by now (if IANNIX is still playing of course). If nothing appears, check your Hosts or IP-Adresses. If you work on different computers, the udpreceive also needs the sender's IP-Adress, so you should write something like: '''udpreceive [IP-Adress]:[Host]'''

[[File:leif_bild4.png|thumb|200px|left|Checking out if stuff works]]

== '''Working with data in Max''' ==

So let's look at the data received and check out what it means. Back in IANNIX you can hover over any cursor or trigger to see how it's OSC-String is build:

[[File:leif_bild5.png|thumb|200px|left|IANNIX OSC-String]]

So this is what Max is receiving. We've just looked at a trigger, so let's say we want to continue working with data from the triggers exclusively. We can do that with a command in Max:
'''route /trigger'''
This only lets OSC-messages from the triggers through the grid.
To make sense of the string and use only the data we want, we'll use the unpack command, which unpacks (duh) the OSC string, followed by the string's logical structure. In our case this leaves us with
'''unpack 0 0. 0. 0. 0. 0. 0.'''
Now we can do with any of the unpacked information whatever we like (I suggest you do some nice art with it), for this tutorial we'll be fine with just printing them to the console piece by piece, and you're done! '''Nice work!'''
[[File:leif_bild6.png|thumb|200px|left|Max Patch to print out individual parts of an OSC-string]]
[[File:leif_bild7.png|thumb|200px|left|Checking back with the console]]

GMU:Tutorials/Networking/Controlling MAX MSP with IanniX

2016-07-27T14:26:56Z

LeifWEi: /* Receiving data in Max */

== ''Introduction'' ==

So you want to work with IANNIX and aren't sure how to receive, unpack and use the IANNIX OSC data in Max? We've got you covered.

== '''Preparing IANNIX''' ==

IANNIX makes it crazy easy to send nice OSC-Data. For this tutorial I created a simple Rosette (Files Tab -- Examples -- Rosette -- Quantity 5)
You can use something else, I don't care. For the sake of this tutorial just be sure it has cursors and triggers.

[[File:leif_bild1.png|thumb|200px|left|Simplified Rosette in IANNIX]]

IANNIX automatically sends OSC-Data locally through port 57120, but better check back with this (Config Tab -- Network -- Enable OSC)

[[File:leif_bild2.png|thumb|200px|left|IANNIX OSC Configuration]]

Press Play and boom, stuff is being sent. Well done so far!

== '''Receiving data in Max''' ==

For receiving data Max you'll want to use the '''udpreceive''' function and the host you want to listen to. In our case this comes to

[[File:leif_bild3.png]]

You may want to check if you got everything communicating by using a print command and checking the console, where lots of words and numbers should appear by now (if IANNIX is still playing of course). If nothing appears, check your Hosts or IP-Adresses. If you work on different computers, the udpreceive also needs the sender's IP-Adress, so you should write something like: '''udpreceive [IP-Adress]:[Host]'''

[[File:leif_bild4.png|thumb|200px|left|Checking out if stuff works]]

== '''Working with data in Max''' ==

So let's look at the data received and check out what it means. Back in IANNIX you can hover over any cursor or trigger to see how it's OSC-String is build:

[[File:leif_bild5.png|thumb|200px|left|IANNIX OSC-String]]

So this is what Max is receiving. We've just looked at a trigger, so let's say we want to continue working with data from the triggers exclusively. We can do that with a command in Max:
'''route /trigger'''
This only lets OSC-messages from the triggers through the grid.
To make sense of the string and use only the data we want, we'll use the unpack command, which unpacks (duh) the OSC string, followed by the string's logical structure. In our case this leaves us with
'''unpack 0 0. 0. 0. 0. 0. 0.'''
Now we can do with any of the unpacked information whatever we like (I suggest you do some nice art with it), for this tutorial we'll be fine with just printing them to the console piece by piece, and you're done! '''Nice work!'''
[[File:leif_bild6.png|thumb|200px|left|Max Patch to print out individual parts of an OSC-string]]
[[File:leif_bild7.png|thumb|200px|left|Checking back with the console]]

GMU:Tutorials/Networking/Controlling MAX MSP with IanniX

2016-07-27T14:25:43Z

LeifWEi: /* Preparing IANNIX */

== ''Introduction'' ==

So you want to work with IANNIX and aren't sure how to receive, unpack and use the IANNIX OSC data in Max? We've got you covered.

== '''Preparing IANNIX''' ==

IANNIX makes it crazy easy to send nice OSC-Data. For this tutorial I created a simple Rosette (Files Tab -- Examples -- Rosette -- Quantity 5)
You can use something else, I don't care. For the sake of this tutorial just be sure it has cursors and triggers.

[[File:leif_bild1.png|thumb|200px|left|Simplified Rosette in IANNIX]]

IANNIX automatically sends OSC-Data locally through port 57120, but better check back with this (Config Tab -- Network -- Enable OSC)

[[File:leif_bild2.png|thumb|200px|left|IANNIX OSC Configuration]]

Press Play and boom, stuff is being sent. Well done so far!

== '''Receiving data in Max''' ==

For receiving data Max you'll want to use the '''udpreceive''' function and the host you want to listen to. In our case this comes to[[File:leif_bild3.png]]

You may want to check if you got everything communicating by using a print command and checking the console, where lots of words and numbers should appear by now (if IANNIX is still playing of course). If nothing appears, check your Hosts or IP-Adresses. If you work on different computers, the udpreceive also needs the sender's IP-Adress, so you should write something like: '''udpreceive [IP-Adress]:[Host]'''

[[File:leif_bild4.png|thumb|200px|left|Checking if stuff works]]

== '''Working with data in Max''' ==

So let's look at the data received and check out what it means. Back in IANNIX you can hover over any cursor or trigger to see how it's OSC-String is build:

[[File:leif_bild5.png|thumb|200px|left|IANNIX OSC-String]]

So this is what Max is receiving. We've just looked at a trigger, so let's say we want to continue working with data from the triggers exclusively. We can do that with a command in Max:
'''route /trigger'''
This only lets OSC-messages from the triggers through the grid.
To make sense of the string and use only the data we want, we'll use the unpack command, which unpacks (duh) the OSC string, followed by the string's logical structure. In our case this leaves us with
'''unpack 0 0. 0. 0. 0. 0. 0.'''
Now we can do with any of the unpacked information whatever we like (I suggest you do some nice art with it), for this tutorial we'll be fine with just printing them to the console piece by piece, and you're done! '''Nice work!'''
[[File:leif_bild6.png|thumb|200px|left|Max Patch to print out individual parts of an OSC-string]]
[[File:leif_bild7.png|thumb|200px|left|Checking back with the console]]

File:Leif bild7.png

2016-07-27T14:24:20Z

LeifWEi:

== Summary ==

== Copyright status: ==

== Licensing ==
{{self|Cc-zero}}
== Source: ==

File:Leif bild6.png

2016-07-27T14:24:03Z

LeifWEi:

== Summary ==

== Copyright status: ==

== Licensing ==
{{self|Cc-zero}}
== Source: ==

File:Leif bild5.png

2016-07-27T14:23:47Z

LeifWEi:

== Summary ==

== Copyright status: ==

== Licensing ==
{{self|Cc-zero}}
== Source: ==

File:Leif bild4.png

2016-07-27T14:23:29Z

LeifWEi:

== Summary ==

== Copyright status: ==

== Licensing ==
{{self|Cc-zero}}
== Source: ==

File:Leif bild3.png

2016-07-27T14:23:08Z

LeifWEi:

== Summary ==

== Copyright status: ==

== Licensing ==
{{self|Cc-zero}}
== Source: ==

File:Leif bild2.png

2016-07-27T14:22:45Z

LeifWEi:

== Summary ==

== Copyright status: ==

== Licensing ==
{{self|Cc-zero}}
== Source: ==

GMU:Tutorials/Networking/Controlling MAX MSP with IanniX

2016-07-27T14:22:20Z

LeifWEi: Created page with "== ''Introduction'' == So you want to work with IANNIX and aren't sure how to receive, unpack and use the IANNIX OSC data in Max? We've got you covered. == '''Preparing IANNIX'..."

== ''Introduction'' ==

So you want to work with IANNIX and aren't sure how to receive, unpack and use the IANNIX OSC data in Max? We've got you covered.

== '''Preparing IANNIX''' ==

IANNIX makes it crazy easy to send nice OSC-Data. For this tutorial I created a simple Rosette (Files Tab -- Examples -- Rosette -- Quantity 5)
You can use something else, I don't care. For the sake of this tutorial just be sure it has cursors and triggers.

[[File:leif_bild1.png|thumb|200px|left|Simplified Rosette in IANNIX]]

IANNIX automatically sends OSC-Data locally through port 57120, but better check back with this (Config Tab -- Network -- Enable OSC)

[[File:leif_bild2.png|thumb|200px|left|IANNIX OSC Configuration]]

Press Play and boom, stuff is being sent. Well done so far!

== '''Receiving data in Max''' ==

For receiving data Max you'll want to use the '''udpreceive''' function and the host you want to listen to. In our case this comes to[[File:leif_bild3.png]]

You may want to check if you got everything communicating by using a print command and checking the console, where lots of words and numbers should appear by now (if IANNIX is still playing of course). If nothing appears, check your Hosts or IP-Adresses. If you work on different computers, the udpreceive also needs the sender's IP-Adress, so you should write something like: '''udpreceive [IP-Adress]:[Host]'''

[[File:leif_bild4.png|thumb|200px|left|Checking if stuff works]]

== '''Working with data in Max''' ==

So let's look at the data received and check out what it means. Back in IANNIX you can hover over any cursor or trigger to see how it's OSC-String is build:

[[File:leif_bild5.png|thumb|200px|left|IANNIX OSC-String]]

So this is what Max is receiving. We've just looked at a trigger, so let's say we want to continue working with data from the triggers exclusively. We can do that with a command in Max:
'''route /trigger'''
This only lets OSC-messages from the triggers through the grid.
To make sense of the string and use only the data we want, we'll use the unpack command, which unpacks (duh) the OSC string, followed by the string's logical structure. In our case this leaves us with
'''unpack 0 0. 0. 0. 0. 0. 0.'''
Now we can do with any of the unpacked information whatever we like (I suggest you do some nice art with it), for this tutorial we'll be fine with just printing them to the console piece by piece, and you're done! '''Nice work!'''
[[File:leif_bild6.png|thumb|200px|left|Max Patch to print out individual parts of an OSC-string]]
[[File:leif_bild7.png|thumb|200px|left|Checking back with the console]]

File:Leif bild1.png

2016-07-27T13:28:21Z

LeifWEi:

== Summary ==

== Copyright status: ==

== Licensing ==
{{self|Cc-zero}}
== Source: ==

GMU:Performance Platform

2016-06-22T19:00:06Z

LeifWEi:

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]]

 

* 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. 
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
|}

 

=== 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).

 

* '''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: [[/Networking/Controlling MAX MSP with IanniX|Controlling MAX MSP with IanniX]]
* 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 – '''[[/Woll's World|Woll's World]] – 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]]
* Group 10 – '''[[/Balance|Balance]] – GMU'''
** Preferred Slots: 7,8,10,11,12
** '''Yuxin Tan''' - Tutorial: [[GMU:Tutorials/Performance_Platform/Using the tracking system|Using the Tracking System to Track the position of arthrosis in Unity]]
** '''Junyuan Wu''' - Tutorial: [[GMU:Tutorials/Performance_Platform/Using the tracking system|Using the Tracking System to control the movement of the scene in Unity]]

== 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
* Elena Liv Felderer - Tutorial: [[GMU: Tutorials/Networking Tutorials|Controlling Unity with Processing]]
** no slots for me

== 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]]. 
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. 
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:Performance Platform

2016-06-22T18:59:04Z

LeifWEi:

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]]

 

* 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. 
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
|}

 

=== 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).

 

* '''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:
[[/Networking/Controlling MAX MSP with IanniX|Controlling MAX MSP with IanniX]]
* 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 – '''[[/Woll's World|Woll's World]] – 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]]
* Group 10 – '''[[/Balance|Balance]] – GMU'''
** Preferred Slots: 7,8,10,11,12
** '''Yuxin Tan''' - Tutorial: [[GMU:Tutorials/Performance_Platform/Using the tracking system|Using the Tracking System to Track the position of arthrosis in Unity]]
** '''Junyuan Wu''' - Tutorial: [[GMU:Tutorials/Performance_Platform/Using the tracking system|Using the Tracking System to control the movement of the scene in Unity]]

== 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
* Elena Liv Felderer - Tutorial: [[GMU: Tutorials/Networking Tutorials|Controlling Unity with Processing]]
** no slots for me

== 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]]. 
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. 
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/Group Leif/Rachel/Kei

2016-06-16T13:21:03Z

LeifWEi: /* Visual Part */

== Overview ==

[[File:setupgraph.png]]

== OSC message generation ==

We used cooked spaghetti to send Serial messages to processing via Arduino using the analogue pin and a voltage divider circuit with the spaghetti acting as a variable resistor. [https://www.uni-weimar.de/medien/wiki/GMU:Sensor_Hacklab/Rachel_Smith (More documentation of this here) ]Processing then sent on these values as OSC messages to Max MSP and Unity.

[[File:Shrs1.png]]
[[File:Dplrs3.png]]
[[File:Dplrs1.png]]
[[File:Dplrs2.png]]

== Visual Part ==

'''Computer 2 splits the incoming OSC-messages to be read by unity on the same machine and sent to computer 3. This is easily done in MAX:
'''

[[File:maxsplit.png]]

'''Unity gets the OSC-messages with a script like this (google might help):'''

[[File:unityleif1.png]]

'''and makes the object move, in this case spin, depending on the OCS signal
'''

[[File:unityleif2.png]]

== Sound Part ==
Max patches for generating noise:

[[Image:Noise generator.jpg]]

GMU:Digital Puppetry Lab/Group Leif/Rachel/Kei

2016-06-16T13:20:35Z

LeifWEi: /* Visual Part */

== Overview ==

[[File:setupgraph.png]]

== OSC message generation ==

We used cooked spaghetti to send Serial messages to processing via Arduino using the analogue pin and a voltage divider circuit with the spaghetti acting as a variable resistor. [https://www.uni-weimar.de/medien/wiki/GMU:Sensor_Hacklab/Rachel_Smith (More documentation of this here) ]Processing then sent on these values as OSC messages to Max MSP and Unity.

[[File:Shrs1.png]]
[[File:Dplrs3.png]]
[[File:Dplrs1.png]]
[[File:Dplrs2.png]]

== Visual Part ==

'''Computer 2 splits the incoming OSC-messages to be read by unity on the same machine and sent to computer 3. This is easily done in MAX:
'''

[[File:maxsplit.png]]

'''Unity gets the code with a script like this (google might help):'''

[[File:unityleif1.png]]

'''and makes the object move, in this case spin, depending on the OCS signal
'''

[[File:unityleif2.png]]

== Sound Part ==
Max patches for generating noise:

[[Image:Noise generator.jpg]]

File:Unityleif2.png

2016-06-16T13:19:48Z

LeifWEi:

== Summary ==

== Copyright status: ==

== Source: ==

File:Unityleif1.png

2016-06-16T13:19:27Z

LeifWEi:

== Summary ==

== Copyright status: ==

== Source: ==

GMU:Digital Puppetry Lab/Group Leif/Rachel/Kei

2016-06-16T13:18:56Z

LeifWEi: /* Visual Part */

== Overview ==

[[File:setupgraph.png]]

== OSC message generation ==

We used cooked spaghetti to send Serial messages to processing via Arduino using the analogue pin and a voltage divider circuit with the spaghetti acting as a variable resistor. [https://www.uni-weimar.de/medien/wiki/GMU:Sensor_Hacklab/Rachel_Smith (More documentation of this here) ]Processing then sent on these values as OSC messages to Max MSP and Unity.

[[File:Shrs1.png]]
[[File:Dplrs3.png]]
[[File:Dplrs1.png]]
[[File:Dplrs2.png]]

== Visual Part ==
Computer 2 splits the incoming OSC-messages to be read by unity on the same machine and sent to computer 3. This is easily done in MAX:
[[File:maxsplit.png]]

Unity gets the code with a script like this (google might help):
[[File:unityleif1.png]]

and makes the object move, in this case spin, depending on the OCS signal
[[File:unityleif2.png]]

== Sound Part ==
Max patches for generating noise:

[[Image:Noise generator.jpg]]

GMU:Digital Puppetry Lab/Group Leif/Rachel/Kei

2016-06-16T13:18:19Z

LeifWEi: /* Visual Part */

== Overview ==

[[File:setupgraph.png]]

== OSC message generation ==

We used cooked spaghetti to send Serial messages to processing via Arduino using the analogue pin and a voltage divider circuit with the spaghetti acting as a variable resistor. [https://www.uni-weimar.de/medien/wiki/GMU:Sensor_Hacklab/Rachel_Smith (More documentation of this here) ]Processing then sent on these values as OSC messages to Max MSP and Unity.

[[File:Shrs1.png]]
[[File:Dplrs3.png]]
[[File:Dplrs1.png]]
[[File:Dplrs2.png]]

== Visual Part ==
Computer 2 splits the incoming OSC-messages to be read by unity on the same machine and sent to computer 3. This is easily done in MAX:
[[File:maxsplit.png]]

Unity gets the code with a script like this (google might help):
[[File:unity2.png]]

and makes the object move, in this case spin, depending on the OCS signal
[[File:codeunity.png]]

== Sound Part ==
Max patches for generating noise:

[[Image:Noise generator.jpg]]

File:Unity.png

2016-06-16T13:17:37Z

LeifWEi:

== Summary ==

== Copyright status: ==

== Source: ==

File:Codeunity.png

2016-06-16T13:12:50Z

LeifWEi:

== Summary ==

== Copyright status: ==

== Source: ==

File:Maxsplit.png

2016-06-16T13:12:06Z

LeifWEi:

== Summary ==

== Copyright status: ==

== Source: ==

GMU:Digital Puppetry Lab/Group Leif/Rachel/Kei

2016-06-16T13:11:54Z

LeifWEi: /* Visual Part */

== Overview ==

[[File:setupgraph.png]]

== OSC message generation ==

We used cooked spaghetti to send Serial messages to processing via Arduino using the analogue pin and a voltage divider circuit with the spaghetti acting as a variable resistor. [https://www.uni-weimar.de/medien/wiki/GMU:Sensor_Hacklab/Rachel_Smith (More documentation of this here) ]Processing then sent on these values as OSC messages to Max MSP and Unity.

[[File:Shrs1.png]]
[[File:Dplrs3.png]]
[[File:Dplrs1.png]]
[[File:Dplrs2.png]]

== Visual Part ==
Computer 2 splits the incoming OSC-messages to be read by unity on the same machine and sent to computer 3. This is easily done in MAX:
[[File:maxsplit.png]]

Unity gets the code with a script like this (google might help):
[[File:codeunity.png]]

and makes the object move, in this case spin, depending on the OCS signal
[[File:unity.png]]

== Sound Part ==
Max patches for generating noise:

[[Image:Noise generator.jpg]]

GMU:Digital Puppetry Lab/Group Leif/Rachel/Kei

2016-06-16T13:11:07Z

LeifWEi: /* Visual Part */

== Overview ==

[[File:setupgraph.png]]

== OSC message generation ==

We used cooked spaghetti to send Serial messages to processing via Arduino using the analogue pin and a voltage divider circuit with the spaghetti acting as a variable resistor. [https://www.uni-weimar.de/medien/wiki/GMU:Sensor_Hacklab/Rachel_Smith (More documentation of this here) ]Processing then sent on these values as OSC messages to Max MSP and Unity.

[[File:Shrs1.png]]
[[File:Dplrs3.png]]
[[File:Dplrs1.png]]
[[File:Dplrs2.png]]

== Visual Part ==
Computer 2 splits the incoming OSC-messages to be read by unity on the same machine and sent to computer 3. This is easily done in MAX:
[[File:max.png]]

Unity gets the code with a script like this (google might help):
[[File:code.png]]

and makes the object move, in this case spin, depending on the OCS signal
[[File:unity.png]]

== Sound Part ==
Max patches for generating noise:

[[Image:Noise generator.jpg]]

GMU:Digital Puppetry Lab/Group Leif/Rachel/Kei

2016-06-16T13:08:21Z

LeifWEi: /* Overview */

File:Setupgraph.png

2016-06-16T13:07:56Z

LeifWEi:

== Summary ==

== Copyright status: ==

== Source: ==

GMU:Digital Puppetry Lab

2016-04-29T09:35:16Z

LeifWEi:

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

 

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

Note:
'''Application is now closed.'''
'''All applicants are invited to the Kickoff meeting at the DBL is on TUESDAY, 19:00h.'''
== Tutoriums ==

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

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

=== May ===
* 03. May, Tue, 19:00 (Max, Su Li)
* 04. May, Wed, 17:00 (Max*, Ben, Su Li )
* 10. May, Tue, 19:00 (Max, Ben, Su Li )
* 17. May, Tue, 19:00 (Max,Su Li )
* 18. May, Wed, 17:00 (Max*, Ben, Su Li )
* 24. May, Tue, 19:00 (Max,Su Li )
* 31. May, Tue, 19:00 (Max, Ben, Su Li)

=== June ===
* 01. June, Wed, 17:00 (Max*, Ben, Su Li)
* 07. June, Tue, 19:00 (Max,Su Li)
* 14. June, Tue, 19:00 (Max, Su Li)
* 15. June, Wed, 17:00 (Max*, Ben, Su Li)
* 21. June, Tue, 19:00 (Max, Ben, Su Li)
* 28. June, Tue, 19:00 (Max,Su Li)
* 29. June, Wed, 17:00 (Max*, Ben, Su Li)

=== July ===
* 05. July, Tue, 19:00 (Max, Ben, Su Li)
* 12. July, Tue, 19:00 (Max,Su Li)
* 13. July, Wed, 17:00 (Max*, Ben, Su Li)

== Weekend Workshop ==

=== Be Prepared ===

Please make sure to install the software on your laptops at home. 
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)

* [https://www.youtube.com/playlist?list=PL12DC9A161D8DC5DC Pure Data Video Tutorial]

=== 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]]
* [[/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]]

== 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]] 
'''Subject:''' Digital Puppetry Lab /// Application 
'''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
* 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]]