7 and 9 tuplet groups result in a corrupted score when reopened

• May 3, 2013 - 14:42
Type
Functional
Severity
S4 - Minor
Status
closed
Project

Audio for the attached fragment is corrupt in 2.0 (Win7; release 2e40e6d)

Attachment Size
CS.mscz 2.96 KB

Comments

I just tried it with 133dde1 (win7) fluid.sf3 and it is still wrong. The audio produced is as if the 9ths weren't tied. The 5ths play correctly. This example works correctly in 1.3.

if you remove the incorrect ties and put them back, the notes will play correctly, but if you then save and reload, they are incorrect again.

Status (old) active closed

The file is broken in the first place. There is no time signature and most importantly, the second measure on the left hand doesn't add up to 4 beats. I guess a tuplet has been forgotten on the first group of notes.
I close this issue. Reopen needed.

Status (old) closed active

Attached is the simplest example I can create that shows the problem. The figure with quintuplets sounds almost identical to the figure with septuplets in 1.3. In 2.0 the septuplets produce three separate tones, as if the septuplets are not tied.

Attachment Size
Test_of_tied_notes.mscz 1.97 KB
Title Corrupt audio in 2.0 Some tuplet groups created in 1.3 result in a corrupted score when opened in 2.0

The problem is not Audio related at all - it is a corruption of the score.....

The actual time signature of the third bar of Ragtime Nightingale is showing as 479/4 in MuseScore 2.0 commit bc04561

Clicking on bar 4 crashes MuseScore 2.0

Opening the score in 1.3 shows none of this behaviour

It seems obvious then that the problem is related to the opening of scores made in1.3 in 2.0, with specific reference to some tuplet figures corrupting the score.

Title changed accordingly.

EDIT: Just checked the other 2 files and it is the same problem. the measures not playing back properly in CS are showing actual time signatures of 959/4 and 961/4 in 2.0 and the single tuplet measure in the test piece is showing as 1921/4. This is not the case in 1.3

PS I'm on Windows 8 Pro

The problem is not just with an import from 1.3. If you create the test shown above (#8) in 2.0, save it and reload it into 2.0, the same problem occurs.

Title Some tuplet groups created in 1.3 result in a corrupted score when opened in 2.0 Some tuplet groups when created result in a corrupted score when reopened

Title changed to reflect current status.

Can someone try to reproduce on Mac and Linux?

Should status be changed to critical? It is resulting in loss of data.

I'm sorry that this is not on point, but I need some help with ties.When I insert a tie from note to note in my already-written piece, two things happen:

1. The lyrics under the notes disappear.
2. The second note changes to duplicate the note it's tied to.

Can someone help me out? Thanks very much.

@CRE: you're at the wrong place here, this issue is totally unrelated and you should better go to the support forum.
Other than that: you probably want a slur rather than a tie

Title Some tuplet groups when created result in a corrupted score when reopened 7 and 9 tuplet groups result in a corrupted score when reopened