On Wednesday 28 September 2011 18:21:47 D. Michael McIntyre wrote: > 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 | >
To be honest, I never really understood how repetition ware implemented in Rosegarden and never got it working. But this example puts me on another path. I will walk it and see where it leads me. > 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 can tell you a lot of stories concerning compatibility. No need to convince me here :-) Best regards, Niek ------------------------------------------------------------------------------ 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
