
b@1693: % -----------------------------------------------
b@1693: % Template for SMC 2012
b@1693: % adapted from the template for SMC 2011, which was adapted from that of SMC 2010
b@1693: % -----------------------------------------------
b@1693: 
b@1693: \documentclass{article}
b@1693: \usepackage{smc2015}
b@1693: \usepackage{times}
b@1693: \usepackage{ifpdf}
b@1693: \usepackage[english]{babel}
b@1693: \usepackage{cite}
b@1693: 
b@1672: \hyphenation{Java-script}
b@1672: 
b@1693: %%%%%%%%%%%%%%%%%%%%%%%% Some useful packages %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
b@1693: %%%%%%%%%%%%%%%%%%%%%%%% See related documentation %%%%%%%%%%%%%%%%%%%%%%%%%%
b@1693: %\usepackage{amsmath} % popular packages from Am. Math. Soc. Please use the 
b@1693: %\usepackage{amssymb} % related math environments (split, subequation, cases,
b@1693: %\usepackage{amsfonts}% multline, etc.)
b@1693: %\usepackage{bm}      % Bold Math package, defines the command \bf{}
b@1693: %\usepackage{paralist}% extended list environments
b@1693: %%subfig.sty is the modern replacement for subfigure.sty. However, subfig.sty 
b@1693: %%requires and automatically loads caption.sty which overrides class handling 
b@1693: %%of captions. To prevent this problem, preload caption.sty with caption=false 
b@1693: %\usepackage[caption=false]{caption}
b@1693: %\usepackage[font=footnotesize]{subfig}
b@1693: 
b@1693: 
b@1693: %user defined variables
b@1669: \def\papertitle{WEB AUDIO EVALUATION TOOL: A BROWSER-BASED LISTENING TEST ENVIRONMENT} %?
b@1698: \def\firstauthor{Nicholas Jillings}
b@1698: \def\secondauthor{Brecht De Man}
b@1693: \def\thirdauthor{David Moffat}
b@1693: \def\fourthauthor{Joshua D. Reiss}
b@1693: 
b@1693: % adds the automatic
b@1693: % Saves a lot of ouptut space in PDF... after conversion with the distiller
b@1693: % Delete if you cannot get PS fonts working on your system.
b@1693: 
b@1693: % pdf-tex settings: detect automatically if run by latex or pdflatex
b@1693: \newif\ifpdf
b@1693: \ifx\pdfoutput\relax
b@1693: \else
b@1693:    \ifcase\pdfoutput
b@1693:       \pdffalse
b@1693:    \else
b@1693:       \pdftrue
b@1693: \fi
b@1693: 
b@1693: \ifpdf % compiling with pdflatex
b@1693:   \usepackage[pdftex,
b@1693:     pdftitle={\papertitle},
b@1693:     pdfauthor={\firstauthor, \secondauthor, \thirdauthor},
b@1693:     bookmarksnumbered, % use section numbers with bookmarks
b@1693:     pdfstartview=XYZ % start with zoom=100% instead of full screen; 
b@1693:                      % especially useful if working with a big screen :-)
b@1693:    ]{hyperref}
b@1693:   %\pdfcompresslevel=9
b@1693: 
b@1693:   \usepackage[pdftex]{graphicx}
b@1693:   % declare the path(s) where your graphic files are and their extensions so 
b@1693:   %you won't have to specify these with every instance of \includegraphics
b@1693:   \graphicspath{{./figures/}}
b@1693:   \DeclareGraphicsExtensions{.pdf,.jpeg,.png}
b@1693: 
b@1693:   \usepackage[figure,table]{hypcap}
b@1693: 
b@1693: \else % compiling with latex
b@1693:   \usepackage[dvips,
b@1693:     bookmarksnumbered, % use section numbers with bookmarks
b@1693:     pdfstartview=XYZ % start with zoom=100% instead of full screen
b@1693:   ]{hyperref}  % hyperrefs are active in the pdf file after conversion
b@1693: 
b@1693:   \usepackage[dvips]{epsfig,graphicx}
b@1693:   % declare the path(s) where your graphic files are and their extensions so 
b@1693:   %you won't have to specify these with every instance of \includegraphics
b@1693:   \graphicspath{{./figures/}}
b@1693:   \DeclareGraphicsExtensions{.eps}
b@1693: 
b@1693:   \usepackage[figure,table]{hypcap}
b@1693: \fi
b@1693: 
nickjillings@1721: %set up the hyperref package - make the links black without a surrounding frame
b@1693: \hypersetup{
b@1693:     colorlinks,%
b@1693:     citecolor=black,%
b@1693:     filecolor=black,%
b@1693:     linkcolor=black,%
b@1693:     urlcolor=black
b@1693: }
b@1693: 
b@1693: 
b@1693: % Title.
b@1693: % ------
b@1693: \title{\papertitle}
b@1693: 
b@1693: % Authors
b@1693: % Please note that submissions are NOT anonymous, therefore 
b@1693: % authors' names have to be VISIBLE in your manuscript. 
b@1693: %
b@1693: % Single address
b@1693: % To use with only one author or several with the same address
b@1693: % ---------------
b@1693: %\oneauthor
b@1693: %   {\firstauthor} {Affiliation1 \\ %
b@1693: %     {\tt \href{mailto:author1@smcnetwork.org}{author1@smcnetwork.org}}}
b@1693: 
b@1693: %Two addresses
b@1693: %--------------
b@1693: % \twoauthors
b@1693: %   {\firstauthor} {Affiliation1 \\ %
b@1693: %     {\tt \href{mailto:author1@smcnetwork.org}{author1@smcnetwork.org}}}
b@1693: %   {\secondauthor} {Affiliation2 \\ %
b@1693: %     {\tt \href{mailto:author2@smcnetwork.org}{author2@smcnetwork.org}}}
b@1693: 
b@1698: 
b@1698: 
b@1698: % FIX!!! 
b@1693:  \fourauthors
b@1693:    {\firstauthor} {%Affiliation1 \\
b@1698:      {\tt \href{mailto:b.deman@qmul.ac.uk}{n.g.r.jillings@se14.qmul.ac.uk, }}}
b@1693:    {\secondauthor} {%Affiliation2\\ %
b@1698:      {\tt \href{mailto:n.g.r.jillings@se14.qmul.ac.uk}{\{b.deman,}}}
b@1693:    {\thirdauthor} {%Affiliation3\\ %
b@1698:      {\tt \href{mailto:d.j.moffat@qmul.ac.uk}{d.j.moffat, }}}
b@1693:     {\fourthauthor} {%Affiliation4\\ %
b@1698:      {\tt \href{mailto:joshua.reiss@qmul.ac.uk}{joshua.reiss\}@qmul.ac.uk}}}
b@1693: 
b@1693: % ***************************************** the document starts here ***************
b@1693: \begin{document}
b@1693: %
b@1693: \capstartfalse
b@1693: \maketitle
b@1693: \capstarttrue
b@1693: %
b@1693: \begin{abstract}
nickjillings@1721: New functionality in HTML5, notably its Web Audio API, allows for increasingly powerful applications in the browser. % is this true?
b@1669: Perceptual evaluation tests for audio, where the subject assesses certain qualities of different audio fragments through a graphical user interface and/or text boxes, require playback of audio and rapid switching between different files. % what else? 
b@1669: The advantage of a web application is easy deployment on any platform, without requiring any other application or library, easy storing of results on a server. 
nickjillings@1721: [...] % Need to expand here!
b@1669: %Place your abstract at the top left column on the first page.
b@1669: %Please write about 150-200 words that specifically highlight the purpose of your work,
b@1669: %its context, and provide a brief synopsis of your results.
b@1669: %Avoid equations in this part.\\
b@1669: 
b@1693: \end{abstract}
b@1710: 
b@1710: % TOTAL PAPER: Minimum 4 pages, 6 preferred, max. 8 (6 for demos/posters)\\ 
b@1693: 
b@1693: \section{Introduction}\label{sec:introduction}
b@1693: 
nickjillings@1676: %NICK: examples of what kind of audio applications HTML5 has made possible, with references to publications (or website)\\
nickjillings@1676: 
nickjillings@1721: Perceptual evaluation of audio plays an important role in a wide range of research including audio quality \cite{schoeffler2013impact,repp}, sound synthesis \cite{de2013real,durr2015implementation}, audio effect design \cite{deman2014a}, source separation \cite{uhlereiss}, music and emotion %emotional analysis \cite{song2013b,song2013a}, and many others \cite{friberg2011comparison}.  % codec design? 
b@1714: 
nickjillings@1721: The Web Audio Application Programming Interface is a high-level JavaScript API designed for real-time processing of audio inside the browser through various processing nodes \cite{webaudioapi}. Various web sites have used the Web Audio API for either creative purposes, such as drum machines and score creation tools \cite{webaudiodemo}, %http://webaudio.github.io/demo-list/
nickjillings@1676: others from the list show real-time captured audio processing such as room reverberation tools and a phase vocoder from the system microphone. The BBC Radiophonic Workshop shows effects used on famous TV shows such as Doctor Who, being simulated inside the browser \cite{bbcradiophonics}. %http://webaudio.prototyping.bbc.co.uk/
nickjillings@1721: Another example is the BBC R\&D personalised compressor which applies a dynamic range compressor on a radio station that dynamically adjusts the compressor settings to match the listener's environment \cite{mason2015compression}. 
b@1710: 
b@1714: This work is based in part on the APE audio perceptual evaluation interface for MATLAB \cite{deman2014b}. An important drawback of this toolbox is the need to have MATLAB to create a test and even to run (barring the use of an executable generated by MATLAB), and limited compatibility with both earlier and newer versions of MATLAB, which makes it hard to maintain. On the other hand, a web application generally has the advantage of running in most browsers on most applications, and we present a tool that requires no specialised software or even programming knowledge to set up. 
b@1712: 
b@1720: % IMPORTANT
b@1720: %[TO ADD: other interfaces for perceptual evaluation of audio, browser-based or not!] \\
b@1720: %BROWSER-BASED: \cite{song2013b,song2013a,beaqlejs} \\
b@1720: %MATLAB: \cite{whisper,mushram,scale}  
b@1720: % to add: OPAQUE, Rumsey's repertory grid technique
b@1720: 
b@1720: Many perceptual audio interfaces are already available, such as the MATLAB-based tools MUSHRAM \cite{mushram}, WhisPER \cite{whisper}, and Scale \cite{scale}, and the browser-based tool used in \cite{song2013a,song2013b} and BeaqleJS \cite{beaqlejs}. The latter makes use of the HTML5 audio capabilities and comes with a number of predefined, established test interfaces such as ABX and MUSHRA \cite{mushra}. 
nickjillings@1721: In this paper, we provide a listening test back end that allows for easy set up of a wide variety of listening tests, highly flexible yet very simple and not requiring any programming skills. 
b@1720: % [How is this one different from all these?] improve
b@1717: 
b@1717: We present a browser-based perceptual evaluation tool from which any kind of multiple stimulus audio evaluation tool where subjects need to rank, rate, select, or comment on different audio samples can be built. 
nickjillings@1721: We also include an example of the multiple stimulus user interface included with the APE tool \cite{deman2014b}, which presents the subject with a number of axes on which a number of markers, corresponding to audio samples, can be moved to reflect any subjective quality, as well as corresponding comment boxes. 
b@1717: However, other graphical user interfaces can be put on top of the engine that we provide with minimal or no modifications. Examples of this are the MUSHRA test \cite{mushra}, single or multiple stimulus evaluation with a two-dimensional interface (such as valence and arousal dimensions), or simple annotation (using free-form text, check boxes, radio buttons or drop-down menus) of one or more audio samples at a time. 
nickjillings@1721: In some cases, such as method of adjustment, where the audio is processed by the user \cite{bech}, or AB test \cite{bech}, where the interface does not show all audio samples to be evaluated at once, the back end of the tool needs to be modified as well. 
b@1717: 
nickjillings@1721: There are a number of advantages to building a web audio based listening test environment. The ability to easily deploy a flexible and scalable testing environment that requires no proprietary software to run makes the web audio evaluation tool a very flexible testing tool. The ability to host a single test server and create multiple clients not only allows multiple participants to be involved in a trial simultaneously, but also permits participants to be located anywhere in the world. There are also less user experience issues, since all users should have some experience with using existing web technologies.
b@1712: 
b@1720: In the following sections, we describe the included interface in more detail, discuss the implementation, and cover considerations that were made in the design process of this tool. 
b@1698: 
b@1714: \section{Interface}\label{sec:interface}
b@1698: 
nickjillings@1721: At this point, we have implemented the interface of the MATLAB-based APE (Audio Perceptual Evaluation) toolbox \cite{deman2014b}. This shows one marker for each simultaneously evaluated audio fragment on one or more horizontal axes, that can be moved to rate or rank the respective fragments in terms of any subjective quality, as well as a comment box for every marker, and any extra text boxes for extra comments. 
nickjillings@1721: The reason for such an interface, where all stimuli are presented on a single rating axis (or multiple axes if multiple subjective qualities need to be evaluated), is that it urges the subject to consider the rating and/or ranking of the stimuli relative to one another, as opposed to comparing each individual stimulus to a given reference, as is the case with e.g. a MUSHRA test \cite{mushra}. See \ref{fig:interface} for an example of the interface, with eleven fragments and one axis. %? change if a new interface is shown
b@1717: 
b@1720: However, the back end of this test environment allows for many more established and novel interfaces for listening tests, particularly ones where the subject only assesses audio without manipulating it (i.e. method of adjustment), which would require additional features to be implemented. 
b@1641: 
djmoffat@1719: \begin{figure*}[ht]
b@1712: \begin{center}
b@1712: \includegraphics[width=0.9\textwidth]{interface.png}
djmoffat@1713: \caption{Example of interface, with 1 axis and 11 fragments}
b@1712: \label{fig:interface}
b@1712: \end{center}
b@1712: \end{figure*}
djmoffat@1719: 
djmoffat@1719: 
b@1714: \section{Architecture}\label{sec:architecture} % or implementation? 
b@1714: 
nickjillings@1721: The tool runs entirely inside the browser through the new HTML5 Web Audio API and is supported by most major web browsers. The API allows for constructing audio processing elements and connecting them together to produce a high quality, real time signal process to manipulate audio streams. The API supports multichannel processing and has an accurate playback timer for precise scheduled playback control. The API is controlled through the browser JavaScript engine and is therefore highly configurable. Processing is all performed in a separate, low latency thread to the main JavaScript thread, so there is no blocking due to real time processing. 
nickjillings@1700: 
nickjillings@1700: The web tool itself is split into several files to operate:
nickjillings@1700: \begin{itemize}
nickjillings@1679: \item \texttt{index.html}: The main index file to load the scripts, this is the file the browser must request to load.
nickjillings@1679: \item \texttt{core.js}: Contains functions and objects to define the audio objects, audio playback engine and loading media files
nickjillings@1721: \item \texttt{ape.js}: Parses set up files to create the interface as instructed, following the same style chain as the MATLAB APE Tool \cite{deman2014b}.
nickjillings@1700: \end{itemize}
nickjillings@1700: 
nickjillings@1721: The HTML file loads the \texttt{core.js} file along with a few other ancillary files (such as the jQuery JavaScript extensions \cite{jquery}), at which point the browser JavaScript begins to execute the on-page instructions, which gives the URL of the test set up XML document (outlined in Section \ref{sec:setupresultsformats}). \texttt{core.js} parses this document and executes the function in \texttt{ape.js} to build the web page with the given audio files. The reason for separating these two files is to allow for further interface designs (such as MUSHRA \cite{mushra} or AB tests \cite{bech}) to be used, which would still require the same underlying core functions outlined in \texttt{core.js}, see also Section \ref{sec:interface}.
nickjillings@1700: 
nickjillings@1721: The \texttt{ape.js} file has several main functions but the most important are \textit{loadInterface(xmlDoc)}, \textit{loadTest(id)}, \textit{pageXMLSave(testId)} and \textit{interfaceXMLSave()}. \textit{loadInterface(xmlDoc)} is called to decode the supplied project document in respect for the interface specified and define any global structures (such as the slider interface). It also identifies the number of pages in the test and randomises the order, if specified to do so. This is the only madatory function in any of the interface files as this is called by \texttt{core.js} when the document is ready. The design style is such that \texttt{core.js} cannot 'see' any interface specific functions and therefore cannot assume any are available. Therefore the \textit{loadInterface(xmlDoc)} is very important to set up the entire test environment. It can be assumed that the interface files can `see' the \texttt{core.js} file and can therefore not only interact with it, but also modify it.
b@1717: 
nickjillings@1721: Each test page is loaded using \textit{loadTest(id)} which performs two major tasks: to populate the interface with the slider elements and comment boxes; and secondly to instruct the \textit{audioEngine} to load the audio fragments and construct the backend audio graph. The markers on the slider at the top of the page are positioned randomly, to minimise the bias that may be introduced when the initial positions are near the beginning, end or middle of the slider. Another approach is to place the markers outside of the slider bar at first and have the subject drag them in, but the authors believe this doesn't encourage careful consideration and comparison of the different fragments as the implicit goal of the test becomes to audition and drag each fragment in just once, rather than to compare all fragments rigorously.
b@1717: 
b@1717: \textit{loadTest(id)} in \texttt{ape.js} also instructs the audio engine in \texttt{core.js} to create the \textit{audioObject} These are custom audio nodes, one representing each audio element specified in each page.
nickjillings@1679: They consist of a \textit{bufferSourceNode} (a node which holds a buffer of audio samples for playback) and a \textit{gainNode}. There are various functions applied depending on metric collection which record the interaction with the audio element. These nodes are then connected to the \textit{audioEngine} (itself a custom web audio node) containing a \textit{gainNode} (where the various \textit{audioObject} connect to) for summation before passing the output to the \textit{destinationNode}, a permanent fixed node of the Web Audio API created as the master output where the browser then passes the audio information to the system sound device. % Does this now make sense?
nickjillings@1679: % audio object/audioObject/Audio Object: -- should always be audioObject if talking about the JavaScript object, otherwise should say audio element or audio fragment.
b@1717: 
nickjillings@1679: When an \textit{audioObject} is created, it is given the URL of the audio sample to load. This is downloaded into the browser asynchronously using the \textit{XMLHttpRequest} object. This downloads any file into the JavaScript environment for further processing which is particularly useful for the Web Audio API because it supports downloading of files in their binary form for decoding. Once downloaded the file is decoded using the Web Audio API offline decoder. This uses the browser available decoding schemes to decode the audio files into raw float32 arrays, which are in turn passed to the relevant \textit{audioObject} for playback.
nickjillings@1679: 
nickjillings@1679: Once each page of the test is completed, identified by pressing the Submit button, the \textit{pageXMLSave(testId)} is called to store all of the collected data until all pages of the test are completed. After the final test and any post-test questions are completed, the \textit{interfaceXMLSave()} function is called. This function generates the final XML file for submission as outlined in Section \ref{sec:setupresultsformats}.
nickjillings@1679: 
nickjillings@1679: Browsers support various audio file formats and are not consistent in any format. Currently the Web Audio API is best supported in Chrome, Firefox, Opera and Safari. All of these support the use of the uncompressed WAV format. Although not a compact, web friendly format, most transport systems are of a high enough bandwidth this should not be a problem. Ogg Vorbis is another well supported format across the 4 supported major desktop browsers, as well as MP3 (although Firefox may not support all MP3 types) \cite{mozdevSupportedMedia}. %https://developer.mozilla.org/en-US/docs/Web/HTML/Supported_media_formats
nickjillings@1679: One issue of the Web Audio API is that the sample rate is assigned by the system sound device, rather than requested and does not have the ability to request a different one. % Does this make sense? The problem is across all audio files.
nickjillings@1721:  Therefore, the default operation when an audio file is loaded with a different sample rate to that of the system is to convert the sample rate. To provide a check for this, the desired sample rate can be supplied with the set up XML and checked against. If the sample rates do not match, a browser alert window is shown asking for the sample rate to be correctly adjusted. 
b@1717: As this happens before any loading or decoding of audio files, the system will only fetch files as soon as the system's sample rate meets any requirements, avoiding requests for large files until they are actually needed.
b@1717: 
b@1717: %During playback, the playback nodes loop indefinitely until playback is stopped. The gain nodes in the \textit{audioObject}s enable dynamic muting of nodes. When a bar in the sliding ranking is clicked, the audio engine mutes all \textit{audioObject}s and un-mutes the clicked one. Therefore, if the audio samples are perfectly aligned up and of the same sample length, they will remain perfectly aligned with each other.
b@1717: % Don't think this is relevant anymore
b@1717: 
b@1720: \section{Input and result files}\label{sec:setupresultsformats}
b@1717: 
nickjillings@1721: The set up and result files both use the common XML document format to outline the various parameters. The set up file determines which interface to use, the location of audio files, how many pages and other general set up rules to define the testing environment. Having one document to modify allows for quick manipulation in a `human readable' form to create new tests, or adjust current ones, without needing to edit multiple web files. An example of this XML document is presented in Figure~\ref{fig:xmlIn}% I mean the .js and .html files, though not sure if any better.
b@1717: 
nickjillings@1721: \subsection{set up and configurability}
b@1717: 
djmoffat@1719: \begin{figure}[ht]
djmoffat@1719: \begin{center}
djmoffat@1719: \includegraphics[width=0.5\textwidth]{XMLInput.png}
djmoffat@1719: \caption{An Example Input XML File}
djmoffat@1719: \label{fig:xmlIn}
djmoffat@1719: \end{center}
djmoffat@1719: \end{figure}
b@1717: 
nickjillings@1721: The set up document has several defined nodes and structure which are documented with the source code. For example there is a section for general set up options where the pre-test and post-test questions and statements are set up and from the example in Figure~\ref{fig:xmlIn}, it can be seen that a question box should be generated, with the id 'location' and it is mandatory to answer. The question is in the PreTest node meaning it will appear before any testing will begin. When the result for the  entire test is shown, then this will appear in the PreTest node of the response with the id 'location' allowing it to be found easily. This outlines the importance of having clear and meaningful ID values. Pre- and post-test dialog boxes allow for comments or questions to be presented before or after the test, to convey listening test instructions, gather information about the subject, listening environment, and overall experience of the test.
b@1717:  
b@1717: 
b@1720: We try to cater to a diverse audience with this toolbox, while ensuring the toolbox is simple, elegant and straightforward. To that end, we include the following options that can be easily switched on and off, by setting the value in the input XML file. 
b@1717: 
djmoffat@1719: \begin{itemize} %Should have used a description list for this.
b@1717: \item \textbf{Snap to corresponding position}: When this is enabled, and a fragment is playing, the playhead skips to the same position in the next fragment that is clicked. If it is not enabled, every fragment is played from the start. 
b@1717: \item \textbf{Loop fragments}: Repeat current fragment when end is reached, until the `Stop audio' or `Submit' button is clicked. 
b@1717: \item \textbf{Comments}: Displays a separate comment box for each fragment in the page.
b@1717: \item \textbf{General comment}: One comment box, additional to the individual comment boxes, to comment on the test or a feature that some or all of the fragments share. 
b@1717: \item \textbf{Resampling}: When this is enabled, tracks are resampled to match the subject's system's sample rate (a default feature of the Web Audio API). When it is not, an error is shown when the system does not match the requested sample rate. 
b@1717: \item \textbf{Randomise page order}: Randomises the order in which different `pages' are presented. % are we calling this 'pages'?
b@1717: \item \textbf{Randomise fragment order}: Randomises the order and numbering of the markers and comment boxes corresponding with the fragments. This permutation is stored as well, to be able to interpret references to the numbers in the comments (such as `this is much [brighter] then 4'). 
b@1717: \item \textbf{Require playback}: Require that each fragment has been played at least once, if not in full. 
b@1717: \item \textbf{Require full playback}: If `Require playback' is active, require that each fragment has been played in full. 
b@1717: \item \textbf{Require moving}: Require that each marker is moved (dragged) at least once. 
b@1717: \item \textbf{Require comments}: This option allows requiring the subject to require a comment for each track. 
nickjillings@1721: \item \textbf{Repeat test}: Number of times test should be repeated (none by default), to allow familiarisation with the content and experiment, and to investigate consistency of user and variability due to familiarity. In the set up, each 'page' can be given a repeat count. These are all gathered before shuffling the order so repeated tests are not back-to-back if possible.
b@1717: \item \textbf{Returning to previous pages}: Indicates whether it is possible to go back to a previous `page' in the test. 
b@1717: \item \textbf{Lowest rating below [value]}: To enforce a certain use of the rating scale, it can be required to rate at least one sample below a specified value. 
b@1717: \item \textbf{Highest rating above [value]}: To enforce a certain use of the rating scale, it can be required to rate at least one sample above a specified value. 
b@1717: \item \textbf{Reference}: Allows for a separate sample (outside of the axis) to be the `reference', which the subject can play back during the test to help with the task at hand \cite{mushra}. 
b@1717: \item \textbf{Hidden reference}: Whether or not an explicit `reference' is provided, the `hidden reference' should be rated above a certain value \cite{mushra} - this can be enforced. 
b@1717: \item \textbf{Hidden anchor}: The `hidden anchor' should be rated lower than a certain value \cite{mushra} - this can be enforced. 
b@1717: \end{itemize}
b@1717: 
nickjillings@1721: When one of these options is not included in the set up file, they assume a default value. As a result, the input file can be kept very compact if default values suffice for the test.  
b@1717: 
b@1717: % loop, snap to corresponding position, comments, 'general' comment, require same sampling rate, different types of randomisation
b@1717: 
b@1720: \subsection{Results}
b@1720: 
nickjillings@1721: The results file is dynamically generated by the interface upon clicking the `Submit' button. This also executes checks, depending on the set up file, to ensure that all tracks have been played back, rated and commented on. The XML output returned contains a node per audioObject and contains both the corresponding marker's position and any comments written in the associated comment box. The rating returned is normalised to be a value between 0 and 1, normalising the pixel representation of different browser windows. An example output file is presented in Figure~\ref{fig:xmlOut}
djmoffat@1719: 
djmoffat@1719: \begin{figure}[ht]
djmoffat@1719: \begin{center}
djmoffat@1719: \includegraphics[width=0.5\textwidth]{XMLOutput.png}
djmoffat@1719: \caption{An Example Output XML File}
djmoffat@1719: \label{fig:xmlOut}
djmoffat@1719: \end{center}
djmoffat@1719: \end{figure}
b@1717: 
nickjillings@1722: The results also contain information collected by any defined pre/post questions. These are referenced against the set up XML by using the same ID so readable responses can be obtained. Taking from the earlier example of setting up a pre-test question, an example response can be seen in Figure \label{fig:xmlOut}.
b@1717: 
b@1720: Each page of testing is returned with the results of the entire page included in the structure. One `audioElement' node is created per audio fragment per page, along with its ID. This includes several child nodes including the value holding the rating between 0 and 1, the comment, and any other collected metrics. The latter include how long the element was listened for, the initial position, boolean flags if the element was listened to, if the element was moved and if the element comment box had any comment. Furthermore, each user action (manipulation of any interface element, such as playback or moving a marker) is logged along with a the corresponding time code and stored or sent along with the results.
b@1720: Furthermore, we also store session data such as the browser the tool was used in. 
b@1717: 
b@1720: We provide the option to store the results locally, and/or to have them sent to a server. 
b@1717: 
nickjillings@1721: %Here is an example of the set up XML and the results XML: % perhaps best to refer to each XML after each section (set up <> results)
b@1717: % Should we include an Example of the input and output XML structure?? --> Sure. 
b@1717: 
djmoffat@1719: %An example of the returned \textit{audioElement} node in the results XML file is as follows.
djmoffat@1719: %
djmoffat@1719: %\texttt{<audioelement id="8"> \\
djmoffat@1719: %<comment> \\
djmoffat@1719: %<question>Comment on track 0</question> \\
djmoffat@1719: %<response> The drums were punchy </response> \\
djmoffat@1719: %</comment> \\
djmoffat@1719: %<value> 0.25169491525423726 </value> \\
djmoffat@1719: %<metric> \\
djmoffat@1719: %<metricresult id="elementTimer"> \\ 2.3278004535147385< /metricresult> \\
djmoffat@1719: %<metricresult id="elementTrackerFull"> \\
djmoffat@1719: %<timepos id="0"> \\
djmoffat@1719: %<time>1.7937414965986385</time> \\
djmoffat@1719: %<position>0.41694915254237286</position> \\
djmoffat@1719: %</timepos> \\
djmoffat@1719: %<timepos id="1"> \\
djmoffat@1719: %<time>2.6993197278911563</time> \\
djmoffat@1719: %<position>0.45847457627118643</position> \\
djmoffat@1719: %</timepos> \\</metricresult> \\
djmoffat@1719: %<metricresult id="elementInitialPosition"> 0.47796610169491527 </metricresult> \\
djmoffat@1719: %<metricresult id="elementFlagListenedTo"> true< /metricresult> \\
djmoffat@1719: %<metricresult id="elementFlagMoved"> true </metricresult> \\
djmoffat@1719: %</metric> \\
djmoffat@1719: %</audioelement>}
b@1717: 
nickjillings@1721: As can be seen from Figure~\ref{fig:xmlOut}, the parent tag \texttt{audioelement} holds the id of the element passed in from the set up document. The first child element is \texttt{comment} and holds both the question shown and the response from the comment box inside. 
b@1717: The child element \texttt{value} holds the normalised ranking value. Next comes the metric node structure, there is one \texttt{metricresult} node per metric event collected. The id of the node identifies the type of data it contains. For example, the first holds the id \textit{elementTimer} and the data contained represents how long, in seconds, the audio element was listened to. The next holds the id \textit{elementTrackerFull} and contains a pair of elements per entry. This represents the entire movement of the elements' slider giving the time the event took place in seconds from when the current test page started, and the new position. In our example there are three \texttt{timepos} children with their id representing their order. There is one of these \texttt{audioelement} tags per audio element outlined on each test page. 
b@1717: 
b@1720: 
b@1717: \section{Conclusions and future work}\label{sec:conclusions}
b@1717: 
b@1717: In this paper we have presented an approach to creating a browser-based listening test environment that can be used for a variety of types of perceptual evaluation of audio. 
b@1717: Specifically, we discussed the use of the toolbox in the context of assessment of preference for different production practices, with identical source material. 
b@1717: The purpose of this paper is to outline the design of this tool, to describe our implementation using basic HTML5 functionality, and to discuss design challenges and limitations of our approach. % or something
b@1717: 
b@1717: % future work
b@1720: Further work may include the development of other common test designs, such as MUSHRA \cite{mushra}, 2D valence and arousal rating, and others. We will add functionality to assist with setting up large-scale tests with remote subjects, so this becomes straightforward and intuitive. 
b@1720: In addition, we will keep on improving and expanding the tool, and highly welcome feedback and contributions from the community. 
b@1717: 
b@1717: The source code of this tool can be found on \url{code.soundsoftware.ac.uk/projects/webaudioevaluationtool}. 
b@1717: 
b@1717: 
b@1717: %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
b@1717: %bibliography here
b@1717: \bibliography{smc2015template}
b@1717: 
b@1717: \end{document}




