>>>>> "Enrique" == Enrique Robledo Arnuncio <[EMAIL PROTECTED]> writes:
Enrique> I have not yet gone through your list, but just a quick
Enrique> guess: Could this be related to a recent upgrade in your
Enrique> system?
Enrique> The rosegarden4 package you have was built against kde
Enrique> 3.2. But kde 3.3 has recently entered testing, and is the
Enrique> version you are using.
Enrique> You may check if this is the case by installing the
Enrique> version of rosegarden4 in unstable, 0.9.91-1
Enrique> (1.0pre1). It seems that you won't need to upgrade any
Enrique> library for that.
Some of the problems occurred before the upgrade. I was still
productive (not counting the other two bugs I reported) after the
upgrade. It wasn't until the next day everything started frustrating
me to the extent that I had to file a bug report ;-).
I will try the unstable version ASAP and let you know.
Just an update:
>> 4. I have 2/4 time selected. As I enter notes in the left hand side of
>> the bar, the half rest is pushed over to the right, making the total
>> number of beats in the bar exceed the maximum of two. Can't it count?
>> The "normalize rest" feature does fix this, I would have hoped this
>> could happen automagically (in fact it usually does). Normalizing such
>> a bar has a side effect of messing up bars to the right.
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.
Another issue I sometimes encounter is after importing MIDI files the
tracks can be of different length. For some reason when using the
notation editor on such much and viewing all staffs at the same time,
it sometimes will make some bars very big (e.g. one bar per screen
width with mostly empty space). Setting the tracks all to the same
length will fix this. This was with the old version in testing, I
haven't yet tried with the current version in testing yet.
rosegarden4 looks like a program with great potential, just needs to
be a bit more user friendly in places.
--
Brian May <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
