<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://robust.cs.unm.edu/lib/exe/css.php?s=feed" type="text/css"?>
<rss version="2.0">
    <channel xmlns:g="http://base.google.com/ns/1.0">
        <title>Robust-first Computing Wiki - people:max_ottesen:project</title>
        <description></description>
        <link>https://robust.cs.unm.edu/</link>
        <lastBuildDate>Mon, 20 Jul 2026 09:14:49 +0000</lastBuildDate>
        <generator>FeedCreator 1.8</generator>
        <image>
            <url>https://robust.cs.unm.edu/lib/exe/fetch.php?media=wiki:logo.png</url>
            <title>Robust-first Computing Wiki</title>
            <link>https://robust.cs.unm.edu/</link>
        </image>
        <item>
            <title>crit1</title>
            <link>https://robust.cs.unm.edu/doku.php?id=people:max_ottesen:project:crit1&amp;rev=1410717508</link>
            <description>&lt;pre&gt;
@@ -59,11 +59,16 @@
  
  As of my most recent idea of how this will work, notes will be stationary and will only know their vertical position and whether they are sharp, flat, or natural. Their vertical position in the MFM will be used to determine what pitch they represent. Each vertical step up in the MFM will represent one scale step up.
  
  === Sorter (need a cooler name) ===
+ 
+ == Idea 1 ==
  
  A Sorter will float around the MFM and if it sees a Res, it will either turn it into a Note or into another Sorter. If it sees a Note, it has a probability of moving it based on what the notes around it are and some very basic Music Theory rules (like creating or resolving tension). A Sorter will have to know things like their vertical position (so they know what pitches they are near), the scale/mode that is being used, the time signature that&amp;#039;s being used (not going to touch this for a while), and the tempo (not going to touch this for a while). I might include some other things like how lenient you want the sorter to be with things like tension and dissonance. For the first iteration of this project, all the sorters will be the same. In the future I might want multiple types of sorters all running at once to create some interesting contrast in the music.
  
+ == Idea 2 ==
+ 
+ I could also have two different sorters. One sorter would move up and down, the other would move left to right. The up/down sorter would be focused more on the individual notes on a specific beat sounding good together. It would also be able to see a little bit to the sides to make sure nothing was too out of the ordinary. The left/right sorter would be focused on the overall flow of the music. This is more related to melody/harmony/rhythm, so I would probably save this for later.
  
  ----
  
  

&lt;/pre&gt;</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Sun, 14 Sep 2014 17:58:28 +0000</pubDate>
        </item>
        <item>
            <title>crit2</title>
            <link>https://robust.cs.unm.edu/doku.php?id=people:max_ottesen:project:crit2&amp;rev=1413778776</link>
            <description>&lt;pre&gt;
@@ -11,9 +11,9 @@
  A Note represents a musical pitch. When the Note&amp;#039;s behavior method is called, it checks around itself to verify that its stored pitch and position within the staff are the same. If it is not, it corrects itself.
  
  ==== Composer ====
  
- The Composer is the real guts/brains of this project. It floats around and turns Res into Notes and more Composers. If a Composer finds a Note, it has a chance to move it based on the surrounding notes. Right now, the Composers are trying to build [[http://en.wikipedia.org/wiki/Triad_(music)|triads]]. Triads are groups of 3 notes stacked in intervals of thirds. They are easy to make and sound good, so naturally they seemed like a good starting place.
+ The Composer is the real guts/brains of this project. It floats around and turns Res into Notes and more Composers. If a Composer finds a Note, it has a chance to move it based on the surrounding notes. Right now, the Composers are trying to build [[http://en.wikipedia.org/wiki/Triad_(music)|triads]]. Triads are groups of 3 notes stacked in intervals of thirds. They are easy to make and sound good, so naturally they seemed like the place to start.
  
  
  {{ :people:max_ottesen:project:primary_triads_in_c.png?nolink&amp;amp;200 |}}
  
@@ -32,6 +32,5 @@
  
  ===== Roadblocks =====
  
    * **The MFM universe is big and Event Windows are small**
-   * No distinction between a melody and supporting parts (possibly use more bits to make the distinction)
    * Threading bug(s)

&lt;/pre&gt;</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Mon, 20 Oct 2014 04:19:36 +0000</pubDate>
        </item>
        <item>
            <title>fake_paper</title>
            <link>https://robust.cs.unm.edu/doku.php?id=people:max_ottesen:project:fake_paper&amp;rev=1413737353</link>
            <description>&lt;pre&gt;
@@ -1,10 +1,7 @@
- ====== The Music of Life ======
+ ====== Distributed Composition of Abstract Music ======
  
  
+ ===== Abstract =====
  
- ==== Abstract ====
- 
- 
- 
- ==== (Hoped for) Conclusion ====
+ Music is a form of art previously explored exclusively by humans. With the invention of computers, computer-generated music has become an interesting branch of music to look at. We decided to take the approach of generating music from an artificial life standpoint. We have done this by creating a cellular automaton that runs inside of the Moveable Feast Machine. By varying parameters such as how likely we are to leave dissonant sounds alone, what kind of chords we wish to produce, or the type of musical scale we want to work with, we can listen to the results change and improve over time.
  

&lt;/pre&gt;</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Sun, 19 Oct 2014 16:49:13 +0000</pubDate>
        </item>
        <item>
            <title>paper</title>
            <link>https://robust.cs.unm.edu/doku.php?id=people:max_ottesen:project:paper&amp;rev=1416435205</link>
            <description>&lt;pre&gt;
@@ -24,11 +24,15 @@
  
  
  ===== Figure 1 =====
  
- {{ :people:max_ottesen:project:figure1.png?nolink |}}
- 
+ {{ :people:max_ottesen:project:figure_1.png?nolink |}}
  
  
  ===== Chart 1 =====
  
- {{ :people:max_ottesen:project:chart1.png?nolink |}}
+ {{ :people:max_ottesen:project:chart1_1.png?nolink |}}
+ 
+ 
+ ===== Chart 2 =====
+ 
+ {{ :people:max_ottesen:project:chart2.png?nolink |}}

&lt;/pre&gt;</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Wed, 19 Nov 2014 22:13:25 +0000</pubDate>
        </item>
    </channel>
</rss>
