Promidi

Any chance of a listen?

If your MIDI track is set to a specific MIDI channel (rather than none), then MIDI is sent on that MIDI channel rather than the MIDI channel of each individual Event. However, if you are in Single Lane Controller mode in the PRV, then the MIDI channels of the individual Events is retentive. Personally, I set RechannelMIDI=1 in File - Initialisation File (Advanced), so that when I do a clip bounce of MIDI clips, the MIDI channel of each individual Event in the resultant clip changes to match that of the MIDI track that the Events are in.

Can you confirm that the UAD instrument plugin files (vst3 or dll) are actually in one of the paths as defined in Preferences - file - VST Settings. Of they are, maybe a reset and scan in in order.

If Cakewalk support ever asks me to do a clean install of Cakewalk (which has happened to me), I see if I can find another PC to do so. I have way too many custom Cakewalk settings that I have no desire to recreate.

Where are your MIDI tracks being routed to? If I have a Cakewalk project that includes MIDI tracks that are being routed to a vsti and I do an export to audio, I simply select none, then export. I make sure “entire mix” is selected tin the export dialogue box (which it usually is) Works every time.

Actually you are right. CAL can set track parameters , but not return them. One work around is to sort tracks by MIDI Channel, then scroll down to the last track and check its MIDI Channel. Then Undo

You could probably write a CAL script to do this.

On any MIDI track, enter CC91 Events before any notes. The value determines the reverb intensity.

Depending on the generation of Scarlet 2i2, use either the Scarlet control software or the scarlet configuration utility to change the sample rate of the Scarlet. On my Scarlet 8i6 3rd generation I have it set to 48khz. In Windows (Start + run > mmsys.cpl) , the only samplerate listed for the Scarlet 8i6 is 48khz

What have you tried so far? · Reinstalled Vdist runtimes? · Reinstalled (update if necessary) audio interface drivers. · No ASIO4ALL installed? (or Steinberg or Magix , etc equivalent)

This will very likely not be a Cakewalk issue. Check audio interface drivers (uninstall and reinstall - update if necessary) Check that you don’t have any wrapper ASIO drivers (ASIO4ALL, Steinberg universal ASIO driver, Magix ASIO driver, etc) . Might want to make sure the only driver that is installed is that of your Audio interface. Hopefully you’re using an audio interface that comes with true native ASIO drivers.

The help pane for the Group Policy entry that controls this setting says "Enable this policy to not include drivers with Windows quality updates." The setting that tells Windows updates to never to touch any drivers applies to quality updates only. Feature updates will still update drivers regardless of that setting. That “latest W11 large update” must have been a Feature Update.

No there isn’t.

I used CbB to open a few projects containing some VSTi and plugin I did a while ago in CbB. I also used CbB to open up an “in progress” project that I am doing in Sonar 2024 No crashes. They all opened and played back fine from start to finish. This is on a PC configured as per signature. I am wondering if the crashes you are experiencing is due to either a plugin or a driver. I am assuming you have opened any crashing projects in SAFE mode to see if it's a plugin, sent any crash dumps to Cakewalk Support.

This is why I have told Windows updates never to touch any drivers. I will do these manually if and when they are required.

Have you inadvertently set loop points?

Windows updates does not update the Vdist runtimes. The Cakewalk installers can. Many other application installer also can. I know some will think this is way overkill,but when ever I install a new program, I check the Windows “programs and feature”, sort by date, and see if an installation of a version of the Vdist runtimes has occurred. If there is a Vdist runtimes installation entry at the top, then I reinstall the latest versions of the Vdist runtimes.

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.