On Wednesday, September 28, 2011, Niek van den Berg wrote:

> So a repetition should be over all tracks (and therefor
> segments) at a certain time. Like a time signature, which changes all time
> signatures at the same time for all segments.

I think I would just take the middle road on this myself.

Try to use the segment repeating properties to tell you where repeats should 
be written, but if things don't add up, it's OK for the export to fail with a 
warning.

Something like this would work:

track 1  |: segment :||: segment :|
track 2  |: segment :||: segment :|
track 3  |: segment :||: segment :|

Something like this would just fail:

track 1  |: segment :||: segment :|
track 2  |         segment        |
track 3  |: segment :||  segment  |

"MusicXML export expects all repeating segments to align on the same 
boundaries.  This composition cannot be exported to this format.  Please 
choose a different export format, or modify the composition.  Go to [wiki 
page] for details on this issue."

I suppose I'd handle this with some pre-processing step to examine the overall 
structure of the composition, and check for repeat flaws before going on to do 
anything else.

Something like that seems just about right.  Even if we did come up with some 
better overall solution to the existing kludge, the kludge is deeply 
entrenched in all the existing .rg format literature, and has to be dealt with 
one way or another, because it's out there, and we'll encounter it.

I still have files that warn me about deprecated controller types, from way 
before Rosegarden 1.0.  Maintaining compatibility with everything all the way 
back to the dawn of the file format is something Rosegarden is unusually good 
at.
-- 
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

Reply via email to