Noel Borthwick

Crazy. I hope they can fix it otherwise I'll have to somehow rename the dll or hide it somewhere else. Renaming is tricky since we're now redisting a prebuilt version of Libsndfile since they no longer ship Visual Studio solutions that are up to date and its too complex to build. Much easier for us to manage just using their prebuilt binaries. FWIW I can't reproduce this on my PC even though I have Waves 12.

@Ken MThanks for the report. Which version of CbB were you running? Most likely your media browser was pointing to the desktop where the zip files are present. Please check if this is the case. If you point the browser to a different folder and resave the problem will not occur. However I was under the impression that this issue had been addressed earlier. It was an issue with the shell browser extension we are using rather than Cakewalk itself. We'll look into it for the next release. Thanks for the detailed report. You can PM me the process monitor log.

See this post

Indeed, this is some weird bug with WavesLocalServer that we found earlier. I've already reported it to Waves. If you run into it the workaround is to kill that task before installing or reboot the machine. I'm sure its not intended to be permanently running since a clean boot doesn't run it.

There is a logged issue with WASAPI shared where the first buffer has some clicks. I'll investigate this for the next major release. WASAPI shared uses the windows Audio engine for mixing and has somewhat different requirements as compared to ASIO or WASAPI shared so there must be some factor related to this that we need to handle differently for the first buffer. Its not related to measure 1 it has the same issue whenever playback is started irrespective of the playback position.

Re 1 there are no changes in this update to change behavior. This is a per project / template setting so you must have inherited it from your project file. As scook noted this is in the media browser settings. Re 2. This has nothing to do with 32 bit files. If its set as a one shot it will not loop. Its an authoring problem if its intended to be a loop.

Do you get a crash dialog? That is the log. If so send a link to the dump file and we can tell you why its crashing. Link in my sig.

@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.