<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="wordpress/2.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>

<channel>
	<title>Networked Music Review</title>
	<link>http://transition.turbulence.org/networked_music_review</link>
	<description>Just another WordPress weblog</description>
	<pubDate>Thu, 28 Aug 2008 19:35:17 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.1</generator>
	<language>en</language>
			<item>
		<title>Flocking Orchestra</title>
		<link>http://transition.turbulence.org/networked_music_review/2007/11/05/flocking-orchestra/</link>
		<comments>http://transition.turbulence.org/networked_music_review/2007/11/05/flocking-orchestra/#comments</comments>
		<pubDate>Mon, 05 Nov 2007 22:01:46 +0000</pubDate>
		<dc:creator>jo</dc:creator>
		
		<category><![CDATA[installation]]></category>

		<category><![CDATA[participatory]]></category>

		<category><![CDATA[audio/visual]]></category>

		<category><![CDATA[software]]></category>

		<category><![CDATA[mixed reality]]></category>

		<category><![CDATA[interactive]]></category>

		<category><![CDATA[motion tracking]]></category>

		<category><![CDATA[algorithmic]]></category>

		<category><![CDATA[acoustic]]></category>

		<category><![CDATA[gesture]]></category>

		<category><![CDATA[interface]]></category>

		<category><![CDATA[conductor]]></category>

		<category><![CDATA[3D]]></category>

		<guid isPermaLink="false">http://transition.turbulence.org/networked_music_review/2007/11/05/flocking-orchestra/</guid>
		<description><![CDATA[Flocking Orchestra (aka DT1) by Tatsuo Unemi and Daniel Bisig: DT1 is an interactive installation that employs flocking algorithms to produce music and visuals. The user&#8217;s motions are captured by a video camera and influence the flock&#8217;s behaviour. Each agent moving in a virtual 3D space controls a MIDI instrument whose playing style depends on [...]]]></description>
			<content:encoded><![CDATA[<p><img src='http://transition.turbulence.org/networked_music_review/wp-content/uploads/2007/11/rfo01-640x480.jpg' alt='rfo01-640×480.jpg' /><strong><a href="http://www.intlab.soka.ac.jp/~unemi/1/DT1/">Flocking Orchestra</a></strong> (aka DT1) by <em>Tatsuo Unemi</em> and <em>Daniel Bisig</em>: DT1 is an interactive installation that employs flocking algorithms to produce music and visuals. The user&#8217;s motions are captured by a video camera and influence the flock&#8217;s behaviour. Each agent moving in a virtual 3D space controls a MIDI instrument whose playing style depends on the agent&#8217;s state. In this system, the user acts as a conductor influencing the flock&#8217;s musical activity. In addition to gestural interaction, the acoustic properties of the system can be modified on the fly by using an intuitive GUI. The acoustical and visual output of the system results from the combination of the flock&#8217;s and user&#8217;s behaviour. It therefore creates on the behavioural level a mixing of natural and artificial reality. The system has been designed to run an a variety of different computational configuration ranging from small laptops to exhibition scale installations.</p>
]]></content:encoded>
			<wfw:commentRss>http://transition.turbulence.org/networked_music_review/2007/11/05/flocking-orchestra/feed/</wfw:commentRss>
		</item>
		<item>
		<title>The Conducter Program: Tapper</title>
		<link>http://transition.turbulence.org/networked_music_review/2007/07/30/the-conducter-program-tapper/</link>
		<comments>http://transition.turbulence.org/networked_music_review/2007/07/30/the-conducter-program-tapper/#comments</comments>
		<pubDate>Mon, 30 Jul 2007 15:54:48 +0000</pubDate>
		<dc:creator>helen</dc:creator>
		
		<category><![CDATA[music]]></category>

		<category><![CDATA[history]]></category>

		<category><![CDATA[conductor]]></category>

		<guid isPermaLink="false">http://transition.turbulence.org/networked_music_review/2007/07/30/the-conducter-program-tapper/</guid>
		<description><![CDATA[The Conductor program &#8212; computer-mediated musical performance by Stephen Malinowski.
Introduction: There are many ways people share the responsibility of making music: they can collaborate in composing and performing music, a composer can leave performing to other musicians, a group of musicians can hire a conductor, a performer can rely on an instrument maker to build [...]]]></description>
			<content:encoded><![CDATA[<p><img src='http://transition.turbulence.org/networked_music_review/wp-content/uploads/2007/07/sam2004.gif' alt='sam2004.gif' /><a href="http://www.musanim.com/tapper/">The Conductor program &#8212; computer-mediated musical performance</a> by Stephen Malinowski.</p>
<p>Introduction: There are many ways people share the responsibility of making music: they can collaborate in composing and performing music, a composer can leave performing to other musicians, a group of musicians can hire a conductor, a performer can rely on an instrument maker to build a machine capable of turning musical gestures into sound. A less commonly used way to share musical responsibility is for a machine to be responsible for storing the notes of the score and playing back those notes in the proper order, leaving a human performer with only the responsibilities of the conductor — rhythm, tempo, dynamics, expression, interpretation.  </p>
<p>With the advent of computers and computer music, development of such an approach (which, when implemented with computers, is sometimes called the conductor program) has taken off, with several people experimenting with its possibilities. In this article, I describe some of this work, including my own implementation of the conductor program, Tapper (which is available as freeware ).  My goal is for the article to provide an introduction to the idea of the conductor program and for Tapper to provide an introduction to the experience of doing computer-mediated musical performance. Neither is intended to be comprehensive, but both are works in progress, and I&#8217;m open to suggestions for simplifications, corrections and additions.</p>
<p><strong>Concepts</strong></p>
<p>First let&#8217;s go over some of the concepts.  What is going on when a performer is using the conductor program?  How is using the conductor program different from other things musicians commonly do? How is one implementation of the conductor program different from another? There are a lots of ways to think about these questions. You can ask: What kinds of choices are musicians making? What roles do the computer and human performers play?  What aspects of musical expression are performers responsible for? Where does the acoustic energy come from? Where does the performance energy come from? How tightly is the performance coupled to the performer&#8217;s gestures? What is the relationship between pitch choice, pitch memory, and pitch responsibility? Is a person using the conductor program really performing? &#8230;</p>
<p>Continue reading this article <a href="http://www.musanim.com/tapper/">here</a>. It contains a description of predecessors, from 1800 on. Or download the program <a href="http://www.musanim.com/tapper/">here</a>. It&#8217;s free.</p>
<p>Stephen Malinowski also created the <a href="http://transition.turbulence.org/networked_music_review/2007/06/03/music-animation-machine-midi-player-windows-freeware-for-all-ages/">Music Animation Machine</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://transition.turbulence.org/networked_music_review/2007/07/30/the-conducter-program-tapper/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
