Tweet
Dorico related
At the moment, Metagrid uses the key command .json file for user expandability. If a user can make a shortcut to a feature then it’s really easy to implement. However, If the user is unable to do this and needs to rely upon macros then they can still be used within Metagrid but there’s catch! To access the macro (.lua) files, I have to copy all of them into the same directory as the Dorico file I’m currently working on. This means I have literally dozens of copies of these tiny macro’s all over the place and I have to remember to copy all of them into the directory before I start any seriously intense work. There is one feature that would stop all of that and that is to have within Metaserver under the ‘files’ tab a second Dorico path.
At the moment there is only one which points to: -
C:\Users\Dave\AppData\Roaming\Steinberg\Dorico 3\keycommands_en.json
If this were to be expanded to two options, like this: -
Dorico 1 (for key commands file)
C:\Users\USER\AppData\Roaming\Steinberg\Dorico 3\keycommands_en.json
Dorico 2 (for Macros)
C:\Users\USER\AppData\Roaming\Steinberg\Dorico 3.5\Script Plug-ins\
This would make any buttons and sets I create even more interchangeable and will make my (and other Dorico users) workflow so much easier. Could you please consider this as an option for including in a future upgrade?
At the moment, Metagrid uses the key command .json file for user expandability. If a user can make a shortcut to a feature then it’s really easy to implement. However, If the user is unable to do this and needs to rely upon macros then they can still be used within Metagrid but there’s catch! To access the macro (.lua) files, I have to copy all of them into the same directory as the Dorico file I’m currently working on. This means I have literally dozens of copies of these tiny macro’s all over the place and I have to remember to copy all of them into the directory before I start any seriously intense work. There is one feature that would stop all of that and that is to have within Metaserver under the ‘files’ tab a second Dorico path.
At the moment there is only one which points to: -
C:\Users\Dave\AppData\Roaming\Steinberg\Dorico 3\keycommands_en.json
If this were to be expanded to two options, like this: -
Dorico 1 (for key commands file)
C:\Users\USER\AppData\Roaming\Steinberg\Dorico 3\keycommands_en.json
Dorico 2 (for Macros)
C:\Users\USER\AppData\Roaming\Steinberg\Dorico 3.5\Script Plug-ins\
This would make any buttons and sets I create even more interchangeable and will make my (and other Dorico users) workflow so much easier. Could you please consider this as an option for including in a future upgrade?