|
@@ -40,6 +40,42 @@ Equipment List:
|
40
|
40
|
7) Scissors for contact mics
|
41
|
41
|
|
42
|
42
|
=============================================================================
|
|
43
|
+Take sequence builder development notes.
|
|
44
|
+
|
|
45
|
+1. The MIDI file implementation should not overload the use of the
|
|
46
|
+ 'dtick' field in cmMidiTrackMsg_t to contain multiple possible
|
|
47
|
+ meanings of time (e.g. tick,microsecond,seconds,samples etc) or at
|
|
48
|
+ the very least the current meaning of the field should be held as a
|
|
49
|
+ flag in the MIDI file. As it i s the field is ambiguous and it can
|
|
50
|
+ be difficult to tell what the meaning of the field is in any given
|
|
51
|
+ algorithm that processes it.
|
|
52
|
+
|
|
53
|
+2. Sostenuto pedal should be added to the score and then implemented
|
|
54
|
+ in cmMidiFileCalcDurations(). When the sostenuto pedal is down
|
|
55
|
+ only notes that are playing when the pedal is depressed are
|
|
56
|
+ sustained.
|
|
57
|
+
|
|
58
|
+3 As current written the UI control architecture supports only one
|
|
59
|
+ user interface element (kcApp.h::ctl_t) per DSP instance. This
|
|
60
|
+ limitation is manifest in kcApp.h::find_ctl() which has no way
|
|
61
|
+ to distiguish which of multiple ctl_t's to return from a given
|
|
62
|
+ instId. In fact this problem probably goes deeper into the
|
|
63
|
+ way that Fl_Widgets and DSP instances are assocated.
|
|
64
|
+
|
|
65
|
+4. TODO:
|
|
66
|
+ a) When pedal events are inserted via cmGrTksrFltk the inserted event
|
|
67
|
+ is shifted backward in time.
|
|
68
|
+
|
|
69
|
+ b) Test the save/restore function of TakeSeqBldr render takes.
|
|
70
|
+ c) TakeSeqBldr load should be threaded.
|
|
71
|
+ d) Eliminate direct communication between cmGrTksb/rFltk and cmTakeSeqBldr.
|
|
72
|
+ All communcation should be serialized.
|
|
73
|
+ e) Run with valgrind to see if cmGrGksb/rFltk has any obvious bugs.
|
|
74
|
+ f) bar select / take select logic is difficult.
|
|
75
|
+ g) There is often a NAN shown in the position select display UI.
|
|
76
|
+ h) Add bars to the cmGrTksrFltk view.
|
|
77
|
+
|
|
78
|
+=============================================================================
|
43
|
79
|
CHANGES TO SIMULATE MODE TO ALLOW MIDI FILE PLAYER TO DRIVE SCORE
|
44
|
80
|
FOLLOWER DIRECTLY RATHER THAN FEEDING SCORE FOLLOWER FROM MIDI INPUT PORT:
|
45
|
81
|
|
|
@@ -57,6 +93,12 @@ BACK TO:
|
57
|
93
|
|
58
|
94
|
|
59
|
95
|
=============================================================================
|
|
96
|
+Session Notes 3/28/15
|
|
97
|
+1. 34-38-49-54 (good take sequence)
|
|
98
|
+2. Try combining bins in the SpecDist algorithm as a variaion on the spectral distortion algorithm.
|
|
99
|
+ For example the bins coud be combined using a Bark grouping.
|
|
100
|
+
|
|
101
|
+
|
60
|
102
|
Session Notes 12/12/14
|
61
|
103
|
1. Write a tool to create multiple MIDI preformances of the piece.
|
62
|
104
|
a) Map each segment to the score using the score follower.
|
|
@@ -688,8 +730,7 @@ Sequence Editor Design
|
688
|
730
|
Enable/Disable selected events.
|
689
|
731
|
|
690
|
732
|
|
691
|
|
-
|
692
|
|
-
|
|
733
|
+
|
693
|
734
|
|
694
|
735
|
|
695
|
736
|
=============================================================================
|