I read in a post from Daniel S that Dorico’s scripting going forward was specifically not going to be lua. Do you have any insight into whether lua will remain supported, regardless of what Dorico finally settles on going forward?
No, Alex won’t have any insight into that, because, firstly, he’s not a Steinberg employee, and secondly, we’ve not made any determination about that. Probably we will keep the existing Lua engine in the software as long as it is practical to do so, but we won’t make promises about future plans, because predicting the future is impossible. What I can say is that right now we are not working on scripting more generally, so you should not expect any significant changes in this area in the next major version of Dorico, i.e. existing Lua scripts will carry on working just fine.
I hope that Lua will be replaced by Python as the scripting language. And that it won’t be too long before scripting climbs a little higher up the priority list …
I think, Bach had a similar problem.
After he played the organ in his church, people came and told him, how to play in the future. No wonder he went on an extended holiday.
It is an interesting insight into music history and shows also what happens, if you don’t treat artists adequately.
This doesn’t work for me – does it work for you? The scripts I have saved show up as items in the jump bar, but when I try to assign aliases to them there, it doesn’t take. I am able to assign aliases in the jump bar to regular Dorico commands.
Hi Asherber, I just set up a new script, and, yes, I can assign an alias in the jump bar.
Did you restart Dorico between recording the macro and assigning the alias? It might help. Sometimes the script doesn’t fully ‘take’ until that’s done.
Yes, I have restarted Dorico multiple times. Are you maybe on Mac? I’m on Win.
Here’s what I see when I try to assign an xx alias to my Make Pitch Constant script. You can see that it executes the first time (while assigning the alias), but then the alias doesn’t work (and doesn’t display next to the script name in the jump bar window).
Assigning the alias does create a registry key.
It seems a little odd to me that the slashes in the path to the script result in a nested key instead of a single value. I tried deleting that key and creating a single value with the appropriate name of Script.RunScript etc., but that didn’t work either.
If the Dorico team is reading this, there’s one other thing about jump bar aliases that I wanted to bring up: There doesn’t appear to be anything stopping me from assigning the same alias to multiple commands. Even in the Preferences dialog, while I can’t assign the same key command to two conflicting actions I can assign the same jump bar alias. Dorico even creates two registry keys:
Yes, I’m on Mac. Try leaving a space between the command and the =, and likewise with the alias.
No luck, same result.
Hi Asher
I made a repeat.lua script containing
local app=DoApp.DoApp()
app:doCommand([[MusicalManipulation.RepeatPitches?ParameterRepeatPitchesNumberOfSteps=1]])
and in the keycommands_en.json file
I can add - within the “shortcuts” : [ … ] space this:
{
"Script.RunScript?ScriptPath=/Users/YOU/AppData/Roaming/Steinberg/Dorico 5/Script Plug-ins/repeat.lua" : [ "Ctrl+Alt+Shift+A" ]
},
(N.B. forward slashes even though it’s a windows location)
and CTRL-ALT-SHIFT-A now repeats all the pitches.
hope this helps
Right, I can add this as a shortcut in the keycommands_en.json file. What I can’t do (on Windows) is assign a jump bar alias to the script.
Same for me on Mac. I’ve tried several ideas: space before = (or after), choosing a script that has no space in the filename, relaunching Dorico after attempting to assign.
Not that this is a big deal to me, but I am burningly curious why it should work for one user and not another.
That’s very strange. I just retested using the alias in case I had fooled myself, but no, it definitely works here.
ah ok sorry,
I can confirm the same (lack of) behaviour with the jump bar and the same registry stuff.
Not sure if this has been said but I recommend looking into the mobile app version – it syncs via bluetooth with your laptop so you can use it anywhere – it’s awesome!
[quote=“Vadian, post:8, topic:943198”]
But afte
But after placing it with one click, you need to do loads of editing. Dorico places things on their right place, so nothing to do after input. What I really love.
Not mentioning that apart from a few people who is professional in music editing, musicians who use music writing apps have just a faint idea about the 100% proper layout. At least I always guessed where is the right place, say, of a forte between the staves and I don’t think I was very bad, but a professional music engraver definitely hasn’t given me A+++ for my achievment. Dorico makes it for me without interfering. So I don’t miss Finale metatool that much although it really was a cool thing:)
Sorry man, but that’s simply untrue. In 30+ years of using Finale, I’ve rarely needed to edit anything after assigning elements via Metatools, especially articulations, dynamics etc. And I’m finding that Dorico’s “smart” positioning frequently isn’t so great and actually requires MORE editing than Finale, and it’s more fiddly to do in Dorico. Both applications have their pros and cons but let’s not use hyperbole to try and make a point.
I’m not bashing Dorico - nor trying to elevate Finale over it - but I see so many posts here and on FB about how much more editing is supposedly required in Finale and it’s simply not true.
Glad if it was so smooth and light for you with Finale. I liked Finale a lot, but my experience is what I’ve said. Maybe not true for you, but definitely true for me:)
I’m kind of in the middle between @Maddcow and @kaposi.g when it comes to the manual editing. I also used metatools a lot in Finale. I was actually a Simple Entry guy and I mainly used the mouse for note input (although even saying you use your mouse for anything may get you tarred and feathered here; I’m actually gravitating towards qwerty in Dorico), but because of those metatools I was quite fast in entering music. I used metatools to add expressions, dynamics and articulations on the fly. However, I did a lot of manual editing in Finale to resolve collisions and e.g. get dynamics properly aligned.
I love Dorico’s collision avoidance in general (a large bulk of the manual editing in Finale went into resolving collisions), especially on a page level. On the bar level however, I find that bars that have multiple items (e.g. tempo mark, rehearsal mark and a text item or playing technique) can still require a lot of manual adjustments in Dorico and at that point I agree with Maddcow that it’s a bit of a hurdle. I also do not find aligning dynamics or other bar/note attached items to be particularly less work in Dorico so far. Sometimes they align properly, a lot of times they do not - I’ve yet to find out the method that works best for me but so far I’m manually grouping a large portion of the dynamics in my project. The upside is that you can do this with a key command in Dorico whereas in Finale this required a plugin (although grouping has the side effect of screwing up or even deleting dynamics in other staves if they are linked, I found out the hard way that I had to turn auto linking off). What does require a lot less work in Dorico (for me) is horizontal placement of hairpins. I absolutely love how Dorico handles that and how hairpins adapt when you add a dynamic. Inputting slurs is also a lot quicker in Dorico (getting them placed the way I like, especially on grace notes, not so much but I’m currently in the process of figuring out my ideal global settings for that).
On topic: I’d also love to be able to assign key commands to playing techniques. 