On Wed, Sep 23, 2015 at 06:29:25PM -0400, D. Michael McIntyre wrote:
> On 09/23/2015 02:42 PM, Tito Latini wrote:
>
> > After some tests, I'm noticing the application of notation-quantization
> > (the current "Fix Notation Q...") is useless. Perhaps it is better to fix
> > only the notation time/duration (and not the absolute time/duration), and
> > in this case the name of the command (Fix ...) is appropriate.
>
> I think the intent was to copy the notation duration to the performance
> duration, and remove the notation duration in the process, which gives a
> result similar to performing a grid quantize. I tested just now, and it
Ok, so it is a duplicated command (fast version of grid quantize) but
in a different context (notation view). No problems.
> seems to meet that description. ("Fix" as in "fasten in position" and
> not as in "repair.")
>
> The other day, I entered that rhythmic figure from the tocatta from
> Widor's 5th Organ Symphony, then I used Adjust -> Interpret to generate
> performance durations that articulated the pattern of tenuto and staccato.
>
> In trying to make that trailing rest go away, I attempted to undo the
> interpretation, to use the written duration as the performance duration,
> and undo the rhythmic interpretation.
>
> The long and the short of it is that I was looking for "Interpret -> Fix
> Notation Quantization" and had forgotten what the option was called. I
> tried that just now, and it worked.
>
> I was finally able to get rid of the hated trailing rests. Excellent!
Now it is also useful after the bug fix for "Remove Notation Quantization".
Before the change, the follow example doesn't work:
- one measure with 8th + staccato
- interpret all
- Remove Notation Quantization command
and we get a sequence of 16th without rests. Now "Remove Notat..."
command introduces a new rest if it is necessary, so we get the
correct result. Then we can use "Fix Notat..." to quantize the
new durations (notes and rests).
The next step is to discover if there are weaknesses in
Segment::fillWithRests() and/or Segment::normalizeRests().
In my limitated experience with rg, I have noticed that sometimes
"Normalize Rests" is necessary after a grid quantization but a
quantization uses normalizeRests() internally, so it seems a double
normalization. I want to discover if it is necessary or if it is
possible to optimize that step.
Thanks to clarify any doubt.
------------------------------------------------------------------------------
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
_______________________________________________
Rosegarden-devel mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
