Programmable real-time audio signal processing application
Du kannst nicht mehr als 25 Themen auswählen Themen müssen mit entweder einem Buchstaben oder einer Ziffer beginnen. Sie können Bindestriche („-“) enthalten und bis zu 35 Zeichen lang sein.

notes.txt 17KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391
  1. CONTENTS:
  2. 1) TODO List
  3. 2) OSX Install Notes
  4. SPAT LAB SETUP:
  5. + 1. Stereo
  6. a. TotalMix - select 'diff. stereo' snapshot
  7. b. mixer: Recall preset 91 ('stereo diff')
  8. + 2. Direct - 24 channels - each channel goes in and out on same number.
  9. a. TotalMix - select 'DTS_24ch'
  10. b. mixer: Recall preset 96 ('24ch firecac ufx')
  11. STRATEGY:
  12. + implement highly parallel version - which can take advantage of multiple processors
  13. to do more - acoustic pitch tracking, source separation based fades
  14. TODO:
  15. + When a cmMsgList item is selected it should send out the selected index
  16. after the individual data items rather than before them - this way the index
  17. can be used as a definitive signal to perform some action on the previously
  18. transmitted data items.
  19. + cmJson and cmLex should report the name of the file when with syntax error messages.
  20. + Use CSV for mod score file format (to eliminate need for labels)
  21. + Autoload of default pgm cfg, program, enable audio, sequence, score location.
  22. + (done) Circuit switcher patch.
  23. + Review and document the app threading and locking during audio file loading.
  24. + Remove old performance evaluation code from cmScore.
  25. + All programs should be able to reload without crashing via enabling/disabling audio.
  26. + (in new version) Select and save audio devices.
  27. + (done) Mac Conversion
  28. + (done) Live MIDI - to test audio/MIDI delay.
  29. + (done) As threshold increases overall volume decreases - add a compensation algorithm.
  30. + There are unintialized variable warnings on the release build.
  31. + Add preset delete.
  32. + All uses of va_copy() should have a complimentary va_end()
  33. + The list boxes do not show the currently selected item.
  34. + (done)MIDI note messages are sent but do not trigger notes on OSX.
  35. *** Usage Notes
  36. live - Disconnects WT cmd input (WT will not receive an 'on' msg)
  37. Disconnects TL reset input (TL will not receive a 'reset' msg)
  38. Disconnects MFP sel input (MPF will not receive an 'on' msg)
  39. Switches audio input to KR from WT to AIN.
  40. Turn the 'meas' checkbox 'on'.
  41. simulate - Turn the 'audio in' checkbox 'on'.
  42. Switch MFP output from SF to Nano.
  43. (SF MIDI input then comes from the MIDI port.)
  44. audio in - Switch audio input to KR from WT to AIN.
  45. meas - Instruct the SF to generate measurement outputs for the active meas. unit.
  46. Otherwise the measurements must be loaded from the recorded measurment list.
  47. print - Print a report from the SF.
  48. quiet - Turn off SF output.
  49. LA Secs - Fragment recd/play unit look-ahead time in seconds.
  50. Fade DbpSec - Framgent recd/play unit fade out time
  51. (time to fade to 0 following a fade msg)
  52. *** Cross-fade Notes
  53. Cross-fades are initiated by sending any msg to the 'AvailCh.trig' input.
  54. The 'AvailCh' object then toggles the parameter router channels and xfader gates.
  55. Only after this should the new parameter values be transmitted either from
  56. the 'ActiveMeas' object (through the scale range chains) or directly from the
  57. 'ScMod' object.
  58. Sending parameter values prior to triggering the 'AvailCh' will result in the
  59. parameters being sent to the currently active 'Kr'. This will result in two
  60. possibly unintended effects:
  61. 1) The effect of the parameter will be heard immediately - possibly resulting in distortion.
  62. 2) If a subsequent trigger is sent to 'AvailCh' the parameters will be routed to
  63. the fade-out (current) channel rather than the fade-in (next) channel.
  64. **** Live Test Score
  65. + Line 1048 has a red G#5 immediiately following another G#5. Is this correct?
  66. For now the second G#5 has been marked as a 'skip'.
  67. + Changed Tempo sections 25,26,27 to 40,47,47a
  68. + Measurements are taken for sections 51-54 but these sections follow bar 136 and
  69. are therefore outside the test. These sections have therefore been redirected
  70. to the downbeat of 201-204.
  71. *** Testing Notes:
  72. + Equipment List:
  73. Four Microphones: Four performance/ Four recording
  74. 2 inside 2 inside
  75. 2 overhead 2 overhead
  76. 4 powered speakers
  77. 2 Mixers (1 performance 1 recording)
  78. Performance Computer (harpo)/ Audio Interface (delta1010) / MIDI interface (Fastlane)
  79. Recording Computer (crel) / Audio Interface (delta 1010) / MIDI interface (???)
  80. Sensor Strip
  81. + Performance Setup
  82. +------ +
  83. Mic0 ----------->| |
  84. Mic1 ----------->| | sends +-----+ +-------+
  85. Mic2 ----------->| |------->| A/D | | | +------+ +--------+
  86. Mic3 ----------->| Mixer |------->| |------>| harpo |<-------| MIDI |<-----| sensor |
  87. aux | | | | | | +------+ | strip |
  88. Spkr0 <----------| |<-------| |<------| | +--------+
  89. Spkr1 <----------| |<-------| | +------ +
  90. main | | | |
  91. Spkr2 <----------| |<-------| D/A |
  92. Spkr3 <----------| |<-------| |
  93. +-------+ +-----+
  94. + Software Development
  95. 1) Create Score File
  96. 2) Create Recording Program (test with long MIDI playback generating audio - look for drift)
  97. Record the index of each MIDI event at it's location in an audio channel.
  98. 3) (DONE) The ability for the measurements to be called at the correct time must be built in.
  99. (or alternatively to use stored effects).
  100. 4) Effects applied to the playback fragments.
  101. 5) Allow all variables and patch connections to be set from the scMod script and have
  102. multiple scripts with varynig effects setups.
  103. 6) All 4 input mic's should go through the computer in order that they remain in phase
  104. (even though the overhead mics will not be used in the effect).
  105. 7) Add comb filters tuned according to the current MIDI notes as an additional effect.
  106. 8) Add EQ output stage (use mixer).
  107. 9) Compressor on input (???).
  108. 10) The dry signal should be able to be routed to seperate output channels - around the compressor.
  109. 11) CROSSFADE BUG - (DONE?) This may be fixed by the change to cmDspAvailCh which
  110. handles the case where no channels are available by sending an error message
  111. but not actually changing the state of the cross fader.
  112. 12) Create a mode in scMod which increments values based on an onset detector. So that
  113. changes only happen on attacks. This still doesn't help if the pedal is down (or
  114. if notes are sustained) but otherwise might be a better way to ramp parameters.
  115. 13) When scanning past ramping variables in scMod the end value should be
  116. taken as the next variable(???) - this is not necessarily correct
  117. because one never knows where a timed change may end - maybe ramped
  118. variables should include a 'skip value' giving the next ambient value
  119. for the ramped variable - experiment with this to figure out what works.
  120. + Experiments:
  121. 1) Speaker placement and live/electronics mix.
  122. 2) Sliver mix level
  123. 3) Try varying degree's of effects
  124. *** 11/19
  125. + The recd/play fade should be able to trigger from a capture note as well as
  126. playback note. An offset might also be useful.
  127. (Should be a default fade for each fragment - keyed to the input. This
  128. will be the fade that will occur when
  129. + Allow setting fade time in the score.
  130. + Allow setting fade rate based on 1.0 to 0.0 from fade point to end point.
  131. + Allow for multiple fades markers per fragment. (what does this mean?)
  132. + Write code to ignore playback when the score follower is not stable -
  133. or to throw out fragments where there is a mistake.
  134. + At the end of each fragment recording the fragment should be truncated by the look-ahead time
  135. to avoid capturing the attack of the marked note.
  136. + FX on fragments.
  137. + MUST be able to record synchronized audio and MIDI during test performance.
  138. + Part 2 data analysis: analyze the order of notes in counter rhythms.
  139. *** 11/1
  140. + Change the wavetable to read stereo files or add a second wavetable to play the other channel.
  141. + The console window is not always updating from the bottom.
  142. + The 'Dump' button results are not going to the console window.
  143. + Put dry signal into separate output channels.
  144. + Add 'adaptive' mode parameters to scale/range mappings.
  145. + The 'meas'->'parameter' mappings should changable from scMod (mod0.js)
  146. + The 'adaptive' mode parameters (e.g. offset and invert) need to be connected in the patch.
  147. + Create a mode in scMod which increments values based on an onset detector. So that
  148. changes only happen on attacks. This still doesn't help if the pedal is down (or
  149. if notes are sustained) but otherwise might be a better way to ramp parameters.
  150. + Mark all notes in the score according to how well they would act as places to transition.
  151. Notes held while the pedal is down would not be good places to transition.
  152. These indicators would then be used to determine where a section change can occur
  153. when the actual section change is missed.
  154. + (done) All score_loc's and event indexes in meas0.js that beginning with
  155. score location 743 must be decremented by two. (e.g. loc 743 becomes 741 ...)
  156. (score_loc_1.txt is now the correct score file)
  157. + When scanning past ramping variables in scMod the end value should be
  158. taken as the next variable(???) - this is not necessarily correct
  159. because one never knows where a timed change may end - maybe ramped
  160. variables should include a 'skip value' giving the next ambient value
  161. for the ramped variable - experiment with this to figure out what works.
  162. *** 10/17
  163. Select bar 129.
  164. Start on F5 before 129.
  165. Score follower jumps to loc. 978 then backs up to 973.
  166. *** 9/27
  167. * (DONE) Implement live recording for use in part 2.
  168. * Implement a delay between when a new section is set to trigger and when
  169. it actually does. This might allow transitions to be set up prior to when they are heard.
  170. * (DONE) OS-X version crashes when the printf("PROCSET ...) is removed from _cmScProcSets().
  171. * Add ability to set mappings and perf. measure settings to scMod.
  172. * The scMod should play through all changes up to the cur starting location so that
  173. we can mimic the state of playing the piece through but allow starting from any location.
  174. * Experiment with changing settings using the scMod ramping functions.
  175. * Make a source separation based fade using an filter/inverse filter based on the
  176. spectrum prior to the cross-fade. As an extra feature notice the state of the pedal
  177. and decay appropriately.
  178. * The electronic score needs the ability to specify that the output is sent to the audible
  179. cross-fade channel rather than the inactive channel.
  180. * Add a score mode that performs some action (e.g. incr/decr) on each incoming score follower
  181. event.
  182. * In AvailCh what happens when no available channels are found - this may be the cause
  183. of the cross-fade cut-out problem.
  184. * Add eq stage to output.
  185. * Setting the upper slope to a negative value is effective.
  186. * Demo Material: Seq 8 Mark 204 (1024-4 2048-4) Fade 10ms Cost->Threshold.
  187. - recd7 Mark 151
  188. - recd8 Mark 145 - same settings a previous take.
  189. - (recd9) Mark 145 - w/ changing xfade switch to mode 4 at 38
  190. - recd10 Mark 145 - same w/ no mode change
  191. - recd11 Mark 145 - a. 3 different takes w/ score constant - no perf. parameters used - fixed threshold=65
  192. - recd12 Mark 148 b.(same settings as recd9)
  193. - recd13 Mark 151 c.
  194. - recd14 Mark 161 Section 40 - fixed changes see mod0.js for note
  195. - Seq 6 Mark 145 M-92 (38,39,39a) (recd16) (recd17) (recd18) (recd19)
  196. - Seq 7 Mark 167 M-100
  197. *** 8/13
  198. * Cross-fade was cutting out during demo.
  199. * Missing takes between seq 7 and seq 8.
  200. * The MIDI is mis-aligned against the audio.
  201. * Are cost / tempo working? ... test changing mode.
  202. * Add an automatic volume adjustment to prevent parameter changes from causing large volume changes.
  203. * What can we actually do between after a MIDI note is received? Is it already too late to
  204. send parameters w/o affecting the attack of the note.
  205. * Live Test material
  206. Part 1: Meas:76 - (one measure) to get measurments for later sections
  207. Part 1: Meas:94 (sect 38 (Seq 6)) through Meas:136 (include 136 stop at 137).
  208. Part 2: ("/Users/kevin/temp/piano score part 2 draft 1 master m 232 - 241 1st 2 bts.sib")
  209. The downbeat of part two aligns with the 3rd beat (in 4/4) of 122 in the first part.
  210. Ends on measure 131 at end of beat 3.
  211. MISSING MIDI for measures 114:126
  212. *** July 10
  213. ** (done) Make separate mappings and scale/range controls for left and right.
  214. ** Add EQ output stage.
  215. ** Work out the speaker setup.
  216. ** Add capture/playback. Analyze notes on capture and do not play if there are
  217. any wrong notes. (Skipped notes however are acceptable.)
  218. **
  219. ** When a section transition is occurs late - (e.g. due to dropped notes) do not apply
  220. the transformation all at once - instead either ramp it in or step it in on subsequent
  221. attacks. Section transitions which are positively identified are intended to have
  222. dramatic changes so applying the updated parameters immediately is acceptable - but
  223. when the parameters are changed mid-section they should be much applied subtely.
  224. ** (done) Build a database of measurements and setup the program to be able to
  225. apply a given measurement at it's assigned section.
  226. ** Redevelop spectral distortion algorithm to use a spline as the transform.
  227. ** use Log frequency frequency transform instead of FFT.
  228. ** Allow for a continous window size via zero padding.
  229. ** Add a 'write' preset file button - so the preset file can be saved prior to next crash.
  230. ** measurement values can generate MAX_DBL - be sure that are not being sent through to the audio algorithm.
  231. (see ln:965 cmDspKr.c for a hack to fix this)
  232. ** add invert to scale/range to cause output to go in opposite direction.
  233. ** non-grace eveneess are used to generate a measurement value from previous tempo calibration section.
  234. (non-grace evenness notes therefore have two scores: 'evenness' and 'overall-duration').
  235. ** note that the default setting for dyn and even.
  236. ** add dyn,even,tempo,cost number boxes to allow artificial setting of these parameters.
  237. add dyn,even,tempo,cost as modulator variables to allow them to be set from the modulator
  238. With these additions we can simulate apply measurements at the 'application' section.
  239. ** add begining and ending measure numbers to 'seq' labels
  240. ** Gain compensation for mode 4.
  241. ** Do IFFT using cos()^c + i * sin()^c - these bases are orthognal but cause harmonic distortion.
  242. To be efficient this might involve writing an FFT function.
  243. // May 22
  244. ** Crashers (Should be tested but are probably already fixed following score follower debugging.)
  245. Seq 2 m24 Mark 36 & 38
  246. Seq 4: Mark 115
  247. Seq 4: m76-79 Mark 129 (W/ meas: even & dyn -> thresh change min Thresh to 40) - use 4th seq w/ b1
  248. Seq 6: m92 Mark 143
  249. Seq 7: m103 Mark 173
  250. Seq 7: Mark 172 Meas 103 - always crashes on playback.
  251. Seq 4: Mark 76 Meas 40 - crash!
  252. Seq 2: First mark meas 23
  253. Crash seems to happen in cmProc4.c: _cmScMatchInitMtx() ln:1311.
  254. It looks like a memory overrun. Looks like the first line is wrong
  255. shouldn't:
  256. if( rn >p->mrn && cn > p->mcn )
  257. be
  258. if(rn*cn > p->mrn*p->mcn)
  259. BUGS:
  260. // Apr 20
  261. The tempo measurement can produce invalid values. Set score to 22 then play Mark 38.
  262. First tempo measurement is a non-sense value - probably produced by an div by zero.
  263. Also: Mark 8, Meas 10.
  264. Crash on playing Mark 37.
  265. Click on list control outside below list item - crash!
  266. Select Mark 171 (Seq 7) Section 43, m103 crash
  267. // Feb 27
  268. + Audio seems to preceded MIDI by around 250ms this probably arises
  269. from a delay that was inserted by 'mas'. Can the delay be removed?
  270. // Feb 25
  271. + Fix the audio file input/output ports
  272. //
  273. // Feb 6 & 7
  274. //
  275. + Performed notes which arrive which about 50ms could be
  276. considered chords. Extra notes notes which were not part of
  277. the chord are probably common and should be discounted during
  278. the cost analysis.
  279. + (done) Add alignment cost as a 4th variable along with dyn,even,tempo.
  280. + (done) In the score print out (score_loc.txt) Section 2 is starting on Bar 5
  281. when it should start inside Bar 7.
  282. + In Take 1 the 2nd dynamics set is not triggered.
  283. + In Take 3 Eveness 2 the C2 and F#4 are NOT missing althrough they are in the
  284. evalation. Also E7 which ends that set is not marked with an 'e'.
  285. + It is possible to have even-non-grace sets where the note rythm value's are not
  286. all the same (e.g. bar 20 )
  287. + User soft-thresholds for the dynamics categories.
  288. + Set 39 even measure 25 shows the first note as G#2 when it should be C#1
  289. + Missig MIDI note sounded:
  290. C1 score-loc:132
  291. A#2 140
  292. A5 173
  293. C#2 195 Marker 36
  294. E5,G33,A#2,C#1 212-218 Marker 36
  295. E3 185 Marker 37
  296. F5,C#4,G#5 986 Marker 204
  297. -------------------------------------------------------------------------------
  298. OSX - Install Notes
  299. -------------------------------------------------------------------------------
  300. 1. Install macports
  301. 2. Install git-core (sudo port install git-core)
  302. 3. sudo port install fftw-3
  303. 4. sudo port install fftw-3--single
  304. 5. port select --list gcc (which gcc is active)
  305. 6. sudo port install gcc47
  306. 7. sudo port --set gcc mp-gcc47
  307. 8. sudo port install fltk
  308. 9. sudo port install xorg-libX11
  309. 10.sudo port install git-core
  310. 11.sudo port install emacs +x11
  311. 10 install ~/Library/Preferences/org.larke.kc.txt (is this required?)
  312. 11 create ~/Library/Preferences/kc
  313. 12 Install ~/Library/Preferences/time_line.js, time_line_preset.js, time_line_preset.csv