blaggins
Senior Member
I've started on a little utility that parses Cubase expression maps to extract information about the articulation, keyswitch, and UACC info. It's in python but you might find it helpful:
easiest way to run it is to just call it from the command line like:
(note the "--csv" flag at the end). This will parse every expression map contained in the directory and dump a CSV with all the articulation, keyswitch, and UACC details for each expression map. I've been using it to design the UI for my OSC articulation controller, like you I have found it very useful to get a list of all the articulations possible in a given library without having to manually type them all out.
The script does other stuff too if you don't add the "--csv" flag but that is fairly specific to my OSC configuration and requires a few more variables to be set up. I posted a quick and dirty blurb about how that works here https://vi-control.net/community/th...nd-cubase-expression-maps.114281/post-4912751 and I may eventually get around to cleaning the code up a bit and properly "releasing" the OSC controller plus associated utility scripts at some point.
Utility-Scripts-for-Composers/ExpressionMaps/expression-map-parser.py at main · tpoots/Utility-Scripts-for-Composers
Collection of useful scripts for composers. Contribute to tpoots/Utility-Scripts-for-Composers development by creating an account on GitHub.
github.com
easiest way to run it is to just call it from the command line like:
>python expression-map-parser.py {path-to-directory-containing-expression-maps} --csv
(note the "--csv" flag at the end). This will parse every expression map contained in the directory and dump a CSV with all the articulation, keyswitch, and UACC details for each expression map. I've been using it to design the UI for my OSC articulation controller, like you I have found it very useful to get a list of all the articulations possible in a given library without having to manually type them all out.
The script does other stuff too if you don't add the "--csv" flag but that is fairly specific to my OSC configuration and requires a few more variables to be set up. I posted a quick and dirty blurb about how that works here https://vi-control.net/community/th...nd-cubase-expression-maps.114281/post-4912751 and I may eventually get around to cleaning the code up a bit and properly "releasing" the OSC controller plus associated utility scripts at some point.