I’m a bit disappointed that there are not too many enhancements in the score editor in the 0.20 update. I know by now that the score editor is to Steinberg not the most important functionality, but what is there should really work correctly I would say….
swing notes look to be correct now. 16th swing notes are correct up to 50% swing, I can live with that.
nice that there are different styles of writing chords, but see below.
other issues are still present.
only people in Boston get to play the right chord apparently (referring to the chord style in Engraving Options), but in all the other styles, and in the style I use it’s still the same story: The Fm7 is suppressed in bar 11. That’s no way to write a chord!
there is still no visual feedback on notes that have been muted. nothing in the info-bar either, so there’s nothing to go on but a very good memory.
select all in the score editor will still select e.g. tempo track events that will get edited while you think you’re just editing notes (if the kind of edit is something the tempo track is sensitive for)
there is still no acoustic feedback when nudging notes up and down.
selection is often off (not in sync with the info line) or very difficult to do.
For this I would use Logical Editor preset commands to select only notes. I woudl not expect any change on this – at least I would hope time would be spent on other functions, since there’s a solid workaround for that.
interesting suggestion. it’s just less direct then just doing cmd-A!
do you know if there would be any way to access logical editor commands through some kind of pull down menu? so you can there straight away. keyboard shortcuts are not possible I think.
Why do you say that? They are all listed in the key command dialog box in the LE and PLE presets sections
There should be but I can’t get it to work as its display would have one assume.
MIDI>Logical Editor>Apply Preset launches a dialog box, usually it works the first time from the keyboard, other times the Apply button is illuminated but the enter key doesn’t activate, one must click the button.
Other times it doesn’t seem to work at all until the dialog is closed and reopened.
I’ll create a separate topic for this problem, or maybe you can, and I’ll do some research on getting it fixed.
well… I didn’t realize! that’s a great help. best option seems to use ‘select all notes in range’ (have to first set the range of course).
since I already had made a preset (or was it shipped with cubase, can’t remember) to select all muted notes, I assigned a key command to that too. helpful.
thanks for pointing this out to me!
I remember I think from previous versions there was a pull down menu for logical editor items. but I would be looking for something that would be part of the tool-section in the score editor (or any editor) window.
I don’t have time to look at this currently, but when reporting score editor issues like this, please attach a minimal project that reproduces the problem, especially for quantization and chord issues like this. There are often other factors that are not obvious from a screenshot. Other users may also be able to spot the problem if they have a project to open.
Re: tuplets, I have written automated tests that run through thousands of different tuplet situations, multiple times every day. Occasionally there is a new case that wasn’t covered by my tests, so I aim to fix it and add a test so it never happens again (which I did for a previous tuplet issue you raised). If there is a minimal score to show the problem then there is a higher chance of it being fixed. In many cases problems are caused by extra Display Quantize events that are no longer needed, so try removing those first.
Thank you for your reply. I may be a bit of a critic at times, but though I’m a 30 years cubase user, going from C13 to C15 has been a steep learning curve to get used to the new score editor. Getting to grips with it, but I have a lot of work at hand and had to invest a lot of time to learn C15. I appreciate the work you put into making it good, and it does look a lot neater then the old score editor.
As for the 16th triplets, I found out by now that setting the display quantise in the Instrument Settings to 32nd notes makes everything look good. Don’t understand, I tried it before and it didn’t work. Nobody in other postings I did on the subject made that suggestion, though a lot of people looked at it.
The other triplet problem remains, which apperently has to do with the fact that the triplet doesn’t fall on the first beat (or in a similar 4/4 situation on the third beat):
Thanks for isolating these cases – it makes it a lot easier to deal with. The tuplet case is one where quarter note triplets were only identified if they fall on the 1st or 3rd beats of the bar. I’ve now got a fix for this.
The chord case is actually expected behaviour. In Dorico this is the default behaviour if you have a chord which is repeated but with a different bass note. If you added a different chord between the Fm and Fm/Bb then the Fm/Bb will show the full name. I’m not an expert on chords, but it seems that this is a common convention. Dorico has the option to turn this off (among it’s hundreds of other chord options).
I have made a change so that if you are using the ‘Follow Chord Track Appearance’ preset in Engraving Options > Chord Symbols then it will show as ‘Fmin/Bb’, consistent with the appearance in the chord track.
