Comment by delgaudm
19 days ago
I'm a voice actor, and I live in Reaper -- it's my "IDE" as it were. I like the idea of the git branching metaphor. Would you say that your DAW is primarily for musicians, or for more general purpose recording (i.e. a voice actors workflow)
You can already use git with REAPER right now, plain and simple.
REAPER’s project files are all very git friendly.
Simple add/commit/push, etc. Of course, if you’re going to be sharing a REAPER project in a repo, you should enable LFS, and have a smart project structure for your works. If collaboration through a repo, with tagging and branching, is part of your setups workflow, this already works quite well with REAPER projects.
However, I have to say that since REAPER allows full control over literally years of recording sessions, the whole concept of having the ability to go back and forth through different versions of the art—form being recorded (music, vocals, etc.) is already well provided in REAPERS sample-accurate ‘reflog’.
;)
I have built it because I'm a musician. That being said I am interested in serving my customers / community and am open to what features would be needed / what user experience would be desired.
How has your business been affected by AI?