From: D. M. M. <mic...@ro...> - 2008-01-27 22:11:00
|
On Sunday 27 January 2008, Aurelien wrote: > Oh, well, that's my nick, actually. It means Wladimir Ohrelianov II, see > there: http://sebkhachott.websanslimit.net/ohreland/ohreland_genesis.php > ;) Ah. > OK, I'm gonna send it to you. I got it. I haven't had time to think about whether there's anything good we can do with this. Usually I try to set things up so that I have one set of segments that will come out correctly as notation, and another set of segments that come out correctly for playback, but in this case with the time signatures, I don't think that's going to be possible. (See the example file lilypond-alternative-endings.rg for a small demonstration of what I mean.) I just don't see a way out of having a different file for playback, unfortunately. The two can't coexist, and the only way to fix the notation is to close up the gaps. So for starters, define a loop/range from 9 to 21, and cut it. I tried to do another range from 11 to the end, and cut that, but it didn't work, so I shortened the composition (Composition -> Change Start and End Time) to only 10 bars. Then you have to stick some LilyPond directives in here to get 1. and 2. endings (and 3. or more are not currently possible) with an Alt1-> somewhere in the first bar of wherever the alternate is supposed to begin (not clear from this text) and Alt2-> in the last bar. It's all quite unpleasant, I'm afraid. Just barely possible, but possible. Sort of. See attachment. (Super compressed so maybe this post will go to the list without being rejected.) That gets a long way, but there are still problems with rendering the little squiggles as tr in LilyPond. I bet this is because they're trying to go out as a long trill, and the note is too short. It would display tr /\/\/\/\/ on a longer note, I bet. This long trill is something Heikki did for me just before some previous release, and it caused more problems than it cured, I fear. We need to give that some more attention. I already have a related bug report open, and this looks like the same phenomenon. > By the way, does Rosegarden/Lylipond know this |1. 2. |3. notation ? I > suppose it's quite hard to program, probably more than a simple > repetition, isn't it? It is. That's why we don't really support it, except through the kludge "LilyPond Directive" mechanism. Even then, we only do two endings, but I think the code is there for up to four, just commented out. I don't remember why I commented it out. I haven't done up a tutorial of this, since it was a lot shorter than I was imagining. Let's see if what I've said is enough. Plus I'll mail you back my modified file. -- D. Michael McIntyre |