Hello Yves,
Concerning:
> One problem is that triggered segments will be edited with
> time signature
> coming from the composition.
> That's already the case with Ian's patch: Modifying the
> composition time
> signature changes the way the triggered segment is
> displayed in the notation
> editor.
>From what I can gather using RG Classic (assuming in trunk), a triggered
>segment seem to use the first time signature in the composition.
This conclusion was derived via experiments of adding / removing time
signatures from the composition to see how they affected the measuring in the
triggered segment editor and the event list editor.
>
> It would be better to edit each triggered (or source)
> segment with its own,
> neutral, tempo ruler and time signature and, therefore, not
> to show such
> segments in the main view.
>
> The instrument use to ear this segments may be defined from
> a dialog, the same
> way currently the metronome instrument is defined.
I see your points on here, but if we instead used a triggered segment track,
which would be a specialized MIDI type track. Then users could use RG's
current functionality to select the instrument to associate with the segment.
Also the user could place the triggered segment on the canvas where the time
signature occurs. Therefore, we could determine the time signature based on
the time signature ruler.
Again this fits in with how RG already works on several levels.
I think dialog boxes and user assigned neutral time signatures is self
limiting. What if the user is writing a complex segment that requires several
time signatures to properly display the segment? Will we plan for this option?
...
Though I see your point and believe that assigning a time signature is valid.
I think the best benefit would come from allowing triggered segments to be
placed on a special track on the canvas.
We have deep history of doing things this way. It may not be the best way, but
it has been the RG way for a long time -- shortcoming and all.
...
Some if we choose dialog boxes:
* How will a user here a triggered segment played back?
* Will we provide a special preview feature in the instrument selection box, to
avoid having the segment be played back with the rest of the composition?
* How will we handle playback when user is editing a triggered segment? They
press play and expect to hear the segment in isolation or in time with the
music... Hmm (this was already mentioned)
* What tempo will we use (the first in the composition), or will we allow them
to set the tempo for the preview or special playback as well?
My point with these questions is that there are several aspects of editing
these segments that are difficult address cleanly.
In my mind the creation of a specialized triggered segment track, solves much
of this. Provides a consistent UI, and reuses much code already in place.
...
Some bullets about the design:
* Create a new track type that accepts triggered segments. There can be as
many triggered segment tracks as the user likes. These would be modeled after
the MIDI tracks. Possibly a subclass with some extra features to tie them with
the triggered segment manager.
* If a triggered segment doesn't appear on the new triggered segment track,
then the RG traditional behavior of using the first time signature applies, and
whatever traditional choice of instrument is also used (behavior stays the
same).
* For triggered segments that appear on the triggered segment track, they
should also appear in the triggered segment manager. They will use the
instrument based on the track settings for the Triggered Segment tracks. The
time signature is derived from the time signature ruler and the segments
position in the composition.
* Deleting a triggered segment from the manager or from the triggered segment
track will delete it from both places (probably with notice if the segments are
actually tied to triggered events or "sym-links").
* Moving a triggered segment from one triggered segment track to another
allowed.
* Moving from triggered segment track to non triggered segment track, removes
the segment form the triggered segment manager (probably with notice if the
segments are actually tied to triggered events or "sym-links").
* If a segment from a non triggered segment track (except Audio track) is
placed on a triggered segment track, it is added to the triggered segment
manager and may be used as a triggered segment.
* A triggered segment can only appear once in the composition. If copies are
made and placed, they are distinct from the original (traditional copy of
segment).
* If we implement a symlink feature, we could allow an additional copy as
symlink, or paste as symlink (based on ease on implementation).
...
I think that is plenty to consider. But that all hinges agreement of
developing a new track type for the RG main canvas.
Well, those are my thoughts.
Sincerely,
Julie S.
------------------------------------------------------------------------------
_______________________________________________
Rosegarden-devel mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
