TIP: Scripter Keyswitches

[Dewdman42]

Try this one:

 

https://gitlab.com/dewdman42/art2script/-/blob/main/art2script.sh

 

Here's another little tip too. You can use this command line tool together with the pbcopy command to automatically copy it to the clipboard too.

 

getSwitches.sh artset.plist | pbcopy

Edited October 18, 2021 by Dewdman42

[D4rkKn1ght]

Legend. Seems to work perfectly!

[D4rkKn1ght]

Just a note for anyone following in our footsteps here:

 

The keyswitches that Terminal will output when you feed it the .plist will be bracketed by these { }

 

If you paste that directly into the Scripter script, it won't work. So first I pasted into TextEdit (any word processor will do obviously) and did a find/replace to change all of the { } to [ ]

 

Then it worked perfectly.

[Dewdman42]

stupid bug on my part, the script is fixed now.

[ravez]

Hi, i am using the automation points (in the lane) via scripter to switch articulations, not using articulation sets at all.

How can i change the script to receive midi in order to trigger the articulations via a midi controller?

What i'd like is a way to write the automation points in the automation lane using a midi controller instead of selecting them with the mouse. Is it possible? thanks

[Dewdman42]

I'm not 100% sure. I am mostly not using LogicPro anymore either...so limited time available to pursue this.

 

You have a generic question to ask which is how to program automation lane curves using a midi controller. You should ask that question on the main LogicPro forum...Its probably something related to Control Surface capabilities of LogicPro, but I'm not entirely sure.

 

Scripter is able to READ the current automation lane value, and do something with it. its also able to change the CURRENT value of that automation lane...but I do not think scripter can be used to actually SET points in the automation lane.

 

And I am pretty sure that in order to do that with a midi controller you will need to setup a Control Surface integration for that...but ask on the other LogicPro main sub forum about that.

[ravez]

sounds good thx!

[Dewdman42]

here's an updated version of the art2script bash script that will generate the COMPLETE working Scripter script, including the KS array of keyswitches, along with the working script. If I get time I will update it to be able to optionally generate the automation lane script with a command line argument. Hope some find it useful.

 

I have also moved these scripts to the following location on gitlab:

 

https://gitlab.com/dewdman42/art2script

Edited October 18, 2021 by Dewdman42

[Atlas007]

here's an updated version of the art2script bash script that will generate the COMPLETE working Scripter script, including the KS array of keyswitches, along with the working script. If I get time I will update it to be able to optionally generate the automation lane script with a command line argument. Hope some find it useful.

 

I have also moved these scripts to the following location on gitlab:

 

https://gitlab.com/dewdman42/dawtools/-/tree/master/LogicPro/Scripter/Art2Script

The link yields a 404...

[Dewdman42]

not for me it doesn't look deeper into it

[Atlas007]

It seems that your script is available only for you then...

[Dewdman42]

no I don't think so, but I will look to make sure. are you able to access gitlab generally?

[Dewdman42]

I was wrong, I put it in a private repo you're right. I'm not ready to make that repo public, so I will create a new one, stay tuned...

[Atlas007]

Ok! Thanx!

[Dewdman42]

Here now:

 

https://gitlab.com/dewdman42/art2script

[Atlas007]

Great!

Thanx a lot!

[Dewdman42]

I updated the scripts a bit today, now the bash script can be used to generate either type of script.....

 

1. based on articulationID to send keyswitches or cc switches
   
2. based on an automation lane to send keyswitches or cc switches
   
3. or optionally just output the ART array and use whatever script you want

 

In the case of articulationID, after you generate the script, make sure to clear the OUTPUT section of the articulation set you used to generate it. The articulation set is still useful in order to see articulation names in the LogicPro GUI, but not essential. ArticulationID's stored in midi events will trigger the keyswitches as configured.

 

When using the automation lane script, you can get rid of the articulation set entirely from your project track once you have generated the automation lane script.

 

Usage

 

art2script.sh [options] <artset.plist>

Options: 
 --id    (default)   produces articulationID based script
 --lane              produces automation lane script
 --array             produces only the ART array

[Dewdman42]

Note with this, it is also possible to have multiple articulation sets in parallel!!! This is kind of like Cubase Groups feature.

 

Basically you can have only one actual articulation set active on a track at once in LogicPro. So articulationID in midi events will trigger from that articulationset....regardless of whether you are using the output section of the artset, or using this Scripter script instead.

 

However...

 

You can have at the same time also a completely seperate and independent set of keyswitches managed by an automation lane, at the same time that that the articulationID is being handled...in parallel. For example, you could use articulationID to specify the basic articulations and an automation lane to specify mute on or off. Just one example.

 

You can also have more than one automation lane script active in one track at a time.

[Dewdman42]

Some user docs added: https://gitlab.com/dewdman42/art2script/-/wikis/home