Noel Borthwick

@Scott Abbey Please upload the project to any file share like Dropbox and pm me the link

@camarea I don't follow. It expect it to update during the bounce process when fast bounce is off since the rest of the UI is active.

Yes their main engineering is here.

@Scott Abbey can you share your project file with us so we can check it? There have been no changes that could have affected latency like that. Did you try reverting to the last release to verify that this is a new issue? LP MB has some delay but nothing close to 1 second so there is something else going on. Another thing to check. What is the ThreadSchedulingModel variable in preferences | Configuration file set to?

Expecting plugins to update while rendering is not a common workflow. The app is deliberately using all resources to export the audio not update the UI. Are you doing a fast bounce when exporting? Plugin views will not update while doing that because the UI thread is blocked while exporting audio. Try disabling fast bounce when exporting.

These are all over Boston near the harborwalk.

That riff you played last night was pretty killing so don't sell yourself short 😛 Seriously all of us here have better things to do with our lives than steal somebody's personal information. We wouldn't be doing this if we didn't care about developing top notch software for people to make music. I think that would be a fair thing to say about most companies building music software. While it might be hard to imagine how this software could be free, its a testament that good things can happen once in a while. Life is too short to mistrust everything.

If you want to use Youtube and other apps while using Cakewalk at the same time use WASAPI shared mode.

Unless you sent the wrong file, the dump file you sent references a crash in your Roland Studio Capture driver. Cakewalk itself isn't crashing, nor is it related to east west as far as I can see. Can you open Cakewalk without crashing and create a new project or load other projects? If the same crashes persist you can follow up with Roland. We can't solve crashes in drivers. Send some more of your dump files so we can verify if the crashes are all the same. You can also try switching to WASAPI shared mode to test whether the crash goes away. Here are the details from your crash. ======== BUGCHECK_STR: APPLICATION_FAULT_INVALID_POINTER_WRITE PRIMARY_PROBLEM_CLASS: APPLICATION_FAULT LAST_CONTROL_TRANSFER: from 00000000081127df to 000000000811a660 STACK_TEXT: 00000000`0013f138 00000000`081127df : 00000000`39db1040 00000000`0000b7da 00000000`7ffe0008 00000000`7ffe0010 : RDAS1138+0xa660 00000000`0013f140 00000000`39db1040 : 00000000`0000b7da 00000000`7ffe0008 00000000`7ffe0010 00000000`083697a0 : RDAS1138+0x27df 00000000`0013f148 00000000`0000b7da : 00000000`7ffe0008 00000000`7ffe0010 00000000`083697a0 00000000`08115b95 : 0x39db1040 00000000`0013f150 00000000`7ffe0008 : 00000000`7ffe0010 00000000`083697a0 00000000`08115b95 00000000`083659b0 : 0xb7da 00000000`0013f158 00000000`7ffe0010 : 00000000`083697a0 00000000`08115b95 00000000`083659b0 00000000`00000000 : SharedUserData+0x8 00000000`0013f160 00000000`083697a0 : 00000000`08115b95 00000000`083659b0 00000000`00000000 00000000`083659b0 : SharedUserData+0x10 00000000`0013f168 00000000`08115b95 : 00000000`083659b0 00000000`00000000 00000000`083659b0 00000000`00000000 : 0x83697a0 00000000`0013f170 00000000`083659b0 : 00000000`00000000 00000000`083659b0 00000000`00000000 00000000`0013f260 : RDAS1138+0x5b95 00000000`0013f178 00000000`00000000 : 00000000`083659b0 00000000`00000000 00000000`0013f260 00000000`0013f264 : 0x83659b0 MODULE_NAME: RDAS1138 IMAGE_NAME: RDAS1138.DLL DEBUG_FLR_IMAGE_TIMESTAMP: 523a635c STACK_COMMAND: ~0s ; .ecxr ; kb FAILURE_BUCKET_ID: INVALID_POINTER_WRITE_c0000005_RDAS1138.DLL!Unknown BUCKET_ID: APPLICATION_FAULT_INVALID_POINTER_WRITE_RDAS1138+a660

@Bill Campbell please PM a link to the project file and we can see if we can reproduce the problem.

@Jacques Boileau the registration of plugins itself is independent of language. The most common reason for that failure is Windows blocking COM object registration but it can also happen due to missing dll dependencies which can happen due to a missing or failed runtime redistributable from Microsoft. These issues are are unfortunately one of the downsides of COM dlls. This only applies to the older DX plugins of course. Of course if the plugins are not being installed at all that is a different issue. Jon is investigating that now.

Um no there is nothing "faulty" about how Cakewalk updates the registry. You make a lot of assumptions that every problem is somehow the DAW's fault. There are plenty of environmental factors including Windows updates that can cause symptoms like this.

We only write premium highest quality unleaded code. Its child and pet safe.

Thanks. Touch support for arranger is not yet available.

If the last time you used cakewalk was 20 years ago then you should be prepared to have a bit of a learning experience. Have you used any current generation music software? Everyone has installers with optional components although some integrate it directly into the program (which is a good thing) Prior to BandLab acquiring Cakewalk we had an installer called command center which was similar in principle to bandlab assistant though more sophisticated. It also allowed to install optional components (many more than what we do now) Bandlab is the company that owns Cakewalk. To use the software the requirement is to create an account that established you as a user. Bandlab is also a powerful cloud platform for recording and sharing music using mobile devices it the web. It has over 20 million users. There is no requirement to use that if you don't need it but it's free and available to any Cakewalk user. In short by default we install the bare minimum for Cakewalk to run to save bandwidth. There is zero bloatware.

@Hillmy as I explained before this will not happen with new users. That is the whole point of this change.

Correct since we have no idea whether this is a user edited preset or not, we can't remove them. Only a fresh install will have the new presets. The other alternative is to manually delete the presets from the registry and rerun CbB while holding CTRL key down, then tell it to personalize. That should recopy the factory presets. I've not tested this mechanism. That said many of the previous presets should work now since we added several plugins that were utilized by them.

Not related to update. Something environmental caused the plugin to lose it's authorization.

The changes we made affects new installs. If you previously had the preset it won't get automatically removed since the installer never removes existing presets.

A big can exist forever if it's not reported. Things don't get fixed automatically. I have never heard of this one. Please write up a proper description and recipe for it as a separate post and we can look at it for a future release.

@Variousartist this should be fixed in the final release. Several testers have already confirmed that its ok now. I've optimized the code so that it will throttle back and consume less UI bandwidth freeing up processing of input messages.

This wouldn't be a Cakewalk problem. All fast bounce does is render audio faster than realtime. If the plugin isn't handling this it would be something the plugin vendor needs to investigate on their end.

Got it thanks. Mark will take a look at it tomorrow.

@sreams check your PM. I'd like you to do a test with a build that should address this issue. If anyone else had this same issue reproducibly and would like to test a build, PM me.

@Kevin Walsh who did you send it to?