Donate Share December 2006: Project of the Month

Rosegarden

Tracker: Bugs

9 octave transpose: accidental spelling not kept - ID: 1577030
Last Update: Comment added ( sf-robot )

In the notation editor, if the user uses the feature
(Ctl-UP or Ctl-DOWN or transpose by 12 steps) to move
selected notes up or down an octave, the "spelling" of
the notes is not always maintained. For example, I'm
working on a piece in C major and moved the notes C, B
flat, and A up an octave. When I did this, the B flat
was changed to an A sharp. The same thing happens when
I move these notes down an octave.

Although this could be considered a feature request, I
think that nine times out of ten any user would expect
the spelling of the accidentals to be maintained - that
is the "right thing" for the software to do is to keep
the same spelling. And no one is likely to want the
current behavior. Therefore, I think it can be
considered a bug.


Jim Cochrane ( jcochrane ) - 2006-10-14 04:49

9

Closed

Fixed

Chris Cannam

notation

None

Public


Comments ( 5 )

Date: 2006-12-04 03:20
Sender: sf-robotSourceForge.net Site Admin


This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).


Date: 2006-11-18 12:41
Sender: cannamProject Admin


Fixed for Transpose command in SVN (reorganisation branch, rev 7648).
Will be merged to trunk shortly.

I couldn't reproduce the problem when pasting, and although I only
used a trivial test case, I did try all five paste types. Can you
give more information about that one?

Also I only dealt with the case where transpose is exactly 12 semitones.
I imagine there may be a case for non-octave transpositions also
having their resulting accidentals influenced by the original choice
of accidentals pre-transpose, but I think that'd be a big can of worms.



Date: 2006-11-15 03:04
Sender: dmmcintyrProject AdminAccepting Donations


MUST MUST MUST MUST MUST fix this ASAP so I can get my project done
without spending a month manually changing all the damn accidentals.

Moving to priority 10, except we don't have a priority 10.


Date: 2006-11-04 03:50
Sender: dmmcintyrProject AdminAccepting Donations

Logged In: YES
user_id=663564

To add, this also affects pasting, which I've just found to be seriously
annoying.

I'll assign to me, since I'm the accidental police.


Date: 2006-10-14 04:59
Sender: dmmcintyrProject AdminAccepting Donations

Logged In: YES
user_id=663564

Yes, quite. I should have logged this bug myself. I've
seen it. It's true.

I haven't investigated far enough to have any sense of how
reasonable it is to fix though. Could be easy, could be
monumental.


Attached File

No Files Currently Attached

Changes ( 9 )

Field Old Value Date By
status_id Pending 2006-12-04 03:20 sf-robot
close_date 2006-11-19 06:13 2006-12-04 03:20 sf-robot
status_id Open 2006-11-19 06:13 dmmcintyr
assigned_to dmmcintyr 2006-11-19 06:13 dmmcintyr
close_date - 2006-11-19 06:13 dmmcintyr
resolution_id Accepted 2006-11-18 12:41 cannam
assigned_to cannam 2006-11-04 03:50 dmmcintyr
priority 5 2006-10-14 04:59 dmmcintyr
resolution_id None 2006-10-14 04:59 dmmcintyr