notes.txt:Update notes.

This commit is contained in:
kevin 2013-07-13 17:17:05 -07:00
parent 7d7682f279
commit 8399be5e53

View File

@ -1,6 +1,3 @@
Is there a reason that bar 191 was marked as "blank" (blk) in the score file?
TODO: TODO:
+ When a cmMsgList item is selected it should send out the selected index + When a cmMsgList item is selected it should send out the selected index
after the individual data items rather than before them - this way the index after the individual data items rather than before them - this way the index
@ -17,12 +14,17 @@ TODO:
+ (done) Mac Conversion + (done) Mac Conversion
+ (done) Live MIDI - to test audio/MIDI delay. + (done) Live MIDI - to test audio/MIDI delay.
+ (done) As threshold increases overall volume decreases - add a compensation algorithm. + (done) As threshold increases overall volume decreases - add a compensation algorithm.
+ THere are unintialized variable warnings on the release build. + There are unintialized variable warnings on the release build.
+ Add preset delete. + Add preset delete.
+ All uses of va_copy() should have a complimentary va_end() + All uses of va_copy() should have a complimentary va_end()
*** july 10 *** July 10
** Make separate mappings and scale/range controls for left and right. ** (done) Make separate mappings and scale/range controls for left and right.
** Add EQ output stage.
** Work out the speaker setup.
** Add capture/playback. Analyze notes on capture and do not play if there are
any wrong notes. (Skipped notes however are acceptable.)
**
** When a section transition is occurs late - (e.g. due to dropped notes) do not apply ** When a section transition is occurs late - (e.g. due to dropped notes) do not apply
the transformation all at once - instead either ramp it in or step it in on subsequent the transformation all at once - instead either ramp it in or step it in on subsequent
@ -30,6 +32,9 @@ attacks. Section transitions which are positively identified are intended to ha
dramatic changes so applying the updated parameters immediately is acceptable - but dramatic changes so applying the updated parameters immediately is acceptable - but
when the parameters are changed mid-section they should be much applied subtely. when the parameters are changed mid-section they should be much applied subtely.
** (done) Build a database of measurements and setup the program to be able to ** (done) Build a database of measurements and setup the program to be able to
apply a given measurement at it's assigned section. apply a given measurement at it's assigned section.
@ -37,15 +42,18 @@ when the parameters are changed mid-section they should be much applied subtely.
** use Log frequency frequency transform instead of FFT. ** use Log frequency frequency transform instead of FFT.
** Allow for a continous window size via zero padding.
** Add a 'write' preset file button - so the preset file can be saved prior to next crash. ** Add a 'write' preset file button - so the preset file can be saved prior to next crash.
** measurement values can generate MAX_DBL - be sure that are not being sent through to the audio algorithm. ** measurement values can generate MAX_DBL - be sure that are not being sent through to the audio algorithm.
(see ln:965 cmDspKr.c for a hack to fix this) (see ln:965 cmDspKr.c for a hack to fix this)
** add invert to scale/range . ** add invert to scale/range to cause output to go in opposite direction.
** non-grace eveneess are used to generate a measurement value from previous tempo calibration section. ** non-grace eveneess are used to generate a measurement value from previous tempo calibration section.
(non-grace evenness notes therefore have two scores: 'evenness' and 'overall-duration'). (non-grace evenness notes therefore have two scores: 'evenness' and 'overall-duration').
** note that the default setting for dyn and even. ** note that the default setting for dyn and even.
** add dyn,even,tempo,cost number boxes to allow artificial setting of these parameters. ** add dyn,even,tempo,cost number boxes to allow artificial setting of these parameters.
@ -59,16 +67,15 @@ when the parameters are changed mid-section they should be much applied subtely.
** Do IFFT using cos()^c + i * sin()^c - these bases are orthognal but cause harmonic distortion. ** Do IFFT using cos()^c + i * sin()^c - these bases are orthognal but cause harmonic distortion.
To be efficient this might involve writing an FFT function. To be efficient this might involve writing an FFT function.
// May 22
** Crashers (Should be tested but are probably already fixed following score follower debugging.)
Seq 2 m24 Mark 36 & 38 Seq 2 m24 Mark 36 & 38
Seq 4: Mark 115 Seq 4: Mark 115
Seq 4: m76-79 Mark 129 (W/ meas: even & dyn -> thresh change min Thresh to 40) - use 4th seq w/ b1 Seq 4: m76-79 Mark 129 (W/ meas: even & dyn -> thresh change min Thresh to 40) - use 4th seq w/ b1
Seq 6: m92 Mark 143 Seq 6: m92 Mark 143
Seq 7: m103 Mark 173 Seq 7: m103 Mark 173
Seq 7: Mark 172 Meas 103 - always crashes on playback.
// May 22
+ Add invert to scale range to cause output to go in opposite direction.
+ Seq 7: Mark 172 Meas 103 - always crashes on playback.
Seq 4: Mark 76 Meas 40 - crash! Seq 4: Mark 76 Meas 40 - crash!
Seq 2: First mark meas 23 Seq 2: First mark meas 23
Crash seems to happen in cmProc4.c: _cmScMatchInitMtx() ln:1311. Crash seems to happen in cmProc4.c: _cmScMatchInitMtx() ln:1311.
@ -78,6 +85,8 @@ Seq 7: m103 Mark 173
be be
if(rn*cn > p->mrn*p->mcn) if(rn*cn > p->mrn*p->mcn)
BUGS: BUGS:
// Apr 20 // Apr 20
The tempo measurement can produce invalid values. Set score to 22 then play Mark 38. The tempo measurement can produce invalid values. Set score to 22 then play Mark 38.
@ -106,9 +115,9 @@ considered chords. Extra notes notes which were not part of
the chord are probably common and should be discounted during the chord are probably common and should be discounted during
the cost analysis. the cost analysis.
+ Add alignment cost as a 4th variable along with dyn,even,tempo. + (done) Add alignment cost as a 4th variable along with dyn,even,tempo.
+ In the score print out (score_loc.txt) Section 2 is starting on Bar 5 + (done) In the score print out (score_loc.txt) Section 2 is starting on Bar 5
when it should start inside Bar 7. when it should start inside Bar 7.
+ In Take 1 the 2nd dynamics set is not triggered. + In Take 1 the 2nd dynamics set is not triggered.