Promidi

This is now done from the Export Dialogue screen. See: http://legacy.cakewalk.com/Documentation?product=Cakewalk&language=3&help=0x2026A

This is why whenever I install any program, I make it a habit to see if it has installed an earlier version of the Vdist runtimes. If so, I re update them.

As per title. Update via Izotope Product Portal RX 11 Standard Release Notes https://www.izotope.com/en/products/release-notes/rx-standard-release-notes.html RX 11 Advanced Release Notes https://www.izotope.com/en/products/release-notes/rx-advanced-release-notes.html

For the actual crashes, my money is on the sysex being the issue. In the past, have had issues where sysex can crash Cakewalk. Since I use sysex intentionally my solution, at the time, was to space them out a bit. However, I agree that, if you a routing your MIDI data to a VSTi, delete the sysex banks.

Just tried it and Works here. Sorry if this is a silly question, but is the MIDI track in which the note(a) you are wanting to audition routed to an audible synth VSTi or out to a synth capable of receiving MIDI notes.

Maybe the $US40 was a glitch?

That should not be happening on a properly configured PC. Have you excluded all Cakewalk folders from any real-time anti-virus/anti-imalware scanners. This could even be a hardware issue. You might have to contact support. https://help.cakewalk.com/hc/en-us/requests/new

Whistle.wav

Not enough information. What have you tried so far? This is probably either be a buggy plugin or a buggy audio interface driver. Update your audio interface driver. You might want to Uninstall and reinstall the drivers for your Audio Interface (head to the manufacturer’s website to see if there is a later version, don’t use Windows Update). To see if it a plugin, hold shift while opening your project to bypass plugins.

Yes.

Here is an example using a single keyboard to split between a piano and pads.

No one here is going to know if here are plans for Sonar 2024 (soon to be Sonar 2025) to ever include a default General MIDI Player. You would probably be better off asking the Bakers at support@cakewalk.com. However, their answer will likely be" “Not at this time, but never say never.....” in other words.... no idea.... Personally, I think they should. I use an external Yamaha XG MIDI player, I do not Sonar 2024 to include a internal GM player to Sonar 2024 at the moment. However, I can see why many Sonar users would want one.

Just to clarify. Are you modifying a factory workspace, keeping the name, and using that as your workspace, or are you modifying a factory workspace and saving that under a new name and then using that as your workspace? If you are modifying a factory workspace and not renaming it, then I would expect that factory workspace to be restored with the factory version when you do a CbB update. I would expect Sonar 2024 to do that same (a Baker might confirm this). I would try modifying a factory workspace and saving that under a new name (effectively, becoming a user Workspace). Then use that as your default workspace. I would also enable “Apply Workspace on Project Load” on the workspace menu.

I have never had my workspace reset or record reset to “comping” after an update. This is with CbB or Sonar 2024. I do have “Apply Workspace on Project Load” enabled on the workspace menu. Are we sure something else is not going here?

As long as you did not do the uninstall and reinstall CbB the includes deleting the registry and cakewalk folders, you should not have to reinstall your virtual instruments and sound libraries. Can we please see the following screenshot: Preferences - MIDI - Devices (being the A-800PRO, you should see several A-800PRO related inputs) Preferences - MIDI - Control Surfaces The MIDI input device used for Control Surfaces needs to not be the same MIDI input device used for any MIDI track’s input. I have the PCR-800 (the predecessor of the A-800PRO) and I do not have any Control Surface under Preferences - MIDI - Control Surfaces > Connected Controllers/Surfaces. My sustain pedal connected to the PCR-800 works fine in CbB.

If you want a MIDI file's tempo map included, then open the MIDI file, do not import it.

I got a confirmation email from the dev.... The website is the prevailing. The PDF needs updating. Interference requires full retail version of Kontakt 7.2.0

MODO Drums 1.5 works fine here (stand-alone and in CbB) - always has. What steps have you tried so far? I am assuming you have gone into the MODO Drums 1.5 settings (cog, top right) and restored purchased content.

Very little to go on. Can you confirm if this Buzzing or vibration also appears on an exported wave file. If so, can you post a short recording of this Buzzing or vibration?

Then they need to update their user guide to reflect that.....

DAW = Digital Audio Workstation. Cakewalk by Bandlab is a Digital Audio Workstation.

The website says KONTAKT 7 Full is required, yet the PDF user guide says KONTAKT 7 PLAYER is required. I have contacted the vendor for official clarification.

Reputable Source?

Instead of export, have you tried File - save as and then select MIDI Format 0 or MIDI Format 1 as filetype.

Upgrade to Melodyne 5