>>>>> "Brian" == Brian May <[EMAIL PROTECTED]> writes:
As of 0.9.91-1:
Brian> 1. Of my tune, one track is set to device #1 timidity
Brian> 128:0/general/72 Clarinet. Another is device #2 timidity
Brian> 128:0/general/74 Flute. The rest (another 4) are device #3
Brian> timidity 128:0/general/acoustic grand piano. However all
Brian> tracks are played back as piano (yes this was working
Brian> yesterday). I have tried resecting these details, but it
Brian> doesn't help.
Something is still a bit weird here. I am not sure what though. Its a
bit too weird to document in too much detail.
At one stage, when inserting notes on a track, it played the note back
using Piano. When playing back the whole thing it used Clarinet. This
was despite the fact it should only have used clarinet.
In another case, if I selected each track in turn, the display on the
left said channel 1/piano, when it actual fact the track was using
another channel (as indicated in menus).
Brian> The following apply to the notation editor:
Brian> 2. It takes approx 5+ seconds just to enter/change/undo a
Brian> note. This tends to be frustrating when entering a lot of
Brian> notes.
On a faster machine (3GHz), speed is acceptable, on this machine though:
model name : AMD Athlon(tm) XP 1800+
cpu MHz : 1535.233
Speed is still very sluggish. I find it hard to understand why a
computer that can render MPEG at 25 fps on a full screen display
(mythtv) cannot cope with entering notes on at a time on a music
score.
Brian> 3. If I mis-enter a note (seems to be easy to do as
Brian> rosegarden forms its own opinion where the note should go,
Brian> not nessarily the position of the mouse), sometimes I will
Brian> try to correct by the undo operation (ctrl-Z). On some
Brian> occasions rosegarden will not delete the note from the
Brian> display, but continue drawing it even though it is no
Brian> longer possible to select it.
Brian> 6. No obvious way of modifying chords. Especially timing. I
Brian> have ended up in a big mess trying to change the timing of
Brian> a chord. Even deleting the choord and re-entering it
Brian> doesn't help, on reentering the choord rosgarden sometimes
Brian> insists on treating each note seperately (and increases the
Brian> total length of the bar to match).
3+6 are related issues. Fixing incorrect notes is still quite
challenging at times.
Brian> 4. I have 2/4 time selected. As I enter notes in the left
Brian> hand side of the bar, the half rest is pushed over to the
Brian> right, making the total number of beats in the bar exceed
Brian> the maximum of two. Can't it count? The "normalize rest"
Brian> feature does fix this, I would have hoped this could happen
Brian> automagically (in fact it usually does). Normalizing such a
Brian> bar has a side effect of messing up bars to the right.
I already said this, but for clarity will past and copy my previous
message here as it is still relevant:
I suspect the problem here is that rosegarden has automatically
entered rests at the beginning of the tune (e.g. by manipulating the
start time to 1.5 beats past the start). However, it appears that
sometimes rosegarden inserts the wrong length rest.
Perhaps a better example: 4/4 time. The music starts on the 4th beat, so
I instruct the track to start on the first bar and the fourth beat.
This is fine if I just imported the file as a MIDI file, if the tack
was nothing but rests though, sometimes the first bar gets a 4 beat
rest. This is despite the fact it is only 1 beat long.
I select this rest and select the "normalize rest" function, and it
fixes this bar up, but messes up the next bar (it now has 4+3 beats of
rest). If I had any notes on the 3rd bar, they would get pushed back
by 3 beats too.
So I select the entire bar and the "normalize rest" function, but I
suspect the problem still exists, just past the end where I can't see
it (so if I enlarge the track I will have problems again).
I hope this explanation makes some sort of sense ;-).
Music that doesn't start on the first beat seems to be pretty common,
but maybe this hasn't been tested enough in rosegarden4.
Sometimes rosegarden can get very confused, I have only just listed
the major problems.
Brian> 5. I have the D minor key, or one flat (B flat). For some
Brian> reason rosegarden insists on modifying other notes in
Brian> wonderful ways I haven't requested or wanted. For example,
Brian> it wanted to make a low C sharp. I have to explicitly make
Brian> it natural. In fact, it seems to be using the last modified
Brian> value I used for the note, which was back several bars
Brian> ago. I consider this wrong. Standard music rules say that
Brian> all modifications cease to exist at bar boundaries.
Issue 5 is totally fixed. Please disregard.
Brian> 7. Cut and pasting or moving large chunks of notes can
Brian> really mess up the display at times, I haven't worked out
Brian> why. Undo doesn't always fix such problems.
Not tested. I have observed situations where the display is completely
messed up. Normally I just back out with Undo.
I haven't used it enough yet to determine if there was any
improvement.
Brian> 8. When entering a note with the mouse, it should be
Brian> possible to cancel entry of the note while the left mouse
Brian> button is still down, e.g. by pushing the right mouse
Brian> button or pushing escape.
Still an issue. I often end up waiting three times: once to insert the
wrong note, once to remove it, and once to add the correct note.
Brian> 9. Something seems really screwy with the timing today on
Brian> playback. Normally timing on this computer works great. I
Brian> haven't been able to work out what the problem is yet
Brian> though (it might be skipping notes).
If this cannot be reproduced (I doubt it), feel free to disregard. At
the time of the test, amavisd-new may have been hogging more CPU then
expected (not sure why), this (combined with the fact I was using
timidity at real-time priority) may have missed things up.
(Note: this doesn't solve 2).
Anyway, thanks for packaging Rosegarden. I hope these issues can be
resolved sometime in the future.
PS. Did you mean to close bug #291171? It is still open.
--
Brian May <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
