From: pbennison <pbe...@ip...> - 2003-11-29 04:04:51
|
Crashes, Extending Score, Change of Key Signature Date: Sat, 29 Nov 2003 14:20:57 +1030 User-Agent: KMail/1.5.4 MIME-Version: 1.0 Content-Disposition: inline Status: RO X-Status: S X-KMail-EncryptionState: N X-KMail-SignatureState: N To: ros...@li... Cc: Chris Cannam <ca...@al...> Content-Type: Multipart/Mixed; boundary="Boundary-00=_heBy/r0nR9Ud62p" Message-Id: <200...@ip...> --Boundary-00=_heBy/r0nR9Ud62p Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi A few problems using Version 4-0.9.5 (downloaded cvs 28/11/03): 1. I am having problems adding bars to my score. I have 102 bars so far, but need another 70 or 80 to complete the piece. I have tried grabbing the stave in the Segments Canvas screen, but can't take it beyond the scroll bar - for some reason the scroll bar acts to stop adding more bars to the stave. It would be useful to be able to add bars while in the Notation Editor. 2. The piece I am working on at the moment requires changing key from G Major to C Major. However, when I applied the change (through Edit/Add Key Change), I expected to see a natural sign appear in the next bar on the stave to indicate the key change - nothing showed. In the snapshot rg1, you can see the natural sign applied to F as the modulation to the new key, but nothing in the next bar to confirm the key change. 3. I am experiencing crashes on a frequent basis. Sometimes I can predict when this is going to happen, because when I use the "Undo" functons rg inserts more rests than the bar should carry, ie in a 4 beat bar there will be 7 or 8 or 9 beats worth of rests. The next operation I perform (usually inserting a note) will cause the crash. Snapshot rg2 shows an example of excess rests in a 4 beat bar as a prelude to a crash -no pun intended. 4. I am not sure if this next one is a problem/issue or not in terms of the way in which rg operates - when I cut or delete notes from the stave, the rests which replace them are 2 minim rests rather than the original semibreve rest generated by rg when the stave is first opened. It doesn't matter too much if the bars are subsequently re-written, but where a bar or two of rests is required by the music, theoretical correctness requires a semibreve rest for the whole bar rather than two minim rests. It would be helpful in this regard if rg could default to semibreve rests whenever a cut or deletion of notes is applied. Snapshot rg3 shows the situation. Thanks in anticipation Paul Bennison |