Le jeudi 27 mai 2010 01:34:04, Julie S a écrit : > I am interested in allowing more robust editing of triggered segments. To > that end we would need a way to play them back in tempo with a desired > instrument, and display them in a user defined time signature. > > If we can not do this in a good way, then I think we should not allow > editing / playback of triggered segments in the fashion the patch provided > allows. >
I agree totally. > > What if we keep triggered segments as they. Limited editing via the event > list editor, and no out-of-context playback. I can't imagine myself writing music with such an editor (Lilypond text is far easier to use)... I don't know for other users... Some years ago, when I first played with triggered segments (I'm afraid I never did it since), I used copy/paste from/to notation editor to edit the triggered segments. If we can't get a correct playback from the editors the patch enables, perhaps should we just gray out the transport buttons on this editors ? > > We can still consider using the triggered segment mechanism to create > sym-links. But sym-links would not show up in the triggered segment > manager or be available as ornaments. I'm still wondering, but probably you are right. > The basic idea would be: > * Create a regular segment on the track canvas. > * Use a "Convert to Sym-link Source" command (name negotiable). > * Now when the segment is selected, we can copy / or paste it as a regular > segment (which will be a new sym-link source segment distinct from the > first), or we can copy / paste it as a non-source sym-link. More simple : * Use a "Link command" or "Copy as Sym-link" (with a special tool ? or Shift + alt + ... ? or anything else ?) on any regular segment and you get a symlink from this segment. * Use the same command on a sym-link and you get a copy of the sim-link (a new sym-link of the original regular segment) * Use some "Transform Sym-link into copy" command to create a regular segment from a Sym-link. Actually, I don't see the need to store the sym-link source segments in any special place. But maybe I forget something... I need to think again about it. > > * Source sym-links can be viewed and edited in the notation / event / > matrix editors. * Non-source sym-links can only be viewed in these > editors. > > I'm a bit concerned that distinguishing these different types of segments > on the track canvas could get confusing. We need some sort of decoration to distinguish the sym-links from the regular segments. May be only write the segment name with italic characters on the sym-links ? A tooltip may be useful here (there is currently no tooltip on segments). > > * We could put energy into devising a way make it clear. > * We could let users just use labels and colors as appropriate to come up > with their own system. I would like sym-links, by default, inherit color from their original regular segment. Then the user would be allowed to change the color if he/she prefers. > > I also wonder how to best handle deleting source segments. > * Should we delete all related non-source sym-link segments? A user may like to keep a trace of where the sym-links was. > * Should we make the next non-source sym-link the source and have all the > related non-source sym-links point to it? The composition may become rather strange... Why not keep the Sim-links pointing to nothing (making it obvious with some appropriate decoration as a black color or naming them "NULL" or something else...) as what is done for Sym-links in a file system ? > > Michael and I are in agreement that we should be able to adjust the pitch > (like we can with triggered segments), but I'm not certain the best way to > do this either. * A dialog box that allows the adjustment to be made when > a non-source symlink is double-clicked. * An addition to the Special > Parameter Box. > * Other thoughts? To use some Segment Parameter Box extension seems consistent with the actual GUI. Nevertheless I have no real preference here. Yves ------------------------------------------------------------------------------ _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
