That workflow would depend on the DAW, not lilypond. For the automatic "synchronization" you're suggesting in step 7, the DAW would have to actively monitor a midi file for changes. Lilypond has nothing to do with that.
As a workaround, if the DAW allows re-importing the midi file without losing automation you've added since last import, it's simple enough to just drag the new Lilypond-generated midi file into the DAW's timeline. As long as you're not editing the actual pitches (or velocities) inside your DAW, I'm pretty sure e.g. Pro Tools would do this easily & non-destructively. Inside the DAW you do all your tempo / volume automation, instrument changes etc, and just replace the midi file whenever you've made changes. If you've changed the form of the piece (made the middle longer/shorter, for example), then anything after those edits would not get shifted to match, of course. Now if you're *editing the actual midi data* in the daw, and expecting Lilypond to catch that, well, that's much more complicated and currently not anywhere near in place. ~ Peter Jaques :: www.huzzam.com ~ May 30, 2019, 11:37 PM by [email protected]: > Hi David, > >> There may be incentive to synchronize the contents of those files. >> > > Yes, that’s the part I’m currently most interested in: synchronizing a > Lilypond input file (or set of files) with a DAW file (or set of files) via a > MIDI file (or set of files). > > At the very least, I’d like to hear if anyone has worked out (or even > attempted) a workflow like the following: > > 1. Write a Lilypond input file. > > 2. Use Lilypond to generate a MIDI file or files (e.g., one per staff or > instrument/staff-group). > > 3. Load those MIDI file(s) into a DAW. > > 4. Make edits to the DAW file (e.g., add a tempo track, modify volumes, etc.). > > and then [this is the critical part!] > > 5. Make a change in the Lilypond input file. > > 6. Use Lilypond to overwrite the associated MIDI files. > > 7. See the changes reflected instantaneously in the DAW, while affecting > ("ruining"/"reverting") the least number of changes made in the DAW in Step > #4. > > Thanks, > Kieren. > ________________________________ > > Kieren MacMillan, composer > ‣ website: > www.kierenmacmillan.info <http://www.kierenmacmillan.info> > ‣ email: > [email protected] <mailto:[email protected]> > > > _______________________________________________ > lilypond-user mailing list > [email protected] <mailto:[email protected]> > https://lists.gnu.org/mailman/listinfo/lilypond-user > <https://lists.gnu.org/mailman/listinfo/lilypond-user> >
_______________________________________________ lilypond-user mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-user
