Found it: you need to add DELETEs for the commands that use @ and * (at least, that’s what it is on my UK Mac keyboard; it might be that your keyboard has something different to @ on Shift-2).
"context" : "kWriteMode",
"shortcuts" : [
{
"NoteInput.PedalLineStop": [ "DELETE:*" ]
},
{
"NoteInput.SetArticulation?Value=kUnstress": [ "DELETE:@" ]
},
Apologies, I misunderstood, a lot of threads today. Thanks for clarification. Yes, I think having both avenues available as an option would be helpful for all kinds of tasks and people, just as the option menu choices are plentiful and represent the many clearly different tastes and demands of musicians, who can never seem to agree on anything! 
What I might be more interested in is if there was the ability to program the various options as buttons on the Stream Deck. Like creating an “intervals” menu. I have the Stream Deck XL so it has 4 rows of 8 buttons (it speeds up my workflow greatly by giving me quick access to things that I have to access in submenus repeatedly, which otherwise would end up being huge time sinks). The Stream Deck XL has enough buttons to have all intervals up to the octave, in #, b, or natural variants all as individual buttons on the Stream Deck. Although I’m not sure if the API used by the Notation Express template allows executing custom commands that are not already implemented as buttons (without actually having to map hotkeys), and whether it would be possible to map all of these chromatic variants in this way.
Again, you’re in the wrong file - stop editing the one in the application bundle - and your line breaks are inconsistent.
Yes, the line breaks in the application bundle file are different to the ones in the user library, but within each file they must be consistent.
So I’m on windows. Local disk C > Program Files > Steinberg > Dorico 5
Is that the Application bundle or user library in this context?
Also I’m editing Keycommands_en.json
Is that not the right one anymore?
On Windows, the application-level preferences are in %appdata%\Steinberg\Dorico 5 , which is the same as C:\Users\your-username\AppData\Roaming\Steinberg\Dorico 5
You need to be editing the keycommands_en.json file in this folder, not the one in Program Files.
(JSON is completely indifferent to all whitespace between tokens, including line breaks and indents. I once reformatted my key commands file to something tidier; Dorico had no problems reading it, but it changed it back to its own format the next time I added a command in the UI.)
ah, sorry, yes I assumed you did.
I feel going back to those Notation Express nightmares with some combinations not working, god knows why… I’m using meta and shift+meta for upwards/downwards intervals, and for some reason it doesn’t work with è, which is the 7 key (without shift in a French layout keyboard). Meta+shift+è increases the grid resolution, even if I delete that action… So everything is working perfectly as planned, except for 7th…
it does not. Notation Expression has every button programmed inside a black box and does whatever it does, no way to access the guts of anything. All you can do with NE is chain together any of their button presses that might make sense to chain together.
the Dorico Websocket API is smart though to query Dorico for information about what is currently selected and so in theory…using an external tool of some kind…you could use the web socket API in much the same way can be done in the Lua Macro programming…determine what is currently selected…make intelligent choices about what to do with it based on that and construct the web socket command to send to dorico based on that information. All attached to a single button…so to speak. so yes…external remote devices can be made more smarter…based on what is currently selected…but this is an area nobody has really gone so far… StreamDeck would probably not be the ideal choice for that kind of project because its macro programming is super simplistic. meanwhile its plugin Sdk is rather complicated. There are other solutions such as MetaGrid, OpenStageControl, even TouchPortal…which have better macro capabilities…and presuming someone integrates them with Dorico’s web socket API…it would theoretically be possible to do much more elaborate programming of what buttons actually do…they would be able to more closely do exactly what can currently be done with Dorico’s macro system.
The main problem with Dorico’s macro system is that there is no way that I know of, correct me if I’m wrong, to attach a key command to a specific recorded (or edited) macro by name.
Anyway I digress…
You can do this in the keycommands file as follows:
{
"Script.RunScript?ScriptPath=/full/path/to/myfile.lua" : [ "Shift+F3" ]
}
Interesting, never knew that - really good to know.
Thanks asherber, that is very helpful info
so question about the notes tool popover…or custom key commands as suggested in this thread…do any of these tricks work while in Pitch-before-duration note entry? it appears to me, the answer is no.
I find chord entry in PBD to be positively painful in every way. wish there was an easy way to get around some of this…the only thing that seems to kind of work is entering the letter names before duration after Q…which it seems to accumulate the notes so that when you hit the duration there will be a chord there, might not be the right inversion though. I really wish there was a way to build up chords based on intervals…while still looking at the shadow notes before hitting the duration key. this appears to be something Steinberg would have to add, I can’t think of any work around using Shift-I which doesn’t respond when the shadow notes are present in PBD.
PBD needs to be improved in several ways, the chord building is one area…for sure.anothe is that when the shadow note(s) are showing, a rest will also be showing at the same time (but not shadowed and its often quite difficult to see exactly where the shadow note is because its obscured by the existing rest symbol that is about to be replaced. Steinberg should really remove the rest while in PBD entry. once you move the caret or leave note entry then put th rest back if it makes sense…but during entry its just in the way and makes it harder to see what you’re doing. side tangent I guess sorry… but anyway am wondering what some of you may do to enter chords in PBD, other then switching modes for that task, or using midi.
I use the custom key command approach, but I’ve never actually tried it while in PBD. I can confirm it (as well as the normal popover) does not work here. Agree with suggested enhancements about building chords while in PBD, it would be nice to be able to build chords intervalically from a note while in that mode. I’m not sure how it would work exactly, I suppose you’d have to have a key command to soft commit a note before moving onto the next one, before commiting the final duration.
well for starters, it can’t depend on the note tools popover. Because that simply doesn’t work in PDB. The way DBP works is that the last entered note remains selected and some subset of note-editing commands can operate on it until you enter the next note; which includes the note tools and numerous others. But PBD doesn’t remain selected after entering a duration, the caret moves and the previous one does not remain selected for note-editing on it (maybe that is what Steinberg needs to add?).
Or if they had actual keystrokes for adding the intervals without going. to the popover…then those same keystrokes could be used for selected notes while editing or while doing DBP…or they could be used to affect shadow notes the same way.
I believe there is some inconsistency creeping into Dorico now as they begin to make PBD more capable…the two modes are becoming more and more separated, and they shouldn’t need to be so separated. I think dorico can function in a consistent way with regards to many of these kinds of things…regardless of whether you’re doing PBD or DBP…but in any case right now…you can’t do some things from PBD…such as NoteTools or any macros based on NoteTools popover…
its the same reason chord building is kind of jacked up in PBD…when you enter a duration, the caret moves forward and the last entered note does not remain selected to operate on it like you can with DBP. I would love it if they had a key so that while look in at shadow notes, you can use the arrow keys to move up and down the staff adding or removing notes from the chord at will until ready to hit a duration key to enter the chord. There are different ways it could be approached, but I feel that PBD mode in dorico is too much of an afterthought…with the sentiment being that DBP is the preferred mode and can do everything…and PBD is not given the same level of attention that it should. There are pros and cons to both modes…but not being able to enter chords efficiently is a major problem that could be resolved IMHO.
If you have this Preference set - and this Preference is apparently the Finale “norm” - then the previous note does remain selected and the Shift-I popover can be used to do something to that note.
excellent info thank you. that kind of makes PBD a little more consistently the same as DBP…I like it. Are there any downsides to using this mode?
Alright, it took a bit but I’m definitely getting a really fun workflow going which works for me. For all my bemoaning, I’m happy there was a solution. I really hope a non-json method to do this gets implemented in the future, but I’m incredibly grateful for your assistance.
And more so, looking around the forum, I appreciate that you take the time to help find the workaround and solutions for the forum, rather than make judgements about other people’s preferences for how they’d like to work…Or worse, just bragging about how much better the default is after 100s of hours of muscle memory.
You did a great job helping out 11/10
