the #rust #tui #daw is actually starting to look cool!

some things in the code become unwieldy where shared ownership is involved. it gets tricky because the model and the view aren't really decoupled.

one feature important to me which #ableton does not provide: being able to extend clips across scenes ("remove stop button" doesn't count)

this is probably the most advanced rust code that i've written so far. i've seen way more complicated codebases but this is as far as my cognitive capacity stretches. especially considering my cure for anxiety and depression is sleep deprivation (don't do that kids 🤣) always can waste 3 more months rewriting it in #zig - or finally get with the program and configure better ide integration for rust in #neovim

delete key now removes clip (instance of phrase) from arrangement.

wondering whether to store a separate set of phrases in each track (sequencer), or have a global phrase pool for the entire project (so the same phrase can be instantiated on multiple tracks and play with multiple voices)

the first (track contains clips) is more conventional, the latter (track contains *instances* of clips) seems simpler to implement and honestly just so much more flexible to use

@unspeaker
> so the same phrase can be instantiated on multiple tracks and play with multiple voices
It's not uncommon — playing the same phrase with different instruments, but I think it would be… cynical to make those links to the same instance of the phrase 😅
I think Live makes a copy when you do this — because often you have to modify the phrase for a particular instrument anyway.

@m0xee cynical is exactly what i'm going for 😅 cloning an instance of a phrase so it can be edited separately is still gonna be 1 action away, but not supporting instantiation at all is i'd say barbaric 😭

@unspeaker
Yeah, good point! It's not an audio signal, but a control stream — cloning on demand would probably take microseconds anyway.