Re: [Rosegarden-devel] Track: Bug or just normal behaviour in the Merge function?

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

Chris Cannam wrote:
> William wrote:
>> * 10. Observe that the composition is still only 1 bar long,
>>      and there is no sign of the n-bar long composition having been
>>      merged at bar 2, where one would expect to find it, or indeed
>> in any of the 101 bars of the composition.
> 
> When I tried this, the merge worked correctly both times.  BUT 
> Rosegarden merged the file into new tracks, which (because the 
> default composition has 64 tracks already) I had to scroll down quite 
> some distance to see.

I see RG "merges" the imported tracks onto track numbers 65,66,..., and
also makes the imported tracks start from bar 3, which is counter-intuitive.

The "merge" operation in its current form seems more like a strange hybrid of

  1) re-numbering the imported tracks from an existing range of track numbers
    of (Tfirst,Tlast) to a new range of (Tfirst+64,Tlast+64), and
  2) adding an offset of 1 bar to the start time of the imported tracks.

I think the "merge" should both preserve the existing track numbering of the
imported tracks and make the imported tracks start at the end of
the final segment in the existing composition, which in this example
happens to be bar 2.

William