Re: [Rosegarden-devel] Bug? Play continues beyond end of the longest segment

[William <ros...@li...>]

Chris Cannam wrote:
>
>William wrote:
>> Is there a feature request for this on the sf tracker?
>> If not, may I enter one, please?
>
>I can't see one.  Feel free.

Ok.  Repeating my earlier question, shall I also log the 20-30(?) bug reports
and feature requests which I emailed to rg-devel in 12.2003 and my followups
in 3.2004?  I guess I should also log 2-3 bugs I reported which I know have
already been fixed just so that anyone who uses an older version of RG and
finds one of those bugs can easily confirm from the bug tracker that the bugs
have definitely been fixed and thus be encouraged to upgrade to the latest RG.

>Turns out no, it isn't anything more subtle -- it's a failure to 
>initialise the duration of any MIDI event read from a file except for 
>notes.  Setting the composition duration is the only time we look at 
>the duration of anything that's not a note, so it was the only thing 
>going wrong because of this.  Fixed now.

That's great.  Can you post an rc4 or an rc3-rc4.patch.bz2 with the fix please
because sf's anon CVS is badly lagging again.

>The resulting composition does still have the default minimum duration 
>of 101 bars though.

Yes.  I might say, as I've said before, I really can't see the benefits of
even having a composition duration in the first place. I don't like having
to open a dialog to extend the composition duration. If it was my choice
I'd do away with it completely.  Compositions would instead be displayed
with 0 bars, initially, in all of the editor windows until you start
inserting notes/rests/etc or defining new segments etc, at which point
the composition would be automatically and proportionally extended.
Just another whimsical idea...

William