Bugs item #1705031, was opened at 2007-04-21 19:32
Message generated for change (Comment added) made by cannam
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=104932&aid=1705031&group_id=4932
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Matrix Editing VERY Slow
Initial Comment:
Whenever I move, transpose, legnten something in the Matrix editor (Debian, RG 4) I have to wait about 1/2 a min as it spews out this before it's done:
DataBlockFile::getData() : file size = 7
DataBlockFile[/tmp/kde-r00t//rosegarden_datablock_2134566121]: prepareToRead
DataBlockFile::getData() : file size = 7
DataBlockFile[/tmp/kde-r00t//rosegarden_datablock_1759023847]: prepareToRead
DataBlockFile::getData() : file size = 7
DataBlockFile[/tmp/kde-r00t//rosegarden_datablock_1849629632]: prepareToRead
DataBlockFile::getData() : file size = 7
DataBlockFile[/tmp/kde-r00t//rosegarden_datablock_1763473668]: prepareToRead
DataBlockFile::getData() : file size = 7
DataBlockFile[/tmp/kde-r00t//rosegarden_datablock_206510641]: prepareToRead
DataBlockFile::getData() : file size = 7
DataBlockFile[/tmp/kde-r00t//rosegarden_datablock_873139044]: prepareToRead
DataBlockFile::getData() : file size = 7
DataBlockFile[/tmp/kde-r00t//rosegarden_datablock_802460098]: prepareToRead
DataBlockFile::getData() : file size = 7
DataBlockFile[/tmp/kde-r00t//rosegarden_datablock_2013569900]: prepareToRead
DataBlockFile::getData() : file size = 7
DataBlockFile[/tmp/kde-r00t//rosegarden_datablock_481271504]: prepareToRead
DataBlockFile::getData() : file size = 7
etc etc etc.
Why does it do this? Can you make it much much faster. Editing is impossible almost.
----------------------------------------------------------------------
>Comment By: Chris Cannam (cannam)
Date: 2007-04-22 10:37
Message:
Logged In: YES
user_id=13489
Originator: NO
[Note: I am assuming that the author of the previous comment is the same
person as the original submitter of the bug. But I don't know for sure, as
neither was logged in.]
I appreciate your frustration, but you need to understand that the reason
this bug exists -- assuming that a bug in Rosegarden is causing this
problem -- is that no user has reported it before, and so we have had no
opportunity to fix it. Remember that hundreds or thousands of Rosegarden
users have never seen this problem at all: just because it appears to be a
show-stopper to you, does not necessarily mean it is obvious to anyone
else.
If we can't reproduce the problem, then without more information from you,
it may never be fixed. We take reports like this seriously, but our time
is limited, we are not paid to help you, you are behaving rudely, and it is
in any case impossible for anyone to help you unless you are prepared to
provide some more details of what exactly is going wrong.
So, please:
* Are you working with a new composition, or are you editing an existing
MIDI file? If you are editing an existing file, can you reproduce the
problem when starting from a new empty composition instead? If this is
happening when editing an existing file, can you send us a copy of an
example file that exhibits the problem? (Either attach it to this report,
or send it to me at cannam@....)
* What amount of output do you see on the terminal window from a single
editing operation? e.g. if you drag a note up a semitone, how much new
output is printed?
* What version of Rosegarden is this (according to the splash screen)?
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2007-04-21 21:13
Message:
Logged In: NO
Is there anything else I can use besides RG. It used to work fine but now
it's unusable. Or is linux audio dead now? (Or midi). THIS SUCKS.
----------------------------------------------------------------------
Comment By: Chris Cannam (cannam)
Date: 2007-04-21 19:45
Message:
Logged In: YES
user_id=13489
Originator: NO
Thanks for the report.
I haven't encountered this problem before, but the lines you mention are
probably printed out when modifying a segment that contains one or more
system exclusive events. Do you have a lot of sysex's in your
composition?
I have just removed these debug lines in the Subversion trunk, so future
releases should no longer print them, but I would still like to understand
why you're seeing so many of them and why this makes it so slow. If you're
using a slow terminal window or X server, simply printing the debug
information may cause the problem you describe, if there are very many of
them -- but there would have to be thousands, and that would itself be odd.
How many times do messages like that get printed, for a typical editing
operation? Can you describe the result of making one simple change within
a simple segment in the matrix editor, in terms of what is printed on the
terminal window and when? (e.g. is there a long pause between lines
printed, or do they all appear at once?)
It would be helpful if you could register a SourceForge account and log in
before posting, as it makes it easier for us to track future comments in
the report and so on. Also, please give the Rosegarden version number (it
will be 1.something -- the 4 is part of the name, since dropped).
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=104932&aid=1705031&group_id=4932
|
