A: Known “must have” features - without which TWO is not suitable for purpose in many contexts.
1 - MIDI out clock sync. I will then add MIDI in clock, followed by Timecode I/O.
2 - Triggering playback of individual loops - e.g. analogous to Ableton’s “Session View”.
3 - “Offset” interpolated curves in timelines need more control over shape - the current ease-in, ease-out doesn’t give enough shape control. Bezier points for example, would improve this.
4 - MacOS build version is trailing behind the Windows one by a lot.
5 - DMX fixture definition in TWO, and through loading standard files.
B: Good to have features - it’s usable but the user experience is sub-optimal.
1 - Keyboard navigation throughout.
2 - Multiple selection and manipulation outside timelines (where it is already implemented per lane).
3 - Automatic crash reporting with Sentry should be added.
4 - Simultaneous selection and editing of keyframes also across lanes.
C: Known bugs - and if known, temporary workarounds.
1 - Right-click menu in clips panel fails to stay engaged.
2 - Keyboard controls can stop working.
These bugs are fixed with 0.12.5:
1 - Very rarely, looping in timelines can stop.
2 - Looping fails to send messages after the first iteration, if the ending loop-point is before the last message in the clip. The temporary workaround is to use a clip where there are no more messages after the end loop-point. - Under some conditions looping fails to send messages in the transport.