> Event List event filter has filters for "Generated Region" and "Segment
> ID". They seem to be related to Phrase -> Figuration.
>
> I fooled with this for a little while and as yet have utterly no clue:
>
> 1) What's this stuff for?
I would've gotten back to you sooner, but I was coding all day.
Generated Region is support for the figuration functionality. The idea of
Figuration is to expand (say) triads into (say) arpeggios. It's handy if
you are doing a lot of figuration, especially over several instruments.
You make a Segment of just chords - say, triads, though the newer stuff
can handle chords with different numbers of notes. You make another
segment with one example of the figuration, and you mark that bar with
Phrase -> Figuration. Usually I put both these segments on a silent
track. Then you select both and Segment -> Expand Figurations.
But the more I used it, I bumped into its limitations. When I first wrote
Figuration, it had the problem that if you changed chords or figuration,
to make the change take you'd have to erase the generated segment(s) and
generate it (them) all over again - it's still easier than rewriting every
note, though. Also, I started wanting to do fancier stuff to figurations,
like volume or expression and adding lead-ins and codas, but when I
regenerated figurations it would erase that stuff. I was able to work
around that but it was work.
So I made Figurations able to regenerate its stuff. To do that, I had to
record where all the stuff it made came from.
So the Event types involved are:
* Generated Region marks a region (like a bar or two) that was generated
and tells which segments came from. It's almost like an indication
except I needed more fields.
* Segment ID is how it identifies a segment. I needed something that
would survive segment-joining and other stuff that could happen to the
C++ segment ID.
* Figuration is an example figuration to be expanded. The code tries to
be smart about expanding it to your chord segment.
* ParameterChord: Suppose you have a C major arpeggio on the first bar,
then you want the same thing on D minor in the second bar. Originally
the only way was to show it a C major triad, and it would know that when
the chord changed to D minor, step all the C's to D's, all the E's to
F's, etc. Nowadays it's optional. If ParameterChord is missing, the
logic will fit the figuration to the chords in a different way.
All of which I know is pretty hairy.
> 2) What is the potential use of the event filters?
IIRC, I did that for EventList mostly for inspecting & debugging.
> 3) After I made a Parameter Chord and a Figuration I still had no
> events of either types showing up in the event list.
I hope my instructions above were good enough. There are also some older
docs on the wiki.
Tom Breton (Tehom)
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk
_______________________________________________
Rosegarden-devel mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
