[CLOSED] Cakewalk 2020.10 Early Access 3 [Updated 5-Nov-2020]

[winkpain]

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

[Nigel Mackay]

"In" is the incoming MIDI event - the channel range, the lowest velocity, the highest velocity, the lowest note, the highest note which is "acceptable."

"Out" is the MIDI event that goes out if the incoming event is acceptable.

"Offset" says how much each parameter must be changed. You can opt to move events 2 channels higher, or lower. You can change the note number, you can change the velocity, you can change a CC's value. If the checkbox is checked, it is a fixed offset, if unchecked, it is a percentage.
Put a 5 in the Vel/CC Val column, unchecked and the Velocity/CC Value will be increased by 5%. Check the checkbox and the Velocity/CC Value will be increased by 5 units.

[msmcleod]

6 hours ago, winkpain said:

...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?

The transforms work on one event at a time.  It's not possible to transform an articulation based on the status of more than one event, so no, you can't do this.

[David Roach]

Bug in latest release. I just installed Cakewalk_by_BandLab_Update_Setup_26.10.0.075. After installation recording did not function correctly.

I put an audio track into record as per usual, pressed R, played for a while. On pressing STOP, the recording disappeared with no indication of a recording in the history. Tried a restart etc etc, still the same.

Wound back to previous release and all is well.

[Promidi]

2 minutes ago, David Roach said:

Bug in latest release. I just installed Cakewalk_by_BandLab_Update_Setup_26.10.0.075. After installation recording did not function correctly.

I put an audio track into record as per usual, pressed R, played for a while. On pressing STOP, the recording disappeared with no indication of a recording in the history. Tried a restart etc etc, still the same.

Wound back to previous release and all is well.

There is an even later release (Release candidate) that is version 2020.10 Build 84 (Installer "Cakewalk_by_BandLab_Update_Setup_26.10.0.084.exe")

The link to the latest installer is in the first post of this thread.

If build 84 does not fix this issue, In Preferences | Project  | Record, does deselecting "Allow Arm Changes During Playback/Record" correct this issue?

[David Roach]

20 minutes ago, Promidi said:

There is an even later release (Release candidate) that is version 2020.10 Build 84 (Installer "Cakewalk_by_BandLab_Update_Setup_26.10.0.084.exe")

The link to the latest installer is in the first post of this thread.

If build 84 does not fix this issue, In Preferences | Project  | Record, does deselecting "Allow Arm Changes During Playback/Record" correct this issue?

Thanks Promidi, the latest release "Cakewalk_by_BandLab_Update_Setup_26.10.0.084.exe" works fine in respect to that issue.

[Noel Borthwick]

Yes the issue has been fixed in the latest release candidate

[Jordi]

Sorry, there's a way to send the articulation inserted data to the synth clicking with the mouse, like you do when click a note in piano roll?

The only way i find is positioning the cursor before the articulation and push the play.

Will be a good option to hear how sound the articulation, you can click with the mouse.

Thanks.

[winkpain]

6 hours ago, msmcleod said:

The transforms work on one event at a time.  It's not possible to transform an articulation based on the status of more than one event, so no, you can't do this.

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!

[msmcleod]

20 minutes ago, winkpain said:

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!

@winkpain - what you've got here is two Generated MIDI Events followed by a single transformation event - this is fine.  I obviously misunderstood your original question.

[winkpain]

3 minutes ago, msmcleod said:

@winkpain - what you've got here is two Generated MIDI Events followed by a single transformation event - this is fine.  I obviously misunderstood your original question.

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 ?

[winkpain]

15 hours ago, Promidi said:

Channel aftertouch to key aftertouch transform:  The example below is the MIDI transform settings I believe should result in changing Channel aftertouch to Key aftertouch affecting Note C3 (60) .  What actually happens is the resultant values get zeroed out.

@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?

[Nigel Mackay]

35 minutes ago, winkpain said:

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 ?

(I hate it when a post seems to disappear. Apologies of this appears twice.)

Remember this caveat:

When triggered any existing MIDI events get transformed.
At the same time, the MIDI events in the top half get created. They do not get transformed.

[winkpain]

20 minutes ago, Nigel Mackay said:

(I hate it when a post seems to disappear. Apologies of this appears twice.)

Remember this caveat:

When triggered any existing MIDI events get transformed.
At the same time, the MIDI events in the top half get created. They do not get transformed.

"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?

[Toy]

sorry. I found a small bug.
The selection is not set correctly when the first Articulation in the track is included.
Look at the range of the time ruler.
When the first Articulation is included, the selection time is set from the beginning.

This bug is pasted in an unexpected location when copying. Please be careful.
I was able to avoid it by inserting some Articulation first.

 

 

Edited November 6, 2020 by Toy

[Rfcousins]

On 10/31/2020 at 4:27 PM, Matthew Sorrels said:

MIDI Event Chase on Play and Include Note Events are both checked.  Zero Controllers When Play Stops is unchecked.

Thanks for this. When did this change? Is there a Global setting or only per project. This is effecting 1000's of my files UGH!

[winkpain]

1 hour ago, Toy said:

sorry. I found a small bug.
The selection is not set correctly when the first Articulation in the track is included.
Look at the range of the time ruler.
When the first Articulation is included, the selection time is set from the beginning.

This bug is pasted in an unexpected location when copying. Please be careful.
I was able to avoid it by inserting some Articulation first.

 

 

I see this as well.

[Promidi]

46 minutes ago, Rfcousins said:

Thanks for this. When did this change? Is there a Global setting or only per project. This is effecting 1000's of my files UGH!

The "MIDI Event Chase on Play" has always been there (All though in older versions of Cakewalk/Sonar it was called "Patch/Controller Searchback before play starts")

The "Include Note Events." feature was added in Sonar Platinum/Professional/Artist in the 2017.1 update

This is a per project setting.  There is no global setting for this as far as I know.

[Promidi]

3 hours ago, winkpain said:

@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?

Because the "kind" parameter for both in and out can be changed independently of each other, I took that as meaning that it is indeed possible to convert Kinds using the transform of articulation maps. 

I am sure that if it was not possible, my post would have been met with a swift: "Sorry that cannot be done!"

I just tried a specific CC to Key Aftertouch transform and that did indeed work. 

I thought I would test a Channel Aftertouch to Key Aftertouch transform and I encountered the issue mentioned.

This would bring Key Aftertouch events a step closer to being able to be directly edited in the PRV (Something not possible currently).  Have them as Channel Aftertouch events in the PRV, but transform them to Key Aftertouch events using articulation maps...   Granted, I would probably have to have an articulation for each key.

Currently I have to use a CAL script I wrote that converts the actual Channel Aftertouch to Key Aftertouch data as it appears in the project.

[Nigel Mackay]

2 hours ago, winkpain said:

"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?

100%