Half note too short
Attached in an example copied from a score in progress. The second half note in the first and third measures sounds (at least on my system) much too short, as if it were a quarter or eighth note, though all the other half notes sound ok. I can't seem to do anything to make it sound half note length. Can anyone see what's happening here? Does it have something to do with the rolled chords?
| Attachment | Size |
|---|---|
| too short.mscz | 1.83 KB |
Comments
See http://musescore.org/en/node/8017 - yes, seems to be a bug in arpeggios, already fixed in 2.0.
In reply to See by Marc Sabatella
OK thanks but is 2.0 available? I only see 1.2 offered on this site.
In reply to OK thanks I'm a version by jcorelis
2.0 is still under development. You can install nightly prerelease builds to play with if you like - scroll down to the bottom of the Download page for info. Not recommended (that's an understatement) for real work, but fun to play with, and worth checking out because reporting a bug or feature request.
In reply to 2.0 is still under by Marc Sabatella
Thanks. I take it there is no work-around. I didn't see one suggested on the linked page. I tried dividing the measure into 2 2/4 measures, so the rolled half note would be in its own measure, but it was still short.
In reply to Thanks. I take it there is by jcorelis
Try playing with the offtime offset in Note Properties. I don't know what I'm doing with those number, really, but I found that setting the offset type to offset and the offtime to -15% worked on an example I tried.
In reply to Try playing with the offtime by Marc Sabatella
Thanks for the suggestion. Strangely, as the attached excerpt shows, it seems to work in the first measure -- the half note after the rolled half note chord sounds ok -- but not in the second, where the half note is still short. So far as I can see, the rolled chords have the same note properties and the single half notes have the same properties.
In reply to Thanks for the suggestion. by jcorelis
More on this: experiment shows that the problem seems to be with the repeated F half notes, that is, after the half note rolled chord C-E-A the half note F sounds fine, but if you change the half note rolled chord to C-F-A, the following half note F is way too short.
I tried substituting two tied quarter notes for the half note, and also tried different note property settings of both the chord and the note, but the problem remains: if the half note following the rolled chord is the same note as a note in the rolled chord, the half note is too short.
Does anyone have any further suggestions for a work-around, even one that makes the score look funny?
What if I downloaded Musescore 2.0, created that one problem measure in it, and then pasted it into the Musescore 1.2 file. Would that work? Can I download 2.0 without overlaying 1.2?
In reply to What if I downloaded by jcorelis
Second question first: yes, 2.0 and 1.2 can coexist, no special effort required. They install into completely separate trees (for the nightly builds, at least; who knows about the final product).
However, as far as copy paste goes, it doesn't appear to work well between applications. You can copy and paste between documents open in a single version, but copying from 2.0 to 1.2 seems flaky. Sometimes it works, sometimes it produces corruption.
In reply to Second question first: yes, by Marc Sabatella
Well I tried installing Musescore 2.0 to experiment whether it could solve this problem, but when I opened nightly.exe, I got the message "The program can't start because QtCorel.dll is missing, try reinstalling,." But that dll is there plain as anything. I'm not sure what reinstalling means here, since there doesn't seem to be any install exec, just the nightly exe, and when I open that again, I get the same message. I have W7 and plenty of memory.
In reply to Well I tried installing by jcorelis
QtCorel or QtCore4? I see the latter but not the former.
Reinstalling in the context of a nightly build means deleting the folder and re-extracting the ZIP. Or for a more complete reinstall, also deleting the appropriate AppData folder(s).
Anyhow, it could be that a change was made recently in the DLL's and the last build is in an inconsistent state. Try one from a few days back and see if it works any better.
Another update: I still can't get 2.0 to run, but I found a sort of work-around in 1.2. If you save the Musescore file as XML and then open the XML file in another program that plays XML directly, the half note in question sounds proper.