3 ms·
Ha, that's funny, I abandonned lilypond precisely to create combined stave/tab scores more easily. I found that flipping back and forth between the lilypond "so
by zwp 6y ago
Ha, that's funny, I abandonned lilypond precisely to create combined stave/tab scores more easily. I found that flipping back and forth between the lilypond "source" and the rendered result was too slow. I read music notation much better than lilypond's "musical LaTex" notation and I found it hard to remember the nuances each time I came back to it. (Adding lyrics to an existing piece was the last straw).
I switched to Musecore. Although I generally eschew GUI apps I much prefer it to LP: I can see my editing changes directly without the "compile, run" steps. My efforts are less DRY, to continue the programming metaphor (eg copy/paste the chorus) but that's acceptable. I don't plan on writing any massive symphonies. As @rekado elsewhere on this page, I don't have to act-as-programmer when I'm making music.
Musecore has had lots of criticism of its design but that area has apparently improved a lot recently. It might be "Word for music" but it's a mostly-complete-but-simple version (so... Word 6? AbiWord?). Works for me.
- rekado 6y ago> I found that flipping back and forth between the lilypond "source" and the rendered result was too slow. I found Frescobaldi to be a decent compromise in that regard as it serves as a decent Lilypond editor while keeping the rendering of the score up to date at the same time. Personally, I'm going to experiment a little more with tighter Emacs and perhaps Org mode integration. I don't care for the full score at all times, so using Lilypond as a server and sending it only short snippets to be displayed in an Org mode babel buffer might be a viable option. (I know that you can tell Lilypond to skip time and only start rendering after some offset, but I'd rather not have to keep adjusting that offset number all the time; it also doesn't work so well for pieces with different odd meters.)