-
Notifications
You must be signed in to change notification settings - Fork 12
/
TODO
411 lines (327 loc) · 18.6 KB
/
TODO
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
TO DO for Seq66 0.99.12
Chris Ahlstrom
2019-04-13 to 2024-01-13
Build:
- Add "make install" support to qbuild.sh.
- Figure out these compiler warnings on the Arch Linux box:
/usr/include/qt/QtCore/qnamespace.h:360:10: warning: type
‘Qt::WidgetAttribute’ violates the C++ One Definition Rule [-Wodr]
360 | enum WidgetAttribute {
Misc:
- Fix and test new record/quantize handling, and verify that
MIDI automation of these displays in the pattern editor.
- Make sure metronome buttons etc. still work. Recorded measures
not saved.
- The Carpet song has PPQN = 120 and displays weirdly in pattern editor.
Too difficult to fix at this time; converted it to 192.
- Show time-sig events in grid slot?
Mutes:
- Mutes via MIDI control, in Learn mode, do not raise the modify
asterisk. Why not???
- If inactive, set "Mute File" setting to "not enabled".
- Consider showing, as a run-time toggle, the mute hot-keys, rather
than the mute number, in the mute-master buttons.
Playlists:
- Consider adding a configurable play-list auto-advance delay value?
- Set all contrib/midi and data/midi MIDI files to use port 0?
From Testing:
When zooming, try to keep the same viewport in view. Got this working
for horizontal seqroll and perfroll, but not for vertical (refactoring
needed). Try to center vertically on notes in the viewport.
Make it center on notes if not visible.
Can we distinguish note-insertion from movement snap, to avoid the
"L"-then-snap-then-move samba?
File errors (fixed!), but odd issues (w/qsynth):
'/usr/local/share/seq66-0.99/midi/FM/judyblue.mid' plays, but some
notes are blipped out. Try with another player.
'/usr/local/share/seq66-0.99/midi/FM/longhair.mid' plays just fine
mostly, some glitches.
The 'usr' time-color settings do not seem to work. Actually, it does
work, but not with the Qt gtk styling.
Awaiting complaints/issue-reports:
- Contrary to Seq24:
- Grid-Solo-Click currently acts like Alt-Left-Click.
- Shift-Left-Click opens the corresponding external live grid.
- Ctrl-Left-Click wants to create a new pattern.
- Right-Ctrl-Left-Click does NOT do a queue action.
- Holding Alt is supposed to save the current snapshot, and then
restore it when lifted.
- Holding Ctrl-Alt is supposed to ... cannot tell from SEQ24 doc.
Pending Macros:
SEQ66_SHOW_TEMPO_IN_PIANO_ROLL: leave code in place just in case.
SEQ66_USE_JACK_SYNC_CALLBACK (saved only for reference).
USE_C_MILLISLEEP (related to high CPU in Windows/portmidi builds).
USE_SONG_BOX_SELECT (this will require a lot of work to perfect).
USE_UNICODE_SUPPORT (used only in Cakewalk WRK file support).
USE_ACTIVE_SENSE_AND_RESET (handled in JACK, but not ALSA or portmidi).
USE_SEQUENCE_REMOVE_EVENTS (no code uses this function yet).
USE_ADJUST_DATA_HANDLE (no code uses this function yet).
USE_INTERSECT_FUNCTIONS (could be used for trigger lookup at some point).
USE_TIMEBASE_MASTER (functionality from Hydrogen, not used).
Ongoing efforts:
- Verify setmapper/setmaster for odd set sizes.
- Perfect the "background recording" feature.
- Why does velocity change in data pane not work when starting from the
left in barrage.midi? The Kepler34 "relative change" feature. This
feature is macroed out for now. Perhaps should make it a Ctrl-Click or
something to start it in addition to "would select".
ISSUES:
#44 "Record live sequence changes" functionality
Currently the "record live sequence changes" only adds patterns into the
song timeline as whole loops, starting at the last pattern loop and ending
at the next, and ignoring queueing completely (queueing a pattern just
adds it to the song immediately). It seems to me that a live-oriented
sequencer like Seq66 should have the ability to record a live performance
as accurately as possible, so that a user can simply hit the record enable
and do their live performance, knowing that can then go back and replay it
exactly (if they want to do a recording session for example, or perform
the same track while focussing entirely on knob tweaking etc.) The song
timeline already supports arbitrary start/end points for pattern "chunks",
so it seems like this should already be possible. Thoughts?
1. When recording live sequence changes in song mode, turning "snap" mode
off makes the pattern block start exactly when you press the button on the
Launchpad, like you expect, but the end point always extends out to the
next multiple of the pattern length when you mute it again.
2. With "snap" mode enabled, live sequence changes always snap to pattern
length regardless of the snap size setting in the drop-down box. The snap
size does work when dragging and resizing pattern blocks in the timeline -
except.
3. ...off-by-one error in the snap size drop-down. 1/1 and 1/2 are both 1/1,
1/3 is actually 1/2, 1/4 is actually 1/3 etc. FIXED.
STATUS: Partially fixed. One can now trigger manually
in the perfnames pane, but there are still issues to resolve.
#46 JACK port groups / order?
STATUS: Probably a future feature (version 2).
#52 Community / discussion place?
STATUS: Partly supported now by using github.io, but much more to be done.
#63 Option to rotate pattern numbers?
STATUS: It works for the live grid.
New issue: Verify that it works in other settings.
#66 Toggle MIDI Recording via CC message
I think modes generally should be triggerable individually. Especially if
there will be more to come in the future, it will get messy when you
only have a single button for them. I think that a next candidate would
be for copy and clear mode. In copy mode, the first grid button press
would highlight a pattern and the second one would paste it to the
appropriate slot. On clear mode, the patterns could be emptied or removed
via the grid buttons on the controller.
We could end up with a lot of modes, perhaps more than keystrokes could
support. If a MIDI controller can emit specific D2 data programmably from
0 to 127 (for Notes, D1 is the note number and D2 is the velocity; for
Controllers, D1 is the CC number and D2 is the value), then we could
consolidate modes in one command (and preserve the stepping through the
modes as an alternative for less flexible controllers).
Ideally there would be an automation control for cycling through the modes
and one for each mode separately. Then people could chose if they want to
set up a control that cycles through the options or set up a control that
instantly activates a specific mode.
STATUS: Partly fulfilled.
Can we leverage continuous controllers (CC) to support modifying synth
parameters through input automation? See the new "macro" facility.
#68 MIDI controller initialization step
STATUS: Closed, some follow-on suggestions:
Actually I have been thinking about the mode transition logic and it would
be nice to have support for temporary transition.
Here is my original suggested flow
1. Controller button pressed
2. MIDI CC message with `on value` sent
3. Seq66 reacts to the message and changes modes
4. Controller button released
5. MIDI CC message with `off value` sent
6. Seq66 does nothing
7. ...
8. Same controller button pressed
9. MIDI CC message with `on value` sent
10. Seq66 reacts to the message and changes to neutral mode
11. Controller button released
12. MIDI CC message with `off value` sent
13. Seq66 does nothing
A temporary transition would be engaged by holding a button down on the
MIDI controller and then releasing it later. While the button is held
down, Seq66 switches to the configured mode, the grid buttons can then be
used to engage with the mode. When the button is released,Seq66 switches
back to the previous mode and not to the neutral one. This could be
implemented via a timer that starts when a CC from a button press is
released. If the button is released under a threshold amount of time then
the mode is toggled permamently. If no `button released` CC message is
received within a threshold amount of time then the transition becomes
temporary and when the `button released` CC message is finally received
then Seq66 switches back to the previous mode.
The idea is that with a MIDI controller you could assign different
functions to a single button. It would also fit nicely with a Launchpad
where apart from the grid buttons, there are "mode" buttons on the side.
#76 MIDI Tempo Sync & Real Time Messages Not Behaving As Expected When SEQ66 is a MIDI Slave
STATUS: Some fix(es) made, needs more testing.
#90 seq66 does not recognize some changes for the save entry in the file menu.
STATUS: Ongoing improvements.
Fix pattern is DONE, but needs a way to allow user to back out more easily.
LFO: Reset needs to undo modify, if no modification already in place.
#95 Velocity screen does not fully refresh when scrolling left or right.
STATUS: Still need to duplicate.
#96 MIDI learn (and wizard) for creating controller maps?
STATUS: If we do this, it will be a separate application. A lot of
potential issues in getting this right.
STATUS: Will push off to version 2
#97 Investigate/resolve differences from Seq24.
Seq24: Input from a keyboard when not playing advances like one-shot
mode, but does not stop when looped back as in Seq66.
STATUS: Fixed.
#100 Seq66's MIDI timing completely falls apart at JACK buffer sizer larger than 128.
STATUS: Added a timestamp to each message in the JACK
ringbuffer (enabled by a C macro in libseq66/include/seq_features.h).
This addes a notable burden on process and we can get buffer overflow
errors. Even with message timestamps disabled, the b4uacuse-stress.midi
file can cause failure, especially when the next set is chosen.
At minimum we should stop, clear out JACK, and panic. We found that
there seems to be no way (using methods culled from other apps such as
Ardour) to completely eliminate hiccups in the synchronization of
note input and playback, due to the unavoidable lag between putting the
note in the ringbuffer and taking it out in the JACK process callback.
#102 How can I use mutes?
After some additional experimentation I found out that Seq66 has these
features too with Windows build. However I am not able to to mute patterns
using computer keyboard no matter what I try to do. I discovered mute tab,
but I don't understand what's going on here and I am pretty sure that
plain muting (with queue functionality) is good enough for me.
Muting using mouse works reasonably well.
I am using Windows 7 if this helps with platform specific bugs.
STATUS: It turns out that we needed a different key-map for Windows.
#103 One-shot (repetitions != 0) patterns do not play
This feature works, but requires the pattern to be armed before
playback begins, either in Live or Song mode. Should we make the loop
auto-arm, or make this an option somehow?
#104 Really confusing usage
This requires some improvements to the LaTeX documentation and the HTML
tutorial. One issue is Pipewire, which is unsupported; the user system
employs pulseaudio-pw.
#107 Can't increase clip length while transport is running
Somehow disabled this feature on 2022-08-20, with no note why.
Tried recording using "Expand", and it failed in a spectacular way. Lets
say I have Jack transport running for a while, so that the transport
indicator says 096:X:xxx. (Had it running up to 800 or so and the same
happens:
When arming a pattern for recording using "Expand", the pattern becomes as
long as the number (96 bars in this case) where I press down the keys on my
keyboard. It then loops being 96 bars, until I press down a couple other
keys, where it again expands to whatever the transport indicates at that
point (for example 142:X:xxx).
When no more keys are being pressed, the pattern becomes 142 bars long,
until I press some more keys. And it seems to repeat like that until I
press the Stop button, when it starts over on 001:X:xxx. The pattern length
remains the same though.
STATUS: Closed by the reporter. Undid the change and commented on it.
Need to investigate the second part.
#110 Windows build download
STATUS: works for 64-bit builds, but 32-bit builds work only in
QtCreator, and too many things to do to build 32-bit on a 64-bit
machine. A ton of refactoring and fixes for the damn MIDI Mapper.
#111 Time signature changes does not get saved on .midi file
STATUS: In progress. See README.md for things done so far.
- Ctrl-Z in pattern editor works, but does not restore original
view until pattern is reopened. Not sure why, it should work.
- Verify measure-count changes upon time-sig. In timesigs.midi,
adding a time-sig 8/16 at 4:1 yields one at 10:1 !!!
- We could update the song editor to redraw sequences that
have time signatures; more for appearances, really.
- Can we have time-signature changes shown during playback by
modifying the combo boxes text?
#112 Send midi-control-out message when New Pattern is created in GUI
When creating a new pattern with right click -> New pattern, the new
pattern does not show up on my control surface upon creation. The new
pattern is outlined in red. The control surface does not show the newly
created pattern until I press the button for the pattern itself (or
arm/queue it by pressing w on the keyboard). Seq66 then sends Arm or Queue
midi signals to the control surface, depending on if the keep-queue
function is set (Q in the interface).
STATUS: Added an announce_sequence() call to performer::new_sequence().
Will test.
#114 [feature request] Include keyboard shortcut in setToolTip function?
STATUS: Nearly finished with this one. Also fixing some automation
errors found during this task.
#115 Accessing Non-Registered Parameter Numbers (NRPNs) possible?
STATUS: It works for this user. As a side issue, he would like to
be able to set data values more easily (e.g. exact number)
than by dragging the data line.
Also found a bug: Open brecluse.mid and then pattern #1.
Then attempt to modify the velocity in the data pane.
We find that many of the events were not drawn in the
data pane when the roll was moved by the arrow keys!
Clicking in the event pane forces redrawing.
Using the horizontal scrollbar refreshes properly.
Added some tricky code [flag_dirty()], as already done
in qstriggereditor.
#116 What happened to the "MIDI Ctrl Out (Display) Bus" setting?
STATUS: Cannot duplicate.
#117 Option to close pattern windows with esc key?
STATUS: Done, not yet official.
#118 When enabling virtual ports, make those new ports enabled by default?
Currently one has to tick the box to enable and enter the number of output
and input ports, restart seq66, and then tick all the input port
checkboxes in the list then restart seq66 again.
STATUS: Done, not yet official.
#119 Quantized Record Active does not work
Having this button active has no effect; tried changing snap size to
different settings... Post processing quantize works as expected (i,e,
Ctrl-A then q)
STATUS: Fixed in the portfix branch. An embarrassing misstep!
To close as fixed (and remove from TODO):
24 Release notes in release tag message?
63 Option to rotate pattern numbers?
79 NSM: starts always with a blank pattern
93 The window of a deleted pattern remains open
97 Seq24 differences
To close as pushed off to version 2:
1 JACK Metadata MIDINAM support
62 PipeWire compatibility
68 MIDI controller initialization step
77 For building without JACK
82 Tabs do not scale to window
96 MIDI Learn/Wizard as separate (?) app
MIDI version 2 considerations::
ALSA:
- When toggling a virtual input port, another port with the same
number gets created. Looks like this bug has been around for awhile.
It also yields an ALSA unsubscribe error when disabling an input.
- Use const char * snd_asoundlib_version () to get the ALSA version.
JACK:
- Pulseaudio gone, so now the USB devices (without a2jmidid running)
show up as "0:n system:midi_playback_n+1 'Device name'" (similar
for 'playback') and qsynth as "1:4 qsynth:midi_00". True even if
short port-naming.
Version 2 features:
- Use Meson/Ninja as the build system.
- Support for multiple languages in user-messages.
- Allow for building without JACK dev files installed. Weak JACK
support. Seq66 dependence on the JACK ringbuffer is an issue here.
- Port refresh in ALSA and JACK at a minimum.
- JACK port groups and order.
- Add option to start JACK if not running.
- MIDI Learn. Separate app?
- Pipewire support.
- Live note mapping?
- Abletone Link support?
- Support for audio-clip patterns?
- Add keyboard configuration to MIDI Learn/Wizard.
- Move the Events, Playlist, Sets, and Mutes to a separate window
(the Preferences editor?).
- Make main menu hide-able.
- Allow multiple instances of seq66.
- Allow multiple tunes to be loaded in seq66.
- More consistent support for undo / redo / unmodify.
- Add console output for every user action.
- Add scripting language?
- Clean up kruft in setmapper/screenset.
- Support more than one tune?
- A way to lay out a pattern from one track into another tracks
playback, to re-use the pattern on a differnt buss and channel.
- Support manual reconnecting, including of the control/display busses.
- Implement solo, FF, rewind, etc.
- Use std::numeric_limits instead of macros.
- LV2 MIDINAM support.
- Live note-mapping.
- Pattern Options (would be a new tab):
- New-pattern editor options (check-boxes)
- BPM display minimum and maximum
- Windows build and installer. 32-bit installer cannot work!
- Drag and drop MIDI files onto seq66 (see sequencer64 issue #137)
# vim: sw=4 ts=4 wm=4 et ft=sh