msmcleod

Have you tried checking "Enable MCSS for ASIO Driver" in Preferences ? This was actually introduced in 2022.09, and defaults to unchecked as some drivers got upset when the DAW tried to override their setting. Prior to 2022.09 it would have been effectively "checked" as long as "Use MMCSS" was checked. You could also try turning off "Plugin Load Balancing" - as a processor with a high number of threads and using a small buffer size may actually spend far more resources context switching than it saves by balancing the load. The other thing to check is your ThreadSchedulingModel. Compare this to what you have set in X3.

Given that you had a "Create Process failed; code 740" (which is to do with the process needing greater privileges), and Cakewalk runs as admin, it sounds to me like there's a permissions issue with your normal account. Until you narrow it down, you could run Cakewalk as admin. You could also try creating a new user account on the PC and see if that has better luck?

It looks like you've zoomed the clip area so that some notes are out of view - double click the area between the clips view and the track headers ( where the keyboard scale is) and that will reset the zoom.

Thanks for the report - we'll look into it. [EDIT] - Found & fixed the issue for the next release. Normally, the cache isn't cleared unless the project topology graph has changed (e.g. routing changes or adding/removing tracks). Bus routing and their names are cached, because it needs to walk the topology graph to find them - this takes time, which is why we introduced the cache in the first place. Track names however are instantly available, so they're grabbed in real-time. The fix was to clear the cache whenever Bus, Aux track, or Patch Points are renamed.

The CTRL key should do that for you: - When using "Insert Audio FX" from the context menu, hold CTRL while choosing the effect - When dragging from the browser, hold down CTRL after you've started dragging. However... what is actually happening here, is it's treating the insert as a quick-group operation - so make sure you've only got the one track in the selection before doing this, otherwise you'll get the effect added to all selected tracks.

FWIW I'm running a very old 3rd gen i7 3770 processor running at 3.4Ghz with 16GB of RAM, and I normally run my Scarlett 18i20 or 6i6 at 64 samples. It will actually run at 32 samples if it's a simple audio project with no FX, but 64 works for most projects unless I start adding some CPU intensive reverbs or something. I rarely need to go above 256. If I'm using my RME, I use a buffer of 128 simply because in real terms it's pretty much the same latency in milliseconds as the Scarletts at 64... and I have no need for lower latency. There has to be something else at play with the Apollo drivers, or at least something else on your system that is interfering with them.

@Michael Richards - For me, the Korg driver had problems not working, and the occasional crash but it never prevented the installation of Cakewalk, or removed other software (I've also got RME TotalMix installed). It was simply a driver that wasn't compatible with the latest Windows. What you're describing are far more serious problems, which sound like they could be: 1. A failing disk 2. A virus 3. A corrupt Windows installation You should rule these out in that order. 1. Failing Disk - right click on your system drive, select properties, then click the "Check" button on the Tools tab. Your computer should restart to do the check. If you've got errors, backup the disk ASAP and replace it. Note that SSD's give very little warning they're about to fail... they just start doing weird things and suddenly die. HDD's at least start clicking or making strange noises. 2. A virus - right click on your system drive, and select "Scan with Microsoft Defender" 3. Press Windows Key + X, followed by A to enter the power shell, then type the following: sfc /scannow If you get errors, type the following: DISM /Online /Cleanup-Image /ScanHealth You should get a report telling you whether it found any errors, and if it could fix them or not. If it found errors but couldn't fix them, as a last resort you can use this... however, you may have to re-install things like redistributables, audio/video drivers etc depending on how much needed to be restored: DISM /Online /Cleanup-Image /RestoreHealth

FWIW - I've found Korg a bit slow to react to Windows changes with their drivers. The Korg software/drivers stopped working when WIndows 10 20H2 came out, and it took a few months before a working update was made available. It looks like the same thing might have happened for 22H2 and WIndows 11. Personally, I've kept the Korg software running on my Windows 7 boot, and uninstalled the Korg software & drivers on my Windows 10 boot. The nanoKONTROL (both nanoKONTROL 2 and nanoKONTROL Studio) work fine with the class compliant drivers. The only reason you need the software is for mapping CC's.

One solution could be to do everything in 440Hz, then slow down the 2 track master in an audio editor (e.g. Audacity) so that it's effectively playing at 432Hz.

No, CbB will always use the default system browser, but FWIW I've got Firefox set as my default browser and BandLab login in CbB via Firefox is working fine for me on several machines. Check Firefox is up-to-date, and also check your security settings within Firefox. I'm using the Firefox default settings for security.

Omnisphere is memory intensive, so it's possible it could be a bad memory. This has happened to me in the past and is very difficult to identify. If you're lucky, you might see some discrepancies in the BIOS when it's reporting the speed of your memory modules - i.e. if one looks different from the other, that's a good indication that one has gone bad. Alternatively, Windows 10 has a built in memory checker: https://www.windowscentral.com/how-check-your-pc-memory-problems-windows-10

Hold down CTRL + SHIFT while dragging them into Cakewalk.

Although it's best to install them in order, I don't think it's absolutely necessary as long as you install (or re-install) CbB last.

Within Preferences->Keyboard Shortcuts, it's possible to bind the commands to MIDI notes - including start/stop. However this will start/stop the whole project, not just a specific track. To trigger a specific track, you could use the Matrix view - however, the Matrix view is clip based, so you'd need to make sure that everything on that track is a single clip (i.e. bounce to clip(s) ).

I've still got MasterWriter 2 running on a VM running Windows XP... it does the job well.

What's wrong with the Windows one?

Drag the meter bar (where it says +6 0 -6) up and down and it'll zoom the meter scale. Double clicking it will reset it to the default.

Linked clips allow you to change one clip, and the change will happen in all of the others. It's useful when you want the same thing repeated many times, and you don't want to have to edit the same thing in all of the copies. The whole point of linked clips is that the contents of them remain exactly the same - so you can't select lots of clips and link them. Linking can only be done at paste time using the "Paste Special" command. To unlink them, select the clips you want to unlink, right click and select "unlink". Linked clips is a pretty old feature, which in many ways has been superseded by groove clips / step sequencer clips. However whereas groove/step sequencer clips can be "rolled out" to many repetitions, a linked clip has the advantage in that it can be placed anywhere and changes will still be kept in sync. The main use case for linked audio clips is repeated copies of a drum loop.

Double check your anti-virus, OneDrive and any cloud sync settings, and make sure your Cakewalk projects directory, and global audio directory are excluded. If any of these are trying to access the audio files while Cakewalk is using them it could cause a freeze or a crash.

I've personally gone through a range of USB MIDI interfaces that have failed to perform to expectations. By far the worst performers were USB MIDI cables. There are two issues with these cables: 1. USB runs at 480Mbps , where as MIDI runs at 31.250Kbs. This means data being sent out needs to be stored in a buffer, so that it can be sent out at a slower speed. The issue is that the buffer in these cables is tiny (in the order of a few 100 bytes), so it doesn't take long for that buffer to be full, and data to be lost. This leads to stuck / lost notes, pitch bend / modulation being jumpy, and sysex basically not working at all. A good analogy is a bucket with small tap in it - you're drinking from the small tap, but at the same time it's being filled from a waterfall. The bigger the bucket, the less water overflows.... these MIDI cables have a very small bucket. 2. You can't really use more than one of them. Each of the cables is seen as a generic "USB Compliant MIDI Device" making it impossible to tell each one apart - and because of the primitive way Windows deals with both MIDI and USB, depending on which port fires up first, they can swap port numbers without reason. Friendly names in Cakewalk won't help you here, because Windows swaps the devices around. The MIDISport 8x8 and 2x2 used to be my interfaces of choice, but their drivers have not been updated for years and now prove unreliable in Windows 10. The only interface I can rely on nowadays is my Miditech MidiFace 8x8 (they also do a 4x4). This is a USB 3 class compliant device. I have 3 control surfaces and several controller keyboards running off one without any issues whatsoever.

As others have mentioned... don't use MIDI notes for key switches or commands - use articulations instead. Articulations won't appear as notes in the staff view. There's an outstanding task to associate articulations with staff view articulations, although I can't say how soon it'll get scheduled. This won't allow you to edit articulations in the staff view, but will at least show you them.

It's not Cakewalk doing this, it's Windows. Windows blocks drag and drop between programs running as different users as a security measure. There are a handful of old DX plugins that need admin permissions on their very first use, but aside from that there's no reason to run Cakewalk as admin. Also, consider that if Cakewalk is running as admin, so will every plugin - are you 100% happy with giving every plugin you've downloaded unrestricted access to your PC?

Just had a look at the code which greys out that command. The conditions are: 1. The selection contains something other than step sequencer clips 2. The first stream in the selection is a MIDI stream. I suspect you've got an envelope stream (either automation or tempo) in your selection. Try switching off "Select Track Envelopes with Clips" in the TV Options.

Ouch - sorry to hear that. Yes, that would explain it. If the CPU is damaged or starved of power, it can cause crashes. I actually had a similar issue, where my CPU would freeze after an hour or so of heavy network traffic (e.g. getting the latest NI Komplete, or copying files). Very frustrating. It turned out that the default CPU voltage setting in the BIOS was just slightly too low. It took me about 4 years to work this out.