Noel Borthwick

Not at all related. The user has the same issue in the 09 release and had some system config changes. Its a new PC. Will have to trouble shoot further before drawing any conclusions. As can be seen in his screenshot the drivers are listed. He gets silence on playback.

@Andrew Betzold what version of Cakewalk are you running? Please install the latest 2019.12 release. Are you using WASAPI shared mode? This is the normal way to handle USB microphones since you need to route it to a different output audio device. There was a fix for a similar problem with WASAPI shared mode. There is also a new release with some more WASAPI fixes so please try it out.

Early access releases are to validate specific fixes. We typically do not add new ones to that release.

@Heinz Hupfer Today full screen mode is not saved so it has to be set after the program starts.

@rv729 Please install this build and report back if it addresses your issue.

Thats really odd since I have that file set and it has no effect on toasts timing out at all.

@razor7music what display timeout are you referring to?

Load balancing should be used with discretion. Here is some information from the release notes when the feature was originally released. WHEN TO USE, OR NOT USE, PLUG-IN LOAD BALANCING Load balancing uses CPU power more efficiently, but it also requires some CPU power because it processes the plug-ins at smaller buffer sizes. If the loads aren’t unbalanced in the first place, any benefits of balancing may be offset by the extra overhead. So, first check out the existing performance status with the new Performance Meter modes (described in the next eZine section). Right-click on the Performance module, choose CPU Meter Display Options, then select Audio Processing Load. The Performance Meter will show whether the load on the CPU cores is balanced or not. Enable plug-in load balancing if: • There is CPU spiking, or one core is significantly higher than the others • The project uses a high audio latency setting • One track performs most of the effects processing Do not enable plug-in load balancing if: • The CPU load is evenly distributed (i.e., there is no excessive core spiking, and no individual core works significantly more than the others) • The project uses many lightweight plug-ins with a similar load • All tracks use about the same number of effects, or have a similar load • The project uses a Mixing Latency Buffer Size setting under 256 samples in Edit > Preferences > Audio - Driver Settings For information about how plug-in load balancing works, as well as “under the hood” tweaks you can do to alter the smallest internal buffer subdivision used for plug-in load balancing (which allows for more aggressive load balancing), please see the online help.

All Sandboxing does is crash a different process We've experimented with sandboxing - after all bitbridge is exactly that, except it only sandboxes 32 bit plugins. Doing it well is a very complex endeavor and potentially introduces a different set of problems. Workarounds are presently the only way most DAW's make plugins work but it takes cooperation and a willingness to work together between vendors.

Also ensure that your power scheme is set to High Performance. Even on desktop PC's this is important to ensure that.

Thanks @Scott Reams we'll investigate this.

The US-600 is a discontinued device and drivers are not maintained by TASCAM. Did you ever have this device work properly with any prior version of Cakewalk? We have not heard any information from you confirming this. Without knowing this there is really not a lot we can do to work around problems with faulty drivers. Yesterday we released an update that addresses a problem with certain buffer sizes that affected one TASCAM user. You can install that update and see if it helps you. See this announcement in the early access forum. PS: Please translate your messages into English when posting here since you are more likely to get responses from other users that way.

What @Colin Nicholls said. This is a known issue and we have plans of gradually addressing it. Its not impossible but its a significant amount of work for the UI to fully handle DPI scaling in the app. Today we let windows do the best it can - hence the somewhat fuzzy images.

I gave Joni some troubleshooting steps and hes unblocked for now...

@Matthew Sorrels we'll look into the string issue. Thanks for the report.

1. You can use the downloaded installer but you must activate on all PCs you install it on. 2. Activation is per PC 3. Starting ba doesn't do it automatically. However you can reactivate anytime in advance and renew the lease that way.

Is the driver from the manufacturer or a third party asio driver like asio4all?

You should use shared mode if you want to hear YouTube when using Cakewalk. Also check if your interface has a native asio driver some that will give you better performance potentially

Some misconceptions. Cakewalk will never get deactivated mid performance. Activation does not require updating the software. You can choose to activate directly from bandlab assistant now from the menu next to the Cakewalk button without installing a new build. Activation is not required very frequently and you will get a reminder weeks before it's required giving you sufficient notice. There playlist has been greatly improved and many issues fixed in the latest 2019.11 release, so it's a lot safer to use live than older versions.

Some questions. Which plugins are you using in your project? What is your audio driver mode set to in preferences / audio / playback and recording? If you want to share YouTube while playing in Cakewalk you may want to set it to wasapi shared. Which build of Cakewalk are you running? Have you installed the latest 2019.11 release?

Yes that wasn't intentional. Its been fixed for the next drop.

@deepseasquid Sent you a message with a link.

@Heinz Hupfer you said it worked before - hence my response. We'll fix the documentation, thanks. Effects settings should be saved in track templates. Those do not have anything to do with mix scenes. >>Also the Drag and drop mixscenes into a new project doesn't recall ProChannel settings like EQ or Comp! Keep in mind that mix scenes are tied to the project that they originated from. If you drag and drop into a project that was not derived from the same project there is no guarantee that the settings will be recalled because the track ID's may be different. However if you drag a scene into a project that was saved from a version of the original project it should recall fine. In the future we may allow importing scenes from other projects and allowing you to match settings from tracks and buses.

It should only stay if your mouse is over the toast message. If you move the mouse away it should disappear.

@deepseasquidTry logging out of BandLab Assistant and back in. Then retry and see if it works. Its possible that the change could take a bit of time to propagate over the web. Where are you located?