OK, I think this thread has been derailed by all the discussion about
channel and track mappings, which perhaps has turned out to be mostly a
distraction.
Coming back to an earlier email and a part I didn't reply to:
On Thursday 02 August 2007 00:13, M. Donalies wrote:
> So you want to rename the current class we call Staff to StaffSegment
> or something?
Sounds OK to me.
> My next iteration:
> 1 voice per Segment
> 1 voice per Track
> Composition owns a list of Scores.
As well as the existing list of tracks (i.e. in my mind at least, the
main sequencer view would not necessarily change much -- the score
management views/dialogs would be elsewhere).
> class ScorePart
> {
> StaffType m_staffType; // StdStaff, GrandStaff, StdTabStaff, etc.
> TablatureTuning m_tabTuning;
> map<Segment*, int> m_segmentVoiceMap; // <segment, voice>
> map<int, int> m_voiceSubstaffMap; // <voice, substaff>
> string m_label;
> };
I'm not sure that it's necessary to identify voices directly. Rather
than saying "this segment is voice 0" and defaulting to "voice 0 is
stem-up on the top staff", why not say "this segment is stem-up on the
top staff"? You can always derive voice numbers from this when you
render it all, assuming you need them for user interaction purposes,
and they'll be consistent between renderings. For identifying voices
to the user, the segment names are now perfectly acceptable as each
segment contains material from only a single voice.
We can also use the instrument database stuff (associated with track in
current RG) to define default staff types for segments.
I imagine most of these details would be open to experimentation --
there'll probably turn out to be hideous problems with most of the
possibilities.
> The user configures the Score in a (tabbed) dialog. NotationView has
> acces to Score. If opened by selecting a bunch of segments in
> TrackEditor followed by "Open in Notation View", a new score is
> created using sensible defaults. When the view is closed, user can
> save the Score or just let it be deleted.
>
> Scores get saved in the .rg file. We could do templates and all sorts
> of convenience stuff later.
Yes, yes and yes. Also, when printing to Lilypond or wherever from the
main view, you could choose one of the set of known scores (or
just "everything arranged per default") to print out.
Chris
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Rosegarden-devel mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
