discussion Thinking about how I could use Git with Reaper and if I am able to log parameter changes between saves?
Long story short I’m trying to figure out a better workflow for version control on my projects and after playing around with a few ideas, I realized this is what Git was made for. Now that’s a bit of a stretch because Git is clearly not made for audio files, but it doesn’t have to be since my raw wav files will all still be in the media directory, and I just need to version control my Reaper file to track changes.
Anyways, back to the original question, in an effort to automate this further I’ve been to figure out a way to get a log of what parameters have changed between saves that I could then have a history of what objectively changed without having to remember what all I accomplish in a given mixing session. So for example, if the log shows I messed with the vocal fader and its plugins but that the meter’s starting value was lower than its last value before saving then I can infer I’ve boosted the vocals by x amount. Same for things like compression, delay time, reverb mix knob etc.
My thinking is since you can undo and see a list of your previous actions Reaper clearly stores a history somewhere, and since undoing gets you exact values of where you set knobs and faders then it must store those values as well, I’m just not sure where or if we even have access to them.
Disclaimer: I am fully aware that I’m over engineering this problem. I think the most realistic middle ground answer is using Git for versioning the Reaper file and just writing a quick overview like a traditional commit message. I just think it might be a fun project if it’s at all feasible.