Noel Borthwick

@winstonhulleyThis is definitely an install issue and not related to the recent update. You may have a virus scanner that blocked this. Its in debugging mode because you turned on VST scan logging in preferences. Check if you have this file: C:\Program Files\Cakewalk\Shared Utilities\TTSLogger.dll If the file is present you can manually register it as follows: Open a dos box as an administrator in the search box type Command Prompt when you see Command Prompt listed, right click on it and choose run as administrator Then in the dos box type this: regsvr32 "c:\Program Files\Cakewalk\Shared Utilities\TTSLogger.dll" You should see a message saying that DllRegisterServer succeeded. This should resolve the issue. Alternatively you can also turn off vst scan logging which will stop using ttslogger. In preferences | VST Settings, uncheck "Generate Scan Log"

I have not followed this whole thread but your symptoms sound like you are getting phase cancellation in the signal path somewhere by doubling your input. You should not use direct monitoring and input monitoring though the DAW at the same time or you are doubling and causing potential phase issues. You may get better help if you post the project you are having trouble with to allow others to look at three rooting.

@lychee Your project has reason with custom modules that we dont have so we can't test it. If possible can you please send us a project that uses standard modules or uses a different synth? Its possible that something is corrupt with the project. Also are you certain that this problem is related to the new release?

Why not hire someone qualified to do system level troubleshooting if you have exhausted all possibilities?

In the picture above, you can drag the file from the browser or windows explorer to the divider between the tracks view and clips view (where the dB scale is drawn) or you can also drag it onto the track pane itself and it will automatically place it at time zero irrespective of the current position.

Just rename the file to .ogg. Its the same file format but oga is the correct file extension for ogg audio files. See this link.

The only reason it worked in WASAPI shared mode is because Windows was doing the sample rate conversion not the driver. In his case Windows would be upsampling from 44.1 to 96K which is inefficient but would work. MMCSS is completely unrelated to this and is unlikely to cause a problem in most cases.

For the record the dropout issue reported by @aidan o driscoll has been resolved. I did a teamviewer session with him and found the source of his problems. Its a driver problem with handling multiple clients at different sample rates and unrelated to Cakewalk. In his case his Windows configuration was set to use the EVO-4 device at 24 bit 96K and Cakewalk was set to work at 24 bit 44.1K. When I loaded his project on his system the driver appears to go into some infinite loop trying to fight Cakewalk setting the sample rate to 44.1. You can see the icons on the taskbar flashing and the driver refuses to switch to 44.1. I can't see what its doing behind the scenes but I expect its sending an infinite loop of ASIO restart notifications to Cakewalk which would explain why Cakewalk drops out immediately and then appears to hang. I changed the Windows sound settings configuration to 16 bit, 44.1Khz for all the input and output ports for the EVO and after that everything works perfectly. We even loaded his project with the driver set to run at 16 samples and it worked perfectly. I'm not sure why it defaulted to 96K in Windows since Aidan said that he didn't set it up that way. I've seen many audio drivers malfunction when used at different sample rates so the first step of troubleshooting should be to either set windows to not use the audio device or make sure that its using the same sample rate/bit depth as Cakewalk. If you have an onboard soundcard, often the easiest thing to do is set Windows to use that instead. The fix for running the device with two apps (Windows and Cakewalk) at different sample rates would have to come from the driver vendor. Aidan please start a correspondence with them.

@aidan o driscoll Send me a PM and I can try and do some troubleshooting with you. This is almost surely some sort of driver interaction issue with the system and Cakewalk.

MMCSS is likely a red herring. The only case I know about it causing a problem was with Lynx and that was due to a bug in their driver which they fixed. They were not handling MMCSS failing which is a normal condition that can occur if the host has set up MMCSS.

We'll look into it. Its a harmless if annoying notification.

It would appear that something is inefficient when running with that ASIO device if its not showing an issue in WASAPI. Hard to say since we've never used that device. Will try and contact the vendor and ask them to send us an interface for testing.

Edge is part of the operating system now whether you use it or not. This is not related to BandLab Assistant, webview is used to serve up html content and to handle the security requirements for single sign on authentication.

Another quick way is to drag the files to the track view or the divider between the TV and clips pane. This is a shortcut to insert at beginning.

A request. Kindly keep this thread in context to issues that are specific to this release. Please do not log general bugs or feature requests here because it will get difficult for us to follow. thanks!

Ive never understood how people can tolerate running such old builds of Cakewalk. 8.5 and SONAR literally have thousands of issues that have been since been addressed. The only reason I see some people running Win7 is for aging hardware that is no longer supported with drivers. We’ve said before that we don’t have resources to support Win7 anymore and only allow it to install as a courtesy. If it stops working due to new features we’ll have to block it installing at that time. The older builds will potentially work but would still need authentication as before.

Thanks. This installer is a one time thing and subsequent updates wont need to do this. We’ll look into the truncated text, We’ve already changed it so the webview install is no longer silent.

No activation is just an operation that requires login. So does connecting to bandlab to upload projects. We’ll also be adding more features in the future that are connected with your account. Activation was the first that uses SSO.

Can you please share the specific project file with us?

Yes. Also turn off any surround stuff as noted.

Logging into the forum has nothing to do with Cbb. You have to log in from CbB itself for in-app activation to work. If you have never logged in it wll prompt you the first time. An easy way to force it is to choose “Help / Refresh Activation”. This will ask for a login the first time and then activate again. Subsequent attempts wont ask for login again.

What was the error? Please send a link to the project file so we can investigate.

Its not just for onboard audio. It shows up with my USB headset too. So its apparently something based on how the driver is written. If SSL is relying on USB class audio support this could explain it since thats using the Microsoft driver.

So indeed it looks like your USB interface got flagged as “enhancible” That would certainly account for the poor quality audio since its not designed for music production. I would report it to Microsoft through feedback as well as SSL

Assuming that you have logged in at least once and the credentials have not changed activation should be automatic. IOW as long as your PC is online at some point when it needs to CbB will automatically refresh itself. This was the main rationale for in-app activation.