annotate docs/WAC2016/WAC2016.tex @ 317:def2de7d24b7 WAC2016

Paper: bits of introduction and remote testing, minor edits
author Brecht De Man <b.deman@qmul.ac.uk>
date Tue, 29 Sep 2015 23:55:10 +0200
parents 594de461a5ea
children 85f05a29a01a
rev   line source
b@308 1 \documentclass{sig-alternate}
b@317 2 \usepackage{hyperref}
b@308 3
b@308 4 \begin{document}
b@308 5
b@308 6 % Copyright
b@308 7 \setcopyright{waclicense}
b@308 8
b@308 9
b@308 10 %% DOI
b@308 11 %\doi{10.475/123_4}
b@308 12 %
b@308 13 %% ISBN
b@308 14 %\isbn{123-4567-24-567/08/06}
b@308 15 %
b@308 16 %%Conference
b@308 17 %\conferenceinfo{PLDI '13}{June 16--19, 2013, Seattle, WA, USA}
b@308 18 %
b@308 19 %\acmPrice{\$15.00}
b@308 20
b@308 21 %
b@308 22 % --- Author Metadata here ---
b@308 23 \conferenceinfo{Web Audio Conference WAC-2016,}{April 4--6, 2016, Atlanta, USA}
b@308 24 \CopyrightYear{2016} % Allows default copyright year (20XX) to be over-ridden - IF NEED BE.
b@308 25 %\crdata{0-12345-67-8/90/01} % Allows default copyright data (0-89791-88-6/97/05) to be over-ridden - IF NEED BE.
b@308 26 % --- End of Author Metadata ---
b@308 27
b@312 28 \title{Web Audio Evaluation Tool something something}
b@308 29 %\subtitle{[Extended Abstract]
b@308 30 %\titlenote{A full version of this paper is available as
b@308 31 %\textit{Author's Guide to Preparing ACM SIG Proceedings Using
b@308 32 %\LaTeX$2_\epsilon$\ and BibTeX} at
b@308 33 %\texttt{www.acm.org/eaddress.htm}}}
b@308 34 %
b@308 35 % You need the command \numberofauthors to handle the 'placement
b@308 36 % and alignment' of the authors beneath the title.
b@308 37 %
b@308 38 % For aesthetic reasons, we recommend 'three authors at a time'
b@308 39 % i.e. three 'name/affiliation blocks' be placed beneath the title.
b@308 40 %
b@308 41 % NOTE: You are NOT restricted in how many 'rows' of
b@308 42 % "name/affiliations" may appear. We just ask that you restrict
b@308 43 % the number of 'columns' to three.
b@308 44 %
b@308 45 % Because of the available 'opening page real-estate'
b@308 46 % we ask you to refrain from putting more than six authors
b@308 47 % (two rows with three columns) beneath the article title.
b@308 48 % More than six makes the first-page appear very cluttered indeed.
b@308 49 %
b@308 50 % Use the \alignauthor commands to handle the names
b@308 51 % and affiliations for an 'aesthetic maximum' of six authors.
b@308 52 % Add names, affiliations, addresses for
b@308 53 % the seventh etc. author(s) as the argument for the
b@308 54 % \additionalauthors command.
b@308 55 % These 'additional authors' will be output/set for you
b@308 56 % without further effort on your part as the last section in
b@308 57 % the body of your article BEFORE References or any Appendices.
b@308 58
b@316 59 % FIVE authors instead of four, to leave space between first two authors.
d@310 60 \numberofauthors{5} % in this sample file, there are a *total*
b@308 61 % of EIGHT authors. SIX appear on the 'first-page' (for formatting
b@308 62 % reasons) and the remaining two appear in the \additionalauthors section.
b@308 63 %
b@308 64 \author{
b@308 65 % You can go ahead and credit any number of authors here,
b@308 66 % e.g. one 'row of three' or two rows (consisting of one row of three
b@308 67 % and a second row of one, two or three).
b@308 68 %
b@308 69 % The command \alignauthor (no curly braces needed) should
b@308 70 % precede each author name, affiliation/snail-mail address and
b@308 71 % e-mail address. Additionally, tag each line of
b@308 72 % affiliation/address with \affaddr, and tag the
b@308 73 % e-mail address with \email.
b@308 74 %
b@308 75 % 1st. author
b@308 76 \alignauthor Nicholas Jillings\\
b@308 77 \email{n.g.r.jillings@se14.qmul.ac.uk}
b@316 78 % dummy author for nicer spacing
b@316 79 \alignauthor
b@308 80 % 2nd. author
b@308 81 \alignauthor Brecht De Man\\
b@308 82 \email{b.deman@qmul.ac.uk}
b@308 83 \and % use '\and' if you need 'another row' of author names
b@308 84 % 3rd. author
b@308 85 \alignauthor David Moffat\\
b@308 86 \email{d.j.moffat@qmul.ac.uk}
b@308 87 % 4th. author
b@308 88 \alignauthor Joshua D. Reiss\\
b@308 89 \email{joshua.reiss@qmul.ac.uk}
b@316 90 \and % new line for address
b@308 91 \affaddr{Centre for Digital Music}\\
b@308 92 \affaddr{School of Electronic Engineering and Computer Science}\\
b@308 93 \affaddr{Queen Mary University of London}\\
b@308 94 \affaddr{Mile End Road,}
b@308 95 \affaddr{London E1 4NS}\\
b@308 96 \affaddr{United Kingdom}\\
b@308 97 }
b@308 98 %Centre for Digital Music, School of Electronic Engineering and Computer Science, Queen Mary University of London
b@308 99 %% 5th. author
b@308 100 %\alignauthor Sean Fogarty\\
b@308 101 % \affaddr{NASA Ames Research Center}\\
b@308 102 % \affaddr{Moffett Field}\\
b@308 103 % \email{fogartys@amesres.org}
b@308 104 %% 6th. author
b@308 105 %\alignauthor Charles Palmer\\
b@308 106 % \affaddr{Palmer Research Laboratories}\\
b@308 107 % \affaddr{8600 Datapoint Drive}\\
b@308 108 % \email{cpalmer@prl.com}
b@308 109 %}
b@308 110 % There's nothing stopping you putting the seventh, eighth, etc.
b@308 111 % author on the opening page (as the 'third row') but we ask,
b@308 112 % for aesthetic reasons that you place these 'additional authors'
b@308 113 % in the \additional authors block, viz.
b@308 114 %\additionalauthors{Additional authors: John Smith (The Th{\o}rv{\"a}ld Group,
b@308 115 %email: {\texttt{jsmith@affiliation.org}}) and Julius P.~Kumquat
b@308 116 %(The Kumquat Consortium, email: {\texttt{jpkumquat@consortium.net}}).}
b@308 117 \date{1 October 2015}
b@308 118 % Just remember to make sure that the TOTAL number of authors
b@308 119 % is the number that will appear on the first page PLUS the
b@308 120 % number that will appear in the \additionalauthors section.
b@308 121
b@308 122 \maketitle
b@308 123 \begin{abstract}
b@308 124 Here comes the abstract.
b@308 125 \end{abstract}
b@308 126
b@308 127
b@308 128 \section{Introduction}
b@317 129
b@317 130 % Listening tests/perceptual audio evaluation: what are they, why are they important
b@317 131 % As opposed to limited scope of WAC15 paper: also musical features, realism of sound effects / sound synthesis, performance of source separation and other algorithms...
b@317 132 Perceptual evaluation of audio, in the form of listening tests, is a powerful way to assess anything from audio codec quality over realism of sound synthesis to the performance of source separation, automated music production and
b@317 133 In less technical areas, the framework of a listening test can be used to measure emotional response to music or test cognitive abilities. % maybe some references? If there's space.
b@317 134
b@317 135 % Why difficult? Challenges? What constitutes a good interface?
b@317 136 Technical, interfaces, user friendliness, reliability
b@317 137
b@317 138 Note that the design of an effective listening test further poses many challenges unrelated to interface design, which are beyond the scope of this paper \cite{bech}.
b@317 139
b@317 140 % Why in the browser?
b@317 141 Web Audio API has made some essential features like sample manipulation of audio streams possible \cite{schoeffler2015mushra}.
b@308 142
b@316 143 Situating the Web Audio Evaluation Tool between other currently available evaluation tools, ...
b@316 144
b@316 145 % only browser-based?
b@316 146 \begin{table*}[htdp]
b@316 147 \caption{Table with existing listening test platforms and their features}
b@316 148 \begin{center}
b@316 149 \begin{tabular}{|*{6}{l|}}
b@316 150 \hline
b@317 151 \textbf{Name} & \textbf{Ref.} & \textbf{Language} & \textbf{Interfaces} & \textbf{Remote} & \textbf{All UI} \\
b@316 152 \hline
b@317 153 APE & \cite{ape} & MATLAB & multiple stimulus one axis & & \\
b@316 154 BeaqleJS & \cite{beaqlejs} & JavaScript & & not natively supported & \\
b@317 155 HULTI-GEN & \cite{hultigen} & MAX & & & \checkmark \\
b@317 156 \textbf{WAET} & \cite{waet} & JavaScript & \textbf{all of the above} & \checkmark & \checkmark \\
b@316 157 \hline
b@316 158 \end{tabular}
b@316 159 \end{center}
b@316 160 \label{tab:toolboxes}
b@316 161 \end{table*}%
b@316 162
b@316 163 % about BeaqleJS
b@316 164 ... However, BeaqleJS \cite{beaqlejs} does not make use of the Web Audio API, %requires programming knowledge...
b@316 165
b@316 166 %
b@317 167 Selling points: remote tests, visualisaton, create your own test in the browser, many interfaces, few/no dependencies, flexibility
b@317 168
b@317 169 As recruiting participants can be very time-consuming, and as for some tests a large number of participants is needed, browser-based tests \cite{schoeffler2015mushra}. However, to our knowledge, no tool currently exists that allows the creation of a remotely accessible listening test. % I wonder what you can do with Amazon Mechanical Turk and the likes.
b@317 170
b@317 171 [Talking about what we do in the various sections of this paper. Referring to \cite{waet}. ]
b@316 172
b@316 173
b@317 174 \section{Architecture} % title? 'back end'? % NICK
b@308 175 A slightly technical overview of the system. Talk about XML, JavaScript, Web Audio API, HTML5.
b@316 176 Describe and/or visualise audioholder-audioelement-... structure.
b@316 177
b@317 178 % see also SMC12 - less detail here
b@317 179
b@317 180 Which type of files? % WAV, anything else? Perhaps not exhaustive list, but say something along the lines of 'whatever browser supports'
b@315 181
b@316 182 Streaming audio? % probably not, unless it's easy
b@316 183
b@317 184 Compatibility? % not IE, everything else fine?
b@317 185
b@317 186
b@315 187
b@315 188
b@316 189 \section{Remote tests} % with previous?
b@317 190
b@317 191 If the experimenter is willing to trade some degree of control for a higher number of participants, the test can be hosted on a web server so that subjects can take part remotely. This way, a link can be shared widely in the hope of attracting a large amount of subjects, while listening conditions and subject reliability may be less ideal. However, a sound system calibration page and a wide range of metrics logged during the test mitigate these problems. Note also that in some experiments, it may be preferred that the subject has a `real life', familiar listening set-up, for instance when perceived quality differences on everyday sound systems are investigated.
b@317 192 Furthermore, a fully browser-based test, where the collection of the results is automatic, is more efficient and technically reliable even when the test still takes place under lab conditions.
b@317 193
b@315 194 The following features allow easy and effective remote testing:
b@315 195 \begin{itemize}
b@315 196 \item PHP script to collect result XML files
b@315 197 \item Randomly pick specified number of audioholders
b@317 198 \item Calibration
b@315 199 \item Functionality to participate multiple times
b@315 200 \begin{itemize}
b@315 201 \item Possible to log in with unique ID (no password)
b@315 202 \item Pick `new user' (need new, unique ID) or `already participated' (need already available ID)
b@315 203 \item Store XML on server with IDs plus which audioholders have already been listened to
b@315 204 \item Don't show `post-test' survey after first time
b@315 205 \item Pick `new' audioholders if available
b@315 206 \item Copy survey information first time to new XMLs
b@315 207 \end{itemize}
b@315 208 \item Intermediate saves
b@315 209 \item Collect IP address information (privacy issues?) --> geo-related API?
b@317 210 \item Time measurement - see before or
b@315 211 \end{itemize}
b@315 212
b@308 213
b@316 214 \section{Interfaces} % title? 'Front end'? % Dave
b@316 215 `Build your own test'
b@316 216
b@317 217 Elements present to build any of the following interfaces, and many more: axes, markers, labels, anchors, references, reference signal button, stop button, comment boxes, radio buttons, checkboxes, transport/scrubber bar
b@317 218
b@317 219 Established tests (see below) included as `presets' in the build-your-own-test page.
b@317 220
b@317 221
b@308 222 We could add more interfaces, such as:
b@308 223 \begin{itemize}
b@316 224 \item (APE style) \cite{ape}
b@308 225 \item Multi attribute ratings
d@310 226 \item MUSHRA (ITU-R BS. 1534)~\cite{recommendation20031534}
d@310 227 \item Interval Scale~\cite{zacharov1999round}
d@310 228 \item Rank Scale~\cite{pascoe1983evaluation}
b@308 229
d@310 230 \item 2D Plane rating - e.g. Valence vs. Arousal~\cite{carroll1969individual}
d@310 231 \item Likert scale~\cite{likert1932technique}
d@309 232
b@316 233 \item {\bf All the following are the interfaces available in HULTI-GEN~\cite{hultigen} }
d@310 234 \item ABC/HR (ITU-R BS. 1116)~\cite{recommendation19971116}
d@309 235 \begin{itemize}
d@309 236 \item Continuous Scale (5-1) Imperceptible, Perceptible but not annoying, slightly annoying, annoying, very annoying. (default Inaudible?)
d@309 237 \end{itemize}
d@309 238 \item -50 to 50 Bipolar with Ref
d@309 239 \begin{itemize}
d@309 240 \item Scale -50 to 50 on Mushra with default values as 0 in middle and a comparison ``Reference'' to compare to 0 value
d@309 241 \end{itemize}
d@310 242 \item Absolute Category Rating (ACR) Scale~\cite{rec1996p}
d@309 243 \begin{itemize}
d@309 244 \item 5 point Scale - Bad, Poor, Fair, Good, Excellent (Default fair?)
d@309 245 \end{itemize}
d@310 246 \item Degredation Category Rating (DCR) Scale~\cite{rec1996p}
d@309 247 \begin{itemize}
d@309 248 \item 5 point Scale - Inaudible, Audible but not annoying, slightly annoying, annoying, very annoying. (default Inaudible?) - {\it Basically just quantised ABC/HR?}
d@309 249 \end{itemize}
d@310 250 \item Comparison Category Rating (CCR) Scale~\cite{rec1996p}
d@309 251 \begin{itemize}
d@309 252 \item 7 point scale: Much Better, Better, Slightly Better, About the same, slightly worse, worse, much worse - Default about the same with reference to compare to
d@309 253 \end{itemize}
d@310 254 \item 9 Point Hedonic Category Rating Scale~\cite{peryam1952advanced}
d@309 255 \begin{itemize}
d@309 256 \item 9 point scale: Like Extremely, Like Very Much, Like Moderate, Like Slightly, Neither Like nor Dislike, dislike Extremely, dislike Very Much, dislike Moderate, dislike Slightly - Default Neither Like nor Dislike with reference to compare to
d@309 257 \end{itemize}
d@310 258 \item ITU-R 5 Point Continuous Impairment Scale~\cite{rec1997bs}
d@309 259 \begin{itemize}
d@309 260 \item 5 point Scale (5-1) Imperceptible, Perceptible but not annoying, slightly annoying, annoying, very annoying. (default Inaudible?)- {\it Basically just quantised ABC/HR, or Different named DCR}
d@309 261 \end{itemize}
d@310 262 \item Pairwise Comparison (Better/Worse)~\cite{david1963method}
d@309 263 \begin{itemize}
d@309 264 \item 2 point Scale - Better or Worse - (not sure how to default this - they default everything to better, which is an interesting choice)
d@309 265 \end{itemize}
b@308 266 \end{itemize}
b@308 267
b@308 268 There are also the following interfaces, which would require a slightly different `engine' underneath, e.g. loading a different page for every possible pair.
b@308 269 \begin{itemize}
d@310 270 \item AB Test~\cite{lipshitz1981great}
d@310 271 \item ABX Test~\cite{clark1982high}
b@308 272 \item JND
b@308 273 \end{itemize}
b@308 274
b@308 275 A screenshot would be nice.
b@308 276
b@308 277 \section{Analysis and diagnostics}
b@317 278 % don't mention Python scripts
b@308 279 It would be great to have easy-to-use analysis tools to visualise the collected data and even do science with it. Even better would be to have all this in the browser. Complete perfection would be achieved if and when only limited setup, installation time, and expertise are required for the average non-CS researcher to use this.
b@308 280
b@312 281 The following could be nice:
b@312 282
b@312 283 \begin{itemize}
b@312 284 \item Web page showing all audioholder IDs, file names, subject IDs, audio element IDs, ... in the collected XMLs so far (\texttt{saves/*.xml})
b@312 285 \item Check/uncheck each of the above for analysis (e.g. zoom in on a certain song, or exclude a subset of subjects)
b@312 286 \item Click a mix to hear it (follow path in XML setup file, which is also embedded in the XML result file)
b@312 287 \item Box plot, confidence plot, scatter plot of values (for a given audioholder)
b@312 288 \item Timeline for a specific subject (see Python scripts), perhaps re-playing the experiment in X times realtime. (If actual realtime, you could replay the audio...)
b@312 289 \item Distribution plots of any radio button and number questions (drop-down menu with `pretest', `posttest', ...; then drop-down menu with question `IDs' like `gender', `age', ...; make pie chart/histogram of these values over selected range of XMLs)
b@312 290 \item All `comments' on a specific audioelement
b@312 291 \item A `download' button for a nice CSV of various things (values, survey responses, comments) people might want to use for analysis, e.g. when XML scares them
b@315 292 \item Validation of setup XMLs (easily spot `errors', like duplicate IDs or URLs, missing/dangling tags, ...)
b@312 293 \end{itemize}
b@312 294
b@312 295 A subset of the above would already be nice for this paper.
b@312 296
b@308 297 Some pictures here please.
b@308 298
b@316 299 \section{Concluding remarks and future work}
b@308 300
b@317 301 The code and documentation can be pulled or downloaded from \url{code.soundsoftware.ac.uk/projects/webaudioevaluationtool}.
b@308 302
b@317 303 [Talking a little bit about what else might happen. Unless we really want to wrap this up. ]
b@316 304
b@317 305 Use \cite{schoeffler2015mushra} as a `checklist', even though it only considers subjective evaluation of audio systems (and focuses on the requirements for a MUSHRA test).
b@317 306 % remote
b@317 307 % language support (not explicitly stated)
b@317 308 % crossfades
b@317 309 % choosing speakers/sound device from within browser?
b@317 310 % collect information about software and sound system
b@317 311 % buttons, scales, ... UI elements
b@317 312 % must be able to load uncompressed PCM
b@317 313
b@317 314 [What can we not do? `Method of adjustment', as in \cite{schoeffler2015mushra} is another can of worms, because, like, you could adjust lots of things (volume is just one of them, that could be done quite easily). Same for using input signals like the participant's voice. Either leave out, or mention this requires modification of the code we provide.]
b@308 315
b@308 316 %
b@308 317 % The following two commands are all you need in the
b@308 318 % initial runs of your .tex file to
b@308 319 % produce the bibliography for the citations in your paper.
b@308 320 \bibliographystyle{abbrv}
b@308 321 \bibliography{WAC2016} % sigproc.bib is the name of the Bibliography in this case
b@308 322 % You must have a proper ".bib" file
b@308 323 % and remember to run:
b@308 324 % latex bibtex latex latex
b@308 325 % to resolve all references
b@308 326 %
b@308 327 % ACM needs 'a single self-contained file'!
b@308 328 %
b@308 329 \end{document}