No matter what I do to the length of the E I can’t get rid of the overlap. Tried in the key editor, deleted overlaps (mon and poly),applied legato etc..
In the key editor it looks like this - it’s totally in the grid with no overlaps:
Any ideas ?
In the key editor it looks like this - it’s totally in the grid with no overlaps:
Are you using the ‘Sync Layout’ in the score editor? I found that using that can give some undesired results. I always create a new layout.
That’s quite unexpected. I can’t reproduce this in a new project, so it looks like there’s something else influencing this. Can you attach a cut down version of the project, or DM to me?
I’m pretty sure this is caused by copying parts around as I’ve been working around this issue daily.
For example, if you copy a midi part from another track using the range tool you think you are copying just those notes, but there are lots of hidden notes also copied. This makes no difference to normal midi as they don’t get played, but the score renders them visually.
Example - I copy the range section from Track1 to Track2:
I see this:
To get around this I’ve been splitting the section I want before I copy:
Then I get:
Interesting bug you found, but that is not the case here. Everything was played in.
It may be different then, but this can also happen if you play in a part and then shorten it.
Done..
I found the problem – the half note had been edited in the score editor to have a notated duration of 1/2 + 1/16. Maybe you’d accidentally pressed the Nudge End right key command (alt right)?
The fix is:
- set the grid to 1/16,
- in the score editor, press Alt+Right to nudge the end right
- press Alt-Shift-Left to nudge the end left
All notes have a MIDI length and an optional notation length, which allows the notation to be presented differently to the MIDI. There isn’t currently any easy way of seeing where you have properties overriden in the score editor.
I see - it’s confusing..
Is there a way to reset the score (or some notes..) so it reflects exactly what’s in the key editor ?
No, not currently. It’s on my list
3 Likes
Would it be possible to have notation vs MIDI discrepancies highlighted or color coded? I think it would serve as a useful indicator.
Ok. Here’s another problem:
Look what happens, when I Alt+Right the last low A:
Notes in the previous bar gets deleted. and the key editor doesn’t change.
(Same file I sent to you)
This is something we’ll think about how best to approach. We’re generally a bit averse to changing colours to highlight state because it can quickly become overloaded (also: how could we communicate that one note has a notated duration set, but another has notated duration and voice override?)
This is a known issue that can happen if you have notes that overlap a barline. The note temporarily disappears from the notation but is still present. When you edit a note , the whole bar is reprocessed, because changing a note’s position or duration could change the voicing decisions or tuplet structure. If a note overlaps a barline (which the one at the start of b51 does) then the previous bar is renotated as well. However, the note at the start of b50 (the one that disappears) actually starts in the previous bar and isn’t included.
If you quantize the first note in b51 then this stops the note from disappearing (note: I’m not suggesting you do this, this is just to illustrate the bug).
Anyway, it’s one that’s on my (long) list.
So basically - as things stand now - it’s not a good idea to move anything in the score editor, but only do it in the keyeditor ?
Hi Paul,
Wouldn’t it generally be a good solution to have a manual function to trigger reprocessing at a specific point?
For me, it’s also essential for redistributing the staves across systems/lines/pages.
Or does that already exist somewhere?
In general it should be ok, it’s just that your project exercises a number of edge cases as the note timings are consistently a small amount before the barline, which triggers this issue. I have fixed this now, so it will be better in the next update.
1 Like
I’m not sure what you mean by ‘trigger reprocessing’. The Scoring Engine’s layout engine is dynamic and automatic. We don’t currently have the full range of control you can get in Dorico, though we will hope to add more capabilities over time, eg note spacing changes, but many of the Layout Options from Dorico are now available, so I suggest experimenting with those, and insert manual system breaks if you need them.
1 Like
Here’s another strange thing:
If I have a score window open and delete the part it shows, it’s still present in the score and plays back.
I couldn’t find a way to delete it in the score except undoing the deletion.
It’s a known issue that adding, deleting or glueing parts doesn’t update the score editor. However, I can’t reproduce the problem that it continues playing back after deleting. It will play back for about a second, but that is expected due to how the events are queued.