Promidi

There are three possibilities of Chase mode: Note, CC or Full. It determines the event Kind in an articulation map that is chased. Being “chased” means that if you start playback in the middle of a NOTE ON event, Cakewalk searches back for the most recent note event or controller events. Now that articulation maps have been added to Cakewalk, these also have to be searched for and sent to activate the keyswitching. Here is a scenario where this is important. Imagine you have a sustain violin on 1 measure followed by a staccato violin on the next. You would use an articulation map to change between those articulations. Now if you open the project and start playback on the measure with the staccato violins and the chase mode for the staccato articulation is set to CC, the key switch note would not be sent. Therefore the staccato would likely play with the wrong articulation instead. Changing the chase mode to "Note" ensures that the correct keyswitch note gets sent when you start playback in the middle of the project and articulation map. Note: For this to work, go to Preferences | Project | MIDI, and make sure both "MIDI Event Chase on Play" and "Include Note Events." are selected.

This is an excellent start. The only change I would make to these is change the Chase Modes from CCs to Note for all articulations . The quick way to do this is to open the artmap file in any text editor and replace all instances of "chaseMode":2 with "chaseMode":1

Ability to rename controller lanes in PRV rather than just those names as defined in the MASTER.INS.

Until this is available in Cakewalk, you could use a VSTi that has a MIDI Thru function. Then you can route its MIDI out to as many synths as your CPU can handle. MIDImonitor 1.3 is an example of a VSTi that does MIDI Thru https://pw.promidi.com.au/softopen/midiMonitor_x64.zip

Yes there is. Look for "Articulation Maps" in the latest version of Cakewalk by Bandlab (Version 2020.11 Build 088) See: http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=EditingMIDI.51.html

There are other options. Do you have a third party audio editor (like Goldwave or something like that)? Depending on the third party audio editor you have, it might open the audio track component of the video file. Another option is to reimport the resultant video back into an empty project in Cakewalk to see if there is an audio track in the resultant video.

Not within Cakewalk itself. However, what you could do is export the articulation map to an artmap file. As this is a standard text file (albeit with an artmap extension), you can edit in a text file editor that handles "regular expression" format for its search and replace function.

Just to make sure, have you opened the resultant video in a video editor to confirm that the video file indeed contains a silent audio track?

Can't tell from the image. Is it possible that a huge clip is hiding what is underneath. Maybe view take lanes for the drum track.

This thread is now closed. You might want to start a new thread for this issue.

Does this need the full version of Kontact?

You are better off sending this as a normal support ticket now that the update has been publicly released. https://help.cakewalk.com/hc/en-us/requests/new?ticket_form_id=360000025633

Click Help | about.... you will see your Cakewalk version. I am agreeing with Mark. That sounds like a plugin causing this. Try bypassing all plugins - how you do that depends on which version of Cakewalk you're using. Are all those plugins 64bit? The latest drivers for the Scarlett 2i2 2nd Gen is version 4.65.5 https://fael-downloads-prod.focusrite.com/customer/prod/s3fs-public/downloads/Focusrite_Usb_4.65.5.658.exe

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.