Mercurial > hg > webaudioevaluationtool

changeset 694:869ed636f7c0

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Edit to project Spec Doc
author Dave Moffat <djmoffat@users.noreply.github.com>
date Thu, 09 Apr 2015 16:30:08 +0100
parents a74cb47e779c
children b95d1ede4c91
files ape.js core.js docs/ProjectSpecificationDocument.pdf docs/ProjectSpecificationDocument.tex docs/ResultsSpecificationDocument.pdf docs/ResultsSpecificationDocument.tex docs/SMC15/smc2015template.tex example_eval/project.xml
diffstat 8 files changed, 296 insertions(+), 44 deletions(-) [+]
line wrap: on
line diff
--- a/ape.js	Thu Apr 09 12:59:46 2015 +0100
+++ b/ape.js	Thu Apr 09 16:30:08 2015 +0100
@@ -17,6 +17,8 @@
 	
 	// The injection point into the HTML page
 	var insertPoint = document.getElementById("topLevelBody");
+	var testContent = document.createElement('div');
+	testContent.id = 'testContent';
 	
 	
 	// Decode parts of the xmlDoc that are needed
@@ -33,9 +35,9 @@
 	
 	// Set title to that defined in XML, else set to default
 	if (titleAttr != undefined) {
-		titleSpan.innerText = titleAttr.value;
+		titleSpan.innerHTML = titleAttr.value;
 	} else {
-		titleSpan.innerText =  'APE Tool';
+		titleSpan.innerHTML =  'APE Tool';
 	}
 	// Insert the titleSpan element into the title div element.
 	title.appendChild(titleSpan);
@@ -54,21 +56,21 @@
 	
 	// Create playback start/stop points
 	var playback = document.createElement("button");
-	playback.innerText = 'Start';
+	playback.innerHTML = 'Start';
 	// onclick function. Check if it is playing or not, call the correct function in the
 	// audioEngine, change the button text to reflect the next state.
 	playback.onclick = function() {
 		if (audioEngineContext.status == 0) {
 			audioEngineContext.play();
-			this.innerText = 'Stop';
+			this.innerHTML = 'Stop';
 		} else {
 			audioEngineContext.stop();
-			this.innerText = 'Start';
+			this.innerHTML = 'Start';
 		}
 	};
 	// Create Submit (save) button
 	var submit = document.createElement("button");
-	submit.innerText = 'Submit';
+	submit.innerHTML = 'Submit';
 	submit.onclick = function() {
 		// TODO: Update this for postTest tags
 		createProjectSave(projectReturn)
@@ -136,7 +138,7 @@
 		var trackComment = document.createElement('div');
 		// Create a string next to each comment asking for a comment
 		var trackString = document.createElement('span');
-		trackString.innerText = 'Comment on track '+index;
+		trackString.innerHTML = 'Comment on track '+index;
 		// Create the HTML5 comment box 'textarea'
 		var trackCommentBox = document.createElement('textarea');
 		trackCommentBox.rows = '4';
@@ -177,12 +179,118 @@
 	});
 	
 	
+	// Create pre and post test questions
+	
 	// Inject into HTML
 	insertPoint.innerHTML = null; // Clear the current schema
-	insertPoint.appendChild(title); // Insert the title
-	insertPoint.appendChild(interfaceButtons);
-	insertPoint.appendChild(sliderBox);
-	insertPoint.appendChild(feedbackHolder);
+	testContent.appendChild(title); // Insert the title
+	testContent.appendChild(interfaceButtons);
+	testContent.appendChild(sliderBox);
+	testContent.appendChild(feedbackHolder);
+	insertPoint.appendChild(testContent);
+	
+	var preTest = xmlDoc.find('PreTest');
+	var postTest = xmlDoc.find('PostTest');
+	preTest = preTest[0];
+	postTest = postTest[0];
+	if (preTest != undefined || postTest != undefined)
+	{
+		testContent.style.zIndex = 1;
+		var blank = document.createElement('div');
+		blank.id = 'testHalt';
+		blank.style.zIndex = 2;
+		blank.style.width = window.innerWidth + 'px';
+		blank.style.height = window.innerHeight + 'px';
+		blank.style.position = 'absolute';
+		blank.style.top = '0';
+		blank.style.left = '0';
+		insertPoint.appendChild(blank);
+	}
+	
+	// Create Pre-Test Box
+	if (preTest != undefined && preTest.children.length >= 1)
+	{
+		
+		var preTestHolder = document.createElement('div');
+		preTestHolder.id = 'preTestHolder';
+		preTestHolder.style.zIndex = 2;
+		preTestHolder.style.width = '500px';
+		preTestHolder.style.height = '250px';
+		preTestHolder.style.backgroundColor = '#fff';
+		preTestHolder.style.position = 'absolute';
+		preTestHolder.style.left = (window.innerWidth/2)-250 + 'px';
+		preTestHolder.style.top = (window.innerHeight/2)-125 + 'px';
+		// Parse the first box
+		var preTestOption = document.createElement('div');
+		preTestOption.id = 'preTest';
+		preTestOption.style.marginTop = '25px';
+		preTestOption.align = "center";
+		var child = preTest.children[0];
+		if (child.nodeName == 'statement')
+		{
+			preTestOption.innerHTML = '<span>'+child.innerHTML+'</span>';
+		} else if (child.nodeName == 'question')
+		{
+			var questionId = child.attributes['id'].value;
+			var textHold = document.createElement('span');
+			textHold.innerHTML = child.innerHTML;
+			textHold.id = questionId + 'response';
+			var textEnter = document.createElement('textarea');
+			preTestOption.appendChild(textHold);
+			preTestOption.appendChild(textEnter);
+		}
+		var nextButton = document.createElement('button');
+		nextButton.id = 'preTestNext';
+		nextButton.value = '1';
+		nextButton.innerHTML = 'next';
+		nextButton.style.position = 'relative';
+		nextButton.style.left = '450px';
+		nextButton.style.top = '175px';
+		nextButton.onclick = function() {
+			// Need to find and parse preTest again!
+			var preTest = projectXML.find('PreTest')[0];
+			// Check if current state is a question!
+			if (preTest.children[this.value-1].nodeName == 'question') {
+				var questionId = preTest.children[this.value-1].attributes['id'].value;
+				var questionHold = document.createElement('comment');
+				var questionResponse = document.getElementById(questionId + 'response');
+				questionHold.id = questionId;
+				questionHold.innerHTML = questionResponse.value;
+				preTestQuestions.appendChild(questionHold);
+			}
+			if (this.value < preTest.children.length)
+			{
+				// More to process
+				var child = preTest.children[this.value];
+				if (child.nodeName == 'statement')
+				{
+					preTestOption.innerHTML = '<span>'+child.innerHTML+'</span>';
+				} else if (child.nodeName == 'question')
+				{
+					var textHold = document.createElement('span');
+					textHold.innerHTML = child.innerHTML;
+					var textEnter = document.createElement('textarea');
+					textEnter.id = child.attributes['id'].value + 'response';
+					preTestOption.innerHTML = null;
+					preTestOption.appendChild(textHold);
+					preTestOption.appendChild(textEnter);
+				}
+			} else {
+				// Time to clear
+				preTestHolder.style.zIndex = -1;
+				preTestHolder.style.visibility = 'hidden';
+				var blank = document.getElementById('testHalt');
+				blank.style.zIndex = -2;
+				blank.style.visibility = 'hidden';
+			}
+			this.value++;
+		};
+		
+		preTestHolder.appendChild(preTestOption);
+		preTestHolder.appendChild(nextButton);
+		insertPoint.appendChild(preTestHolder);
+	}
+
 }
 
 function dragEnd(ev) {
@@ -208,19 +316,24 @@
 	var rateMax = window.innerWidth-50;
 	for (var i=0; i<trackSliderObjects.length; i++)
 	{
-		var trackObj = document.createElement("Track");
+		var trackObj = document.createElement("audioElement");
 		trackObj.id = i;
+		trackObj.url = audioEngineContext.audioObjects[i].url;
 		var slider = document.createElement("Rating");
 		var rate = Number(trackSliderObjects[i].style.left.substr(0,trackSliderObjects[i].style.left.length-2));
 		rate = (rate-rateMin)/rateMax;
-		slider.innerText = Math.floor(rate*100);
+		slider.innerHTML = Math.floor(rate*100);
 		var comment = document.createElement("Comment");
-		comment.innerText = commentObjects[i].value;
+		comment.innerHTML = commentObjects[i].value;
 		trackObj.appendChild(slider);
 		trackObj.appendChild(comment);
 		xmlDoc.appendChild(trackObj);
 	}
 	
+	// Append Pre/Post Questions
+	xmlDoc.appendChild(preTestQuestions);
+	xmlDoc.appendChild(postTestQuestions);
+	
 	return xmlDoc;
 }
 
--- a/core.js	Thu Apr 09 12:59:46 2015 +0100
+++ b/core.js	Thu Apr 09 16:30:08 2015 +0100
@@ -10,13 +10,16 @@
 var projectXML;
 var audioEngineContext;
 var projectReturn;
+var preTestQuestions = document.createElement('PreTest');
+var postTestQuestions = document.createElement('PostTest');
 
 window.onload = function() {
 	// Function called once the browser has loaded all files.
 	// This should perform any initial commands such as structure / loading documents
 	
 	// Create a web audio API context
-	// NORE: Currently this will only work with webkit browsers (Chrome/Safari)!
+	// Fixed for cross-browser support
+	var AudioContext = window.AudioContext || window.webkitAudioContext;
 	audioContext = new AudioContext;
 	
 	// Create the audio engine object
@@ -153,6 +156,7 @@
 	
 	this.id = id;
 	this.state = 0; // 0 - no data, 1 - ready
+	this.url = null; // Hold the URL given for the output back to the results.
 	
 	// Create a buffer and external gain control to allow internal patching of effects and volume leveling.
 	this.bufferNode = audioContext.createBufferSource();
@@ -183,6 +187,7 @@
 
 	this.constructTrack = function(url) {
 		var request = new XMLHttpRequest();
+		this.url = url;
 		request.open('GET',url,true);
 		request.responseType = 'arraybuffer';
 		
Binary file docs/ProjectSpecificationDocument.pdf has changed
--- a/docs/ProjectSpecificationDocument.tex	Thu Apr 09 12:59:46 2015 +0100
+++ b/docs/ProjectSpecificationDocument.tex	Thu Apr 09 16:30:08 2015 +0100
@@ -88,12 +88,49 @@
 
 \subsubsection{Question}
 
-This allows for a question to be asked pre/post the test. This is added to the response XML in the same location as the other common/global questions. The response includes both the question asked and the response. The optional attribute 'mandatory' defines whether the question can be blank or not, default is for optional. If mandatory, the next button is not available until something is entered.
+This allows for a question to be asked pre/post the test. This is added to the response XML in the same location as the other common/global questions. The response includes both the question asked and the response. This takes two attributes, id and mandatory. ID is a mandatory field. The same ID will be used in the results so it is important it is properly entered. Mandatory is optional. True means the field must be entered before continuing.
 
 \subsubsection{Resource}
 
 The resource tag is only available in the postTest tag. This allows for the linking to some external resource via the href attribute.
 
+\section{Feature List}
+\begin{itemize}
+\item Paging listening tests - eg. Ask multiple questions in each experiment
+\item Labels on X axis - scale
+\item Input questions/comment at top to guide towards the question being asked.
+\item Randomise track numbers -(inc. comment boxes and relate back to correct reference track)
+\item Randomise order of individual tests
+\item Save output XML file to remote server
+\item Tests Metrics
+\begin{itemize}
+\item Duration of listening to each track
+\item Time spent on each individual test
+\item Start and end position of every track
+\item Flags on each track, to ensure each track (but may not restrict users from submitting)
+\begin{itemize}
+\item Has been listened to 
+\item Has been moved
+\item Has comments about it
+\end{itemize}
+\end{itemize}
+\end{itemize}
+
+\subsection{Advanced feature list}
+\begin{itemize}
+\item Repeat each tests number of times (2 or 3?) to remove learning / experience bias and ensure that the order is consistent
+\item Perform Loudness equalisation on all tracks
+\item Selection of test type
+\item Pre-test of some basic hearing test
+\begin{itemize}
+\item MUSHRA (with vertical slider per track)
+\item APE (Single horizontal slider)
+\item AB Test
+\end{itemize}
+\end{itemize}
+
+
+
 \section{Example}
 
 Here is an example XML structure
Binary file docs/ResultsSpecificationDocument.pdf has changed
--- a/docs/ResultsSpecificationDocument.tex	Thu Apr 09 12:59:46 2015 +0100
+++ b/docs/ResultsSpecificationDocument.tex	Thu Apr 09 16:30:08 2015 +0100
@@ -12,19 +12,38 @@
 This document outlines the return XML document structure to hold the results from the Browser Evaluation Tool, specifically for the APE Interface.
 
 \section{Root}
-The root of the document is \texttt{BrowserEvaluationResult}. This takes no attributes but contains all children.
+The root of the document is \texttt{BrowserEvaluationResult}.
 
-\section{Track}
-The first child element is the \texttt{Track} element. This contains the results for a specific track. This requires the attribute \texttt{trackId} to be set to the numerical track Id.
+\section{AudioElement}
+A 1st level node, this contains the results for a specific audioElement.
+
+\subsection{Attributes}
+Has the following attributes, depending on the variables set in the Project Specification.
+\begin{itemize}
+\item \texttt{id} - Mandatory. This returns the ID of the track in question. This is either the value passed in from the project specification, or calculated based on the position in the list. For instance, in the automatic system, the first test sample has ID 0, the second ID 1 and so forth. The value passed in from the project specification can either be a string or a Number.
+\item \texttt{url} - Mandatory. Returns the full URL given incase of errors or for later checking.
+\end{itemize}
 
 \subsection{Value}
 One of these elements per track, containing the value between 0 and 100 relating the user rating of the track. This is a mandatory element.
+% float or int? (I, Brecht, am sort of indifferent here, it used to be down to .01 or something before, so maybe that or .1)
+% Nick - Can be a float, was trying to remove/reduce ambiguity from pixel position. But can easily make it to .01
 
 \subsection{Comment}
-One of these elements per track, containing any commenting data from the interface text boxes.
+One of these elements per track, containing any commenting data from the interface text boxes. Has the two following child nodes.
+\begin{itemize}
+\item \texttt{Question} - Returns the text next to the comment box
+\item \texttt{Response} - Returns the text in the comment box
+\end{itemize}
+
+\section{PreTest and PostTest}
+A 1st level node, contains the response to any pre-test questions given in the project specification. These are stored in the same Comment node as outlined in the above audioElement.
+
+The PostTest is a 1st level node and contains the response to any post-test questions given in the project specification.
 
 \section{Session Data}
 This will contain any captured session data. Currently not implemented but here for future referencing.
+% I used to have a 'global' comment for each 'session' as well
 
 \section{Globals}
 Contains any comment boxes which were specified in the APE project specification with the comment ID, comment text and the comment results.
--- a/docs/SMC15/smc2015template.tex	Thu Apr 09 12:59:46 2015 +0100
+++ b/docs/SMC15/smc2015template.tex	Thu Apr 09 16:30:08 2015 +0100
@@ -25,9 +25,9 @@
 
 
 %user defined variables
-\def\papertitle{APE FOR WEB: A BROWSER-BASED EVALUATION TOOL FOR AUDIO}
-\def\firstauthor{Brecht De Man}
-\def\secondauthor{Nicholas Jillings}
+\def\papertitle{APE FOR WEB: A BROWSER-BASED EVALUATION TOOL FOR AUDIO} %?
+\def\firstauthor{Nicholas Jillings}
+\def\secondauthor{Brecht De Man}
 \def\thirdauthor{David Moffat}
 \def\fourthauthor{Joshua D. Reiss}
 
@@ -111,17 +111,18 @@
 %   {\secondauthor} {Affiliation2 \\ %
 %     {\tt \href{mailto:author2@smcnetwork.org}{author2@smcnetwork.org}}}
 
-% Three addresses
-% --------------
+
+
+% FIX!!! 
  \fourauthors
    {\firstauthor} {%Affiliation1 \\
-     {\tt \href{mailto:b.deman@qmul.ac.uk}{\{b.deman@, }}}
+     {\tt \href{mailto:b.deman@qmul.ac.uk}{n.g.r.jillings@se14.qmul.ac.uk, }}}
    {\secondauthor} {%Affiliation2\\ %
-     {\tt \href{mailto:n.g.r.jillings@se14.qmul.ac.uk}{n.g.r.jillings@se14. ,}}}
+     {\tt \href{mailto:n.g.r.jillings@se14.qmul.ac.uk}{\{b.deman,}}}
    {\thirdauthor} {%Affiliation3\\ %
-     {\tt \href{mailto:d.j.moffat@qmul.ac.uk}{d.j.moffat@, }}}
+     {\tt \href{mailto:d.j.moffat@qmul.ac.uk}{d.j.moffat, }}}
     {\fourthauthor} {%Affiliation4\\ %
-     {\tt \href{mailto:joshua.reiss@qmul.ac.uk}{joshua.reiss@\}qmul.ac.uk}}}
+     {\tt \href{mailto:joshua.reiss@qmul.ac.uk}{joshua.reiss\}@qmul.ac.uk}}}
 
 % ***************************************** the document starts here ***************
 \begin{document}
@@ -134,21 +135,105 @@
 Place your abstract at the top left column on the first page.
 Please write about 150-200 words that specifically highlight the purpose of your work,
 its context, and provide a brief synopsis of your results.
-Avoid equations in this part.
+Avoid equations in this part.\\
+TOTAL PAPER: Minimum 4 pages, 6 preferred, max. 8 (6 for demos/posters)\\ 
 \end{abstract}
 %
 
 \section{Introduction}\label{sec:introduction}
 
-background (types of research)\\
-prior work: \cite{deman2014b} \\
+background (types of research where this type of perceptual evaluation of audio is relevant)\\
+
+multiple stimulus perceptual evaluation (reference to Bech etc.)\\
+
+prior work: \cite{deman2014b} in MATLAB, much less easy to deploy, and often stops working due to version updates \\ 
+
 goal, what are we trying to do? \\
 
+[Previously, due to limited functionality of HTML, ..., it was not possible to design this type of interfaces with such high quality audio... ]
 
-Minimum 4 pages, 6 preferred, max. 8 (6 for demos/posters)
 
+\section{Design considerations}\label{sec:designconsiderations}
 
+We present a browser-based perceptual evaluation tool for audio that ... \\
 
+see \cite{deman2014b}: requirements informed by research on music production (see my work and that of others' in the group), such as randomisation, playback of high quality audio, some degree of flexibility in terms of configuration, ... \\
+
+
+\section{Implementation}\label{sec:implementation}
+%[Nick???]
+
+%section on overall architecture\\
+
+%section with overview of the structure of the input and output files, perhaps with graph or table
+
+The tool runs entirely inside the browser through the new HTML5 Web Audio API. The API is supported by most major web browsers (except Internet Explorer) and allows for constructing a chain of audio processing elements to produce a high quality, real time signal process to manipulate audio streams. The API supports multi-channel processing and has an accurate playback timer for precise scheduled playback control. The web audio API is controlled through the browser JavaScript and is therefore highly controllable. The Web Audio API processing is all controlled in a separate thread to the main JavaScript thread, meaning there is no blocking due to real time processing.
+
+\subsection{Architecture}\label{sec:architecture}
+
+The web tool itself is split into several files to operate:
+\begin{itemize}
+\item apeTool.html: The main index file to load the scripts, this is the file the browser must request to load
+\item core.js: Contains functions and objects to manage the audio control, audio objects for testing and loading of files
+\item ape.js: Parses setup files to create the interface as instructed, following the same style chain as the MATLAB APE Tool.
+\end{itemize}
+
+The HTML file loads the core.js file with it along with a few other ancillary files (such as the jQuery javascript extensions), the browser JavaScript begins to execute the on page instructions, which gives the URL of the test setup XML document (outlined in the next section). The core.js parses this document and executes the function in 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 or A-B tests) to be used, which would still require the same underlying core functions outlined in core.js
+
+The ape.js file has only two main functions: loadInterface(xmlDoc) and interfaceXMLSave(). The first function is called to build the interface once the setup document has been loaded. This includes creating the slider interface to rate the tracks and creating the comment boxes bellow. The bars in the slider ranking at the top of the page are randomly spaced. It also instructs the audio engine in the core.js to create the audio objects. The audio objects are custom built audio nodes built on the web audio API. They consist of a bufferSourceNode (a node which holds a buffer of audio samples for playback) and a gainNode. These are then connected to the audioEngine (itself a custom web audio node) containing a gainNode (where the various audio Objects connect to) for summation before passing the output to the destination Node, a fixed node created where the browser then passes the audio information to the system sound device.
+
+When an audioObject is created, the URL of the audio sample to load is given to it. This is downloaded into the browser asynchronously using the XMLHttpRequest object. This allows for downloading of any file into the JavaScript environment for further processing. It is particularly useful for the web audio API because it supports downloading of files in their binary form, allowing a perfect copy. Once the asynchronous download is complete, the file is then 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 audioObject bufferSourceNode for playback.
+
+Browsers support various audio file formats and are not consistent in any format. One sure format that all browsers support is the WAV format. Although not a compact, web friendly format, most transport systems are of a high enough bandwidth this should not be a problem. However one problem is that of sample rate. On loading, the browser uses the sample rate assigned by the system sound device. The browser does not have the ability to request a different sound rate. 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 setup 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. This happens before any loading or decoding of audio files. Only once the sample rates match will the system actually fetch any files, keeping down requests for the larger files until they are actually needed.
+
+During playback, the playback nodes loop indefinitely until playback is stopped. The gain nodes in the audioObjects enable dynamic muting of nodes. When a bar in the sliding ranking is clicked, the audio engine mutes all audioObjects 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.
+
+\subsection{Setup and Results Formats}\label{sec:setupresultsformats}
+
+Setup and the results both use the common XML document format to outline the various parameters. The setup file contains all the information needed to initialise a test session. Several Nodes can be defined to outline the audio samples to use, questions to be asked and any pre- or post-test questions or instructions. 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 which web files.
+
+The results file is dynamically generated by the interface upon clicking the submit button. There will be checks, depending on the setup file, to ensure that all tracks have been evaluated and their positions in the slider moved. The XML returned contains a node per audioObject and contains its rating in the slider and any comments written in its associated comment box. The rating returned is normalised to be within a integer range of 0 to 100. This normalises the pixel representation of different browser windows. If a window for instance is only 1280 wide, reporting its pixel position is not representative to a display with a width of 1920.
+
+The pre- and post-test options allow for comments or questions to be presented before or after the test. These are automatically generated based upon the given setup XML and allow nearly any form of question and comment to be included in a window on its own. Questions are stored and presented in the response section labelled 'pretest' and 'posttest' along with the question ID and its response. Questions can be made optionally mandatory. Example questions may involve entering mixing experience or listening environment.
+
+The results will also contain information collected by any defined pre/post questions. These are referenced against the setup XML by using the same ID as well as printing in the same question, so readable responses can be obtained. Future development will also evolve to include any session data, such as the browser the tool was used in, how long the test took and any other metrics. Currently the results files are downloaded on the user side of the browser as a .xml file to be manually returned. However the end goal is to allow the XML files to be submitted over the web to a receiving server to store them, allowing for automated collection.
+
+Here is an example of the setup XML and the results XML:
+% Should we include an Example of the input and output XML structure??
+
+\section{Applications}\label{sec:applications} %?
+
+\subsection{Listening Environment Standardisation}
+
+
+discussion of use of this toolbox (possibly based on a quick mock test using my research data, to be repeated with a large number of participants and more data later)\\
+
+
+\section{Conclusions and future work}\label{sec:conclusions}
+
+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. 
+Specifically, we discussed the use of the toolbox in the context of assessment of preference for different production practices, with identical source material. 
+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
+
+% future work
+Further work may include the development of other common test designs, such as [...], and [...]. In addition, [...]. 
+
+...
+
+The source code of this tool can be found on \url{code.soundsoftware.ac.uk/projects/browserevaluationtool}.
+
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%bibliography here
+\bibliography{smc2015template}
+
+
+
+\end{document}
+
+
+
+% RUBBISH
 
 %\subsection{Equations}
 %Equations of importance, 
@@ -188,7 +273,7 @@
 %\end{figure}
 
 
-\section{Conclusions}\label{sec:conclusions}
+
 
 
 %\begin{acknowledgments}
@@ -198,11 +283,3 @@
 %``Acknowledgments'' (with no numbering).
 %\end{acknowledgments} 
 
-%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-%bibliography here
-%\bibliography{smc2015template}
-
-\bibliography{../General}{}
-
-
-\end{document}
--- a/example_eval/project.xml	Thu Apr 09 12:59:46 2015 +0100
+++ b/example_eval/project.xml	Thu Apr 09 16:30:08 2015 +0100
@@ -1,7 +1,7 @@
 <?xml version="1.0" encoding="utf-8"?>
 <BrowserEvalProjectDocument>
 	<setup interface="APE" projectReturn="null" />
-	<audioHolder hostURL="example_eval/" sampleRate="44100" sampleRateExplicit="true">
+	<audioHolder hostURL="example_eval/" sampleRate="44100">
 		<audioElements url="0.wav" ID="0"/>
 		<audioElements url="1.wav"/>
 		<audioElements url="2.wav"/>
@@ -17,9 +17,10 @@
 	<CommentQuestion>What is your mixing experiance</CommentQuestion>
 	<PreTest>
 		<statement>Please listen to all mixes</statement>
+		<question id="location" mandatory="true">Please enter your listening location</question>
 	</PreTest>
 	<PostTest>
 		<statement>Thank you for taking this listening test.</statement>
-		<question>Please enter your name.</question>
+		<question id="SessionID">Please enter your name.</question>
 	</PostTest>
 </BrowserEvalProjectDocument>
\ No newline at end of file