Promidi

If you are talking about the apostrophe, no it doesn’t... (not on my keyboard anyway). On my keyboard, shift apostrophe generates a double quote.

I created a custom keybinding for this. (apostrophe)

Remember, starting your project at measure 1 can cause issues if synths (or even plugins) need to initialise before hitting that first note.

For the benefit of those down under, that’s around September/October 2023.

As far I remember, they all do.

Rolling back to a previous version of CbB might leave users with a version of CbB that will eventually fail to activate. That is very likely the reason a roll back installer for CbB is not provided.

Massive and Massive X have received updates. Update via Native Access (Tried this on my PC configured as per signature and this works) Massive X Version 1.4.5 16 December 2024 FIXED Massive X is now macOS Sequoia compatible ADDED User defined tags can now be added to presets ADDED Splice licensing support KNOWN ISSUE Graphical anomalies can be observed when switching presets in browser and when saving user tags Massive Version 1.7.0 16 December 2024 Please note: this is the last version of Massive that ships a VST2 target. We recommend to use VST3 whenever you can FIXED Massive is now macOS Sequoia compatible ADDED Scalable user interface ADDED Splice licensing support

Cakewalk updates would not do this. Can you post a screenshot of your project, including the inspector showing the MIDI track info for the problem track.

https://discuss.cakewalk.com/forum/8-feedback-loop/

Maybe a user with FX Collection 5 can chime in....

After logging on to Arturia, I was offered it for $US59.00. Probably because I have FX Collection 4 At this time I do not intent purchasing - I have enough tape emulation vsts.

Loading this project will make this issue manifest on my system. Controller Pane Gets Smaller with Every Click of Drum Pane Note - Sonar.cwp

As per title. Update via Melodyne > Help > Check for Updates.

The best way to know for sure is to give the trial a go.

By giving us more information....

Try using Cakewalk’s Vdist runtime repair tool. See:

I am using a PCR-800 which is also quite old and I have never had this issue. I am sure we can get the bottom of this. Can you please try the following: If you create a project with a single MIDI track. On this MIDI track: 1) set the input to receive from CasioWK-1600 on MIDI channel 1 (or what ever MIDI channel the CasioWK-1600 is transmitting on - even omni might do) 2) set input echo on, arm it. When you record to this single MIDI track, does this scenario create the doubled notes?

Forgive me if this is mentioned elsewhere..... but what model is your MIDI keyboard?

Remove that entry in Preferences - MIDI - Control Surfaces and see what happens....

One way to find out.....

If you rename your aud.ini file (found here: "%AppData%\Cakewalk\Cakewalk Core\") Does Cakewalk start?

What is in Preferences - MIDI - Control Surfaces

I really hope not. That would really stuff up my workflow. In fact, I broached this subject with the bakers, and they have no plans to abandon CAL scripts (or even Studioware Panels) because there are still many people (myself included) who use them every day in their projects. Instead of waiting for said MIDI editing function to be made available in Sonar, I simply write a CAL script to do it. I am really thankful that I have that ability. MIDI is really how you get all the cool stuff to happen in any DAW. Without MIDI, then all your DAW becomes is a glorified tape deck.

See if uninstalling your Vdist runtimes then runing the Cakewalk redist installer helps. Im am not sure if Cakewalk’s redist installer requires Vdist to be present in the first place. If it does, then you can run Microsoft’s latest Vdist runtime. See: (Next to X86) https://learn.microsoft.com/en-au/cpp/windows/latest-supported-vc-redist?view=msvc-170#latest-microsoft-visual-c-redistributable-version

CAL scripts can be written to adjust existing velocity values or set velocity values to new values. For instance, this will set the velocities of selected notes to a random number between 60 and 100) (do (forEachEvent (if (== Event.Kind NOTE) (= Note.Vel (random 60 100))))) This one shifts the velocities of selected notes up or down by a random number up to 10. (do (int newvel) (forEachEvent (if (== Event.Kind NOTE) (do (= newvel (+ Note.Vel (random -10 10))) (if (> newvel 127) (= newvel 127)) (if (< newvel 0) (= newvel 0)) (= Note.Vel newvel) );end do );end if );end for );end do