Package: rosegarden
Version: 1:1.6.0-1
Forwarded: [EMAIL PROTECTED]
Severity: Normal
X-Debbugs-CC: [EMAIL PROTECTED]

Forwarding this bug which was originally reported to the rosegarden-user
list to the Debian bug tracking system....

thanks,
stew

----- Forwarded message from Chris Cannam <[EMAIL PROTECTED]> -----

From: Chris Cannam <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED],
        Paul Ulrich Niggli <[EMAIL PROTECTED]>
Subject: Re: [Rosegarden-devel] [Rosegarden-user] bug in debian unstable
Date: Tue, 18 Dec 2007 20:15:37 +0000

On Tuesday 18 December 2007 15:59, Paul Ulrich Niggli wrote:
> I think, i found a bug in debian-unstable package
> of rosegarden.when i save tempo-changes as
> fixed,they get opend as ramp to following tempo.

OK, thanks for the test files and description off-list.  I was simply 
misreading the problem -- it's to do with saving files, not loading 
files.

To reproduce without an example file:

 * start RG (1.6.0) with empty composition
 * add new (non-ramped) tempo change with any tempo other than 120, at 
any point after the start (anything that makes the tempo actually 
change)
 * save the file
 * reload it
 * note that the opening tempo is now ramped to the one you just added

This is a pretty significant bug -- the sort of thing one rolls out a 
point release for, when it's fixed.  We have to fix it first of course.

Thanks for the report.


Chris

-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Rosegarden-devel mailing list
[EMAIL PROTECTED] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel

----- End forwarded message -----

Attachment: signature.asc
Description: Digital signature

Reply via email to