Promidi

Sounds like something a CAL script would be good at. (do (int note_number 1) (int even 0) (int nth 2) (getInt nth "Please enter nth note" 2 50) (forEachEvent (if (== Event.Kind NOTE) (do (= even (% note_number nth)) (if (== even 1) (do );exit do (do (delete) (insert Event.Time Event.Chan NOTE Note.Key Note.Vel Note.Dur) ) );exit if (++ note_number) );exit do );exit if );exit for );exit do

These Articulation Maps are a true game changer.....

Have you tried uninstalling the 2019 runtime and reinstalling See: https://support.microsoft.com/en-au/help/2977003/the-latest-supported-visual-c-downloads On my system the latest Microsoft Visual C++ 2015-2019 Redistributable is 14.28.29325 Exactly what error message do you see?

Feature requests live here: https://discuss.cakewalk.com/index.php?/forum/8-feedback-loop/

Is your controller showing up in the ACT Module?

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.

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.

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?

Just to make sure I understand what your synth responds to. For the articulation to trigger, it needs to receive a CC64 127 event.... but it will only work for those notes whose velocities fall between 0 and 39. Which VSTi or synth are you using that responds to both CC64 and notes with velocities between 0 and 39? For the given articulation, you would still have to have the two entries under "Generate New MIDI Events" for the CC64 events to actually generate the CC64 events. Then in the same articulation you would have to have an entry under "Transform Existing MIDI events" that maps all velocities from 0 to 127 to 0 to 39 I hope my understanding of what you're asking is correct.

Actually yes, you're right, but you don't have to have it at exactly the same time As long as it's on the note or before. I prefer to have it slightly before so I can tell that it's before simply by looking at it on the screen in the PRV - especially when zoomed out a bit.

Controller events do not have velocity information therein. Velocity only pertains to Note MIDI events. Do do what you have described as above, you need to have two entries under "Generate New MIDI Events" in the single articulation. One to send CC64 127 and the other to send CC64 0 The "Play at" settings for these entries need to be as follows: For the entry that contains the CC64 127, the "play at" needs to be set to "At Start" For the entry that contains the CC64 0, the "play at" needs to be set to "At End" Also, make sure the articulation map's start point is before the note(s) you wish this articulation map to affect.

First of all, I want to thank the Bakers for their diligent work with this release. This early release is adding a major feature that is needing that extra attention. It's almost ready. 2020.10 EA3 Build 84 Pitch bend transforms: The example below is the MIDI transform settings I believe should result in changing the pitch bends from full to half 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.

Try downloading a MIDI monitoring tool so you can see what events are actually being transmitted by the articulations in the a MIDI track. The one I use is MIDIMonitor1.3 Windows Just place the DLL file in your VST2 folder, rescan and insert as a VSTi

Only those with very high end machines would be able to take advantage of such a feature and maintain glitch free play back at the same time. Most people would simply leave this disabled if it were ever option.

I have that same audio interface (only I have Windows 10 64bit) You still have not provided enough information. What version number of Cakewalk are you using? (Numerically - don't just say "The latest") What is the version number of your Focusrite drivers? What sample rate, bit depth and Buffer size are you using? What driver mode are you using? Exactly what error message do you get (If you post a screenshot of it, You will have to translate to English)

Yes!

See:

In Preferences | Project | Record, does deselecting "Allow Arm Changes During Playback/Record" correct this issue?

And no Kontact Full version required .......

Did windows update mess with your audio drivers? Have you tried updating your audio drivers manually? (Using manufacturer's websites rather than Windows updates)

Just to confirm, do you have Preferences | Project | MIDI > "MIDI Event Chase on Play" and "Include Note Events" both selected. Also, to confirm , are you on 2020.10 build 75 Also, in your "sustain" articulation map, do you have it set to the correct MIDI channel. If the MIDI track's MIDI channel is set then setting the articulation map's MIDI channel to "Follow" causes the articulation map's MIDI channel to follow your MIDI track's channel setting? While the bakers are still working out some niggles, I have found with EA3 that for the events to be sent, the "transpose" needs to be ticked and the "chase mode" need to be set to "Full" or "Note". Unfortunately, with this EA3, setting "Chase Mode" to "full" reverts that setting to the following when the project is saved: If an articulation map's "transpose" is ticked, the articulation map's reverts to "Note" If an articulation map's "transpose" is unticked, the articulation map's reverts to "CC" I have found the MIDI event get sent (and in the correct order with "transpose" ticked and "chase mode" set to "Note".

See: https://help.cakewalk.com/hc/en-us/requests/new?ticket_form_id=360000025633

Exporting a project that contains key switches as a MIDI file already exports the key switches in the MIDI file.

Found an another couple of slight issues with MIDI transform in articulation maps In the Transform Existing MIDI Events section, if user has entered "Ch Aft" or "Wheel" for the Kind, the "Key/CC No". should be greyed out. Also, if "Wheel" is selected for the Kind, the allowable range for the vel/CC field should increase to -8192 to 8191 rather than the 0 to 127 for other "kinds".

Do you remember if this issue was present before the release of the 2020.10 ER?