Closed GoogleCodeExporter closed 9 years ago
Original comment by guse...@datamininglab.com
on 2 Oct 2013 at 3:24
Original comment by guse...@datamininglab.com
on 2 Oct 2013 at 3:30
Original comment by guse...@datamininglab.com
on 2 Oct 2013 at 4:27
Original comment by guse...@datamininglab.com
on 2 Oct 2013 at 4:29
Changes made by r174
Property 'probeDetuneOffsets' has been added to allow a hook into detuning the
probe tone.
Values can be entered similarly to the way used for baseIOI offsets, namely
comma delimited values.
probeDetuneOffsets can accept integer values between -50 and 50, allowing up to
a half semitone detune in either direction.
Property 'offsetDegrees' changed to 'baseIOIoffsetDegrees', for clarity.
Original comment by zach.br...@datamininglab.com
on 7 Jan 2014 at 9:02
Requested changes as per correspondence:
See r177
-Renamed 'probeDetuneOffsets' to 'probeDetuneAmounts'
-Renamed 'baseIOIoffsetDegrees' back to 'offsetDegrees'
-Added ability to be able to detune arbitrarily far, not limited to -50 to 50
cents. However this arbitrary detune is limited to the minimum and maximum
pitches allowed by MIDI.
-Added property to label the first accuracy question for responses, called
'accuracyResponseLabel'
Original comment by zach.br...@datamininglab.com
on 9 Jan 2014 at 9:22
Fixed error that made response checking only check baseIOI differences. New
property added to specify what is being tested (timing or detune) called
'experimentTestingType'.
See r185
Original comment by zach.br...@datamininglab.com
on 5 Feb 2014 at 6:42
Original issue reported on code.google.com by
guse...@datamininglab.com
on 2 Oct 2013 at 3:22