On Sunday 16 Jul 2006 19:08, D. Michael 'Silvan' McIntyre wrote: > OK, brace yourself. This is another long one
Wow, you're not joking! > > These parameters are purely a set of default values for some other > > parameters of a segment. Right? > > Right, except for the clef, which inserts a clef event into each new > MIDI segment you draw or record (clef comes from the track), which > isn't a segment property at all. That's a good point, I hadn't thought about the clef. That works well as an example. > [...] So now it changes all those clefs in all > the other "piano T.C." associated segments throughout the composition > to bass? That's totally wrong. Confusing, annoying, madness. Right. > (Making the "insert this key into all segments at this time" take > segment transpose into account will also add a TREMENDOUS > convenience. Yeah, I agree about that requirement as well. > There is also the conceptual problem. What if I want to use a > xylophone patch for my trumpet part? The idea of a xylophone > instrument (instrument as a container including both MIDI and flesh > and blood instrument parameters) with parameters for trumpet is > confusing. A track designated as a trumpet part that happens to be > playing using a xylophone patch through its associated Rosegarden > instrument (which is strictly a MIDI thing) is an entirely more > logical thing in my view. Possibly. I think that's less persuasive than the rest of the argument. It doesn't seem too wrong to me to have a segment written for trumpet and playing through a trumpet MIDI instrument that just happens to be using a xylophone MIDI patch, if that's what you happen to want. Or rather than say it doesn't seem wrong, perhaps I should say either of them sounds like the sort of playback tweak that would probably be obvious enough not to confuse too much. > > Either way, these "defaults for segment parameters" will presumably > > need some associated actual segment parameters. For example, if > > you can set the default colour for a segment, you also have to have > > a colour parameter in each segment so that you have something to > > set, and in case you want to change it later. > > We have had a segment color parameter for years. Yes, I realise that -- I was just using it as the obvious example before moving on to the range parameters which aren't in the segment yet. Well, your explanation makes sense anyway. I'm persuaded. I think. > complete for 1.3, just as I have been envisioning it in the back of > my head for years. Years during which someone else had every > opportunity to come up with their own implementation of a similar > concept, I might add. I'm writing something that immediately makes > perfect sense to my inner user, and he is happy. Indeed. Often the best way. The one thing related to this that I can remember discussing with any conviction was the idea of having a New Composition dialog that allows you to create a set of staffs for a new score. For example, by saying you want four instruments, that they should be this, this, this and this, and that you want to start with a 40 bar composition. Various good reasons that idea may have foundered include the fact that we didn't really have enough data to make this a meaningful selection (e.g. we lacked data about instrument range and transposition), that the dialog was just a bit complicated to make, etc. Presumably this work might also make that sort of a dialog more effective, if we ever got around to thinking about it again. I'd like to see that. > Digression from above: > > (* Assuming we continue to have to write piano parts on multiple > tracks. I think that's a fair assumption. If I ever get around to doing the multi-voice display/edit I've had in mind for after 1.3, then it will be an optional visual arrangement based on having segments from more than one track display on the same staff (should you want to edit them that way). Chris ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Rosegarden-devel mailing list Rosegarden-devel@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
