From: D. M. M. <ros...@gm...> - 2016-07-14 21:37:08
|
On 07/14/2016 04:20 AM, Yves Guillemot wrote: > Is a preset of the label really useful ? Honestly, I don't even remember writing it that way, and I had to look. So no, it's not that useful. > Indeed this field is lost although the preset values are saved. > It would be fine to save it to remember what these values are. I surely meant to save and restore those values, and just missed something. > Moreover the original preset name should be automatically altered (postfixed ?) > as soon as the change is done. Postfix it with "custom" maybe. > After a preset is loaded there is currently no easy way to remove it and come > back to the default values. True. > The Clef and transpose parameters are stored in the created segment and > memorized with it. The clef parameter causes the generation of a clef, and it isn't really a parameter as such. > The lowest and highest pitches are stored in the segment, but not memorized > (they are lost when the file is saved then restored). Currently these > parameters are only usable in the session where the segment is created. That was an oversight too. > If a segment is created on one track then moved on another track, its lowest > and highest pitches are kept from its creation track, which is probably not > that the users want (these pitches are related to the instrument which comes > from the track). That might be why I attached the label from the preset to the segment. A Bb trumpet segment is still -2 low F# to high C if you drop the segment on an Eb saxophone track. You have to fix it manually. This is one of those things that isn't quite as nice as it should be, but very few people ever use this, and doing it up really nice would be very expensive. Plus there are a lot of behavioral questions to debate. Should it change this when you do that, and what about the other? Instead of getting into that, I just left it up to the user to sync this stuff manually. I think segment symlinks were theoretically supposed to help with this kind of thing, symlink to the trumpet segment and it sounds in a different transpose on a sax track. We talked about that a lot, but I don't think the guy ever got it working, and I know I never did. Again, it can make your head hurt just trying to decide what to do when. > The lowest/highest playable pitch attributes might be removed from the segment > and the same already existing attributes from the track used instead. Semantically, the "Create segments with" parameters are only supposed to change things you have yet to create, so dropping a segment here and having it adopt things from here breaks with that convention. If you think about it, it is also pretty complicated to figure out how to transform the thing automatically, and this is best left up to the user. You drop a trumpet segment onto a contrabass trombone track and another copy on a baritone saxophone track. Now what? Best to let the user deal with this manually. > I wonder about the transpose parameter which is frequently related to the > instrument. Should not it be a track parameter rather a segment one ? > Or maybe the final transpose should be the sum of two parameters, one from the > track and one from the segment ? Historical legacy and backwards compatibility. Segment parameters existed before there were track parameters, otherwise transpose probably would have ended up with track parameters. I wouldn't be very interested in changing that now. -- D. Michael McIntyre |