Programmable real-time audio signal processing application
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

notes.txt 6.2KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161
  1. TODO:
  2. + When a cmMsgList item is selected it should send out the selected index
  3. after the individual data items rather than before them - this way the index
  4. can be used as a definitive signal to perform some action on the previously
  5. transmitted data items.
  6. + cmJson and cmLex should report the name of the file when with syntax error messages.
  7. + Use CSV for mod score file format (to eliminate need for labels)
  8. + Autoload of default pgm cfg, program, enable audio, sequence, score location.
  9. + Circuit switcher patch.
  10. + Review and document the app threading and locking during audio file loading.
  11. + Remove old performance evaluation code from cmScore.
  12. + All programs should be able to reload without crashing via enabling/disabling audio.
  13. + Select and save audio devices.
  14. + (done) Mac Conversion
  15. + (done) Live MIDI - to test audio/MIDI delay.
  16. + (done) As threshold increases overall volume decreases - add a compensation algorithm.
  17. + There are unintialized variable warnings on the release build.
  18. + Add preset delete.
  19. + All uses of va_copy() should have a complimentary va_end()
  20. *** 8/13
  21. * Cross-fade was cutting out during demo.
  22. * Missing takes between seq 7 and seq 8.
  23. * The MIDI is mis-aligned against the audio.
  24. * Are cost / tempo working? ... test changing mode.
  25. * Add an automatic volume adjustment to prevent parameter changes from causing large volume changes.
  26. * What can we actually do between after a MIDI note is received? Is it already too late to
  27. send parameters w/o affecting the attack of the note.
  28. * Live Test material
  29. Part 1: Meas:76 - (one measure) to get measurments for later sections
  30. Part 1: Meas:94 (sect 38) through Meas:136 (include 136 stop at 137).
  31. Part 2: ("/Users/kevin/temp/piano score part 2 draft 1 master m 232 - 241 1st 2 bts.sib")
  32. The downbeat of part two aligns with the 3rd beat (in 4/4) of 122 in the first part.
  33. Ends on measure 131 at end of beat 3.
  34. *** July 10
  35. ** (done) Make separate mappings and scale/range controls for left and right.
  36. ** Add EQ output stage.
  37. ** Work out the speaker setup.
  38. ** Add capture/playback. Analyze notes on capture and do not play if there are
  39. any wrong notes. (Skipped notes however are acceptable.)
  40. **
  41. ** When a section transition is occurs late - (e.g. due to dropped notes) do not apply
  42. the transformation all at once - instead either ramp it in or step it in on subsequent
  43. attacks. Section transitions which are positively identified are intended to have
  44. dramatic changes so applying the updated parameters immediately is acceptable - but
  45. when the parameters are changed mid-section they should be much applied subtely.
  46. ** (done) Build a database of measurements and setup the program to be able to
  47. apply a given measurement at it's assigned section.
  48. ** Redevelop spectral distortion algorithm to use a spline as the transform.
  49. ** use Log frequency frequency transform instead of FFT.
  50. ** Allow for a continous window size via zero padding.
  51. ** Add a 'write' preset file button - so the preset file can be saved prior to next crash.
  52. ** measurement values can generate MAX_DBL - be sure that are not being sent through to the audio algorithm.
  53. (see ln:965 cmDspKr.c for a hack to fix this)
  54. ** add invert to scale/range to cause output to go in opposite direction.
  55. ** non-grace eveneess are used to generate a measurement value from previous tempo calibration section.
  56. (non-grace evenness notes therefore have two scores: 'evenness' and 'overall-duration').
  57. ** note that the default setting for dyn and even.
  58. ** add dyn,even,tempo,cost number boxes to allow artificial setting of these parameters.
  59. add dyn,even,tempo,cost as modulator variables to allow them to be set from the modulator
  60. With these additions we can simulate apply measurements at the 'application' section.
  61. ** add begining and ending measure numbers to 'seq' labels
  62. ** Gain compensation for mode 4.
  63. ** Do IFFT using cos()^c + i * sin()^c - these bases are orthognal but cause harmonic distortion.
  64. To be efficient this might involve writing an FFT function.
  65. // May 22
  66. ** Crashers (Should be tested but are probably already fixed following score follower debugging.)
  67. Seq 2 m24 Mark 36 & 38
  68. Seq 4: Mark 115
  69. Seq 4: m76-79 Mark 129 (W/ meas: even & dyn -> thresh change min Thresh to 40) - use 4th seq w/ b1
  70. Seq 6: m92 Mark 143
  71. Seq 7: m103 Mark 173
  72. Seq 7: Mark 172 Meas 103 - always crashes on playback.
  73. Seq 4: Mark 76 Meas 40 - crash!
  74. Seq 2: First mark meas 23
  75. Crash seems to happen in cmProc4.c: _cmScMatchInitMtx() ln:1311.
  76. It looks like a memory overrun. Looks like the first line is wrong
  77. shouldn't:
  78. if( rn >p->mrn && cn > p->mcn )
  79. be
  80. if(rn*cn > p->mrn*p->mcn)
  81. BUGS:
  82. // Apr 20
  83. The tempo measurement can produce invalid values. Set score to 22 then play Mark 38.
  84. First tempo measurement is a non-sense value - probably produced by an div by zero.
  85. Also: Mark 8, Meas 10.
  86. Crash on playing Mark 37.
  87. Click on list control outside below list item - crash!
  88. Select Mark 171 (Seq 7) Section 43, m103 crash
  89. // Feb 27
  90. + Audio seems to preceded MIDI by around 250ms this probably arises
  91. from a delay that was inserted by 'mas'. Can the delay be removed?
  92. // Feb 25
  93. + Fix the audio file input/output ports
  94. //
  95. // Feb 6 & 7
  96. //
  97. + Performed notes which arrive which about 50ms could be
  98. considered chords. Extra notes notes which were not part of
  99. the chord are probably common and should be discounted during
  100. the cost analysis.
  101. + (done) Add alignment cost as a 4th variable along with dyn,even,tempo.
  102. + (done) In the score print out (score_loc.txt) Section 2 is starting on Bar 5
  103. when it should start inside Bar 7.
  104. + In Take 1 the 2nd dynamics set is not triggered.
  105. + In Take 3 Eveness 2 the C2 and F#4 are NOT missing althrough they are in the
  106. evalation. Also E7 which ends that set is not marked with an 'e'.
  107. + It is possible to have even-non-grace sets where the note rythm value's are not
  108. all the same (e.g. bar 20 )
  109. + User soft-thresholds for the dynamics categories.
  110. + Set 39 even measure 25 shows the first note as G#2 when it should be C#1
  111. + Missig MIDI note sounded:
  112. C1 score-loc:132
  113. A#2 140
  114. A5 173
  115. C#2 195 Marker 36
  116. E5,G33,A#2,C#1 212-218 Marker 36
  117. E3 185 Marker 37
  118. F5,C#4,G#5 986 Marker 204