hekeus@1: hekeus@3: %% bare_conf.tex hekeus@3: %% V1.3 hekeus@3: %% 2007/01/11 hekeus@3: %% by Michael Shell hekeus@3: %% See: hekeus@3: %% http://www.michaelshell.org/ hekeus@3: %% for current contact information. hekeus@3: %% hekeus@3: %% This is a skeleton file demonstrating the use of IEEEtran.cls hekeus@3: %% (requires IEEEtran.cls version 1.7 or later) with an IEEE conference paper. hekeus@3: %% hekeus@3: %% Support sites: hekeus@3: %% http://www.michaelshell.org/tex/ieeetran/ hekeus@3: %% http://www.ctan.org/tex-archive/macros/latex/contrib/IEEEtran/ hekeus@3: %% and hekeus@3: %% http://www.ieee.org/ hekeus@3: hekeus@3: %%************************************************************************* hekeus@3: %% Legal Notice: hekeus@3: %% This code is offered as-is without any warranty either expressed or hekeus@3: %% implied; without even the implied warranty of MERCHANTABILITY or hekeus@3: %% FITNESS FOR A PARTICULAR PURPOSE! hekeus@3: %% User assumes all risk. hekeus@3: %% In no event shall IEEE or any contributor to this code be liable for hekeus@3: %% any damages or losses, including, but not limited to, incidental, hekeus@3: %% consequential, or any other damages, resulting from the use or misuse hekeus@3: %% of any information contained here. hekeus@3: %% hekeus@3: %% All comments are the opinions of their respective authors and are not hekeus@3: %% necessarily endorsed by the IEEE. hekeus@3: %% hekeus@3: %% This work is distributed under the LaTeX Project Public License (LPPL) hekeus@3: %% ( http://www.latex-project.org/ ) version 1.3, and may be freely used, hekeus@3: %% distributed and modified. A copy of the LPPL, version 1.3, is included hekeus@3: %% in the base LaTeX documentation of all distributions of LaTeX released hekeus@3: %% 2003/12/01 or later. hekeus@3: %% Retain all contribution notices and credits. hekeus@3: %% ** Modified files should be clearly indicated as such, including ** hekeus@3: %% ** renaming them and changing author support contact information. ** hekeus@3: %% hekeus@3: %% File list of work: IEEEtran.cls, IEEEtran_HOWTO.pdf, bare_adv.tex, hekeus@3: %% bare_conf.tex, bare_jrnl.tex, bare_jrnl_compsoc.tex hekeus@3: %%************************************************************************* hekeus@3: hekeus@3: % *** Authors should verify (and, if needed, correct) their LaTeX system *** hekeus@3: % *** with the testflow diagnostic prior to trusting their LaTeX platform *** hekeus@3: % *** with production work. IEEE's font choices can trigger bugs that do *** hekeus@3: % *** not appear when using other class files. *** hekeus@3: % The testflow support page is at: hekeus@3: % http://www.michaelshell.org/tex/testflow/ hekeus@3: hekeus@3: hekeus@3: hekeus@3: % Note that the a4paper option is mainly intended so that authors in hekeus@3: % countries using A4 can easily print to A4 and see how their papers will hekeus@3: % look in print - the typesetting of the document will not typically be hekeus@3: % affected with changes in paper size (but the bottom and side margins will). hekeus@3: % Use the testflow package mentioned above to verify correct handling of hekeus@3: % both paper sizes by the user's LaTeX system. hekeus@3: % hekeus@3: % Also note that the "draftcls" or "draftclsnofoot", not "draft", option hekeus@3: % should be used if it is desired that the figures are to be displayed in hekeus@3: % draft mode. hekeus@3: % hekeus@3: \documentclass[conference]{IEEEtran} hekeus@3: % Add the compsoc option for Computer Society conferences. hekeus@3: % hekeus@3: % If IEEEtran.cls has not been installed into the LaTeX system files, hekeus@3: % manually specify the path to it like: hekeus@3: % \documentclass[conference]{../sty/IEEEtran} hekeus@3: hekeus@3: hekeus@3: hekeus@3: hekeus@3: hekeus@3: % Some very useful LaTeX packages include: hekeus@3: % (uncomment the ones you want to load) hekeus@3: hekeus@3: hekeus@3: % *** MISC UTILITY PACKAGES *** hekeus@3: % hekeus@3: %\usepackage{ifpdf} hekeus@3: % Heiko Oberdiek's ifpdf.sty is very useful if you need conditional hekeus@3: % compilation based on whether the output is pdf or dvi. hekeus@3: % usage: hekeus@3: % \ifpdf hekeus@3: % % pdf code hekeus@3: % \else hekeus@3: % % dvi code hekeus@3: % \fi hekeus@3: % The latest version of ifpdf.sty can be obtained from: hekeus@3: % http://www.ctan.org/tex-archive/macros/latex/contrib/oberdiek/ hekeus@3: % Also, note that IEEEtran.cls V1.7 and later provides a builtin hekeus@3: % \ifCLASSINFOpdf conditional that works the same way. hekeus@3: % When switching from latex to pdflatex and vice-versa, the compiler may hekeus@3: % have to be run twice to clear warning/error messages. hekeus@3: hekeus@3: hekeus@3: hekeus@3: hekeus@3: hekeus@3: hekeus@3: % *** CITATION PACKAGES *** hekeus@3: % hekeus@3: %\usepackage{cite} hekeus@3: % cite.sty was written by Donald Arseneau hekeus@3: % V1.6 and later of IEEEtran pre-defines the format of the cite.sty package hekeus@3: % \cite{} output to follow that of IEEE. Loading the cite package will hekeus@3: % result in citation numbers being automatically sorted and properly hekeus@3: % "compressed/ranged". e.g., [1], [9], [2], [7], [5], [6] without using hekeus@3: % cite.sty will become [1], [2], [5]--[7], [9] using cite.sty. cite.sty's hekeus@3: % \cite will automatically add leading space, if needed. Use cite.sty's hekeus@3: % noadjust option (cite.sty V3.8 and later) if you want to turn this off. hekeus@3: % cite.sty is already installed on most LaTeX systems. Be sure and use hekeus@3: % version 4.0 (2003-05-27) and later if using hyperref.sty. cite.sty does hekeus@3: % not currently provide for hyperlinked citations. hekeus@3: % The latest version can be obtained at: hekeus@3: % http://www.ctan.org/tex-archive/macros/latex/contrib/cite/ hekeus@3: % The documentation is contained in the cite.sty file itself. hekeus@3: hekeus@3: hekeus@3: hekeus@3: hekeus@3: hekeus@3: hekeus@3: % *** GRAPHICS RELATED PACKAGES *** hekeus@3: % hekeus@3: \ifCLASSINFOpdf hekeus@3: % \usepackage[pdftex]{graphicx} hekeus@3: % declare the path(s) where your graphic files are hekeus@3: % \graphicspath{{../pdf/}{../jpeg/}} hekeus@3: % and their extensions so you won't have to specify these with hekeus@3: % every instance of \includegraphics hekeus@3: % \DeclareGraphicsExtensions{.pdf,.jpeg,.png} hekeus@3: \else hekeus@3: % or other class option (dvipsone, dvipdf, if not using dvips). graphicx hekeus@3: % will default to the driver specified in the system graphics.cfg if no hekeus@3: % driver is specified. hekeus@3: % \usepackage[dvips]{graphicx} hekeus@3: % declare the path(s) where your graphic files are hekeus@3: % \graphicspath{{../eps/}} hekeus@3: % and their extensions so you won't have to specify these with hekeus@3: % every instance of \includegraphics hekeus@3: % \DeclareGraphicsExtensions{.eps} hekeus@3: \fi hekeus@3: % graphicx was written by David Carlisle and Sebastian Rahtz. It is hekeus@3: % required if you want graphics, photos, etc. graphicx.sty is already hekeus@3: % installed on most LaTeX systems. The latest version and documentation can hekeus@3: % be obtained at: hekeus@3: % http://www.ctan.org/tex-archive/macros/latex/required/graphics/ hekeus@3: % Another good source of documentation is "Using Imported Graphics in hekeus@3: % LaTeX2e" by Keith Reckdahl which can be found as epslatex.ps or hekeus@3: % epslatex.pdf at: http://www.ctan.org/tex-archive/info/ hekeus@3: % hekeus@3: % latex, and pdflatex in dvi mode, support graphics in encapsulated hekeus@3: % postscript (.eps) format. pdflatex in pdf mode supports graphics hekeus@3: % in .pdf, .jpeg, .png and .mps (metapost) formats. Users should ensure hekeus@3: % that all non-photo figures use a vector format (.eps, .pdf, .mps) and hekeus@3: % not a bitmapped formats (.jpeg, .png). IEEE frowns on bitmapped formats hekeus@3: % which can result in "jaggedy"/blurry rendering of lines and letters as hekeus@3: % well as large increases in file sizes. hekeus@3: % hekeus@3: % You can find documentation about the pdfTeX application at: hekeus@3: % http://www.tug.org/applications/pdftex hekeus@3: hekeus@3: hekeus@3: hekeus@3: hekeus@3: hekeus@3: % *** MATH PACKAGES *** hekeus@3: % hekeus@3: %\usepackage[cmex10]{amsmath} hekeus@3: % A popular package from the American Mathematical Society that provides hekeus@3: % many useful and powerful commands for dealing with mathematics. If using hekeus@3: % it, be sure to load this package with the cmex10 option to ensure that hekeus@3: % only type 1 fonts will utilized at all point sizes. Without this option, hekeus@3: % it is possible that some math symbols, particularly those within hekeus@3: % footnotes, will be rendered in bitmap form which will result in a hekeus@3: % document that can not be IEEE Xplore compliant! hekeus@3: % hekeus@3: % Also, note that the amsmath package sets \interdisplaylinepenalty to 10000 hekeus@3: % thus preventing page breaks from occurring within multiline equations. Use: hekeus@3: %\interdisplaylinepenalty=2500 hekeus@3: % after loading amsmath to restore such page breaks as IEEEtran.cls normally hekeus@3: % does. amsmath.sty is already installed on most LaTeX systems. The latest hekeus@3: % version and documentation can be obtained at: hekeus@3: % http://www.ctan.org/tex-archive/macros/latex/required/amslatex/math/ hekeus@3: hekeus@3: hekeus@3: hekeus@3: hekeus@3: hekeus@3: % *** SPECIALIZED LIST PACKAGES *** hekeus@3: % hekeus@3: %\usepackage{algorithmic} hekeus@3: % algorithmic.sty was written by Peter Williams and Rogerio Brito. hekeus@3: % This package provides an algorithmic environment fo describing algorithms. hekeus@3: % You can use the algorithmic environment in-text or within a figure hekeus@3: % environment to provide for a floating algorithm. Do NOT use the algorithm hekeus@3: % floating environment provided by algorithm.sty (by the same authors) or hekeus@3: % algorithm2e.sty (by Christophe Fiorio) as IEEE does not use dedicated hekeus@3: % algorithm float types and packages that provide these will not provide hekeus@3: % correct IEEE style captions. The latest version and documentation of hekeus@3: % algorithmic.sty can be obtained at: hekeus@3: % http://www.ctan.org/tex-archive/macros/latex/contrib/algorithms/ hekeus@3: % There is also a support site at: hekeus@3: % http://algorithms.berlios.de/index.html hekeus@3: % Also of interest may be the (relatively newer and more customizable) hekeus@3: % algorithmicx.sty package by Szasz Janos: hekeus@3: % http://www.ctan.org/tex-archive/macros/latex/contrib/algorithmicx/ hekeus@3: hekeus@3: hekeus@3: hekeus@3: hekeus@3: % *** ALIGNMENT PACKAGES *** hekeus@3: % hekeus@3: %\usepackage{array} hekeus@3: % Frank Mittelbach's and David Carlisle's array.sty patches and improves hekeus@3: % the standard LaTeX2e array and tabular environments to provide better hekeus@3: % appearance and additional user controls. As the default LaTeX2e table hekeus@3: % generation code is lacking to the point of almost being broken with hekeus@3: % respect to the quality of the end results, all users are strongly hekeus@3: % advised to use an enhanced (at the very least that provided by array.sty) hekeus@3: % set of table tools. array.sty is already installed on most systems. The hekeus@3: % latest version and documentation can be obtained at: hekeus@3: % http://www.ctan.org/tex-archive/macros/latex/required/tools/ hekeus@3: hekeus@3: hekeus@3: %\usepackage{mdwmath} hekeus@3: %\usepackage{mdwtab} hekeus@3: % Also highly recommended is Mark Wooding's extremely powerful MDW tools, hekeus@3: % especially mdwmath.sty and mdwtab.sty which are used to format equations hekeus@3: % and tables, respectively. The MDWtools set is already installed on most hekeus@3: % LaTeX systems. The lastest version and documentation is available at: hekeus@3: % http://www.ctan.org/tex-archive/macros/latex/contrib/mdwtools/ hekeus@3: hekeus@3: hekeus@3: % IEEEtran contains the IEEEeqnarray family of commands that can be used to hekeus@3: % generate multiline equations as well as matrices, tables, etc., of high hekeus@3: % quality. hekeus@3: hekeus@3: hekeus@3: %\usepackage{eqparbox} hekeus@3: % Also of notable interest is Scott Pakin's eqparbox package for creating hekeus@3: % (automatically sized) equal width boxes - aka "natural width parboxes". hekeus@3: % Available at: hekeus@3: % http://www.ctan.org/tex-archive/macros/latex/contrib/eqparbox/ hekeus@3: hekeus@3: hekeus@3: hekeus@3: hekeus@3: hekeus@3: % *** SUBFIGURE PACKAGES *** hekeus@3: %\usepackage[tight,footnotesize]{subfigure} hekeus@3: % subfigure.sty was written by Steven Douglas Cochran. This package makes it hekeus@3: % easy to put subfigures in your figures. e.g., "Figure 1a and 1b". For IEEE hekeus@3: % work, it is a good idea to load it with the tight package option to reduce hekeus@3: % the amount of white space around the subfigures. subfigure.sty is already hekeus@3: % installed on most LaTeX systems. The latest version and documentation can hekeus@3: % be obtained at: hekeus@3: % http://www.ctan.org/tex-archive/obsolete/macros/latex/contrib/subfigure/ hekeus@3: % subfigure.sty has been superceeded by subfig.sty. hekeus@3: hekeus@3: hekeus@3: hekeus@3: %\usepackage[caption=false]{caption} hekeus@3: %\usepackage[font=footnotesize]{subfig} hekeus@3: % subfig.sty, also written by Steven Douglas Cochran, is the modern hekeus@3: % replacement for subfigure.sty. However, subfig.sty requires and hekeus@3: % automatically loads Axel Sommerfeldt's caption.sty which will override hekeus@3: % IEEEtran.cls handling of captions and this will result in nonIEEE style hekeus@3: % figure/table captions. To prevent this problem, be sure and preload hekeus@3: % caption.sty with its "caption=false" package option. This is will preserve hekeus@3: % IEEEtran.cls handing of captions. Version 1.3 (2005/06/28) and later hekeus@3: % (recommended due to many improvements over 1.2) of subfig.sty supports hekeus@3: % the caption=false option directly: hekeus@3: %\usepackage[caption=false,font=footnotesize]{subfig} hekeus@3: % hekeus@3: % The latest version and documentation can be obtained at: hekeus@3: % http://www.ctan.org/tex-archive/macros/latex/contrib/subfig/ hekeus@3: % The latest version and documentation of caption.sty can be obtained at: hekeus@3: % http://www.ctan.org/tex-archive/macros/latex/contrib/caption/ hekeus@3: hekeus@3: hekeus@3: hekeus@3: hekeus@3: % *** FLOAT PACKAGES *** hekeus@3: % hekeus@3: %\usepackage{fixltx2e} hekeus@3: % fixltx2e, the successor to the earlier fix2col.sty, was written by hekeus@3: % Frank Mittelbach and David Carlisle. This package corrects a few problems hekeus@3: % in the LaTeX2e kernel, the most notable of which is that in current hekeus@3: % LaTeX2e releases, the ordering of single and double column floats is not hekeus@3: % guaranteed to be preserved. Thus, an unpatched LaTeX2e can allow a hekeus@3: % single column figure to be placed prior to an earlier double column hekeus@3: % figure. The latest version and documentation can be found at: hekeus@3: % http://www.ctan.org/tex-archive/macros/latex/base/ hekeus@3: hekeus@3: hekeus@3: hekeus@3: %\usepackage{stfloats} hekeus@3: % stfloats.sty was written by Sigitas Tolusis. This package gives LaTeX2e hekeus@3: % the ability to do double column floats at the bottom of the page as well hekeus@3: % as the top. (e.g., "\begin{figure*}[!b]" is not normally possible in hekeus@3: % LaTeX2e). It also provides a command: hekeus@3: %\fnbelowfloat hekeus@3: % to enable the placement of footnotes below bottom floats (the standard hekeus@3: % LaTeX2e kernel puts them above bottom floats). This is an invasive package hekeus@3: % which rewrites many portions of the LaTeX2e float routines. It may not work hekeus@3: % with other packages that modify the LaTeX2e float routines. The latest hekeus@3: % version and documentation can be obtained at: hekeus@3: % http://www.ctan.org/tex-archive/macros/latex/contrib/sttools/ hekeus@3: % Documentation is contained in the stfloats.sty comments as well as in the hekeus@3: % presfull.pdf file. Do not use the stfloats baselinefloat ability as IEEE hekeus@3: % does not allow \baselineskip to stretch. Authors submitting work to the hekeus@3: % IEEE should note that IEEE rarely uses double column equations and hekeus@3: % that authors should try to avoid such use. Do not be tempted to use the hekeus@3: % cuted.sty or midfloat.sty packages (also by Sigitas Tolusis) as IEEE does hekeus@3: % not format its papers in such ways. hekeus@3: hekeus@3: hekeus@3: hekeus@3: hekeus@3: hekeus@3: % *** PDF, URL AND HYPERLINK PACKAGES *** hekeus@3: % hekeus@3: %\usepackage{url} hekeus@3: % url.sty was written by Donald Arseneau. It provides better support for hekeus@3: % handling and breaking URLs. url.sty is already installed on most LaTeX hekeus@3: % systems. The latest version can be obtained at: hekeus@3: % http://www.ctan.org/tex-archive/macros/latex/contrib/misc/ hekeus@3: % Read the url.sty source comments for usage information. Basically, hekeus@3: % \url{my_url_here}. hekeus@3: hekeus@3: hekeus@3: hekeus@3: hekeus@3: hekeus@3: % *** Do not adjust lengths that control margins, column widths, etc. *** hekeus@3: % *** Do not use packages that alter fonts (such as pslatex). *** hekeus@3: % There should be no need to do such things with IEEEtran.cls V1.6 and later. hekeus@3: % (Unless specifically asked to do so by the journal or conference you plan hekeus@3: % to submit to, of course. ) hekeus@3: hekeus@3: hekeus@1: \begin{document} hekeus@3: \title{Cognitive Music Modelling: An Information Dynamics Approach} hekeus@1: hekeus@3: \author{\IEEEauthorblockN{Samer Abdallah, Henrik Ekeus, Peter Foster, Andrew Robertson, Mark D. Plumbley} hekeus@3: \IEEEauthorblockA{Queen Mary University of London\\Centre for Digital Music\\School of Electronic Engineering and Computer Science\\Email: } hekeus@3: } hekeus@1: hekeus@1: \maketitle hekeus@1: %\setcounter{secnumdepth}{2} hekeus@3: %\setcounter{tocdepth}{2} hekeus@3: %\tableofcontents hekeus@3: \begin{abstract} hekeus@3: People take in information when perceiving music. With it they continually build predictive models of what is going to happen. There is a relationship between information measures and how we perceive music. An information theoretic approach to music cognition is thus a fruitful avenue of research. hekeus@3: \end{abstract} hekeus@1: hekeus@1: hekeus@8: \section{Information Theory and Prediction} hekeus@2: Bayesian probability and modelling the building of predictions hekeus@1: \subsection{Link to music} hekeus@1: Music as a temporal pattern. Meyer, Narmour. Music unfolding in time. How listeners see different kinds of predictability in musical patters.. hekeus@1: \section{Information Dynamics Approach} hekeus@1: hekeus@8: \emph{Re-iterate core hypothesis} hekeus@1: hekeus@1: \subsection{models/parameters/observations} hekeus@8: The grouping of elements into past, present and future.. hekeus@1: \subsection{Information measures} hekeus@1: Predictive information rate as a measure of structure hekeus@1: Cruchfield papers, anatomy of abit hekeus@1: \subsection{Case of this approach being good at modelling music cognition} hekeus@1: Inverted U hekeus@8: hekeus@8: hekeus@8: hekeus@8: \section{Information Dynamics in Analysis} hekeus@1: refer to the work with the analysis of minimalist pieces hekeus@1: hekeus@8: \subsection{Sound Categorisation} Using Information Dynamics it is possible to segment music. From there we can then use this to search large data sets. Determine musical structure for the purpose of playlist navigation and search. (Peter) hekeus@1: hekeus@1: \subsection{Beat Tracking} hekeus@1: Bayesian belief can be used to predict when things happen (as oppose to just what happens). Information Dynamics of? hekeus@1: hekeus@1: hekeus@2: hekeus@8: \section{Information Dynamics as Design Tool} hekeus@6: hekeus@8: In addition to applying Information Dynamics to analysis, it is also possible use this approach in design, such as the composition of musical materials. By providing a framework for linking information theoretic measures to the control of generative processes, it becomes possible to steer the output of these processes to match a criteria defined by these measures. For instance outputs of a stochastic musical process could be filtered to match constraints defined by a set of information theoretic measures. hekeus@6: hekeus@8: The use of stochastic processes for the generation of musical material has been widespread for decades -- Iannis Xenakis applied probabilistic mathematical models to the creation of musical materials, including to the formulation of a theory of Markovian Stochastic Music. However we can use information dynamics measures to explore and interface with such processes at the high and abstract level of expectation, randomness and predictability. The Melody Triangle is such a system. hekeus@8: hekeus@8: \subsection{The Melody Triangle} The Melody Triangle is an exploratory interface for the discovery of melodic content, where the input -- positions within a triangle -- directly map to information theoretic measures associated with the output. The measures are the entropy rate, redundancy and predictive information rate of the random process used to generate the sequence of notes. These are all related to the predictability of the the sequence and as such address the notions of expectation and surprise in the perception of music.\emph{self-plagiarised} hekeus@8: hekeus@2: hekeus@8: Before the Melody Triangle can used, it has to be ÔpopulatedÕ with possible parameter values for the melody generators. These are then plotted in a 3d statistical space of redundancy, entropy rate and predictive information rate. In our case we generated thousands of transition matrixes, representing first-order Markov chains, by a random sampling method. In figure x we see a representation of how these matrixes are distributed in the 3d statistical space; each one of these points corresponds to a transition matrix.\emph{self-plagiarised} hekeus@2: hekeus@8: When we look at the distribution of transition matrixes plotted in this space, we see that it forms an arch shape that is fairly thin. It thus becomes a reasonable approximation to pretend that it is just a sheet in two dimensions; and so we stretch out this curved arc into a flat triangle. It is this triangular sheet that is our ÔMelody TriangleÕ and forms the interface by which the system is controlled. \emph{self-plagiarised} hekeus@2: hekeus@8: When the Melody Triangle is used, regardless of whether it is as a screen based system, or as an interactive installation, it involves a mapping to this statistical space. When the user, through the interface, selects a position within the triangle, the corresponding transition matrix is returned. Figure x shows how the triangle maps to different measures of redundancy, entropy rate and predictive information rate.\emph{self-plagiarised} hekeus@2: hekeus@8: Each corner corresponds to three different extremes of predictability and unpredictability, which could be loosely characterised as ÔperiodicityÕ, ÔnoiseÕ and ÔrepetitionÕ. Melodies from the ÔnoiseÕ corner have no discernible pattern; they have high entropy rate, low predictive information rate and low redundancy. These melodies are essentially totally random. A melody along the ÔperiodicityÕ to ÔrepetitionÕ edge are all deterministic loops that get shorter as we approach the ÔrepetitionÕ corner, until it becomes just one repeating note. It is the areas in between the extremes that provide the more ÔinterestingÕ melodies. That is, those that have some level of unpredictability, but are not completely ran- dom. Or, conversely, that are predictable, but not entirely so. This triangular space allows for an intuitive explorationof expectation and surprise in temporal sequences based on a simple model of how one might guess the next event given the previous one.\emph{self-plagiarised} hekeus@8: hekeus@8: hekeus@8: hekeus@8: Any number of interfaces could be developed for the Melody Triangle. We have developed two; a standard screen based interface where a user moves tokens with a mouse in and around a triangle on screen, and a multi-user interactive installation where a Kinect camera tracks individuals in a space and maps their positions in the space to the triangle. Each visitor would generate a melody, and could collaborate with their co-visitors to generate musical textures -- a playful yet informative way to explore expectation and surprise in music. hekeus@8: hekeus@8: As a screen based interface the Melody Triangle can serve as composition tool. A triangle is drawn on the screen, screen space thus mapped to the statistical space of the Melody Triangle. A number of round tokens, each representing a melody can be dragged in and around the triangle. When a token is dragged into the triangle, the system will start generating the sequence of notes with statistical properties that correspond to its position in the triangle.\emph{self-plagiarised} hekeus@8: hekeus@8: In this mode, the Melody Triangle can be used as a kind of composition assistant for the generation of interesting musical textures and melodies. However unlike other computer aided composition tools or programming environments, here the composer engages with music on the high and abstract level of expectation, randomness and predictability.\emph{self-plagiarised} hekeus@8: hekeus@8: hekeus@8: Additionally the Melody Triangle serves as an effective tool for experimental investigations into musical preference and their relationship to the information dynamics models. hekeus@2: hekeus@8: %As the Melody Triangle essentially operates on a stream of symbols, it it is possible to apply the melody triangle to the design of non-sonic content. hekeus@8: hekeus@8: \section{Musical Preference and Information Dynamics} hekeus@8: We carried out a preliminary study that sought to identify any correlation between aesthetic preference and the information theoretical measures of the Melody Triangle. In this study participants were asked to use the screen based interface but it was simplified so that all they could do was move tokens around. To help discount visual biases, the axes of the triangle would be randomly rearranged for each participant.\emph{self-plagiarised} hekeus@8: hekeus@2: The study was divided in to two parts, the first investigated musical preference with respect to single melodies at different tempos. In the second part of the study, a back- ground melody is playing and the participants are asked to find a second melody that Õworks wellÕ with the background melody. For each participant this was done four times, each with a different background melody from four different areas of the Melody Triangle. For all parts of the study the participants were asked to ÔmarkÕ, by pressing the space bar, whenever they liked what they were hearing.\emph{self-plagiarised} hekeus@8: hekeus@8: \emph{todo - results} hekeus@8: hekeus@8: \section{Information Dynamics as Evaluative Feedback Mechanism} hekeus@8: hekeus@8: \emph{todo - code the info dyn evaluator :) } hekeus@8: hekeus@2: It is possible to use information dynamics measures to develop a kind of `critic' that would evaluate a stream of symbols. For instance we could develop a system to notify us if a stream of symbols is too boring, either because they are too repetitive or too chaotic. This could be used to evaluate both pre-composed streams of symbols, or could even be used to provide real-time feedback in an improvisatory setup. hekeus@2: hekeus@2: \emph{comparable system} Gordon Pask's Musicolor (1953) applied a similar notion of boredom in its design. hekeus@2: The Musicolour would react to audio input through a microphone by flashing coloured lights. Rather than a direct mapping of sound to light, Pask designed the device to be a partner to a performing musician. It would adapt its lighting pattern based on the rhythms and frequencies it would hear, quickly `learning' to flash in time with the music. However Pask endowed the device with the ability to `be bored'; if the rhythmic and frequency content of the input remained the same for too long it would listen for other rhythms and frequencies, only lighting when it heard these. As the Musicolour would `get bored', the musician would have to change and vary their playing, eliciting new and unexpected outputs in trying to keep the Musicolour interested. hekeus@2: hekeus@2: In a similar vain, our \emph{Information Dynamics Critic}(name?) allows for an evaluative measure of an input stream, however containing a more sophisticated notion of boredom that \dots hekeus@8: hekeus@8: hekeus@1: hekeus@1: \section{Conclusion} hekeus@1: hekeus@8: \end{document}