What's new

Any problems with Logic's articulation system?

I still haven't found a way to use multiple KS with OTs Capsule. Sending more than one KS doesn't work and if I edit the event and double it with another articulation Capsule goes crazy.
Maybe I am missing something but, why do you need multiple key switches for OT? Their instruments work fine with regular single key switches. Are using them for combining articulations?
 
Maybe I am missing something but, why do you need multiple key switches for OT? Their instruments work fine with regular single key switches. Are using them for combining articulations?
Within their multi patches you can select up to 4 articulations. This way you can xfade from f.e. no vibrato to strong vibrato or sustain to tremolo for strings or create some weird movements in their Time Macro library. Really good and easy to use, but for this you need to send more than one KS.
I´m using ARTzID for it, but as much as I appreciate this system, it´s not perfect for this either, because you can´t just do it on the fly.
 
I´m using ARTzID for it, but as much as I appreciate this system, it´s not perfect for this either, because you can´t just do it on the fly.
The factory Logic Art Sets do not support four KS at the moment - no offense.
Do you mean that you cannot xfade sustain to tremolo (for example) in the middle or anywhere of a sustaining chord on the fly using the ARTzID? Do you mean that the problem is that the Note ID switching method is locked only to the Note ON art triggering? I am asking because I need more info about your “on the fly” need.
 
Last edited:
I still haven't found a way to use multiple KS with OTs Capsule. Sending more than one KS doesn't work and if I edit the event and double it with another articulation Capsule goes crazy.

Hey there HG, do you not have the Capsule Script? It can be programmed to send up to 4 keyswitches per ID. If you don't have it for some reason, let me know and I'll send it to you. :)
 
Hey there HG, do you not have the Capsule Script? It can be programmed to send up to 4 keyswitches per ID. If you don't have it for some reason, let me know and I'll send it to you. :)
1st I want to apologize , I didn't´t want to turn the thread into a 3rd party discussion again. I just responded to Marcs "..not sure about the OT libraries."

Peter, I always praise ARTzID and of course I have the Capsule script and I use it for multiple KS. My (little !) problem with it is, that you have to set up the script upfront for certain combinations and I like to keep things simple during composing and arranging. So it would be perfect to have an articulation system that works like normal KS but with the benefits of the implanted articulations: If I only need f.e. Sustain on C0, I press C0. If I need a combination of 2 or more , I press C0,E0 and what ever I need in this moment. But maybe this just is technically impossible, otherwise you´ld have found a way I guess.
 
Hey HG, I wasn't looking to turn this into a 3rd party discussion either. But the good news is that your latest post clarified (for me, anyway) what you're looking to accomplish. Interesting!

Gonna take this opportunity to say "hey man!" to babylonwaves Marc. And with that, "we now return you to your regularly scheduled non-3rd-party thread".
 
So it would be perfect to have an articulation system that works like normal KS but with the benefits of the implanted articulations: If I only need f.e. Sustain on C0, I press C0. If I need a combination of 2 or more , I press C0,E0 and what ever I need in this moment. But maybe this just is technically impossible, otherwise you´ld have found a way I guess.

For that you should avoid using articulation id at all and either just record your keyswitches manually on a track or use automation in some fashion, combined with scripter. The articulation id concept is one articulation per note. Which means in order to do what you want you have to setup a separate articulation id for every combination of keyswitches you foresee using.
 
For that you should avoid using articulation id at all and either just record your keyswitches manually on a track or use automation in some fashion, combined with scripter. The articulation id concept is one articulation per note. Which means in order to do what you want you have to setup a separate articulation id for every combination of keyswitches you foresee using.
The benefit of articulation IDs is much to big to avoid them and being able to send more than one articulation ID at once into Logic, would save this problem. It works under certain conditions, when you edit it afterwards though....but as I said, I don't know if it is possible technically.
 
"The articulation id concept is one articulation per note."

Not really. The concept is to embed an additional value into a note. What you want that value to represent, or how it's leveraged, is up to the user, script programmer, etc.
 
sounds like you're picking apart my words Peter, not sure why...

You get one articulation id available per note. As I already explained, that means if you want the ability, for example, to use any combination of two different key switches..., which is three different combinations, then you need to use 3 articulation id's and setup them up each with the combination of key switches. There are advantages to the articulation id concept, but this is not one of them in HG's case.
 
Eh, no picking-apart intended or involved. I'm not sure why you'd see my response as being anything other than informative or conversational. I understand what HG is trying to accomplish. Just because a note can have only one ID doesn't mean it can't be leveraged to perform some other feat of MIDI magic. :cool:
 
sure thing, but nonetheless, you can only attach one articulation id per note...which means, in his case, as he described, it would not work as he desires. and in that case, if he wants to work the way he described, he should either send the key switches manually or use automation in some fashion, or as I already described, set up a separate articulation id for each combination of key switches he needs to use.
 
Please guys, I don't want be the reason for any controversy ;)

Dewdman42, I understand the concept of one id per note and I'm a complete fool concerning scripting. But my naive question is, isn't there a possibility to just create an additional note event with a second ks, when I press 2 ks events on my controller , so I have f.e. C1 with ID Sustain and C1 with ID Tremolo ? It might not work with Logic IDs, but it seems to work with ARTzID when I copy and paste manuelly(sorry 3rd party again). That's all I need I guess.
 
When you use the articulation set it listens for your input keyswitches and then selects one articulation at a time. So if you hit the ks for sustain then it’s in a ready state to encode the next note with an articulation id for sustain. If you hit next the ks for tremolo then the articulation id for tremolo will be active and the next note will be encoded with that articulation id, but even though you might be coincidentally hearing a tremolo sustain, the articulation id will really only be referring to tremolo. You need a third input keyswitch to signify sustain-tremolo combo, and that will encode the third articulation id into the next note.

Then during playback Id 1 sends out one ks, id2 sends out the second ks and Id 3 sends two keyswitches to ensure sustained tremolo.

Sometimes you might make the music and it sort of works out that you haven’t fully encoded your articulation combos because your instrument goes first to sustain state and then to tremolo without turning off sustain in the instrument so it still kind of works but if you were to move that note to another place in the score or make some other edits then it would not necessarily retain that sustain-tremolo articulation combo unless you have an actual artid that represents that combo and programmed to send both ks no matter what
 
Is anyone else having issues selecting articulations for CC events in the event list?

Appears to be an issue with the latest update. The articulation changes are taking effect, but are still displayed as a “-“ in the event list..
 
It seems that the "Capsule" comments go to a dead end.

Dewdman42, please try to optimize your posts and their contents - it will be more easy to follow your ideas. Thanks.

Heinigoldstein, thanks for your "on the fly" details.

I contacted Tobias from OT a long time ago after they released Capsule. Our conversation was about Articulation Maps and their "On the Fly" compatibility.
The "Articulation Maps" concept is locked: i.e you can program up to 4 KS embedded into a Map (say Sus+Stacc+Trem+Pizz) but it is a pre-designed custom decision programing which is locked into the Maps (Art Set).

The "Capsule" goal is a simultaneous KS (chord) real time triggering which enables the correspondent Groups in the KSP script.

This is not possible in the current Logic factory Art Sets technology. I may say that it requires a special programing...
 
Last edited:
Is anyone else having issues selecting articulations for CC events in the event list?

Appears to be an issue with the latest update. The articulation changes are taking effect, but are still displayed as a “-“ in the event list..

Yes I noted about that earlier in the thread. It might be a bug or It might be intentional as I saw comments in one of their release notes about not sending key switches for cc events. It really sure, it’s kind of half baked and unclear now though
 
Top Bottom