winkpain

"When triggered" means when the created/mapped articulation is triggered, yes? And then "any existing MIDI events" means any events that meet the Transform's "In" criteria, yes? And the second point is simply that any articulation generated events from the upper right Articulation Map Editor section do not also get transformed by any of the functions in the lower Transform section. Have I got all this right?

@Promidi, in the situation that you mention in your post above and show in the associated image, does this mean that.....this would.... create the possibility of polyphonic aftertouch from Channel aftertouch?? Is that.... possible?

Ah! This is good. I hate making things work and not knowing why! 😉 So, is it correct to think of the Generated MIDI Events followed by a Transform in the same way as the logical argument "If A, then B and C"? With A being the created/mapped Articulation, B being the Generated Event, and C being the Transformation ?

Hmmmm.... Well, then I am confused as to the effects of this setup in my Articulation Map (1st image) in an attempt to meet the conditions of the articulation map in Kontakt (2nd image). To test this I run the shown project looping through the 1/8 note pattern passing through all the articulation changes, Legato - Marcato. I can hear the changes to the articulation (samples) that plays, and it is as desired -i.e. the legato articulations (there are two kinds of legato), which are set to play only when the two conditions are met (pedal state down and appropriate velocity range) play as desired, and the short articulations, which are likewise set to play only when the two conditions are met (pedal state up and appropriate velocity range) also play as desired. I can also watch in the Kontakt mapping editor and see the velocities mapped to the articulations displaying their appropriately changing values on the map, and I can clearly hear the effect of pedal down and pedal up. I have added no pedal CC MIDI data anywhere else, and all the velocities attached to the notes themselves are at 64. SO, @msmcleod, if the setup I have shown in my CW Articulation Map is not sending both the pedal (CC 64) state and velocity transform data, where else is Kontakt getting that data from?? I ask this in all humility. Curious-er and curious-er!

Correction: For the (Cinesamples) record, Velocity still effects volume of notes played in Legato (standard) mode in the above setup.

I use mostly Cinesamples in Kontakt for orchestral instruments. They have many ways to map articulations within an instrument, but for my example I am using their strings "Velocity map". It is set up as shown in the attached (2nd) image. Velocity ranges simply call on the various articulation samples (in their "Articulations" patches), and when using these, velocities no longer have any effect on "volume" of the notes. I have set up my Cakewalk Articulation map as shown in the other attached (1st) image. I think this is working, but I don't quite understand what the In, Out, and Offset settings in the Transform section mean exactly. BUT it is working!

...So then, what if an articulation is conditional on two conditions? Following from my above example: If for the legato articulation to be called, both the pedal (CC 64) must be "down" (127) and the note(s) velocity must be with a range of, say, 0-39. Is there a way to map one of these new articulations thusly? Is this where the Transform section comes in? And what/where is this done if so, in the In sub-section or Out sub-section?

Ah hah! Yes. Now that's dialing in the understanding. Thank you!

Trying to understand Articulation Maps and looking forward to an in depth Help file. In the meantime I've been reading over the PDF addendum. Please forgive me if this is obvious or already explained... BUT, I don't quite understand how to think of the articulation...clips? cells? (What are they called?) What does the length of them signify. It was my impression that they would only apply for the length of the shape. In the simplest way of stating my query: I have a simple violin legato articulation that is activated by pressing the sustain pedal (CC 64). When the pedal is then released the legato articulation is no longer applied and the previous articulation that was playing before depressing the pedal continues. The way I wanted my articulation mapped "clip" to work after mapping it to CC 64 is to play the legato articulation for as long as the articulation "clip" is in the time line, then revert to the previous articulation in the same way that the pedal works. This is not what happens. I specifically thought that is how it would behave when choosing "Duration" under "Play at" in the Art. Map Editor. But no matter what I choose in that section, nor how long or short the articulation "clip" is, the legato articulation plays from then on, or until meeting a different articulation "clip". Surely I am not understanding something. Is there a way to map, for example, pedal-down (CC 64, Val 127) to the start of the art. clip and pedal-up (CC64, Val 0) to the end of the art. clip? How is this done?

This is true! I thought I had tried unchecking fast bounce before. But yes, this works for bouncing and exporting. Well, it's a work-around when using ProCh automation but a little time consuming on large projects, and still doesn't work on freezing tracks (which was the main desired function that got me to notice this issue) Any idea why a myriad of automation on a plethora of plug-ins (I know, not all) can work with Fast Bounce, but the most basic use of them on ProCh modules will not? Is there something inherent in ProChannel that prohibits Fast Bounce??

Yes, I have. Read above. Freezing, bouncing, exporting. I've tried it all.

@Wookiee and @Jonathan Sasor, Exactly. It doesn't matter whether jumps (dotted envelope) or linear/curves (solid) are used. It plays back with the envelopes affecting the modules, but it does not bounce that way.

@Jonathan Sasor So you're saying that what I am noticing is the same for you? In my test project, for instance?

Look at the envelopes (open up the automation lanes). The track starts with everything being disabled, then plays through and the envelopes enable the effects, then off again. This is the automation that I am talking about. It plays back, but does not then get committed when bouncing.

That's because I had saved it after attempting the freeze the track . Sorry . See above. Try this one. ProCh Export TEST.cwp

Sorry @Jonathan Sasor (not Jason!) the project file I sent was in the frozen state. So, if I unfreeze it and with the ProCh global turned ON and then either freeze or bounce to track or export, nothing commits.

I did just that! And yes, the problem still persists, and persists in whatever module I've tried it on. Here is my sample project with envelopes on three modules, for example. All these modulations playback but will not commit when bouncing/exporting as mentioned. ProCh Export TEST.cwp

Thank you, Jason, but I of course checked all that in the beginning. If there is something there that somehow applies only to ProCh. FX during export, tho, I'm not aware of it. But, to reiterate, it's only ProCh automations that don't get committed in any of the above mentioned operations, not just exporting (i.e. freezing or bouncing the tracks). And automations/envelopes on any non-ProCh effects get applied as expected in all cases.

...Any ideas on this??

And this is a good idea to get it into a text file, which is ultimately all I currently need. I'm not sharing the project or the files. I just need to deliver a list to a collaborator. Many thanks, as alwars!

Wow! That's exactly it! It's been staring me in the face all these years and I've never noticed it. Thanks so much!

Thank you! Yes, I forgot to mention that I know the CWAF tool, but this is (correct me if I'm wrong) a global audio finder tool, taking some time to do a system-wide search and then showing all files and all projects and their associations requiring quite a bit more work than just displaying all used files in the current project only in a readable list. Even when choosing the current project in the CWAF tool after it spends the time to do its search, it only sort of highlights the files by putting them at the top of a big list. If you then "Save report" , the report still contains the massive list of all files. I am looking just for a simple list of used files in the current project only that I can export in some way to be available as a list for remote collaborators who share libraries. Even if I could expand the window from Associated Audio Files and do a screen capture of the full list, this would be better than nothing! Why is this window (or any file list window for that matter) un-sizeable anyway?? I know this is pointless to ask because there's likely no way to change it, and I could likely do this with the CWAF window, but just saying....

I am finding that, when using automation for ProChannel FX parameters, that none of these automated controls have any effect when doing any of the things one would do to commit them to the project, i.e. none of the following: freezing the track bouncing to track exporting the track mixdown of the entire project The automations do however playback as expected before attempting to commit them to a mixdown, but It's as if the automation is being completely ignored during the mixdown. (I of course have Automation Read enabled.) In testing I find that simply applying the same controls statically applied (without automation) will get committed with a mixdown as intended. AND if I simply copy and paste these same automations into similar FX controls in the FX bin, for example, these also behave as expected in mixdown. What could be preventing only these ProCh parameters (any that I have tried) from automating in mixdown??

Is there a quick/easy way to view and then export this for an entire project? I only know of doing a Select all (Ctrl-A) and then choosing Associated Audio Files (Shift-K). This brings up a window listing all the said files, but the window is un-sizeable , so therefor very awkward to view a long list of long file paths/names. AND it allows no way to even copy or export this list. Is there some other way??

Ah! So I would use "MIDI Transforms" section, and not the "Events" section, over the full range of Notes (0-127), in order to apply to any note played, with the limited range of Velocity for the desired articulation, yes? I will give this a try. Thanks!