[Rosegarden-devel] Re: [Rosegarden-user] In search of sane cut and paste...

[Chris C. <ca...@al...>]

On Thursday 19 May 2005 07:31, ro...@lu... wrote:
> On Wed, May 18, 2005 at 02:45:39PM -0400, Silvan wrote:
> > The most immediate problem with doing
> > anything of this nature is that there are not currently any "track
> > level" properties for anythinga
>
> Ooooh.  That's a wrench in the works.

I've been reminded of this thread by a post you made on LAU today 
("[t]he notation editor in Rosegarden might one day start to become 
usable, but right now it's one of the most frustratingly poor programs 
I've used").  It's always frustrating to read something like that, not 
because I have any dispute with the particular things you have reported 
having found difficult about it, but because of the obvious lack of 
time and programmerpower available to us to act on everything that is 
reported.

I get the impression from your posts here that your problems have been 
mostly what may be technically relatively minor troubles (though with 
their subtleties) in Rosegarden that affect you seriously because they 
are in conflict with the ways of working that you find natural.

 * What Michael says is true -- there are no track-level defaults.  
That's because they're at instrument level, not track level.  
Conceptually this probably is still the level you're looking for.
 * Clef currently exists as an event, it can change, and it has a 
default of treble if no clef is set within a segment.  There is no 
instrument or segment default.
 * There is a Segment transpose option, and you can easily set this on a 
set of segments at once.  I don't know why it's set at Segment level 
instead of Instrument.

I don't imagine that the lack of a track-level default clef is the cause 
of all your problems.  Can you summarise the things that are causing 
you grief?


Chris