Promidi

There was an August Windows update as well. Check your drivers - maybe Microsoft updated those to generic versions. Personally, I have told Microsoft never to touch drivers while doing their monthly updates. Disabling all Windows updates is generally a bad idea - but I like to update hardware drivers myself by visiting the actual manufacturer's websites. This could also be a hard disk on the way out. Check your system event logs for disk errors - like bad blocks, etc

Did you also install the 2019.7 Build 79 hot fix? The old April 2018 version "may work", but there have been many bug fixes and enhancements since then. I could not imagine going back to April 2018. Did you contact Bandlab support? https://help.cakewalk.com/hc/en-us/requests/new While I am not doubting you had issues, I have been updating Cakewalk by Bandlab with every update. The only major issue I had was with Build 70 in that old projects would not load. Cakewalk released a hot fix to fix this issue. Currently we are at Build 79. To date, this is the most stable version yet.

I have never had a Windows update (even a milestone one) turn game mode back on. Mind you, if one is having issues, it does not do any harm to check.

Depending on the soft synth. I use a hardware XG synth and all I need to send is RPN 0 and 128 x the number of semitones required as the value. Therefore if I want to set the pitch bend range to 12 semitones, the value would be 128 x 12 which is 1536 I enter RPN 0 1536 As RPNs are a combination of CC events, for the above they are CONTROL, not RPN

As a test, what happens if you temporarily disable your Nvidia driver in device manager? Your screen will flicker as you do this - it's quite normal. Note: I am assuming your Nvidia driver is version 431.60

Unfortunately the screenshots are too small to read (The forum reduces the size). However, what video card do you have....if it's an Nvidia, have you disabled its audio. Might be worth uninstalling and reinstalling your video driver. When reinstalling, do a clean install. Also, for what it's worth, disable your wifi card (if you have one) and see if that makes a difference. I have an Nvidia GTX960 with the latest Nvidia drivers (as of 14 Aug, 2019 version 431.60). I do not have a wifi card.

At the end of the day it probably doesn't really matter - especially if you have SSDs drives all round. If you have enough ram, then the page file should not even be touched. It's just that some programs require one to be actually present even if it's not utilised. You signature says "16 ghz RAM" I'm assuming that is actually 16gig ram so in your case your page file would not be utilised even if it's present.

Latencymon should tell you the highest reported ISR routine execution time (us) and highest reported DPC routine time (us) When the red light comes up hopefully this will tell you the process causing the hiccup, Also, have a look at the driver tab and sort by ISR count and DPC count (to put the highest at the top) That may give you some clues. Note: the latest version of Latencymon is 6.71

You might want to leave this installed. This is basically Intel's hard drive controller. If you uninstall it, your machine will use Microsoft's hard drive controller driver. I think I would rather let Intel's driver handle that. Also, if you need to reinstall it you will have to hunt the correct version for your chipset. Note: I also have Intel Rapid Storage Technology installed - In fact, I just updated it. It does not negatively impact my system or Cakewalk in any way. Have you heard of a tool called Latencymon. That may help in working out what is causing the pops and clicks on your PC https://www.resplendence.com/latencymon

Just to confirm that DropoutMsec=-8 . Did you notice that the value is minus 8 Also with your page file, You should at least set it to something. I have 16 gig ram and three physical disks (C:\ D:\ and S:\) My page file is set to 1000meg and it's only on D:\. The rest are set to zero. I have no clicks or pops, even while playing with a project running a few synth VSTs and effects In the old days the (unwritten) rule was your paging file should be 1.5 (or was it 2.5, I can't remember) times your physical ram. But that no longer applies. I mean I am not comfortable with a 24gig paging file.

Depends what data is actually present that is causing the dead air at the end of the song. Look for MIDI events. Look for automation events. There may also be markers or even time signature changes. Tempo changes are also events to look out for. If you have many tracks to check, you can select all tracks. Work out where you want the track to end. Put the Now marker to that point. Then go Edit | Select | From=NOW. Then hit delete Special. Make sure you select all boxes there. Also under the track menu, make sure Options | Stop at project end is selected. Hope that helps

I would suggest saving your project closing Cakewalk overnight. Even if you do leave your Windows logged on. There may be tasks that Windows itself performs over any given night that could adversely affect an open Cakewalk session. For instance, you do nightly backups don't you (at least I hope you do)?. Even though backup programs generally can backup open files (which your project and its files would be), it would probably be safer to have your machine logged off and at the log on screen for things like this. There many be other task that happen overnight that could affect an open project. My Pc stays on 24/7. It gets restarted every 2nd Tuesday of the month (Patch Tuesday) after the installation of Windows updates. However generally, overnight, the screen gets turned off, but the PC is at the logon screen.

I have a Focusrite Scarlett 2nd Gen 2i2 with the latest drivers and I am also very intermittently experiencing the second issue. Unfortunately , I have not really done any troubleshooting of the issue. Stopping and starting the audio engine always gets me back up and running. If I were to ever troubleshoot this issue, the first thing I would be trying is to increase your buffer size using whatever tool Focusrite gives you for that. I have mine set to 256 samples. Sorry I could not be of more help. (as least you know the second issue is not just you)

Make a copy of your AUD.ini file. This is important so you can revert This file can be found here: %APPDATA%\cakewalk\Cakewalk Core Then go into Cakewalk , Preferences | Audio | Configuration file. Try the following changes (This is assuming you have enabled hyperthreading) EnableSetThreadIdealProcessor=0 MixThreadCount=7 ExtraPluginBufs=16 DropoutMsec=-8 Don't forget to restart Cakewalk once done.

What version of Cakewalk/Sonar are you using? BTW, yes, you would want to enable Hyperthreading.

In Windows power options, have you set min and max CPU to 100%. You might also have to also disable C States in your BIOS What plugins are you using? Is your PC fully patched? Are you using the latest Focusrite Scarlett 18i20 drivers? Have you disabled your onboard sound?

Looking at the user guide for Morphoder, it states that "By default the Morphoder will launch with the Internal synthesiser selected as the Carrier signal". This internal synthesiser likely has a pitch bend range of 2 semi tones and this cannot be changed. However, I'm thinking because it says "by default", it implies that you can route another sound to be your carrier. What I would do is find another synth that allows a pitch bend range greater than two semitones. Then tell Morphoder to use that synth's sound as the carrier. You might want to set this synth to a simple sawtooth sound to start with. See Page 6 of the Morphoder user guide. Look under "CARRIER SELECT". You might want to set this to "sidechain". Then you can set up a synth as a simple instrument and route its output to the Morphoder side chain input. The Morphoder user guide can be downloaded from here. https://www.waves.com/1lib/pdf/plugins/morphoder.pdf

Sounds like you have a simple instrument loaded. Without seeing your screen, it's a bit hard to guess your track configuration. What you need to do is open the inspector and set the MIDI track's output to the MIDI port. At the moment, it sounds like the MIDI track is being routed to a VSTi plugin.

Is the Yamaha USB driver listed in Cakewalk Preferences | MIDI | Devices and are they selected. Is the PSR2725 actually transmitting anything? Note: Not having the S975.ins file would not prevent the MIDI data actually being sent and received. The S975.ins file only allows you to select patches, controllers and what not by name within Cakewalk.

I highly doubt this is an issue with Cakewalk itself, but it's a deeper Windows issue. I once had this with Microsoft office a little while a go. Running the program wanted to run the installer. On my PC, It turned out to be a corrupted installer tree in the registry. When this happened to me, I was able to track down the corrupted entries in the registry and delete them. I think it was somewhere in the installer tree in the registry where windows keeps track of your program installations. However, I am a former IT technician. Some of my troubleshooting and repair techniques were pretty complicated, so I would not recommend a non IT technician even attempt it. If you have a friend who knows exactly what they are doing, they might be able to solve this for you. An "end user" fix may be to do a system restore to a time when Sonar or CbB started correctly.

My mistake.... but where ever they are from, I agree with you about the need for the note names to persist across sessions (as well as being saved in Screensets)

I tried Samplitude Pro x3 when Gibson pulled the plug on Sonar.... I ended up uninstalling Samplitude and going back to Cakewalk by Bandlab. For me and they way I use CbB and all the functions I use, nothing can actually touch it. I could not even go back to Sonar Platinum as it was first released. I would miss many features of Cakewalk by Bandlab.

You can right click on the vertical keyboard on the left and temporarily set which note names display. It gets the list from the drum maps that are available. However, it would be nice if Screensets retained this setting.

That is correct. See Page 102 of the user guide. Here is the link for the Yamaha USB driver. Install this before connecting your PSR970 Keyboard. https://usa.yamaha.com/products/musical_instruments/keyboards/arranger_workstations/psr-s970/downloads.html

It actually happens on more than the guitars. It even happens on some native ST4 instruments.... On the plus side, I got an email from IKM support to say the development team have verified and fixed this clicking issue (as well as the Steel Drum instrument issue) internally. An forthcoming update will be released soon to address these issues (Not sure of ETA).