Medien Wiki - User contributions [en]

EKK:LoFi Sounds in HiFi Spaces/Immersive Collage

2013-05-16T20:44:21Z

Kevin:

===Idea===
[[File:360screenwall.jpg|thumb|some first thoughts on the environment]]

'''''These are just some first thoughts on a project idea. Of course there are still plenty of possibilities for changes or merging with other project ideas.'''''

How do we think of places that we‘ve never been to before?
How have the new media changed that way of thinking?
How do we imagine a place in San Diego, if we only hear its soundscape?

First of all, if we hear things of an unknown place, we are projecting images of our own experiences onto these “unknown” places, which therefore become “mappings” that are provided with our own mind.

But – due to internet services like google maps or google streetview, nowadays it‘s not a big deal anymore to demistify and to discover unknown places via internet. A massive amount of available image-data tells us anything about the far places.
Still the place we expire via the internet is only a fragmental space.

So, what happens if we are confronted with a new random environment of San Diego?

My idea is to play with these thoughts and build an immersive space that can be discovered by visitors in weimar. I want the visitor to be confronted with some new, made-up space. I‘m thinking of an audiovisual environment that is fed by two different sorts of data:

* 4 channel (live-)audio-stream from San Diego
* googleMaps/panoramio images from San Diego which have been shot on a location that is close to the current position of the recording device

I want to discover new relations between San Diego soundscapes, google/panoramio-image data and the associations each visitor would have on his own, once the images are shown in a fragmental way only.

The plan is play and to analyze (FFT) the incoming live audio data (potential latencies are not a problem) and use it to trigger a generative collage of the picture-footage that is found on the internet. I am thinking of designing some nice algorithms that put together different parts of images in relation to the sonic events. So maybe if you hear some waves of San Diego beach or some car traffic, pixels from the images that are located near to the recording device will appear in a wavelike movement etc...
The different parts of the images would then fade-out gently after some moments.

===Participants===
* [[../Alex/]]
* [[../Kevin/]]

===Links, Literature===
* Corinne Vionnet: [http://www.mymodernmet.com/profiles/blogs/hundreds-of-tourist-photos Photo Opportunities] Crowdsourced photography.

more to come

EKK:LoFi Sounds in HiFi Spaces/Immersive Collage

2013-05-16T20:40:15Z

Kevin:

EKK:LoFi Sounds in HiFi Spaces/Mingling sounds/Alex Kevin

2013-04-29T16:42:23Z

Kevin:

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

'''Kevin:''' Like radio, telephony, and television before it, the emerging paradigm of screen-based, networked collaboration effectively eliminates distances. Of those earlier mediums, only telephony was characterized by two-way communications. Because of the power of vision, video as a bi-directional medium can bridge space in ways that sound alone can't. It facilitates the connections of people but also their contexts - their environments. This presents an interesting schism: on one hand, people who have never met are able to communicate intimately; on the other, the people we come to know in this way are people we are unlikely to ever meet in person.

'''Alex:'''
I think McLuhans thoughts are still interesting. Since the 20th century, the physical ascertainable reality is being changed. As reasons for that one can see two technological innovations, which can be recognized in the development of mass media as well as in pieces of contemporary art: First, it's the increase of velocity which is now beyond the skills of human cognition, and second, it's the digitalization, the conversion of an anlogue "reality" towards a code-based (and therefore arbitrarily changeable) level. According to McLuhan, the message of every medium is "the change of scale or pace or pattern" that a new invention or innovation "introduces into human affairs." In other words: Media have the function to translate experiences into new forms, they are, as has often been said, the extensions of our sensory organs.
These possibilities of dealing with reality and of shaping the experience of old and new phenomenons in an artistic way are of a major importance to my own works. And also for the cooperation with our partners in San Diego, the thoughts of McLuhan are not unimportant, because the process of a mediatization of cognition is ever since not only a process of removal from physicalness. It is – due to the exceedings of physicalness and its implications – much more the transgression of the mechanistic system in general. Thus, the project-title "LoFi Sounds in HiFi Spaces" already implies two cores of our research and our projects. To say it with McLuhan, beyond a mechanistic point of view, we are approaching a comprehension of virtual systems, such as one is sound or the bridged-space we create.
Considering our common meetings which are mediated via skype or the small experiments like the interchanged audio-visual relations in our recent works, i think that the interesting implications in dealing with these specifics of recent media innovations are already beginning to be recognizable at this stage of our project, and of course, they will be marked clearly, they will be the message, no matter if they are LoFi or HiFi or raspberryPi.

* 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?

'''Kevin:''' A recording, whether visual or auditory, establishes a scene - a set of expectations - of the things which are likely to occur.

For the most part, we expect a correlation between the things we see and the things we hear. Both senses alert us to things to pay attention to: our hearing can inform us of things we don't see, and our vision can inform us of things we don't hear. The alert itself may be the fact that the two senses aren't in agreement, in which case we work to make them align.

A location swap is powerful because it provides juxtaposition, an opportunity to contrast two states. Attention is drawn to those characteristics which don't align, and to those that do resolve for unexpected reasons. We realize the things that we take for granted, and glimpse the structures that frame our perception.

'''Alex:''' As Kevin already observed very well, we expect a correlation between the things we see and the things we hear. The perception of our natural environment has always been multimodal, it always occured with multiple sensory organs at once. That is due to the fact, that our natural environment does not appear in isolated and independent modalities, it appears much more as a unit of optical, acoustical and/or other stimulations. The "non-natural" ability for a splitted human perception is only possible due to an enormous effort in terms of abstraction. Therefore, works like those of Bill Fontana offer the possibility of a multimodal perception, but on the same hand play with our confirmed habits of trying to put everything in a relation.
I think that the locational switch of sound gives the place a different emotional shape and therefore influences our rational and visual perception. It challenges our habits and makes us reinterpret the occuring phenomenons, which is an ideal mode of artistic examination.

* 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?

'''Kevin:''' We have expectations of known things in terms of the kinds of sounds they're likely to make, and notions of what different sounds or qualities of sound might signify. When our expectations don't align with our perceptions, it's a signal that our understanding of a situation may be in immediate need of re-evaluation.

'''Alex:''' The need of re-evaluation is a nice point, because by doing this, it means that we pay much more attention towards something than we would have done otherwise.

See the mingled videos:

[https://www.dropbox.com/s/uh9e6gqr3qx56ab/gliderportIlmparkModified.mp4 Ilmpark and Gliderport]

[https://www.dropbox.com/s/at8acfblodwj8om/IlmarkparkGliderport.mp4 Gliderport and Ilmpark]

EKK:LoFi Sounds in HiFi Spaces/Mingling sounds/Alex Kevin

2013-04-29T00:00:09Z

Kevin:

EKK:LoFi Sounds in HiFi Spaces/Mingling sounds/Alex Kevin

2013-04-28T23:31:48Z

Kevin:

EKK:LoFi Sounds in HiFi Spaces/Mingling sounds/Alex Kevin

2013-04-28T23:20:23Z

Kevin:

EKK:LoFi Sounds in HiFi Spaces/Mingling sounds/Alex Kevin

2013-04-28T22:15:23Z

Kevin: Created page with "* 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..."

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

'''Kevin'''

Here is my response.

* 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?

* 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?

EKK:LoFi Sounds in HiFi Spaces/Making connection/OS X Messages/FaceTime

2013-04-24T05:22:39Z

Kevin:

==OS X Messages==

Messages is a video, screen sharing, file transfer, and text-chat platform that ships with OS X 10.8. It supports multiple chat protocols such as AIM, Yahoo, Google Talk, and Jabber, as well as Apple's iMessages protocol. Despite this support, Messages appears to segregate each protocol, meaning that a user with an AIM account cannot communicate with a Yahoo user.

Messages offers only a single option for adjusting the signal: a bandwidth limit (down to 100kbps/12.5kB).

==Communications==

Weimar and San Diego tested video chat and file transfer using the AIM protocol. Performance was hit and miss. The best aspect was latency, with both sides agreeing that the timing of communications felt natural. Video quality was significantly different on each side: Weimar witnessed crisp imagery from San Diego, while San Diego consistently received blocky video featuring varying degrees of artifacts. Audio dropouts correlated with video performance.

<gallery>
File:ViewOfSanDiego.jpg|A view of San Diego
File:ViewOfWeimar.jpg|A view of Weimar
</gallery>

It's worth noting that at one point, Messages lost connection, throwing an error message and ''crashing San Diego's cable modem''. This is considered worth mentioning, since San Diego had memory of this happening before, in a different city with a different ISP.

File transfers worked well, with recordings for this project exchanged via drag-and-drop into Messages' text chat window. Transfer rates of 135K were reached, and were probably limited only by our ISP services.

==Sending Signals==

Audio signals were generated by each side, transmitted via Soundflower through Messages, and recorded via Soundflower on the other side. Dropouts were naturally the most significant problem, but in a sine wave test, a strong amplitude modulation would appear and disappear at 50Hz. This is evident in the accompanying screen shot.

A spectrum plot of white noise shows the removal of all frequencies above 6000 Hz, and a roll off of frequencies below 300 Hz.

<gallery>
File:1kSineFromWeimar.png|Pure 1kHz sine from Weimar
File:WhiteNoiseFromWeimar.png|White noise from Weimar
File:WhiteNoiseFromWeimarSpectrum.png|White noise from Weimar (spectrum)
</gallery>

EKK:LoFi Sounds in HiFi Spaces/Making connection/OS X Messages/FaceTime

2013-04-24T05:14:31Z

Kevin:

==OS X Messages==

Messages is a video, screen sharing, file transfer, and text-chat platform that ships with OS X 10.8. It supports multiple chat protocols such as AIM, Yahoo, Google Talk, and Jabber, as well as Apple's iMessages protocol. Despite this support, Messages appears to segregate each protocol, meaning that a user with an AIM account cannot communicate with a Yahoo user.

Messages offers only a single option for adjusting the signal: a bandwidth limit (down to 100kbps/12.5kB).

==Communications==

Weimar and San Diego tested video chat and file transfer using the AIM protocol. Performance was hit and miss. The best aspect was latency, with both sides agreeing that the timing of communications felt natural. Video quality was significantly different on each side: Weimar witnessed crisp imagery from San Diego, while San Diego consistently received blocky video featuring varying degrees of artifacts. Audio dropouts correlated with video performance.

<gallery>
File:ViewOfSanDiego.jpg|A view of San Diego
File:ViewOfWeimar.jpg|A view of Weimar
</gallery>

It's worth noting that at one point, Messages lost connection, throwing an error message and ''crashing San Diego's cable modem''. This is considered worth mentioning, since San Diego had memory of this happening before, in a different city with a different ISP.

File transfers worked well, with recordings for this project exchanged via drag-and-drop into Messages' text chat window. Transfer rates of 135K were reached, and were probably limited only by our ISP services.

==Audio Signals==

Audio signals were generated by each side, transmitted via Soundflower through Messages, and recorded via Soundflower on the other side. Dropouts were naturally the most significant problem, but in a sine wave test, a strong amplitude modulation would appear and disappear at 50Hz. This is evident in the accompanying screen shot.

A spectrum plot of white noise shows the removal of all frequencies above 6000 Hz, and a roll off of frequencies below 300 Hz.

<gallery>
File:1kSineFromWeimar.png|Pure 1kHz sine from Weimar
File:WhiteNoiseFromWeimar.png|White noise from Weimar
File:WhiteNoiseFromWeimarSpectrum.png|White noise from Weimar (spectrum)
</gallery>

EKK:LoFi Sounds in HiFi Spaces/Making connection/OS X Messages/FaceTime

2013-04-24T05:07:51Z

Kevin:

==OS X Messages==

Messages is a video, screen sharing, file transfer, and text-chat platform that ships with OS X 10.8. It supports multiple chat protocols such as AIM, Yahoo, Google Talk, and Jabber, as well as Apple's iMessages protocol. Despite this support, Messages appears to segregate each protocol, meaning that a user with an AIM account cannot communicate with a Yahoo user.

==Communications==

Weimar and San Diego tested video chat and file transfer using the AIM protocol. Performance was hit and miss. The best aspect was latency, with both sides agreeing that the timing of communications felt natural. Video quality was significantly different on each side: Weimar witnessed crisp imagery from San Diego, while San Diego consistently received blocky video featuring varying degrees of artifacts. Audio dropouts correlated with video performance.

<gallery>
File:ViewOfSanDiego.jpg|A view of San Diego
File:ViewOfWeimar.jpg|A view of Weimar
</gallery>

It's worth noting that at one point, Messages lost connection, throwing an error message and ''crashing San Diego's cable modem''. This is considered worth mentioning, since San Diego had memory of this happening before, in a different city with a different ISP.

File transfers worked well, with recordings for this project exchanged via drag-and-drop into Messages' text chat window. Transfer rates of 135K were reached, and were probably limited only by our ISP services.

==Audio Signals==

Audio signals were generated by each side, transmitted via Soundflower through Messages, and recorded via Soundflower on the other side. Dropouts were naturally the most significant problem, but in a sine wave test, a strong amplitude modulation would appear and disappear at 50Hz. This is evident in the accompanying screen shot.

A spectrum plot of white noise shows the removal of all frequencies above 6000 Hz, and a roll off of frequencies below 300 Hz.

<gallery>
File:1kSineFromWeimar.png|Pure 1kHz sine from Weimar
File:WhiteNoiseFromWeimar.png|White noise from Weimar
File:WhiteNoiseFromWeimarSpectrum.png|White noise from Weimar (spectrum)
</gallery>

File:WhiteNoiseFromWeimarSpectrum.png

2013-04-24T05:03:34Z

Kevin:

== Summary ==

== Copyright status: ==

== Source: ==

EKK:LoFi Sounds in HiFi Spaces/Making connection/OS X Messages/FaceTime

2013-04-24T05:03:16Z

Kevin:

==OS X Messages==

Messages is a video, screen sharing, file transfer, and text-chat platform that ships with OS X 10.8. It supports multiple chat protocols such as AIM, Yahoo, Google Talk, and Jabber, as well as Apple's iMessages protocol. Despite this support, Messages appears to segregate each protocol, meaning that a user with an AIM account cannot communicate with a Yahoo user.

==Communications==

Weimar and San Diego tested video chat and file transfer using the AIM protocol. Performance was hit and miss. The best aspect was latency, with both sides agreeing that the timing of communications felt natural. Video quality was significantly different on each side: Weimar witnessed crisp imagery from San Diego, while San Diego consistently received blocky video featuring varying degrees of artifacts. Audio dropouts correlated with video performance.

<gallery>
File:ViewOfSanDiego.jpg|A view of San Diego
File:ViewOfWeimar.jpg|A view of Weimar
</gallery>

It's worth noting that at one point, Messages lost connection, throwing an error message and ''crashing San Diego's cable modem''. This is considered worth mentioning, since San Diego had memory of this happening before, in a different city with a different ISP.

File transfers worked well, with recordings for this project exchanged via drag-and-drop into Messages' text chat window. Transfer rates of 135K were reached, and were probably limited only by our ISP services.

==Audio Signals==

Audio signals were generated by each side, transmitted via Soundflower through Messages, and recorded via Soundflower on the other side. Dropouts were naturally the most significant problem, but in a sine wave test, a strong amplitude modulation would appear and disappear at 50Hz. This is evident in the accompanying screen shot.

[[File:WhiteNoiseFromWeimarSpectrum.png]]

<gallery>
File:1kSineFromWeimar.png|Pure 1kHz sine from Weimar
File:WhiteNoiseFromWeimar.png|White noise from Weimar
File:WhiteNoiseFromWeimarSpectrum.png|White noise from Weimar (spectrum)
</gallery>

EKK:LoFi Sounds in HiFi Spaces/Making connection/OS X Messages/FaceTime

2013-04-24T05:02:42Z

Kevin:

==OS X Messages==

Messages is a video, screen sharing, file transfer, and text-chat platform that ships with OS X 10.8. It supports multiple chat protocols such as AIM, Yahoo, Google Talk, and Jabber, as well as Apple's iMessages protocol. Despite this support, Messages appears to segregate each protocol, meaning that a user with an AIM account cannot communicate with a Yahoo user.

==Communications==

Weimar and San Diego tested video chat and file transfer using the AIM protocol. Performance was hit and miss. The best aspect was latency, with both sides agreeing that the timing of communications felt natural. Video quality was significantly different on each side: Weimar witnessed crisp imagery from San Diego, while San Diego consistently received blocky video featuring varying degrees of artifacts. Audio dropouts correlated with video performance.

<gallery>
File:ViewOfSanDiego.jpg|A view of San Diego
File:ViewOfWeimar.jpg|A view of Weimar
</gallery>

It's worth noting that at one point, Messages lost connection, throwing an error message and ''crashing San Diego's cable modem''. This is considered worth mentioning, since San Diego had memory of this happening before, in a different city with a different ISP.

File transfers worked well, with recordings for this project exchanged via drag-and-drop into Messages' text chat window. Transfer rates of 135K were reached, and were probably limited only by our ISP services.

==Audio Signals==

Audio signals were generated by each side, transmitted via Soundflower through Messages, and recorded via Soundflower on the other side. Dropouts were naturally the most significant problem, but in a sine wave test, a strong amplitude modulation would appear and disappear at 50Hz. This is evident in the accompanying screen shot.

<gallery>
File:1kSineFromWeimar.png|Pure 1kHz sine from Weimar
File:WhiteNoiseFromWeimar.png|White noise from Weimar
File:WhiteNoiseFromWeimarSpectrum.png|White noise from Weimar (spectrum)
</gallery>

EKK:LoFi Sounds in HiFi Spaces/Making connection/OS X Messages/FaceTime

2013-04-24T04:55:29Z

Kevin:

==OS X Messages==

Messages is a video, screen sharing, file transfer, and text-chat platform that ships with OS X 10.8. It supports multiple chat protocols such as AIM, Yahoo, Google Talk, and Jabber, as well as Apple's iMessages protocol. Despite this support, Messages appears to segregate each protocol, meaning that a user with an AIM account cannot communicate with a Yahoo user.

==Communications==

Weimar and San Diego tested video chat and file transfer using the AIM protocol. Performance was hit and miss. The best aspect was latency, with both sides agreeing that the timing of communications felt natural. Video quality was significantly different on each side: Weimar witnessed crisp imagery from San Diego, while San Diego consistently received blocky video featuring varying degrees of artifacts. Audio dropouts correlated with video performance.

<gallery>
File:ViewOfSanDiego.jpg|A view of San Diego
File:ViewOfWeimar.jpg|A view of Weimar
</gallery>

It's worth noting that at one point, Messages lost connection, throwing an error message and ''crashing San Diego's cable modem''. This is considered worth mentioning, since San Diego had memory of this happening before, in a different city with a different ISP.

File transfers worked well, with recordings for this project exchanged via drag-and-drop into Messages' text chat window. Transfer rates of 135K were reached, and were probably limited only by our ISP services.

==Audio Signals==

Audio signals were generated by each side, transmitted via Soundflower through Messages, and recorded via Soundflower on the other side. Dropouts were naturally the most significant problem, but in a sine wave test, a strong amplitude modulation would appear and disappear at 50Hz. This is evident in the accompanying screen shot.

<gallery>
File:1kSineFromWeimar.png|Pure 1kHz sine from Weimar
File:WhiteNoiseFromWeimar.png|White noise from Weimar
</gallery>

EKK:LoFi Sounds in HiFi Spaces/Making connection/OS X Messages/FaceTime

2013-04-24T04:44:36Z

Kevin:

==OS X Messages==

Messages is a video, screen sharing, file transfer, and text-chat platform that ships with OS X 10.8. It supports multiple chat protocols such as AIM, Yahoo, Google Talk, and Jabber, as well as Apple's iMessages protocol. Despite this support, Messages appears to segregate each protocol, meaning that a user with an AIM account cannot communicate with a Yahoo user.

==Communications==

Weimar and San Diego tested video chat and file transfer using the AIM protocol. Performance was hit and miss. The best aspect was latency, with both sides agreeing that the timing of communications felt natural. Video quality was significantly different on each side: Weimar witnessed crisp imagery from San Diego, while San Diego consistently received blocky video featuring varying degrees of artifacts. Audio dropouts correlated with video performance.

<gallery>
File:ViewOfSanDiego.jpg|A view of San Diego
File:ViewOfWeimar.jpg|A view of Weimar
</gallery>

It's worth noting that at one point, Messages lost connection, throwing an error message and ''crashing San Diego's cable modem''. This is considered worth mentioning, since San Diego had memory of this happening before, in a different city with a different ISP.

File transfers worked well, with recordings for this project exchanged via drag-and-drop into Messages' text chat window. Transfer rates of 135K were reached, and were probably limited only by our ISP services.

==Audio Signals==

Audio signals were generated by each side, transmitted via Soundflower through Messages, and recorded via Soundflower on the other side. Fidelity was generally horrendous.

<gallery>
File:1kSineFromWeimar.png|Pure 1kHz sine from Weimar
File:WhiteNoiseFromWeimar.png|White noise from Weimar
</gallery>

EKK:LoFi Sounds in HiFi Spaces/Making connection/OS X Messages/FaceTime

2013-04-24T04:28:45Z

Kevin:

EKK:LoFi Sounds in HiFi Spaces/Making connection/OS X Messages/FaceTime

2013-04-24T04:04:05Z

Kevin:

==OS X Messages==

Messages.

<gallery>
File:ViewOfSanDiego.jpg|A view of San Diego
File:ViewOfWeimar.jpg|A view of Weimar
</gallery>

==Audio Signals==

These are the audio signals.

<gallery>
File:1kSineFromWeimar.png|Pure 1kHz sine from Weimar
File:WhiteNoiseFromWeimar.png|White noise from Weimar
</gallery>

File:WhiteNoiseFromWeimar.png

2013-04-24T04:00:00Z

Kevin:

== Summary ==

== Copyright status: ==

== Source: ==

File:1kSineFromWeimar.png

2013-04-24T03:59:19Z

Kevin:

== Summary ==

== Copyright status: ==

== Source: ==

File:ViewOfWeimar.jpg

2013-04-24T03:58:15Z

Kevin:

== Summary ==

== Copyright status: ==

== Source: ==

File:ViewOfSanDiego.jpg

2013-04-24T03:57:03Z

Kevin:

== Summary ==

== Copyright status: ==

== Source: ==

EKK:LoFi Sounds in HiFi Spaces/Making connection/OS X Messages/FaceTime

2013-04-24T03:56:29Z

Kevin:

EKK:LoFi Sounds in HiFi Spaces/Making connection/OS X Messages/FaceTime

2013-04-24T03:50:09Z

Kevin: Created page with "==OS X Messages== Messages. File:ViewOfSanDiego.jpg File:ViewOfWeimar.jpg File:1kSineFromWeimar.png File:WhiteNoiseFromWeimar.png"

==OS X Messages==

Messages.

[[File:ViewOfSanDiego.jpg]]

[[File:ViewOfWeimar.jpg]]

[[File:1kSineFromWeimar.png]]

[[File:WhiteNoiseFromWeimar.png]]

EKK:LoFi Sounds in HiFi Spaces/Mingling sounds

2013-04-23T16:27:41Z

Kevin:

due 04-29

# Discuss and answer questions with your new partner. Have your answerd in writing (a amall paragraph) ready and posted in the wiki.
#* 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.
#* 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?
#* 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?
# record a 30 second static HD Video using a tripod with decent stereo sound of a place in your city. Exchange the soundtrack of your video with the one of your partner.

* [[../Clemens|Clemens]]/[[../Bo|Bo]]: [[/Clemens Bo/]]
* [[../Alice|Alice]]/[[../Ryan Welsh|Ryan]]: [[/Alice Ryan/]]
* [[../Ben|Ben]]/[[../ElisabetCurbelo|Elisabet]]: [[/Ben Elisabet/]]
* [[../Ludwigberger|Ludwig]]/[[../Jeffrey|Jeffrey]]: [[/Ludwig Jeffrey/]]
* [[../Andre|Andre]]/[[../Joe Cantrell|Joe]]: [[/Andre Joe/]]
* [[../Dorian|Dorian]]/[[../Melanie|Melanie]]: [[/Dorian Melanie/]]
* [[../Cornelio|Cornelius]]/[[../Jamilah|Jamilah]]: [[/Cornelius Jamilah/]]
* [[../Rico|Rico]]/[[../Brendan Bernhardt Gaffney|Brendan]]: [[/Rico Brendan/]]
* [[../Paul|Paul]]/[[../czyskows|Colin]]: [[/Paul Colin/]]
* [[../TimH|Tim]]/[[../NickDrashner|Nick]]: [[/Tim Nick/]]
* [[../Alex|Alex]]/[[../Kevin|Kevin]]: [[/Alex Kevin/]]
* [[../Jonas|Jonas]]/[[../Andy|Andy]]: [[/Jonas Andy/]]
* [[../Ives|Ives]]/[[../Marcelo|Marcelo]]: [[/Ives Marcelo/]]

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

2013-04-21T19:46:33Z

Kevin: /* The ooVoo Interface */

==ooVoo==

ooVoo is a multi-platform video conferencing/chat application that boasts allowing up to 12 simultaneous video streams.

Unlike Skype, ooVoo doesn't make use of peer-to-peer connections, instead relying on some kind of cloud configuration. Apparently because of this, ooVoo's CEO has stated that ooVoo isn't typically used for "scheduled international calls or professional meetings," instead focusing on casual users. Nevertheless, the Washington Post claimed in 2011 that ooVoo had been approved for official communications within the US House of Representatives.

==The ooVoo Interface==

ooVoo manifests as a cluttered and non-native interface spread across multiple windows for its various tasks: a contacts list, a text chat window, a video chat window, etc. ''Every window'' in ooVoo displays advertisements at you. It can be assumed that these are targeted: during our intercontinental chats, I was shown a Volkswagen ad comprised of text in Spanish, German, and English simultaneously. Some ads automatically play audio at you, destroying any recordings you might be making - this is significant since call recording is a built-in feature.

[[File:oovoo.jpg]]

In a video conference, ooVoo partitions the window based on how many participants are present. In the default view with two people, the video streams appear as adjacent rectangles. With three people present, the right and left streams are angled in a gratuitous 3D effect. As an alternative, any single stream can be designated to fill the window, with the remaining streams delegated into a single corner.

==Testing ooVoo==

We tested ooVoo as a 3-person team with one person in Weimar and 2 people at separate locations in San Diego. Audio fidelity during conversation was relatively poor, as has come to be expected from internet telephony. All three of us experienced intermittent feedback bursts, where audio with about a half-second of delay would return loudly for a few seconds at a time. ooVoo's automatic gain control didn't have much of an effect on this.

Weimar occasionally experienced bandwidth issues, which ooVoo deals with by automatically dropping the affected video stream, while keeping audio alive.

==Exploring==

We explored latency pragmatically. As an initial experiment, we attempted to clap steadily as a group. This failure found new form in our second attempt, where our hands were kept clearly visible in front of the camera, providing both strong visual and audio cues for timing.

The power of feedback in mediating our group dynamic led us to our next experiment. We decided upon a feedback-based "call and response" exercise that would demonstrate the audio, visual, and perceptual latencies present.

Weimar found a way to stream a video file in place of the webcam image, and generated a series of stroboscopic videos displaying a burst of white between lulls of blackness. When darkness fell in San Diego, Weimar began broadcasting. With each flash, Weimar uttered the German word for light, "licht." The San Diegans, from independent locations, monitored Weimar fullscreen. Whenever they witnessed the light of Weimar, they responded in their own native tongues, Spanish and English: "Luz!" "Light!"

With microphone gains and speakers set to maximum, an unsteady but hypnotic mantra emerged. The whole process was recorded by Weimar, who was witness to all three streams. Playback provided clear documentation of the timing discrepancies of audio and video between the three locations. Unable to resist the cycle of feedback, Weimar again recorded the viewing of this recording. We present the result here.

As soon as it is uploaded.

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

2013-04-21T19:45:03Z

Kevin:

==ooVoo==

ooVoo is a multi-platform video conferencing/chat application that boasts allowing up to 12 simultaneous video streams.

Unlike Skype, ooVoo doesn't make use of peer-to-peer connections, instead relying on some kind of cloud configuration. Apparently because of this, ooVoo's CEO has stated that ooVoo isn't typically used for "scheduled international calls or professional meetings," instead focusing on casual users. Nevertheless, the Washington Post claimed in 2011 that ooVoo had been approved for official communications within the US House of Representatives.

==The ooVoo Interface==

ooVoo manifests as a cluttered and non-native interface spread across multiple windows for its various tasks: a contacts list, a text chat window, a video chat window, etc. ''Every window'' in ooVoo displays advertisements at you. It can be assumed that these are targeted: during our intercontinental chats, I was shown a Volkswagen ad comprised of text in Spanish, German, and English simultaneously. Some ads automatically play audio at you, destroying any recordings you might be making - this is significant since call recording is a built-in feature.

Frustratingly, some menu items are not identical across platforms. In trying to troubleshoot issues we were having, ooVoo's tech support page referred to necessary menu entries which existed on OS X, but not on Windows.

[[File:oovoo.jpg]]

In a video conference, ooVoo partitions the window based on how many participants are present. In the default view with two people, the video streams appear as adjacent rectangles. With three people present, the right and left streams are angled in a gratuitous 3D effect. As an alternative, any single stream can be designated to fill the window, with the remaining streams delegated into a single corner.

==Testing ooVoo==

We tested ooVoo as a 3-person team with one person in Weimar and 2 people at separate locations in San Diego. Audio fidelity during conversation was relatively poor, as has come to be expected from internet telephony. All three of us experienced intermittent feedback bursts, where audio with about a half-second of delay would return loudly for a few seconds at a time. ooVoo's automatic gain control didn't have much of an effect on this.

Weimar occasionally experienced bandwidth issues, which ooVoo deals with by automatically dropping the affected video stream, while keeping audio alive.

==Exploring==

We explored latency pragmatically. As an initial experiment, we attempted to clap steadily as a group. This failure found new form in our second attempt, where our hands were kept clearly visible in front of the camera, providing both strong visual and audio cues for timing.

The power of feedback in mediating our group dynamic led us to our next experiment. We decided upon a feedback-based "call and response" exercise that would demonstrate the audio, visual, and perceptual latencies present.

Weimar found a way to stream a video file in place of the webcam image, and generated a series of stroboscopic videos displaying a burst of white between lulls of blackness. When darkness fell in San Diego, Weimar began broadcasting. With each flash, Weimar uttered the German word for light, "licht." The San Diegans, from independent locations, monitored Weimar fullscreen. Whenever they witnessed the light of Weimar, they responded in their own native tongues, Spanish and English: "Luz!" "Light!"

With microphone gains and speakers set to maximum, an unsteady but hypnotic mantra emerged. The whole process was recorded by Weimar, who was witness to all three streams. Playback provided clear documentation of the timing discrepancies of audio and video between the three locations. Unable to resist the cycle of feedback, Weimar again recorded the viewing of this recording. We present the result here.

As soon as it is uploaded.

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

2013-04-21T19:43:43Z

Kevin:

==ooVoo==

ooVoo is a multi-platform video conferencing/chat application that boasts allowing up to 12 simultaneous video streams.

Unlike Skype, ooVoo doesn't make use of peer-to-peer connections, instead relying on some kind of cloud configuration. Apparently because of this, ooVoo's CEO has stated that ooVoo isn't typically used for "scheduled international calls or professional meetings," instead focusing on casual users. Nevertheless, the Washington Post claimed in 2011 that ooVoo had been approved for official communications within the US House of Representatives.

==The ooVoo Interface==

ooVoo manifests as a cluttered and non-native interface spread across multiple windows for its various tasks: a contacts list, a text chat window, a video chat window, etc. ''Every window'' in ooVoo displays advertisements at you. It can be assumed that these are targeted: during our intercontinental chats, I was shown a Volkswagen ad comprised of text in Spanish, German, and English simultaneously. Some ads automatically play audio at you, destroying any recordings you might be making - this is significant since call recording is a built-in feature.

Frustratingly, some menu items are not identical across platforms. In trying to troubleshoot issues we were having, ooVoo's tech support page referred to necessary menu entries which existed on OS X, but not on Windows.

[[File:oovoo.jpg]]

In a video conference, ooVoo partitions the window based on how many participants are present. In the default view with two people, the video streams appear as adjacent rectangles. With three people present, the right and left streams are angled in a gratuitous 3D effect. As an alternative, any single stream can be designated to fill the window, with the remaining streams delegated into a single corner.

==Testing ooVoo==

We tested ooVoo as a 3-person team with one person in Weimar and 2 people at separate locations in San Diego. Audio fidelity during conversation was relatively poor, as has come to be expected from internet telephony. All three of us experienced intermittent feedback bursts, where audio with about a half-second of delay would return loudly for a few seconds at a time. ooVoo's automatic gain control didn't have much of an effect on this.

Weimar occasionally experienced bandwidth issues, which ooVoo deals with by automatically dropping the affected video stream, while keeping audio alive.

==Exploring==

We explored latency pragmatically. As an initial experiment, we attempted to clap steadily as a group. This failure found new form in our second attempt, where our hands were kept clearly visible in front of the camera, providing both strong visual and audio cues for timing.

The power of feedback in mediating our group dynamic led us to our next experiment. We decided upon a feedback-based "call and response" exercise that would demonstrate the audio, visual, and perceptual latencies present.

Weimar found a way to stream a video file in place of the webcam image, and generated a series of stroboscopic videos displaying a burst of white between lulls of blackness. When darkness fell in San Diego, Weimar began broadcasting. With each flash, Weimar uttered the German word for light, "licht." The San Diegans, from independent locations, monitored Weimar fullscreen. Whenever they witnessed the light of Weimar, they responded in their own native tongues, Spanish and English: "Luz!" "Light!"

With microphone gains and speakers set to maximum, an unsteady but hypnotic mantra emerged. The whole process was recorded by Weimar, who was witness to all three streams. Playback provided clear documentation of the timing discrepancies of audio and video between the three locations. Unable to resist the cycle of feedback, Weimar again recorded the viewing of this recording. We present the result here.

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

2013-04-21T19:38:51Z

Kevin:

==ooVoo==

ooVoo is a multi-platform video conferencing/chat application that boasts allowing up to 12 simultaneous video streams.

Unlike Skype, ooVoo doesn't make use of peer-to-peer connections, instead relying on some kind of cloud configuration. Apparently because of this, ooVoo's CEO has stated that ooVoo isn't typically used for "scheduled international calls or professional meetings," instead focusing on casual users. Nevertheless, the Washington Post claimed in 2011 that ooVoo had been approved for official communications within the US House of Representatives.

==The ooVoo Interface==

ooVoo manifests as a cluttered and non-native interface spread across multiple windows for its various tasks: a contacts list, a text chat window, a video chat window, etc. ''Every window'' in ooVoo displays advertisements at you. It can be assumed that these are targeted: during our intercontinental chats, I was shown a Volkswagen ad comprised of text in Spanish, German, and English simultaneously. Some ads automatically play audio at you, destroying any recordings you might be making - this is significant since call recording is a built-in feature.

Frustratingly, some menu items are not identical across platforms. In trying to troubleshoot issues we were having, ooVoo's tech support page referred to necessary menu entries which existed on OS X, but not on Windows.

[[File:oovoo.jpg]]

In a video conference, ooVoo partitions the window based on how many participants are present. In the default view with two people, the video streams appear as adjacent rectangles. With three people present, the right and left streams are angled in a gratuitous 3D effect. As an alternative, any single stream can be designated to fill the window, with the remaining streams delegated into a single corner.

==Testing ooVoo==

We tested ooVoo as a 3-person team with one person in Weimar and 2 people at separate locations in San Diego. Audio fidelity during conversation was relatively poor, as has come to be expected from internet telephony. All three of us experienced intermittent feedback bursts, where audio with about a half-second of delay would return loudly for a few seconds at a time. ooVoo's automatic gain control didn't have much of an effect on this.

Weimar occasionally experienced bandwidth issues, which ooVoo deals with by automatically dropping the affected video stream, while keeping audio alive.

==Exploring==

We explored latency pragmatically. As an initial experiment, we attempted to clap steadily as a group. This failure found new form in our second attempt, where our hands were kept clearly visible in front of the camera, providing both strong visual and audio cues for timing.

The power of feedback in mediating our group dynamic led us to our next experiment. We decided upon a feedback-based "call and response" exercise that would demonstrate the audio, visual, and perceptual latencies present.

Weimar found a way to stream a video file in place of the webcam image, and generated a series of stroboscopic videos displaying a burst of white between lulls of blackness. When darkness fell in San Diego, Weimar began broadcasting. With each flash, Weimar uttered the German word for light, "licht." The San Diegans, from independent locations, monitored Weimar fullscreen. Whenever they witnessed the light of Weimar, they responded in their own native tongues, Spanish and English: "Luz!" "Light!"

With microphone gains and speakers set to maximum, an unsteady but hypnotic mantra emerged. The whole process was recorded by Weimar, who was witness to all three streams. Playback provided clear documentation of the timing discrepancies of audio and video between the three locations. To wrap things further in feedback, Weimar again recorded the viewing of this recording. We present the result here.

File:Oovoo.jpg

2013-04-21T19:36:10Z

Kevin:

== Summary ==

== Copyright status: ==

== Source: ==

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

2013-04-21T19:35:25Z

Kevin:

==ooVoo==

ooVoo is a multi-platform video conferencing/chat application that boasts allowing up to 12 simultaneous video streams.

Unlike Skype, ooVoo doesn't make use of peer-to-peer connections, instead relying on some kind of cloud configuration. Apparently because of this, ooVoo's CEO has stated that ooVoo isn't typically used for "scheduled international calls or professional meetings," instead focusing on casual users. Nevertheless, the Washington Post claimed in 2011 that ooVoo had been approved for official communications within the US House of Representatives.

==The ooVoo Interface==

ooVoo manifests as a cluttered and non-native interface spread across multiple windows for its various tasks: a contacts list, a text chat window, a video chat window, etc. ''Every window'' in ooVoo displays advertisements at you. It can be assumed that these are targeted: during our intercontinental chats, I was shown a Volkswagen ad comprised of text in Spanish, German, and English simultaneously. Some ads automatically play audio at you, destroying any recordings you might be making - this is significant since call recording is a built-in feature.

[[File:oovoo.jpg]]

Frustratingly, some menu items are not identical across platforms. In trying to troubleshoot issues we were having, ooVoo's tech support page referred to necessary menu entries which existed on OS X, but not on Windows.

In a video conference, ooVoo partitions the window based on how many participants are present. In the default view with two people, the video streams appear as adjacent rectangles. With three people present, the right and left streams are angled in a gratuitous 3D effect. As an alternative, any single stream can be designated to fill the window, with the remaining streams delegated into a single corner.

==Testing ooVoo==

We tested ooVoo as a 3-person team with one person in Weimar and 2 people at separate locations in San Diego. Audio fidelity during conversation was relatively poor, as has come to be expected from internet telephony. All three of us experienced intermittent feedback bursts, where audio with about a half-second of delay would return loudly for a few seconds at a time. ooVoo's automatic gain control didn't have much of an effect on this.

Weimar occasionally experienced bandwidth issues, which ooVoo deals with by automatically dropping the affected video stream, while keeping audio alive.

==Exploring==

We explored latency pragmatically. As an initial experiment, we attempted to clap steadily as a group. This failure found new form in our second attempt, where our hands were kept clearly visible in front of the camera, providing both strong visual and audio cues for timing.

The power of feedback in mediating our group dynamic led us to our next experiment. We decided upon a feedback-based "call and response" exercise that would demonstrate the audio, visual, and perceptual latencies present.

Weimar found a way to stream a video file in place of the webcam image, and generated a series of stroboscopic videos displaying a burst of white between lulls of blackness. When darkness fell in San Diego, Weimar began broadcasting. With each flash, Weimar uttered the German word for light, "licht." The San Diegans, from independent locations, monitored Weimar fullscreen. Whenever they witnessed the light of Weimar, they responded in their own native tongues, Spanish and English: "Luz!" "Light!"

With microphone gains and speakers set to maximum, an unsteady but hypnotic mantra emerged. The whole process was recorded by Weimar, who was witness to all three streams. Playback provided clear documentation of the timing discrepancies of audio and video between the three locations. To wrap things further in feedback, Weimar again recorded the viewing of this recording. We present the result here.

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

2013-04-21T19:24:53Z

Kevin:

==ooVoo==

ooVoo is a multi-platform video conferencing/chat application that boasts allowing up to 12 simultaneous video streams.

Unlike Skype, ooVoo doesn't make use of peer-to-peer connections, instead relying on some kind of cloud configuration. Apparently because of this, ooVoo's CEO has stated that ooVoo isn't typically used for "scheduled international calls or professional meetings," instead focusing on casual users. Nevertheless, the Washington Post claimed in 2011 that ooVoo had been approved for official communications within the US House of Representatives.

==The ooVoo Interface==

ooVoo manifests as a cluttered and non-native interface spread across multiple windows for its various tasks: a contacts list, a text chat window, a video chat window, etc. ''Every window'' in ooVoo displays advertisements at you. It can be assumed that these are targeted: during our intercontinental chats, I was shown a Volkswagen ad comprised of text in Spanish, German, and English simultaneously. Some ads automatically play audio at you, destroying any recordings you might be making - this is significant since call recording is a built-in feature.

Frustratingly, some menu items are not identical across platforms. In trying to troubleshoot issues we were having, ooVoo's tech support page referred to necessary menu entries which existed on OS X, but not on Windows.

In a video conference, ooVoo partitions the window based on how many participants are present. In the default view with two people, the video streams appear as adjacent rectangles. With three people present, the right and left streams are angled in a gratuitous 3D effect. As an alternative, any single stream can be designated to fill the window, with the remaining streams delegated into a single corner.

==Testing ooVoo==

We tested ooVoo as a 3-person team with one person in Weimar and 2 people at separate locations in San Diego. Audio fidelity during conversation was relatively poor, as has come to be expected from internet telephony. All three of us experienced intermittent feedback bursts, where audio with about a half-second of delay would return loudly for a few seconds at a time. ooVoo's automatic gain control didn't have much of an effect on this.

Weimar occasionally experienced bandwidth issues, which ooVoo deals with by automatically dropping the affected video stream, while keeping audio alive.

==Exploring==

We explored latency pragmatically. As an initial experiment, we attempted to clap steadily as a group. This failure found new form in our second attempt, where our hands were kept clearly visible in front of the camera, providing both strong visual and audio cues for timing.

The power of feedback in mediating our group dynamic led us to our next experiment. We decided upon a feedback-based "call and response" exercise that would demonstrate the audio, visual, and perceptual latencies present.

Weimar found a way to stream a video file in place of the webcam image, and generated a series of stroboscopic videos displaying a burst of white between lulls of blackness. When darkness fell in San Diego, Weimar began broadcasting. With each flash, Weimar uttered the German word for light, "licht." The San Diegans, from independent locations, monitored Weimar fullscreen. Whenever they witnessed the light of Weimar, they responded in their own native tongues, Spanish and English: "Luz!" "Light!"

With microphone gains and speakers set to maximum, an unsteady but hypnotic mantra emerged. The whole process was recorded by Weimar, who was witness to all three streams. Playback provided clear documentation of the timing discrepancies of audio and video between the three locations. To wrap things further in feedback, Weimar again recorded the viewing of this recording. We present the result here.

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

2013-04-21T19:11:41Z

Kevin:

==ooVoo==

ooVoo is a multi-platform video conferencing/chat application that boasts allowing up to 12 simultaneous video streams.

Unlike Skype, ooVoo doesn't make use of peer-to-peer connections, instead relying on some kind of cloud configuration. Apparently because of this, ooVoo's CEO has stated that ooVoo isn't typically used for "scheduled international calls or professional meetings," instead focusing on casual users. Nevertheless, the Washington Post claimed in 2011 that ooVoo had been approved for official communications within the US House of Representatives.

==The ooVoo Interface==

ooVoo manifests as a cluttered and non-native interface spread across multiple windows for its various tasks: a contacts list, a text chat window, a video chat window, etc. ''Every window'' in ooVoo displays advertisements at you. It can be assumed that these are targeted: during our intercontinental chats, I was shown a Volkswagen ad comprised of text in Spanish, German, and English simultaneously. Some ads automatically play audio at you, destroying any recordings you might be making - this is significant since call recording is a built-in feature.

Frustratingly, some menu items are not identical across platforms. In trying to troubleshoot issues we were having, ooVoo's tech support page referred to necessary menu entries which existed on OS X, but not on Windows.

In a video conference, ooVoo partitions the window based on how many participants are present. In the default view with two people, the video streams appear as adjacent rectangles. With three people present, the right and left streams are angled in a gratuitous 3D effect. As an alternative, any single stream can be designated to fill the window, with the remaining streams delegated into a single corner.

==Testing ooVoo==

We tested ooVoo as a 3-person team with one person in Weimar and 2 people at separate locations in San Diego. Audio fidelity during conversation was relatively poor, as has come to be expected from internet telephony. All three of us experienced intermittent feedback bursts, where audio with about a half-second of delay would return loudly for a few seconds at a time. ooVoo's automatic gain control didn't have much of an effect on this.

Weimar occasionally experienced bandwidth issues, which ooVoo deals with by automatically dropping the affected video stream, while keeping audio alive.

==Exploring==

We explored latency pragmatically. As an initial experiment, we attempted to clap steadily as a group. This failure found new form in our second attempt, where our hands were kept clearly visible in front of the camera, providing both strong visual and audio cues for timing.

The power of feedback in mediating our group dynamic led us to our next experiment. We decided upon a feedback-based "call and response" exercise that would demonstrate the audio, visual, and perceptual latencies present. Weimar found a way to stream a video file in place of the webcam image, and generated a series of stroboscopic videos displaying a burst of white between lulls of blackness. When darkness fell in San Diego, Weimar began broadcasting. With each flash, Weimar uttered the German word for light, "licht." The San Diegans, from independent locations, monitored Weimar fullscreen. Whenever they witnessed the light of Weimar, they responded in their own native tongues, Spanish and English.

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

2013-04-21T18:52:22Z

Kevin:

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

2013-04-21T18:40:37Z

Kevin:

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

2013-04-21T18:26:20Z

Kevin:

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

2013-04-21T17:58:52Z

Kevin:

ooVoo is a multi-platform video conferencing/chat application that boasts allowing up to 12 simultaneous video streams.

Unlike Skype, ooVoo doesn't make use of peer-to-peer connections, instead relying on some kind of cloud configuration. Apparently because of this, ooVoo's CEO has stated that ooVoo isn't typically used for "scheduled international calls or professional meetings," instead focusing on casual users. Nevertheless, the Washington Post claimed in 2011 that ooVoo had been approved for official communications within the US House of Representatives.

We tested ooVoo as a 3-person team with one person in Weimar and 2 people at separate locations in San Diego.

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

2013-04-21T17:55:40Z

Kevin: Created page with "ooVoo is video conferencing/chat application that boasts allowing up to 12 simultaneous video streams. Unlike Skype, ooVoo doesn't make use of peer-to-peer connections, instead ..."

ooVoo is video conferencing/chat application that boasts allowing up to 12 simultaneous video streams.

Unlike Skype, ooVoo doesn't make use of peer-to-peer connections, instead relying on some kind of cloud configuration. Apparently because of this, ooVoo's CEO has stated that ooVoo isn't typically used for "scheduled international calls or professional meetings," instead focusing on casual users. Nevertheless, the Washington Post claimed in 2011 that ooVoo, along with Skype, was approved for official communications within the US House of Representatives.

EKK:LoFi Sounds in HiFi Spaces/Making connection

2013-04-21T17:32:32Z

Kevin: /* 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/]]
* [[../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/Kevin

2013-04-16T00:04:59Z

Kevin: /* Interests */

Kevin

==Interests==
I'm interested in musical interaction and interface.
I'm generally thinking about how the properties of tools or systems affect how they work.

===My collaboration interest===
I'm interested in capturing gestures and signals and reapplying them (with modifications) as control signals. These signals could be derived from gestural performance, from musical input, from the output of lights/displays/actuators, etc.

==Project Idea==

==Platforms==
I work on OS X, although I'm also interested in mobile/embedded possibilities, so I have a Raspberry Pi and a few Arduinos as well.

Skpye: kevinlofihifi

EKK:LoFi Sounds in HiFi Spaces/Kevin

2013-04-15T19:28:50Z

Kevin: /* Platforms */

Kevin

==Interests==
I'm interested in musical interaction and interface.
I generally think about how systems work from the conceptual side.

===My collaboration interest===
I'm interested in capturing gestures and signals and reapplying them (with modifications) as control signals. These signals could be derived from gestural performance, from musical input, from the output of lights/displays/actuators, etc.

==Project Idea==

==Platforms==
I work on OS X, although I'm also interested in mobile/embedded possibilities, so I have a Raspberry Pi and a few Arduinos as well.

Skpye: kevinlofihifi

EKK:LoFi Sounds in HiFi Spaces/Kevin

2013-04-15T19:27:54Z

Kevin: /* Platforms */

Kevin

==Interests==
I'm interested in musical interaction and interface.
I generally think about how systems work from the conceptual side.

===My collaboration interest===
I'm interested in capturing gestures and signals and reapplying them (with modifications) as control signals. These signals could be derived from gestural performance, from musical input, from the output of lights/displays/actuators, etc.

==Project Idea==

==Platforms==
I work on OS X, although I'm also interested in mobile/embedded applications, so I have a Raspberry Pi and a few Arduinos as well.

Skpye: kevinlofihifi

EKK:LoFi Sounds in HiFi Spaces/Kevin

2013-04-15T19:26:54Z

Kevin: /* Interests */

Kevin

==Interests==
I'm interested in musical interaction and interface.
I generally think about how systems work from the conceptual side.

===My collaboration interest===
I'm interested in capturing gestures and signals and reapplying them (with modifications) as control signals. These signals could be derived from gestural performance, from musical input, from the output of lights/displays/actuators, etc.

==Project Idea==

==Platforms==
I work on OS X, although I have a Raspberry Pi and a few Arduinos as well.

Skpye: kevinlofihifi

EKK:LoFi Sounds in HiFi Spaces/Kevin

2013-04-15T19:26:42Z

Kevin: /* Project Idea */

EKK:LoFi Sounds in HiFi Spaces/Kevin

2013-04-15T19:24:40Z

Kevin: /* Interests */

Kevin

==Interests==
I'm interested in musical interaction and interface.
I generally think about how systems work from the conceptual side.

===My collaboration interest===

==Project Idea==
I'm interested in capturing gestures and signals and reapplying them (with modifications) as control signals. These signals could be derived from gestural performance, from musical input, from the output of lights/displays/actuators, etc.

==Platforms==
I work on OS X, although I have a Raspberry Pi and a few Arduinos as well.

Skpye: kevinlofihifi

EKK:LoFi Sounds in HiFi Spaces/Kevin

2013-04-15T19:09:11Z

Kevin: /* My collaboration interest */

Kevin

==Interests==
I'm interested in musical interaction and interface.

===My collaboration interest===
I generally think about how systems work from the conceptual side.

==Project Idea==
I'm interested in capturing gestures and signals and reapplying them (with modifications) as control signals. These signals could be derived from gestural performance, from musical input, from the output of lights/displays/actuators, etc.

==Platforms==
I work on OS X, although I have a Raspberry Pi and a few Arduinos as well.

Skpye: kevinlofihifi

EKK:LoFi Sounds in HiFi Spaces/Kevin

2013-04-15T19:04:46Z

Kevin: /* Platforms */

Kevin

==Interests==
I'm interested in musical interaction and interface.

===My collaboration interest===
I generally focus on planning how a system should work; developing the conceptual side.

==Project Idea==
I'm interested in capturing gestures and signals and reapplying them (with modifications) as control signals. These signals could be derived from gestural performance, from musical input, from the output of lights/displays/actuators, etc.

==Platforms==
I work on OS X, although I have a Raspberry Pi and a few Arduinos as well.

Skpye: kevinlofihifi

EKK:LoFi Sounds in HiFi Spaces/Kevin

2013-04-15T19:04:13Z

Kevin: /* Platforms */

EKK:LoFi Sounds in HiFi Spaces/Kevin

2013-04-07T19:29:26Z

Kevin:

EKK:LoFi Sounds in HiFi Spaces/Kevin

2013-04-01T18:49:18Z

Kevin:

I'm Kevin.

I work with musical interaction / expressive interfaces.

EKK:LoFi Sounds in HiFi Spaces/Kevin

2013-04-01T18:37:53Z

Kevin: Created page with "I am Kevin!"

I am Kevin!