<?xml version="1.0" encoding="utf-8"?>
<rss version="0.92" xml:base="http://looplog.org">
<channel>
 <title>looplog - issues</title>
 <link>http://looplog.org/project/issues</link>
 <description> Looplog is the product of ongoing work undertaken for my completion of postgraduate studies at Murdoch University. I am an artist researcher working principally in the area of soundscape studies and acoustic ecology but with a strong sense of maintaining the creative commons via the internet. This site and its content is in fairly constant development - it is not a representation of work that I have done but a direct access to work that I am doing - so pages and menus might change around a little. Nonetheless, you can navigate to any of site&#039;s main areas by using the navigation links in the header, nestled in the leaves.
</description>
 <language>en</language>
<item>
 <title>tuning the kernel</title>
 <link>http://looplog.org/node/280</link>
 <description>&lt;p&gt; It&#039;s interesting that the process of optimizing performance of a machine is called tuning. It holds true for automobiles as much as it does for computers designed for audio composition work.
&lt;/p&gt;
&lt;p&gt;Regardless, I&#039;ve been conducting some more tests under Linux to see if I can get stable and reliable performance for a long time frame loop-network system. I was having troubles with the kernel and Jack, the audio routing software, which was leading to audio drop-outs. From here on in it just gets more technical, so if that doesn&#039;t interest you then I bid you farewell.&amp;nbsp; Just take this important message. Without the persistent networks of practice enabled by the internet, I could not in any way have made these refinements, and would remain at a loss as to how to tackle the problems I was having.
&lt;/p&gt;</description>
 <pubDate>Sun, 25 Feb 2007 10:48:28 -0500</pubDate>
 <comments>http://looplog.org/node/280</comments>
 <category>designing the loop network</category>
</item>
<item>
 <title>a new direction</title>
 <link>http://looplog.org/node/204</link>
 <description>&lt;p&gt; Up until now the development of Looplog has been dependent on progress on the initial stages of the learning curve of the software on which Looplog is based. Now that I&#039;ve gotten somewhat of an understanding of what is going on here, I feel I can safely start making a more reconsidered approach to how Looplog works for my practice and how it works as my practice.&amp;nbsp; The upcoming release of Drupal 5 offers a perfect opportunity to do this, as I will have to upgrade the site when this occurs.&amp;nbsp; As such, I think the move to 5.0 will be a big one, but will represent the final incarnation of the site, and subsequently the final representation of my practice, as I head into the assessment stage of my PhD project.
&lt;/p&gt;</description>
 <pubDate>Wed, 15 Nov 2006 12:58:02 -0500</pubDate>
 <comments>http://looplog.org/node/204</comments>
 <category>looplog : a practice network</category>
</item>
<item>
 <title>circulating the loop network</title>
 <link>http://looplog.org/node/265</link>
 <description>&lt;p&gt; Essentially a place for discussing the rationale, design imperatives and function of setting up a podcast for making available audio documentation of the composition experiments of this project. The podcast can then be attached to the project or provided as an external playlist, whichever is easier to manage.
&lt;/p&gt;
&lt;p&gt;This stems for an earlier question and a problem I have been considering for some time.&amp;nbsp; When dealing with multi-channel soundscape systems, and indeed multi-phonic acoustic experiences, how does one mediate those experiences and experiments within a broader circulation network so as to provide a modicum of currency to the work, and of course, receive feedback?
&lt;/p&gt;</description>
 <pubDate>Tue, 13 Feb 2007 13:50:18 -0500</pubDate>
 <comments>http://looplog.org/node/265</comments>
 <category>composing the loop network</category>
</item>
<item>
 <title>bibliography broken</title>
 <link>http://looplog.org/node/272</link>
 <description>It appears in updating the bibliography module to the latest to gain proper author sorting, the database didn&#039;t update correctly.  As a result, the bibliography is kind of messed up at the moment.  So for now, you&#039;ll have to bear with it until I put in some time this weekend to clean everything up.  Once it&#039;s done though, I can being importing bibliographic data en masse, something I have been holding off on doing until the author sorting features had been fully implemented.</description>
 <pubDate>Tue, 20 Feb 2007 13:47:39 -0500</pubDate>
 <comments>http://looplog.org/node/272</comments>
 <category>looplog : a practice network</category>
</item>
<item>
 <title>evaluating multiple operating systems for linux audio</title>
 <link>http://looplog.org/node/257</link>
 <description>I&#039;m currently in the process of deciding which linux distribution I will use as the basis for the loop network. In order to do this, I need to have a single computer setup for multibooting between various distros to compare and contrast. I have used &lt;a href=&quot;http://fedora.redhat.com/&quot;&gt;Fedora Core&lt;/a&gt; since FC1, and prior to that learned what little I know about linux from a Red Hat 7.2 book with included CD that was being sold for blowout price. I have my main internet machine which hosts my tasks database setup with FC5 and the &lt;a href=&quot;http://ccrma.stanford.edu/planetccrma/software/&quot;&gt;Planet CCRMA&lt;/a&gt; low-latency enabled preemptive kernel, which has some really great performance.</description>
 <pubDate>Mon, 05 Feb 2007 13:01:40 -0500</pubDate>
 <comments>http://looplog.org/node/257</comments>
 <category>designing the loop network</category>
</item>
<item>
 <title>acoustic network writing</title>
 <link>http://looplog.org/node/129</link>
 <description>&lt;p&gt; It&#039;s a fancy title to be sure, but it means little more than to refer to the &quot;how&quot; of the writing process. It seems that most writing techniques are heavily visual, especially word-processors which employ composition according to visual blocks of text. I shant be the first, as there is a whole field devoted to data sonification, but one of the uses of the loop network is to investigate writing acoustically. That is, using the loop network and my trusty handheld recording system, I hope to brainstorm aspects of theory using simultaneous spoken (and hence recorded) lines, which will then be reproduced and remixed as a multi-channel soundscape. In the event of remixing, I will transcribe the product, which will be edited and formatted for academic circulation.&amp;nbsp; If anything, this should prove an interesting studio exercise and hence learning experience and I have no doubt it will provide some insight into the theory to be remixed in a way that is fundamentally integrated with the practice I am concerned with.
&lt;/p&gt;</description>
 <pubDate>Mon, 28 Aug 2006 01:26:19 -0400</pubDate>
 <comments>http://looplog.org/node/129</comments>
 <category>composing the loop network</category>
</item>
<item>
 <title>what am I doing with technology?</title>
 <link>http://looplog.org/node/206</link>
 <description>&lt;p&gt;What is it that I am trying to do with technology?
&lt;/p&gt;
&lt;p&gt;Firstly, in the process of building some sort of multi channel dispersion system, I am playing with sound in a very spatial sense.&amp;nbsp; What am I trying to achieve in doing this?&amp;nbsp; Really, what I have always had I&#039;m mind is synthesizing soundscapes indeed the soundscape) from a systemic viewpoint.&amp;nbsp; That is, from a compositional viewpoint I am interested not in producing compositions per se but defining and constructing a system which produces an ongoing soundscape that interrogates the very functional principals of soundscape - the way in which it is created and way in which it is experienced, the way in which it is perceived and the way in which it is recognized.&amp;nbsp; That is, I am looking to setup a system in a space and leave it there such that I can interact with the system in an ongoing manner to learn about the relationship between the functional modes of repetition as they can be employed in a systematic, compositional and constructive manner.&amp;nbsp; The content itself is not of interest so much as is the ability to investigate the modes of repetition through the content and to use the modes of repetition to generate content.
&lt;/p&gt;</description>
 <pubDate>Sun, 26 Nov 2006 13:47:00 -0500</pubDate>
 <comments>http://looplog.org/node/206</comments>
 <category>composing the loop network</category>
</item>
<item>
 <title>multiboot howto</title>
 <link>http://looplog.org/node/258</link>
 <description>Technical details for how to configure grub for multibooting between 3 or 4 linux distros on the same hard drive on the same computer.</description>
 <pubDate>Mon, 05 Feb 2007 13:04:54 -0500</pubDate>
 <comments>http://looplog.org/node/258</comments>
 <category>designing the loop network</category>
</item>
<item>
 <title>import from tasks</title>
 <link>http://looplog.org/node/254</link>
 <description>I&#039;ve just added some nodes to import data from the tasks database on a regular schedule, so it should make the workflow between the two environments run complete.  A quick test run has successfully imported one entry for each of the modes of repetition.  From here on in I can start importing and editing more complete and coherent tasks so that they are updated on the website soon after I have updated them on the computer in the studio.</description>
 <pubDate>Mon, 29 Jan 2007 09:19:55 -0500</pubDate>
 <comments>http://looplog.org/node/254</comments>
 <category>looplog : a practice network</category>
</item>
<item>
 <title>project module modifications</title>
 <link>http://looplog.org/node/9</link>
 <description>the project module is useful in its present form but has some serious shortcomings. the first of these are that it has no way to easily collect a projects components as separate sub-projects. that is to say, whilst a project has components defined at the meta-level, these do not exist as manipulable or displayable objects at the content level. in other words, if the components of a project are defined at the meta-level in the project node, it would be highly useful to organise the project as follows project&amp;gt;components&amp;gt;issues but this still doesn&#039;t solve the problem i have with the soundscape studies project, and that is, the use of the project module is designed to make the process open to criticism and feedback to enable a more [[transparent praxis]].</description>
 <pubDate>Mon, 07 Aug 2006 12:56:35 -0400</pubDate>
 <comments>http://looplog.org/node/9</comments>
 <category>looplog : a practice network</category>
</item>
<item>
 <title>map</title>
 <link>http://looplog.org/node/123</link>
 <description>what is a map?  it is a transcription of a place.  it is also a guide of how to get somewhere.  the latter is the context in which I am using maps in this project.  as such, I have promised a map of the acoustic ecology of the Internet and a map of my daily life.  in the former, it must be said that the goal is the utilisation of the Internet to achieve some of the revolutionary potential within the scope of acoustic ecology.  That is, how are we using the Internet and how can we use the Internet to achieve a goal of social change that integrates the concerns of acoustic ecology in the listed modes of repetition in daily social life.</description>
 <pubDate>Sun, 20 Aug 2006 08:35:29 -0400</pubDate>
 <comments>http://looplog.org/node/123</comments>
 <category>WFAE 2006 Presentation</category>
</item>
<item>
 <title>modify notify module</title>
 <link>http://looplog.org/node/133</link>
 <description>It should be possible to modify the Notify module such that it includes a comment creation link below published content.  One problem I can see in this is that not all node types will have comment functionality - eg issues, which rather have &quot;follow ups&quot;.  Nonetheless, issue nodes also have comment functionality, so the distinction between the two needs to be discerned.</description>
 <pubDate>Tue, 29 Aug 2006 15:23:37 -0400</pubDate>
 <comments>http://looplog.org/node/133</comments>
 <category>looplog : a practice network</category>
</item>
<item>
 <title>compositional tactic</title>
 <link>http://looplog.org/node/32</link>
 <description>simultaneous muting of mainstream at a specific point.  capture sub-loops of stream and disperse the loops throughout the system.  the stream can re-enter the daydream sporadically, in a filtered, processed or time-distorted manner.</description>
 <pubDate>Sun, 16 Jul 2006 04:27:28 -0400</pubDate>
 <comments>http://looplog.org/node/32</comments>
 <category>composing the loop network</category>
</item>
</channel>
</rss>
