Medien Wiki - User contributions [en]

EKK:LoFi Sounds in HiFi Spaces/Wind stream

2013-05-06T14:55:54Z

Ludwigberger:

===Idea===
The idea is to transmit wind from San Diego to Weimar and vice versa. The wind would be analyzed at one side via anemometers (wind sensors) and reproduced at the other side via computer fans. We want to trasnmit not only the speed, but also the direction of the wind (e.g. due "octophonic" positioning of the fans). Sound aspects of the fans/wind should also be considered.

===Possibilities of collaboration===
* transmitting wind data
* developing a collective installation

===Participants===
Team Weimar:
* [[../Cornelio/]]
* [[../Jonas/]]
* [[../Ludwigberger/]]

Team San Diego:
* [[../Andy/]]

===Questions and Research===
====name====
* wind stream
* wind transfer
* wind tunnel
====central idea====
* concept / philosophy
* which sense
** sound
** visual
** haptic / skin
* transparency of used material
* one way / two way communication : Weimar <-> San Diego
====reference works====
* art dealing with wind / weather
* dealing with fans / ventilators
* sound bridges etc.
* translating sound in different media
* how has wind been sonificated?
====scientific research====
* what is wind, how it works
* what is the sound of wind, what could it be
* how does wind feel
* meteorology
* philosophy of wind
====technical aspects / material====
* ventilators/fans
** type (computer fans etc.)
** sound
** parameters
** control
** costs
** power / wind speed / air pressure
* wind sensors (anemometers)
** several or one directional?
** weather station? (temperature, humidity, rain, etc.)
** parameters
* software & hardware
** Arduino
** Raspberry Pi
** Processing
** PureData / Max
** Wview
* data transmission
**control data (OSC)
**…
* setup
** arrangement of the different parts
** how to deal with space
** the context (other installations etc.)
** additional material for visualisation (dust, cloth etc.)
** permant or singular installation?

EKK:LoFi Sounds in HiFi Spaces/Wind stream

2013-05-06T14:55:19Z

Ludwigberger: /* Project Task Queue */

===Idea===
The idea is to transmit wind from San Diego to Weimar and vice versa. The wind would be analyzed at one side via anemometers (wind sensors) and reproduced at the other side via computer fans. We want to trasnmit not only the speed, but also the direction of the wind (e.g. due "octophonic" positioning of the fans). Sound aspects of the fans/wind should also be considered.

===Possibilities of collaboration===
* transmitting wind data
* developing a collective installation

===Participants===
Team Weimar:
* [[../Cornelio/]]
* [[../Jonas/]]
* [[../Ludwigberger/]]

Team San Diego:
* [[../Andy/]]

===Questions and Research===

====name====
* wind stream
* wind transfer
* wind tunnel

====central idea====
* concept / philosophy
* which sense
** sound
** visual
** haptic / skin
* transparency of used material
* one way / two way communication : Weimar <-> San Diego

====reference works====
* art dealing with wind / weather
* dealing with fans / ventilators
* sound bridges etc.
* translating sound in different media
* how has wind been sonificated?

====scientific research====
* what is wind, how it works
* what is the sound of wind, what could it be
* how does wind feel
* meteorology
* philosophy of wind

====technical aspects / material====
* ventilators/fans
** type (computer fans etc.)
** sound
** parameters
** control
** costs
** power / wind speed / air pressure
* wind sensors (anemometers)
** several or one directional?
** weather station? (temperature, humidity, rain, etc.)
** parameters
* software & hardware
** Arduino
** Raspberry Pi
** Processing
** PureData / Max
** Wview
* data transmission
**control data (OSC)
**…
* setup
** arrangement of the different parts
** how to deal with space
** the context (other installations etc.)
** additional material for visualisation (dust, cloth etc.)
** permant or singular installation?

EKK:LoFi Sounds in HiFi Spaces/Wind stream

2013-05-06T14:54:05Z

Ludwigberger:

===Idea===
The idea is to transmit wind from San Diego to Weimar and vice versa. The wind would be analyzed at one side via anemometers (wind sensors) and reproduced at the other side via computer fans. We want to trasnmit not only the speed, but also the direction of the wind (e.g. due "octophonic" positioning of the fans). Sound aspects of the fans/wind should also be considered.

===Possibilities of collaboration===
* transmitting wind data
* developing a collective installation

===Participants===
Team Weimar:
* [[../Cornelio/]]
* [[../Jonas/]]
* [[../Ludwigberger/]]

Team San Diego:
* [[../Andy/]]

===Project Task Queue===

====name====
* wind stream
* wind transfer
* wind tunnel

====central idea====
* concept / philosophy
* which sense
** sound
** visual
** haptic / skin
* transparency of used material
* one way / two way communication : Weimar <-> San Diego

====reference works====
* art dealing with wind / weather
* dealing with fans / ventilators
* sound bridges etc.
* translating sound in different media
* how has wind been sonificated?

====scientific research====
* what is wind, how it works
* what is the sound of wind, what could it be
* how does wind feel
* meteorology
* philosophy of wind

====technical aspects / material====

* ventilators/fans
** type (computer fans etc.)
** sound
** parameters
** control
** costs
** power / wind speed / air pressure
* wind sensors (anemometers)
** several or one directional?
** weather station? (temperature, humidity, rain, etc.)
** parameters
* software & hardware
** Arduino
** Raspberry Pi
** Processing
** PureData / Max
** Wview
* data transmission
**control data (OSC)
**…
* setup
** arrangement of the different parts
** how to deal with space
** the context (other installations etc.)
** additional material for visualisation (dust, cloth etc.)
** permant or singular installation?

EKK:LoFi Sounds in HiFi Spaces/Wind stream

2013-05-06T11:07:40Z

Ludwigberger: /* Participants */

EKK:LoFi Sounds in HiFi Spaces/Wind stream

2013-05-06T11:05:53Z

Ludwigberger: Created page with "===Idea=== The idea is to transmit wind from San Diego to Weimar and vice versa. The wind would be analyzed at one side via anemometers (wind sensors) and reproduced at the other..."

EKK:LoFi Sounds in HiFi Spaces

2013-05-06T11:05:45Z

Ludwigberger: /* Collaborative Projects */

[[:Category:Projektmodul|Projektmodul]] 
''Lecturers:'' [[Robin Minard]], [[/miller|Miller Puckette]], Katharina Rosenberger, [[/Shahrokh|Shahrokh Yadegari]], [[Ludger Hennig]], [[Max Neupert]] 
''Credits:'' 18 [[ECTS]], 16 [[SWS]] 
''Date:'' Monday, 18:00 until 21:30 h (due to the time difference to San Diego) 
''Venue:'' [[Coudraystraße 13a]], SeaM Werkstattstudio 
''First meeting:'' 15.04.2013

==Description==
The sensation of space through spatialized sound may be influenced by sources that differ in their quality and quantity. Within this project, we will investigate ways to modify, expand or augment how space can be experienced through sound. The outcome may be, for instance, an electroacoustic composition, a simulation of spatial perception, sonic architecture or a set-design as a virtual or performative environment.

This project is the beginning of a long-term cooperation between the Bauhaus-Universität Weimar and the University of California in San Diego. Partners in Weimar are Prof. Robin Minard and Ludger Hennig from the Studio for Electroacoustic Music (SeaM) and Max Neupert (Medial Environments). Partners in San Diego are Prof. Miller Puckette (Computer Music), Prof. Katharina Rosenberger (Music) and Prof. Shahrokh Yadegari (Theatre and Dance). Telematic classes will allow students from both faculties to work together. Classes will take place in Weimar in the evening, mid-morning in San Diego. The cooperation is funded by the German Academic Exchange Service (DAAD).

===German description===
Die Wahrnehmung von Raum durch verräumlichten Klang, kann durch Klangquellen beeinflusst werden, welche sich in ihrer Qualität und Quantität unterscheiden. In diesem Projekt werden wir untersuchen, auf welche Art wir die Erfahrung von Raum durch den Klang verändern, erweitern oder verbessern können. Das Ergebnis kann beispielsweise eine elektroakustische Komposition, eine Simulation einer räumlichen Wahrnehmung, klangliche Architektur oder ein Bühnenbild als virtuelle oder performative Umgebung sein.

Dieses Projekt ist der Beginn einer langfristigen Zusammenarbeit zwischen der Bauhaus-Universität und der Universität von Kalifornien in San Diego. Partner aus Weimar sind Prof. Robin Minard und Ludger Hennig vom Studio für Elektoakustische Musik (SeaM) und Max Neupert (Gestaltung medialer Umgebungen). Partner aus San Diego sind Prof. Miller Puckette (Computermusik), Prof. Katharina Rosenberger (Musik) und Prof. Shahrokh Yadegari (Theater und Tanz). Gemeinsamer Unterricht mit einer Videoverbindung wird es den Studierenden beider Universitäten ermöglichen, zusammen zu arbeiten. Der Unterricht wird in Weimar am Abend und vormittags in San Diego stattfinden. Die Zusammenarbeit wird vom Deutschen Akademischen Austauschdienst (DAAD) gefördert.

===Werk/Fachmodule===
We recommend the Werk/Fachmodul [[GMU:Dataflow II]] and/or Ludger Hennigs soundscapes class along with this Project module.

==Assignments==
# [[/Making connection/]] due 04-22
# [[/Mingling sounds/]] due 04-29
# [[/Textualize ideas/]] due 05-06
# [[/Proposing concepts/]] due 05-13

==Evaluation==
Active participation, presentation, artistic examination, documentation, edits in the wiki.

==Participants==
===Weimar===
* [[/Rico/]]
* [[/Alex/]]
* [[/Alice/]]
* [[/Jonas/]]
* [[/Andre/]]
* [[/Paul/]]
* [[/Ben/]]
* [[/Ludwigberger/]]
* [[/TimH/]]
* [[/Dorian/]]
* [[/Clemens/]]
* [[/Ives/]]
* [[/Cornelio/]]
* [[/Johannes/]]

* [[/Max/]] (you may use this as a template for your self-introduction)

===San Diego===
* [[/Brendan Bernhardt Gaffney/]]
* [[/Kevin/]]
* [[/Melanie/]]
* [[/Jeffrey/]]
* [[/Bo/]]
* [[/Andy/]]
* [[/Jamilah/]]
* [[/Marcelo/]]
* [[/Ryan Welsh/]]
* [[/ElisabetCurbelo/]]
* [[/Joe Cantrell/]]
* [[/czyskows/]]
* [[/NickDrashner/]]

* [[/miller/]]
* [[/Shahrokh/]]
* [[/CarolineMiller/]]

==Collaborative Projects==
* [[/Convergence/]]
* [[/Wind stream/]]
* [[/Body Instrument/]]

==Syllabus==
ISO Standard: MONTH/DAY
# 04/01 Only in San Diego (Easter Monday is holiday in Germany; Robin, Ludger and Max join via Skype/Google+ Hangout) faculty presentations about technical means and/or artistic issues. Introduction to the wiki.
# 04/08 Only in San Diego – faculty presentations continued. Miller - Rasberry Pi as an audio and video platform. Shahrokh - Mugic protocol; video walls
# 04/15 First joint class
# 04/22 Robin, Ludger and Max are in San Diego
# 04/29
# 05/06
# 05/13
# 05/20
# 05/27 Only in Weimar (Memorial day in the U.S.)
# 06/03
# 06/10
# 06/17
# 06/24
# 07/01

==SAM connection==
We have two dedicated machines to facilitate the connection between the two places. In Weimar it is remote@141.54.193.23 (Linux Mint), in San Diego it is ideas@ideas-mac.ucsd.edu (OS X)

==Literature==
* Föllmer, Golo: Netzmusik, Wolke Verlag ISBN 3936000336
* LaBelle, Brandon: Background Noise ISBN 9780826418456
* LaBelle, Brandon: Site of Sound: Or Architecture and the Ear ISBN 978-0982743904
* Minard, Robin: Silent Music ISBN 978-3933257130
* Minard, Robin: Sound Installation Art
* Leitner, Bernard: Sound:Space ISBN 978-3893224449

Pd books:
{{Template:PdBooks}}

==Links==
* [https://groups.google.com/forum/#!forum/buw-ucsd-class Google Group BUW-UCSD-class]
* [https://puredata.info/docs/raspberry-pi Pure Data on the Raspberry Pi]

===Sending data over the network===
* [[OSC]]
* netsend/netreceive, netserver/netclient. In Pd look at <tt>mrpeach</tt> and <tt>iemnet libraries</tt>
* [http://ivl.calit2.net/wiki/index.php/StreamingGraphics Mugic]

===Sending Audio and Video over the Internet===
* [[wikipedia:Audio Video Bridging]] AVB is a set of standards for audio and video transmission by the IEEE

====Intended for Communcation====
* [http://www.skype.com Skype] [[File:Icon newtux 16x16.png]] [[File:Icon android 16x16.png]] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]]
* [https://tools.google.com/dlpage/hangoutplugin Google+ Hangout] [[File:Icon newtux 16x16.png]] [[File:Icon android 16x16.png]] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]] (Seems to work best in Chome/Chromium)
* [http://www.oovoo.com ooVoo] [[File:Icon android 16x16.png]] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]]
* [http://www.voxox.com voxox] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]]
* [http://line.naver.jp/en LINE] [[File:Icon android 16x16.png]] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]]
* [http://www.teamviewer.com TeamViewer] [[File:Icon newtux 16x16.png]] [[File:Icon android 16x16.png]] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]]
* [http://www.teamspeak.com TeamSpeak] [[File:Icon newtux 16x16.png]] [[File:Icon android 16x16.png]] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]]

Teleconferencing
* [http://www.polycom.com Polycom] [[File:Icon windows8 16x16.png]] System available in Weimar
* [http://www.radvision.com/Products/Video-Conference-Systems Radvision Scopia] [[File:Icon windows8 16x16.png]]
* [http://www.lifesize.com Livesize] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]] System available in San Diego

Unidirectional only (aka streaming)
* [http://giss.tv Global Independent Streaming Support], [http://giss.tv/wiki/index.php/Main_Page G.I.S.S wiki]
* [http://www.ustream.tv Ustream]
* [http://www.justin.tv justin.tv]
* [http://www.shoutcast.com/ shoutcast] also as vst plugin availlable

====Intended for Performance/Creative Use====
* [http://code.sat.qc.ca/redmine/projects/scenic/wiki/Scenic_fr Scenic] Audio and video in high quality, as well as MIDI [[File:Icon newtux 16x16.png]]
* [http://code.google.com/p/jacktrip JackTrip] [[File:Icon newtux 16x16.png]] [[File:Icon apple 16x16.png]] a network extension for [http://jackaudio.org/ Jack Audio Connection Kit] [[File:Icon newtux 16x16.png]] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]]
* [http://gstreamer.freedesktop.org GStreamer] and bindings for Pd: [http://umlaeute.mur.at/Members/zmoelnig/projects/pdgst PdGst] [[File:Icon newtux 16x16.png]]
* netsend~ for Max/MSP and Pd: [http://www.nullmedium.de/dev/netsend~ Olaf Matthes' Original Version] [[File:Icon newtux 16x16.png]] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]], [http://www.olivierguillerminet.com/portfolio/netsend Olivier Guillerminet's/Remu's Fork] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]]
* [http://code.google.com/p/streaming-audio Streaming Audio Manager (SAM)] by [https://ccrma.stanford.edu/~danielsm/research.html Michelle Daniels] [[File:Icon newtux 16x16.png]] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]]

===Performing Remotely===
* [http://www.netpd.org NetPd]
* [http://at.or.at/serendipd SerendiPd] collaborative patching

[[Category:SS13]]
[[Category:Projektmodul]]
[[Category:Robin Minard]]
[[Category:Miller Puckette]]
[[Category:Katharina Rosenberger]]
[[Category:Shahrokh Yadegari]]
[[Category:Ludger Hennig]]
[[Category:Max Neupert]]
[[Category:Pure Data]]
[[Category:Performance]]
[[Category:Community]]
[[Category:Max/MSP]]
[[Category:Telematic]]
[[Category:Coorperation]]

EKK:LoFi Sounds in HiFi Spaces/Wind transfer/Ludwigberger

2013-05-03T10:38:59Z

Ludwigberger: Created page with "thumb I study electroacoustic composition under the direction of Robin Minard at the Franz Liszt School of Music in Weimar. ..."

EKK:LoFi Sounds in HiFi Spaces/Ludwigberger

2013-05-03T09:33:58Z

Ludwigberger:

EKK:LoFi Sounds in HiFi Spaces

2013-04-29T18:53:46Z

Ludwigberger: /* Collaborative Projects */

[[:Category:Projektmodul|Projektmodul]] 
''Lecturers:'' [[Robin Minard]], [[/miller|Miller Puckette]], Katharina Rosenberger, [[/Shahrokh|Shahrokh Yadegari]], [[Ludger Hennig]], [[Max Neupert]] 
''Credits:'' 18 [[ECTS]], 16 [[SWS]] 
''Date:'' Monday, 18:00 until 21:30 h (due to the time difference to San Diego) 
''Venue:'' [[Coudraystraße 13a]], SeaM Werkstattstudio 
''First meeting:'' 15.04.2013

==Description==
The sensation of space through spatialized sound may be influenced by sources that differ in their quality and quantity. Within this project, we will investigate ways to modify, expand or augment how space can be experienced through sound. The outcome may be, for instance, an electroacoustic composition, a simulation of spatial perception, sonic architecture or a set-design as a virtual or performative environment.

This project is the beginning of a long-term cooperation between the Bauhaus-Universität Weimar and the University of California in San Diego. Partners in Weimar are Prof. Robin Minard and Ludger Hennig from the Studio for Electroacoustic Music (SeaM) and Max Neupert (Medial Environments). Partners in San Diego are Prof. Miller Puckette (Computer Music), Prof. Katharina Rosenberger (Music) and Prof. Shahrokh Yadegari (Theatre and Dance). Telematic classes will allow students from both faculties to work together. Classes will take place in Weimar in the evening, mid-morning in San Diego. The cooperation is funded by the German Academic Exchange Service (DAAD).

===German description===
Die Wahrnehmung von Raum durch verräumlichten Klang, kann durch Klangquellen beeinflusst werden, welche sich in ihrer Qualität und Quantität unterscheiden. In diesem Projekt werden wir untersuchen, auf welche Art wir die Erfahrung von Raum durch den Klang verändern, erweitern oder verbessern können. Das Ergebnis kann beispielsweise eine elektroakustische Komposition, eine Simulation einer räumlichen Wahrnehmung, klangliche Architektur oder ein Bühnenbild als virtuelle oder performative Umgebung sein.

Dieses Projekt ist der Beginn einer langfristigen Zusammenarbeit zwischen der Bauhaus-Universität und der Universität von Kalifornien in San Diego. Partner aus Weimar sind Prof. Robin Minard und Ludger Hennig vom Studio für Elektoakustische Musik (SeaM) und Max Neupert (Gestaltung medialer Umgebungen). Partner aus San Diego sind Prof. Miller Puckette (Computermusik), Prof. Katharina Rosenberger (Musik) und Prof. Shahrokh Yadegari (Theater und Tanz). Gemeinsamer Unterricht mit einer Videoverbindung wird es den Studierenden beider Universitäten ermöglichen, zusammen zu arbeiten. Der Unterricht wird in Weimar am Abend und vormittags in San Diego stattfinden. Die Zusammenarbeit wird vom Deutschen Akademischen Austauschdienst (DAAD) gefördert.

==Werk/Fachmodule==
We recommend the Werk/Fachmodul [[GMU:Dataflow II]] and/or Ludger Hennigs soundscapes class along with this Project module.

==Assignments==
# [[/Making connection/]] due 04-22
# [[/Mingling sounds/]] due 04-29
# [[/Textualize ideas/]] due 05-06
# [[/Proposing concepts/]] due 05-13

==Evaluation==
Active participation, presentation, artistic examination, documentation, edits in the wiki.

==Participants==
===Weimar===
* [[/Rico/]]
* [[/Alex/]]
* [[/Alice/]]
* [[/Jonas/]]
* [[/Andre/]]
* [[/Paul/]]
* [[/Ben/]]
* [[/Ludwigberger/]]
* [[/TimH/]]
* [[/Dorian/]]
* [[/Clemens/]]
* [[/Ives/]]
* [[/Cornelio/]]
* [[/Johannes/]]

* [[/Max/]] (you may use this as a template for your self-introduction)

===San Diego===
* [[/Brendan Bernhardt Gaffney/]]
* [[/Kevin/]]
* [[/Melanie/]]
* [[/Jeffrey/]]
* [[/Bo/]]
* [[/Andy/]]
* [[/Jamilah/]]
* [[/Marcelo/]]
* [[/Ryan Welsh/]]
* [[/ElisabetCurbelo/]]
* [[/Joe Cantrell/]]
* [[/czyskows/]]
* [[/NickDrashner/]]

* [[/miller/]]
* [[/Shahrokh/]]
* [[/CarolineMiller/]]

==Collaborative Projects==
[[/Wind transfer/]]

==Syllabus==
ISO Standard: MONTH/DAY
# 04/01 Only in San Diego (Easter Monday is holiday in Germany; Robin, Ludger and Max join via Skype/Google+ Hangout) faculty presentations about technical means and/or artistic issues. Introduction to the wiki.
# 04/08 Only in San Diego – faculty presentations continued. Miller - Rasberry Pi as an audio and video platform. Shahrokh - Mugic protocol; video walls
# 04/15 First joint class
# 04/22 Robin, Ludger and Max are in San Diego
# 04/29
# 05/06
# 05/13
# 05/20
# 05/27 Only in Weimar (Memorial day in the U.S.)
# 06/03
# 06/10
# 06/17
# 06/24
# 07/01

==Literature==
* Föllmer, Golo: Netzmusik, Wolke Verlag ISBN 3936000336
* LaBelle, Brandon: Background Noise ISBN 9780826418456
* LaBelle, Brandon: Site of Sound: Or Architecture and the Ear ISBN 978-0982743904
* Minard, Robin: Silent Music ISBN 978-3933257130
* Minard, Robin: Sound Installation Art
* Leitner, Bernard: Sound:Space ISBN 978-3893224449

Pd books:
{{Template:PdBooks}}

==Links==
* [https://groups.google.com/forum/#!forum/buw-ucsd-class Google Group BUW-UCSD-class]
* [https://puredata.info/docs/raspberry-pi Pure Data on the Raspberry Pi]

===Sending data over the network===
* [[OSC]]
* netsend/netreceive, netserver/netclient. In Pd look at <tt>mrpeach</tt> and <tt>iemnet libraries</tt>
* [http://ivl.calit2.net/wiki/index.php/StreamingGraphics Mugic]

===Sending Audio and Video over the Internet===
* [[wikipedia:Audio Video Bridging]] AVB is a set of standards for audio and video transmission by the IEEE

====Intended for Communcation====
* [http://www.skype.com Skype] [[File:Icon newtux 16x16.png]] [[File:Icon android 16x16.png]] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]]
* [https://tools.google.com/dlpage/hangoutplugin Google+ Hangout] [[File:Icon newtux 16x16.png]] [[File:Icon android 16x16.png]] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]] (Seems to work best in Chome/Chromium)
* [http://www.oovoo.com ooVoo] [[File:Icon android 16x16.png]] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]]
* [http://www.voxox.com voxox] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]]
* [http://line.naver.jp/en LINE] [[File:Icon android 16x16.png]] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]]
* [http://www.teamviewer.com TeamViewer] [[File:Icon newtux 16x16.png]] [[File:Icon android 16x16.png]] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]]
* [http://www.teamspeak.com TeamSpeak] [[File:Icon newtux 16x16.png]] [[File:Icon android 16x16.png]] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]]

Teleconferencing
* [http://www.polycom.com Polycom] [[File:Icon windows8 16x16.png]] System available in Weimar
* [http://www.radvision.com/Products/Video-Conference-Systems Radvision Scopia] [[File:Icon windows8 16x16.png]]
* [http://www.lifesize.com Livesize] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]] System available in San Diego

Unidirectional only (aka streaming)
* [http://giss.tv Global Independent Streaming Support], [http://giss.tv/wiki/index.php/Main_Page G.I.S.S wiki]
* [http://www.ustream.tv Ustream]
* [http://www.justin.tv justin.tv]
* [http://www.shoutcast.com/ shoutcast] also as vst plugin availlable

====Intended for Performance/Creative Use====
* [http://code.sat.qc.ca/redmine/projects/scenic/wiki/Scenic_fr Scenic] Audio and video in high quality, as well as MIDI [[File:Icon newtux 16x16.png]]
* [http://code.google.com/p/jacktrip JackTrip] [[File:Icon newtux 16x16.png]] [[File:Icon apple 16x16.png]] a network extension for [http://jackaudio.org/ Jack Audio Connection Kit] [[File:Icon newtux 16x16.png]] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]]
* [http://gstreamer.freedesktop.org GStreamer] and bindings for Pd: [http://umlaeute.mur.at/Members/zmoelnig/projects/pdgst PdGst] [[File:Icon newtux 16x16.png]]
* netsend~ for Max/MSP and Pd: [http://www.nullmedium.de/dev/netsend~ Olaf Matthes' Original Version] [[File:Icon newtux 16x16.png]] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]], [http://www.olivierguillerminet.com/portfolio/netsend Olivier Guillerminet's/Remu's Fork] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]]
* [http://code.google.com/p/streaming-audio Streaming Audio Manager (SAM)] by [https://ccrma.stanford.edu/~danielsm/research.html Michelle Daniels] [[File:Icon newtux 16x16.png]] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]]

===Performing Remotely===
* [http://www.netpd.org NetPd]
* [http://at.or.at/serendipd SerendiPd] collaborative patching

EKK:LoFi Sounds in HiFi Spaces

2013-04-29T18:36:51Z

Ludwigberger: /* Collaborative Projects */

[[:Category:Projektmodul|Projektmodul]] 
''Lecturers:'' [[Robin Minard]], [[/miller|Miller Puckette]], Katharina Rosenberger, [[/Shahrokh|Shahrokh Yadegari]], [[Ludger Hennig]], [[Max Neupert]] 
''Credits:'' 18 [[ECTS]], 16 [[SWS]] 
''Date:'' Monday, 18:00 until 21:30 h (due to the time difference to San Diego) 
''Venue:'' [[Coudraystraße 13a]], SeaM Werkstattstudio 
''First meeting:'' 15.04.2013

==Description==
The sensation of space through spatialized sound may be influenced by sources that differ in their quality and quantity. Within this project, we will investigate ways to modify, expand or augment how space can be experienced through sound. The outcome may be, for instance, an electroacoustic composition, a simulation of spatial perception, sonic architecture or a set-design as a virtual or performative environment.

This project is the beginning of a long-term cooperation between the Bauhaus-Universität Weimar and the University of California in San Diego. Partners in Weimar are Prof. Robin Minard and Ludger Hennig from the Studio for Electroacoustic Music (SeaM) and Max Neupert (Medial Environments). Partners in San Diego are Prof. Miller Puckette (Computer Music), Prof. Katharina Rosenberger (Music) and Prof. Shahrokh Yadegari (Theatre and Dance). Telematic classes will allow students from both faculties to work together. Classes will take place in Weimar in the evening, mid-morning in San Diego. The cooperation is funded by the German Academic Exchange Service (DAAD).

===German description===
Die Wahrnehmung von Raum durch verräumlichten Klang, kann durch Klangquellen beeinflusst werden, welche sich in ihrer Qualität und Quantität unterscheiden. In diesem Projekt werden wir untersuchen, auf welche Art wir die Erfahrung von Raum durch den Klang verändern, erweitern oder verbessern können. Das Ergebnis kann beispielsweise eine elektroakustische Komposition, eine Simulation einer räumlichen Wahrnehmung, klangliche Architektur oder ein Bühnenbild als virtuelle oder performative Umgebung sein.

Dieses Projekt ist der Beginn einer langfristigen Zusammenarbeit zwischen der Bauhaus-Universität und der Universität von Kalifornien in San Diego. Partner aus Weimar sind Prof. Robin Minard und Ludger Hennig vom Studio für Elektoakustische Musik (SeaM) und Max Neupert (Gestaltung medialer Umgebungen). Partner aus San Diego sind Prof. Miller Puckette (Computermusik), Prof. Katharina Rosenberger (Musik) und Prof. Shahrokh Yadegari (Theater und Tanz). Gemeinsamer Unterricht mit einer Videoverbindung wird es den Studierenden beider Universitäten ermöglichen, zusammen zu arbeiten. Der Unterricht wird in Weimar am Abend und vormittags in San Diego stattfinden. Die Zusammenarbeit wird vom Deutschen Akademischen Austauschdienst (DAAD) gefördert.

==Werk/Fachmodule==
We recommend the Werk/Fachmodul [[GMU:Dataflow II]] and/or Ludger Hennigs soundscapes class along with this Project module.

==Assignments==
# [[/Making connection/]] due 04-22
# [[/Mingling sounds/]] due 04-29
# [[/Textualize ideas/]] due 05-06
# [[/Proposing concepts/]] due 05-13

==Evaluation==
Active participation, presentation, artistic examination, documentation, edits in the wiki.

==Participants==
===Weimar===
* [[/Rico/]]
* [[/Alex/]]
* [[/Alice/]]
* [[/Jonas/]]
* [[/Andre/]]
* [[/Paul/]]
* [[/Ben/]]
* [[/Ludwigberger/]]
* [[/TimH/]]
* [[/Dorian/]]
* [[/Clemens/]]
* [[/Ives/]]
* [[/Cornelio/]]
* [[/Johannes/]]

* [[/Max/]] (you may use this as a template for your self-introduction)

===San Diego===
* [[/Brendan Bernhardt Gaffney/]]
* [[/Kevin/]]
* [[/Melanie/]]
* [[/Jeffrey/]]
* [[/Bo/]]
* [[/Andy/]]
* [[/Jamilah/]]
* [[/Marcelo/]]
* [[/Ryan Welsh/]]
* [[/ElisabetCurbelo/]]
* [[/Joe Cantrell/]]
* [[/czyskows/]]
* [[/NickDrashner/]]

* [[/miller/]]
* [[/Shahrokh/]]
* [[/CarolineMiller/]]

==Collaborative Projects==

==Syllabus==
ISO Standard: MONTH/DAY
# 04/01 Only in San Diego (Easter Monday is holiday in Germany; Robin, Ludger and Max join via Skype/Google+ Hangout) faculty presentations about technical means and/or artistic issues. Introduction to the wiki.
# 04/08 Only in San Diego – faculty presentations continued. Miller - Rasberry Pi as an audio and video platform. Shahrokh - Mugic protocol; video walls
# 04/15 First joint class
# 04/22 Robin, Ludger and Max are in San Diego
# 04/29
# 05/06
# 05/13
# 05/20
# 05/27 Only in Weimar (Memorial day in the U.S.)
# 06/03
# 06/10
# 06/17
# 06/24
# 07/01

==Literature==
* Föllmer, Golo: Netzmusik, Wolke Verlag ISBN 3936000336
* LaBelle, Brandon: Background Noise ISBN 9780826418456
* LaBelle, Brandon: Site of Sound: Or Architecture and the Ear ISBN 978-0982743904
* Minard, Robin: Silent Music ISBN 978-3933257130
* Minard, Robin: Sound Installation Art
* Leitner, Bernard: Sound:Space ISBN 978-3893224449

Pd books:
{{Template:PdBooks}}

==Links==
* [https://groups.google.com/forum/#!forum/buw-ucsd-class Google Group BUW-UCSD-class]
* [https://puredata.info/docs/raspberry-pi Pure Data on the Raspberry Pi]

===Sending data over the network===
* [[OSC]]
* netsend/netreceive, netserver/netclient. In Pd look at <tt>mrpeach</tt> and <tt>iemnet libraries</tt>
* [http://ivl.calit2.net/wiki/index.php/StreamingGraphics Mugic]

===Sending Audio and Video over the Internet===
* [[wikipedia:Audio Video Bridging]] AVB is a set of standards for audio and video transmission by the IEEE

====Intended for Communcation====
* [http://www.skype.com Skype] [[File:Icon newtux 16x16.png]] [[File:Icon android 16x16.png]] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]]
* [https://tools.google.com/dlpage/hangoutplugin Google+ Hangout] [[File:Icon newtux 16x16.png]] [[File:Icon android 16x16.png]] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]] (Seems to work best in Chome/Chromium)
* [http://www.oovoo.com ooVoo] [[File:Icon android 16x16.png]] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]]
* [http://www.voxox.com voxox] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]]
* [http://line.naver.jp/en LINE] [[File:Icon android 16x16.png]] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]]
* [http://www.teamviewer.com TeamViewer] [[File:Icon newtux 16x16.png]] [[File:Icon android 16x16.png]] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]]
* [http://www.teamspeak.com TeamSpeak] [[File:Icon newtux 16x16.png]] [[File:Icon android 16x16.png]] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]]

Teleconferencing
* [http://www.polycom.com Polycom] [[File:Icon windows8 16x16.png]] System available in Weimar
* [http://www.radvision.com/Products/Video-Conference-Systems Radvision Scopia] [[File:Icon windows8 16x16.png]]
* [http://www.lifesize.com Livesize] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]] System available in San Diego

Unidirectional only (aka streaming)
* [http://giss.tv Global Independent Streaming Support], [http://giss.tv/wiki/index.php/Main_Page G.I.S.S wiki]
* [http://www.ustream.tv Ustream]
* [http://www.justin.tv justin.tv]
* [http://www.shoutcast.com/ shoutcast] also as vst plugin availlable

====Intended for Performance/Creative Use====
* [http://code.sat.qc.ca/redmine/projects/scenic/wiki/Scenic_fr Scenic] Audio and video in high quality, as well as MIDI [[File:Icon newtux 16x16.png]]
* [http://code.google.com/p/jacktrip JackTrip] [[File:Icon newtux 16x16.png]] [[File:Icon apple 16x16.png]] a network extension for [http://jackaudio.org/ Jack Audio Connection Kit] [[File:Icon newtux 16x16.png]] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]]
* [http://gstreamer.freedesktop.org GStreamer] and bindings for Pd: [http://umlaeute.mur.at/Members/zmoelnig/projects/pdgst PdGst] [[File:Icon newtux 16x16.png]]
* netsend~ for Max/MSP and Pd: [http://www.nullmedium.de/dev/netsend~ Olaf Matthes' Original Version] [[File:Icon newtux 16x16.png]] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]], [http://www.olivierguillerminet.com/portfolio/netsend Olivier Guillerminet's/Remu's Fork] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]]
* [http://code.google.com/p/streaming-audio Streaming Audio Manager (SAM)] by [https://ccrma.stanford.edu/~danielsm/research.html Michelle Daniels] [[File:Icon newtux 16x16.png]] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]]

===Performing Remotely===
* [http://www.netpd.org NetPd]
* [http://at.or.at/serendipd SerendiPd] collaborative patching

EKK:LoFi Sounds in HiFi Spaces

2013-04-29T18:36:24Z

Ludwigberger: /* Collaborative Projects */

[[:Category:Projektmodul|Projektmodul]] 
''Lecturers:'' [[Robin Minard]], [[/miller|Miller Puckette]], Katharina Rosenberger, [[/Shahrokh|Shahrokh Yadegari]], [[Ludger Hennig]], [[Max Neupert]] 
''Credits:'' 18 [[ECTS]], 16 [[SWS]] 
''Date:'' Monday, 18:00 until 21:30 h (due to the time difference to San Diego) 
''Venue:'' [[Coudraystraße 13a]], SeaM Werkstattstudio 
''First meeting:'' 15.04.2013

==Description==
The sensation of space through spatialized sound may be influenced by sources that differ in their quality and quantity. Within this project, we will investigate ways to modify, expand or augment how space can be experienced through sound. The outcome may be, for instance, an electroacoustic composition, a simulation of spatial perception, sonic architecture or a set-design as a virtual or performative environment.

This project is the beginning of a long-term cooperation between the Bauhaus-Universität Weimar and the University of California in San Diego. Partners in Weimar are Prof. Robin Minard and Ludger Hennig from the Studio for Electroacoustic Music (SeaM) and Max Neupert (Medial Environments). Partners in San Diego are Prof. Miller Puckette (Computer Music), Prof. Katharina Rosenberger (Music) and Prof. Shahrokh Yadegari (Theatre and Dance). Telematic classes will allow students from both faculties to work together. Classes will take place in Weimar in the evening, mid-morning in San Diego. The cooperation is funded by the German Academic Exchange Service (DAAD).

===German description===
Die Wahrnehmung von Raum durch verräumlichten Klang, kann durch Klangquellen beeinflusst werden, welche sich in ihrer Qualität und Quantität unterscheiden. In diesem Projekt werden wir untersuchen, auf welche Art wir die Erfahrung von Raum durch den Klang verändern, erweitern oder verbessern können. Das Ergebnis kann beispielsweise eine elektroakustische Komposition, eine Simulation einer räumlichen Wahrnehmung, klangliche Architektur oder ein Bühnenbild als virtuelle oder performative Umgebung sein.

Dieses Projekt ist der Beginn einer langfristigen Zusammenarbeit zwischen der Bauhaus-Universität und der Universität von Kalifornien in San Diego. Partner aus Weimar sind Prof. Robin Minard und Ludger Hennig vom Studio für Elektoakustische Musik (SeaM) und Max Neupert (Gestaltung medialer Umgebungen). Partner aus San Diego sind Prof. Miller Puckette (Computermusik), Prof. Katharina Rosenberger (Musik) und Prof. Shahrokh Yadegari (Theater und Tanz). Gemeinsamer Unterricht mit einer Videoverbindung wird es den Studierenden beider Universitäten ermöglichen, zusammen zu arbeiten. Der Unterricht wird in Weimar am Abend und vormittags in San Diego stattfinden. Die Zusammenarbeit wird vom Deutschen Akademischen Austauschdienst (DAAD) gefördert.

==Werk/Fachmodule==
We recommend the Werk/Fachmodul [[GMU:Dataflow II]] and/or Ludger Hennigs soundscapes class along with this Project module.

==Assignments==
# [[/Making connection/]] due 04-22
# [[/Mingling sounds/]] due 04-29
# [[/Textualize ideas/]] due 05-06
# [[/Proposing concepts/]] due 05-13

==Evaluation==
Active participation, presentation, artistic examination, documentation, edits in the wiki.

==Participants==
===Weimar===
* [[/Rico/]]
* [[/Alex/]]
* [[/Alice/]]
* [[/Jonas/]]
* [[/Andre/]]
* [[/Paul/]]
* [[/Ben/]]
* [[/Ludwigberger/]]
* [[/TimH/]]
* [[/Dorian/]]
* [[/Clemens/]]
* [[/Ives/]]
* [[/Cornelio/]]
* [[/Johannes/]]

* [[/Max/]] (you may use this as a template for your self-introduction)

===San Diego===
* [[/Brendan Bernhardt Gaffney/]]
* [[/Kevin/]]
* [[/Melanie/]]
* [[/Jeffrey/]]
* [[/Bo/]]
* [[/Andy/]]
* [[/Jamilah/]]
* [[/Marcelo/]]
* [[/Ryan Welsh/]]
* [[/ElisabetCurbelo/]]
* [[/Joe Cantrell/]]
* [[/czyskows/]]
* [[/NickDrashner/]]

* [[/miller/]]
* [[/Shahrokh/]]
* [[/CarolineMiller/]]

==Collaborative Projects==

===Wind transfer===

====Idea====
The idea is to transmit wind from San Diego to Weimar and vice versa. The wind would be analyzed at one side via anemometers (wind sensors) and reproduced at the other side via computer fans. We want to trasnmit not only the speed, but also the direction of the wind (e.g. due "octophonic" positioning of the fans). Sound aspects of the fans/wind should also be considered.

====Possibilities of collaboration====
* transmitting wind data
* developing a collective installation

====Participants====
Team Weimar:
* [[/Cornelio/]]
* [[/Jonas/]]
* [[/Ludwigberger/]]

==Syllabus==
ISO Standard: MONTH/DAY
# 04/01 Only in San Diego (Easter Monday is holiday in Germany; Robin, Ludger and Max join via Skype/Google+ Hangout) faculty presentations about technical means and/or artistic issues. Introduction to the wiki.
# 04/08 Only in San Diego – faculty presentations continued. Miller - Rasberry Pi as an audio and video platform. Shahrokh - Mugic protocol; video walls
# 04/15 First joint class
# 04/22 Robin, Ludger and Max are in San Diego
# 04/29
# 05/06
# 05/13
# 05/20
# 05/27 Only in Weimar (Memorial day in the U.S.)
# 06/03
# 06/10
# 06/17
# 06/24
# 07/01

==Literature==
* Föllmer, Golo: Netzmusik, Wolke Verlag ISBN 3936000336
* LaBelle, Brandon: Background Noise ISBN 9780826418456
* LaBelle, Brandon: Site of Sound: Or Architecture and the Ear ISBN 978-0982743904
* Minard, Robin: Silent Music ISBN 978-3933257130
* Minard, Robin: Sound Installation Art
* Leitner, Bernard: Sound:Space ISBN 978-3893224449

Pd books:
{{Template:PdBooks}}

==Links==
* [https://groups.google.com/forum/#!forum/buw-ucsd-class Google Group BUW-UCSD-class]
* [https://puredata.info/docs/raspberry-pi Pure Data on the Raspberry Pi]

===Sending data over the network===
* [[OSC]]
* netsend/netreceive, netserver/netclient. In Pd look at <tt>mrpeach</tt> and <tt>iemnet libraries</tt>
* [http://ivl.calit2.net/wiki/index.php/StreamingGraphics Mugic]

===Sending Audio and Video over the Internet===
* [[wikipedia:Audio Video Bridging]] AVB is a set of standards for audio and video transmission by the IEEE

====Intended for Communcation====
* [http://www.skype.com Skype] [[File:Icon newtux 16x16.png]] [[File:Icon android 16x16.png]] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]]
* [https://tools.google.com/dlpage/hangoutplugin Google+ Hangout] [[File:Icon newtux 16x16.png]] [[File:Icon android 16x16.png]] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]] (Seems to work best in Chome/Chromium)
* [http://www.oovoo.com ooVoo] [[File:Icon android 16x16.png]] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]]
* [http://www.voxox.com voxox] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]]
* [http://line.naver.jp/en LINE] [[File:Icon android 16x16.png]] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]]
* [http://www.teamviewer.com TeamViewer] [[File:Icon newtux 16x16.png]] [[File:Icon android 16x16.png]] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]]
* [http://www.teamspeak.com TeamSpeak] [[File:Icon newtux 16x16.png]] [[File:Icon android 16x16.png]] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]]

Teleconferencing
* [http://www.polycom.com Polycom] [[File:Icon windows8 16x16.png]] System available in Weimar
* [http://www.radvision.com/Products/Video-Conference-Systems Radvision Scopia] [[File:Icon windows8 16x16.png]]
* [http://www.lifesize.com Livesize] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]] System available in San Diego

Unidirectional only (aka streaming)
* [http://giss.tv Global Independent Streaming Support], [http://giss.tv/wiki/index.php/Main_Page G.I.S.S wiki]
* [http://www.ustream.tv Ustream]
* [http://www.justin.tv justin.tv]
* [http://www.shoutcast.com/ shoutcast] also as vst plugin availlable

====Intended for Performance/Creative Use====
* [http://code.sat.qc.ca/redmine/projects/scenic/wiki/Scenic_fr Scenic] Audio and video in high quality, as well as MIDI [[File:Icon newtux 16x16.png]]
* [http://code.google.com/p/jacktrip JackTrip] [[File:Icon newtux 16x16.png]] [[File:Icon apple 16x16.png]] a network extension for [http://jackaudio.org/ Jack Audio Connection Kit] [[File:Icon newtux 16x16.png]] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]]
* [http://gstreamer.freedesktop.org GStreamer] and bindings for Pd: [http://umlaeute.mur.at/Members/zmoelnig/projects/pdgst PdGst] [[File:Icon newtux 16x16.png]]
* netsend~ for Max/MSP and Pd: [http://www.nullmedium.de/dev/netsend~ Olaf Matthes' Original Version] [[File:Icon newtux 16x16.png]] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]], [http://www.olivierguillerminet.com/portfolio/netsend Olivier Guillerminet's/Remu's Fork] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]]
* [http://code.google.com/p/streaming-audio Streaming Audio Manager (SAM)] by [https://ccrma.stanford.edu/~danielsm/research.html Michelle Daniels] [[File:Icon newtux 16x16.png]] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]]

===Performing Remotely===
* [http://www.netpd.org NetPd]
* [http://at.or.at/serendipd SerendiPd] collaborative patching

EKK:LoFi Sounds in HiFi Spaces/Mingling sounds/Ludwig Jeffrey

2013-04-29T13:19:38Z

Ludwigberger: /* Q3. How does an instrument through which sound is transmitted shape our expectation and the perception of it (loudspeaker, telephone, alarm-clock), in other words, what if the expectation is not met, what impact can this have on our perception? */

==Q1. How does the sentence “The medium is the message” by Marshall McLuhan applies to your practice? Comment on this quote in the context of your own work and in regards to this transcontinental collaboration, etc.==

Some points we talked about together:

* The internet-conversations show how the medium changes or way of communicating - we do things we wouldn't normally do (wave our hands etc.)

* Every medium provides a singular approach to reality. In a skype conference our two separated rooms find somehow together and we accept the medium as a our environment.

* We have different approaches in our work: When Jeffrey does Live Engineering, he tries to build a immersive environment that suggests what you hear is what happens on stage (even though the audience could never tell what really happens on the stage). In Ludwigs [https://soundcloud.com/ludwigberger/1959-1 work], he reflects about the medium of sound recording and brakes the illusion of contiunity.

==Q2. American sound artist Bill Fontana made several pieces in which he transfers sound from one location to another. How does this locational switch change our understanding of a the space(s) in question? What new aspects of a sonic environment might emerge? What happens to our perception of a location once it is stripped from its original sounds and these are replaced by sounds from another location?==

First, we think the quality of the sounds being transfer from one place to another is really important for the listener, if the sounds can be reproduce without any distortion and playback in a n appropriate volume, the listener will have a lot of reference points to determine whether these sounds are from the real environment or cleverly played in this space. On the other hand, if the sound quality not that good listener will lose most of the reference point, and make judgement by using few points. Therefore, it's easy to let the listener make a misjudgment in the environment with poor sound quality. But once the sound sender took all of the reference points, and process the sound that the listener will much easy to accept these pre-prepared sound as the real sound in the space.

For example, during our conversation I can hear some birds sound from Ludwig's place, then he move the camera to the window want to show me the birds in the woods, I still hear the bird singing but I just can't see any birds in the screen.

==Q3. How does an instrument through which sound is transmitted shape our expectation and the perception of it (loudspeaker, telephone, alarm-clock), in other words, what if the expectation is not met, what impact can this have on our perception?==

Depending on the medium, we have different expectations concerning time and space: When you hear sounds through a telephone, you expect them to happen all at another place, but at the same time. When you hear sounds through a loudspeaker, you expect them to be recorded at another place at another time (if you don't see a sound source). This changes our perception: we have more distance to it, as a reproduced sound can be reproduced again and doesn't provoke a physical reaction. This is based on experience: The first cinema audience panicked seeing a [http://www.youtube.com/watch?v=1dgLEDdFddk train arriving].

==Videos==
We choice the train station as our theme, we shoot those video in San Diego Old Town Transit Center and Weimar Train Station. We take the door open moment as our reference point then switch the audio from each other.

San Diego + Weimar mix
<videoflash type="youtube">f0lo5yxya4E|500|280</videoflash>

Weimar + San Diego mix
<videoflash type="youtube">pbqpB9k-Bas|500|280</videoflash>

EKK:LoFi Sounds in HiFi Spaces/Mingling sounds/Ludwig Jeffrey

2013-04-29T13:06:16Z

Ludwigberger: /* Q1. How does the sentence “The medium is the message” by Marshall McLuhan applies to your practice? Comment on this quote in the context of your own work and in regards to this transcontinental collaboration, etc. */

==Q1. How does the sentence “The medium is the message” by Marshall McLuhan applies to your practice? Comment on this quote in the context of your own work and in regards to this transcontinental collaboration, etc.==

Some points we talked about together:

* The internet-conversations show how the medium changes or way of communicating - we do things we wouldn't normally do (wave our hands etc.)

* Every medium provides a singular approach to reality. In a skype conference our two separated rooms find somehow together and we accept the medium as a our environment.

* We have different approaches in our work: When Jeffrey does Live Engineering, he tries to build a immersive environment that suggests what you hear is what happens on stage (even though the audience could never tell what really happens on the stage). In Ludwigs [https://soundcloud.com/ludwigberger/1959-1 work], he reflects about the medium of sound recording and brakes the illusion of contiunity.

==Q2. American sound artist Bill Fontana made several pieces in which he transfers sound from one location to another. How does this locational switch change our understanding of a the space(s) in question? What new aspects of a sonic environment might emerge? What happens to our perception of a location once it is stripped from its original sounds and these are replaced by sounds from another location?==

First, we think the quality of the sounds being transfer from one place to another is really important for the listener, if the sounds can be reproduce without any distortion and playback in a n appropriate volume, the listener will have a lot of reference points to determine whether these sounds are from the real environment or cleverly played in this space. On the other hand, if the sound quality not that good listener will lose most of the reference point, and make judgement by using few points. Therefore, it's easy to let the listener make a misjudgment in the environment with poor sound quality. But once the sound sender took all of the reference points, and process the sound that the listener will much easy to accept these pre-prepared sound as the real sound in the space.

For example, during our conversation I can hear some birds sound from Ludwig's place, then he move the camera to the window want to show me the birds in the woods, I still hear the bird singing but I just can't see any birds in the screen.

==Q3. How does an instrument through which sound is transmitted shape our expectation and the perception of it (loudspeaker, telephone, alarm-clock), in other words, what if the expectation is not met, what impact can this have on our perception?==

==Videos==
We choice the train station as our theme, we shoot those video in San Diego Old Town Transit Center and Weimar Train Station. We take the door open moment as our reference point then switch the audio from each other.

San Diego + Weimar mix
<videoflash type="youtube">f0lo5yxya4E|500|280</videoflash>

Weimar + San Diego mix
<videoflash type="youtube">pbqpB9k-Bas|500|280</videoflash>

EKK:LoFi Sounds in HiFi Spaces/Ludwigberger

2013-04-22T12:50:15Z

Ludwigberger:

[[File:Ludwig-Berger-Portrait--008kleinswquadr.jpg|thumb]]

I study electroacoustic composition under the direction of Robin Minard at the Franz Liszt School of Music in Weimar. Before, I studied musicology, art history and literature in Eichstätt-Ingolstadt University (Germany). While studying there I began composing music for film and theatre.
You can find my website [http://www.ludwigberger.com here].

skype name: ludwigberger

==Interests==
I'm interested in acousmatic/radiophonic works, but also in theatre and installations.

==Projet idea: "Wind tunnel"==
I'd like to work on a installation that "transports" wind in realtime via subsonic frequencies.
The idea would be to install in every place a microphone which is streamed with a low-pass filter under 20 Hz into loudspeakers in the other continent. Instead of hearing a sound, a movement should be seen. This movement could again stimulate a object (e.g. with strings) and create a sound.

===Collaboration===
* working on online low-frequency sound transmission (compression would be an issue)
* finding appropriate loudspeakers and amplifiers
* developing sound objects

===Realization===
At the end of the semester, a installation with a "Wind tunnel" between San Diego and Weimar could be realized. (This could be also interesting in combination with the rain and weather station ideas).

==Platforms==
OS X

EKK:LoFi Sounds in HiFi Spaces/Making connection/TeamViewer

2013-04-22T10:09:03Z

Ludwigberger: /* Examples */

==Analysis of TeamViewer==
Ludwig and Cornelius from Weimar and Brendan from UCSD worked to analyze the TeamViewer teleconferencing software.

Our approach was simply to first attempt a more traditional, conference like discussion over the software, discussing its merits, features and usability. This allowed us to evaluate the functionality of the application as intended. Connection to the application was made through both Mac OSX and iOS.

After investigating the base functionality of the software, we attempted to "break" or "misuse" the software to create musically interesting sounds with no outside processing beyond mic positioning and volume. This allowed us to evaluate the potential of the software for our interests, as an aleatoric source of sound and telematic platform for music performance.

==The Software==

[[File:teamViewer.png|thumb|The TeamViewer logo.]]

TeamViewer is a teleconferencing software, geared towards setting up "meetings" between remote users (up to 25 participants), with an emphasis on presentation and screen sharing. The software's most significant features relate to the interactivity between a displayed screen and users, with several levels of participation (audio only, video only, etc.) selectable for different members of a meeting. It also supports large numbers of present users, and generates unique meetings with invitations and private ids.

===Setup, configuration and usability===
Intricate, defective and not intuitive.
* We had several problems with the account validation and login
* One can't easily find people without their exact Alias
* To start a meeting you have to create an ID and mail this number
* The start preferences are questionable (i.e. in the meeting the screensharing turns on automatically)
* iOS doesn't support video

===Sound Control===

[[File:teamViewerAudio.png|thumb|The audio settings within TeamViewer.]]

The control available in TeamViewer for audio is limited, but has a few important features. First, it has a variable volume, separate from that of the internal mic level control built into the OSX operating system. More interestingly, the application includes a variable noise gate, with an associated volume meter, allowing a user to easily select a threshold for a noise gate. Outside this relatively noise threshold (which appears to act as a simple gate with slightly ramped amplitude crossfade when cutting in and out) there is only a selection of input and output destinations.

===Quality of Transmission===

The immediate impression of the quality of video and audio transmission was poor. The video never quite worked (stayed frozen through most of the session) and the audio cut in and out quite a bit, with significant bit-rate reduction effects. One feature that did work quite well was the screen-sharing capabilities, which allowed us to compare our methods for recording and testing the audio latency.

Sound trip latency varied, but the clearest measured data (as our audio was generally quite poor) resulted in 590 ms roundtrip latency. This software is therefore incapable of supporting any interactive performance beyond cue-less improvisation.

===Subjective experience===

It was very difficult to start a meeting and communicate. It was a relief to switch to skype at the end.

==Musical Uses==

While the quality of transmission is quite bad, the ability to eliminate or heighten the noise threshold of the transmitted audio, coupled with the bit-rate reduction and lossy connection made for interesting musical experimentation.

As stated above, the latency prevents this software from use in actual interactive situations, but allows for meaningful (if limited) control of transmitted feedback loops. These controls, along with the simple parameters of mic placement, type and volume and speaker placement, type and volume allowed for an interesting sound space. While decidedly bright and noisy, larger musical forms and aims could be followed with some experience.

===Examples===
Here is an example of the sound quality during the feedback experiments, as directly recorded without any processing or filtering in San Diego:

'''Transmission recorded in San Diego'''
<flashmp3 id="exampleSD">exampleSD.mp3</flashmp3>

 
And here an example of the sound quality of Brendan normally speaking, recorded in Weimar: 
'''Transmission recorded in Weimar''' 
<flashmp3 id="TeamViewerSpeech.mp3">TeamViewerSpeech.mp3</flashmp3>

===Composed Piece===

The piece below contains two sections, using the recorded sounds that occurred over the course of the session. They have been stitched together. Each side of the transmission (here in San Diego and Weimar) recordings of the transmitted audio were rearranged and replaced into 45 second mono clips. These clips were sent off the to other locale, where it was heard and reacted to with other sounds from the session. Each locale is panned to one or the other side (San Diego L, Weimar R) resulting in a two part, binaural piece lasting 1'30".

<flashmp3 id="MakingConnection(Brendan-Cornelius-Ludwig).mp3">MakingConnection(Brendan-Cornelius-Ludwig).mp3</flashmp3>

===Musical Conclusions===

While useless as a telematic performance tool, the software did yield very interesting results due to its lossy and inconsistent transmission. These could be learned and controlled with some experience and understanding of the software's functionality. After this investigation, there seems potential for some piece of loudspeaker music, especially concerned with the uses and themes provided by the topic of telematic performance and its inherent issues (which are highlighted by this software).

EKK:LoFi Sounds in HiFi Spaces/Making connection/TeamViewer

2013-04-22T10:06:40Z

Ludwigberger: /* Examples */

==Analysis of TeamViewer==
Ludwig and Cornelius from Weimar and Brendan from UCSD worked to analyze the TeamViewer teleconferencing software.

Our approach was simply to first attempt a more traditional, conference like discussion over the software, discussing its merits, features and usability. This allowed us to evaluate the functionality of the application as intended. Connection to the application was made through both Mac OSX and iOS.

After investigating the base functionality of the software, we attempted to "break" or "misuse" the software to create musically interesting sounds with no outside processing beyond mic positioning and volume. This allowed us to evaluate the potential of the software for our interests, as an aleatoric source of sound and telematic platform for music performance.

==The Software==

[[File:teamViewer.png|thumb|The TeamViewer logo.]]

TeamViewer is a teleconferencing software, geared towards setting up "meetings" between remote users (up to 25 participants), with an emphasis on presentation and screen sharing. The software's most significant features relate to the interactivity between a displayed screen and users, with several levels of participation (audio only, video only, etc.) selectable for different members of a meeting. It also supports large numbers of present users, and generates unique meetings with invitations and private ids.

===Setup, configuration and usability===
Intricate, defective and not intuitive.
* We had several problems with the account validation and login
* One can't easily find people without their exact Alias
* To start a meeting you have to create an ID and mail this number
* The start preferences are questionable (i.e. in the meeting the screensharing turns on automatically)
* iOS doesn't support video

===Sound Control===

[[File:teamViewerAudio.png|thumb|The audio settings within TeamViewer.]]

The control available in TeamViewer for audio is limited, but has a few important features. First, it has a variable volume, separate from that of the internal mic level control built into the OSX operating system. More interestingly, the application includes a variable noise gate, with an associated volume meter, allowing a user to easily select a threshold for a noise gate. Outside this relatively noise threshold (which appears to act as a simple gate with slightly ramped amplitude crossfade when cutting in and out) there is only a selection of input and output destinations.

===Quality of Transmission===

The immediate impression of the quality of video and audio transmission was poor. The video never quite worked (stayed frozen through most of the session) and the audio cut in and out quite a bit, with significant bit-rate reduction effects. One feature that did work quite well was the screen-sharing capabilities, which allowed us to compare our methods for recording and testing the audio latency.

Sound trip latency varied, but the clearest measured data (as our audio was generally quite poor) resulted in 590 ms roundtrip latency. This software is therefore incapable of supporting any interactive performance beyond cue-less improvisation.

===Subjective experience===

It was very difficult to start a meeting and communicate. It was a relief to switch to skype at the end.

==Musical Uses==

While the quality of transmission is quite bad, the ability to eliminate or heighten the noise threshold of the transmitted audio, coupled with the bit-rate reduction and lossy connection made for interesting musical experimentation.

As stated above, the latency prevents this software from use in actual interactive situations, but allows for meaningful (if limited) control of transmitted feedback loops. These controls, along with the simple parameters of mic placement, type and volume and speaker placement, type and volume allowed for an interesting sound space. While decidedly bright and noisy, larger musical forms and aims could be followed with some experience.

===Examples===
Here is an example of the sound quality during the feedback experiments, as directly recorded without any processing or filtering in San Diego:

Transmission recorded in San Diego
<flashmp3 id="exampleSD">exampleSD.mp3</flashmp3>

 
And here an example of the sound quality of Brendan normally speaking, recorded in Weimar:

Transmission recorded in Weimar
<flashmp3 id="TeamViewerSpeech.mp3">TeamViewerSpeech.mp3</flashmp3>

===Composed Piece===

The piece below contains two sections, using the recorded sounds that occurred over the course of the session. They have been stitched together. Each side of the transmission (here in San Diego and Weimar) recordings of the transmitted audio were rearranged and replaced into 45 second mono clips. These clips were sent off the to other locale, where it was heard and reacted to with other sounds from the session. Each locale is panned to one or the other side (San Diego L, Weimar R) resulting in a two part, binaural piece lasting 1'30".

<flashmp3 id="MakingConnection(Brendan-Cornelius-Ludwig).mp3">MakingConnection(Brendan-Cornelius-Ludwig).mp3</flashmp3>

===Musical Conclusions===

While useless as a telematic performance tool, the software did yield very interesting results due to its lossy and inconsistent transmission. These could be learned and controlled with some experience and understanding of the software's functionality. After this investigation, there seems potential for some piece of loudspeaker music, especially concerned with the uses and themes provided by the topic of telematic performance and its inherent issues (which are highlighted by this software).

EKK:LoFi Sounds in HiFi Spaces/Making connection/TeamViewer

2013-04-22T10:05:43Z

Ludwigberger: /* Examples */

==Analysis of TeamViewer==
Ludwig and Cornelius from Weimar and Brendan from UCSD worked to analyze the TeamViewer teleconferencing software.

Our approach was simply to first attempt a more traditional, conference like discussion over the software, discussing its merits, features and usability. This allowed us to evaluate the functionality of the application as intended. Connection to the application was made through both Mac OSX and iOS.

After investigating the base functionality of the software, we attempted to "break" or "misuse" the software to create musically interesting sounds with no outside processing beyond mic positioning and volume. This allowed us to evaluate the potential of the software for our interests, as an aleatoric source of sound and telematic platform for music performance.

==The Software==

[[File:teamViewer.png|thumb|The TeamViewer logo.]]

TeamViewer is a teleconferencing software, geared towards setting up "meetings" between remote users (up to 25 participants), with an emphasis on presentation and screen sharing. The software's most significant features relate to the interactivity between a displayed screen and users, with several levels of participation (audio only, video only, etc.) selectable for different members of a meeting. It also supports large numbers of present users, and generates unique meetings with invitations and private ids.

===Setup, configuration and usability===
Intricate, defective and not intuitive.
* We had several problems with the account validation and login
* One can't easily find people without their exact Alias
* To start a meeting you have to create an ID and mail this number
* The start preferences are questionable (i.e. in the meeting the screensharing turns on automatically)
* iOS doesn't support video

===Sound Control===

[[File:teamViewerAudio.png|thumb|The audio settings within TeamViewer.]]

The control available in TeamViewer for audio is limited, but has a few important features. First, it has a variable volume, separate from that of the internal mic level control built into the OSX operating system. More interestingly, the application includes a variable noise gate, with an associated volume meter, allowing a user to easily select a threshold for a noise gate. Outside this relatively noise threshold (which appears to act as a simple gate with slightly ramped amplitude crossfade when cutting in and out) there is only a selection of input and output destinations.

===Quality of Transmission===

The immediate impression of the quality of video and audio transmission was poor. The video never quite worked (stayed frozen through most of the session) and the audio cut in and out quite a bit, with significant bit-rate reduction effects. One feature that did work quite well was the screen-sharing capabilities, which allowed us to compare our methods for recording and testing the audio latency.

Sound trip latency varied, but the clearest measured data (as our audio was generally quite poor) resulted in 590 ms roundtrip latency. This software is therefore incapable of supporting any interactive performance beyond cue-less improvisation.

===Subjective experience===

It was very difficult to start a meeting and communicate. It was a relief to switch to skype at the end.

==Musical Uses==

While the quality of transmission is quite bad, the ability to eliminate or heighten the noise threshold of the transmitted audio, coupled with the bit-rate reduction and lossy connection made for interesting musical experimentation.

As stated above, the latency prevents this software from use in actual interactive situations, but allows for meaningful (if limited) control of transmitted feedback loops. These controls, along with the simple parameters of mic placement, type and volume and speaker placement, type and volume allowed for an interesting sound space. While decidedly bright and noisy, larger musical forms and aims could be followed with some experience.

===Examples===
Here is an example of the sound quality during the feedback experiments, as directly recorded without any processing or filtering in San Diego:

Transmission recorded in San Diego
<flashmp3 id="exampleSD">exampleSD.mp3</flashmp3>

 
And here an example of the sound quality of Brendan normally speaking, recorded in Weimar:

'''Transmission recorded in Weimar'''
<flashmp3 id="TeamViewerSpeech.mp3">TeamViewerSpeech.mp3</flashmp3>

===Composed Piece===

The piece below contains two sections, using the recorded sounds that occurred over the course of the session. They have been stitched together. Each side of the transmission (here in San Diego and Weimar) recordings of the transmitted audio were rearranged and replaced into 45 second mono clips. These clips were sent off the to other locale, where it was heard and reacted to with other sounds from the session. Each locale is panned to one or the other side (San Diego L, Weimar R) resulting in a two part, binaural piece lasting 1'30".

<flashmp3 id="MakingConnection(Brendan-Cornelius-Ludwig).mp3">MakingConnection(Brendan-Cornelius-Ludwig).mp3</flashmp3>

===Musical Conclusions===

While useless as a telematic performance tool, the software did yield very interesting results due to its lossy and inconsistent transmission. These could be learned and controlled with some experience and understanding of the software's functionality. After this investigation, there seems potential for some piece of loudspeaker music, especially concerned with the uses and themes provided by the topic of telematic performance and its inherent issues (which are highlighted by this software).

EKK:LoFi Sounds in HiFi Spaces/Making connection/TeamViewer

2013-04-22T10:04:16Z

Ludwigberger: /* Examples */

==Analysis of TeamViewer==
Ludwig and Cornelius from Weimar and Brendan from UCSD worked to analyze the TeamViewer teleconferencing software.

Our approach was simply to first attempt a more traditional, conference like discussion over the software, discussing its merits, features and usability. This allowed us to evaluate the functionality of the application as intended. Connection to the application was made through both Mac OSX and iOS.

After investigating the base functionality of the software, we attempted to "break" or "misuse" the software to create musically interesting sounds with no outside processing beyond mic positioning and volume. This allowed us to evaluate the potential of the software for our interests, as an aleatoric source of sound and telematic platform for music performance.

==The Software==

[[File:teamViewer.png|thumb|The TeamViewer logo.]]

TeamViewer is a teleconferencing software, geared towards setting up "meetings" between remote users (up to 25 participants), with an emphasis on presentation and screen sharing. The software's most significant features relate to the interactivity between a displayed screen and users, with several levels of participation (audio only, video only, etc.) selectable for different members of a meeting. It also supports large numbers of present users, and generates unique meetings with invitations and private ids.

===Setup, configuration and usability===
Intricate, defective and not intuitive.
* We had several problems with the account validation and login
* One can't easily find people without their exact Alias
* To start a meeting you have to create an ID and mail this number
* The start preferences are questionable (i.e. in the meeting the screensharing turns on automatically)
* iOS doesn't support video

===Sound Control===

[[File:teamViewerAudio.png|thumb|The audio settings within TeamViewer.]]

The control available in TeamViewer for audio is limited, but has a few important features. First, it has a variable volume, separate from that of the internal mic level control built into the OSX operating system. More interestingly, the application includes a variable noise gate, with an associated volume meter, allowing a user to easily select a threshold for a noise gate. Outside this relatively noise threshold (which appears to act as a simple gate with slightly ramped amplitude crossfade when cutting in and out) there is only a selection of input and output destinations.

===Quality of Transmission===

The immediate impression of the quality of video and audio transmission was poor. The video never quite worked (stayed frozen through most of the session) and the audio cut in and out quite a bit, with significant bit-rate reduction effects. One feature that did work quite well was the screen-sharing capabilities, which allowed us to compare our methods for recording and testing the audio latency.

Sound trip latency varied, but the clearest measured data (as our audio was generally quite poor) resulted in 590 ms roundtrip latency. This software is therefore incapable of supporting any interactive performance beyond cue-less improvisation.

===Subjective experience===

It was very difficult to start a meeting and communicate. It was a relief to switch to skype at the end.

==Musical Uses==

While the quality of transmission is quite bad, the ability to eliminate or heighten the noise threshold of the transmitted audio, coupled with the bit-rate reduction and lossy connection made for interesting musical experimentation.

As stated above, the latency prevents this software from use in actual interactive situations, but allows for meaningful (if limited) control of transmitted feedback loops. These controls, along with the simple parameters of mic placement, type and volume and speaker placement, type and volume allowed for an interesting sound space. While decidedly bright and noisy, larger musical forms and aims could be followed with some experience.

===Examples===
Here is an example of the sound quality during the feedback experiments, as directly recorded without any processing or filtering in San Diego:

Transmission recorded in San Diego
<flashmp3 id="exampleSD">exampleSD.mp3</flashmp3>

And here an example of the sound quality of Brendan normally speaking, recorded in Weimar:

Transmission recorded in Weimar
<flashmp3 id="TeamViewerSpeech.mp3">TeamViewerSpeech.mp3</flashmp3>

===Composed Piece===

The piece below contains two sections, using the recorded sounds that occurred over the course of the session. They have been stitched together. Each side of the transmission (here in San Diego and Weimar) recordings of the transmitted audio were rearranged and replaced into 45 second mono clips. These clips were sent off the to other locale, where it was heard and reacted to with other sounds from the session. Each locale is panned to one or the other side (San Diego L, Weimar R) resulting in a two part, binaural piece lasting 1'30".

<flashmp3 id="MakingConnection(Brendan-Cornelius-Ludwig).mp3">MakingConnection(Brendan-Cornelius-Ludwig).mp3</flashmp3>

===Musical Conclusions===

While useless as a telematic performance tool, the software did yield very interesting results due to its lossy and inconsistent transmission. These could be learned and controlled with some experience and understanding of the software's functionality. After this investigation, there seems potential for some piece of loudspeaker music, especially concerned with the uses and themes provided by the topic of telematic performance and its inherent issues (which are highlighted by this software).

EKK:LoFi Sounds in HiFi Spaces/Making connection/TeamViewer

2013-04-22T10:03:27Z

Ludwigberger: /* Examples */

==Analysis of TeamViewer==
Ludwig and Cornelius from Weimar and Brendan from UCSD worked to analyze the TeamViewer teleconferencing software.

Our approach was simply to first attempt a more traditional, conference like discussion over the software, discussing its merits, features and usability. This allowed us to evaluate the functionality of the application as intended. Connection to the application was made through both Mac OSX and iOS.

After investigating the base functionality of the software, we attempted to "break" or "misuse" the software to create musically interesting sounds with no outside processing beyond mic positioning and volume. This allowed us to evaluate the potential of the software for our interests, as an aleatoric source of sound and telematic platform for music performance.

==The Software==

[[File:teamViewer.png|thumb|The TeamViewer logo.]]

TeamViewer is a teleconferencing software, geared towards setting up "meetings" between remote users (up to 25 participants), with an emphasis on presentation and screen sharing. The software's most significant features relate to the interactivity between a displayed screen and users, with several levels of participation (audio only, video only, etc.) selectable for different members of a meeting. It also supports large numbers of present users, and generates unique meetings with invitations and private ids.

===Setup, configuration and usability===
Intricate, defective and not intuitive.
* We had several problems with the account validation and login
* One can't easily find people without their exact Alias
* To start a meeting you have to create an ID and mail this number
* The start preferences are questionable (i.e. in the meeting the screensharing turns on automatically)
* iOS doesn't support video

===Sound Control===

[[File:teamViewerAudio.png|thumb|The audio settings within TeamViewer.]]

The control available in TeamViewer for audio is limited, but has a few important features. First, it has a variable volume, separate from that of the internal mic level control built into the OSX operating system. More interestingly, the application includes a variable noise gate, with an associated volume meter, allowing a user to easily select a threshold for a noise gate. Outside this relatively noise threshold (which appears to act as a simple gate with slightly ramped amplitude crossfade when cutting in and out) there is only a selection of input and output destinations.

===Quality of Transmission===

The immediate impression of the quality of video and audio transmission was poor. The video never quite worked (stayed frozen through most of the session) and the audio cut in and out quite a bit, with significant bit-rate reduction effects. One feature that did work quite well was the screen-sharing capabilities, which allowed us to compare our methods for recording and testing the audio latency.

Sound trip latency varied, but the clearest measured data (as our audio was generally quite poor) resulted in 590 ms roundtrip latency. This software is therefore incapable of supporting any interactive performance beyond cue-less improvisation.

===Subjective experience===

It was very difficult to start a meeting and communicate. It was a relief to switch to skype at the end.

==Musical Uses==

While the quality of transmission is quite bad, the ability to eliminate or heighten the noise threshold of the transmitted audio, coupled with the bit-rate reduction and lossy connection made for interesting musical experimentation.

As stated above, the latency prevents this software from use in actual interactive situations, but allows for meaningful (if limited) control of transmitted feedback loops. These controls, along with the simple parameters of mic placement, type and volume and speaker placement, type and volume allowed for an interesting sound space. While decidedly bright and noisy, larger musical forms and aims could be followed with some experience.

===Examples===
*Here is an example of the sound quality during the feedback experiments, as directly recorded without any processing or filtering in San Diego:

Transmission recorded in San Diego
<flashmp3 id="exampleSD">exampleSD.mp3</flashmp3>

*And here an example of the sound quality of Brendan normally speaking, recorded in Weimar:
<flashmp3 id="TeamViewerSpeech.mp3">TeamViewerSpeech.mp3</flashmp3>

===Composed Piece===

The piece below contains two sections, using the recorded sounds that occurred over the course of the session. They have been stitched together. Each side of the transmission (here in San Diego and Weimar) recordings of the transmitted audio were rearranged and replaced into 45 second mono clips. These clips were sent off the to other locale, where it was heard and reacted to with other sounds from the session. Each locale is panned to one or the other side (San Diego L, Weimar R) resulting in a two part, binaural piece lasting 1'30".

<flashmp3 id="MakingConnection(Brendan-Cornelius-Ludwig).mp3">MakingConnection(Brendan-Cornelius-Ludwig).mp3</flashmp3>

===Musical Conclusions===

While useless as a telematic performance tool, the software did yield very interesting results due to its lossy and inconsistent transmission. These could be learned and controlled with some experience and understanding of the software's functionality. After this investigation, there seems potential for some piece of loudspeaker music, especially concerned with the uses and themes provided by the topic of telematic performance and its inherent issues (which are highlighted by this software).

EKK:LoFi Sounds in HiFi Spaces/Making connection/TeamViewer

2013-04-22T10:02:50Z

Ludwigberger: /* Example */

==Analysis of TeamViewer==
Ludwig and Cornelius from Weimar and Brendan from UCSD worked to analyze the TeamViewer teleconferencing software.

Our approach was simply to first attempt a more traditional, conference like discussion over the software, discussing its merits, features and usability. This allowed us to evaluate the functionality of the application as intended. Connection to the application was made through both Mac OSX and iOS.

After investigating the base functionality of the software, we attempted to "break" or "misuse" the software to create musically interesting sounds with no outside processing beyond mic positioning and volume. This allowed us to evaluate the potential of the software for our interests, as an aleatoric source of sound and telematic platform for music performance.

==The Software==

[[File:teamViewer.png|thumb|The TeamViewer logo.]]

TeamViewer is a teleconferencing software, geared towards setting up "meetings" between remote users (up to 25 participants), with an emphasis on presentation and screen sharing. The software's most significant features relate to the interactivity between a displayed screen and users, with several levels of participation (audio only, video only, etc.) selectable for different members of a meeting. It also supports large numbers of present users, and generates unique meetings with invitations and private ids.

===Setup, configuration and usability===
Intricate, defective and not intuitive.
* We had several problems with the account validation and login
* One can't easily find people without their exact Alias
* To start a meeting you have to create an ID and mail this number
* The start preferences are questionable (i.e. in the meeting the screensharing turns on automatically)
* iOS doesn't support video

===Sound Control===

[[File:teamViewerAudio.png|thumb|The audio settings within TeamViewer.]]

The control available in TeamViewer for audio is limited, but has a few important features. First, it has a variable volume, separate from that of the internal mic level control built into the OSX operating system. More interestingly, the application includes a variable noise gate, with an associated volume meter, allowing a user to easily select a threshold for a noise gate. Outside this relatively noise threshold (which appears to act as a simple gate with slightly ramped amplitude crossfade when cutting in and out) there is only a selection of input and output destinations.

===Quality of Transmission===

The immediate impression of the quality of video and audio transmission was poor. The video never quite worked (stayed frozen through most of the session) and the audio cut in and out quite a bit, with significant bit-rate reduction effects. One feature that did work quite well was the screen-sharing capabilities, which allowed us to compare our methods for recording and testing the audio latency.

Sound trip latency varied, but the clearest measured data (as our audio was generally quite poor) resulted in 590 ms roundtrip latency. This software is therefore incapable of supporting any interactive performance beyond cue-less improvisation.

===Subjective experience===

It was very difficult to start a meeting and communicate. It was a relief to switch to skype at the end.

==Musical Uses==

While the quality of transmission is quite bad, the ability to eliminate or heighten the noise threshold of the transmitted audio, coupled with the bit-rate reduction and lossy connection made for interesting musical experimentation.

As stated above, the latency prevents this software from use in actual interactive situations, but allows for meaningful (if limited) control of transmitted feedback loops. These controls, along with the simple parameters of mic placement, type and volume and speaker placement, type and volume allowed for an interesting sound space. While decidedly bright and noisy, larger musical forms and aims could be followed with some experience.

===Examples===
Here is an example of the sound quality during the feedback experiments, as directly recorded without any processing or filtering in San Diego:

Transmission recorded in San Diego
<flashmp3 id="exampleSD">exampleSD.mp3</flashmp3>

And here an example of the sound quality of Brendan normally speaking, recorded in Weimar:

<flashmp3 id="TeamViewerSpeech.mp3">TeamViewerSpeech.mp3</flashmp3>

===Composed Piece===

The piece below contains two sections, using the recorded sounds that occurred over the course of the session. They have been stitched together. Each side of the transmission (here in San Diego and Weimar) recordings of the transmitted audio were rearranged and replaced into 45 second mono clips. These clips were sent off the to other locale, where it was heard and reacted to with other sounds from the session. Each locale is panned to one or the other side (San Diego L, Weimar R) resulting in a two part, binaural piece lasting 1'30".

<flashmp3 id="MakingConnection(Brendan-Cornelius-Ludwig).mp3">MakingConnection(Brendan-Cornelius-Ludwig).mp3</flashmp3>

===Musical Conclusions===

While useless as a telematic performance tool, the software did yield very interesting results due to its lossy and inconsistent transmission. These could be learned and controlled with some experience and understanding of the software's functionality. After this investigation, there seems potential for some piece of loudspeaker music, especially concerned with the uses and themes provided by the topic of telematic performance and its inherent issues (which are highlighted by this software).

File:TeamViewerSpeech.mp3

2013-04-22T10:01:18Z

Ludwigberger:

== Summary ==

== Copyright status: ==

== Licensing ==
{{self|c}}
== Source: ==

EKK:LoFi Sounds in HiFi Spaces/Making connection/TeamViewer

2013-04-22T10:00:31Z

Ludwigberger: /* The Software */

==Analysis of TeamViewer==
Ludwig and Cornelius from Weimar and Brendan from UCSD worked to analyze the TeamViewer teleconferencing software.

Our approach was simply to first attempt a more traditional, conference like discussion over the software, discussing its merits, features and usability. This allowed us to evaluate the functionality of the application as intended. Connection to the application was made through both Mac OSX and iOS.

After investigating the base functionality of the software, we attempted to "break" or "misuse" the software to create musically interesting sounds with no outside processing beyond mic positioning and volume. This allowed us to evaluate the potential of the software for our interests, as an aleatoric source of sound and telematic platform for music performance.

==The Software==

[[File:teamViewer.png|thumb|The TeamViewer logo.]]

TeamViewer is a teleconferencing software, geared towards setting up "meetings" between remote users (up to 25 participants), with an emphasis on presentation and screen sharing. The software's most significant features relate to the interactivity between a displayed screen and users, with several levels of participation (audio only, video only, etc.) selectable for different members of a meeting. It also supports large numbers of present users, and generates unique meetings with invitations and private ids.

===Setup, configuration and usability===
Intricate, defective and not intuitive.
* We had several problems with the account validation and login
* One can't easily find people without their exact Alias
* To start a meeting you have to create an ID and mail this number
* The start preferences are questionable (i.e. in the meeting the screensharing turns on automatically)
* iOS doesn't support video

===Sound Control===

[[File:teamViewerAudio.png|thumb|The audio settings within TeamViewer.]]

The control available in TeamViewer for audio is limited, but has a few important features. First, it has a variable volume, separate from that of the internal mic level control built into the OSX operating system. More interestingly, the application includes a variable noise gate, with an associated volume meter, allowing a user to easily select a threshold for a noise gate. Outside this relatively noise threshold (which appears to act as a simple gate with slightly ramped amplitude crossfade when cutting in and out) there is only a selection of input and output destinations.

===Quality of Transmission===

The immediate impression of the quality of video and audio transmission was poor. The video never quite worked (stayed frozen through most of the session) and the audio cut in and out quite a bit, with significant bit-rate reduction effects. One feature that did work quite well was the screen-sharing capabilities, which allowed us to compare our methods for recording and testing the audio latency.

Sound trip latency varied, but the clearest measured data (as our audio was generally quite poor) resulted in 590 ms roundtrip latency. This software is therefore incapable of supporting any interactive performance beyond cue-less improvisation.

===Subjective experience===

It was very difficult to start a meeting and communicate. It was a relief to switch to skype at the end.

==Musical Uses==

While the quality of transmission is quite bad, the ability to eliminate or heighten the noise threshold of the transmitted audio, coupled with the bit-rate reduction and lossy connection made for interesting musical experimentation.

As stated above, the latency prevents this software from use in actual interactive situations, but allows for meaningful (if limited) control of transmitted feedback loops. These controls, along with the simple parameters of mic placement, type and volume and speaker placement, type and volume allowed for an interesting sound space. While decidedly bright and noisy, larger musical forms and aims could be followed with some experience.

===Example===
Here is an example of the sound quality during the feedback experiments, as directly recorded without any processing or filtering in San Diego:

Transmission recorded in San Diego
<flashmp3 id="exampleSD">exampleSD.mp3</flashmp3>

===Composed Piece===

The piece below contains two sections, using the recorded sounds that occurred over the course of the session. They have been stitched together. Each side of the transmission (here in San Diego and Weimar) recordings of the transmitted audio were rearranged and replaced into 45 second mono clips. These clips were sent off the to other locale, where it was heard and reacted to with other sounds from the session. Each locale is panned to one or the other side (San Diego L, Weimar R) resulting in a two part, binaural piece lasting 1'30".

<flashmp3 id="MakingConnection(Brendan-Cornelius-Ludwig).mp3">MakingConnection(Brendan-Cornelius-Ludwig).mp3</flashmp3>

===Musical Conclusions===

While useless as a telematic performance tool, the software did yield very interesting results due to its lossy and inconsistent transmission. These could be learned and controlled with some experience and understanding of the software's functionality. After this investigation, there seems potential for some piece of loudspeaker music, especially concerned with the uses and themes provided by the topic of telematic performance and its inherent issues (which are highlighted by this software).

EKK:LoFi Sounds in HiFi Spaces/Making connection/TeamViewer

2013-04-22T09:57:28Z

Ludwigberger: /* Setup, configuration and usability */

==Analysis of TeamViewer==
Ludwig and Cornelius from Weimar and Brendan from UCSD worked to analyze the TeamViewer teleconferencing software.

Our approach was simply to first attempt a more traditional, conference like discussion over the software, discussing its merits, features and usability. This allowed us to evaluate the functionality of the application as intended. Connection to the application was made through both Mac OSX and iOS.

After investigating the base functionality of the software, we attempted to "break" or "misuse" the software to create musically interesting sounds with no outside processing beyond mic positioning and volume. This allowed us to evaluate the potential of the software for our interests, as an aleatoric source of sound and telematic platform for music performance.

==The Software==

[[File:teamViewer.png|thumb|The TeamViewer logo.]]

TeamViewer is a teleconferencing software, geared towards setting up "meetings" between remote users (up to 25 participants), with an emphasis on presentation and screen sharing. The software's most significant features relate to the interactivity between a displayed screen and users, with several levels of participation (audio only, video only, etc.) selectable for different members of a meeting. It also supports large numbers of present users, and generates unique meetings with invitations and private ids.

===Setup, configuration and usability===
Intricate, defective and not intuitive.
* We had several problems with the account validation
* One can't easily find people without their exact Alias
* To start a meeting you have to create an ID and mail this number
* The start preferences are questionable (i.e. in the meeting the screensharing turns on automatically)
* iOS doesn't support video

===Sound Control===

[[File:teamViewerAudio.png|thumb|The audio settings within TeamViewer.]]

The control available in TeamViewer for audio is limited, but has a few important features. First, it has a variable volume, separate from that of the internal mic level control built into the OSX operating system. More interestingly, the application includes a variable noise gate, with an associated volume meter, allowing a user to easily select a threshold for a noise gate. Outside this relatively noise threshold (which appears to act as a simple gate with slightly ramped amplitude crossfade when cutting in and out) there is only a selection of input and output destinations.

===Quality of Transmission===

The immediate impression of the quality of video and audio transmission was poor. The video never quite worked (stayed frozen through most of the session) and the audio cut in and out quite a bit, with significant bit-rate reduction effects. One feature that did work quite well was the screen-sharing capabilities, which allowed us to compare our methods for recording and testing the audio latency.

Sound trip latency varied, but the clearest measured data (as our audio was generally quite poor) resulted in 590 ms roundtrip latency. This software is therefore incapable of supporting any interactive performance beyond cue-less improvisation.

===Subjective experience===

It was very difficult to start a meeting and communicate. It was a relief to switch to skype at the end.

==Musical Uses==

While the quality of transmission is quite bad, the ability to eliminate or heighten the noise threshold of the transmitted audio, coupled with the bit-rate reduction and lossy connection made for interesting musical experimentation.

As stated above, the latency prevents this software from use in actual interactive situations, but allows for meaningful (if limited) control of transmitted feedback loops. These controls, along with the simple parameters of mic placement, type and volume and speaker placement, type and volume allowed for an interesting sound space. While decidedly bright and noisy, larger musical forms and aims could be followed with some experience.

===Example===
Here is an example of the sound quality during the feedback experiments, as directly recorded without any processing or filtering in San Diego:

Transmission recorded in San Diego
<flashmp3 id="exampleSD">exampleSD.mp3</flashmp3>

===Composed Piece===

The piece below contains two sections, using the recorded sounds that occurred over the course of the session. They have been stitched together. Each side of the transmission (here in San Diego and Weimar) recordings of the transmitted audio were rearranged and replaced into 45 second mono clips. These clips were sent off the to other locale, where it was heard and reacted to with other sounds from the session. Each locale is panned to one or the other side (San Diego L, Weimar R) resulting in a two part, binaural piece lasting 1'30".

<flashmp3 id="MakingConnection(Brendan-Cornelius-Ludwig).mp3">MakingConnection(Brendan-Cornelius-Ludwig).mp3</flashmp3>

===Musical Conclusions===

While useless as a telematic performance tool, the software did yield very interesting results due to its lossy and inconsistent transmission. These could be learned and controlled with some experience and understanding of the software's functionality. After this investigation, there seems potential for some piece of loudspeaker music, especially concerned with the uses and themes provided by the topic of telematic performance and its inherent issues (which are highlighted by this software).

EKK:LoFi Sounds in HiFi Spaces/Making connection/TeamViewer

2013-04-22T09:54:30Z

Ludwigberger: /* The Software */

==Analysis of TeamViewer==
Ludwig and Cornelius from Weimar and Brendan from UCSD worked to analyze the TeamViewer teleconferencing software.

Our approach was simply to first attempt a more traditional, conference like discussion over the software, discussing its merits, features and usability. This allowed us to evaluate the functionality of the application as intended. Connection to the application was made through both Mac OSX and iOS.

After investigating the base functionality of the software, we attempted to "break" or "misuse" the software to create musically interesting sounds with no outside processing beyond mic positioning and volume. This allowed us to evaluate the potential of the software for our interests, as an aleatoric source of sound and telematic platform for music performance.

==The Software==

[[File:teamViewer.png|thumb|The TeamViewer logo.]]

TeamViewer is a teleconferencing software, geared towards setting up "meetings" between remote users (up to 25 participants), with an emphasis on presentation and screen sharing. The software's most significant features relate to the interactivity between a displayed screen and users, with several levels of participation (audio only, video only, etc.) selectable for different members of a meeting. It also supports large numbers of present users, and generates unique meetings with invitations and private ids.

===Setup, configuration and usability===
Intricate, defective and not intuitive.
- One can't easily find people without their exact Alias
- To start a meeting you have to create an ID and mail this number
- The start preferences are questionable (i.e. in the meeting the screensharing turns on automatically)
- iOS doesn't support video

===Sound Control===

[[File:teamViewerAudio.png|thumb|The audio settings within TeamViewer.]]

The control available in TeamViewer for audio is limited, but has a few important features. First, it has a variable volume, separate from that of the internal mic level control built into the OSX operating system. More interestingly, the application includes a variable noise gate, with an associated volume meter, allowing a user to easily select a threshold for a noise gate. Outside this relatively noise threshold (which appears to act as a simple gate with slightly ramped amplitude crossfade when cutting in and out) there is only a selection of input and output destinations.

===Quality of Transmission===

The immediate impression of the quality of video and audio transmission was poor. The video never quite worked (stayed frozen through most of the session) and the audio cut in and out quite a bit, with significant bit-rate reduction effects. One feature that did work quite well was the screen-sharing capabilities, which allowed us to compare our methods for recording and testing the audio latency.

Sound trip latency varied, but the clearest measured data (as our audio was generally quite poor) resulted in 590 ms roundtrip latency. This software is therefore incapable of supporting any interactive performance beyond cue-less improvisation.

===Subjective experience===

It was very difficult to start a meeting and communicate. It was a relief to switch to skype at the end.

==Musical Uses==

While the quality of transmission is quite bad, the ability to eliminate or heighten the noise threshold of the transmitted audio, coupled with the bit-rate reduction and lossy connection made for interesting musical experimentation.

As stated above, the latency prevents this software from use in actual interactive situations, but allows for meaningful (if limited) control of transmitted feedback loops. These controls, along with the simple parameters of mic placement, type and volume and speaker placement, type and volume allowed for an interesting sound space. While decidedly bright and noisy, larger musical forms and aims could be followed with some experience.

===Example===
Here is an example of the sound quality during the feedback experiments, as directly recorded without any processing or filtering in San Diego:

Transmission recorded in San Diego
<flashmp3 id="exampleSD">exampleSD.mp3</flashmp3>

===Composed Piece===

The piece below contains two sections, using the recorded sounds that occurred over the course of the session. They have been stitched together. Each side of the transmission (here in San Diego and Weimar) recordings of the transmitted audio were rearranged and replaced into 45 second mono clips. These clips were sent off the to other locale, where it was heard and reacted to with other sounds from the session. Each locale is panned to one or the other side (San Diego L, Weimar R) resulting in a two part, binaural piece lasting 1'30".

<flashmp3 id="MakingConnection(Brendan-Cornelius-Ludwig).mp3">MakingConnection(Brendan-Cornelius-Ludwig).mp3</flashmp3>

===Musical Conclusions===

While useless as a telematic performance tool, the software did yield very interesting results due to its lossy and inconsistent transmission. These could be learned and controlled with some experience and understanding of the software's functionality. After this investigation, there seems potential for some piece of loudspeaker music, especially concerned with the uses and themes provided by the topic of telematic performance and its inherent issues (which are highlighted by this software).

EKK:LoFi Sounds in HiFi Spaces/Making connection/TeamViewer

2013-04-22T09:48:53Z

Ludwigberger: /* The Software */

==Analysis of TeamViewer==
Ludwig and Cornelius from Weimar and Brendan from UCSD worked to analyze the TeamViewer teleconferencing software.

Our approach was simply to first attempt a more traditional, conference like discussion over the software, discussing its merits, features and usability. This allowed us to evaluate the functionality of the application as intended. Connection to the application was made through both Mac OSX and iOS.

After investigating the base functionality of the software, we attempted to "break" or "misuse" the software to create musically interesting sounds with no outside processing beyond mic positioning and volume. This allowed us to evaluate the potential of the software for our interests, as an aleatoric source of sound and telematic platform for music performance.

==The Software==

[[File:teamViewer.png|thumb|The TeamViewer logo.]]

TeamViewer is a teleconferencing software, geared towards setting up "meetings" between remote users (up to 25 participants), with an emphasis on presentation and screen sharing. The software's most significant features relate to the interactivity between a displayed screen and users, with several levels of participation (audio only, video only, etc.) selectable for different members of a meeting. It also supports large numbers of present users, and generates unique meetings with invitations and private ids.

===Setup, configuration and usability===
Easy to install, but not intuitive to use:
- One can't easily find people without their exact Alias
- To start a meeting you have to create an ID and mail this number
- The start preferences are questionable (i.e. in the meeting the screensharing turns on automatically)
- iOS doesn't support video

===Sound Control===

[[File:teamViewerAudio.png|thumb|The audio settings within TeamViewer.]]

The control available in TeamViewer for audio is limited, but has a few important features. First, it has a variable volume, separate from that of the internal mic level control built into the OSX operating system. More interestingly, the application includes a variable noise gate, with an associated volume meter, allowing a user to easily select a threshold for a noise gate. Outside this relatively noise threshold (which appears to act as a simple gate with slightly ramped amplitude crossfade when cutting in and out) there is only a selection of input and output destinations.

===Quality of Transmission===

The immediate impression of the quality of video and audio transmission was poor. The video never quite worked (stayed frozen through most of the session) and the audio cut in and out quite a bit, with significant bit-rate reduction effects. One feature that did work quite well was the screen-sharing capabilities, which allowed us to compare our methods for recording and testing the audio latency.

Sound trip latency varied, but the clearest measured data (as our audio was generally quite poor) resulted in 590 ms roundtrip latency. This software is therefore incapable of supporting any interactive performance beyond cue-less improvisation.

===Subjective experience===
It was very difficult to start a meeting and communicate. It was a relief to switch to skype at the end.

==Musical Uses==

While the quality of transmission is quite bad, the ability to eliminate or heighten the noise threshold of the transmitted audio, coupled with the bit-rate reduction and lossy connection made for interesting musical experimentation.

As stated above, the latency prevents this software from use in actual interactive situations, but allows for meaningful (if limited) control of transmitted feedback loops. These controls, along with the simple parameters of mic placement, type and volume and speaker placement, type and volume allowed for an interesting sound space. While decidedly bright and noisy, larger musical forms and aims could be followed with some experience.

===Example===
Here is an example of the sound quality during the feedback experiments, as directly recorded without any processing or filtering in San Diego:

Transmission recorded in San Diego
<flashmp3 id="exampleSD">exampleSD.mp3</flashmp3>

===Composed Piece===

The piece below contains two sections, using the recorded sounds that occurred over the course of the session. They have been stitched together. Each side of the transmission (here in San Diego and Weimar) recordings of the transmitted audio were rearranged and replaced into 45 second mono clips. These clips were sent off the to other locale, where it was heard and reacted to with other sounds from the session. Each locale is panned to one or the other side (San Diego L, Weimar R) resulting in a two part, binaural piece lasting 1'30".

<flashmp3 id="MakingConnection(Brendan-Cornelius-Ludwig).mp3">MakingConnection(Brendan-Cornelius-Ludwig).mp3</flashmp3>

===Musical Conclusions===

While useless as a telematic performance tool, the software did yield very interesting results due to its lossy and inconsistent transmission. These could be learned and controlled with some experience and understanding of the software's functionality. After this investigation, there seems potential for some piece of loudspeaker music, especially concerned with the uses and themes provided by the topic of telematic performance and its inherent issues (which are highlighted by this software).

EKK:LoFi Sounds in HiFi Spaces/Making connection/TeamViewer

2013-04-22T09:30:20Z

Ludwigberger: /* The Software */

==Analysis of TeamViewer==
Ludwig and Cornelius from Weimar and Brendan from UCSD worked to analyze the TeamViewer teleconferencing software.

Our approach was simply to first attempt a more traditional, conference like discussion over the software, discussing its merits, features and usability. This allowed us to evaluate the functionality of the application as intended. Connection to the application was made through both Mac OSX and iOS.

After investigating the base functionality of the software, we attempted to "break" or "misuse" the software to create musically interesting sounds with no outside processing beyond mic positioning and volume. This allowed us to evaluate the potential of the software for our interests, as an aleatoric source of sound and telematic platform for music performance.

==The Software==

[[File:teamViewer.png|thumb|The TeamViewer logo.]]

TeamViewer is a teleconferencing software, geared towards setting up "meetings" between remote users (up to 25 participants), with an emphasis on presentation and screen sharing. The software's most significant features relate to the interactivity between a displayed screen and users, with several levels of participation (audio only, video only, etc.) selectable for different members of a meeting. It also supports large numbers of present users, and generates unique meetings with invitations and private ids.

===Sound Control===

[[File:teamViewerAudio.png|thumb|The audio settings within TeamViewer.]]

The control available in TeamViewer for audio is limited, but has a few important features. First, it has a variable volume, separate from that of the internal mic level control built into the OSX operating system. More interestingly, the application includes a variable noise gate, with an associated volume meter, allowing a user to easily select a threshold for a noise gate. Outside this relatively noise threshold (which appears to act as a simple gate with slightly ramped amplitude crossfade when cutting in and out) there is only a selection of input and output destinations.

===Quality of Transmission===

The immediate impression of the quality of video and audio transmission was poor. The video never quite worked (stayed frozen through most of the session) and the audio cut in and out quite a bit, with significant bit-rate reduction effects. One feature that did work quite well was the screen-sharing capabilities, which allowed us to compare our methods for recording and testing the audio latency.

Sound trip latency varied, but the clearest measured data (as our audio was generally quite poor) resulted in 590 ms roundtrip latency. This software is therefore incapable of supporting any interactive performance beyond cue-less improvisation.

==Musical Uses==

While the quality of transmission is quite bad, the ability to eliminate or heighten the noise threshold of the transmitted audio, coupled with the bit-rate reduction and lossy connection made for interesting musical experimentation.

As stated above, the latency prevents this software from use in actual interactive situations, but allows for meaningful (if limited) control of transmitted feedback loops. These controls, along with the simple parameters of mic placement, type and volume and speaker placement, type and volume allowed for an interesting sound space. While decidedly bright and noisy, larger musical forms and aims could be followed with some experience.

===Example===
Here is an example of the sound quality during the feedback experiments, as directly recorded without any processing or filtering in San Diego:

Transmission recorded in San Diego
<flashmp3 id="exampleSD">exampleSD.mp3</flashmp3>

===Composed Piece===

The piece below contains two sections, using the recorded sounds that occurred over the course of the session. They have been stitched together. Each side of the transmission (here in San Diego and Weimar) recordings of the transmitted audio were rearranged and replaced into 45 second mono clips. These clips were sent off the to other locale, where it was heard and reacted to with other sounds from the session. Each locale is panned to one or the other side (San Diego L, Weimar R) resulting in a two part, binaural piece lasting 1'30".

<flashmp3 id="MakingConnection(Brendan-Cornelius-Ludwig).mp3">MakingConnection(Brendan-Cornelius-Ludwig).mp3</flashmp3>

===Musical Conclusions===

While useless as a telematic performance tool, the software did yield very interesting results due to its lossy and inconsistent transmission. These could be learned and controlled with some experience and understanding of the software's functionality. After this investigation, there seems potential for some piece of loudspeaker music, especially concerned with the uses and themes provided by the topic of telematic performance and its inherent issues (which are highlighted by this software).

EKK:LoFi Sounds in HiFi Spaces/Making connection

2013-04-22T09:25:25Z

Ludwigberger: /* Teams */

We randomly put you in teams to work together. In each team one student of Weimar and one from San Diego will work together. Each team will get their own communication tool assigned (from this list: [[../#Sending data over the network]] )

==Tasks==
* Assess setup, configuration and usability of the software in brief.
* Describe the subjective experience of the connection.
* Assess the qualities of the audio (and video if available) connection
** What is the roundtrip latency. Does it vary?
** What kind of filtering is applied? Can it be influenced (e.g. settings)?
** Is there compression, noise gate, feedback suppression?
** Develop techniques to measure the above, communicate standards in the group so your results are comparable.
* Prepare a 1 minute presentation (make a audiofile/or video) where you are working creatively with the restraints of the technological framework. If sound only: upload to wiki and embed as high quality .mp3 / if video upload to vimeo and embed in wiki.

==Teams==
(Weimar/San Diego)
* [[../Clemens|Clemens]]/[[../Ryan Welsh|Ryan]]: [[/JackTrip/]]
* [[../Alice|Alice]]/[[../ElisabetCurbelo|Elisabet]]: [[/Skype/]]
* [[../Ben|Ben]]/[[../Jeffrey|Jeffrey]]: [[/Google+ Hangout/]]
* [[../Andre|Andre]]/[[../Marcelo|Marcelo]]/[[../Kevin|Kevin]]: [[/ooVoo/]]
* [[../Dorian|Dorian]]/[[../Jamilah|Jamilah]]: [[/voxox/]]
* [[../Cornelio|Cornelius]]/[[../Ludwigberger|Ludwig]]/[[../Brendan Bernhardt Gaffney|Brendan]]: [[/TeamViewer/]]
* [[../Rico|Rico]]/[[../czyskows|czyskows]]: [[/Scenic/]]
* [[../Paul|Paul]]/[[../NickDrashner|Nick]]: [[/netsend~/]]
* [[../TimH|Tim]]/[[../Kevin|Kevin]]: [[/OS X Messages/FaceTime/]]
* [[../Alex|Alex]]/[[../Andy|Andy]]: [[/NetPd/]]
* [[../Jonas|Jonas]]/[[../Joe Cantrell|Joe]]: [[/TeamSpeak/]]
* [[../Ives|Ives]]/[[../Bo|Bo]]: [[/LINE/]]

If your name is missing on this list, just join any of the teams of your choice.

EKK:LoFi Sounds in HiFi Spaces/Making connection

2013-04-22T09:24:16Z

Ludwigberger: /* Teams */

We randomly put you in teams to work together. In each team one student of Weimar and one from San Diego will work together. Each team will get their own communication tool assigned (from this list: [[../#Sending data over the network]] )

==Tasks==
* Assess setup, configuration and usability of the software in brief.
* Describe the subjective experience of the connection.
* Assess the qualities of the audio (and video if available) connection
** What is the roundtrip latency. Does it vary?
** What kind of filtering is applied? Can it be influenced (e.g. settings)?
** Is there compression, noise gate, feedback suppression?
** Develop techniques to measure the above, communicate standards in the group so your results are comparable.
* Prepare a 1 minute presentation (make a audiofile/or video) where you are working creatively with the restraints of the technological framework. If sound only: upload to wiki and embed as high quality .mp3 / if video upload to vimeo and embed in wiki.

==Teams==
(Weimar/San Diego)
* [[../Clemens|Clemens]]/[[../Ryan Welsh|Ryan]]: [[/JackTrip/]]
* [[../Alice|Alice]]/[[../ElisabetCurbelo|Elisabet]]: [[/Skype/]]
* [[../Ben|Ben]]/[[../Jeffrey|Jeffrey]]: [[/Google+ Hangout/]]
* [[../Andre|Andre]]/[[../Marcelo|Marcelo]]/[[../Kevin|Kevin]]: [[/ooVoo/]]
* [[../Dorian|Dorian]]/[[../Jamilah|Jamilah]]: [[/voxox/]]
* [[../Cornelio|Cornelius]][[../Ludwigberger|Ludwig]]/[[../Brendan Bernhardt Gaffney|Brendan]]: [[/TeamViewer/]]
* [[../Rico|Rico]]/[[../czyskows|czyskows]]: [[/Scenic/]]
* [[../Paul|Paul]]/[[../NickDrashner|Nick]]: [[/netsend~/]]
* [[../TimH|Tim]]/[[../Kevin|Kevin]]: [[/OS X Messages/FaceTime/]]
* [[../Alex|Alex]]/[[../Andy|Andy]]: [[/NetPd/]]
* [[../Jonas|Jonas]]/[[../Joe Cantrell|Joe]]: [[/TeamSpeak/]]
* [[../Ives|Ives]]/[[../Bo|Bo]]: [[/LINE/]]

If your name is missing on this list, just join any of the teams of your choice.

EKK:LoFi Sounds in HiFi Spaces/Making connection/TeamViewer

2013-04-22T07:38:30Z

Ludwigberger: /* Composed Piece */

==Analysis of TeamViewer==
Ludwig and Cornelius from Weimar and Brendan from UCSD worked to analyze the TeamViewer teleconferencing software.

Our approach was simply to first attempt a more traditional, conference like discussion over the software, discussing its merits, features and usability. This allowed us to evaluate the functionality of the application as intended. Connection to the application was made through both Mac OSX and iOS.

After investigating the base functionality of the software, we attempted to "break" or "misuse" the software to create musically interesting sounds with no outside processing beyond mic positioning and volume. This allowed us to evaluate the potential of the software for our interests, as an aleatoric source of sound and telematic platform for music performance.

==The Software==

[[File:teamViewer.png|thumb|The TeamViewer logo.]]

TeamViewer is a teleconferencing software, geared towards setting up "meetings" between remote users, with an emphasis on presentation and screen sharing. The software's most significant features relate to the interactivity between a displayed screen and users, with several levels of participation (audio only, video only, etc.) selectable for different members of a meeting. It also supports large numbers of present users, and generates unique meetings with invitations and private ids.

===Sound Control===

[[File:teamViewerAudio.png|thumb|The audio settings within TeamViewer.]]

The control available in TeamViewer for audio is limited, but has a few important features. First, it has a variable volume, separate from that of the internal mic level control built into the OSX operating system. More interestingly, the application includes a variable noise gate, with an associated volume meter, allowing a user to easily select a threshold for a noise gate. Outside this relatively noise threshold (which appears to act as a simple gate with slightly ramped amplitude crossfade when cutting in and out) there is only a selection of input and output destinations.

===Quality of Transmission===

The immediate impression of the quality of video and audio transmission was poor. The video never quite worked (stayed frozen through most of the session) and the audio cut in and out quite a bit, with significant bit-rate reduction effects. One feature that did work quite well was the screen-sharing capabilities, which allowed us to compare our methods for recording and testing the audio latency.

Sound trip latency varied, but the clearest measured data (as our audio was generally quite poor) resulted in 590 ms roundtrip latency. This software is therefore incapable of supporting any interactive performance beyond cue-less improvisation.

==Musical Uses==

While the quality of transmission is quite bad, the ability to eliminate or heighten the noise threshold of the transmitted audio, coupled with the bit-rate reduction and lossy connection made for interesting musical experimentation.

As stated above, the latency prevents this software from use in actual interactive situations, but allows for meaningful (if limited) control of transmitted feedback loops. These controls, along with the simple parameters of mic placement, type and volume and speaker placement, type and volume allowed for an interesting sound space. While decidedly bright and noisy, larger musical forms and aims could be followed with some experience.

===Example===
Here is an example of the sound quality during the feedback experiments, as directly recorded without any processing or filtering in San Diego:

Transmission recorded in San Diego
<flashmp3 id="exampleSD">exampleSD.mp3</flashmp3>

===Composed Piece===

The piece below contains two sections, using the recorded sounds that occurred over the course of the session. They have been stitched together. Each side of the transmission (here in San Diego and Weimar) recordings of the transmitted audio were rearranged and replaced into 45 second mono clips. These clips were sent off the to other locale, where it was heard and reacted to with other sounds from the session. Each locale is panned to one or the other side (San Diego L, Weimar R) resulting in a two part, binaural piece lasting 1'30".

<flashmp3 id="MakingConnection(Brendan-Cornelius-Ludwig).mp3">MakingConnection(Brendan-Cornelius-Ludwig).mp3</flashmp3>

===Musical Conclusions===

While useless as a telematic performance tool, the software did yield very interesting results due to its lossy and inconsistent transmission. These could be learned and controlled with some experience and understanding of the software's functionality. After this investigation, there seems potential for some piece of loudspeaker music, especially concerned with the uses and themes provided by the topic of telematic performance and its inherent issues (which are highlighted by this software).

File:MakingConnection(Brendan-Cornelius-Ludwig).mp3

2013-04-22T07:37:55Z

Ludwigberger:

== Summary ==

== Copyright status: ==

== Licensing ==
{{self|c}}
== Source: ==

EKK:LoFi Sounds in HiFi Spaces/Making connection/TeamViewer

2013-04-22T07:31:33Z

Ludwigberger: /* Composed Piece */

==Analysis of TeamViewer==
Ludwig and Cornelius from Weimar and Brendan from UCSD worked to analyze the TeamViewer teleconferencing software.

Our approach was simply to first attempt a more traditional, conference like discussion over the software, discussing its merits, features and usability. This allowed us to evaluate the functionality of the application as intended. Connection to the application was made through both Mac OSX and iOS.

After investigating the base functionality of the software, we attempted to "break" or "misuse" the software to create musically interesting sounds with no outside processing beyond mic positioning and volume. This allowed us to evaluate the potential of the software for our interests, as an aleatoric source of sound and telematic platform for music performance.

==The Software==

[[File:teamViewer.png|thumb|The TeamViewer logo.]]

TeamViewer is a teleconferencing software, geared towards setting up "meetings" between remote users, with an emphasis on presentation and screen sharing. The software's most significant features relate to the interactivity between a displayed screen and users, with several levels of participation (audio only, video only, etc.) selectable for different members of a meeting. It also supports large numbers of present users, and generates unique meetings with invitations and private ids.

===Sound Control===

[[File:teamViewerAudio.png|thumb|The audio settings within TeamViewer.]]

The control available in TeamViewer for audio is limited, but has a few important features. First, it has a variable volume, separate from that of the internal mic level control built into the OSX operating system. More interestingly, the application includes a variable noise gate, with an associated volume meter, allowing a user to easily select a threshold for a noise gate. Outside this relatively noise threshold (which appears to act as a simple gate with slightly ramped amplitude crossfade when cutting in and out) there is only a selection of input and output destinations.

===Quality of Transmission===

The immediate impression of the quality of video and audio transmission was poor. The video never quite worked (stayed frozen through most of the session) and the audio cut in and out quite a bit, with significant bit-rate reduction effects. One feature that did work quite well was the screen-sharing capabilities, which allowed us to compare our methods for recording and testing the audio latency.

Sound trip latency varied, but the clearest measured data (as our audio was generally quite poor) resulted in 590 ms roundtrip latency. This software is therefore incapable of supporting any interactive performance beyond cue-less improvisation.

==Musical Uses==

While the quality of transmission is quite bad, the ability to eliminate or heighten the noise threshold of the transmitted audio, coupled with the bit-rate reduction and lossy connection made for interesting musical experimentation.

As stated above, the latency prevents this software from use in actual interactive situations, but allows for meaningful (if limited) control of transmitted feedback loops. These controls, along with the simple parameters of mic placement, type and volume and speaker placement, type and volume allowed for an interesting sound space. While decidedly bright and noisy, larger musical forms and aims could be followed with some experience.

===Example===
Here is an example of the sound quality during the feedback experiments, as directly recorded without any processing or filtering in San Diego:

Transmission recorded in San Diego
<flashmp3 id="exampleSD">exampleSD.mp3</flashmp3>

===Composed Piece===

The piece below contains two sections, using the recorded sounds that occurred over the course of the session. They have been stitched together. Each side of the transmission (here in San Diego and Weimar) recordings of the transmitted audio were rearranged and replaced into 45 second mono clips. These clips were sent off the to other locale, where it was heard and reacted to with other sounds from the session. Each locale is panned to one or the other side (San Diego L, Weimar R) resulting in a two part, binaural piece lasting 1'30".

<flashmp3 id="Making connection (Brendan, Cornelius, Ludwig)">Making_connection_(Brendan,_Cornelius,_Ludwig).mp3</flashmp3>

===Musical Conclusions===

While useless as a telematic performance tool, the software did yield very interesting results due to its lossy and inconsistent transmission. These could be learned and controlled with some experience and understanding of the software's functionality. After this investigation, there seems potential for some piece of loudspeaker music, especially concerned with the uses and themes provided by the topic of telematic performance and its inherent issues (which are highlighted by this software).

EKK:LoFi Sounds in HiFi Spaces/Making connection/TeamViewer

2013-04-22T07:28:49Z

Ludwigberger: /* Composed Piece */

==Analysis of TeamViewer==
Ludwig and Cornelius from Weimar and Brendan from UCSD worked to analyze the TeamViewer teleconferencing software.

Our approach was simply to first attempt a more traditional, conference like discussion over the software, discussing its merits, features and usability. This allowed us to evaluate the functionality of the application as intended. Connection to the application was made through both Mac OSX and iOS.

After investigating the base functionality of the software, we attempted to "break" or "misuse" the software to create musically interesting sounds with no outside processing beyond mic positioning and volume. This allowed us to evaluate the potential of the software for our interests, as an aleatoric source of sound and telematic platform for music performance.

==The Software==

[[File:teamViewer.png|thumb|The TeamViewer logo.]]

TeamViewer is a teleconferencing software, geared towards setting up "meetings" between remote users, with an emphasis on presentation and screen sharing. The software's most significant features relate to the interactivity between a displayed screen and users, with several levels of participation (audio only, video only, etc.) selectable for different members of a meeting. It also supports large numbers of present users, and generates unique meetings with invitations and private ids.

===Sound Control===

[[File:teamViewerAudio.png|thumb|The audio settings within TeamViewer.]]

The control available in TeamViewer for audio is limited, but has a few important features. First, it has a variable volume, separate from that of the internal mic level control built into the OSX operating system. More interestingly, the application includes a variable noise gate, with an associated volume meter, allowing a user to easily select a threshold for a noise gate. Outside this relatively noise threshold (which appears to act as a simple gate with slightly ramped amplitude crossfade when cutting in and out) there is only a selection of input and output destinations.

===Quality of Transmission===

The immediate impression of the quality of video and audio transmission was poor. The video never quite worked (stayed frozen through most of the session) and the audio cut in and out quite a bit, with significant bit-rate reduction effects. One feature that did work quite well was the screen-sharing capabilities, which allowed us to compare our methods for recording and testing the audio latency.

Sound trip latency varied, but the clearest measured data (as our audio was generally quite poor) resulted in 590 ms roundtrip latency. This software is therefore incapable of supporting any interactive performance beyond cue-less improvisation.

==Musical Uses==

While the quality of transmission is quite bad, the ability to eliminate or heighten the noise threshold of the transmitted audio, coupled with the bit-rate reduction and lossy connection made for interesting musical experimentation.

As stated above, the latency prevents this software from use in actual interactive situations, but allows for meaningful (if limited) control of transmitted feedback loops. These controls, along with the simple parameters of mic placement, type and volume and speaker placement, type and volume allowed for an interesting sound space. While decidedly bright and noisy, larger musical forms and aims could be followed with some experience.

===Example===
Here is an example of the sound quality during the feedback experiments, as directly recorded without any processing or filtering in San Diego:

Transmission recorded in San Diego
<flashmp3 id="exampleSD">exampleSD.mp3</flashmp3>

===Composed Piece===

The piece below contains two sections, using the recorded sounds that occurred over the course of the session. They have been stitched together. Each side of the transmission (here in San Diego and Weimar) recordings of the transmitted audio were rearranged and replaced into 45 second mono clips. These clips were sent off the to other locale, where it was heard and reacted to with other sounds from the session. Each locale is panned to one or the other side (San Diego L, Weimar R) resulting in a two part, binaural piece lasting 1'30".

<flashmp3 id="exampleSD">Making_connection_(Brendan,_Cornelius,_Ludwig).mp3</flashmp3>

===Musical Conclusions===

While useless as a telematic performance tool, the software did yield very interesting results due to its lossy and inconsistent transmission. These could be learned and controlled with some experience and understanding of the software's functionality. After this investigation, there seems potential for some piece of loudspeaker music, especially concerned with the uses and themes provided by the topic of telematic performance and its inherent issues (which are highlighted by this software).

EKK:LoFi Sounds in HiFi Spaces/Making connection/TeamViewer

2013-04-22T07:26:45Z

Ludwigberger: /* Composed Piece */

==Analysis of TeamViewer==
Ludwig and Cornelius from Weimar and Brendan from UCSD worked to analyze the TeamViewer teleconferencing software.

Our approach was simply to first attempt a more traditional, conference like discussion over the software, discussing its merits, features and usability. This allowed us to evaluate the functionality of the application as intended. Connection to the application was made through both Mac OSX and iOS.

After investigating the base functionality of the software, we attempted to "break" or "misuse" the software to create musically interesting sounds with no outside processing beyond mic positioning and volume. This allowed us to evaluate the potential of the software for our interests, as an aleatoric source of sound and telematic platform for music performance.

==The Software==

[[File:teamViewer.png|thumb|The TeamViewer logo.]]

TeamViewer is a teleconferencing software, geared towards setting up "meetings" between remote users, with an emphasis on presentation and screen sharing. The software's most significant features relate to the interactivity between a displayed screen and users, with several levels of participation (audio only, video only, etc.) selectable for different members of a meeting. It also supports large numbers of present users, and generates unique meetings with invitations and private ids.

===Sound Control===

[[File:teamViewerAudio.png|thumb|The audio settings within TeamViewer.]]

The control available in TeamViewer for audio is limited, but has a few important features. First, it has a variable volume, separate from that of the internal mic level control built into the OSX operating system. More interestingly, the application includes a variable noise gate, with an associated volume meter, allowing a user to easily select a threshold for a noise gate. Outside this relatively noise threshold (which appears to act as a simple gate with slightly ramped amplitude crossfade when cutting in and out) there is only a selection of input and output destinations.

===Quality of Transmission===

The immediate impression of the quality of video and audio transmission was poor. The video never quite worked (stayed frozen through most of the session) and the audio cut in and out quite a bit, with significant bit-rate reduction effects. One feature that did work quite well was the screen-sharing capabilities, which allowed us to compare our methods for recording and testing the audio latency.

Sound trip latency varied, but the clearest measured data (as our audio was generally quite poor) resulted in 590 ms roundtrip latency. This software is therefore incapable of supporting any interactive performance beyond cue-less improvisation.

==Musical Uses==

While the quality of transmission is quite bad, the ability to eliminate or heighten the noise threshold of the transmitted audio, coupled with the bit-rate reduction and lossy connection made for interesting musical experimentation.

As stated above, the latency prevents this software from use in actual interactive situations, but allows for meaningful (if limited) control of transmitted feedback loops. These controls, along with the simple parameters of mic placement, type and volume and speaker placement, type and volume allowed for an interesting sound space. While decidedly bright and noisy, larger musical forms and aims could be followed with some experience.

===Example===
Here is an example of the sound quality during the feedback experiments, as directly recorded without any processing or filtering in San Diego:

Transmission recorded in San Diego
<flashmp3 id="exampleSD">exampleSD.mp3</flashmp3>

===Composed Piece===

The piece below contains two sections, using the recorded sounds that occurred over the course of the session. They have been stitched together. Each side of the transmission (here in San Diego and Weimar) recordings of the transmitted audio were rearranged and replaced into 45 second mono clips. These clips were sent off the to other locale, where it was heard and reacted to with other sounds from the session. Each locale is panned to one or the other side, resulting in a two part, binaural piece lasting 1'30".

<flashmp3 id="exampleSD">Making_connection_(Brendan,_Cornelius,_Ludwig).mp3</flashmp3>

===Musical Conclusions===

While useless as a telematic performance tool, the software did yield very interesting results due to its lossy and inconsistent transmission. These could be learned and controlled with some experience and understanding of the software's functionality. After this investigation, there seems potential for some piece of loudspeaker music, especially concerned with the uses and themes provided by the topic of telematic performance and its inherent issues (which are highlighted by this software).

EKK:LoFi Sounds in HiFi Spaces/Making connection/TeamViewer

2013-04-22T07:26:34Z

Ludwigberger: /* Composed Piece */

==Analysis of TeamViewer==
Ludwig and Cornelius from Weimar and Brendan from UCSD worked to analyze the TeamViewer teleconferencing software.

Our approach was simply to first attempt a more traditional, conference like discussion over the software, discussing its merits, features and usability. This allowed us to evaluate the functionality of the application as intended. Connection to the application was made through both Mac OSX and iOS.

After investigating the base functionality of the software, we attempted to "break" or "misuse" the software to create musically interesting sounds with no outside processing beyond mic positioning and volume. This allowed us to evaluate the potential of the software for our interests, as an aleatoric source of sound and telematic platform for music performance.

==The Software==

[[File:teamViewer.png|thumb|The TeamViewer logo.]]

TeamViewer is a teleconferencing software, geared towards setting up "meetings" between remote users, with an emphasis on presentation and screen sharing. The software's most significant features relate to the interactivity between a displayed screen and users, with several levels of participation (audio only, video only, etc.) selectable for different members of a meeting. It also supports large numbers of present users, and generates unique meetings with invitations and private ids.

===Sound Control===

[[File:teamViewerAudio.png|thumb|The audio settings within TeamViewer.]]

The control available in TeamViewer for audio is limited, but has a few important features. First, it has a variable volume, separate from that of the internal mic level control built into the OSX operating system. More interestingly, the application includes a variable noise gate, with an associated volume meter, allowing a user to easily select a threshold for a noise gate. Outside this relatively noise threshold (which appears to act as a simple gate with slightly ramped amplitude crossfade when cutting in and out) there is only a selection of input and output destinations.

===Quality of Transmission===

The immediate impression of the quality of video and audio transmission was poor. The video never quite worked (stayed frozen through most of the session) and the audio cut in and out quite a bit, with significant bit-rate reduction effects. One feature that did work quite well was the screen-sharing capabilities, which allowed us to compare our methods for recording and testing the audio latency.

Sound trip latency varied, but the clearest measured data (as our audio was generally quite poor) resulted in 590 ms roundtrip latency. This software is therefore incapable of supporting any interactive performance beyond cue-less improvisation.

==Musical Uses==

While the quality of transmission is quite bad, the ability to eliminate or heighten the noise threshold of the transmitted audio, coupled with the bit-rate reduction and lossy connection made for interesting musical experimentation.

As stated above, the latency prevents this software from use in actual interactive situations, but allows for meaningful (if limited) control of transmitted feedback loops. These controls, along with the simple parameters of mic placement, type and volume and speaker placement, type and volume allowed for an interesting sound space. While decidedly bright and noisy, larger musical forms and aims could be followed with some experience.

===Example===
Here is an example of the sound quality during the feedback experiments, as directly recorded without any processing or filtering in San Diego:

Transmission recorded in San Diego
<flashmp3 id="exampleSD">exampleSD.mp3</flashmp3>

===Composed Piece===

The piece below contains two sections, using the recorded sounds that occurred over the course of the session. They have been stitched together. Each side of the transmission (here in San Diego and Weimar) recordings of the transmitted audio were rearranged and replaced into 45 second mono clips. These clips were sent off the to other locale, where it was heard and reacted to with other sounds from the session. Each locale is panned to one or the other side, resulting in a two part, binaural piece lasting 1'30".

<flashmp3 id="exampleSD">Making_connection_(Brendan,_Cornelius,_Ludwig).mp3</flashmp3>

===Musical Conclusions===

While useless as a telematic performance tool, the software did yield very interesting results due to its lossy and inconsistent transmission. These could be learned and controlled with some experience and understanding of the software's functionality. After this investigation, there seems potential for some piece of loudspeaker music, especially concerned with the uses and themes provided by the topic of telematic performance and its inherent issues (which are highlighted by this software).

EKK:LoFi Sounds in HiFi Spaces/Ludwigberger

2013-04-17T16:58:39Z

Ludwigberger:

EKK:LoFi Sounds in HiFi Spaces/Ludwigberger

2013-04-15T16:33:19Z

Ludwigberger: /* Platforms */

EKK:LoFi Sounds in HiFi Spaces/Ludwigberger

2013-04-15T16:33:12Z

Ludwigberger: Created page with " thumb I study electroacoustic composition under the direction of Robin Minard at the Franz Liszt School of Music in Weimar...."

EKK:LoFi Sounds in HiFi Spaces

2013-04-15T16:32:36Z

Ludwigberger: /* Weimar */

[[:Category:Projektmodul|Projektmodul]] 
''Lecturers:'' [[Robin Minard]], Miller Puckette, Katharina Rosenberger, Shahrokh Yadegari, [[Ludger Hennig]], [[Max Neupert]] 
''Credits:'' 18 [[ECTS]], 16 [[SWS]] 
''Date:'' Monday, 18:00 until 21:30 h (due to the time difference to San Diego) 
''Venue:'' [[Coudraystraße 13a]], SeaM Werkstattstudio 
''First meeting:'' 15.04.2013

==Description==
The sensation of space through spatialized sound may be influenced by sources that differ in their quality and quantity. Within this project, we will investigate ways to modify, expand or augment how space can be experienced through sound. The outcome may be, for instance, an electroacoustic composition, a simulation of spatial perception, sonic architecture or a set-design as a virtual or performative environment.

This project is the beginning of a long-term cooperation between the Bauhaus-Universität Weimar and the University of California in San Diego. Partners in Weimar are Prof. Robin Minard and Ludger Hennig from the Studio for Electroacoustic Music (SeaM) and Max Neupert (Medial Environments). Partners in San Diego are Prof. Miller Puckette (Computer Music), Prof. Katharina Rosenberger (Music) and Prof. Shahrokh Yadegari (Theatre and Dance). Telematic classes will allow students from both faculties to work together. Classes will take place in Weimar in the evening, mid-morning in San Diego. The cooperation is funded by the German Academic Exchange Service (DAAD).

===German description===
Die Wahrnehmung von Raum durch verräumlichten Klang, kann durch Klangquellen beeinflusst werden, welche sich in ihrer Qualität und Quantität unterscheiden. In diesem Projekt werden wir untersuchen, auf welche Art wir die Erfahrung von Raum durch den Klang verändern, erweitern oder verbessern können. Das Ergebnis kann beispielsweise eine elektroakustische Komposition, eine Simulation einer räumlichen Wahrnehmung, klangliche Architektur oder ein Bühnenbild als virtuelle oder performative Umgebung sein.

Dieses Projekt ist der Beginn einer langfristigen Zusammenarbeit zwischen der Bauhaus-Universität und der Universität von Kalifornien in San Diego. Partner aus Weimar sind Prof. Robin Minard und Ludger Hennig vom Studio für Elektoakustische Musik (SeaM) und Max Neupert (Gestaltung medialer Umgebungen). Partner aus San Diego sind Prof. Miller Puckette (Computermusik), Prof. Katharina Rosenberger (Musik) und Prof. Shahrokh Yadegari (Theater und Tanz). Gemeinsamer Unterricht mit einer Videoverbindung wird es den Studierenden beider Universitäten ermöglichen, zusammen zu arbeiten. Der Unterricht wird in Weimar am Abend und vormittags in San Diego stattfinden. Die Zusammenarbeit wird vom Deutschen Akademischen Austauschdienst (DAAD) gefördert.

==Werk/Fachmodule==
We recommend the Werk/Fachmodul [[GMU:Dataflow II]] along with this Project module.

==Admission requirements==
Motivation and intermediate knowledge and experience in the field of electroacoustic music.

==Registration procedure==
Registration is a bit complicated this time. It is a two step procedure. Here is how it works:

1. Send your application in one email with the Subject ''{{PAGENAME}}'' to all three receipients robin.minard@'''uni'''-weimar.de, max.neupert@'''uni'''-weimar.de and ludger.hennig@'''hfm'''-weimar.de.
It must contain the following information:
* Name, Surname
* program and semester (Studienprogramm und Fachsemester)
* matriculation number (Matrikelnummer)
* Angabe der geltenden Prüfungsordnung
* Valid email address @uni-weimar.de (no other mailing addresses will be accepted) [[SCC-Services#E-Mail|Why?]]
* A '''short''' motivation letter (I want to take part in this class because...).

2. Go to Cudraystraße 13a, Room 011 (SeaM Werkstattstudio) and write your name on the list for interviews. Please leave no gaps! Fill the list from top to bottom. Then come to your interview appointment on Monday the 15th of April 9:00 - 11:00, 13:00 - 15:00.

==Evaluation==
Active participation, presentation, artistic examination, documentation, edits in the wiki.

==Eligible participants==
Undergraduates and graduates enrolled in the Faculties of Media, Gestaltung and in the MediaArchitecture program

==Participants==
===Weimar===
* [[/Max/]] (you may use this as a template for your self-introduction)
* [[/Rico/]]
* [[/Alex/]]
* [[/Alice/]]
* [[/Jonas/]]
* [[/Andre/]]
* [[/Paul/]]
* [[/Markus/]]
* [[/Ben/]]
* [[/Ludwigberger/]]

===San Diego===
* [[/Brendan Bernhardt Gaffney/]]
* [[/Kevin/]]
* [[/Melanie/]]
* [[/Jeffrey/]]
* [[/Bo/]]
* [[/Andy/]]
* [[/Jamilah/]]
* [[/Marcelo/]]
* [[/Ryan Welsh/]]
* [[/ElisabetCurbelo/]]
* [[/CarolineMiller/]]
* [[/Joe Cantrell/]]
* [[/czyskows/]]
* [[/miller/]]
* [[/NickDrashner/]]
* [[/Shahrokh/]]

==Syllabus==
ISO Standard: MONTH/DAY
# 04/01 Only in San Diego (Easter Monday is holiday in Germany; Robin, Ludger and Max join via Skype/Google+ Hangout) faculty presentations about technical means and/or artistic issues. Introduction to the wiki.
# 04/08 Only in San Diego – faculty presentations continued. Miller - Rasberry Pi as an audio and video platform. Shahrokh - Mugic protocol; video walls
# 04/15 First joint class
# 04/22 Robin, Ludger and Max are in San Diego
# 04/29
# 05/06
# 05/13
# 05/20
# 05/27 Only in Weimar (Memorial day in the U.S.)
# 06/03
# 06/10
# 06/17
# 06/24
# 07/01

==Literature==
* Föllmer, Golo: Netzmusik, Wolke Verlag ISBN 3936000336
* LaBelle, Brandon: Background Noise ISBN 9780826418456
* LaBelle, Brandon: Site of Sound: Or Architecture and the Ear ISBN 978-0982743904
* Minard, Robin: Silent Music ISBN 978-3933257130
* Minard, Robin: Sound Installation Art
* Leitner, Bernard: Sound:Space ISBN 978-3893224449

Pd books:
{{Template:PdBooks}}

==Links==
* [https://groups.google.com/forum/?&fromgroups#!forum/buw-ucsd Google Group BUW-UCSD]
* [https://puredata.info/docs/raspberry-pi Pure Data on the Raspberry Pi]

===Sending data over the network===
* [[OSC]]
* netsend/netreceive, netserver/netclient. In Pd look at <tt>mrpeach</tt> and <tt>iemnet libraries</tt>
* [http://ivl.calit2.net/wiki/index.php/StreamingGraphics Mugic]

===Sending Audio and Video over the Internet===
* [[wikipedia:Audio Video Bridging]] AVB is a set of standards for audio and video transmission by the IEEE

====Intended for Communcation====
* [http://www.skype.com Skype] [[File:Icon newtux 16x16.png]] [[File:Icon android 16x16.png]] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]]
* [https://tools.google.com/dlpage/hangoutplugin Google+ Hangout] [[File:Icon newtux 16x16.png]] [[File:Icon android 16x16.png]] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]] (Seems to work best in Chome/Chromium)
* [http://www.oovoo.com ooVoo] [[File:Icon android 16x16.png]] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]]
* [http://www.voxox.com voxox] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]]
* [http://www.teamviewer.com teamviewer] [[File:Icon newtux 16x16.png]] [[File:Icon android 16x16.png]] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]]
* [http://jackaudio.org/ Jack Audio Connection Kit] [[File:Icon newtux 16x16.png]] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]]
* [https://code.google.com/p/jacktrip/ Jacktrip (network facilities for Jack ][[File:Icon newtux 16x16.png]] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]]

Teleconferencing
* [http://www.polycom.com Polycom] [[File:Icon windows8 16x16.png]] System available in Weimar
* [http://www.radvision.com/Products/Video-Conference-Systems Radvision Scopia] [[File:Icon windows8 16x16.png]]
* [http://www.lifesize.com Livesize] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]] System available in San Diego

Unidirectional only (aka streaming)
* [http://giss.tv Global Independent Streaming Support], [http://giss.tv/wiki/index.php/Main_Page G.I.S.S wiki]
* [http://www.ustream.tv Ustream]
* [http://www.justin.tv justin.tv]

====Intended for Performance/Creative Use====
* [http://code.sat.qc.ca/redmine/projects/scenic/wiki/Scenic_fr Scenic] Audio and video in high quality, as well as MIDI [[File:Icon newtux 16x16.png]]
* [http://code.google.com/p/jacktrip JackTrip] [[File:Icon newtux 16x16.png]] [[File:Icon apple 16x16.png]]
* [http://gstreamer.freedesktop.org GStreamer] and bindings for Pd: [http://umlaeute.mur.at/Members/zmoelnig/projects/pdgst PdGst] [[File:Icon newtux 16x16.png]]
* netsend~ for Max/MSP and Pd: [http://www.nullmedium.de/dev/netsend~ Olaf Matthes' Original Version] [[File:Icon newtux 16x16.png]] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]], [http://www.olivierguillerminet.com/2008/12/netsend Olivier Guillerminet's/Remu's Fork] [[File:Icon apple 16x16.png]] [[File:Icon windows8 16x16.png]]
* [https://ccrma.stanford.edu/~danielsm/research.html Michelle Daniels] Streaming Audio Manager

===Performing Remotely===
* [http://www.netpd.org NetPd]
* [http://at.or.at/serendipd SerendiPd] collaborative patching

User:Ludwigberger

2013-04-15T16:30:11Z

Ludwigberger: /* Platforms */

User:Ludwigberger

2013-04-15T16:30:02Z

Ludwigberger:

User:Ludwigberger

2013-04-15T16:29:21Z

Ludwigberger: /* Platforms */

I study electroacoustic composition under the direction of Robin Minard at the Franz Liszt School of Music in Weimar. Before, I studied musicology, art history and literature in Eichstätt-Ingolstadt University (Germany). While studying there I began composing music for film and theatre.
You can find my website [http://www.ludwigberger.com here]

==Interests==
I'm interested in acousmatic/radiophonic works, but also in theatre and installations.

==Platforms==
OS X

File:Ludwig-Berger-Portrait--008kleinswquadr.jpg

2013-04-15T16:28:53Z

Ludwigberger:

== Summary ==

== Copyright status: ==

== Licensing ==
{{self|c}}
== Source: ==

User:Ludwigberger

2013-04-15T16:28:08Z

Ludwigberger:

User:Ludwigberger

2013-04-15T16:25:17Z

Ludwigberger: Created page with "I study electroacoustic composition under the direction of Robin Minard at the Franz Liszt School of Music in Weimar. Before, I studied musicology, art history and literature in ..."