On Sat, Sep 17, 2011 at 10:17:26AM -1000, Joel Roth wrote: > I'm still working on this. Last night I tore out > some ugly old code. That always feels good. Out with the old, in with the new! > > I'm also thinking about a couple other issues: > * using git to manage project data > * latency compensation > > Latency compensation, if well thought out, > might even allow you to use a hardware effect > via the soundcard as an insert, and still > keep alignment with all the other signals. That would be seriously cool! > > One issue is calculating the latency in > the different arms of the signal-processing network. > A second issue is determining the latency of > other components of the system, such as the > soundcard input and output, that might need > to be factored in. I'm not sure how you would achieve the first, but the second can be fairly easily done using a utility like Fons adriansen's jack_delay and a patch cable on the sound card. > > Git might help branched development. > Thinking about syntax, perhaps something like this: > > nama> save sax_left -m "mix with sax placed to the left" > > If save_state/git-commit is fast enough, every change of > state could be stored as a commit, useful for undo/redo. Really funnyyou should mention that. Yesterday I just completed a fairly big (to me) project for someone, something like 8-10 tracks with loads of plugins and fades (nama held up relatively well BTW, though I will follow up with a list of bugs :-) ). Anyway, I saved often, of course using names like roughmix[1-9], polishedmix[1-9], finalmix[1-9], etc, but soon started to forget which number was at which stage and wished for something more like a revision control system with timestamps and "changelogs". Eventually, I grew dissatisfied with my first mix/treatment of the vocals and link_tracked to a second, alternate vocals track and ended up with 2 final mixes to show. At this point, I would have sold my soul for an RCS style mechanism. So, to cut a long story short, I'm very interested in this idea. Cheers, s.M.