Promidi

Are you talking about using pitch bend events of a single note, or are you talking about using portamento on two notes where first note ends after the second note begins (legato). All methods are possible in the PRV. Whether your synth responds depends on the synth itself.

Thinking further about this, I am thinking that the Vdist runtimes might have been the culprit here (which would have been reinstalled).

No. I mean internally able to take advantage of multiple cores or your CPU. I.E. I believe a a single instance runs on one core only.

The reason I said test that specific plugin is to make sure that the GPU on your Graphics card is doing it's job of increasing GUI performance. If this was a common issue among Cakewalk by Bandlab 2020.11 users, these forums would have lit up with "me too" in response to your question. Personally, I am suspecting something with your system rather than Cakewalk itself. Sure, uninstall and reinstall Cakewalk by Bandlab if just to rule that out.

I am not sure a reinstall of Cakewalk by Bandlab will actually make a difference. As a test (and if you have the plug in) try an instance of Cakewalk's Linear Phase EQ (The one that was added to Sonar in April 2016). Then mess around with the GUI (adding bands) and see what kind of graphic performance you get there. (This plugin uses OpenGL for the GUI) Is Cakewalk the only program experiencing this lag? Are there any other processes running in task manager hogging the CPU (I guess you would have checked that)

Not here. What graphic adapter do you have? Do you have the latest drivers for it? (Check using manufacturer's websites rather than Windows updates)

Did anyone notice MTurboAmp is now in Alpha? Select it when installing. Also, it appears to be part of the MCreativeFXBundle bundle.

Personally I have found the VST2 version to be more stable than the VST3 version - especially when using multiple tracks. I find I have to use several instances as ST4 itself is not multi-threaded.

The latest version of Bandlab Assistant is 6.2.0 Download the latest installer from here https://www.bandlab.com/download/assistant/windows Make sure the Bandlab Assistant process is not running before installing. Go to Task Manager and make sure Bandlab Assistant is not listed under "Processes"

All Meldaproduction plugins have been updated to 14.12 https://www.meldaproduction.com/downloads List of changes here https://www.meldaproduction.com/changes-test#changes-14.12 https://www.meldaproduction.com/changes/?product=MSoundFactory https://www.meldaproduction.com/changes/?product=MPowerSynth

"IPP" was a little obscure (to me anyway) - I did not even notice it....

For some reason , Izotope Product portal does not present a new version at this time. The latest version is actually 1.9 and is now available as a VST3 as well as VST2 I simply downloaded it directly from Izotope (Much faster than Izotope Product portal anyway) https://www.izotope.com/en/products/vinyl.html

Can you give us a bit more info about your set up? Audio interface? Driver mode? MIDI Controller, Windows version What have you tried so far?

Yeah, I noticed this too....more so in this version as they are using two engines.

Can we have a screenshot of what you are seeing. What version of Cakewalk? Define "normal" means. The black dot is indicating which marker is to the left of the NOW

Things to try: With cakewalk confirmed as not running, rename your AUD.ini file. This file is here: %appdata%\Cakewalk\Cakewalk Core In preferences | Audio | Configuration File try adjusting the following EnableSetThreadIdealProcessor = False MixThreadCount = {number of cores minus 1} You might like to exit Cakewalk by Bandlab, go to the following folder and make a copy of the AUD.INI file before doing this: %appdata%\Cakewalk\Cakewalk Core Tried disabling C-states and Intel Speedsteep? (This is done in the PC's BIOS and the method varies between PCs) If that fails, maybe drop a note Cakewalk support at https://help.cakewalk.com/hc/en-us/requests/new?ticket_form_id=360000025633

What happens at 48khz 24bit 256 buffer size? What audio interface are you using? Are you using its native ASIO driver and not an ASIO wrapper, like ASIO4ALL? Have you checked for the latest drivers for your audio interface (using manufacturer's websites rather than Windows updates)

Save the file as a *.CAL file and save it in the folder location as defined in Preferences | File | Folder locations > Cal files Once that file is there, select the notes you want to alternate select. Then go to the menu Process | Run CAL (Or press Ctrl+F1) and select the file you saved.

You can do this with an Browser Addon called Stylus. However, you do need to know a bit about HTML and CSS to use it.

I have not encountered this issue with the 2020.11 Cakewalk by Bandlab update (or with any Cakewalk by Bandlab update for that matter) One thing you might want to try is updating your 2019 Vdist Runtimes. (Reboot after installation) See: https://support.microsoft.com/en-au/help/2977003/the-latest-supported-visual-c-downloads

You might be better off posting this as a new topic on the following forum. https://discuss.cakewalk.com/index.php?/forum/12-qa/

How long have they been saying that for?

That should work. I would use CC for the Chase mode for those particular Articulation maps. Really, the only real way to know if it's correct is to actually test it. Make sure you include in your test a playback from the middle of an Articulation map. That ensures CC events are chased property.

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