changeset 85:bbc3f1617e12

Paper: Changed links into footnotes instead of references.

--- a/docs/SMC15/smc2015template.bbl	Fri Apr 24 17:42:04 2015 +0100
+++ b/docs/SMC15/smc2015template.bbl	Fri Apr 24 18:53:24 2015 +0100
@@ -29,7 +29,7 @@
 \bibitem{repp}
 R.~Repp, ``Recording quality ratings by music professionals,'' in
   \emph{Proceedings of the 2006 International Computer Music Conference}, 2006,
-  pp. pp. 468--474.
+  pp. 468--474.
 
 \bibitem{de2013real}
 A.~de~G{\"o}tzen, E.~Sikstr{\"o}m, F.~Grani, and S.~Serafin, ``Real, foley or
@@ -49,7 +49,7 @@
 
 \bibitem{uhlereiss}
 J.~D. Reiss and C.~Uhle, ``Determined source separation for microphone
-  recordings using iir filters,'' in \emph{129th Convention of the Audio
+  recordings using {IIR} filters,'' in \emph{129th Convention of the Audio
   Engineering Society}.\hskip 1em plus 0.5em minus 0.4em\relax Audio
   Engineering Society, November 2010.
 
@@ -68,19 +68,6 @@
   audio features,'' in \emph{Proceedings of the SMC2011, 8th Sound and Music
   Computing Conference}, 2011, pp. 122--127.
 
-\bibitem{webaudioapi}
-W3C, ``Web audio api,'' 2015, \url{http://webaudio.github.io/web-audio-api/}
-  [Accessed 22nd April, 2015].
-
-\bibitem{webaudiodemo}
-------, ``Web audio / midi demo list,'' 2015,
-  \url{http://webaudio.github.io/demo-list/} [Accessed 22nd April, 2015].
-
-\bibitem{bbcradiophonics}
-{BBC R\&D}, ``Recreating the sounds of the bbc radiophonic workshop using the
-  web audio api,'' 2012, \url{http://webaudio.prototyping.bbc.co.uk/} [Accessed
-  22nd April, 2015].
-
 \bibitem{mason2015compression}
 A.~Mason, N.~Jillings, Z.~Ma, J.~D. Reiss, and F.~Melchior, ``Adaptive audio
   reproduction using personalized compression,'' in \emph{Audio Engineering
@@ -121,12 +108,4 @@
   Application}.\hskip 1em plus 0.5em minus 0.4em\relax John Wiley \& Sons,
   2007.
 
-\bibitem{jquery}
-{The jQuery Foundation}, ``Homepage of the {jQuery} and {jQueryUI} {JavaScript}
-  libraries.'' \url{http://jquery.com/} [Accessed 24th April, 2015].
-
-\bibitem{mozdevSupportedMedia}
-Mozilla, ``Media formats supported by the {HTML} audio and video elements,''
-  2015.
-
 \end{thebibliography}

--- a/docs/SMC15/smc2015template.bib	Fri Apr 24 17:42:04 2015 +0100
+++ b/docs/SMC15/smc2015template.bib	Fri Apr 24 18:53:24 2015 +0100
@@ -27,33 +27,6 @@
 	Title = {{APE}: {A}udio {P}erceptual {E}valuation toolbox for {MATLAB}},
 	Year = {2014}}
 
-@misc{webaudioapi,
-	Author = {W3C},
-	Title = {Web Audio API},
-	Year = {2015},
-	Note = {\url{http://webaudio.github.io/web-audio-api/} [Accessed 22nd April, 2015]}
-	}
-
-@misc{webaudiodemo,
-	Author = {W3C},
-	Title = {Web Audio / MIDI Demo List},
-	Year = {2015},
-	Note = {\url{http://webaudio.github.io/demo-list/} [Accessed 22nd April, 2015]}
-	}
-	
-@misc{bbcradiophonics,
-	Author = {{BBC R\&D}},
-	Title = {Recreating the sounds of the BBC Radiophonic Workshop using the Web Audio API},
-	Year = {2012},
-	Note = {\url{http://webaudio.prototyping.bbc.co.uk/} [Accessed 22nd April, 2015]}
-	}
-
-@misc{mozdevSupportedMedia,
-	Author = {Mozilla},
-	Title = {Media formats supported by the {HTML} audio and video elements},
-	Year = {2015},
-	Node = {\url{https://developer.mozilla.org/en-US/docs/Web/HTML/Supported_media_formats} [Accessed 22nd April, 2015]}
-	}
 
 @inproceedings{de2013real,
   title={Real, foley or synthetic? {A}n evaluation of everyday walking sounds},
@@ -98,7 +71,7 @@
 	Booktitle = {129th Convention of the Audio Engineering Society},
 	Month = {November},
 	Organization = {Audio Engineering Society},
-	Title = {Determined Source Separation for Microphone Recordings Using IIR Filters},
+	Title = {Determined Source Separation for Microphone Recordings Using {IIR} Filters},
 	Year = {2010}}
 
 
@@ -108,13 +81,6 @@
 	Month = {January},
 	Title = {Adaptive Control of Amplitude Distortion Effects},
 	Year = {2014}}
-
-
-@article{jquery,
-	Author = {{The jQuery Foundation}},
-	Note = {\url{http://jquery.com/} [Accessed 24th April, 2015]},
-	Title = {Homepage of the {jQuery} and {jQueryUI} {JavaScript} libraries.}}
-	
 	
 @conference{song2013b,
 	Author = {Song, Yading and Dixon, Simon and Halpern, Andrea R.},
@@ -157,7 +123,7 @@
 @conference{repp,
 	Author = {Richard Repp},
 	Booktitle = {Proceedings of the 2006 International Computer Music Conference},
-	Pages = {pp. 468-474},
+	Pages = {468-474},
 	Title = {Recording Quality Ratings by Music Professionals},
 	Year = {2006}}
 	

--- a/docs/SMC15/smc2015template.tex	Fri Apr 24 17:42:04 2015 +0100
+++ b/docs/SMC15/smc2015template.tex	Fri Apr 24 18:53:24 2015 +0100
@@ -151,10 +151,10 @@
 
 %NICK: examples of what kind of audio applications HTML5 has made possible, with references to publications (or website)\\
 
-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? 
+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 analysis \cite{song2013b,song2013a}, and many others \cite{friberg2011comparison}.  % codec design? 
 
-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/
-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/
+The Web Audio API is a high-level JavaScript Application Programming Interface (API) designed for real-time processing of audio inside the browser through various processing nodes\footnote{http://webaudio.github.io/web-audio-api/}. Various web sites have used the Web Audio API for either creative purposes, such as drum machines and score creation tools\footnote{http://webaudio.github.io/demo-list/}, 
+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\footnote{http://webaudio.prototyping.bbc.co.uk/}. 
 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}. 
 
 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. 
@@ -205,7 +205,7 @@
 \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}.
 \end{itemize}
 
-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}.
+The HTML file loads the \texttt{core.js} file along with a few other ancillary files (such as the jQuery JavaScript extensions\footnote{http://jquery.com/}), 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}.
 
 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.
 
@@ -219,7 +219,7 @@
 
 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}.
 
-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
+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) \footnote{https://developer.mozilla.org/en-US/docs/Web/HTML/\\Supported\_media\_formats}. %https://developer.mozilla.org/en-US/docs/Web/HTML/Supported_media_formats
 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.
  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. 
 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.
@@ -231,7 +231,7 @@
 
 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.
 
-\subsection{set up and configurability}
+\subsection{Set up and configurability}
 
 \begin{figure}[ht]
 \begin{center}