On Monday, September 26, 2011, Niek van den Berg wrote: > measure 7. This what I ment by "real" repeats. Every part shows a repeat > start and end at the same location in the part.
We do have support for those, through segment repeats, at least to a limited extent. It is also possible to do 1 and 2 endings, but this is very crude. Come to think of it, Niek, I need to step back and see how things have changed after Yves did his work on the anacrusis problem before I try to explain this to you. Some things may have changed. > However in part two there is another repeat in measure 3. This measure > repeats measure 2. This is what in my opinion the segment repeat > represents. I did not implement such a measure repeat because segment not > allways starts or end at a measure boundary so simply writing out the > measure repeat is the savest way to go. We don't have the % measure repeat at all, no. I seem to remember there's another kind of repeat too, maybe //, and we don't have that one either. These are rarely encountered in trumpet music anyway, and I haven't missed them. In any case, the problems we have with repeats and flow control in general come from being a sequencer under the hood, rather than a notation editor. It's much more complicated trying to make things like 1-2 endings, coda, segno, DC, DS, etc. work inside a sequencer. That's why all of those things are faked out, and don't work properly, or at all. The time axis is completely linear and only moves one way in Rosegarden, whereas a program like MusE Score can just loop back and jump around at will; even having different timelines in different parts, presumably. We tried to figure out how to get flow control to jump around in Rosegarden too, but we came away with numb minds, and a desire to run away and forget about it. It is one of those things that seems just possible, but it's so ridiculously complicated as to make one bleed out the ears thinking about it. It's the one truly monumental obstacle to trying to do a full-bodied notation editor on top of a sequencer, instead of just working in notation and generating MIDI on the fly at playback time the way all the real score editors do. > I see MusicXML as a vehicle to communicatie with other programs like > mscore. Next step is a MusicXML importer (still working on it) so there > will be a two way communication. It will help to exchange music to other > people who are not using Rosegarden yet :-). Import sounds like a very good idea if you can make it work. Hans Kieserman wanted to do a LilyPond importer years ago, and it proved too complicated. MusicXML looks like a more realistic problem to tackle. -- D. Michael McIntyre ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
