Promidi

Try increasing it further.... I have mine at 750

Preferences | Audio | Devices and settings - Driver mode

However, even if the MIDI track's channel is set to a value from 1 to 16...... the PRV controller lane for that track still takes into account the channel of the individual controller events when choosing which lane to display in single lane controller view. If you have controller events that are set to different channels on the same track, you may not see all controller events in the controller lane. On the controller lane of older versions of Cakewalk, you could tell Cakewalk to display events of "all channels". That option is not available on later versions of Cakewalk. You can only select channel 1 to 16. "all channels" is not present on the channel select drop down menu. I wish the bakers would bring that back. What I like to do is configure my cakewalk.ini file so that when I bounce MIDI clips to a single clip on a given MIDI track, the MIDI channels of all the MIDI events on that track will change to match the MIDI channel of the track itself. To get Cakewalk by Bandlab to Rechannel the events when bouncing MIDI clips on the same track, to match that of the track itself, do the following: In the file %APPDATA%\cakewalk\Cakewalk Core\cakewalk.ini under the [WinCake] section, add the following line. RechannelMIDI=1

Are you using ASIO mode?

I have updated to 4.0.7 and on my PC, the clicking issues I reported in 4.06 no longer occur. I never had the other issues you mention. If you do upgrade and you still find there are issues with 4.0.7,you can always roll back to 4.0.4

Thanks for all the hard work you guys have put into this update.

You must have one hell of a Dropbox Quota.....

In that case, you could automate the bus level (where the effect is) rather than the send level of the track. That being said, most effects do have a wet level control that could also be automated.

Yes, I use this myself - I have the paid version.

Probably because the 9th generation CPU is so efficient that it does not really need hyperthreading. That being said, if it's available, you still might want to enable it - even if "hyperthreading has little to no impact on DAW production" I am thinking that there are likely many other processes that are running on a typical Windows 10 PC that can and does benefit from hyperthreading.

One thing I can suggest is that you disable every solitary power saving feature you can find. Speedstep (sometime called EIST), C-States, USB power management - lose all of it. Set CPU min and Max to 100% in WIndows power settings. Use highest performance power settings. If you have an Nvidia card, set Power Management Mode to "prefer Maximum Performance in 3d settings...(Remember, some plugins use the GPU for any dynamic GUIs - melda plugins do this) Another thing, is fully patch your PC. Make sure you always use the latest drivers for all hardware (Video, network, Audio interface - everything). Do all this before installing CbB. Disable any audio devices you don't use. Settle on a sample rate and set every audio device you do use (and have enabled) to that sample rate - even in Windows Control Panel sound settings. Obviously use ASIO for your main audio interface. Avoid ASIO4ALL like the plague. Others will have further suggestions.

One way I can think of is set up a bus (or an AUX track) with the given effect on it. Then, for the track that you want to effect on, automate the send level to that bus (which has the actual effect. I say to adjust the send level rather than simply disabling the VST is because disabling the VST would cause an abrupt silencing of a reverb tail for example. Others may have other methods.

I have configured my Windows updates so that Microsoft never updates any drivers on Patch Tuesday. I like to manage drivers myself - for this very reason.

Not at this time, no.

I notice 13.04 has been pulled, so especially if you have this version you might want to upgrade.

Note: Works only with the full version of Kontakt 5.1.0.6 or higher

Blue screens are either a driver issue or hardware failture. Initially I was going to suggest that maybe a driver was updated when Windows perform its update. That is until I read about corrupted files. Maybe have a look at the SMART info for your system drive. Can you check your system event viewer for disk errors (like bad blocks)

That sounds like something that would have to be sorted at your end - either your router or your ISP or even your PC itself... I have yet to have an issue downloading Cakewalk by Bandlab using Bandlab assistant.

It must be only certain Nvidia Video cards. I have one (an MSI GTX960, not over clocked) and I am not getting any latency issues in CbB. In my Nvidia control Panel - Manage 3D settings, I have my Power management mode set to Prefer Maximum Performance. I actually measured the current draw between modes and it was only a 3 watt difference. In fact, all power saving features on my PC are disabled. Those settings are really only for notebooks when battery life might be important (or maybe for those where power costs are insane).

This is done by editing your %APPDATA%\cakewalk\Cakewalk Core\cakewalk.ini file. You need to add WarnSilentBuses=0 in the [WinCake] section See: https://www.cakewalk.com/Support/Knowledge-Base/20090221/Warning-when-busses-have-no-output

Adelaide, Australia

There are a couple of third party programs that allow you to do this. https://winaero.com/ https://www.oo-software.com/en/shutup10

That's always an option as a test. However, remember there are some plugin's graphic User interfaces that take advantage of the Nvida CUDA. Meldaproduction is an example of such a plugin suite.

Start Run and enter eventvwr.msc However, to Interpret these properly, you really need to know what you're doing. There will be many events present, even on a system exhibiting very little issues.

Build 79 will be installed using Bandlab Assistant. I also do extensive 16 track MIDI only editing and there have even been enhancements in this area (Mainly with multi track editing on a single PRV window)